[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: DocBook Technical Committee Meeting Minutes: 13 JAN 2021
DocBook Technical
Committee Meeting Minutes: 13 JAN 2021
=============================================================
The DocBook Technical Committee met on Wed, 13 JAN 2021
Next meeting: 10 FEB 2021
a. Norm
to update the Definitive Guide. [Continued]
b. Scott to discuss with Jirka
to create a beta of DocBook Publishers v 5.2, which includes the accepted additions/changes ( Issues
99, 86, 85, 84, 82, 81) COMPLETE. Jirka to create beta DocBook Publishers
v5.2 TBD (scott send reminder)
c. Jirka to include the @class="legal"
for all of the sect levels, but let's leave unresctricted. Allow extension through the @class="other" and @otherclass attributes. Either section in legalnotice, or as a regular section with the class attribute would be considered.
d. Scott to follow up with Norm
for Twitter account access [CONTINUED]
e. Bob to discuss implementation of #141, 149, 150, 151, 152, 153,
156 with Jirka into next beta. [Bob to discuss with Norm instead. CONTINUED].
f. Bob to follow up with Dick on #172 [Fixed in 5.2, 5.0.1. If needed,
could fix in 5.1.1. ACTION: Bob has started OASIS process to create 5.1.1 version. [IN PROGRESS] Norm has initiated the fix.]
g. Scott to follow up with requester for #171 [Role attr should
be sufficient per Norm's suggestion. Scott to follow up w/user] COMPLETE
h. Bob
to follow up with Norm on #158 [CONTINUED]
i. Sabine to reach out to Paligo folks for input on any addition requirements for v5.2 COMPLETE.
6. Social media presence for DocBook
Purpose: To raise awareness of actions (votes, calls for information, etc.)
7. Remaining items for v5.2 Committee Spec
a. DocBook for
Publishers v5.2, want to see this through completion.
1. Add Issues 99, 86, 85, 84,
82, 81 schema and formalize the release. ACTION: Jirka to create beta schema TBD.
8. New issues for discussion:
9. Remanining issues
111 DocBook
Library (tentative name) Status: Norm implemented his suggestions and Bob approved the Pull Request merge. Originator objected to the merge.
141 The
definition of db._any is too narrow
148 Should
simplesect be allowed in legalsection?
149 Should
legalsection be allowed in topic?
150 Support
legal sections with a class attribute?
Adopt the @class="legal" for all of the sect levels, but let's leave unresctricted. Allow extension through the @class="other" and @otherclass attributes. Either section in legalnotice,
or as a regular section with the class attribute would be considered.
ACTION: Bob to follow up with Norm on implementation.
151 Add
a schematron rule for the callout type constraint
152 Add
schematron rules for productionset reference constraints
153 Future
use comments for XLink elements
156 docbookxi
doesn't support XInclude 1.1
157 Propose
algorithm float along with figures, tables, and examples?
158 Get
rid of docbook-schemas Maven artifact dependencies
163 Add
Transclusion Attributes to Assembly Schema
164 Allow
pubwork attribute on biblioentry
171 Support
CRediT for contributor info and allow several roles?
172 DB5.1:
Schematron anomaly with the rule: "Root must have version"
180 title
and titleabbrev: do they both need to be either inside <info> or outside? 10. Review of DocBook charter All to review and send comments/vote over email. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]