/
eDelivery CMB meeting 2024-03-27 minutes

eDelivery CMB meeting 2024-03-27 minutes

Mar 27, 2024

Date: 2024-03-27

Time: 08:30-10:00 CET

Type of meeting: 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, without voting right)

@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 2024-03-14

Status: approved

Information/Discussion items

  1.  Organisational topics 

    1. Operational plan is done - to be presented in next GA on April 16th

    2. Code List alignment between POAC and eDEC needs to start - @Georg Birgisson (Unlicensed) and @Philip Helger to start analysing the issue; eDEC CMB approved the centralization of code lists

    3. Seong Wah Geok will participate in the next CMB (April 11th) and take over in the one afterwards (April 25th)

  2. News

    1. News from the Peppol Network

      1. No update

    2. Peppol - EESPA/GENA consolidation

      1. Document with shared requirements (business and technical) is now available. The architecture design phase may start now.

    3. Service Provider Identification Scheme

      1. No update

    4. MLA work group (for MLS)

      1.  No update - no input received

    5. Reporting

      1. Reporting period for Februrary was prolonged until March 22nd

      2. Big discussion in last SPC (19.3.2024) on the presentation of the End User Statistics

    6. SMP 2.0.0

      1. Call for participation was sent out. Deadline is Friday March 29th, 2024 23:59:59 UTC

      2. Kick-off is scheduled for Wed April 3rd, 8:30 to 10:00 CEST

    7. CIWG

      1. Initial Plenary meeting happened this week

      2. 3 sub work groups were identified (A - existing SML issues, B - federated SML and C - business policies and requirements)

      3. Next meeting on April 3rd, 10:00 to 11:00 CEST

  3. Open Tasks @Philip Helger

    1. Finalize TICC-19

      1. Add hint on upcoming SMP 2.0 specification

    2. Code List alignment (see above)

  4. Activities for this year

    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. Timezone change in Europe: Sunday March  31st

    2. Next meeting: Thursday April 11th, 8:30 to 10:30 CEST

SPC relevant

  • none

New tasks and Issues (from last meeting)

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

 

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

    1. Information: Add new column to identify abstract document type identifiers

    2. Decision: Agreed to add column in next minor release

    3. Responsible: @Philip Helger

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

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

    2. Decision: Create an broader impact-analysis document including thoughts on migrating existing unwanted setups

    3. Responsible: @Philip Helger

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

    1. Information: New profile for "Adviseringsmelding" (Customs Advice) in Norway

    2. Decision: 

    3. Responsible: 

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

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

    2. Decision: 

    3. Responsible: 

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

    1. Information: Ambiguity of Participant Identifier Casing between POLICY 1 and POLICY 2

    2. Decision: approved to create an error correction

    3. Responsible: @Philip Helger

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

    1. Information: add additional SETU document types to the codelist

    2. Decision: Approved with additional comments to the requestor.

    3. Responsible: @Philip Helger

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

    1. Information: Clarification on the Peppol AS4 profile on the usage of BinarySecurityToken

    2. Decision: No update

    3. Responsible: @Philip Helger

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

    1. Information: Peppol Reporting name change

    2. Update: Was presented in last SPC meeting - no comments received

    3. Responsible: @Philip Helger

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

    1. Information: added Participant Identifier Scheme 0234 to the eDEC CodeList

    2. Decision: 

    3. Responsible: @Philip Helger

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

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

    2. Update: 

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

    1. Information: Codelist alignment

    2. Update: none

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

    1. Information: Codelist alignment

    2. Update: none

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

    1. Information: internal activity: create AP Operational Guideline

    2. Update: none

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

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

    2. Update: none

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

    1. Suggestion on C4 Country Code

    2. Decision: Wait for full CMB group participation

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

    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 Business Cards.

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

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

    1. Update: Impact Analysis was provided

    2. Update: none

    3. Responsible: PH

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

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

    2. Update: none

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

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

    1. Information: Request to add Participant Identifier scheme 0218

    2. Update: Approved by eDEC CMB

    3. Responsible: @Philip Helger

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

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

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

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

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

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

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

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

    1. Information: New SMP API proposal (identify)

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

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

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

    1. Information: Clarify case sensitivity of Peppol Seat ID

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: Number of retries on an AS4 level

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    1. Information: Review of new/updated OASIS specifications

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

    1. Information: Allow 0080 as new Participant Identifier scheme

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

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

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

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

    2. Update: none

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

    1. Information: regarding joint information on news and noteworthy

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    1. Information: https for SMP

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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