DocBook Technical Committee Meeting Minutes: 14 February 2018
=============================================================
The DocBook Technical Committee met on Wednesday, 14 February 2018
(11am PDT, 12noon MDT, 1pm CDT, 2pm EDT, and 8pm CEST)
1.
Roll call
Scott Hudson
Bill Burns
Dick Hamilton
Larry Rowland
Regrets: Bob Stayton
2.
Accept the minutes [1] of the previous meeting (10 January 2018)
a.
Motion to accept, second by Bill Burns.
3.
Next meeting: 14 March 2018
a.
no objections
4.
Review of the agenda.
a.
Larry: Discuss more about Github ( issue 6.5)
5. Review of open action items
a: Larry: See if we can use Jirka's suggested RDFa vocabulary
for license links for the examples Larry identified. CONTINUED. Need more guidance.
b. All: Look for other example (e.g., Flickr) and try out the license link vocabulary.
Dick looked at Flickr (discuss in 6.5)
c. Jirka: Update schema for 5.2 to allow zero or more instances of
type as described in Github issue 91. [http://docbook.org/xml/5.2b03/]
COMPLETED.
d. Bob: Update documentation related to Github issue 93
About mismatch between docs for assembly and spec.
Found another issue, so Bob will review the entire chapter
to make sure the docs match. Still finding problems with examples, so
Bob is testing all the examples. CONTINUED.
e. Bob will handle the Oasis notification and system changes to make Scott the official secretary.
COMPLETED.
f. Issue 97: Missing bibliography in glossary
Misclassified. Should be a stylesheet issue.
COMPLETED: Bob asked submitter to move issue to xslt10-stylesheets on Github.
6.
Status of the DocBook v5.0 Errata document.
b.
ACTION: Bob to follow up with Chet to ensure Errata 01 listed as part of DocBook standard lists.
c.
ACTION: Scott to update TC home page to reflect Errata 01.
d.
ACTION: Bob to update Docbook.org to reflect Errata 01.
e.
ACTION: Scott to send update to social media.
6.5 RDFa vocabulary
Jirka's comments are the last entry in the issue on github at
https://github.com/docbook/docbook/issues/71.
LARRY: You can have single copyright with multiple licenses. Thinking the correct structure would be <legalnotice> with structure elements that reflect the individual license that apply (RDFa). Copyright has
a single holder and range, but multiple licenses could apply. (copyleft, BSD, MIT for examples)
<legalnotice>
<license>
<info>
<copyright>
</info>
How can we apply multiple licenses? License is a peer of copyright, not children.
DICK: should license(s) be children of copyright?
LARRY: Not sure that would work because different copyrights might apply to each license? Peer model seems more accurate to reflect the situation.
DICK: They still have to be linked in some way, though?
LARRY: Will follow up with internal contact on the copyright/license relationships as part of his open action item.
Having license and copyright as children of legalnotice should allow for either relationship? Larry to look at whether we still need to extend DocBook or not.
DICK: Flickr example for holder. How to reference a user name on that service? Could RDFa still be used to identify such user aliases?
LARRY: if this is supposed to be machine-readable, we need some way for the machine to determine this relationship. RDFa could address this.
Modifying copyright might not be the best way to go, but Larry will analyze.
7. Discuss subfigures (Github issue 94)
Larry distributed a .zip file that has a RelaxNG schema and an example.
All: Review Larry's materials in more detail (ensuring only subfigures of the same type
can be used inside a formalgroup) [2]
DICK: Able to load and test in eMacs/Trang without issue!
formalgroup naming? Not sure what else we could use for better intuitive use.
Solution is pretty solid.
ACTION: Larry to follow up with user on github issue to confirm usability of solution before we accept it for 5.2
8. Social media presence for DocBook
Purpose: To raise awareness of actions (votes, calls for information, etc.)
Scott has access to @docbook on Twitter
ACTION: Scott to post message about Errata 01 and link to OASIS.
ACTION: Scott to follow up w/Bob on schema availability
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):
6 Add buildtarget element
Add wherever varname is allowed? Scott moves to accept. Dick second.
ACTION: Scott to follow up with Jirka to add element?
49 Support multiple image resolutions (NOTE: resolve by #52. Should we
close?)
ACTION: Scott to follow up with Jirka to close.
54 Add XIncludes to Assembly Schema
ACTION: Bob to follow up with Norm to close.
71 license tag
CONTINUED.
72 The DocBook websites should really be using https
ACTION: Bob to follow up with Norm.
78 Schema website should be updated
ACTION: Bob to follow up OASIS on publish
88 DB 5.0: @name -> title change not published on docbook.org
ACTION: Scott to follow up with Jirka.
93 Diff between doc of resource element and Assembly schema
CONTINUED.
94 Allow subfigures
ACTION: Larry to follow up w/user.
97 Missing bibliography in glossary
Misclassified. Should be a stylesheet issue.
COMPLETED: Bob will ask submitter to reclassify.
How do we move this?
98 recursive glossentry causes XSL exception
Misclassified. Should be a stylesheet issue?
ACTION: Scott to follow up with user.
Links:
[1]
https://www.oasis-open.org/apps/org/workgroup/docbook/email/archives/201801/msg00003.html
[2]
https://www.oasis-open.org/apps/org/workgroup/docbook/email/archives/201801/msg00002.html
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.