/
eDelivery CMB meeting 2023-11-09 minutes

eDelivery CMB meeting 2023-11-09 minutes

Nov 09, 2023

Date: 2023-11-09

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) (apologies received)

Agenda

  1. News from the Peppol Network

  2. Open Tasks

  3. New Tickets

  4. Other

Approval of Minutes

eDelivery CMB meeting 2023-09-28

Status: approved

Information/Discussion items

  1. Organisational topics

    1. Please send apologies ahead of time if you are not able to join

  2.  News

    1. News from the Peppol network

      1. GA16 was yesterday

      2. Next CC meeting on November 13th

      3. Next MC++ meeting on November 27th

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

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

    3. MLS work group

      1. MLS will be between C2 and C3 (compared to MLR being between C1 and C4) → implies mandatory receiving capabilities of MLS for Service Providers in the future (details to be worked out)

    4. Peppol - EESPA consolidation

      1. EESPA is renamed to "GENA" (Global Exchange Network Association)

      2. EESPA already started the consolidation process, OpenPeppol status is unknown to this group (Lefteris and Klaus? being the participants)

    5. SMP 1.3.0

      1. Commenting period ended on October 26th, 2023

      2. One comment sheet was received - no comments on the specification at all

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

    7. Nemhandel network in Denmark

      1. Uses the Peppol Network in a non-compliant way (~11K participants today)

        1. Uses the Peppol SML specification

        2. Uses the Peppol SMP specification

        3. Uses a separate AS4 profile

        4. Uses a different AP PKI

        5. Uses only OIOUBL document types

  3. Open Tasks @Philip Helger

    1. SMP 1.3.0

      1. Create a migration plan for SMP 1.3.0 specification (gradual implementation on SMP side should work, no big bang)

        1. 6 month implementation time for SMP servers

        2. SMP servers are able to implement the feature immediately

      2. Publish final version; target date asap

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

      4. News items for email, website and SPC meeting needed

    2. PPFUOI 4.2.0

      1. Create an impact analysis on PPFUOI 4.2.0

    3. Finalize TICC-19

      1. Add hint on upcoming SMP 2.0 specification

    4. Codelists

      1. Version 8.7 nearly ready for release - just waiting for TICC-297 details

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

  5. Next meeting

    1. Thursday November 23th, 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-297

    1. -

    2. Decision: Accepted

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

    1. -

    2. Decision: Accepted

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

    1. -

    2. Decision: Minor change and accepted

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

    1. Fix removal date of 9956 in a hotfix release to 2024-01-01

    2. Decision: Agreed to be changed

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

    1. Suggestion on C4 Country Code

    2. Decision: Wait for full CMB group participation

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

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

    2. Handling: divide it in two: a policy issue and how Business Card is presented in the Reporting Guideline. 

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

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

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

    2. Decision: AS4 Error Messages should be signed. A way forward was sketched

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

    1. Information: Deprecate Business Card formats v1 and v2 and requrest to support only v3

    2. Decision: RFC accepted

    3. Responsible: PH

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

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

    2. Update: none

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

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

    1. Information: Request to add Participant Identifier scheme 0218

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

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

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

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

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

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

    1. Information: New SMP API proposal (identify)

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

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

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

    1. Information: Clarify case sensitivity of Peppol Seat ID

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: Number of retries on an AS4 level

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: Please add SHA256 XMLsig to Peppol-SMP specs because Java17-security change

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    1. Information: Review of new/updated OASIS specifications

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

    1. Information: Allow 0080 as new Participant Identifier scheme

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

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

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

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

    2. Update: none

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

    1. Information: regarding joint information on news and noteworthy

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    1. Information: https for SMP

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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