← Prev in month ← Prev in thread
Next in thread → Next in month →

Minutes of Atlantic UBL TC call 21 September 2016 14:00UTC - voting meeting

From
G. Ken Holman <>
Date
2016-09-21T15:16:40+00:00
ID
Thread
Minutes of Atlantic UBL TC call 21 September 2016 14:00UTC - voting meeting
Minutes of Atlantic UBL TC call 21 September 2016 14:00UTC - voting meeting

ATTENDANCE

Atlantic teleconference:

  Oriol Bausa
  Erlend Klakegg Bergheim
  Kees Duvekot
  G. Ken Holman (convener)
  Ole Madsen

Pacific teleconference attendance:

  G. Ken Holman (convener)
  Tim McGrath


REFERENCING THE SPECIFICATION

    - the following should be used as a specific citation:
      OASIS Universal Business Language (UBL) v2.1 (ISO/IEC 19845:2015)
    - the following would be used for a general (any version) citation:
      OASIS UBL (ISO/IEC 19845)
    - the canonical documents are available in the OASIS repository:
      http://docs.oasis-open.org/ubl/os-UBL-2.1/
    - the ISO/IEC catalogue entry is found at:
      http://www.iso.org/iso/catalogue_detail.htm?csnumber=66370
    - the ISO/IEC document and attachments are found at:
      http://standards.iso.org/ittf/PubliclyAvailableStandards/


STANDING ITEMS

   Additions to events calendar: http://ubl.xml.org/events
    - October 11, 2016 - CEN/TC 434 Public Conference
      Barcelona, Spain (in conjunction with Exchange Summit Conference)
      http://www.exchange-summit.com/registration-cen

   Review of Pacific call minutes
      https://lists.oasis-open.org/archives/ubl/201609/msg00046.html

   Review of Atlantic call minutes
      https://lists.oasis-open.org/archives/ubl/201609/msg00035.html

   Membership status review
    https://www.oasis-open.org/policies-guidelines/tc-process#membership
    https://www.oasis-open.org/committees/membership.php?wg_abbrev=ubl
    https://www.oasis-open.org/apps/org/workgroup/ubl/members/roster.php?num_items=80

   - voting status is determined by the following:
      - existing voting members must not miss two consecutive meetings to
        maintain voting status
      - non-voting members must attend two consecutive meetings to obtain
        voting status
      - members formally on leave by prior request must not attend and
        their voting status is not impacted
    - committee officers (alphabetical):
      - Jon Bosak (secretary)
      - G. Ken Holman (co-chair)
      - Tim McGrath (co-chair)
    - current UBL TC voting member list (alphabetical) and relationships:
      - Oriol Bausà Peris
        - Member OASIS BDXR, Member OASIS ebXML, Editor TC434 Validation
      - Kenneth Bengtsson
        - Chair OASIS BDXR, Member OASIS ebXML
      - Kees Duvekot
        - Member OASIS BDXR
      - G. Ken Holman
        - Member OASIS BDXR, CA Member JTC 1/SC32, CA Expert UN/CEFACT
      - Ole Ellerbæk Madsen
        - DK Member CEN/TC440, CEN/TC440 Liaison JTC 1/SC 32
      - Tim McGrath
        - EESPA Observer CEN/TC434, AU Expert UN/CEFACT
    - active non-voting members
      - Erlend Klakegg Bergheim
        - Member OASIS BDXR, Member OASIS ebXML Core & MS
        - Member CEN/TC434/WS8
      - Roberto Cisternino
      - Audun Vennesland

Recognition of contribution
 - one of the TC's longest-standing members, Andy has informed the chairs that
   he is not renewing his membership and is retiring from the committee work
 - the members of the UBL committee are unanimous in thanking Andy Schoka
   for his outstanding contribution over the years in the success of UBL and
   the work of our technical committee


UBL 2.2
 - the initial suggestion period for UBL 2.2 is now closed
   - the TC is now expecting each of the Transportation, Pre-award and
     Post-award subcommittees to make the recommendations for 2.2 additions
     to be agreed upon by the TC; this is done by way of a JIRA ticket
 - Tim managing requirements for transportation documents
 - Kees managing requirements for post-award documents
 - Ole managing requirements for pre-award documents
 - Roberto managing requirements for party information documents

 - the current UBL 2.2 csd01wd08 spreadsheet is found here:
https://docs.google.com/spreadsheets/d/185sbrn5rodJmu612GGI54_N0eQKNvKZhnoIgksM-MWI/edit
   - the csd01wd07 working draft release of UBL 2.2 artefacts is found at:
     https://www.oasis-open.org/committees/document.php?document_id=58873
     https://lists.oasis-open.org/archives/ubl/201609/msg00021.html

 - documentation requirements
   - a Google text document of the hub document is here:
https://docs.google.com/document/d/11Atj1Knidip35iwt_3hWgJlY7OhNhHh5OYCCx53mAYE/edit
    - committee members have been given permissions to edit the document
     - Ken will try to move the content into XML when the edits are complete
     - removing hanging paragraphs by adding introductory sections
     - disambiguating section titles
   - each submitter of new documents and objects must consider what additional
     documentation is needed in the UBL hub document:
     - general business rules - sections 2.2.x
     - business objects - sections 2.x
     - party roles - section 2.20
     - example instances to Ken for inclusion in sections 3.2.x and in the
       xml/ subdirectory

 - please review all JIRA tickets and comment and/or act where necessary:
       https://issues.oasis-open.org/issues/?filter=12972
   - all of the issues are to be closed by September 1, 2016 in order to
     create the first committee specification draft and public review draft
     - we aren't going to make this because of vacation schedules
   - please remember to document your actions on the ticket and then assign
     the ticket to the next person (usually Ken) to deal with the ticket, as
     others won't know what is being done, leaving the ticket status as "OPEN"
     (Ken will change it from OPEN to RESOLVED when the changes have been
      incorporated into internal draft or external released deliverables)
   - when asking a question in the spreadsheet, or challenging a value such
     as a definition, please include a question mark (?) and that can be used
     to search for outstanding issues ... better still would be to simply
     create a JIRA ticket for the issue and leave the definitions untouched
     until they are addressed
← Prev in month ← Prev in thread
Next in thread → Next in month →