← Prev in month ← Prev in thread
Next in thread → Next in month →

DocBook Technical Committee Meeting Agenda: 14 February 2018

From
Scott Hudson
Date
2018-02-12T16:06:00+00:00
ID
Thread
DocBook Technical Committee Meeting Agenda: 14 February 2018
DocBook Technical Committee Meeting Agenda: 14 February 2018

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

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

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



Attendance at teleconferences is restricted to members

(and prospective members) of the committee.

Dial-in information is available at:
  https://lists.oasis-open.org/archives/docbook-tc/201708/msg00001.html



Agenda

1. Roll call



2. Accept the minutes [1] of the previous meeting (10 January 2018)



3. Next meeting: 14 March 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. All: Look for other example (e.g., Flickr) and try

out the license link vocabulary.



c. Jirka: Update schema for 5.2 to allow zero or more instances of

type as described in Github issue 91.



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.



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.

ACTION: Bob will ask submitter to move issue to xslt10-stylesheets on Github.



6. Status of the DocBook v5.0 Errata document.



7. Discuss subfigures (Github issue 94)

Larry distributed a .zip file that has a RelaxNG schema and an example.

ACTION: All: Review Larry's materials in more detail (ensuring only subfigures of the same type

can be used inside a formalgroup) [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



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



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.

ACTION: Bob will ask submitter to reclassify.



98 recursive glossentry causes XSL exception

Misclassified. Should be a stylesheet issue?



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.
← Prev in month ← Prev in thread
Next in thread → Next in month →