/
eDelivery CMB meeting 2025-07-03 minutes

eDelivery CMB meeting 2025-07-03 minutes

Date: 2025-07-03

Time: 10:00-11:00 CEST

Type of meeting: Teams

Participants and absents

 

Chair

@GEOK_Seong_Wah@imda.gov.sg as eDelivery Community Leader

 

Elected members (with voting right)

@Bård Langöy (Pagero)

@Risto Collanus (Visma) (apologies received)

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

@Arun Kumar Sharma (Basware)

 

Guests (without voting right)

@Philip Helger (OpenPeppol OO)

@Klaus Vilstrup (OpenPeppol OO) (apologies received)

@Erwin Wulterkens (OpenPeppol OO) (apologies received)

Agenda

  1. Open Tasks

  2. New Tickets

  3. Any other business

Approval of Minutes

eDelivery CMB meeting 2025-06-05 minutes

Status: approved

Information/Discussion items

 

  1. Open Tasks

    1. Code List alignment (not handled in this meeting)

    2. eDEC Specifications (not handled in this meeting)

      1. Add that new specifications take effect at 00:00 UTC unless noted otherwise

    3. Tasks in scope:

      1. MLS tasks

        1. OO to create a draft MLS Policy (no progress since last)

          1. This document will go out for formal member review for 4 weeks

        2. OO to create a draft SPOG on MLS (no progress since last)

          1. The SPOG will eventually go out for member review

          2. SPOG should contain the note, that each SP MUST be able to receive MLS, even if they only requested negative MLS

          3. SPOG should also contain a statement, how different document types may have different response time requirements

          4. Clarify that the Scope of MLS activities does not mean they have to be done

          5. Highlight the architectural change in the document exchange itself

          6. If C2 requested always MLS and does not get an MLS in time - what then?

        3. eDEC to create an internal document: “Evaluation of the mandatory usage of MLS in the Peppol Network”

          1. Remember the discussions and decisions and their foundations

  2. Organisational topics

    1. Optimizing the RFC, Development, Review and Publishing processes.

      1. #

    2. F2F CIWG meeting on Thursday after the conference with special invite to eDEC CMB members

      1. #

    3. Availability over the summer 2025

      1. Seong Wah: Around except 28.8. (vacation)

      2. Bard: Available for eDEC CMB meetings

      3. Arun: Always around

      4. Iacopo: Around, except 11.8 to 22.8 (tentative)

      5. Risto: ?

      6. Klaus: Always around

      7. Erwin: ?

      8. Philip: always around

  3. News (not handled in this meeting)

    1. News from the Peppol Network

    2. CIWG

    3. Service Provider Identification Scheme (identify C2 and C3)

      1. Out for member review

    4. SMP 2.0 WG

      1. Paused until end of March

    5. OO Internal Peppol Directory Initiative

  4. Activities for this year (not handled in this meeting)

    1. Initial draft for Activities 2024 was circulated internally

    2. Published

      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

    3. Resource problem is still pressing

    4. Ad activity 2: Discussion on the comparison of new and existing standards should be done in a less "ad hoc way"

      1. Start documenting findings in a more structured way

    5. Ad activity 3: Brainstorming for Peppol Architecure v2 has been started

      1. Check if a restricted Confluence page can be used instead

      2. Crosscheck with the long term tasks

  5. Next meeting(s)

    1. Next meeting: Thursday July 17th 2025, 10:00 to 11:30 CEST

New tasks and Issues (from last meeting)

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

 

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

    1. Information: retract decision from TICC-394 to include 9960. Instead use 0242 for UAE as well.

    2. Decision: Approved by eDEC CMB

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

    1. Information: Add 0242 to the code list of Participant Identifier Schemes

    2. Decision: Approved by eDEC CMB

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

    1. Information: Migration of PKI to a new PKI and platform, imposed by DigiCert.

    2. Decision: Approved and moved to OO for public consultation of migration plan.

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

    1. Information: Alignment between PPFUI and SBDH specification on non-XML payloads

    2. Decision: Approved and moved to OO for development, considering a solution that caters for eB2B and not create confusion to the non-eB2B users

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

    1. Information: SPIS still waiting for an ICD code, to make MLS happen in UAE it is requested to use 9960 and then let UAE follow the general migration of the SPIS

    2. Update: Retracted in favour of TICC-397 in alignment with UAE Tax Authority

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

    1. Information: Add PINT EU document type ID to code list. urn:peppol:pint:billing-1@eu-1

    2. Decision: Approved, to be aligned with other realeases

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

    1. Information: This RFC requests to update the Peppol SBDH spec to include MLS_TO and MLS_TYPE as contained in the Peppol MLS specification

    2. Decision: Approved and moved to OO for development

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

    1. Information: Change the example values to lowercase and add a recommendation to use lowercase

    2. Decision: not handled yet

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

    1. Information: Specify the HTTP status code for AS4 message exchanges in greater clarity

    2. Decision: not handled yet

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

    1. Information: Request to remove column from Participant Identifier Scheme Code List

    2. Decision: Generally agreed to move forward and include in next major release

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

    1. Information: Request for an error correction on Peppol AS4 profile on Content-Transfer-Encoding

    2. Decision: Generally agreed

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

    1. Information: Update reference style in Peppol AS4 specification

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

    1. Information: Internal task to cleanup document type identifier code list based on Service Domain feedback

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

    1. Information: Internal task to define rules how to name code list entries issued by OpenPeppol

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

    1. Information: Change document type identifier code list names

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

    1. Information: Error correction request in SMP specification

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

    1. Information: Make identifier scheme mandatory in SBDH

  18. https://openpeppol.atlassian.net/browse/TICC-347
    a. Information: support for larger documents in the Peppol Network

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

    1. Information: Create a Service Provider Identification Scheme

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

    1. Information: Error correction for Reporting Specification needed

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

    1. Information: Create official clarification between the use of a Participant Identifier and a Legal Identifier

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

    1. Information: Change Lower boundary of Business Entity within Business Card

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

    1. Information: Peppol Reporting name change

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

    1. Information: Use UTC as timezone for all Peppol publications date time

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

    1. Information: Codelist alignment

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

    1. Information: Codelist alignment

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

    1. Information: internal activity: create AP Operational Guideline

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

    1. Information: extract Business Card specification from Peppol Directory specification

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

    1. Information: Proposal to make mandatoriness of Directory API in SMP specification more clear

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

    1. Update: Deprecate old Business Card Formats

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

    1. Information: Request to improve consistency in AS4 error handling

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

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

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

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

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

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

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

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

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

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

    1. Information: New SMP API proposal (identify)

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

    1. Information: Number of retries on an AS4 level

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

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

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

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

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

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

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

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

    1. Information: https for SMP

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

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

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

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

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

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

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

    1. Information: (Whitepaper)

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

    1. Information: (Whitepaper)

Attachments

 

none