Agenda for Atlantic UBL TC call 27 March 2024 15:00UTC
http://www.timeanddate.com/worldclock/fixedtime.html?iso=2024-03-27T15:00:00
Atlantic: 10:00MSP/11:00Ottawa/15:00UTC/16:00Europe
Conferencing info
Meeting ID: 547 975 473
Passcode: oasis
Join from PC, Mac, Linux, iOS or Android:
https://us02web.zoom.us/j/547975473?pwd=bjVvdDhDcEZXZ3R3cldRYkpuQU13Zz09
Or iPhone one-tap (US toll):
+13462487799,,547975473#,,,,,,0#,,130346# US (Houston)
+16465588656,,547975473#,,,,,,0#,,130346# US (New York)
Or international dial-in number (toll):
https://us02web.zoom.us/u/kchtpYJm7L
Meeting ID: 547 975 473
Passcode: 130346
Referencing the specification
One of the following should be used as a specific citation:
- OASIS Universal Business Language (UBL) v2.4
- OASIS Universal Business Language (UBL) v2.3
- OASIS Universal Business Language (UBL) v2.2
- 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 2.4 documents are available in the OASIS repository:
- http://docs.oasis-open.org/ubl/cs01-UBL-2.4/
The canonical 2.3 documents are available in the OASIS repository:
- http://docs.oasis-open.org/ubl/os-UBL-2.3/
The canonical 2.2 documents are available in the OASIS repository:
- http://docs.oasis-open.org/ubl/os-UBL-2.2/
The canonical 2.1 documents are available in the OASIS repository:
- http://docs.oasis-open.org/ubl/os-UBL-2.1/
The ISO/IEC catalogue entry for UBL 2.1 is found at:
- http://www.iso.org/iso/catalogue_detail.htm/?csnumber=66370
The ISO/IEC document and attachments for UBL 2.1 are found at:
- http://standards.iso.org/ittf/PubliclyAvailableStandards/
Standing items
Anything to add?
Wikipedia page
Updates and maintenance of: https://en.wikipedia.org/wiki/Universal_Business_Language
Review of Atlantic call minutes
Minutes available under "Discussion" in the new Community Workspace: https://groups.oasis-open.org/communities/community-home/digestviewer?communitykey=556949c8-dac8-40e6-bb16-018dc7ce54d6
Membership status review
https://www.oasis-open.org/policies-guidelines/tc-process#membership
New member orientation information:
https://www.oasis-open.org/committees/document.php?document_id=59647
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):
- Todd Albers
o Member of X9, X12 B2X, ISO 20022 Payment SEG, OASIS BDXR, and convenor of the Business Payments Coalition e-Invoice work groups
- Kenneth Bengtsson
o Chair OASIS BDXR TC, Observer OASIS ebXML, DK Expert UN/CEFACT
- Erlend Klakegg Bergheim
o Member OASIS BDXR, Member OASIS ebXML Core & MS, Member CEN/TC434/WS8
- Peter Borresen
o DK Member CEN/TC440, Convenor CEN/TC440/WG7
- Andrea Caccia
- Paul Donohoe
- Kees Duvekot
o Member OASIS BDXR, Member of the NEN TC 434
- Sander Fieten
o Cochair OASIS ebXML Messaging Services TC, Cochair OASIS BDXR TC
- Ken Holman
o Member OASIS BDXR, member OASIS Code List Representation TC
- Yves Jordan
- Ole Madsen
o DK Member CEN/TC440
- Natalie Muric
Members losing voting status after this meeting:
- Kees Duvekot
- Sander Fieten
TC Vitality Check
The TC must next appoint or reappoint chair(s) in January 2025.
Next TC vitality check must be made in January 2025.
UNESCAP/ICC DSI Cross-border Paperless Trade Database
Mail from Craig about the UBL entry in the Cross-border Paperless Trade Database: https://groups.oasis-open.org/discussion/ubl-in-the-cross-border-paperless-trade-database
UBL 2.4
Pending launch of 60-day public review of candidate OASIS Standard: https://issues.oasis-open.org/projects/TCADMIN/issues/TCADMIN-4484
UBL 2.5
Deprecation Policy
The TC has approved a UBL Deprecation Policy version 1.0 available here:
- https://www.oasis-open.org/committees/document.php?document_id=71497&wg_abbrev=ubl (PDF)
- https://www.oasis-open.org/committees/document.php?document_id=71496&wg_abbrev=ubl (ODT)
Publishing tools
Implement deprecation support in the UBL tools and publishing environment.
Erlend has presented a strawman proposal for a YAML-format for documenting 2.5 work: https://github.com/klakegg/oasis-ubl-model. Agreed that the functionality added by a structured format adds value, not least when adding the complexity of deprecated components. A "front end" layer will be needed for business users to maintain the files.
Master spreadsheets for UBL 2.5 are available here:
- Library elements: https://docs.google.com/spreadsheets/d/18o1YqjHWUw0-s8mb3ja4i99obOUhs-4zpgso6RZrGaY/
- Document elements: https://docs.google.com/spreadsheets/d/1024Th-Uj8cqliNEJc-3pDOR7DxAAW7gCG4e-pbtarsg/
Ken has created a list of changes based on Definition and Cardinality that can be used to populate the "Last change" column: https://lists.oasis-open.org/archives/ubl/202401/msg00013.html. Kenneth will work on updating the spreadsheet models.
Workgroup participants: Erlend and Kees.
Semantic library review
Documents reviewed by the TC:
- ApplicationResponse
- AttachedDocument
- DocumentStatus
- DocumentStatusRequest
UBL 2.5 issues:
- UBL-357, ESG Information elements:
o https://issues.oasis-open.org/browse/UBL-357
o Ole reported that the Danish authorities are initiating work with product passport and other ESG reporting
o Input from Levine here:
§ https://issues.oasis-open.org/browse/UBL-357?focusedCommentId=84141&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-84141
§ https://issues.oasis-open.org/secure/attachment/12125/UBL%202.5%20Library%20Elements%20Spreadsheet%20-%20PCF%20Elements.xlsx
o Kenneth will create a first draft for UBL 2.5 based on Levine's data model.
o Erlend will set up a new Github branch to allow us to test the PCF data model.
- Digital product passport discussion:
o https://lists.oasis-open.org/archives/ubl/202401/msg00018.html
o The TC agrees that UBL shall facilitate the requirements of the digital product passport. A new Product Passport document type will be developed for UBL 2.5.
o The requirements are not entirely clear yet. It is anticipated that the EU will send out request for standardization this year.
o CEN/CENELEC has established JTC 24 to work on the digital product passport. The UBL TC ideally would like to establish a formal liaison with JTC 24, however, the establishing of a formal way to liaise with CEN at committee level is still pending.
o Kenneth will open a new ticket to track work on the product passport data model. Peter volunteered to be assigned the ticket.
- UBL-375, Standardize use of ApplicationResponse, DocumentStatus, EnquiryResponse, DocumentStatusRequest, and Enquiry:
o https://issues.oasis-open.org/browse/UBL-375
o Identified that the use of ApplicationResponse in the Billing diagrams (figures 77, 78 and 79) is incorrect. Kenneth will open a separate ticket.
- UBL-376, Deprecate AttachedDocument document type:
o https://issues.oasis-open.org/browse/UBL-376
o Cecile will reach out to the European Commission to ask for the status of its use.
- UBL-377, new InvoiceResponse document type:
o https://issues.oasis-open.org/browse/UBL-377
Agreed to review supplementary components at our next face-to-face meeting, i.e., the XML attributes listed here: https://docs.oasis-open.org/ubl/cs01-UBL-2.4/UBL-2.4.html#T-UBL-UNQUALIFIED-DATA-TYPES
Can we make a tool that users can run in their local environments to create a report about the use of supplementary components?
- Creating a stylesheet to extract the information is simple, but how do we get it out to the users? And what will we use the results for?
- Peter will contact users of UBL to assess how much information we would be able to harvest.
Specification review
Divide specification into multiple parts. Aim is to create a multipart specification.
Kenneth will identify the normative parts of the prose specification and create a first draft.
Workgroup participants: Kees, Kenneth, Levine, and Paul.
JSON syntax binding
Develop specification for a UBL JSON syntax binding.
Workgroup participants: Erlend and Kenneth.
Product Circularity Datasheet
The TC has been asked to review a mapping between UBL and the PCDS. Andrea and Kenneth to follow up.
Subcommittee reports
UBL Post-award
Anything to report?
UBL Pre-award
Anything to report?
UBL Transportation Subcommittee (TSC)
The TSC met March 5, 2024. Discussion about deprecating Freight Invoice, and Waybill or Bill of Lading. Peter will send out meeting minutes.
The next TSC meeting will be in early April (Peter will send out the invite with agenda).
Anything to report?
Organisation Master Data Subcommittee
Anything to report?
Payments and Finance SC
Anything to report?
TC Liaisons
CEN TCs 434 and 440
Agreed at the Copenhagen face-to-face meeting that the UBL TC is open to establish a formal liaison with CEN TC 434 to create a European or international standard for electronic invoicing, if there is an interest from the CEN TC.
OASIS has reported that there is an agreement on a way forward. The TC has agreed to appoint Wim Kok liaison officer to the CEN TC 434, and Peter Borresen as liaison officer to the CEN TC 440, as recorded here: https://lists.oasis-open.org/archives/ubl/202301/msg00017.html. The appointments have been communicated to OASIS.
ISO/IEC JTC 1/SC 32/WG 1
Decision to appoint Andrea as liaison representative between ISO/IEC JTC 1/SC 32 and the TC recorded here: https://lists.oasis-open.org/archives/ubl/202007/msg00014.html
Last year's SC 32 meeting was held on June 2022. OASIS should have been following up with the SC 32 secretariat last year but still no progress. Jamie will follow up with SC 32.
ISO TC 323 (WG5)
Decision to appoint Andrea as liaison representative between ISO TC 323 (WG5) and the TC recorded here: https://lists.oasis-open.org/archives/ubl/202402/msg00004.html
Subcommittee conference calls
- Subcommittees will be meeting on an as-required basis.
TC conference call schedule
Face-to-face meeting
Time and venue for next face-to-face meeting?
Spring meeting:
- Budapest, May 27-30, 2024:
o Confirmed that the MSZT (Hungarian standardization body) will host our face-to-face meeting in Budapest.
o Meeting will commence May 27 midday, so that participants can travel in the morning.
o Craft Conference will be held the same week, May 30-31 (https://craft-conf.com/2024)
o XML Prague is the following week, June 6-8 (https://www.xmlprague.cz)
Fall meeting:
- Confirmed that Logius will host us in The Hague November 11-14, 2024.
Call schedule
Agreed to temporarily suspend the Pacific calls while we have no participants from the Pacific region. Pacific calls will be reinstated upon request from any TC member.
2024-03-26/2024-03-27
- Pacific: Canceled
- Atlantic: 10:00MSP/11:00Ottawa/15:00UTC/16:00Europe
2024-04-02/2024-04-03
- Pacific: Canceled
- Atlantic: 09:00MSP/10:00Ottawa/14:00UTC/16:00Europe
2024-04-09/2024-04-10
- Pacific: Canceled
- Atlantic: 09:00MSP/10:00Ottawa/14:00UTC/16:00Europe
2024-04-16/2024-04-17
- Pacific: Canceled
- Atlantic: 09:00MSP/10:00Ottawa/14:00UTC/16:00Europe
2024-04-23/2024-04-24
- Pacific: Canceled
- Atlantic: 09:00MSP/10:00Ottawa/14:00UTC/16:00Europe
2024-04-30/2024-05-01
- Pacific: Canceled
- Atlantic: 09:00MSP/10:00Ottawa/14:00UTC/16:00Europe
2024-05-07/2024-05-08
- Pacific: Canceled
- Atlantic: 09:00MSP/10:00Ottawa/14:00UTC/16:00Europe
2024-05-14/2024-05-15
- Pacific: Canceled
- Atlantic: 09:00MSP/10:00Ottawa/14:00UTC/16:00Europe
2024-05-21/2024-05-22
- Canceled
TC calendar
http://www.oasis-open.org/committees/calendar.php?wg_abbrev=ubl
iCal subscription link: http://www.oasis-open.org/apps/org/workgroup_feeds/ical/my_vcalendar.ics?token=fa658a7994a6cefb10c10be09e139af3&workgroup_id=50
Other business
As comes forward
Este correo electrónico y cualquier archivo transmitido con él son propiedad de Efact S.A.C., contiene información confidencial, y están destinados exclusivamente al uso de la persona o entidad a la que van dirigidas. Si usted no es el destinatario señalado, no puede difundir y distribuir o copiar este e-mail. Por favor notifique inmediatamente al remitente por correo electrónico si usted ha recibido este correo electrónico por error, y eliminar este correo electrónico de su sistema. Si usted no es el destinatario, se le notifica que revelar, copiar, distribuir o tomar cualquier acción basada en el contenido de esta información está estrictamente prohibida.
This email and any files transmitted with it are the properties of Efact S.A.C., contains confidential information, and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee you may not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake, and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.