RE: DocBook Technical Committee Meeting Agenda: 14 November 2018

I thought I still had an open action item to produce a modified assembly schema with xi:include added.  Looks like it may have disappeared from being continued for so long.

 

However, attached please find a ZIP with:

assemblyxi.rng

assembly-with-xinclude.xml

resource-block.xml

stock-blocks.xml

File 1 is an attempt at adding xi:include to the assembly.  I started by doing a diff against docbookxi.rng, since a lot of DocBook is included in the assembly schema, and then added xi:include
 elements as alternate content elements for the assembly components (or so I hope).  

 

File 2 is a sample, trying to exercise some of the include process.  Files 3 and 4 provide xinclude referenced content that allowed me to get a grasp of whether the inclusion was working as intended.

 

Not sure how complete the implementation is, but it seems to do at least a good deal of what was intended.  A more thorough sample project will need to be undertaken (and perhaps draft the requester
 to see if it does what was requested).  Hoping others can look at this and see if it needs fixing.

 

Regards,

Larry Rowland

 

From:  [mailto:]
On Behalf Of Scott Hudson

Sent: Wednesday, November 14, 2018 7:26 AM

To: 

Cc: Jirka Kosek <>

Subject: [docbook-tc] DocBook Technical Committee Meeting Agenda: 14 November 2018

Importance: High

 

Apologies for the last minute notice. This month snuck up on me!

 

Best regards,

 

--Scott

 

 

DocBook Technical Committee Meeting Minutes: 14 November 2018

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

The DocBook Technical Committee will meet on Wednesday, 14 November 2018

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

1.         Roll call

2.        Accept
 the minutes [1] of the previous meeting (24 October 2018) 

3. Next meeting: 12 December 2018

4. Review of the agenda. 

5. Review of open action items

a.   Larry to create a candidate for the necessary schema changes to add XInclude support for Assemblies for DocBook 5.2.

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

c. 
Bob to fill out request form with OASIS and a formal ballot should be created by OASIS. COMPLETED.

d.
Bob to follow up on the synopsis RFEs to request more clarification.

 

6. DocBook v5.0.1 approved as a Committee Specification [2]. Announcements sent via Twitter, Linked In.

 

7. Other business

 

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

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

  

99 Add <endorsement> to <info>

Consider for Publishers.

 

100 DocBook 5.1 catalog.xml uses incorrect version

 

103 XML DTD of DocBook 5.1

 

107 namespacesynopsis - should use generic <info> rather than introduce <namespacesynopsisinfo>.

108 enumsynopsis

109 typedefsynopsis

110 macrosynopsis

 

NEW:

none.

  

Links:

[1] https://www.oasis-open.org/apps/org/workgroup/docbook/email/archives/201810/msg00010.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.

Attachment:
xinclude-assembly.zip

Description: xinclude-assembly.zip