Versions Compared

Old Version 1

changes.mady.by.user Philip Helger

Saved on

compared with

New Version Current

changes.mady.by.user Philip Helger

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Type of meeting: MS Teams

Participants and absents


Chair

Elly Stinchcombe (Unlicensed) as eDelivery Community Leader

...

Bård Langöy (Pagero)

Risto Collanus (Visma)

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

Arun Kumar Sharma (Basware)

...

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 2023-01-19 minutes

Status: Approved

New tasks and Issues

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

...

  1. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-246
    1. Information: update the SMP digest algorithms from SHA-1 to SHA-256
    2. Decision: CMB approves the change
    3. Responsible: Philip Helger
  2. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-245
    1. Information: Request to remove Deprecated XRechnung Document Type Identifiers
    2. Decision:Agreed
    3. Responsible: Philip Helger
  3. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-244
    1. Information: Add XRechnung 2.3 Extension Document Type Identifiers to the Peppol Code Lists
    2. Decision: Approved
    3. Responsible: Philip Helger:
  4. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-243
    1. Information: Add XRechnung 2.3 Document Type Identifiers to the Peppol Code Lists
    2. Decision: Approved
    3. Responsible: Philip Helger
  5. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-235
    1. Information: Start definining potential actions for removing identifiers in the Code List States Document. Start with TICC-228
    2. Responsible: Philip Helger
  6. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-234
    1. Information: RFC about Ppfuoi changes for PINT - making DDTS officially supported
    2. Update: none
    3. Responsible: Philip Helger
  7. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-233
    1. Information; Its about a wording issue in the Peppol Envelope Policy (SBDH)
    2. Update: none
    3. Responsible: Elly Stinchcombe (Unlicensed)
  8. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-232
    1. Information: Request to remove 9906 and 9907
    2. Update: Approved by CC29
    3. Responsible: Philip Helger
  9. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-229
    1. Information: Deprecation of 9955 identifier
    2. Update: Approved via email
    3. Responsible: Philip Helger
  10. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-228
    1. Information: Request to remove 9958
    2. Update: Approved by CC29
    3. Responisble: Elly Stinchcombe (Unlicensed)
  11. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-227
    1. Information: New Participant Identifier scheme 0221 for Japan
    2. Update: none
    3. Responsible: Elly Stinchcombe (Unlicensed)
  12. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-226
    1. Information: New SMP API proposal (migration code exchange)
  13. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-225
    1. Information: New SMP API proposal (health check)
  14. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-224
    1. Information: New SMP API proposal (identify)
  15. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-223
    1. Information: Collection issue: Peppol, EESPA, BPC
  16. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-218
    1. Information: Clarify case sensitivity of Peppol Seat ID
    2. Update: None
    3. Responsible: Philip Helger
  17. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-211
    1. Information: New Participant Identifier Scheme 0205
    2. Update: none.
    3. Responsible: Elly Stinchcombe (Unlicensed)
  18. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-206
    1. Information: Number of retries on an AS4 level
    2. Update: none
    3. Responsible: Philip Helger
  19. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-203
    1. Information: Please add SHA256 XMLsig to Peppol-SMP specs because Java17-security change
    2. Update: none
    3. Responsible: Philip Helger
  20. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-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. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-201
    1. Information: Review of new/updated OASIS specifications
    2. Update: none
    3. Responsible: Elly Stinchcombe (Unlicensed)
  22. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-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. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-187
    1. Information: Allow 0080 as new Participant Identifier scheme
    2. Update: None
    3. Responsible: Elly Stinchcombe (Unlicensed)
  24. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-184
    1. Information: Align Participant Identifier Scheme Code lists of PoAC and eDEC
    2. Update: none
    3. Responsible: Philip Helger
  25. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-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
  26. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-168
    1. Information: Have a separate participant identifier prefix for testing purposes.
    2. Update: none
  27. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-167
    1. Information: regarding joint information on news and noteworthy
    2. Update: none
    3. Responsible: Philip Helger
  28. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-166
    1. Information: Clarification on the words "custom validation" in the AS4 profile was sought.
    2. Update: none
    3. Responsible: Philip Helger
  29. Jira Legacy
    serverSystem JIRA
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-153
    1. Information: https for SMP
    2. Update: None
    3. Responsible: Philip Helger
  30. Jira Legacy
    serverSystem JIRA
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-151
    1. Information: (Whitepaper) Enforce people to use SMK for testing?
    2. Update: none
    3. Responsible: Philip Helger
  31. Jira Legacy
    serverSystem JIRA
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-149
    1. Information: add a Schematron for verifying the AS4 headers. Updates directly in the issue.
    2. Update: none
    3. Responsible: Philip Helger
  32. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-146
    1. Information: (Whitepaper) Creation of the Whitepaper.
    2. Responsible: Philip Helger
  33. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-142
    1. Information: (Whitepaper)
    2. Responsible: Philip Helger
  34. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-140
    1. Information: (Whitepaper)
    2. Responsible: Philip Helger
  35. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-98
    Information: Adding 0203 (SE) as a participant identifier scheme
    -
    the domain name like structure
  36. Update: none
  37. Responsible: not eDEC
    38. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-19
    1. Information: Information on how to determine and handle inactive SMP providers
    2. Update: none
    3. Responsible: Philip Helger

Information/Discussion items

  1. Next meeting 2023-02-16, 9:00 to 11:00 CET
  2. .AS2 removal - updates from CC29
    1. Approve Approved content of Confluence page?
    2. OK to start the process?
    3. Removal of transport profile code list identifiers (deprecated AS2 v2 first)
    4. ==> Start removal process
  3. SBDH 2.0 update
    1. No update
  4. Policy for use of Identifiers Update for DDTS
    1. No update
  5. SMP 2.0 Work group
    1. Progress Start off as SMP 2.0 as an eDEC internal work group instead?
  6. Removal of participant identifier schemes - updates from CC29
    1. 9906, 9907 and 9958 → will be removed
  7. Next MC++ Meeting next week
    1. How to handle grown up Peppol
    2. Input directly to be send to Elly
  8. Centralized Code List Management for PoAC and eDEC agreed
    1. Adding Participant Identier Schemes needs alignment between PoAC and eDEC
    2. eDEC will be in charge of the eDEC Participant Identifier Scheme code list that corresponds to the EAS Code List for PoAC BIS Billing
    3. The discrepancies between PoAC November 2022 release and latest eDEC Release 8.3.1 will be resolved between PoAC and eDEC immediately
  9. Clarify to Service Providers, that there is no date yet for mandatory Reporting (neither TSR nor EUSR)
    1. Last release info from https://peppol.eu/reporting-bis-release/ states "is expected to be operational in Q3 of 2023"
    2. Release is at least 6 month AFTER notification from OpenPeppol - this notification hasn't be send out yet
    3. Inform SPC on the status
  10. eDEC Updates to the Community
    1. No update yet

Attachments