Date: 2025-12-18

Time: 10:00-11:00 CET

Type of meeting: Teams

Chair

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

Elected members (with voting right)

@Bård Langöy (Pagero)

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

@Arun Kumar Sharma (Basware)

@Mathieu Pasture (Unlicensed) (PeppolEdge)

Guests (without voting right)

@Philip Helger (OpenPeppol OO)

@Klaus Vilstrup (OpenPeppol OO)

@Erwin Wulterkens (OpenPeppol OO)

Agenda

1. Open Tasks

2. New Tickets

3. Any other business

eDelivery CMB meeting 2025-12-04 minutes

Status: approved

1. Open Tasks

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

   2. eDEC Specifications

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

   3. Tasks in scope:

      1. OpenPeppol PKI Migration

      2. MLS tasks

         1. OO to create a draft SPOG on MLS

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

         3. Draft a few slides on the status of the MLS for presenting it in the PAC (and SPC?) meeting

         4. PNP Document is ready for Member Review

            1. The decision of the eDEC CMB Meeting 2025-12-05 on approving the PNP document was revoked unanimously in today’s meeting as the member review hasn’t been started yet

            2. eDEC CMB approved a slightly modified Peppol Network Policy 1.0.0 for Member Review

            3. The Peppol Business Message Envelope Specification 2.0.2 was approved for Member Review

            4. The Peppol MLS Specification 1.1.0 changes were approved for Member Review

            5. The Member Review is supposed to start today, December 18th, 2025

            6. Expected Review Period until January 26th, 2026

2. Organisational topics (not handled in this meeting)

   1. Noteworthy absences 2025

      1. Seong Wah: none atm

      2. Bard: none atm

      3. Arun: none atm

      4. Iacopo: none atm

      5. Klaus: none atm

      6. Erwin: 25.12.2025 to 1.1.2026

      7. Philip: 22.12.2025 to 9.1.2026 (meeting free time)

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: January 15th, 2026, 10:00 to 11:30 CET, Teams

      1. Apologies from Mathieu

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

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

   1. Information: Request to register new Document Type ID for XRechnung CVD

   2. Decision: discussion was postponed due to lack of time

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

   1. Information: Request to register new Participant Identifier Scheme GEBA (0246)

   2. Decision: Approved

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

   1. Information: Request to add existing process ID to existing document type IDs

   2. Decision: Approved

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

   1. Information: Remove AU-NZ busdox Document types

   2. Decision: Approved

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

   1. Information: Request to update UAE TDD document types

   2. Decision: Approved

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

   1. Information: Request to deprecate and remove old XRechnung Document Types (2.0 to 2.3)

   2. Decision: Approved

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

   1. Information: Request to deprecate one document type in LoC

   2. Decision: Approved

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

   1. Information: Request to remove deprecated document types issued by OpenPeppol

   2. Decision: Approved with a specific process

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

   1. Information: Add 0245 for Slovakia to Participant Identifier Scheme Code List

   2. Decision: Approved

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

    1. Information: Add 0244 for Nigeria to Participant Identifier Scheme Code List

    2. Decision: Approved

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

    1. Information: Add PING NG Document Type Identifiers to the code list

    2. Decision: Approved

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

    1. Information: Request to change Scheme ID of 0190 from “NL:OINO” to “NL:OIN”

    2. Decision: Conditionally approved by eDEC CMB in combination with the change of TICC-380 which will change the “Scheme ID” from a “key column” to an informational column. This will be part of the upcoming codelist release v10

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

    1. Information: Request to remove 9954 in favour of 0190

    2. Decision: Approved by eDEC CMB

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

    1. Information: request to add EN 16931 2026 code list identifier

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

    1. Information: request to provide and enforce Participant Identifier Scheme structure

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

    1. Information: Request for new code list entry

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

    1. Small wording improvements in MLS needed

    2. Update: approved wording update; clarification on the Architecture Framework needed

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

    1. Information: Wording in PFUOI policy not consistent

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

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

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

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

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

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

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

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

    1. Information: Update reference style in Peppol AS4 specification

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

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

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

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

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

    1. Information: Error correction request in SMP specification

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

    1. Information: Make identifier scheme mandatory in SBDH

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

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

    1. Information: Error correction for Reporting Specification needed

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

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

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

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

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

    1. Information: Peppol Reporting name change

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

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

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

    1. Information: Codelist alignment

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

    1. Information: Codelist alignment

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

    1. Information: internal activity: create AP Operational Guideline

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    1. Information: New SMP API proposal (identify)

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

    1. Information: Number of retries on an AS4 level

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    1. Information: (Whitepaper)

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

    1. Information: (Whitepaper)

none