[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: DocBook Technical Committee Meeting Minutes 10 NOV 2021
DocBook Technical Committee Meeting Minutes: 10 NOV 2021
=============================================================
The DocBook Technical Committee met on Wed, : 10 NOV 2021
Scott Hudson
Bob Stayton
Norm Walsh
Larry Rowland
Next meeting: 08 DEC 2021
a. ALL: Test
v5.2 b11 (https://github.com/docbook/docbook/pull/218 )
Purpose: To raise awareness of actions (votes, calls for information, etc.)
Norm:
Programming languages vary *a lot* and part of the challenge here is elements that can be used across a variety of languages. 1. Java doesn’t have anything it calls namespaces. It has packages that have a lot of functional similarity to namespaces in other languages. 2. C++ and C# have namespace. They are clearly a wrapper around other language constructs. 3. What Python calls namespaces are really about scope of identifiers. There are only a few namespaces and programmers can’t add new ones. Python does have packages that you can import and, like Java, these behave a lot like what other languages use a thing called “namespaces” for. 4. Perl, like Java and Python, has packages which scope names. I suggest we change the content model of namespacesynopsis to something like this: [ db:refname [ "namespacesynopsis" ] db:refpurpose [ "The syntax summary for a name space definition" ] ] div { db.namespacesynopsis.info = db._info.title.forbidden db.namespacesynopsis.role.attribute = attribute role { text } db.namespacesynopsis.attlist = db.namespacesynopsis.role.attribute? & db.common.attributes & db.common.linking.attributes & db.language.attribute? db.namespacesynopsis = element namespacesynopsis { db.namespacesynopsis.attlist, db.namespacesynopsis.info, db.synopsisinfo*, (db.package | db.modifier)*, (db.namespace | db.namespacename), (db.package | db.modifier)*, (db.synopsisinfo | db.classsynopsis | db.constructorsynopsis | db.destructorsynopsis | db.enumsynopsis | db.fieldsynopsis | db.funcsynopsis | db.macrosynopsis | db.methodsynopsis | db.synopsis | db.typedefsynopsis | db.unionsynopsis | db.namespacesynopsis)* } } that makes package a container again, rather than needing namespace and/or confusing it with xml namespaces. Bob: This is about documenting programming languages, so we need to make it as efficient. Consensus: rename namespacesynopsis to packagesynopsis. Test the implementation of this in the next beta (b12) with a plan to approve in Dec meeting.
222 Request for value attribute with the <listitem> tag ACTION: Norm to clarify in a documentation update 221 XPath _expression_ error in Schematron file for 5.2b10a5? ACTION: Norm to include in next beta with a pull request 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: TC to test schemas |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]