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 TC Meeting Agenda -- March 15, 2017

DocBook Technical Committee Meeting Agenda: 15 March 2017

The DocBook Technical Committee will meet on Wednesday,
15 March 2017 at 2:00pm ET

Attendance at teleconferences is restricted to members
(and prospective members) of the committee.

This is the phone number for Wednesday's DocBook TC call:

Phone: +1-719-387-5556
Code: 902213


1. Roll call

2. Accept the minutes [1] of the previous meeting (15 February 2017).

3. Next meeting: 19 April 2017

4. Review of the agenda.
5. Review of open action items

  a:  Jirka: Investigate best method to resolve Github issue 52, after March, 2017.
  b:  Jirka: Re-open Github issue 53 and assign it the label "accepted"
  c:  Larry: Investigate whether we have already implemented Github 54
       Follow up from February's meeting:  Larry volunteered to generate
       some sample cases to show where XInclude would be useful.
  d:  Dick: For Github issue 71, investigate to see how we might add a license
       link to legalnotice using class, info, or other existing markup.
       Follow up: Dick reached out to the person who originated this issue for more information. So far,
       no response.
  e:  Larry: Come up with a list of alternatives to the proposed buildtarget element using current elements.
  e:  Bob: Talk with Norm to clarify Github issue 72 and determine which
       sites need https and which already have it.
       See item 7 below.

  f: TBD: Update docbook.org to include official 5.1 and point to OASIS for official releases on docbook.org.
      See item 7 below.
  g: Bob: Update the OASIS front page for 5.1.

6. Add buildtarget element (continue discussion on Github issue 6). Notes from last month:
        Suggestions include:
           - Use existing tag, systemitem, or function elements.
           - Use a broader element, e.g., target
           - Create a new buildtarget element
           - Another element name that allows for branching.
           - Are we trying to explain a build language?
           Concern about whether we lose clarity if we go broader.
        Larry volunteered to come up with a list of alternatives to discuss this month.

7.  HTTPS for docbook.org: Norm suggested that we should use https for docbook.org, at least for downloads.
     Discuss whether we should do this and, if so, how we should do this. Connected with this, we should
     discuss ongoing maintenance for docbook.org.
8.  Review of Requests for Enhancement

  To find a Github issue by number, enter the URL (on one line):

  6     Add buildtarget element
  7     Allow revnumber inline.
  52   Allow multimediaparam in imagedata
         See action a: above.
  53   Extend article @class with other and otherclass [ closed on 9/18/2016 ]
         See action b: above.
  54   Add XIncludes to Assembly Schema
         See action c: above.
  71   license tag (migrated from sourceforge)
         See action d: above.
  72   The DocBook websites should really be using https
         See action e: above.
  76   Allow nesting of <option/> in <command/> in DB 5
  78   Schema website should be updated
[1] https://lists.oasis-open.org/archives/docbook-tc/201702/msg00003.html

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