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

Guests (without voting right)

Philip Helger (OpenPeppol OO)

Klaus Vilstrup (OpenPeppol OO)

Agenda

Open Tasks
New Tickets
Any other business

Approval of Minutes

eDelivery CMB meeting 2025-01-16 minutes

Status: approved

Information/Discussion items

Open Tasks
1. Code List alignment (not handled in this meeting)
2. eDEC Specifications (not handled in this meeting)
  1. Add that new specifications take effect at 00:00 UTC unless noted otherwise
3. Tasks in scope:
  1. TICC-355 - Getting issue details... STATUS Addition of Scheme 0225 for France
    1. Approved by eDEC CMB with comments (see the ticket for details)
  2. Review comments from "CNAME to NAPTR" public consultation
    1. Only one set of comments received. All suggestions were accepted and integrated into the specification documents.
    2. The final version of the specification documents are ready
    3. There will be a Migration Guideline, which is still work in progress
    4. As soon as the Migration Guideline is ready and approved, the publication will be started
  3. TICC-332 - Getting issue details... STATUS MLS
    1. The current work in progress version of the MLS was discussed
    2. Another meeting on Nov 20th will be held, to finalize the comments and get the MLS spec ready for public review
    3. Next steps
      1. Finalize the Documentation (it's not a BIS but an eDEC Specification)
      2. Get the Documentation approved by eDEC CMB
        Present release candidate for next eDEC CMB meeting on January 16th, 2025
      3. In parallel work on the supporting material like semantic model, syntax binding, code lists, rules and Schematrons
        No eDEC approval required but will be sent out for information
      4. Decide on the way forward how to introduce the MLS into the Peppol Network BEFORE the public review
      5. Package for public review
        MLS as a deployment on test-docs.peppol.eu
        Includes Documentation and supporting material
        SPIS specification Public Review Draft
      6. Run the public review
      7. Collect and resolve comments and get eDEC CMB approval on final version
      8. Publish version
Organisational topics (not handled in this meeting)
1. Peppol Conference on June 17th (Tue) and 18th (Wed), 2025 (Brussels)
  1. Prepare a technical track
  2. Two parallel tracks for two half days (Tue afternoon, Wed morning) - one technical, one other
    1. to be shared with PoAC
  3. Brainstorm for technical topics
    1. Information on current migrations
      1. PINT migration busdox/wildcard - incl. Q&A
      2. CNAME / NAPTR record changes in DNS - incl. Q&A
    2. WG updates
      1. CIWG update
      2. MLS
    3. Panel discussion on Security and resilience (speakers from different groups)
    4. Testbed
    5. ViDA / CTC / DCTCE - Architectural perspective
    6. eB2B and the consequences on Peppol specifications
    7. Peppol Directory???
  4. Brainstorm for business topics:
    1. Peppol France
News (not handled in this meeting)
1. News from the Peppol Network
  1. Public review for eDEC specification changes for SML operational improvements
    1. 2024.12.20 review for SML Operational Improvements
    2. Public Review period was extended by two weeks compared to the original proposal (until February 2nd)
2. Peppol - GENA consolidation
3. CIWG
4. Service Provider Identification Scheme (identify C2 and C3)
5. SMP 2.0 WG
  1. Paused until end of February
6. MLA work group (for MLS)
7. OO Internal Peppol Directory Initiative
Activities for this year (not handled in this meeting)
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
Next meeting(s)
1. Next meeting: Thursday February 20th 2025, 10:00 to 11:30 CET

New tasks and Issues (from last meeting)

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

Not updated and not handled in this meeting.

TICC-376 - Getting issue details... STATUS
1. Information: Add eB2B Document Types and Processes to the code lists
2. Decision: Approved by eDEC CMB on 30.1.2025
TICC-374 - Getting issue details... STATUS
1. Information: Deprecated and remove relevant PINT busdox Document Types in the code list
2. Decision: Approved by eDEC CMB on 30.1.2025
TICC-373 - Getting issue details... STATUS
1. Information: Add PINT AE Document Types to the code list
2. Decision: Approved by eDEC CMB on 30.1.2025
TICC-372 - Getting issue details... STATUS
1. Information: Add new Participant Identifier Scheme 0235 (TIN) to the code list
2. Decision: Approved by eDEC CMB on 30.1.2025
TICC-371 - Getting issue details... STATUS
1. Information: Add new Peppol France Document Types to the code list
2. Decision: Approved by eDEC CMB on 30.1.2025
TICC-370 - Getting issue details... STATUS
1. Information: Update reference style in Peppol AS4 specification
2. Decision: Agree to create an error correct of the AS4 specification to amend the reference links
TICC-369 - Getting issue details... STATUS
1. Information: Internal task to cleanup document type identifier code list based on Service Domain feedback
TICC-368 - Getting issue details... STATUS
1. Information: Internal task to define rules how to name code list entries issued by OpenPeppol
TICC-366 - Getting issue details... STATUS
1. Information: Change document type identifier code list names
2. Decision: rejected with a request for reconsideration
TICC-360 - Getting issue details... STATUS
1. Information: Request to add DICO MaintenanceStatus document to the code list.
2. Decision:
3. Responsible:
TICC-355 - Getting issue details... STATUS
1. Information: Request add 0225 Participant Identifier Scheme for France
2. Decision: approved with comments
TICC-354 - Getting issue details... STATUS
1. Information: Clarification on PFUOI length of participant identifiers is requested (Policy 1)
TICC-352 - Getting issue details... STATUS
1. Information: Error correction request in SMP specification
2. Decision:
3. Responsible:
TICC-351 - Getting issue details... STATUS
1. Information: Make identifier scheme mandatory in SBDH
2. Decision:
3. Responsible:
TICC-347 - Getting issue details... STATUS
1. Information: support for larger documents in the Peppol Network
2. Update: none
TICC-336 - Getting issue details... STATUS
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
TICC-332 - Getting issue details... STATUS
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
TICC-327 - Getting issue details... STATUS
1. Information: Error correction for Reporting Specification needed
2. Update: none
3. Responsible: Philip Helger
TICC-325 - Getting issue details... STATUS
1. Information: Create official clarification between the use of a Participant Identifier and a Legal Identifier
2. Update: none
3. Responsible: Philip Helger
TICC-323 - Getting issue details... STATUS
1. Information: Change Lower boundary of Business Entity within Business Card
2. Update: none
3. Responsible: Philip Helger
TICC-315 - Getting issue details... STATUS
1. Information: Peppol Reporting name change
2. Update: none
3. Responsible: Philip Helger
TICC-311 - Getting issue details... STATUS
1. Information: Use UTC for all Peppol publications date time
2. Update: none
TICC-310 - Getting issue details... STATUS
1. Information: Codelist alignment
2. Update: none
TICC-309 - Getting issue details... STATUS
1. Information: Codelist alignment
2. Update: none
TICC-308 - Getting issue details... STATUS
1. Information: internal activity: create AP Operational Guideline
2. Update: none
TICC-303 - Getting issue details... STATUS
1. Information: extract Business Card specification from Peppol Directory specification
2. Update: none
TICC-285 - Getting issue details... STATUS
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.
TICC-282 - Getting issue details... STATUS
1. Update: Deprecate old Business Card Formats
2. Update: none
3. Responsible: Philip Helger
TICC-269 - Getting issue details... STATUS
1. Information: Request to improve consistency in AS4 error handling
2. Update: none
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
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
TICC-233 - Getting issue details... STATUS
1. Information; Its about a wording issue in the Peppol Envelope Policy (SBDH)
2. Update: none
TICC-226 - Getting issue details... STATUS
1. Information: New SMP API proposal (migration code exchange)
TICC-225 - Getting issue details... STATUS
1. Information: New SMP API proposal (health check)
TICC-224 - Getting issue details... STATUS
1. Information: New SMP API proposal (identify)
2. Update: none
TICC-218 - Getting issue details... STATUS
1. Information: Clarify case sensitivity of Peppol Seat ID
2. Update: none
3. Responsible: Philip Helger
TICC-206 - Getting issue details... STATUS
1. Information: Number of retries on an AS4 level
2. Update: none
3. Responsible: Philip Helger
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
TICC-187 - Getting issue details... STATUS
1. Information: Allow 0080 as new Participant Identifier scheme
2. Update: none
3. Responsible:
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
TICC-168 - Getting issue details... STATUS
1. Information: Have a separate participant identifier prefix for testing purposes.
2. Update: none
TICC-167 - Getting issue details... STATUS
1. Information: regarding joint information on news and noteworthy
2. Update: none
3. Responsible: Philip Helger
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
TICC-153 - Getting issue details... STATUS
1. Information: https for SMP
2. Update: none
3. Responsible: Philip Helger
TICC-151 - Getting issue details... STATUS
1. Information: (Whitepaper) Enforce people to use SMK for testing?
2. Update: none
3. Responsible: Philip Helger
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
TICC-146 - Getting issue details... STATUS
1. Information: (Whitepaper) Creation of the Whitepaper.
2. Responsible: Philip Helger
TICC-142 - Getting issue details... STATUS
1. Information: (Whitepaper)
2. Responsible: Philip Helger
TICC-140 - Getting issue details... STATUS
1. Information: (Whitepaper)
2. Responsible: Philip Helger

Attachments

none

eDelivery Network (TICC) Coordinating Community

eDelivery CMB meeting 2025-02-13 minutes