Re: [docbook-tc] DocBook TC meeting, Wednesday April 19, 2017

[Scott Hudson <scott.hudson@jeppesen.com>]

I can set up a quick webex, if that will help?

--Scott

On 4/19/17, 12:05 PM, "docbook-tc@lists.oasis-open.org on behalf of Scott Hudson" <docbook-tc@lists.oasis-open.org on behalf of scott.hudson@jeppesen.com> wrote:

    I’m getting an invalid code error for the dial in?
    
    --Scott
    
    On 4/17/17, 7:30 PM, "docbook-tc@lists.oasis-open.org on behalf of Richard Hamilton" <docbook-tc@lists.oasis-open.org on behalf of hamilton@xmlpress.net> wrote:
    
        Here is the agenda for this month’s meeting, which will be held this Wednesday, April 19, 2017 at 2:00pm  EDT.
        
        Everyone please check your action items, and if you have status, please send me a note before the meeting.
        
        Best regards,
        Dick
        ===================
        DocBook Technical Committee Meeting Agenda: 19 April 2017
        =============================================================
        
        The DocBook Technical Committee will meet on Wednesday,
        19 April 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
        
        Agenda
        
        1. Roll call
        
        2. Accept the minutes [1][2] of the previous two meetings (15 February and 15 March 2017).
        
        3. Next meeting: 17 May 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.
               
          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.
              COMPLETE
        
        6. Thank Jirka for his service on the TC and discuss his future work on DocBook.
        
        7. 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.
        
        8.  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.
             
        9.  Review of Requests for Enhancement
        
          To find a Github issue by number, enter the URL (on one line):
          https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_docbook_docbook_issues_NUMBER&d=DwIFaQ&c=P3aKjizb3qsxp0SERaL2sw&r=YQWdLfM9mekBOdoMmoBdn9RgyqIHrveGolBbb4_uGWQ&m=wkle8_Rdn3TPFpTU1x9Dxc7L4r676dNtuT0KSJZeL-s&s=qKe_fVfCSWMncCr3merz6uupGZ55uKCJ4eyMHowm0NU&e= 
        
          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.
          NEW
          76   Allow nesting of <option/> in <command/> in DB 5
          78   Schema website should be updated
          82   Add admonitions to Publishers
          83   include mechanisms for table accessibility
          84   Epigraphs should allow poetry in Publishers schema
          85   Replacement for "annotation" element in Publishers schema
          86   linegroup and blockquote elements
          88   DB 5.0: @name -> title change not published on docbook.org
        
          
        [1] https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.oasis-2Dopen.org_archives_docbook-2Dtc_201702_msg00003.html&d=DwIFaQ&c=P3aKjizb3qsxp0SERaL2sw&r=YQWdLfM9mekBOdoMmoBdn9RgyqIHrveGolBbb4_uGWQ&m=wkle8_Rdn3TPFpTU1x9Dxc7L4r676dNtuT0KSJZeL-s&s=y5Yx_xsJLBh3EcLaTQfXGMblmSuCStQrLkNKHjE1LPk&e= 
        [2] https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.oasis-2Dopen.org_archives_docbook-2Dtc_201703_msg00002.html&d=DwIFaQ&c=P3aKjizb3qsxp0SERaL2sw&r=YQWdLfM9mekBOdoMmoBdn9RgyqIHrveGolBbb4_uGWQ&m=wkle8_Rdn3TPFpTU1x9Dxc7L4r676dNtuT0KSJZeL-s&s=bZxVU6Dv8msb_nsEsJ6zYgZE9uM4zAAfoJlzHMS3AzA&e= 
        
        
        
        ---------------------------------------------------------------------
        To unsubscribe from this mail list, you must leave the OASIS TC that
        generates this mail.  Follow this link to all your TCs in OASIS at:
        https://urldefense.proofpoint.com/v2/url?u=https-3A__www.oasis-2Dopen.org_apps_org_workgroup_portal_my-5Fworkgroups.php&d=DwIFaQ&c=P3aKjizb3qsxp0SERaL2sw&r=YQWdLfM9mekBOdoMmoBdn9RgyqIHrveGolBbb4_uGWQ&m=wkle8_Rdn3TPFpTU1x9Dxc7L4r676dNtuT0KSJZeL-s&s=QZ4wouzxBGos8SeBesXbsGDIykLlb0NTcjUq4HvwBvE&e=