Next in thread → Next in month →

DocBook Technical Committee Meeting Agenda: 24 October 2018

From
Scott Hudson
Date
2018-10-22T23:08:00+00:00
ID
Thread
DocBook Technical Committee Meeting Agenda: 24 October 2018
DocBook Technical Committee Meeting Agenda: 24 October 2018

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

The DocBook Technical Committee meets on Wednesday, 24 October 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

2. Accept the minutes [1] of the previous meeting (12 September 2018)

3. Next meeting:
  14 November
2018

  4. Review of the agenda.

  5. Review of open action items

  a.   Bob to follow up with Jirka to determine why the namespace was lost (issue 88).

b.

Bob
  to fix the catalog as part of the 5.1 Errata 01.

  c.

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

  d.

Bob
  to create a sample of structure as a resource and test stylesheet mods to see if it introduces further issues.

  e.

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

                f.   Bob to follow up with Norm on toolchain issues and documentation.



              g.  Larry to rework with a legalsection, Bob to provide an XSL customization.

h.

Larry to experiment with nesting legalsection and also with attempting legalnotice nested within legalsection.

6. Request a Special Majority Vote to approve v5.0.1 as a Committee Specification.



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



  NEW:

107 namespacesynopsis

108 enumsynopsis

109 typedefsynopsis

110 macrosynopsis



  Links:

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



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