← Prev in month ← Prev in thread

DocBook Technical Committee Meeting Agenda: 14 Aug 2019

From
Scott Hudson
Date
2019-08-12T21:18:00+00:00
ID
Thread
DocBook Technical Committee Meeting Agenda: 14 Aug 2019
DocBook Technical Committee Meeting   Agenda: 14 Aug 2019

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

The DocBook Technical Committee will   met   on Wednesday,   14 Aug 2019

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



  1.      Roll call

  2.
Accept the minutes [1] of the previous meeting (12 June 2019)

  3. Next meeting:   11 September 2019

  4. Review of the agenda.

  5. Review of open action items

  a.   Extension for synopsis elements

              (Issue #111)

  ACTION: All to review info element proposals and provide any feedback to Bob. Bob submitted samples to list 11FEB2019.CONTINUED.   Response from Stefan, but we are looking for generic constructions
  that apply to multiple languages, not specifically C++. Would need a point by point comparison to adequately determine if the Summer of Code proposal would work.



  b. ACTION: Bob to contact
dourouc05
(from
  issues list) valuate the Summer of Code work to determine if the proposal works or if there are other gaps to be considered.



c.
Larry to create an integrated proposal
  for legalsection, all to review before next meeting for approval.   CONTINUED.

  ACTION: Bob to follow up with Norm and Jirka to get input. Plan to vote at next meeting.   Need formal proposal to vote at next meeting.

d. ACTION: Bob to have Norm/Jirka document the integration process.

  e. ALL: start work on action items earlier. CONTINUED

  Some progress!

  f. Scott to send a reminder mid-month.   CONTINUED

  [still needs work!]

g.

ACTION: (Issue #117 - allow info in listitem) Bob to follow up with Jirka to create a mocked-up schema change to vote on.   CONTINUED.


i.
The
  info element is a bit complicated (some models with titles, some without). Jirka suggested to use the non-titled version.


ii.
Should
  have a formal proposal to vote on at next meeting.

  6. Social media presence for DocBook

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



  7. 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



  112
refentry
  in sect1



  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)

ACTION: Bob to request schema change to Jirka/Norm to add the fix.



  117 Allow info in listitem

  associate some metadata with a listitem, but no place to put it.



  Links:

  [1]
https://lists.oasis-open.org/archives/docbook-tc/201906/msg00002.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
← Prev in month ← Prev in thread