OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-tc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: DocBook Technical Committee Meeting Agenda: 12 September 2018

Hello, Scott (and everyone else),


Attached please find a ZIP file with an XML sample document and an HTML rendering of it (done from within oXygen, and the PDF rendering was atrocious).


This is in fulfillment of 5.f. 


The sample document is an article with two sections in it, one for an End User License Agreement and the other for an Additional License Authorizations document.  They represent samples of the two types of license documents we have to produce in this environment.  There are two sections because I needed two info elements with some separation between them to hold the legalnotice elements.  I looked over the two types of documents we produce at HPE (links to each of them in the document) and tried to create samples of each type of information that was included in the samples in my experimental document.  I did not make any attempt at tuning the render (probably don't really want things like âthe section called  âEnd User License Agreementâ instead of just the name of the section).  However, I tried to make a reasonable representation of the documents in question using the 5.1 legalnotice structure.


My conclusions are in the XML document, but the short form is that for EULAs it looks like a reasonable fit, but for the ALA it seems like a real stretch to do it without the idea of sections (or legalsections) inside the legalnotice.  It is doable but I really dislike how it was done (see the notes in the documents).  There also seem to be some fairly far out things like funcsynopsis that Iâm not entirely sure I understand why they would show up in a legalnotice, but I had to use a screen to get a fixed-width, preformatted presentation, so I guess the broad range of markup is useful.


Started working on the assembly schema with xi:xinclude in it for 5.e but have been struggling a little with how xi:include works in DocBook itself.  I also noticed that Bob had something related to it in 5.g â sorry I didnât complete this sooner but it is a heavier lift than I anticipated.  I may have to spring for a copy of oXygen to use at home so that I donât have to stay so late to do things at work â wish there was a hobbyist version.



Larry Rowland




From: docbook-tc@lists.oasis-open.org [mailto:docbook-tc@lists.oasis-open.org] On Behalf Of Scott Hudson
Sent: Monday, September 10, 2018 10:11 AM
To: docbook-tc@lists.oasis-open.org
Subject: [docbook-tc] DocBook Technical Committee Meeting Agenda: 12 September 2018


DocBook Technical Committee Meeting Agenda: 12 September 2018


The DocBook Technical Committee meets on Wednesday, 12 September 2018

(11am PDT, 12noon MDT, 1pm CDT, 2pm EDT, and 8pm CEST)


Meeting password: Please obtain your meeting password from Scott Hudson.

Dial-in number (US): (605) 475-4729
International dial-in numbers: https://fccdl.in/i/bobs00
Online meeting ID: bobs00
Join the online meeting: https://join.freeconferencecall.com/bobs00

For 24/7 Customer Care, call (844) 844-1322


1.      Roll call

a.      Regrets: Sabine Ocker

2. Accept the minutes [1] of the previous meeting (13 June 2018) 

3. Next meeting: 10 October 2018

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). COMPLETED.
Implemented changes are:

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.

f.       Larry to create an alternative structure using legalnotice as a block, and see if legalsection is needed, or if the existing block elements would suffice.

g.      Bob to create a sample of add XInclude to assembly (enables structure as a resource) and test stylesheet mods to see if it introduces further issues.

h.     Scott to announce availability of 5.0.1 as ready for review COMPLETED.

i.       Scott to follow up with Norm to generate the 5.1 DTD and document the process for generating it. COMPLETED.
"Several years ago, after a lot of effort, I concluded that it wasnât possible. I began working on the XSD version of DocBook by hand because I thought I could generate a DTD from that. I expect thatâs still the most practical way forward. Be seeing you, norm"

j.       Bob/Jirka to include Assembly proposals in 5.2: CONTINUED.

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

k.      Committee draft specification for 5.0.1 approved by members via email vote on 09 JUL 2018. (COMPLETED)

                                          i.     The DocBook Schema Version 5.0.1
Committee Specification Draft 01
09 July 2018

Relax NG schemas: http://docs.oasis-open.org/docbook/docbook/v5.0.1/csd01/schemas/rng/
Schematron schema: http://docs.oasis-open.org/docbook/docbook/v5.0.1/csd01/schemas/sch/
DTD schema: http://docs.oasis-open.org/docbook/docbook/v5.0.1/csd01/schemas/dtd/
XML schemas: http://docs.oasis-open.org/docbook/docbook/v5.0.1/csd01/schemas/xsd/

8. Social media presence for DocBook

Purpose: To raise awareness of actions (votes, calls for information, etc.)


9. Review of Requests for Enhancement

To find a Github issue by number, enter the URL (on one line):



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)


103 XML DTD of DocBook 5.1





[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,




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 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.




Attachment: legalnotice-experiments.zip
Description: legalnotice-experiments.zip

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]