/
eDelivery CMB meeting 2021-04-01 minutes

eDelivery CMB meeting 2021-04-01 minutes

Apr 01, 2021

Date: 2021-04-01

Time: 10:00-11:00 CEST

Type of meeting: Gotomeeting (https://www.gotomeet.me/MartinMane)

Participants and absents

 

Chair

@Martin Mane (Unlicensed) as eDelivery Community Leader

 

Elected members (with voting right)

@Bård Langöy (Pagero)

@Hans Berg (Deactivated) (Tickstar) (apologies received)

@Iacopo.Arduini@regione.emilia-romagna.it (Emilia Romagna)

@Espen Kørra (Unlicensed) (DigDir)

 

Guests (without voting right)

@Philip Helger (OpenPEPPOL OO) 

Agenda

  1. Approval of minutes

  2. New tasks and Issues

  3. Actions

  4. Information items

  5. AoB

Approval of Minutes

eDelivery CMB meeting 2021-03-18 minutes

Approved

New tasks and Issues

Issues: https://openpeppol.atlassian.net/issues/?filter=10226

 

  1. https://openpeppol.atlassian.net/browse/TICC-174

    1. Information: The term "Subject Unique Identifier" in the Peppol SMP specification 1.1.0 requires clarification, as this certificate field is not present in the Peppol certificates.

    2. Decision: It was agreed to use the "X.509 Certificate Subject X.500 Name" as the identifier of the SMP to redirect to. Will be part of the next round of eDEC specifications. The collection issue for this one is https://openpeppol.atlassian.net/browse/TICC-175.

    3. Responsible: @Philip Helger

  2. https://openpeppol.atlassian.net/browse/TICC-168

    1. Information: Have a separate participant identifier prefix for testing purpises.

    2. Decision: Should also be part of the Whitepaper.

  3. https://openpeppol.atlassian.net/browse/TICC-167

    1. Information: regarding joint information on news and noteworthy

    2. Decision: see ticket for details. OO to execute the actions.

  4. https://openpeppol.atlassian.net/browse/TICC-166

    1. Information: Clarification on the words "custom validation" in the AS4 profile was sought.

    2. Decision: A clarification was stated as a response to the ticket, that "custom validation" does NOT include business document validation. Improvement of the wording in the AS4 spec was put in the backlog.

  5. https://openpeppol.atlassian.net/browse/TICC-162

    1. Information: Deprecate the AS2 transport protocol

    2. Update: Questions have been designed by OO and agreed with the PA Community. Most suitable way forward is sought be OO. Waiting for the results.

  6. https://openpeppol.atlassian.net/browse/TICC-158

    1. Information: Updated the issue

    2. Decision: Further evaluate if ISO 6523 structuring can be used more efficiently (like in 9915:123456789:sadhjsadghas). Look into the ISO 6523 standard. Is most likely of strategic relevance.

    3. Responsible: @Martin Mane (Unlicensed)

  7. https://openpeppol.atlassian.net/browse/TICC-153

    1. Information: https for SMP; Philip sent out an email (2020-11-18) with a decision basis paper

    2. Update: CC action CC8-1 refers to this. On hold until the whitepaper is finished.

    3. Responsible: @Philip Helger

  8. https://openpeppol.atlassian.net/browse/TICC-151

    1. Information: Enforce people to use SMK for testing?

    2. Decision: Part of the Whitepaper.

    3. Responsible: @Philip Helger

  9. https://openpeppol.atlassian.net/browse/TICC-149

    1. Information: add a Schematron for verifying the AS4 headers. Updates directly in the issue

    2. Update: no update

    3. Responsible: @Philip Helger

  10. https://openpeppol.atlassian.net/browse/TICC-146

    1. Information: Creation of the Whitepaper. No further updates.

    2. Responsible: @Philip Helger

  11. https://openpeppol.atlassian.net/browse/TICC-142

    1. Information: Part of Whitepaper.

    2. Responsible: @Philip Helger

  12. https://openpeppol.atlassian.net/browse/TICC-140

    1. Information: Part of Whitepaper

    2. Responsible: @Philip Helger

  13. https://openpeppol.atlassian.net/browse/TICC-133

    1. Update: No further update. Wait for OO polling the AS2 usage and than piggyback on this solution

    2. Responsible: @Martin Mane (Unlicensed)

  14. https://openpeppol.atlassian.net/browse/TICC-132

    1. Information: Publication of the eDEC specification backlog.

    2. Update: Open for feedback until 2021-03-18

    3. Responsible: @Martin Mane (Unlicensed)

  15. https://openpeppol.atlassian.net/browse/TICC-98

    1. Update: none

  16. https://openpeppol.atlassian.net/browse/TICC-19

    1. Update: Part of Whitepaper

    2. Responsible: @Philip Helger

Other:

Actions

Action log: eDelivery CMB action log

Actions handled in this meeting:

Actions not handled in this meeting:

Information/Discussion items

  1. Next meeting on Thursday April 15th, 9:00 to 11:00 CEST

  2. No CC meeting last week. Hence no endorsement on Code List 7.5 changes. PH to send Code List 7.5 changes to CC for review

  3. Code Lists 7.4 was published and communicated.

  4. Feedback on the eDEC changes sent out on March 3rd were editorial only, as we accepted only comments on the specification changes.

    1. CC will be informed that publication procedure can start and the 6 month grace period can start.

    2. The list at https://docs.peppol.eu/edelivery/ requires an update. Ticket TICC-176 was created for that.

Attachments