Committee Meeting Agenda: 13 March 2019
The DocBook Technical Committee will
meet on Wednesday,Â13
(11am PDT, 12noon MDT, 1pm CDT, 2pm
EDT, and 8pm CET)
Regrets: Sabine Ocker
2.ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂAccept the minutes 
of the previous meeting (13 February 2019)Â
3. Next meeting:Â10 April 2019
4. Review of the agenda.Â
5. Review of open action items
a. Â Bob to discuss with Jirka how
to trim down the assembly model with the xinclude support.
b.ÂÂÂÂÂBob to update documentation of Assembly
proposals in 5.2
Bob has the content, but needs to understand the process.
Bob needs to get more info from Norm on how to maintain the
documentation in github.
Bob/Jirka to include
Assembly proposals in 5.2:
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂi.ÂÂÂÂÂÂJirka provided samples, Bob still needs
to test. CONTINUED.
i.ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂGrammar is used to identify a particular
set of content. A matching grammar should also appear on the
transform to convert the content appropriately.
ii.ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂname is used to identify a particular
set of content, with a matching transform to some
iii.ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂgrammar = inputs to normalize to DocBook
iv.ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂname = outputs from DocBook to a
v.ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂset name OR grammar, but not both on
both transform and resource
vi.ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂdo not use mime type for grammar
**Bob clarify according to minutes:
Add @name to transform and @transform to resource. Need to
reflect changes (after test) to the documentation.Â
d. 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.
ACTION: Bob follow up with the
submitter to see if generic info would work.
ACTION: All to review with someone
familiar with various programming languages to see if this
provides enough detail to map to various languages
to create an integrated proposal for legalsection, all to
review before next meeting for approval.ÂÂÂÂ
f. Bob to review models
for issue #112 and address schema corrections.
g. ALL: start work on action items
h. Scott to send a reminder mid-month.
i. OASIS has gone through a re-branding
effort, which will impact future deliverables. Rework
9. Social media presence for DocBook
Purpose: To raise awareness of
actions (votes, calls for information, etc.)
10. Review of
Requests for Enhancement
To find a Github issue by number,
enter the URL (on one line):
No new issues.
Open Issues (Note: items that have
been accepted are still open
on Github until included in a
but they are not listed here):
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
Consider for Publishers.
100 DocBook 5.1 catalog.xml uses
103 XML DTD of DocBook 5.1
Library (tentative name)Â- Supercedes 107,
108, 109, 110
and best regards,
Data Standards Technical Advisory Board
DocBook TC (Secretary), Publishers SC (Chair)
DITA TC, Tech Comm SC, LwDITA SC, Learning Content SC
DITA Adoption TC
Augmented Reality in Information Products (ARIP) TC
and Knowledge Services
55 Inverness Drive East |ÂEnglewood,
contains only administrative, uncontrolled data under U.S.
International Traffic in Arms Regulations.