/
eDelivery CMB meeting 2023-06-05 minutes

eDelivery CMB meeting 2023-06-05 minutes

Jun 05, 2023

Date: 2023-06-05

Time: 09:00-10:35 CEST

Type of meeting: MS Teams

Participants and absents

 

Chair

@Elly Stinchcombe (Unlicensed) as eDelivery Community Leader

 

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)

@Klaus Vilstrup (OpenPeppol OO) (apologies received)

Agenda

  1. Progress alignment with change and release management based on new agreement change processes

  2. Continue Peppol specification upgrade based on latest version of underlying standard e.g., OASIS

  3. Commence work on future of SML – defining business requirements followed by solution implementation in due course

  4. Documentation of Peppol eDelivery Network Architecture

  5. Ensure and maintain safe & secure operation over Peppol eDelivery Network

  6. Other

Approval of Minutes

eDelivery CMB meeting 2023-05-25 minutes

Status: approved

Information/Discussion items

  1. News

    1. This week is a Brussels live week

      1. Tuesday is an APAC meeting (AU, NZ, JP, SG)

      2. Wednesday is an MC++ meeting all day

      3. Thursday is the GA15

    2. Next SPC meeting next Tuesday: no specific eDEC input

    3. Proposed Webinar on Reporting implementation hints and guideline - to be clarified with OO

    4. Review period for Peppol Policy for Identifiers 4.2.0 ended. 50 comments received.

  2. Other

    1. Considering XHE over SBDH is not a topic for the SMP 2.0 work group

    2. Peppol Directory Analysis currently running through OO and APPCMB

  3. Tasks

    1. @Philip Helger - Speak to Didier and ask if he can present the French PoC to the eDEC CMB for 10 to 15 minutes

    2. Create a small document that outlines eDECs requirements for a smaller Change Managemet Process without a public review (e.g. for "low impact" code list changes)

      1. Align with Erwin and potentially add amendments to the IRs

    3. @Philip Helger to finalize TICC-19

    4. @Philip Helger to finalize TICC-246

  4. Next meeting

    1. Thursday June 22nd, 9:00 to 11:00 CEST

    2. Next SMP 2.0 workgroup meeting: June 19th, 12:30 to 14:00 CEST

SPC relevant

  • Nothing atm

New tasks and Issues (from last meeting)

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

 

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

    1. Information: New Document Type: SETU TimeCard

    2. Decision: Proposed an updated Document Type ID. Besides that approved to add the new Document Type ID

    3. Responsible: @Philip Helger

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

    1. Information: Add to the EUSR BIS that EU statistics must be provided per country

    2. Decision: Approved. Waiting for the specifics from the Peppol Reporting team.

    3. Responsible: @Philip Helger

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

    1. Information: Peppol Participant (Corner 4) served by more than one Access Point

    2. Decision: Duplicate from https://openpeppol.atlassian.net/browse/TICC-108 and https://openpeppol.atlassian.net/browse/TICC-142. eDEC to propose a way forward and discuss the possibilities with OO

    3. Responsible: @Philip Helger

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

    1. Information: TSR and EUSR Document Type Identifier is outdated

    2. Decision: Deprecated existing Reporting Dcument Type Identifiers (for removal per Sept 5th, 2023) and add the new ones

    3. Responsible: @Philip Helger

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

    1. Information: Request to add Participant Identifier scheme 0218

    2. Decision: none

    3. Responsible: @Philip Helger

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

    1. Information: Remove participant identifier scheme 9956

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

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

    2. Update: Approved in last CMB

    3. Responsible: @Philip Helger

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

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

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

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

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

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

    1. Information: New SMP API proposal (identify)

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

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

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

    1. Information: Clarify case sensitivity of Peppol Seat ID

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: Number of retries on an AS4 level

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

    1. Information: Review of new/updated OASIS specifications

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

    1. Information: Allow 0080 as new Participant Identifier scheme

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

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

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

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

    2. Update: none

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

    1. Information: regarding joint information on news and noteworthy

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    1. Information: https for SMP

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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

Attachments

none