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


Help: OASIS Mailing Lists Help | MarkMail Help

ubl message

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

Subject: Minutes of Pacific UBL TC call 25 April 2018 00:00UTC

Minutes of Pacific UBL TC call 25 April 2018 00:00UTC


  Todd Albers
  Kenneth Bengtsson
  G. Ken Holman (convener)
  Levine Naidoo


     - 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/cs01-UBL-2.2/ (standardization pending)
     - the ISO/IEC catalogue entry for UBL 2.1 is found at:
     - the ISO/IEC document and attachments for UBL 2.1 are found at:


    Additions to events calendar: http://ubl.xml.org/events
     - see below regarding face-to-face

    Review of Pacific call minutes

    Review of Atlantic call minutes

    Membership status review

     - 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
     - current UBL TC voting member list (alphabetical) and relationships:
       - Todd Albers
         - Member ASC X9 AB, Member ISO 20022 Payment SEG, Member W3C Web
           Payments Interest Group, Business Payments Coalition
       - Oriol Bausà Peris
         - Member OASIS BDXR, Member OASIS ebXML, Editor TC434 Validation
       - Kenneth Bengtsson
         - Chair OASIS BDXR, Observer OASIS ebXML, DK Expert UN/CEFACT
       - Erlend Klakegg Bergheim
         - Member OASIS BDXR, Member OASIS ebXML Core & MS
         - Member CEN/TC434/WS8
       - Peter Borresen
         - DK Member CEN/TC440, Assistant Convenor CEN/TC440/WG7
       - 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
       - Levine Naidoo
         - Member OASIS BDXR, Observer OASIS ebXML, Member Fintech Australia
       - Matt Vickers, Xero
         - Member OASIS BDXR, Member US Business Payments Coalition
     - members approaching gaining voting status after this meeting:
       - Cécile Guasch
     - members approaching losing voting status after this meeting:
       - Ole Madsen
     - active non-voting members
       - Cécile Guasch
         - Member CEN/TC440, Convenor CEN/TC440/WG1, Convenor CEN/TC440/WG2,
           European Commission liaison (DIGIT Interoperability Unit)
       - Enric Staromiejski Torregrosa
         - Member OASIS ebXML, European Commission liaison (DG GROWTH)
       - Roberto Cisternino
         - IT Expert UN/CEFACT
       - Audun Vennesland
     - new member orientation information:

UBL 2.2
  - Ole managing requirements for pre-award documents
  - Kees managing requirements for post-award documents
  - Peter managing requirements for transportation documents
  - Roberto managing requirements for party information documents

  - UBL 2.2 Committee Specification 01 is published:


  - UBL 2.2 Candidate OASIS Specification 01 is published:


  - countdown to standardization outlined in our UBL Governance document:


    - 60-day public review of COS01 over by the end of June
    - 14-day OASIS member call for consent at beginning of July
    - late July UBL 2.2 becomes an OASIS Standard
    - mid-August we will begin the ISO revision process for ISO/IEC 19845
    - we are already 8 months from our original objective of end of 2017
    - do we need to review our governance and our timing for releases?

UBL 2.3
  - a posting has been made to the mail archives so that it can be cited
    in other correspondence:


  - Ole managing requirements for pre-award documents
  - Kees managing requirements for post-award documents
  - Peter managing requirements for transportation documents
  - Kenneth and Todd managing requirements for payments and finance documents
  - Roberto managing requirements for party information documents
  - all subcommittee and task group leaders are asked to take on the
    assignment of JIRA tickets from the current list of "Later" tickets,
    and open each one:
    - use the button "Reject Resolution" in order to re-open the ticket, and
      then "Assign to me" to take on the ticket
    - there should be none left for Ken when this task is done
  - we should further consider the idea raised earlier of splitting UBL into
    different normative parts
    - could split based on deliverables (objects, XML, JSON)
    - could split based on domains (procurement, transportation)
  - reminder about the calendar for UBL 2.3:
    - working drafts at the end of 2018
    - final OASIS Standard at the end of 2019
    - final ISO Standard at the end of 2020
  - new requirements identified in Europe:
    - pre-award catalogue
    - contract information

UBL Payments and Finance Subcommittee
  - upcoming face-to-face during the Exchange Summit Americas conference
    http://www.exchange-summit.com/exa/miami May 8-9, 2017 in Miami, Florida
  - consider hosting a public information session during the conference
  - work on hold until around April
  - what is needed in order to accommodate cryptocurrencies for payments?
    - possibly either payment means or payment channel

Outreach and communications
  - work progressing on analyzing current communication channels

UBL Transportation Subcommittee
  - new document types discussed at the face-to-face
  - teleconferences are being scheduled ... please join the subcommittee to
    subscribe to the subcommittee email list

UBL Small Business Subcommittee
  - this subcommittee was formed 13 years ago and suspended 10 years ago:


  - proposal by Matt to restart the committee:


    - some online comments received:


Git repository
  - the repository has been created:  https://github.com/oasis-tcs/ubl/
  - for now Ken is the only "Maintainer", but there can be any number
  - committee members can pull and be contributors, open and comment on issues
  - non-committee members can open issues and comment on issues
  - guidelines for use:

OASIS Business Document Naming and Design Rules
  - Ken to prototype proposed augmented extension mechanism first discussed
    at the Fremantle face-to-face:
    - add an extension point at the beginning of *every* ABIE, not just the
      document ABIEs
    - ticket created to track online discussion:
  - working extensible UBL 2.1 schemas link posted to the ticket
    - Martin notified and he is contacting his industry colleagues who need it
  - 2018-02-22 discussion preserved for more discussion:
    - concerns based on real-world implementations of UBL where, without prior
      experience, and who do not have a data model that matches UBL, then UBL
      is very complex
    - what has been seen are very grave examples of claiming conformance but
      just throwing it into an extension rather than using the appropriate
      data element from UBL because it is easy to do so
    - maybe even up to 70% of the document shows up in the extension rather
      than in standard business objects
    - adding more extension points makes it more attractive to put one's data
into extensions for one of many reasons other than conformance (laziness,
      time-lines, understanding, etc.)
    - perhaps better documentation would make conformance better
    - the argument for is that there may be more uptake of UBL if
      implementers are able to more easily add what they need where they
      need it
    - one cannot prevent bad use of UBL but would more extension points
      promote more bad use?
    - proposed approach is intended to contextualize extensions where they
      belong rather than grouping them all up-front and having to determine
      where they apply
  - first comments received (on the ticket) regarding extensible ABIEs:


 - JSON rules in the OASIS Business Document Naming and Design Rules
  - active tickets:  https://issues.oasis-open.org/issues/?filter=13472
  - the TC continues to invite public comment on the latest versions of
    these specifications until such time as we agree to progress the documents
    to their next steps in the process:


  - awaiting TC Administration feedback regarding:


    - as this is a facet of the public perception of an OASIS specification,
      the OASIS TC Administration not only needs to be involved, but they are
      the ones to do the heavy lifting with IANA with an amalgam of our
      needs and their needs, so we have to work with them and through them
      - ticket created for tracking:


  - comment posted for review from Tradeshift
    - https://lists.oasis-open.org/archives/ubl-comment/201709/msg00000.html
  - comment posted for review from Australia (though it is an indirect link
    and not properly posted for commenting), and it appears to be observations
    and not a specific comment for action
    - https://lists.oasis-open.org/archives/ubl-comment/201709/msg00001.html
  - Ken has begun work on the changes but is stalled looking for a JSON
    schema processor for Draft-7 of the json-schema specification

JIRA tickets
  - available filters:
       - UBL 2.x - https://issues.oasis-open.org/issues/?filter=12972
       - BDNDR   - https://issues.oasis-open.org/issues/?filter=13472
       - All UBL - https://issues.oasis-open.org/issues/?filter=11670
       - TCAdmin - https://issues.oasis-open.org/issues/?filter=13070

   - when creating tickets, remember to distinguish the following components
     by how they are described to be used as categories:
     - if you leave the "Component/s" field empty, the ticket will not show up
       in the summary filter

   - status and resolution values:
     - NEW - the issue has been created but not yet agreed to be in
             consideration or not for the development distribution
           - in order for the issue to become active work for the committee
             the new ticket must be changed to OPEN or it will not be seen
             in the "to do" filter
           - the other option on a new ticket is to change it to DEFERRED
           - please remember to look at the open filter to ensure visibility:
     - OPEN - the issue is in consideration for the development distribution
            - keep the issue OPEN when assigning to Ken for incorporation
            - please remember to add a comment regarding expectations whenever
              you assign an OPEN ticket to another person for any action
     - RESOLVED + Applied - the issue is incorporated in test but not released
     - RESOLVED + Fixed - the issue is incorporated in a working draft version
     - RESOLVED + Later - the issue is still up for discussion for a future
                          minor revision but not the current development
     - RESOLVED + No Action - considered as no action for any distribution
     - RESOLVED + Cannot Reproduce - considered as no action for distribution
     - APPLIED + Fixed - the issue is included in a public review (record the
                         availability of the disposition once review opened)
     - DEFERRED - the issue is not in consideration for any minor revision
                - please remember to use this when creating new tickets for
                  backwards-incompatible changes
    - see also the discussion on the status workflows here:

   - members please note to discuss ticket issues as comments to the ticket so
     that we can audit the discussion when making decisions about the ticket,
     without having to find the discussion on the main mail list

   - to find all of the OASIS TC Administration tickets related to UBL, use
     the https://issues.oasis-open.org/issues/?filter=13070 filter


   - we have a formal offer to host a face-to-face meeting in Zwolle, NL
     during the week of October 1, 2018 with multiple meeting rooms for
- suggested we start the afternoon of October 1 and end at noon on October 5
     - the Exchange Summit conference is in Berlin during the following week
   - we will make a preliminary decision in four weeks so that people can
     start thinking about travel arrangements if we are agreed


2018-04-25 UBL Atlantic - 09:00MSP/09:00Lima/10:00Ottawa/14:00UTC/16:00Europe
  2018-05-09 No UBL Meetings
2018-05-23 UBL Pacific - 19:00MSP/19:00Lima/20:00Ottawa/00:00UTC/10:00Sydney 2018-05-23 UBL Atlantic - 09:00MSP/09:00Lima/10:00Ottawa/14:00UTC/16:00Europe 2018-06-06 UBL Pacific - 19:00MSP/19:00Lima/20:00Ottawa/00:00UTC/10:00Sydney 2018-06-06 UBL Atlantic - 09:00MSP/09:00Lima/10:00Ottawa/14:00UTC/16:00Europe 2018-06-20 UBL Pacific - 19:00MSP/19:00Lima/20:00Ottawa/00:00UTC/10:00Sydney 2018-06-20 UBL Atlantic - 09:00MSP/09:00Lima/10:00Ottawa/14:00UTC/16:00Europe 2018-07-04 UBL Pacific - 19:00MSP/19:00Lima/20:00Ottawa/00:00UTC/10:00Sydney 2018-07-04 UBL Atlantic - 09:00MSP/09:00Lima/10:00Ottawa/14:00UTC/16:00Europe 2018-07-18 UBL Pacific - 19:00MSP/19:00Lima/20:00Ottawa/00:00UTC/10:00Sydney 2018-07-18 UBL Atlantic - 09:00MSP/09:00Lima/10:00Ottawa/14:00UTC/16:00Europe

  Notes regarding teleconference times:

   - meeting times stable now until October:


  Will anyone be requesting a leave of absence in the near future?  For
  privacy reasons, this discussion will be kept off of the minutes.

 TC calendar:

 TC calendar iCal subscription link:


 - UBL is going to be the subject of a case study in an upcoming workshop
   written by Kenneth and Ken to be delivered in Miami on May 7, the day
   before the Exchange Summit conference:


Contact info, blog, articles, etc. http://www.CraneSoftwrights.com/o/ |
Check our site for free XML, XSLT, XSL-FO and UBL developer resources |
Streaming hands-on XSLT/XPath 2 training class @ US$45 (5 hours free) |

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