With regard to 5.d, I posted a summary of the suggested solution:
Sorry it has taken so long to get back to you on this.
After discussing this issue and realizing that there are similar requirements for examples and other formal elements, the TC is
proposing adding a formalgroup element that would allow a set of children, all of the same type of formal element without introducing additional
complexity in the schema for the formal elements to handle not permitting content at one level but permitting it at another level. It also makes the intention of the structure clearer. This would allow for something like:
<formalgroup>
<title>More Still</title>
<figure>
<title>Glamourous</title>
<mediaobject>
<textobject>
<para>High</para>
</textobject>
</mediaobject>
</figure>
<figure>
<title>Fast</title>
<para>Hello</para>
</figure>
</formalgroup>
And also permit:
<formalgroup align="center" columns="2" type="horiz">
<title>Testing Formal Group</title>
<equation>
<title>Addition</title>
<mathphrase>5 + 2</mathphrase>
</equation>
<equation>
<title>Subtraction</title>
<mathphrase>5 -2</mathphrase>
</equation>
</formalgroup>
and other similar constructs for other formal elements. A type attribute similar to that used for simple lists would allow specifying
horizontal or vertical and would combine with a column attribute to provide simple control of the representation with an align attribute to control simple alignment of the group on the page. It would also be possible to specify a
floatstyle attribute to reference more complex CSS-bindings for the rendered elements.
To which he responded:
That would be so much better than my proposal!
Still working on 5.a.
Regards,
Larry Rowland
From: docbook-tc@lists.oasis-open.org [mailto:docbook-tc@lists.oasis-open.org]
On Behalf Of Scott Hudson
Sent: Tuesday, April 10, 2018 9:48 AM
To: docbook-tc@lists.oasis-open.org
Subject: [docbook-tc] DocBook Technical Committee Meeting Agenda: 11 April 2018
DocBook Technical Committee Meeting Agenda: 11 April 2018
=============================================================
The DocBook Technical Committee will meet on Wednesday, 11 April 2018
(11am PDT, 12noon MDT, 1pm CDT, 2pm EDT, and 8pm CEST)
1. Roll call
2. Accept the minutes [1] of the previous meeting (14 March 2018)
3. Next meeting: 9 May 2018
4. Review of the agenda.
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.
b. Bob to follow up with Chet regarding Errata 01 approval. CONTINUED.
c. Bob to update Docbook.org to reflect Errata 01. Will revise link once approved.
d. Larry to follow up with user on github issue to confirm usability of Subfigures solution before we accept it for 5.2 (Github issue 94) CONTINUED.
e. Jirka will prepare a new release.
f. Bob to follow up with Jirka to close Github issue 54.
g. Bob to follow up with OASIS to publish Github issue 78. CONTINUED.
h. Jirka to fix Github issue 88 in place.
i. Bob to fix the catalog as part of the 5.0 Errata 01
j. Dick to follow up on issue 99 Add <endorsement> to <info>
k. Bob to follow up on issue 97 Missing bibliography in glossary
7. Social media presence for DocBook
Purpose: To raise awareness of actions (votes, calls for information, etc.)
Scott posted announcement of 5.0 Errata 01 approval.
8. 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
49 Support multimple image resolutions (NOTE: resolve by #52. Should we
close?)
54 Add XIncludes to Assembly Schema
71 license tag
72 The DocBook websites should really be using https
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
97 Missing bibliography in glossary
Misclassified. Should be a stylesheet issue.
98 recursive glossentry causes XSL exception
Misclassified. Should be a stylesheet issue?
99 Add <endorsement> to <info>
NEW:
100 DocBook 5.1 catalog.xml uses incorrect version
Links:
[1] https://www.oasis-open.org/apps/org/workgroup/docbook/email/archives/201802/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.