/
eDelivery CMB meeting 2022-12-08 minutes

eDelivery CMB meeting 2022-12-08 minutes

Dec 08, 2022

Date: 2022-12-08

Time: 09:00-10:00 CET

Type of meeting: MS 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) (excuses received)

@Arun Kumar Sharma (Basware)

 

Guests (without voting right)

@Philip Helger (OpenPeppol OO)

Agenda

  1. Approval of minutes

  2. New tasks and Issues

  3. Actions

  4. Information items

  5. Input from email

Approval of Minutes

eDelivery CMB meeting 2022-11-24 minutes

Status: Approved

New tasks and Issues

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

 

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

    1. Information: Deprecate Document Type Identifiers for XRechnung 1.2 as originally requested in TICC-117

    2. Decision: Agreed to deprecate them

    3. Responsible: @Philip Helger

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

    1. Information: Deprecate Participant Identifier Scheme 9908

    2. Decision: Agreed to deprecate in favour of 0192

    3. Responsible: @Philip Helger

  3. 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. Responsible: @Philip Helger

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

    1. Information: RFC about Ppfuoi changes for PINT - making DDTS officially supported

    2. Decision: To be put on the agenda of the next CC

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

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

    2. Decision: To be put on the agenda of the next CC

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

    1. Information: Request to remove 9906 and 9907

    2. Update: None

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

    1. Information: Add support for EAS code 9959

    2. Update: Agreed, because request came from CC.

    3. Responisble: @Philip Helger

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

    1. Information: Deprecation of 9955 identifier

    2. Update: Not handled

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

    1. Information: Request to remove 9958

    2. Decision: Okay to proceed.

    3. Responisble: @Elly Stinchcombe (Unlicensed)

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

    1. Information: New Participant Identifier scheme 0221 for Japan

    2. Decision: Not yet in EAS code list. To be discussed.

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

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

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

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

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

    1. Information: New SMP API proposal (identify)

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

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

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

    1. Information: New document types for advanced ordering

    2. Decision: We have to wait until the BIS is published - then its okay to add the identifiers immediately.

    3. Responsible: @Philip Helger

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

    1. Information: Clarify case sensitivity of Peppol Seat ID

    2. Decision: None

    3. Responsible: @Philip Helger

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

    1. Information: New Participant Identifier Scheme 0205

    2. Update: To be put on the agenda of the next CC.

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

    1. Information: Number of retries on an AS4 level

    2. Update: none

    3. Responsible: @Philip Helger

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

    1. Information: Please add SHA256 XMLsig to Peppol-SMP specs because Java17-security change

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    1. Information: Review of new/updated OASIS specifications

    2. Update: none

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

    1. Information: how to effectivly apply the new state "removed" for code list entries. This is a subtask of TICC-184.

    2. Update: None

    3. Responsible: @Elly Stinchcombe (Unlicensed) / @Philip Helger

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

    1. Information: Italian identifier scheme (PEC) - email address (REM)

    2. Update: Discussed in CC28. On hold until a strategic decision is made.

    3. Responsible: not eDEC

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

    1. Information: Allow 0080 as new Participant Identifier scheme

    2. Update: None

    3. Responsible: @Elly Stinchcombe (Unlicensed)

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

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

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

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

    2. Update: none

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

    1. Information: regarding joint information on news and noteworthy

    2. Update: none

    3. Responsible: @Philip Helger

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

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

    1. Information: https for SMP

    2. Update: None

    3. Responsible: @Philip Helger

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

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

    2. Update: none

    3. Responsible: @Philip Helger

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

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

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

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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

    1. Information: (Whitepaper)

    2. Responsible: @Philip Helger

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

    1. Information: Adding 0203 (SE) as a participant identifier scheme - the domain name like structure

    2. Update: Discussed in CC28. On hold until a strategic decision is made.

    3. Responsible: not eDEC

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

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

    2. Update: Document to be finalized and spread.

    3. Responsible: @Philip Helger

Other:

  • SMP 2.0 Work Group Mandate 0.3 was distributed to CMB members

    • eDEC CMB to review the document until Wed December 15th eob (Australian time - 9:00 CET)

    • Afterwards Elly to follow up on the process

  • AS2 removal status

    • discussed in CC27

    • RFC from OO to eDEC needed

    • Fact finding for the use of AS2 in the UK by OO

Information/Discussion items

  1. Next meeting 2023-01-05, 9:00 to 11:00 CET

  2. Next CC meeting supposed to be on January 26th, 2023

Attachments