Date: 2025-08-28

Time: 10:30-11:00 CEST

Type of meeting: Zoom

Chair

@GEOK_Seong_Wah@imda.gov.sg 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)

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-07-31 minutes

Status: approved

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. OpenPeppol PKI Migration plan - final version

         1. Recommendation to OO to schedule a Webinar on the details of the PKI migration as soon as possible

      2. 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” (no progress since last)

            1. Remember the discussions and decisions and their foundations

2. Organisational topics

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

      1. #

   2. Noteworthy absences 2025

      1. Seong Wah: ?

      2. Bard: none atm

      3. Arun: Oct 20th to 26th, Nov 24th to 30th

      4. Iacopo: Sept 8th to 15th

      5. Risto: none atm

      6. Klaus: Oct 3rd to 19Oct

      7. Erwin: none atm

      8. Philip: Oct 6th to Oct 20th

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

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

1. https://openpeppol.atlassian.net/browse/PEPPOL-15397

   1. Information: add “MLS” as an SPIS Use Case ID

   2. Decision: accepted

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

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

   2. Decision: more information needed from PoAC CMB

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

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

   2. Decision: understanding the need; asking OO to come up with a proposal on how to best move forward

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

   1. Information: Request for new code list entry

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

   1. Small wording improvements in MLS needed

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

   1. Information: change domain community in code lists

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

   1. Information: Process ID using non-standard scheme

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

   1. Information: Wording in PFUOI policy not consistent

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

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

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

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

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

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

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

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

    1. Information: Update reference style in Peppol AS4 specification

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

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

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

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

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

    1. Information: Change document type identifier code list names

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

    1. Information: Error correction request in SMP specification

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

    1. Information: Make identifier scheme mandatory in SBDH

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

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

    1. Information: Create a Service Provider Identification Scheme

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

    1. Information: Error correction for Reporting Specification needed

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

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

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

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

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

    1. Information: Peppol Reporting name change

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

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

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

    1. Information: Codelist alignment

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

    1. Information: Codelist alignment

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

    1. Information: internal activity: create AP Operational Guideline

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

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

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

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

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

    1. Update: Deprecate old Business Card Formats

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

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

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

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

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

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

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

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

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

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

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

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

    1. Information: New SMP API proposal (identify)

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

    1. Information: Number of retries on an AS4 level

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

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

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

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

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

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

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

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

    1. Information: https for SMP

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

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

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

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

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

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

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

    1. Information: (Whitepaper)

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

    1. Information: (Whitepaper)

none