[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: DocBook Technical Committee Meeting Minutes: 08 May 2019
|
DocBook Technical Committee Meeting Minutes: 08 May 2019
=============================================================
The DocBook Technical Committee will met on Wednesday, 08 May 2019
(11am PDT, 12noon MDT, 1pm CDT, 2pm EDT, and 8pm CET)
1.
Roll call
2. Accept the minutes [1] of the previous meeting (10
April 2019)
3. Next meeting: 12 June 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.
ACTION: All to review with someone familiar with various programming languages to see if this provides enough detail to map to various languages. Larry provided a thorough analysis and feedback on the list. ACTION: Larry to follow up on github issue and allow requester to respond.
ACTION: Bob to send proposed structure to docbook-apps list to get additional input. 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.
c. ALL: start work on action items earlier. CONTINUED
Some progress!
d. Scott to send a reminder mid-month. CONTINUED
[still needs work!]
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
117 Allow info in listitem
associate some metadata with a listitem, but no place to put it. Sabine: there is an info container on the list, itself, but how would info on the listitem level differ from the metadata at the list level? Bob: if multiple contributors work on a list, this would help to identify what changed per list item. Larry: makes sense Scott: makes sense ACTION: Bob to follow up with Jirka to create a mocked-up schema change to vote on.
Open Issues (Note: items that have been accepted are still open
on Github until included in a release,
but they are not listed here): Docbook-comment submission about graphing Docbook element relationships. Scott: tried to find a tool that would work, but didn't have success Larry: complexities of parent relationships might be a problem. Most graphic tools depend on a mathematical graph behind them to make it work. Requires someone familiar with the recursive
"gotchas" to make this work. Might take a look if has time.
71 license tag
78 Schema website should be updated
88 DB 5.0: @name -> title change not published on docbook.org CLOSED
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
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
This document contains only administrative, uncontrolled data under U.S. International Traffic in Arms Regulations. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]