Hello All
Recording my email votes to the issues outlined in item 5 of the agenda below.
Sabine
From: <
docbook-tc@lists.oasis-open.org> on behalf of Scott Hudson <
scott.hudson@servicenow.com>
Date: Friday, August 21, 2020 at 2:59 PM
To: "docbook-tc@lists.oasis-open.org" <
docbook-tc@lists.oasis-open.org>
Subject: [docbook-tc] DocBook Technical Committee Meeting Minutes: 21 AUG 2020
DocBook Technical Committee Meeting Minutes: 21 AUG 2020
=============================================================
The DocBook Technical Committee met on Friday, 21 AUG 2020
(11am PDT, 12noon MDT, 1pm CDT, 2pm EDT, and 8pm CET)
Roll call
Bob Stayton
Scott Hudson
Larry Rowland
Regrets: Sabine Ocker
Accept the minutes [1] of the previous meeting (13 MAY 2020).
Bob moves, Scott seconds. Accepted.
Next meeting: 09 SEP 2020
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: Jirka to update schemas CONTINUED.
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.
CONTINUED.
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) CONTINUED.
Recording of email votes:
Issue #141 - definition of db._any is too narrow:
21JUL2020 - Motion: Bob Stayton, Second: Scott Hudson Bob = yes, Scott = yes
Sabine =Yes
Issue #149 allow legalsection in topic
21JUL2020 - Motion: Bob Stayton, Second: Scott Hudson Further discussion needed. See agenda item #6.
Issue #150 allow class="legalsection in topic
21JUL2020 - Motion: Bob Stayton, Second: Scott Hudson Further discussion needed. See agenda item #6.
Issue #151 - Add a schematron rule for the callout type constraint
21JUL2020 - Motion: Bob Stayton, Second: Scott Hudson Votes: Bob = yes, Scott = yes
Sabine= yes
Issue #152 Add schematron rules for productionset reference constraints
21JUL2020 - Motion: Bob Stayton, Second: Scott Hudson Votes: Bob = yes, Scott = yes
Sabine =Yes
Issue #153 create meta element with required @name, and optional @content, or allow any content.
21JUL2020 - Motion: Bob Stayton, Second: Scott Hudson Votes: Bob = yes, Scott = yes
Sabine=Yes
Issue #156 Add support for XInclude 1.1 (@fragid, @href, allow anywhere)
23JUL2020 Motion: Bob Stayton, Second: Scott Hudson Votes: Bob = yes, Scott = yes
Sabine=Yes
Discuss inclusion of legalsection in topic (#149) or a class attribute on the section element (#150)?
Adopt the @class="legal" for all of the sect levels, but let's leave unresctricted. It is difficult to anticipate all of the possible use cases that a restricted
model might affect. Adopters can restrict in their own custom schema if needed. 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.
What other classes might we want for sections?
ACTION: Open discussion for section classes on the mailing list. Send to social media as well.
ACTION: Scott to also post to social media for input.
"As legal notices have become more necessary and also more complicated (licensing, etc), the DocBook TC is planning to enable this type of legal content
by adding a class="legal" to section elements (including all of the section levels). As class values are typically enumerated, the DocBook TC is soliciting input on other needed classifications for sections."
The meeting had to be suspended due to fire evacuation.
7. Social media presence for DocBook
Purpose: To raise awareness of actions (votes, calls for information, etc.)
ACTION: Once 5.2 is ready, notify the list
ACTION: Scott to also post to social media for review and testing.
8. Remaining items for v5.2 Committee Spec
a. DocBook for Publishers v1.1, want
to see this through completion.
1. Add
Issues 99, 86, 85, 84, 82, 81 schema and formalize the release. Could this be done by Jirka at the same time as the 5.2 release?
b. Library proposal should be included.
1. Include
by default.
c. Status of build: + Checklist [13/18]
- [X] 14-Jun-17 allows multimediaparam in imagedata [[
https://github.com/docbook/docbook/issues/52 ][52]]
- [X] 18-Jan-17 discontinue support for XSD
- [ ] 18-Jan-17 Allow revnumber inline [[
https://github.com/docbook/docbook/issues/7 ][7]]
- [ ] 18-Jan-17 (Re)allow recursive use of optional [[
https://github.com/docbook/docbook/issues/74 ][74]]
- [ ] 21-Sep-16 license (legalsection) [[
https://github.com/docbook/docbook/issues/291 ][291]]
- [ ] 11-Apr-18 XInclude support to Assemblies [[
https://github.com/docbook/docbook/issues/54 ][54]]
- [X] 11-Dec-19 Allow info in listitem [[
https://github.com/docbook/docbook/issues/117 ][117]]
- [X] 11-Oct-17 allow zero or more instances of type [[
https://github.com/docbook/docbook/issues/91 ][91]]
- [X] 22-Jun-16 Allow Block Elements inside <abstract> [[
https://github.com/docbook/docbook/issues/58 ][58]]
- [X] 22-Jun-16 Allow <modifier> within <paramdef> [[
https://github.com/docbook/docbook/issues/59 ][59]]
- [X] 22-Jun-16 Allow <void> within <funcdef> [[
https://github.com/docbook/docbook/issues/60 ][60]]
- [ ] 9-May-18 Fix namespaces and catalog (assembly) [[
https://github.com/docbook/docbook/issues/100 ][100]]
- [X] 25-May-16 Add <danger> to list of admonitions [[
https://github.com/docbook/docbook/issues/55 ][55]]
- [X] 22-Jun-16 Add article @class with other, otherclass [[
https://github.com/docbook/docbook/issues/53 ][53]]
- [X] 11-Apr-18 Allow subfigures [[
https://github.com/docbook/docbook/issues/94 ][94]]
- [X] 13-Jun-18 incorporate <formalgroup>
- [X] 13-Feb-19 refentry in sect1 [[
https://github.com/docbook/docbook/issues/112 ][112]]
- [X] 11-Mar-20 DocBook Library for code documentation [[
https://github.com/docbook/docbook/issues/111 ][111]]
9. New issues for discussion:
#172 - DB5.1: Schematron anomaly with the rule: "Root must have
version"
#171 - Support
CRediT for contributor info and allow several roles?
#167 - The
new definition of db._any causes validation errors
#164 - Allow
pubwork attribute on biblioentry
#163 - Add
Transclusion Attributes to Assembly Schema
#158 - Get
rid of docbook-schemas Maven artifact dependencies
#157 - Propose
algorithm float along with figures, tables, and examples?
_____________________________________________
Scott Hudson
Staff, Content Tools and Engineering
docs.servicenow.com