← Prev in month
← Prev in thread
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 (11am PDT, 12noon MDT, 1pm CDT, 2pm EDT, and 8pm CET) Roll call Accept the minutes [1] of the previous meeting (11 NOV 2020). Next meeting: 10 FEB 2021 Review of open action items 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. [NORM to implement. Bob to follow up] 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 111 DocBook Library (tentative name) Status: Norm implemented his suggestions and Bob approved the Pull Request merge. Originator objected to the merge. ACTION: Bob follows up with Norm. 141 The definition of db._any is too narrow Status: CLOSED. 148 Should simplesect be allowed in legalsection? Status: CLOSED. 149 Should legalsection be allowed in topic? Status: CLOSED. 150 Support legal sections with a class attribute? Status: Accepted. From 14OCT2020 minutes: 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 Status: Accepted and closed. ACTION: Bob to follow up with Norm on implementation. 152 Add schematron rules for productionset reference constraints Status: Accepted, closed, and implemented. ACTION: We will need to check the next beta to confirm. 153 Future use comments for XLink elements Status: This became the meta element in info. Accepted, closed, and implemented in PR #176. ACTION: Check next beta. 156 docbookxi doesn't support XInclude 1.1 Status: Accepted, closed, and implemented in PR #175. ACTION: Check next beta. 157 Propose algorithm float along with figures, tables, and examples? Status: This became type attribute. Accepted, closed, and implemented in PR #185. ACTION: Check next beta. 158 Get rid of docbook-schemas Maven artifact dependencies Status: CLOSED. Norm says this does not affect the schema but is a build artifact. 163 Add Transclusion Attributes to Assembly Schema Status: tentatively approved, need to see beta. ACTION: Bob to ask Norm to implement it. 164 Allow pubwork attribute on biblioentry Status: Accepted, closed, and implemented in PR #184. ACTION: Check next beta. 171 Support CRediT for contributor info and allow several roles? Status: Norm suggested using @role. Scott followed up and requestor is OK to implement using @role. ACTION: Bob to ask Norm to implement it 172 DB5.1: Schematron anomaly with the rule: "Root must have version" Status: Accepted and implemented as 5.1.1 by Norm in PR #181. ACTION: Bob to prepare OASIS document to create a 5.1.1 approval process. 180 title and titleabbrev: do they both need to be either inside <info> or outside? Status: TC not inclined to change the schema. ACTION: Bob to ask Norm to update TDG to clarify this.
← Prev in month
← Prev in thread