OASIS Business Document Exchange (BDXR) TC

Agenda for Atlantic BDXR TC call 04 December 2019 16:00UTC
http://www.timeanddate.com/worldclock/fixedtime.html?iso=2019-12-04T16:00:00
Atlantic: 11:00MSP/11:00Lima/12:00Ottawa/16:00UTC/17:00Europe
 
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
 
Standing items
 
Review of Pacific call minutes
https://lists.oasis-open.org/archives/bdxr/201912/msg00001.html
 
Review of Atlantic call minutes
https://lists.oasis-open.org/archives/bdxr/201911/msg00006.html
 
Membership status review
https://www.oasis-open.org/policies-guidelines/tc-process#membership
 
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 BDXR TC voting member list (alphabetical):
 

-   
Todd Albers

-   
Kenneth Bengtsson

-   
Erlend Klakegg Bergheim

-   
Ger Clancy

-   
Ken Holman
 
SMP 2.0
 
Issues found:
 

-   
Sections 2.1.3 and 4.3.4: Is Endpoint vs. Redirect conditional per request or per ProcessMetadata?

-   
REST URIs in 5.4 should be [{identifier scheme}::]{participant id} to be consistent with 3.6.3.

-   
Section 5.6.2.1: canonicalization identifier should be
http://www.w3.org/2006/12/xml-c14n11
 
If we open up the specification again, we can review some of Philip s earlier comments as well.
 
Status of Statements of Use:

-   
Difi (OpenPEPPOL?)

-   
IBM

-   
Philip Helger

-   
DG-DIGIT?

-   
Sander Fieten

-   
Business Payments Coalition

-   
Efact
 
Exchange Header Envelope (XHE)
 
Candidates for Statements of Use
OASIS Statement of Use and UN/CEFACT Proof of Concept candidates:

-   
Philip Helger

-   
IBM

-   
Efact

-   
Business Payment Coalition?
 
BDXL administration interface
 
Proposal from Erlend:
https://lists.oasis-open.org/archives/bdxr/201905/msg00015.html
 
There is a broad interest in this work product. Work on the specification will begin in January, with the decision of different bindings as the principal discussion to be had.
 
TC conference call schedule
 
Face-to-face meeting
Suggestion to co-locate face-to-face meeting with the UBL meeting tentatively scheduled for May 2020, either Napa Valley or Minneapolis.
 
Call schedule
 
2019-12-04

-   
Pacific: 20:00MSP/21:00Lima/21:00Ottawa/02:00UTC/13:00Sydney

-   
Atlantic: 10:00MSP/11:00Lima/11:00Ottawa/16:00UTC/17:00Europe
2019-12-17

-   
Pacific: 20:00MSP/21:00Lima/21:00Ottawa/02:00UTC/13:00Sydney

-   
Atlantic: 10:00MSP/11:00Lima/11:00Ottawa/16:00UTC/17:00Europe
2020-01-01

-   
Conference calls cancelled this week
 
Other business
 
As comes forward
 

Hi all, I already had a look on the questions raised by Kenneth on SMP2 CS01, find below my comments: -     Sections 2.1.3 and 4.3.4: Is Endpoint vs. Redirect conditional per request or per ProcessMetadata? This is probably a left over from SMP 1.0 where the redirect was on a higher level. Seems a minor issue to me as section 4.3.4 is explicit on that the condition described in section 2.1.3 applies only on the process level within the response and not to the response in general. But as we probably need to make some edits anyway I believe it would be good to also clarify this in section 2.1.3 by replacing in the same response with for the same process . REST URIs in 5.4 should be  [{identifier scheme}::]{participant id}  to be consistent with 3.6.3. I had a look on the old JIRA issues and meeting minutes, but couldn t quickly find the motivation for the current formatting as specified in section 3.6.3. It seems to make sense that in case no scheme is used to also leave out the :: part. As SMP 1.0 however does not make any statement on this it should be assumed that the :: should be included. Treating this differently makes it more difficult to create a generic implementation that can handle identifiers based on both versions of the spec. We could therefore also change section 3.6.3 (and to be consistent also 5.4) to  [{identifier scheme}]::{participant id}  ? I personally have a slight preference for changing the format to  [{identifier scheme}]::{participant id}  because of the  Interoperability with SMP 1.0, but won t object to keep the current format either. If we need some more discussion on this issue we maybe should consider creating a JIRA issue for it? -     Section 5.6.2.1: canonicalization identifier should be  http://www.w3.org/2006/12/xml-c14n11 Yes, this seems to be an editorial issue where the specification is referenced instead of the algorithm itself. So I agree this should be corrected. Groet, Regards, Sander Fieten, MSc T : +31 6 51 50 78 86 skype:  sfieten W :   www.chasquis-consulting.com eDelivery Holodeck B2B AS4 Consultancy On 4 Dec 2019, at 03:19, Kenneth Bengtsson < kbengtsson@efact.pe > wrote: AGENDA FOR ATLANTIC BDXR TC CALL 04 DECEMBER 2019 16:00UTC http://www.timeanddate.com/worldclock/fixedtime.html?iso=2019-12-04T16:00:00 Atlantic: 11:00MSP/11:00Lima/12:00Ottawa/16:00UTC/17:00Europe   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   STANDING ITEMS   Review of Pacific call minutes https://lists.oasis-open.org/archives/bdxr/201912/msg00001.html   Review of Atlantic call minutes https://lists.oasis-open.org/archives/bdxr/201911/msg00006.html   Membership status review https://www.oasis-open.org/policies-guidelines/tc-process#membership   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 BDXR TC voting member list (alphabetical):   -      Todd Albers -      Kenneth Bengtsson -      Erlend Klakegg Bergheim -      Ger Clancy -      Ken Holman   SMP 2.0   Issues found:   -      Sections 2.1.3 and 4.3.4: Is Endpoint vs. Redirect conditional per request or per ProcessMetadata? -      REST URIs in 5.4 should be   [{identifier scheme}::]{participant id}   to be consistent with 3.6.3. -      Section 5.6.2.1: canonicalization identifier should be   http://www.w3.org/2006/12/xml-c14n11   If we open up the specification again, we can review some of Philip s earlier comments as well.   Status of Statements of Use: -      Difi (OpenPEPPOL?) -      IBM -      Philip Helger -      DG-DIGIT? -      Sander Fieten -      Business Payments Coalition -      Efact   EXCHANGE HEADER ENVELOPE (XHE)   Candidates for Statements of Use OASIS Statement of Use and UN/CEFACT Proof of Concept candidates: -      Philip Helger -      IBM -      Efact -      Business Payment Coalition?   BDXL ADMINISTRATION INTERFACE   Proposal from Erlend:   https://lists.oasis-open.org/archives/bdxr/201905/msg00015.html   There is a broad interest in this work product. Work on the specification will begin in January, with the decision of different bindings as the principal discussion to be had.   TC CONFERENCE CALL SCHEDULE   Face-to-face meeting Suggestion to co-locate face-to-face meeting with the UBL meeting tentatively scheduled for May 2020, either Napa Valley or Minneapolis.   Call schedule   2019-12-04 -      Pacific: 20:00MSP/21:00Lima/21:00Ottawa/02:00UTC/13:00Sydney -      Atlantic: 10:00MSP/11:00Lima/11:00Ottawa/16:00UTC/17:00Europe 2019-12-17 -      Pacific: 20:00MSP/21:00Lima/21:00Ottawa/02:00UTC/13:00Sydney -      Atlantic: 10:00MSP/11:00Lima/11:00Ottawa/16:00UTC/17:00Europe 2020-01-01 -      Conference calls cancelled this week   OTHER BUSINESS   As comes forward Attachment: smime.p7s Description: S/MIME cryptographic signature