[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: DocBook Technical Committee Meeting Agenda: 13 JAN 2021
DocBook Technical Committee Meeting Agenda: 13 JAN 2021
The DocBook Technical Committee will meet on Wed, 13 JAN 2021
Next meeting: 10 FEB 2021
a. Norm to update the Definitive Guide. [TBD]
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
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 to start OASIS process to create 5.1.1 version. 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
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
Library (tentative name) Status: Norm implemented his suggestions and Bob approved the Pull Request merge. Originator objected to the merge.
definition of db._any is too narrow
simplesect be allowed in legalsection?
legalsection be allowed in topic?
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.
a schematron rule for the callout type constraint
schematron rules for productionset reference constraints
use comments for XLink elements
doesn't support XInclude 1.1
algorithm float along with figures, tables, and examples?
rid of docbook-schemas Maven artifact dependencies
Transclusion Attributes to Assembly Schema
pubwork attribute on biblioentry
CRediT for contributor info and allow several roles?
Schematron anomaly with the rule: "Root must have version"
and titleabbrev: do they both need to be either inside <info> or outside?