/
eDelivery CMB meeting 2023-03-30 minutes

eDelivery CMB meeting 2023-03-30 minutes

Mar 30, 2023

Date: 2023-03-30

Time: 09:00-10:30 CET

Type of meeting: MS Teams / Zoom

Participants and absents

 

Chair

@Elly Stinchcombe (Unlicensed) as eDelivery Community Leader (apologies received)

 

Elected members (with voting right)

@Bård Langöy (Pagero)

@Risto Collanus (Visma)

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

@Arun Kumar Sharma (Basware) (apologies received)

 

Guests (without voting right)

@Philip Helger (OpenPeppol OO)

Agenda

  1. Approval of minutes

  2. New tasks and Issues

  3. Actions

  4. Information items

  5. Input from email

Approval of Minutes

eDelivery CMB meeting 2023-03-16 minutes

Status: Approved

New tasks and Issues

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

 

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

    1. Information: Change name of Code List Entries from Logistics

    2. Decision: Accepted by CMB. Part of Code List Release v8.5

    3. Responsible: @Philip Helger

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

    1. Information: Japan Self Billing Document Type Identifier request

    2. Decision: accepted by email - part of code list v8.5

    3. Responsible: PH

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

    1. Information: update the SMP digest algorithms from SHA-1 to SHA-256

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: Start definining potential actions for removing identifiers in the Code List States Document. Start with TICC-228

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: RFC about Ppfuoi changes for PINT - making DDTS officially supported

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information; Its about a wording issue in the Peppol Envelope Policy (SBDH)

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

    1. Information: New Participant Identifier scheme 0221 for Japan

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

    1. Information: New SMP API proposal (migration code exchange)

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

    1. Information: New SMP API proposal (health check)

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

    1. Information: New SMP API proposal (identify)

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

    1. Information: Collection issue: Peppol, EESPA, BPC

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

    1. Information: Clarify case sensitivity of Peppol Seat ID

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: Number of retries on an AS4 level

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: Please add SHA256 XMLsig to Peppol-SMP specs because Java17-security change

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: Information about caching of SMP results for usage in a Peppol AP is missing

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: Review of new/updated OASIS specifications

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

  17. https://openpeppol.atlassian.net/browse/TICC-197

    1. Information: how to effectivly apply the new state "removed" for code list entries. This is a subtask of TICC-184.

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed) / @Philip Helger

  18. https://openpeppol.atlassian.net/browse/TICC-187

    1. Information: Allow 0080 as new Participant Identifier scheme

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

    1. Information: Align Participant Identifier Scheme Code lists of PoAC and eDEC

    2. Update: none

    3. Responsible: @Philip Helger

  20. 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. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

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

    1. Information: regarding joint information on news and noteworthy

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: https for SMP

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: (Whitepaper) Creation of the Whitepaper.

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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

    1. Information: Information on how to determine and handle inactive SMP providers

    2. Update: none

    3. Responsible: @Philip Helger

Information/Discussion items

  1. Next meeting 2023-04-13, 9:00 to 11:00 CET

  2. Reporting

    1. eDEC CMB approved to take over the responsibility of the future developments of the End User Statistics Report Specification 1.0.0

    2. Suggestion to add more examples from Arun was accepted - 2 additional, non-normative examples will be provided

    3. Based on the EUSR example addition, also two TSR examples will be added

  3. Policy for use of Identifiers Update for Peppol Wildcard [Document Type Identifier] Scheme (previously DDTS)

    1. eDEC CMB approved the provided version for sending it out to public review

  4. SMP 2.0 internal Work group

    1. Next meeting: April 4th, 2023

  5. Next Code List update v8.5

    1. Will be released asap

 

Internal priorities

  1. Policy for use of Identifiers update for Peppol Wildcard Scheme (previously known as DDTS)

  2. Code List v8.5 update

  3. SMP signature algorithm update

  4. SMP 2.0 specification update (joint effort)

SPC relevant

  • Policy for use of Identifiers 4.2.0 draft

  • Takover of EUSR specification

Attachments

none