eDelivery CMB meeting 2024-01-18 minutes

Owned by Philip Helger
Last updated: Feb 08, 2024
3 min read

Date: 2024-01-18

Time: 08:30-09: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 (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-12-21

Status: approved

Information/Discussion items

  1. Organisational topics
    1. Idea on eDEC CMB members: one PA member would be considered positive
    2. Elly only available for another 3 month (leaving on April 19th, 2024 - last eDEC CMB on April 11th)
      1. Crosscheck with OO on how to do a smooth handover until the GA - potentially an interim from ATO
  2.  News
    1. News from the Peppol Network
      1. None so far this year
      2. Trond (Visma; APPCMB member) left the company by end of 2023 - was stepping down from the CMB position
      3. NPA performed a security check amongst NL Service Providers and found some issues
      4. SML impact on the beginning of January - discussed in the SPC meeting January 9th
      5. Next MC++ on Jan 29th
    2. Peppol - EESPA/GENA consolidation
      1. No update
    3. MLA work group (for MLS)
      1. No update
    4. Reporting
      1. Reporting data collection started on January 1st - country code is missing for some SP
      2. Accidentally a Reporting Email with a reminder to report in January was sent - bug in the OpenPeppol solution
    5. Service Provider Identification Scheme
      1. No update
    6. SMP 2.0.0
      1. Next Meeting Jan 25th, 16:00 to 17:30 CET
  3. Open Tasks Philip Helger
    1. Finalize TICC-19
      1. Add hint on upcoming SMP 2.0 specification
    2. Create a ticket to create a Guideline on the tasks of an Access Point solution
  4. Activities for this year
    1. Activities for 2024 not yet completely discussed and decided
    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. Thursday February 1st, and February 15th 8:30 to 10:30 CET are cancelled
    2. Next meeting: Thursday February 8th, 8:30 to 10:30 CET - followed by Feb 29th

SPC relevant

  • Nothi

New tasks and Issues (from last meeting)

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


  1. TICC-307 - Getting issue details... STATUS
    1. Information: Make reporting Specification repository on GitHub public
    2. Decision: Agreed
    3. Update: Done
  2. TICC-305 - Getting issue details... STATUS
    1. Information: error corrections and improvements to the SBDH specification
    2. Update: none
  3. TICC-304 - Getting issue details... STATUS
    1. Information: deprecate and remove old DE specific document type
    2. Update: none
  4. TICC-303 - Getting issue details... STATUS
    1. Information: extract Business Card specification from Peppol Directory specification
    2. Update: none
  5. TICC-286 - Getting issue details... STATUS
    1. Suggestion on C4 Country Code
    2. Decision: Wait for full CMB group participation
  6. TICC-285 - Getting issue details... STATUS
    1. 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 Businees Cards.
  7. TICC-284 - Getting issue details... STATUS
    1. Information: AS4 inconclusive specification on signing of AS4 Error messages
    2. Update: none
    3. Responsible: Elly Stinchcombe (Unlicensed)
  8. TICC-282 - Getting issue details... STATUS
    1. Update: Impact Analysis was provided
    2. Update: All Peppl SP support BC format v3 - okay to remove v1 and v2 from the published list of XSDs
    3. Responsible: PH
  9. TICC-269 - Getting issue details... STATUS
    1. Information: Request to improve consistency in AS4 error handling
    2. Update: none
  10. TICC-263 - Getting issue details... STATUS
    1. Information: Peppol Participant (Corner 4) served by more than one Access Point
    2. Update: none
    3. Responsible: Philip Helger
  11. TICC-259 - Getting issue details... STATUS
    1. Information: Request to add Participant Identifier scheme 0218
    2. Update: none
    3. Responsible: Philip Helger
  12. TICC-246 - Getting issue details... STATUS
    1. Information: update the SMP digest algorithms from SHA-1 to SHA-256
    2. Update: none
    3. Responsible: Philip Helger
  13. TICC-235 - Getting issue details... STATUS
    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. TICC-233 - Getting issue details... STATUS
    1. Information; Its about a wording issue in the Peppol Envelope Policy (SBDH)
    2. Update: none
    3. Responsible: Elly Stinchcombe (Unlicensed)
  15. TICC-226 - Getting issue details... STATUS
    1. Information: New SMP API proposal (migration code exchange)
  16. TICC-225 - Getting issue details... STATUS
    1. Information: New SMP API proposal (health check)
  17. TICC-224 - Getting issue details... STATUS
    1. Information: New SMP API proposal (identify)
  18. TICC-223 - Getting issue details... STATUS
    1. Information: Collection issue: Peppol, EESPA, BPC
  19. TICC-218 - Getting issue details... STATUS
    1. Information: Clarify case sensitivity of Peppol Seat ID
    2. Update: none
    3. Responsible: Philip Helger
  20. TICC-206 - Getting issue details... STATUS
    1. Information: Number of retries on an AS4 level
    2. Update: none
    3. Responsible: Philip Helger
  21. TICC-202 - Getting issue details... STATUS
    1. Information: Information about caching of SMP results for usage in a Peppol AP is missing
    2. Update: none
    3. Responsible: Philip Helger
  22. TICC-201 - Getting issue details... STATUS
    1. Information: Review of new/updated OASIS specifications
    2. Update: none
    3. Responsible: Elly Stinchcombe (Unlicensed)
  23. TICC-187 - Getting issue details... STATUS
    1. Information: Allow 0080 as new Participant Identifier scheme
    2. Update: none
    3. Responsible: Elly Stinchcombe (Unlicensed)
  24. TICC-184 - Getting issue details... STATUS
    1. Information: Align Participant Identifier Scheme Code lists of PoAC and eDEC
    2. Update: none
    3. Responsible: Philip Helger
  25. TICC-174 - Getting issue details... STATUS
    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
  26. TICC-168 - Getting issue details... STATUS
    1. Information: Have a separate participant identifier prefix for testing purposes.
    2. Update: none
  27. TICC-167 - Getting issue details... STATUS
    1. Information: regarding joint information on news and noteworthy
    2. Update: none
    3. Responsible: Philip Helger
  28. TICC-166 - Getting issue details... STATUS
    1. Information: Clarification on the words "custom validation" in the AS4 profile was sought.
    2. Update: none
    3. Responsible: Philip Helger
  29. TICC-153 - Getting issue details... STATUS
    1. Information: https for SMP
    2. Update: none
    3. Responsible: Philip Helger
  30. TICC-151 - Getting issue details... STATUS
    1. Information: (Whitepaper) Enforce people to use SMK for testing?
    2. Update: none
    3. Responsible: Philip Helger
  31. TICC-149 - Getting issue details... STATUS
    1. Information: add a Schematron for verifying the AS4 headers. Updates directly in the issue.
    2. Update: none
    3. Responsible: Philip Helger
  32. TICC-146 - Getting issue details... STATUS
    1. Information: (Whitepaper) Creation of the Whitepaper.
    2. Responsible: Philip Helger
  33. TICC-142 - Getting issue details... STATUS
    1. Information: (Whitepaper)
    2. Responsible: Philip Helger
  34. TICC-140 - Getting issue details... STATUS
    1. Information: (Whitepaper)
    2. Responsible: Philip Helger
  35. TICC-19 - Getting issue details... STATUS
    1. Information: Information on how to determine and handle inactive SMP providers
    2. Update: work in progress
    3. Responsible: Philip Helger

Attachments


none