Re: [docbook-tc] DocBook Technical Committee Meeting Agenda: 12 FEB 2020

I could use the time if we don t have any updates,
  Sabine-
From:
<> on behalf of "Rowland, Larry" <>
Date:  Tuesday, February 11, 2020 at 11:28 AM
To:  Scott Hudson <>, Bob Stayton <>, "" <>
Subject:  RE: [docbook-tc] DocBook Technical Committee Meeting Agenda: 12 FEB 2020



Sounds like dropping tomorrow s meeting makes sense.  I don t  have anything to add on updates.



Regards,

Larry Rowland
From:   [mailto:]
  On Behalf Of  Scott Hudson
  Sent:  Tuesday, February 11, 2020 9:25 AM
To:  Bob Stayton <>; 
Subject:  Re: [docbook-tc] DocBook Technical Committee Meeting Agenda: 12 FEB 2020



I don't have any updates. I could use the time to work on my action item follow-ups



--Scott
From:

< 
> on behalf of Bob Stayton < 
>
Date:  Tuesday, February 11, 2020 at 9:17 AM
To:  "  " < 
>
Subject:  Re: [docbook-tc] DocBook Technical Committee Meeting Agenda: 12 FEB 2020



I'm not sure we need to meet this week.  We are waiting for Jirka to prepare the schema changes, but he is tied up with the upcoming XML Prague conference and won't get to the
  work until the second half of February.  Does anyone have other business that needs a meeting to discuss?
  Bob Stayton


On 2/10/2020 8:22 PM, Scott Hudson wrote:

DocBook Technical Committee Meeting Agenda: 12 FEB 2020

=============================================================

The DocBook Technical Committee will meet on Wednesday, 12 FEB 2020

(11am PDT, 12noon MDT, 1pm CDT, 2pm EDT, and 8pm CET)



  1.         Roll call

2.

Accept the minutes [1] of the previous meeting (11 Dec 2019)

3.

Review of the agenda

4.

Review of open action items

  a.   Extension for synopsis elements

              (Issue #111)

  Need ALL to test before we can have a proposal to vote on. Larry has tested. No issues. Requester is already using in a local variant. Larry thinks it's in good shape. Need someone that is really good at schema to
  test (Jirka?). ACTION: Bob to ask Jirka to review.

  Regarding new synopsis element:

           Bob will ask Jirka to document  and test the schema

           Larry says the Definitive Guide will need to be updated to document the schema extensions, which will require some expertise.

           Bob suggests that perhaps we could ask Norm to update the Definitive Guide.

           Larry offered to collaborate with Norm or whomever will work on this and to draft useful descriptions of the multiple programing constructs
   (the  C++ vs. python extensions for example)

           No timeline was determined for either Jirka or Norm s efforts

  b.            Bob to request schema change to Jirka/Norm to add the fix for 112 refentry in sect 1 CONTINUED.

  c.       Bob to discuss with Jirka to create a beta with DocBook Library (
https://github.com/docbook/docbook/issues/111  )

models.



  d. Scott to discuss with Jirka to create a beta of DocBook Publishers v1.1 (based on 5.2), which includes the accepted additions/changes (   Issues 99, 86, 85, 84, 82,
  81)


5.

Social media presence for DocBook

  Purpose: To raise awareness of actions (votes, calls for information, etc.)



5.

Remaining items for v5.2 Committee Spec

a.

DocBook for Publishers v1.1: Add Issues 99, 86, 85, 84, 82, 81 schema and formalize the release.

b.

Include Library proposal (#111)

6. Review of Requests for Enhancement

  To find a Github issue by number, enter the URL (on one line):

  github.com/docbook/docbook/issues



  Open Issues (Note: items that have been accepted are still open

  on Github until included in a release, but they are not listed here):



  71 license tag



  78 Schema website should be updated



  93 Diff between doc of resource element and Assembly schema



  99 Add <endorsement> to <info>

  Consider for Publishers.



  100 DocBook 5.1 catalog.xml uses incorrect version



  103 XML DTD of DocBook 5.1



  111
DocBook Library (tentative name)
  -
  (Supercedes 107, 108, 109, 110; other issues closed by Scott 6/10).



  112 refentry in sect 1 - Needs to be addressed in schema. (bug fix)



  117 Allow info in listitem

               APPROVED: Accept info in listitem for v5.2. Norm suggested:
a separate synopsis.rnc module makes sense. All of the synopses are currently in programming.rnc





Links:

  [1]   https://lists.oasis-open.org/archives/docbook-tc/201912/msg00003.html

[2]    http://github.com/docbook/docbook/issues






  Thanks and best regards,



  --Scott


  Scott Hudson

Content Technology Strategist, DS&A Information and Knowledge Services

  Jeppesen, A Boeing Company

  55 Inverness Drive East
Englewood, CO 80112

  303-328-6228
Cell: 303-350-7934





http://www.jeppesen.com