DocBook Technical Committee Meeting Agenda: 13 June 2018
=============================================================
The DocBook Technical Committee meets on Wednesday, 13 June 2018
(11am PDT, 12noon MDT, 1pm CDT, 2pm EDT, and 8pm CEST)
Meeting number (access code): 890 083 874
Meeting password: Please obtain your meeting password from Scott Hudson.
Join by phone
1-888-787-5387 U.S Toll Free-high cost
+1-425-943-7320 U.S. NW
Czech Republic Prague (420) 239-018-563
Czech Republic TollFree 800-050349
1. Roll call
2. Accept the minutes [1] of the previous meeting (9 May 2018)
3. Next meeting: 11 July 2018
a. Regrets: Scott
4. Review of the agenda.
5. Review of open action items
a: Bob to update Docbook.org to reflect Errata 01 once the schema is available on the site for download.
b. Jirka will prepare a new release to incorporate <formalgroup> (5.2).
c. Bob to follow up with Jirka to determine why the namespace was lost (issue 88).
d. Bob to fix the catalog as part of the 5.1 Errata 01.
e. Larry to create a candidate for the necessary schema changes to add XInclude support for Assemblies for DocBook 5.2. CONTINUED.
f. Larry to re-post legalnotice examples to help with the classification. (As agreed in last mtg to
make legalnotice a block structure to help the current issues and add a class attribute or attribute value to article, appendix, section, etc)
g. Bob/Jirka to include Assembly proposals in 5.2:
i.
Grammar is used to identify a particular set of content. A matching grammar should also appear on the transform to convert the content appropriately.
ii.
name is used to identify a particular set of content, with a matching transform to some non-standard output.
iii.
grammar = inputs to normalize to DocBook
iv.
name = outputs from DocBook to a non-standard format
v.
set name OR grammar, but not both on both transform and resource
vi.
do not use mime type for grammar
h. Bob to create draft specification for 5.0.1 (COMPLETED)
6. Committee Draft for 5.0.1 [2]
7.
Structure as a resource. Should a resourceref be allowed to point to a structure id?
The idea being that a structure could be defined as a resource that could be used in another part of the structure.
8. Social media presence for DocBook
Purpose: To raise awareness of actions (votes, calls for information, etc.)
Announce availability of 5.0.1 for review?
9. Review of Requests for Enhancement
To find a Github issue by number, enter the URL (on one line):
github.com/docbook/docbook/issues
Open Issues (Note: items that have been accepted are still open
on Github until included in a release,
but they are not listed here):
71 license tag
78 Schema website should be updated
88 DB 5.0: @name -> title change not published on docbook.org
93 Diff between doc of resource element and Assembly schema
94 Allow subfigures (accepted)
99 Add <endorsement> to <info>
100 DocBook 5.1 catalog.xml uses incorrect version
102 Add
"interface" value to systemitem class (accepted)
NEW:
103 XML DTD of DocBook 5.1
Links:
[1] https://www.oasis-open.org/apps/org/workgroup/docbook/email/archives/201805/msg00005.html
[2] https://www.oasis-open.org/apps/org/workgroup/docbook/documents.php
Thanks and best regards,
--Scott
Voting member:
Boeing Data Standards Technical Advisory Board
OASIS DocBook TC (Secretary), Publishers SC (Chair)
OASIS DITA TC, Tech Comm SC, LwDITA SC, Learning Content SC (Secretary)
OASIS DITA Adoption TC
OASIS Augmented Reality in Information Products (ARIP) TC
Scott Hudson
Content Strategist, Digital Aviation Learning and Development
Jeppesen, A Boeing Company
55 Inverness Drive East
Englewood, CO 80112
303-328-6228 | Cell: 303-350-7934
This document contains only administrative, uncontrolled data under U.S. International Traffic in Arms Regulations.