Agenda for Pacific UBL TC call 07 March 2018 01:00UTC
http://www.timeanddate.com/worldclock/fixedtime.html?iso=2018-03-07T01:00:00 2018-03-07 UBL Pacific - 19:00MSP/20:00Lima/20:00Ottawa/01:00UTC/12:00Sydney CONFERENCING INFO Meeting ID: 547 975 473 Join from PC, Mac, Linux, iOS or Android:
https://zoom.us/j/547975473 Or iPhone one-tap (US toll): +14086380968,,547975473# or +16465588656,,547975473# Or international dial-in number (toll):
https://zoom.us/zoomconference?m=tZYVoCjT6sw0zaoKK3bbfRHUX43prdSf Many thanks to
http://eFact.pe for sponsoring our teleconferences. 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ÜÛ?umber=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 - any new events to add at this time? Review of Pacific call minutes
https://lists.oasis-open.org/archives/ubl/201802/msg00056.html Review of Atlantic call minutes
https://lists.oasis-open.org/archives/ubl/201802/msg00058.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, 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 - Cécile Guasch - Member CEN/TC440, Convenor CEN/TC440/WG1, Convenor CEN/TC440/WG2, European Commission liaison (DIGIT Interoperability Unit) - 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 - members approaching losing voting status after this meeting: - Peter Borresen - Kees Duvekot - Cécile Guasch - members approaching gaining voting status after this meeting: - Matt Vickers, Xero - Member OASIS BDXR, Member US Business Payments Coalition - active non-voting members - Enric Staromiejski Torregrosa - Member OASIS ebXML, European Commission liaison (DG GROWTH) - Roberto Cisternino - IT Expert UN/CEFACT - Audun Vennesland - new member orientation information:
https://www.oasis-open.org/committees/document.php?document_id=59647 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 CSPRD03 underway until March 13:
https://lists.oasis-open.org/archives/ubl-comment/201802/msg00007.html - we need 3 statements of use, one of which must be an organizational member of OASIS before we can proceed to the next stage and each one must follow a strict format:
https://www.oasis-open.org/policies-guidelines/oasis-defined-terms-2017-05-26#dStatementUse - if there are no show-stopping comments, Ken can prepare the Committee Specification package for acceptance March 14 and get it published so that writers of statements of use can cite the CS - if we have the statements of use, Ken can prepare Candidate OASIS Standard for a "vote for a vote" during the meetings of March 21 per:
https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#OSsubmission - we will vote to ask TC Administration to prepare an online Special Majority Vote to put out the candidate for standardization
https://www.oasis-open.org/policies-guidelines/oasis-defined-terms-2017-05-26#dSpecialMajority - countdown to standardization outlined in our UBL Governance document:
http://docs.oasis-open.org/ubl/UBL-Governance/v1.0/cn01/UBL-Governance-v1.0-cn01.html#S-THE-PATHWAY-TO-STANDARDIZATION - CSPRD03 15 day review - Candidate OASIS Standard COS1 prepared in mid March -
https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#OSsubmission - search begins for Statements of Use of candidate UBL 2.2 - we need three statements of use to make UBL 2.2 a final standard -
https://www.oasis-open.org/policies-guidelines/oasis-defined-terms-2017-05-26#dStatementUse - 60-day public review of COS1 over by the end of May - 14-day OASIS member ballot at end of May - early July UBL 2.2 becomes an OASIS Standard - mid-May we will begin the ISO revision process for ISO/IEC 19845 - we are already 6 months from our original objective of end of 2017 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 - 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 - we should further consider the idea raised earlier of splitting UBL into different normative parts - 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 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 Outreach and communications - work progressing on analyzing current communication channels
https://lists.oasis-open.org/archives/ubl-adoption/201710/msg00001.html - Kenneth will ask TC Admin about elaborating on the bounce message to UBL-comment with more details about the nature of subscribing to use the list UBL Transportation Subcommittee - new document types discussed at the face-to-face 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:
https://issues.oasis-open.org/browse/UBL-174 - 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 - no comments yet received regarding extensible ABIEs:
https://www.oasis-open.org/committees/document.php?document_id=62586 JSON Task Group and 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:
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 - awaiting TC Administration feedback regarding:
https://lists.oasis-open.org/archives/ubl-comment/201705/msg00000.html - 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:
https://issues.oasis-open.org/browse/TCADMIN-2587 - 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
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 - 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:
https://issues.oasis-open.org/issues/?filter=12972 - 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:
https://lists.oasis-open.org/archives/ubl/201709/msg00000.html - 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 NEXT FACE-TO-FACE - the face-to-face meeting in Australia was very successful and fruitful - should we be planning our next face-to-face meeting? TC CONCALL SCHEDULE 2018-03-07 UBL Pacific - 19:00MSP/20:00Lima/20:00Ottawa/01:00UTC/12:00Sydney 2018-03-07 UBL Atlantic - 09:00MSP/10:00Lima/10:00Ottawa/15:00UTC/16:00Europe 2018-03-14 UBL Pacific - 19:00MSP/19:00Lima/20:00Ottawa/00:00UTC/11:00Sydney 2018-03-14 UBL Atlantic - 10:00MSP/10:00Lima/11:00Ottawa/15:00UTC/16:00Europe 2018-03-21 UBL Pacific - 19:00MSP/19:00Lima/20:00Ottawa/00:00UTC/11:00Sydney 2018-03-21 UBL Atlantic - 10:00MSP/10:00Lima/11:00Ottawa/15:00UTC/16:00Europe 2018-03-28 UBL Pacific - 19:00MSP/19:00Lima/20:00Ottawa/00:00UTC/11:00Sydney 2018-03-28 UBL Atlantic - 09:00MSP/09:00Lima/10:00Ottawa/14:00UTC/16:00Europe 2018-04-04 UBL Pacific - 19:00MSP/19:00Lima/20:00Ottawa/00:00UTC/10:00Sydney 2018-04-04 UBL Atlantic - 09:00MSP/09:00Lima/10:00Ottawa/14:00UTC/16:00Europe Notes regarding teleconference times: - note in the next weeks the only times not changing are Pacific calls in North America and Atlantic calls in Europe ... all other times are somewhat juggled until April and then no changes until October
https://lists.oasis-open.org/archives/ubl/201802/msg00000.html 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: <
http://www.oasis-open.org/committees/calendar.php?wg_abbrev=ubl >
http://www.oasis-open.org/committees/calendar.php?wg_abbrev=ubl TC calendar iCal subscription link: <
http://www.oasis-open.org/apps/org/workgroup_feeds/ical/my_vcalendar.ics?token=fa658a7994a6cefb10c10be09e139af3&workgroup_id=50 >
http://www.oasis-open.org/apps/org/workgroup_feeds/ical/my_vcalendar.ics?token=fa658a7994a6cefb10c10be09e139af3&workgroup_id=50 OTHER BUSINESS - as comes forward -- 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)