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 Atlantic UBL TC call 28 September 2016 14:00UTC - voting meeting

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


Atlantic teleconference:

  Oriol Bausà
  G. Ken Holman (convener)
  Ole Madsen

Pacific teleconference attendance:

  Kenneth Bengtsson
  Kees Duvekot
  G. Ken Holman (convener)
  Tim McGrath


    - 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:
    - the ISO/IEC catalogue entry is found at:
    - the ISO/IEC document and attachments are found at:


   Additions to events calendar: http://ubl.xml.org/events
    - no new events to add at this time

   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
    - 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

Formal recognition of retired member
 - the officers of the UBL TC have composed the following text to send to
   Andy Schoka on behalf of the entire committee
   - proposed that the committee confirm this with a vote
     - AGREED - unanimous

The OASIS Universal Business Language Technical Committee wishes to formally recognize the exceptional contribution Andy Schoka has made to the development and success of the UBL standard (ISO/IEC 19845).

Andy joined the Committee exactly eleven years ago, an amazing commitment for a person who was supposedly slowing down into retirement. His deep knowledge of standardization processes, his tenacity, and his meticulous eye for detail have proven invaluable on many occasions. The quality of the work and the experiences of committee members have all benefitted from Andy's participation.

Voluntary activities such as this engage not only the professional but also the personal side of life. The UBL Technical Committee also appreciates the tacit acceptance by his patient wife Rita of the late night calls, long distance travel and periods of absence that she and Andy have endured over this time. The Committee thanks them both.

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:
   - the csd01wd07 working draft release of UBL 2.2 artefacts is found at:

 - documentation requirements
   - a Google text document of the hub document is here:
    - 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
   - section 3.2.x is now managed separately using the XML document
     "UBL-2.2-Schema-summary-information.xml" in this directory:
     - edit the XML directly, or copy and paste into your favourite editor
     - please do the process quickly to avoid conflict edits with others
     - there is no need to maintain alphabetization ... just group new
       documents at the end by subcommittee
     - please inform Ken when the changes are made

 - please review all JIRA tickets and comment and/or act where necessary:
   - 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

UBL-42 Add ActualPickupTransportEvent and ActualDeliveryTransportEvent as ASBIEs in Consignment

UBL-41 Replace references to UBL 1.0 to be UBL 2.0 for history of versions

UBL-34 Hub document change tracking

UBL-28 Support for Verified Gross Mass

UBL-27 Code lists for UBL 2.2

UBL-16 Allow for requested document distribution in Waybill and Bill of Lading document types

UBL-1 Documents for integrating supply chain
 - a lengthy discussion on this ticket occurred

Naming and Design Rules

 - three Statements of Use for BD-NDR have been submitted:
   - OASIS BDXR TC - Kenneth Bengtsson (for the BDE project)
     - https://lists.oasis-open.org/archives/ubl/201609/msg00052.html
   - OASIS UBL TC - G. Ken Holman (for the UBL project)
     - https://lists.oasis-open.org/archives/ubl/201609/msg00053.html
   - Document Engineering Services - Tim McGrath (for the Australian Digital
     Business Council)
     - https://lists.oasis-open.org/archives/ubl/201609/msg00054.html
   - VOTE: are these three submissions acceptable to the committee?
     - AGREED - unanimous
 - VOTE: does the committee agree to the Business Document Naming and Design
   Rules Version 1.0 Committee Specification 01 being submitted as a Candidate
   OASIS Standard?
     - AGREED - unanimous

JSON Task Group
 - notes from last week:
   - it was suggested that we create a JSON task group to explore the
     appropriateness of the technology w.r.t. UBL
- JSON and noSQL database solutions are good for working *with* UBL documents
   - XML is good for representing UBL documents for interchange
   - many vendors are coming out with solutions incorporating JSON, but they
     are all bespoke and incompatible with each other
   - if we ended up with a methodology for applying UBL structures in a
     JSON environment, this may be helpful to the community
 - does anyone know the provenance of http://json-schema.org/ to know if this
   is suitable?
 - still looking for a lead to take on this review
 - the comment was made that JSON realizes a specific instance of information
   and so any use of JSON will be application-specific on how that information
   is being used, and so it would be out of scope of the UBL committee to
   express constraints of a general nature across all use of JSON
 - Ken notes that ECMA has submitted JSON to ISO for standardization as
   ISO/IEC 21778 "The JSON data interchange format" as a PAS submission ...
   interestingly, the body of the document is only 5 pages of content and that
   fully describes the syntax
   - the ISO specification is this ECMA-404 document with an ISO cover page:
 - the discussion centred around what might be needed is a "serialization
   specification" of how to take a particular instance of the UBL business
   objects and express that and its constituent components using JSON syntax
 - this is not the equivalent of the XSD expression of constraints (which is
   then serialized as XML), this is directly going to the JSON syntax from
   some abstract programmatic expression of the values of the objects as CCTS
   business objects that we have standardized

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:

   - 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:
     - DEFERRED - the issue is not in consideration for the development
                - 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
- RESOLVED + Fixed - the issue is incorporated in a released test version;
                          (record which one)
     - RESOLVED + No Action - considered as no action for distribution
     - RESOLVED + Cannot Reproduce - considered as no action for distribution
     - APPLIED - the issue is included in a public review (record which one)
     - 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

UBL TC next steps

  - what promotional issues need to be addressed?
  - do we need a travelling road show along the lines of UBL International?
    - http://www.UBLConference.com
  - can anyone volunteer to create more short video segments to be shared?


 Next meetings:
  2016-10-05 Pacific 01:00UTC/21:00EDT, Atlantic 14:00UTC/16:00CEST/10:00EDT
  2016-10-12 No UBL teleconferences
  2016-10-19 Pacific 01:00UTC/21:00EDT, Atlantic 14:00UTC/16:00CEST/10:00EDT
  2016-10-26 Pacific 01:00UTC/21:00EDT, Atlantic 14:00UTC/16:00CEST/10:00EDT

 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:


 - none

Check our site for free XML, XSLT, XSL-FO and UBL developer resources |
Streaming hands-on XSLT/XPath 2 training @US$45: http://goo.gl/Dd9qBK |
Crane Softwrights Ltd. _ _ _ _ _ _ http://www.CraneSoftwrights.com/o/ |
G Ken Holman _ _ _ _ _ _ _ _ _ _ mailto:gkholman@CraneSoftwrights.com |
Google+ blog _ _ _ _ _ http://plus.google.com/+GKenHolman-Crane/posts |
Legal business disclaimers: _ _ http://www.CraneSoftwrights.com/legal |

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