/
eDelivery CMB meeting 2024-08-01 minutes

eDelivery CMB meeting 2024-08-01 minutes

Aug 01, 2024

Date: 2024-08-01

Time: 10:00-12:00 CEST

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

@Risto Collanus (Visma)

@Iacopo.Arduini@regione.emilia-romagna.it (Emilia Romagna)

@Arun Kumar Sharma (Basware)

 

Guests (without voting right)

@Philip Helger (OpenPeppol OO)

@Klaus Vilstrup (OpenPeppol OO)

Hayden Tay (IMDA) (apologies received)

Agenda

  1. Open Tasks

  2. New Tickets

  3. Any other business

Approval of Minutes

eDelivery CMB meeting 2024-07-18

Status: approved

Information/Discussion items

  1.  Organisational topics 

    1. eDEC Webinar to present recent updates in eDEC

      1. Proposed date and time:

        1. End of September/beginning of October

      2. Possible contents:

        1. Focus on information (90%), less interaction (10%)

        2. CIWG status

        3. SMP 2.0 status

        4. eDEC perspective on PINT

        5. Changes in 2024 so far

        6. Detailed plans for the near/medium future

        7. MLS status

        8. GENA incubation

        9. Peppol France?

        10. ...

      3. Detailed Planning on beginning of August

  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)

    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

  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 August 15st, 10:00 to 12:00 CEST

SPC relevant

  • Code List Update v8.9

  • Changes to Peppol Policy for use of Identifiers 4.3.0

  • Eventually: SP Identification Scheme

New tasks and Issues (from last meeting)

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

 

  1. https://openpeppol.atlassian.net/issues/TICC-349

    1. Information: Changes to the peppol-doctype-wildcard scheme to support exact matches

    2. Update: proposed changes to the specification were approved and will be send out to public review asap

    3. Responsible: @Philip Helger

  2. https://openpeppol.atlassian.net/issues/TICC-348

    1. Information: Request to add ICD code 0236 to eDEC Participant Identifier Scheme code list

    2. Updated: none

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

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

    2. Update: none

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

    1. Information: RFC to align receiver identification in SBDH and Payload; similar to TICC-330

  5. TICC-335 to TICC-341 are related to the new Enhanced B2B domain

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

    1. Information: Addition of Italy specific Invoice identifiers

    2. Update: none

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

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

    1. Information: Mandatory use of same identifier in recipient field of SBDH and endpointID in document; relates to TICC-344

    2. Update: none

    3. Responsible:

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

    1. Information: Error correction for Reporting Specification needed

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

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

    2. Update: This will be part of the Peppol Policy for use of Identifier 4.3.0

    3. Responsible: @Philip Helger

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

    1. Information: Peppol Reporting name change

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Decision: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

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

    1. Information: Codelist alignment

    2. Update: none

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

    1. Information: Codelist alignment

    2. Update: none

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

    1. Information: internal activity: create AP Operational Guideline

    2. Update: none

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

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

    2. Update: none

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

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

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

    1. Update: Deprecate old Business Card Formats

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: none

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

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

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

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

    2. Update: none

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

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

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

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

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

    1. Information: New SMP API proposal (identify)

    2. Update: none

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

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

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

    1. Information: Clarify case sensitivity of Peppol Seat ID

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: Number of retries on an AS4 level

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    1. Information: Allow 0080 as new Participant Identifier scheme

    2. Update: none

    3. Responsible:

  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

Attachments

 

none