/
eDelivery CMB meeting 2024-12-19 minutes

eDelivery CMB meeting 2024-12-19 minutes

Dec 19, 2024

Date: 2024-12-10

Time: 10:00-11:30 CET

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)

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

@Arun Kumar Sharma (Basware)

 

Guests (without voting right)

@Philip Helger (OpenPeppol OO)

@Klaus Vilstrup (OpenPeppol OO)

Agenda

  1. Open Tasks

  2. New Tickets

  3. Any other business

Approval of Minutes

eDelivery CMB meeting 2024-12-05 minutes

Status: approved

Information/Discussion items

  1.  Organisational topics (not handled in this meeting)

    1. Exchange Summit in Kuala Lumpur (@GEOK_Seong_Wah@imda.gov.sg)

  2. News (no news)

    1. News from the Peppol Network

    2. Peppol - GENA consolidation

    3. CIWG

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

    5. SMP 2.0 WG

    6. MLA work group (for MLS)

    7. OO Internal Peppol Directory Initiative

  3. 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. https://openpeppol.atlassian.net/browse/TICC-361 SML Operational Issue

        1. Mandate on https for SMP providers in combination with the CNAME-NAPTR change (See last meetings)

        2. Next steps

          1. Finalize specification changes (incl. SMP 2.0 WG members and eDEC CMB members) (done)

            1. The specifications was shared with the CMB at the beginning of the meeting:

              1. * Policy for use of identifiers: ready for public review from Philip perspective

              2. * SML specification: ready for public review from Philip perspective

              3. * SMP specification: needs further fine tuning before read for public review (to be shared ASAP)

            2. A walkthrough of the specification was conducted by @Arun Kumar Sharma

            3. It was agreed that the members of the CMB @GEOK_Seong_Wah@imda.gov.sg, @Arun Kumar Sharma, @Iacopo.Arduini@regione.emilia-romagna.it, @Bård Langöy, @Risto Collanus  individually reviews the specifications and sends comments/approval for readiness for Public Review by Wednesday 11th of December 2024 to the eDEC CMB mailinglist.

            4. It was agreed that @Philip Helger and @Klaus Vilstrup prepares the specifications for public review.

          2.  eDEC CMB decision on proceeding to the public review (done)

            1. Was handled through email (see item a.)

          3. Run the public review (duration until Sun Jan 19th, 2025) 

            1. The public review publication text was agreed in today's meeting 

            2. Create the migration plan in parallel

          4. Collect and resolve comments and get eDEC CMB approval on final version (plan: End of January 2025)

          5. Publish version and start migration periode (phase in)

      2. https://openpeppol.atlassian.net/browse/TICC-332 MLS

        1. Some work was done by Klaus and Philip

        2. Next steps

          1. Finalize the Documentation (it's not a BIS but an eDEC Specification)

          2. Get the Documentation approved by eDEC CMB

            1. Present release candidate for next eDEC CMB meeting on January 16th, 2025

          3. In parallel work on the supporting material like semantic model, syntax binding, code lists, rules and Schematrons

            1. No eDEC approval required but will be sent out for information

          4. Decide on the way forward how to introduce the MLS into the Peppol Network BEFORE the public review

          5. Package for public review

            1. MLS as a deployment on test-docs.peppol.eu

              1. Includes Documentation and supporting material

            2. SPIS specification Public Review Draft

          6. Run the public review

          7. Collect and resolve comments and get eDEC CMB approval on final version

          8. Publish version

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

    1. Initial draft for Activities 2024 was ciruclated 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 January 16th 2025, 10:00 to 11:30 CET

New tasks and Issues (from last meeting)

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

Not updated and not handled in this meeting.

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

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

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

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

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

    1. Information: New Norway specific document type identifiers

    2. Update: Requires MC approval first

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

    1. Information: Change document type identifier code list names

    2. Decision: rejected with a request for reconsideration

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

    1. Information: New process identifiers for France

    2. Decision: Approved by eDEC CMB with comment

    3. Responsible: 

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

    1. Information: Request to remove Germany specific identifier from codelist

    2. Decision: Approved by eDEC CMB

    3. Responsible: 

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

    1. Information: Add support for France Document Types

    2. Decision: Approved by eDEC CMB with comment

    3. Resonsible: 

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

    1. Information: Request to use NAPTR record lookup instead of CNAME lookup

    2. Decision: Agreed by eDEC CMB to move forward

    3. Responsible: 

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

    1. Information: Request to add DICO MaintenanceStatus document to the code list.

    2. Decision:

    3. Responsible:

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

    1. Information: Request to add BIS Self Billing to the Code List

    2. Decision: Approved by eDEC CMB

    3. Responsible: @Philip Helger

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

    1. Information: Clarification on PFUOI length of participant identifiers is requested (Policy 1)

    2. Decision: It was decided to increase the Party and Participant Identifier length to 130 and a clarification on the identifier scheme was added

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

    1. Information: Error correction request in SMP specification

    2. Decision:

    3. Responsible:

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

    1. Information: Make identifier scheme mandatory in SBDH

    2. Decision:

    3. Responsible:

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

    1. Information: Request to add ICD code 0236 to eDEC Participant Identifier Scheme code list

    2. Updated: Request is denied, as the request is for Post Award Party identification only

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

    1. Information: support for larger documents in the Peppol Network

    2. Update: none

  16. TICC-337 to TICC-341 are related to the new Enhanced B2B domain

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

    1. Information: Create a Service Provider Identification Scheme

    2. Update: 1.0.0-RC2 available; agreed by eDEC CMB

    3. Next steps: Public Review together with MLS

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

    1. Information: RFC to convert the output of the MLA work group (the Message Level Status, MLS) into an eDEC specification

    2. Update: We agreed to phase out MLR and make sure that MLS is defined in a clear way instead. The MLS data model and use cases covers the MLR data model and use cases.

    3. Next steps: Fine tune the text and provide for a public review

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

    1. Information: Error correction for Reporting Specification needed

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: Peppol Reporting name change

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

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

    1. Information: Codelist alignment

    2. Update: none

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

    1. Information: Codelist alignment

    2. Update: none

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

    1. Information: internal activity: create AP Operational Guideline

    2. Update: none

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

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

    2. Update: none

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

    1. Information: Request to add new document types

    2. Decision: Agreed to include in the codelist

    3. Responsible: 

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

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

    2. Update: none

    3. Decision: OO to clarify on the mandatory use of Business Cards.

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

    1. Information: AS4 inconclusive specification on signing of AS4 Error messages

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Update: Deprecate old Business Card Formats

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

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

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

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

    2. Update: none

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

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

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

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

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

    1. Information: New SMP API proposal (identify)

    2. Update: none

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

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

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

    1. Information: Clarify case sensitivity of Peppol Seat ID

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: Number of retries on an AS4 level

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    1. Information: Allow 0080 as new Participant Identifier scheme

    2. Update: none

    3. Responsible:

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

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

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

    2. Update: none

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

    1. Information: regarding joint information on news and noteworthy

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    1. Information: https for SMP

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

Attachments

 

none