Hello, All,
I have not had time to cover item f.
With respect to item e, I have attached a zip of the last assembly sample I generated quite some time ago.
Took a while to dig this out and make sure I understood what was being discussed when this file was generated; the file is pretty old and probably does not reflect the final syntax we settled
on, but maybe it will help understand what was intended for the output transforms.
If you look at lines 310 to 320 a module is defined that is intended to produce a tutorial. The tutorial is designed to be presented by a tutorial engine that provides the framework for a tutorial,
including things like next/previous navigation, percent completed, Q&A proof of content mastery and other characteristics of a tutorial. There are two output elements: the first one specifies the name of the tutorial file (so that the tutorial engine can
pick it up correctly) and the transform to be used to render (the transform attribute matches the name attribute on the transform in line 445); the second one says to render it as a chapter in the PDF that is produced of the help system (something that was
provided as a convenience for customers).
This is in contrast to the DITA content specified in lines 166-170, where the grammar attribute on the resource element matches the grammar attribute on the transform element in line 445 that
is intended to normalize the DITA content to DocBook.
There are a number of notes in the comment section that address how the overall file is to be treated.
I hope this will set up the background to continue the discussion started at the last meeting.
Regards,
Larry Rowland
From: docbook-tc@lists.oasis-open.org [mailto:docbook-tc@lists.oasis-open.org]
On Behalf Of Scott Hudson
Sent: Tuesday, May 08, 2018 7:30 AM
To: docbook-tc@lists.oasis-open.org
Subject: [docbook-tc] DocBook Technical Committee Meeting Agenda: 9 May 2018
DocBook Technical Committee Meeting Agenda: 9 May 2018
=============================================================
The DocBook Technical Committee will meet on Wednesday, 9 May 2018
(11am PDT, 12noon MDT, 1pm CDT, 2pm EDT, and 8pm CEST)
1. Roll call
2. Accept the minutes [1] of the previous meeting (11 April 2018)
3. Next meeting: 13 June 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).
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 repost examples of <transform> usage in assemblies.
f. Larry to create a candidate for the necessary schema changes to add XInclude support for Assemblies for DocBook 5.2.
6. Issue 71: Parts can be done using RDFa, but some require structural changes. Jirka pointed out an issue that there is no definitive RDFa vocabulary, which will make portability
more difficult. This will need to be addressed. There is no obvious solution to only use RDFa.
7. Issue 88: Fix namespaces and catalog for 5.1 errata.
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):
6 Add buildtarget element (added to v5.2b05 by Jirka)
49 Support multiple image resolutions (implemented in 5.2b02 by Jirka)
54 Add XIncludes to Assembly Schema (accepted)
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
NEW:
102
Add "interface" value to systemitem class
Links:
[1] https://lists.oasis-open.org/archives/docbook-tc/201804/msg00007.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.