/
eDelivery CMB meeting 2024-04-25 minutes

eDelivery CMB meeting 2024-04-25 minutes

Apr 25, 2024

Date: 2024-04-25

Time: 08:30-10:30 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)

@Risto Collanus (Visma)

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

@Arun Kumar Sharma (Basware)

 

Guests (without voting right)

@Philip Helger (OpenPeppol OO)

@Klaus Vilstrup (OpenPeppol OO)

Hayden Tay (IMDA)

Agenda

  1. News from the Peppol Network

  2. Open Tasks

  3. New Tickets

  4. Other

Approval of Minutes

eDelivery CMB meeting 2024-04-11

Status: approved

Information/Discussion items

  1.  Organisational topics 

    1. Discuss the exact schedule for upcoming meetings

      1. Seong to schedule eDEC CMB meetings in Teams (Currently: UTC 6:30 CEST 8:30 SG: 14:30)

      2. Proposed time: every second Thursday UTC 8:00, CEST 10:00, SG: 16:00 - starting from May 23th 2024

        1. May 9th is a public holiday in many European Countries

    2. General Assembly April 16th

      1. Request for a separate open eDEC meeting similar to eDEC meeting

        1. There are currently no plans to establish a separate eDEC public meeting and being part of the SPC meetings has been proven very valuable as the number of SPC participants is very high

        2. It needs to be ensured, that the solution providers are invited to the SPC meetings

        3. Topic related meetings are scheduled on demand - scheduled at least one month ahead of time

        4. Tentative meeting on general eDEC updates in end of September - eDEC Forums - start with a trial version and see how it evolves

  2. News

    1. News from the Peppol Network

      1. Peppol Conference 2024

        1. Conference: Wed 29th, Thu 30th;

        2. CIWG Meeting: Fri 31st 9:00 to 13:00 CEST

        3. PA Meeting: Fri 31st

        4. Participants from eDEC CMB: Seong, Klaus (27th evening to 31st), Risto (28th, 6:15pm to 31st, 7pm), Iacopo? (remotely), Philip?, Bard (no), Arun (most likely)

        5. Tentative eDEC CMB F2F: late afternoon/evening on Thu 30th - as a hybrid solution; @Philip Helger to check with Mairi on the location details

    2. Peppol - EESPA/GENA consolidation

      1. Architecurally alignment with Peppol France (formerly known as French PoC)

        1. Separation of domains

      2. Moving towards an incubation architecture

        1. Alignment on interoperability requirements, payload types, technical components

      3. Hopefully results can be presented at the Peppol Conference

    3. CIWG

      1. WG C started working - focus on (PA) data sovereignity

      2. WG B - initial presentations done - narrow to 3 big pictures

      3. WG A hasn't really started yet - depending on external inputs

    4. Service Provider Identification Scheme (identify C2 and C3)

      1. Finalized alignment with GENA

      2. PH to cleanup the document and share with this group for informational purposes

    5. SMP 2.0 WG

      1. Regular meetings scheduled - work in progress

      2. Same End User services by multiple Service Providers is out of scope here; eventually considered in CWIG-C

    6. MLA work group (for MLS)

      1. No update - @Philip Helger to check with Simon

    7. OO Internal Peppol Directory Initiative

      1. Initial meeting - no plan, no scope etc. yet

  3. Open Tasks @Philip Helger

    1. Finalize TICC-19

      1. Please provide feedback until next CMB meeting so that it can be finalized

    2. Code List alignment

      1. Todo New dependency: Participant Identifier Scheme descriptions may be linked to PoAC validation rules

  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 April 25th, 8:30 to 10:30 CEST

SPC relevant

  • 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-330

    1. Information: Mandatory use of same identifier in recipient field of SBDH and endpointID in document

    2. Decision:

    3. Responsible:

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

    1. Information: Change the description of what is allowed in distinct content in PINT

    2. Decision:

    3. Responsible: 

  3. https://openpeppol.atlassian.net/issues/TICC-328

    1. Information: Malaysian PINT DocTypes with busdox-docid-qns

    2. Update: Done. Part of eDEC Code List v8.8 release.

    3. Responsible: @Philip Helger

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

    1. Information: Error correction for Reporting Specification needed

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: Done. Part of the eDEC Code List v8.8 release

    3. Responsible: @Philip Helger

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

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

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

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

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    2. Update: MC approval is present

    3. Responsible: @Philip Helger

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

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

    2. Decision: Done. Part of the AS4 profile v2.0.3 release.

    3. Responsible: @Philip Helger

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

    1. Information: Peppol Reporting name change

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

    2. Update: none

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

    1. Information: Codelist alignment

    2. Update: none

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

    1. Information: Codelist alignment

    2. Update: none

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

    1. Information: internal activity: create AP Operational Guideline

    2. Update: none

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

    1. Information: About certain points in the SBDH specification

    2. Update: none

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

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

    2. Update: none

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

    1. Information: Suggestion on C4 Country Code

    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

    3. Responsible: @Elly Stinchcombe (Unlicensed)

  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)

  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-201

    1. Information: Review of new/updated OASIS specifications

    2. Update: Part of the SMP 2.0 and CIWG WGs. Closed.

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

    1. Information: Allow 0080 as new Participant Identifier scheme

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

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

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

    2. Update: none

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

    1. Information: regarding joint information on news and noteworthy

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    1. Information: https for SMP

    2. Update: Part of the SMP 2.0 specification update

    3. Responsible: @Philip Helger

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

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

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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

    1. Information: Information on how to determine and handle inactive SMP providers

    2. Update: New draft version 0.7 circulated. For review until next eDEC CMB

    3. Responsible: @Philip Helger

Attachments

 

none