[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: DocBook Technical Committee Meeting Minutes: 08 JUN 2022
|
DocBook Technical Committee Meeting Minutes: 08 JUN 2022 ============================================================= The DocBook Technical Committee met on Wed, : 08 JUN 2022
Next meeting: 13 JUL 2022
a. ALL: Test v5.2 CR 1 (https://github.com/docbook/docbook/releases/tag/5.2CR1 ) STATUS: Release Notes need to be added to the zip file for CR2. Bob provided, so Norm to include in next build. Include the Release Notes in the announcement to the list. A PR was requested: Allow db:modifier after db:methodname and the parameters in db:constructorsynopsis #232 ACTION: Bob to create issue for this in the github tracker
ACTION: Norm to generate CR2 to include this change as well as the Release Notes. b. Norm to update TDG based on latest content. Bob to provide Release Notes for the package (changes since 5.1). STATUS: In-progress. ACTION: TC will need to review to ensure the doc matches the schema. c. Bob to announce schema to the list and get feedback. Refer people to the stylesheets that Norm has updated for processing. COMPLETE. d. Norm to package as v5.2 Candidate 1, notify the TC to review before sending to public. Plan for comment review period to end sometime in June or July. (60 day review from time of release candidate availability) COMPLETE e. Eliot Kimber requested clarification on targetdoc and olink. Bob:
The targetdoc attribute is *not* a URI.
The targetdoc is meant to be just an identifier string, unique among targetdocs but not an xml-id. ACTION: Norm to update TDG regarding targetdoc:
The targetdoc attribute specifies a unique look up key for the target document in the context of an implementation-dependent olink resolution database where the look up keys are mapped to the target document such that the DocBook processor
can translate source olink into resolvable links in deliverables generated from the document that specifies the olink.
Purpose: To raise awareness of actions (votes, calls for information, etc.) a. ACTION: announce CR2 when available. (30 day review)
229 Add a packageref attribute to all of the children of packagesynopsis Status: included in CR1. 228 Embedding an indexterm inside indexterm/primary or indexterm/secondary should not be allowed Status: nested indexterm is not meaningful. Should use xref to refer to other terms.
ACTION: Document that it should not be done, but flag that it will be deprecated in v6.0 (if that ever happens). 222 Request for value attribute with the <listitem> tag Status: moved to Definitive Guide (doc issue) https://github.com/docbook/defguide/issues/84 221 XPath _expression_ error in Schematron file for 5.2b10a5? 219 Assembly: allow <structure> as root element 201 use correct OASIS URLs in catalog.xml Status: Complete 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: Complete 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? 163 Add
Transclusion Attributes to Assembly Schema 164 Allow
pubwork attribute on biblioentry 171 Support
CRediT for contributor info and allow several roles? 180 title
and titleabbrev: do they both need to be either inside <info> or outside? 188 include.xsl doesn't work if there is div around overridden definitions inside include Status: Jirka added a fix for this. ACTION: Check CR1 |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]