/
eDelivery CMB meeting 2024-11-07 minutes

eDelivery CMB meeting 2024-11-07 minutes

Nov 07, 2024

Date: 2024-11-07

Time: 9:00-11:00 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) (apologies received)

 

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-08-01

Status: approved

Information/Discussion items

  1.  Organisational topics 

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

      1. Pain point in MLR: don't make it mandatory between C4 and C1, as ERP integration is a hassle

    7. OO Internal Peppol Directory Initiative

  3. Open Tasks @Philip Helger

    1. Code List alignment

    2. eDEC Specifications

      1. Add that new specifications take effect at 00:00 UTC unless noted otherwise

    3. At least these tasks need to be discussed today:

      1. https://openpeppol.atlassian.net/browse/TICC-361 SML Operational Issue - handled

      2. https://openpeppol.atlassian.net/browse/TICC-362 Codelist - handled

      3. https://openpeppol.atlassian.net/browse/TICC-359 Codelist - handled

      4. https://openpeppol.atlassian.net/browse/TICC-355 Codelist - handled

      5. https://openpeppol.atlassian.net/browse/TICC-348 Codelist - handled

      6. https://openpeppol.atlassian.net/browse/TICC-336 SPIS - handled

      7. https://openpeppol.atlassian.net/browse/TICC-300 Codelist - handled

      8. https://openpeppol.atlassian.net/browse/TICC-332 MLS - handled; focus in next session

  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. Next meeting: Thursday November 21st, 9:00 to 11:00 CET

SPC relevant

New tasks and Issues (from last meeting)

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

 

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

    1. Information: Request to add a new "Category" column in the Document Type Identifier Code List

    2. Decision: Approved by eDEC CMB.

    3. Responsible: @Philip Helger

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

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

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

    2. Decision:

    3. Responsible:

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

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

    1. Information: Request to add Participant Identifier scheme 0225 to the code list

    2. Decision: The request was rejected, as the character set of the Identifier scheme does not match the PFUOI

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

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

    2. Decision:

    3. Responsible:

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

    1. Information: Error correction request in SMP specification

    2. Decision:

    3. Responsible:

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

    1. Information: Make identifier scheme mandatory in SBDH

    2. Decision:

    3. Responsible:

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

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

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

    2. Update: none

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

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

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

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

    1. Information: Error correction for Reporting Specification needed

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

    1. Information: Peppol Reporting name change

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

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

    1. Information: Codelist alignment

    2. Update: none

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

    1. Information: Codelist alignment

    2. Update: none

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

    1. Information: internal activity: create AP Operational Guideline

    2. Update: none

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

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

    2. Update: none

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

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

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

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

    1. Update: Deprecate old Business Card Formats

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

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

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

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

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

    2. Update: none

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

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

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

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

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

    1. Information: New SMP API proposal (identify)

    2. Update: none

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

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

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

    1. Information: Clarify case sensitivity of Peppol Seat ID

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: Number of retries on an AS4 level

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    1. Information: Allow 0080 as new Participant Identifier scheme

    2. Update: none

    3. Responsible:

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

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

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

    2. Update: none

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

    1. Information: regarding joint information on news and noteworthy

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    1. Information: https for SMP

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

Attachments

 

none