Re: [docbook-tc] DocBook Technical Committee Meeting Agenda: 09 DEC 2020

DocBookÂTechnical Committee MeetingÂAgenda:Â09 DEC 2020

=============================================================

TheÂDocBookÂTechnical CommitteeÂwill meet on Wed,Â09 DEC 2020
(11am PDT, 12noon MDT, 1pm CDT, 2pm EDT, and 8pm CET)

Roll call

Sabine gave regrets

Accept the minutes [1] of the previous meeting (11 NOV 2020).ÂÂ

Next meeting:Â13 JANÂ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.

docbook-tc message