OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-tc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: DocBook Technical Committee Meeting Minutes: 13 June 2018


DocBook Technical Committee Meeting Minutes: 13 June 2018

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

The DocBook Technical Committee meets on Wednesday, 13 June 2018

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

 

Meeting number (access code): 890 083 874

Meeting password: Please obtain your meeting password from Scott Hudson.

 

Join by phone

1-888-787-5387 U.S Toll Free-high cost

+1-425-943-7320 U.S. NW

Czech Republic Prague   (420) 239-018-563

Czech Republic TollFree 800-050349

 

1. Roll call

2. Accept the minutes [1] of the previous meeting (9 May 2018) 

Accepted.

3. Next meeting: 08 August 2018

                a. Regrets: Scott, Bob for 11 July 2018

4. Review of the agenda. 

Add 6.5 for legalnotice

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. CONTINUED.

  b. Jirka will prepare a new release to incorporate <formalgroup> (5.2) CONTINUED.

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

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

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

f.  Larry to re-post legalnotice examples to help with the classification. (As agreed in last mtg to make legalnotice a block structure to help the current issues and add a class attribute or attribute value to article, appendix, section, etc) COMPLETED.

 g. Bob/Jirka to include Assembly proposals in 5.2: 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

h. Bob to create draft specification for 5.0.1 (COMPLETED)

 

6. Committee Draft for 5.0.1 [2]

            Draft completed. Bob showed the Schematron changes to George Bina at SyncroSoft, and the changes look OK.

No additional comments. Larry makes a motion to accept the Committee Draft. Dick seconds. Unanimous approval. Bob to follow up with OASIS for the next step in the Committee Draft process.

 

6.5: Discussion of legalnotice / license

Larry provided an example of a license, which includes sections and other block-level content. Legalnotice will need to be modified to allow these types of block-level and section elements.

 

We need to look at the implications of allowing sections. Legalnotice is essentially being promoted to a section-like thing, though it is allowed to occur in additional locations, such as info.

 

With nested sections, you can’t add paragraphs in between the levels.

 

Bob: what about creating a special “legalsection” element to have special containment rules?

Larry: what would make it different from the existing section constraints?

Dick: What about creating a higher level “legalnotices” wrapper that can contain multiple “legalnotice” elements, which would allow section.

Larry: If we created a <section class=”legalnotice”>, would the numbering scheme be affected? It does seem that it is a variation of section.

Bob: The processing stylesheets would really need to know the context. The concern is more about sections that are a descendant of legalnotice. This is why a different element is needed (since it could have different contexts and processing).

Larry: Like the idea of “legalsection”, but would need to allow the nestings, etc.

Dick: What if legalnotice was promoted to the same level as a chapter or preface or appendix?

Larry: Then it would contain the sections as normal.

Scott: Since this started around license, should that be the element name?

Dick: content model should be similar to chapter or preface.

Bob: you still may want legalnotice at other levels though?

Larry: if legalnotice is allowed in many places, we may run into processing issues due to their complexity. More structure will be needed, but maybe not as much as section requires?

Bob: a block structure is something that could be contained within a section (para, etc).

ACTION: Larry to create an alternative structure using legalnotice as a block, and see if legalsection is needed, or if the existing block elements would suffice.

 

7. Structure as a resource. Should a resourceref be allowed to point to a structure id?

                The idea being that a structure could be defined as a resource that could be used in another part of the structure. (refer to previously sent assembly example).

 

Bob: Structure itself contains modules. You could have a module or structure refer to an id of another structure.

Think of it as an XInclude process for structure.

The processing would have to then follow the other structure to build the appropriate list of resources.

I can see how this would be useful.

Larry: Adding XInclude to assembly will help to address this very type of issue. If I can define the reuse, rather than copy/paste, this is what the mechanism is intended to support.

Scott: as long as it doesn’t severly impact the processing, I could see this being very useful!

ACTION: Bob to create a sample and test stylesheet mods to see if it introduces further issues.

  

8. Social media presence for DocBook

Purpose: To raise awareness of actions (votes, calls for information, etc.)

Announce availability of 5.0.1 for review? YES. As soon as it is ready for review.

  

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

 

94 Allow subfigures (accepted)

  

99 Add <endorsement> to <info>

 

100 DocBook 5.1 catalog.xml uses incorrect version

 

102 Add "interface" value to systemitem class (accepted)

 

NEW:

103 XML DTD of DocBook 5.1

ACTION: Scott to follow up with Norm to generate the 5.1 DTD and document the process for generating it.

Larry: supposedly there is an open toolkit to convert RNG to DTD. (DITA)

 

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

 

/var/folders/vn/40l0twkn2nvd8h0p58s4m069fmh2c3/T/com.microsoft.Outlook/WebArchiveCopyPasteTempFiles/cidimage001.png@01D3E796.35B0DB90

 

This document contains only administrative, uncontrolled data under U.S. International Traffic in Arms Regulations.

 

 

 

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

 

/Users/scott.hudson/Library/Containers/com.microsoft.Outlook/Data/Library/Caches/Signatures/signature_1955532617

 

This document contains only administrative, uncontrolled data under U.S. International Traffic in Arms Regulations.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]