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

Minutes of Atlantic UBL TC call 17 May 2017 14:00UTC

From
G. Ken Holman <>
Date
2017-05-17T16:26:38+00:00
ID
Thread
Minutes of Atlantic UBL TC call 17 May 2017 14:00UTC
Minutes of Atlantic UBL TC call 17 May 2017 14:00UTC

ATTENDANCE

  Todd Albers
  Kenneth Bengtsson
  Erlend Klakegg Bergheim
  G. Ken Holman (convener)
  Ole Madsen

  Observer:
   Troels Nørgaard Nielsen

  Regrets received in advance:
   Kees Duvekot


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
    - no new events to add at this time

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

   Review of ad-hoc call minutes
      https://lists.oasis-open.org/archives/ubl/201705/msg00008.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
    - 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
      - 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
      - G. Ken Holman (Chair OASIS UBL TC)
        - 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
      - Enric Staromiejski Torregrosa
        - Member OASIS ebXML, European Commission liaison (DG GROWTH)
    - members losing voting status after this meeting:
      - Enric Staromiejski Torregrosa
    - members approaching losing voting status after next meeting:
      - Oriol Bausà Peris
    - active non-voting members
      - Roberto Cisternino
        - IT Expert UN/CEFACT
      - Kees Duvekot
        - Member OASIS BDXR
      - Audun Vennesland
    - new member orientation information:
      https://www.oasis-open.org/committees/document.php?document_id=59647


UBL 2.2
 - someone is needed to manage 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 UBL 2.2 CSPRD01 first 45-day public review has just ended:

   https://lists.oasis-open.org/archives/ubl/201701/msg00019.html

 - draft disposition of public comments has been started:

https://docs.google.com/spreadsheets/d/1GpAMQDtoxSAiRPwX4uhi5huxpCVutbTKpb9zYO3p-QM/view

 - committee members can create new JIRA tickets for UBL 2.2 on their own
   without needing to include them in the summary of public comments
 - the tickets for the next revision can be found using the same link as
   before ... please begin commenting on the tickets with your input:

   https://issues.oasis-open.org/issues/?filter=12972


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

   https://lists.oasis-open.org/archives/ubl/201702/msg00006.html

 - someone is needed to manage 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
 - Kenneth and Todd managing requirements for payments and finance documents
 - Kenneth is preparing an initial set of semantic requirements for the
   bill of exchange (a tradable trade receivable) for consideration


UBL Payments and Finance Subcommittee
 - subcommittee creation agreed upon at ad-hoc meeting 2017-05-05
 - work underway to establish the committee presence

   https://issues.oasis-open.org/browse/TCADMIN-2581

 - Ken noted projects such as http://bbiller.com looking at using UBL with
   the blockchain including the need to make payments using virtual currency
   and that the Australian Standards organization has successfully started
   an ISO committee on blockchain use of ISO20022 as reported in this article:

   http://www.pymnts.com/news/b2b-payments/2016/iso-20022-blockchain-standards-australia-cross-border-payments-smart-contracts/

 - perhaps there are some synergies between what we are doing and what they
   are doing


JSON Task Group
 - 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:

http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.1/Business-Document-NDR-v1.1.html
http://docs.oasis-open.org/ubl/UBL-2.1-JSON/v1.0/UBL-2.1-JSON-v1.0.html

 - implementation endorsement and feedback from Tradeshift (with thanks!)

     https://lists.oasis-open.org/archives/ubl-comment/201705/msg00000.html

     Suggested MIME data types:

     # Universal Business Language XML Canonical Representation
     application/vnd.oasis.ubl+xml
     # Universal Business Language JSON Alternative Representation
     application/vnd.oasis.ubl+json

   - I (Ken) suggest that we take the adjectives out of the descriptions to
     have future flexibility in changing any kind of normative status, which
     doesn't change the actual coded suggestions:

     # Universal Business Language XML Representation
     application/vnd.oasis.ubl+xml
     # Universal Business Language JSON Representation
     application/vnd.oasis.ubl+json

   - 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
     - this isn't a problem as they are interested in helping us with this
     - do we agree to forward this modified Tradeshift suggestion to TC
       Administration for guidance and action?
      - AGREED - unanimous by those present, a majority of voting members

 - implementation feedback from Australian DBC (with thanks!):

     https://lists.oasis-open.org/archives/ubl-comment/201705/msg00004.html

   - JSON task group (Erlend, Kenneth and Ken) to draft up a response for the
     TC to review and accept


Outreach and communications
 - UBL Adoption SC report


JIRA tickets
   https://issues.oasis-open.org/issues/?filter=12972 (note that the view can
   be changed using the box icon at top right; the list view provides the most
   summary information, without the detail view obscuring the screen space)

   - when creating tickets, remember to distinguish the following components
     by how they are described to be used as categories:
<https://issues.oasis-open.org/browse/UBL/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel>https://issues.oasis-open.org/browse/UBL/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel

   - 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:
             https://issues.oasis-open.org/issues/?filter=12972
     - DEFERRED - the issue is not in consideration for the development
                  distribution
                - please remember to use this when creating new tickets for
                  backwards-incompatible changes
     - 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
← Prev in month ← Prev in thread
Next in thread → Next in month →