← Prev in month
← Prev in thread
Next in thread →
Next in month →
DocBook Technical Committee Meeting Agenda: 12 December 2018
DocBook Technical Committee Meeting Agenda: 12 December 2018 ============================================================= The DocBook Technical Committee will meet on Wednesday, 12 December 2018 (11am PDT, 12noon MDT, 1pm CDT, 2pm EDT, and 8pm CET) 1. Roll call Regrets: Sabine Ocker 2. Accept the minutes [1] of the previous meeting (14 November 2018) 3. Next meeting: 09 January 2019 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. COMPLETED. XIncludes seem to be working successfully. Sample sent to the mailing list. ACTION: all to test and provide feedback. Add to agenda for next meeting. b. Bob/Jirka to include Assembly proposals in 5.2: i. Jirka provided samples, Bob still needs to test. CONTINUED. 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 d. Bob to follow up on the synopsis RFEs to request more clarification. i. Jirka followed up with requestor, who provided further use case. Bob to follow up. CONTINUED. 6. XInclude support for Assemblies for DocBook 5.2. 7. Legalsection vs section - Norm (via list) suggested adding it to db.nopara.blocks. Possibly by creating a new pattern, maybe âdb.notice.blocksâ. Reluctant to allow section in legalnotice (don't allow block content after a regular section). What about enumeration? Suggest making it behave like simplesect. 8. Social media presence for DocBook Purpose: To raise awareness of actions (votes, calls for information, etc.) Scott to post link to final files (when available); Scott to update OASIS public page with final files. COMPLETED 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.
← Prev in month
← Prev in thread
Next in thread →
Next in month →