Minutes of Atlantic UBL TC call 07 October 2020 14:00UTC

http://www.timeanddate.com/worldclock/fixedtime.html?iso=2020-10-07T14:00:00

Atlantic: 09:00MSP/10:00Ottawa/14:00UTC/16:00Europe

Participation

Todd Albers

Oriol Bausa Peris

Kenneth Bengtsson (convener)

Erlend Klakegg Bergheim

Peter Borresen

Ger Clancy

Paul Donohoe

Kees Duvekot

Cecile Guasch

Philip Helger

Ken Holman

Yves Jordan

Natalie Muric

Matt Vickers

Pacific call:

Kenneth Bengtsson (convener)

Andrea Caccia

Ken Holman

Levine Naidoo

Regrets:

Ole Madsen

Referencing the specification

One of the following should be used as a specific citation:

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

Additions to events calendar - http://ubl.xml.org/events

Nothing

Review of Pacific call minutes

https://lists.oasis-open.org/archives/ubl/202010/msg00010.html

Review of Atlantic call minutes

https://lists.oasis-open.org/archives/ubl/202009/msg00023.html

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

- Oriol Bausa Peris

o Member OASIS BDXR, Member OASIS ebXML, Editor TC434 Validation

- Kenneth Bengtsson

o Chair OASIS BDXR, Observer OASIS ebXML, DK Expert UN/CEFACT

- Peter Borresen

o DK Member CEN/TC440, Convenor CEN/TC440/WG7

- Andrea Caccia

o Chair CEN/TC 434, Member ETSI/ESI TC, IT Expert UN/CEFACT

- Ger Clancy

- Kees Duvekot

o Member OASIS BDXR, Member of the StandaardisatieÂplatform e-factureren

- Cecile Guasch

o Member CEN/TC440, Convenor CEN/TC440/WG1, Convenor CEN/TC440/WG2, European Commission liaison (DIGIT Interoperability Unit)

- Philip Helger

o Member OASIS BDXR

- G. Ken Holman

o Member OASIS BDXR

- Yves Jordan

- Ole Madsen

o DK Member CEN/TC440

- Natalie Muric

- Levine Naidoo

o Member OASIS BDXR, Observer OASIS ebXML

Members gaining voting status after this meeting:

- Erlend Klakegg Bergheim

- Paul Donohoe

UBL 2.3

ISO submission

Editors and subcommittee chairs need to familiarize themselves with ISO/IEC Directives Part 2 in order to produce content that is compliant with ISO requirements:

https://www.iso.org/directives-and-policies.html

ISO requirements being discussed here: https://issues.oasis-open.org/browse/UBL-240

UBL 2.3 CSD03 comment resolution

The two examples reported to be not validating (comment number CSD03-02) appear to be working fine.

https://www.oasis-open.org/committees/document.php?document_id=67718&wg_abbrev=ubl

Agreed that the errors reported cannot be reproduced. Kenneth will reply to David Goodenoughâs original comment on the UBL Comment list.

UBL 2.3 backwards compatibility

Discussion here: https://lists.oasis-open.org/archives/ubl-comment/202010/msg00000.html

Analyzed and discussed at the Pacific call that the change of the namespace for unqualified data types does not break backwards compatibility as the namespace is not used in any UBL instance.

Reply on the mailing list:

âThe unqualified data type namespace as no role in a UBL instance. It is a housekeeping namespace used in the declaration of the elements whose namespaces are being preserved for backward compatibility.â.

Agreed at the Atlantic call that our commitment to backwards compatibility is to ensure interoperability at the instance level between minor versions.

UBL 2.3 CSD04

Action items:

- Implement comment resolutions: https://www.oasis-open.org/committees/document.php?document_id=67718&wg_abbrev=ubl

- Manifest and Common Transportation Report documents

- Open JIRA tickets:

o Examples for new eFreight elements: https://issues.oasis-open.org/browse/UBL-296

o Usage and definition of SignatureMethod in ShipStoreArticle: https://issues.oasis-open.org/browse/UBL-297

o Usage of MeasureItemProperty in PortCallRecord: https://issues.oasis-open.org/browse/UBL-298

o Usage of DisposalOfCaseDescription in PersonnelHealthIncident: https://issues.oasis-open.org/browse/UBL-299

o HazardousGoodsTransit is missing a description: https://issues.oasis-open.org/browse/UBL-301

o Make shipment id optional: https://issues.oasis-open.org/browse/UBL-302

o Add ShipmentStageTypeCode and SequenceNumeric to ShipmentStage: https://issues.oasis-open.org/browse/UBL-303

Public reviews

UBL 2.1 JSON Alternative Representation 2.0 CND01

- Draft Comment Resolution Log: https://www.oasis-open.org/committees/document.php?document_id=67806&wg_abbrev=ubl

UBL 2.2 JSON Alternative Representation 1.0 CND01

- Draft Comment Resolution Log: https://www.oasis-open.org/committees/document.php?document_id=67807&wg_abbrev=ubl

UBL 2.3 JSON Alternative Representation 1.0 CND01

- Draft Comment Resolution Log: https://www.oasis-open.org/committees/document.php?document_id=67808&wg_abbrev=ubl

UBL Governance 1.1 CND01

- Draft Comment Resolution Log: https://www.oasis-open.org/committees/document.php?document_id=67813&wg_abbrev=ubl

UBL NDR 3.1 CND01

- Draft Comment Resolution Log: https://www.oasis-open.org/committees/document.php?document_id=67814&wg_abbrev=ubl

All 5 draft comment resolution logs were approved by the Pacific and Atlantic calls.

Editorship after UBL 2.3

Who will be taking over the editorship and maintenance of artefacts after Ken?

Peter has offered to help with spreadsheet maintenance. Kees and Cecile have offered to help with editorship and maintenance.

Agreed to schedule an âediting workshopâ to do a handover once we are closer to CSD04. Ken is working on finalizing the documentation. New sections added to the readme file in both Git repositories:

- https://github.com/oasis-tcs/ubl-2.3-artefacts/tree/develop#readme

- https://github.com/oasis-tcs/ubl-2.3-hub/tree/develop#readme

UBL Payments and Finance Subcommittee (PayFin)

Levine and Oriol working on updated Payment Means committee note.

UBL Post-award

Nothing

UBL Pre-award

Nothing

UBL Transportation Subcommittee (TSC)

Nothing

UBL Naming and Design Rules Subcommittee (NDRSC)

Nothing

Formation of new Organisation Master Data Subcommittee

Proposed charter for the Organisation Master Data Subcommittee:

The aim of this subcommittee shall be as follows:

To harmonise the semantics used in exchange of information sets about organisations including identifiers, attributes and properties, known as master data, required by governments or other bodies to organisations that is not linked to a specific process of the supply chain. This includes exchange of information mandated by governments such as in the Public procurement directives, Business Register Information System, etc. The first document to be produced is the Society Registration Information Notice.

Providing such a language will support facilitating the streamlining and the automation of the exchange of such information. In particular, it will be a cost saving instrument for SMEs.

Does the TC approve the formation of the Organisation Master Data Language Subcommittee with the above charter, and that the Subcommittee shall be cochaired by Cecile Guasch and Natalie Muric?

Agreed to vote about the formation of the SC next week.

Ken asked the SC to look into the custody of Business Card, Digital Agreement and Digital Capability document types.

TC Liaisons

ISO TC 204/WG7

Agreed at the September 11, 2019 TC conference call to seek a formal liaison with ISO TC 204/WG7 specifically for collaborating on the new ISO 24533 specification.

We need to appoint a liaison, preferably someone who is a member of both groups. See also: https://www.oasis-open.org/policies-guidelines/liaison#liaisons

CEN TC 434

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.

CEN informs that a liaison cannot be established at TC level. Awaiting feedback from 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

Andrea has requested that OASIS contacts SC 32 before next plenary August 19 so that the liaison can be formalized. No knowledge of communication from OASIS to SC 32 as of yet (September 02). Kenneth will follow up with Jaimie.

JIRA tickets

Available filters:

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

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

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.

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.

JIRA status and resolution value definitions

Necessary to review the definitions of ticket status and resolution in JIRA to align with the values that currently can be assigned.

Our current definitions are:

- NEW: the issue has been created but not yet agreed to be in consideration or not for the development distribution

o 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

o the other option on a new ticket is to change it to DEFERRED

o 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

o keep the issue OPEN when assigning to Ken for incorporation

o please remember to add a comment regarding expectations whenever you assign an OPEN ticket to another person for any action

- RESOLVED + Incomplete: the issue has been decided but not yet in test

- 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

o 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

Subcommittee conference calls

- Transportation Subcommittee will be on hold until after August.

- Pre-award Subcommittee will be on hold until further notice, unless there is a request for a meeting.

- Other subcommittees will be meeting on an as-required basis

Face-to-face

Agreed that an online work session in September is not necessary for resolving CSPRD03 comments nor for producing CSD04. A new work session can be planned if the need arises.

TC conference call schedule

Call schedule

Upcoming time zone changes marked with yellow:

2020-10-13/2020-10-14

- Pacific: 16:00MSP/23:00Europe/17:00Ottawa/21:00UTC/08:00Sydney

- Atlantic: 09:00MSP/10:00Ottawa/14:00UTC/16:00Europe

2020-10-20/2020-10-21

- Pacific: 16:00MSP/23:00Europe/17:00Ottawa/21:00UTC/08:00Sydney

- Atlantic: 09:00MSP/10:00Ottawa/14:00UTC/16:00Europe

2020-10-27/2020-10-28

- Pacific: 16:00MSP/22:00Europe/17:00Ottawa/21:00UTC/08:00Sydney

- Atlantic: 10:00MSP/11:00Ottawa/15:00UTC/16:00Europe

2020-11-03/2020-11-04

- Pacific: 16:00MSP/23:00Europe/17:00Ottawa/22:00UTC/09:00Sydney