← Prev in month ← Prev in thread
Next in thread → Next in month →

DocBook Technical Committee Meeting Minutes: 12 June 2019

From
Scott Hudson
Date
2019-06-12T18:21:00+00:00
ID
Thread
DocBook Technical Committee Meeting Minutes: 12 June 2019
DocBook Technical Committee Meeting   Minutes: 12 June 2019

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

The DocBook Technical Committee will   met   on Wednesday,   12 June 2019

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

1.

Roll call

a.

Regrets: Sabine Ocker

b.

Scott Hudson

c.

Bob Stayton

d.

Larry Rowland

  2.
Accept the minutes [1] of the previous meeting (08
  May 2019)

  3. Next meeting:   10 July 2019

                                a. Larry may/may not be able to attend, but will keep us posted.

  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.


  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.





  ACTION: All to review with someone familiar with various programming languages to see if this provides enough detail to map to various languages.

  ACTION: Larry to follow up on github issue and allow requester to respond.  COMPLETED



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

  Scott and Bob reviewed. No problems, but would like to confirm with Jirka.

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.

  Larry tested the capabilities of the existing proposal, and that it works as-is. Not needed for Sect1, Sect2, etc. -> only for section.
Norm wanted to ensure that the changes were made to the appropriate source files (for proper integration), but no changes to the proposal.
ACTION: Bob to have Norm/Jirka document the integration process.

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

  Some progress!

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

  [still needs work!]

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://www.oasis-open.org/apps/org/workgroup/docbook/email/archives/201904/msg00003.html

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





  Thanks and best regards,



  --Scott



  Voting member:

  Boeing Data Standards Technical Advisory Board

  OASIS DocBook TC (Secretary), Publishers SC (Chair)

OASIS DITA TC, Tech Comm SC, LwDITA SC, Learning Content SC (Secretary)

OASIS DITA Adoption TC

  OASIS Augmented Reality in Information Products (ARIP)

TC

Scott Hudson

Content Technology Strategist

Information and Knowledge Services

_____________________________________
  Jeppesen

A Boeing Company

 ph: 303.328.6228

Mobile : 303.350.7934


 55 Inverness Drive East
Englewood,
  CO  80112

www.jeppesen.com



  This document contains only administrative, uncontrolled data under U.S. International Traffic in Arms Regulations.
← Prev in month ← Prev in thread
Next in thread → Next in month →