← Prev in month ← Prev in thread
Next in thread → Next in month →

DocBook Technical Committee Meeting Agenda: 13 JUL 2022

From
Scott Hudson
Date
2022-07-12T23:38:00+00:00
ID
Thread
DocBook Technical Committee Meeting Agenda: 13 JUL 2022
DocBook

Technical Committee Meeting Agenda: 13 JUL 2022

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

The
DocBook
 Technical Committee will meet on Wed, : 13 JUL 2022  (11am PDT, 12noon MDT, 1pm CDT, 2pm EDT, and 8pm CET)
Roll call
Accept the minutes [1] of the previous meeting ( 08 JUN  2022).
Next meeting: 10 AUG 2022
Review of open action items
a.           ALL: Test v5.2 CR 1 ( https://github.com/  docbook  /  docbook  /releases/tag/5.2CR1  )
b. Bob to create issue for db:modifier in the github tracker  (#232 COMPLETE)
c.  Norm to generate CR2 to include this change as well as the Release Notes. (PR#235 COMPLETE)
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. 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.

Social media presence for   DocBook
Purpose: To raise awareness of actions (votes, calls for information, etc.)
a.       ACTION: announce CR2 when available. (30 day review)

Remaining items for v5.2 Committee Spec
Completion schedule for v5.2
Collect review feedback (if any) from 60-day public comment
Remaining issues
234
Allow db:modifier after db:methodname and the parameters in db:constructorsynopsis
Status: included in DocBook 5.2CR2 (PR#235)
229   Add a packageref attribute to all of the children of packagesynopsis
 Status: included in V5.2CR2.
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?
                Status: fixed 14NOV2021

219  Assembly: allow <structure> as root element
              Status: Approved on 11AUG2021.

201  use correct OASIS URLs in catalog.xml
Status: Complete

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: Complete

151  Add  a schematron rule for the callout type constraint    Status: Accepted and closed.    ACTION: Check V5.2CR2

152  Add  schematron rules for productionset reference constraints    Status: Accepted, closed, and implemented.    ACTION: Check V5.2CR2

153  Future  use comments for XLink elements     Status: This became the meta element in info.  Accepted, closed, and implemented in PR #176.   ACTION: Complete.

156
docbook  xi  doesn't support XInclude 1.1    Status: Accepted, closed, and implemented in PR #175.   ACTION: Complete.

157  Propose  algorithm float along with figures, tables, and examples?    Status: This became type attribute. Accepted, closed, and implemented in PR #185.    ACTION: Complete.

163  Add  Transclusion Attributes to Assembly Schema    Status: tentatively approved, need to see beta.    ACTION: Check V5.2CR2.

164  Allow  pubwork attribute on biblioentry    Status: Accepted, closed, and implemented in PR #184.   ACTION: Complete.

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: Check V5.2CR2.

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.

188 include.xsl doesn't work if there is div around overridden definitions inside include
Status: Jirka added a fix for this.
ACTION: Check V5.2CR2
← Prev in month ← Prev in thread
Next in thread → Next in month →