/
eDelivery CMB meeting 2023-11-23 minutes

eDelivery CMB meeting 2023-11-23 minutes

Nov 23, 2023

Date: 2023-11-23

Time: 08:30-10:30 CET

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)

Agenda

  1. News from the Peppol Network

  2. Open Tasks

  3. New Tickets

  4. Other

Approval of Minutes

eDelivery CMB meeting 2023-11-09

Status: approved

Information/Discussion items

  1. Organisational topics

    1.  

  2.  News

    1. News from the Peppol network

      1. GA16 was yesterday

      2. CC meeting on November 13th was cancelled

      3. Next MC++ meeting on November 27th

        1. Input from eDEC desired on progress and plan for 2024

      4. Next SPC meeting on December 5th - Elly can't participate

    2. Peppol - EESPA consolidation

      1. Incubation project basically re-started. Contains technical specification choices, document types to be exchanged - series of biweekly meetings started

    3. SMP 1.3.0

      1. Was published on the website; email communication was sent out

      2. Migration document created + Impact Analysis was updated based on community comments

    4. Code List v8.7 release

      1. Adds new document types

    5. MLA work group (for MLS)

      1. Final Work Group draft is currrently created

      2. "Delayed" option will be removed

      3. Will be circulated in the MLA Work Group asap

    6.  Reporting

      1. Reporting team created an updated Schematron for publication. See TICC-296

      2. Reporting specification requires immediate update

      3. Reporting Beta testing is still running and a third round (=month) will be performed. Testing until solution is considered "stable".

      4. Specific SP Participant Identification Scheme - considers potential alignment with EESPA EIN number. Peppol format is [0-9]{6}, EIN is [A-Z0-9]{7}

      5. Question how much data will be published by the PAs. Eventually guidelines for what data should/could be published publicly.

    7. SMP 2.0.0

      1. Next work group meeting following this meeting

      2. Goal is to have a public review candidate SMP 2.0 specification by the end of the year

      3. Once the document is ready for internal review, we need to see how to progress

    8. Nemhandel network in Denmark

      1. Uses the Peppol Network in a non-compliant way (~11K participants today) - OO in contact with the Danish PA

        1. Coexistance might be allowed for a temporary duration

  3. Open Tasks eDEC CMB

    1. Provide input on MC++ meeting to Elly - until Sun Nov 26th, 5pm UTC

      1. Source: "We will take the opportunity to consider progress against the 2023 Operational Plan and to discuss the process for developing the 2024 Operational Plan. It would be helpful if MC++ members can give thought to this in advance of the workshop."

      2. On the progress for 2023

      3. On the operational plan for 2024

  4. Open Tasks @Philip Helger

    1. SMP 1.3.0

      1. Provide an internal plan how to monitor SMP 1.3.0 implementation progress (for OO based on Peppol Analytics)

      2. Announce and explain in next SPC meeting

    2. Update Reporting specifications (TICC-296) - see above

    3. PPFUOI 4.2.0

      1. Create an impact analysis on PPFUOI 4.2.0

    4. Finalize TICC-19

      1. Add hint on upcoming SMP 2.0 specification

  5. Activities for this year

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

    2. Resource problem is still pressing

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

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

  6. Next meeting

    1. Thursday December 7th, 8:30 to 10:30 CET

SPC relevant

  • SMP 1.3.0 update

  • Codelist v8.7 update

  • Very vague SMP 2.0.0 information

  • Reporting update (Schematron focus)

New tasks and Issues (from last meeting)

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

 

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

    1. -

    2. Decision: Accepted

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

    1. -

    2. Decision: Minor change and accepted

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

    1. Suggestion on C4 Country Code

    2. Decision: Wait for full CMB group participation

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

    1. Proposal to make mandatoriness of Directory API in SMP specification more clea

    2. Update: none

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

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

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

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

    1. Update: Impact Analysis was provided

    2. Decision: Deprecate and Remove old Business Card Formats version 1 and version 2. Whether the result is Directory 1.1.2, 1.2.0 or 2.0.0 depends on the agility of the 3 affected SMP operators. PH to reach out to them.

    3. Responsible: PH

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

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

    2. Update: none

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

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

    1. Information: Request to add Participant Identifier scheme 0218

    2. Update: Part of EAS code list v12. To be added to OpenPeppol

    3. Responsible: @Philip Helger

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

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

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

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

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

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

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

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

    1. Information: New SMP API proposal (identify)

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

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

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

    1. Information: Clarify case sensitivity of Peppol Seat ID

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: Number of retries on an AS4 level

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    1. Information: Review of new/updated OASIS specifications

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

    1. Information: Allow 0080 as new Participant Identifier scheme

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

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

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

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

    2. Update: none

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

    1. Information: regarding joint information on news and noteworthy

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    1. Information: https for SMP

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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

    1. Information: Information on how to determine and handle inactive SMP providers

    2. Update: work in progress

    3. Responsible: @Philip Helger

Attachments

 

none