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
-
Accept the minutes [1] of the previous meeting (11 Dec 2019)
- Review of the agenda
-
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.)
Â
-
Remaining items for v5.2
Committee Spec
-
DocBook for Publishers v1.1: Add Issues 99, 86, 85, 84,
82, 81 schema and formalize the release.
-
Include Library proposal
(#111)
-
DocBook for Publishers v1.1: Add Issues 99, 86, 85, 84,
82, 81 schema and formalize the release.
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
