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.

...

Time: 10:00-11:00 CEST

Type of meeting: Teams

Participants and absents


Chair

GEOK_Seong_Wah@imda.gov.sg as eDelivery Community Leader

...

Hayden Tay (IMDA) (apologies received)

Agenda

  1. News from the Peppol Network
  2. Open Tasks
  3. New Tickets
  4. Other

Approval of Minutes

eDelivery CMB meeting 2024-04-25

Status: approved

Information/Discussion items

  1.  Organisational topics 
  2. News
    1. News from the Peppol Network
      1. PoAC is planning a new BIS "Billing with Invoice Response" as well as "PINT Self Billing"
      2. PoAC is working on harmonizing the time zone management inside their documents types (UTC, time zone provision etc.); that also affects the putting in use of new specifications and validation artefacts
    2. Peppol - EESPA/GENA consolidation
    3. CIWG
    4. Service Provider Identification Scheme (identify C2 and C3)
    5. SMP 2.0 WG
    6. MLA work group (for MLS)
      1. Philip to circulate the work group draft document to eDEC CMB for reading and further discussion in the next eDEC CMB
    7. OO Internal Peppol Directory Initiative
  3. Open Tasks Philip Helger
    1. Finalize TICC-19
      1. Version 2024-04-10 was accepted as version 1.0. Ticket to be closed
    2. Code List alignment
    3. 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. Changes to eDEC internal guidelines
    1. The guideline on "Code List States" was modified. A "Document Type Identifier Code List entry" must be at least 3 month in state "Deprecated" before it can be in state "Removed".
  6. Next meeting(s)
    1. Next meeting: Thursday July 4th, 10:00 to 12:00 CEST

SPC relevant

  • Code List Update v8.9
  • Eventually: SP Identification Scheme

New tasks and Issues (from last meeting)

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

...

  1. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-345
    1. Information: request to remove Participant Identifier schemes 0037, 0212, 0213, 0215
    2. Decision: none yet
  2. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-343
    1. Information: remove Japan busdox document type identifiers from Code Lists
    2. Decision: Approved by eDEC CMB with a specific supporting activity described in the ticket
    3. Responsible: Philip Helger
  3. TICC-335 to TICC-341 are related to the new Enhanced B2B domain
  4. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-333
    1. Information: Addition of Italy specific Invoice identifiers
    2. Update: this is extended use and requires prior MC approval
  5. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-332
    1. Information: RFC to convert the output of the MLA work group (the Message Level Status) into an eDEC specification
    2. Update: Information to be circulated to the group; will be discussed in next eDEC CMB meeting
  6. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-331
    1. Information: Add new document types for Norwegian "INNBYGGERPOST"
    2. Decision: approved by F2F eDEC CMB. Will be part of Code Lists v8.9
    3. Reponsible Philip Helger
  7. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-330
    1. Information: Mandatory use of same identifier in recipient field of SBDH and endpointID in document
    2. Update: none
    3. Responsible:
  8. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-327
    1. Information: Error correction for Reporting Specification needed
    2. Update: none
    3. Responsible: Philip Helger
  9. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-325
    1. Information: Create official clarification between the use of a Participant Identifier and a Legal Identifier
    2. Update: none
    3. Responsible: Philip Helger
  10. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-323
    1. Information: Change Lower boundary of Business Entity within Business Card
    2. Update: none
    3. Responsible: Philip Helger
  11. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-322
    1. Information: Ambiguity of Participant Identifier Casing between POLICY 1 and POLICY 2
    2. Update: none
    3. Responsible: Philip Helger
  12. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-319
    1. Information: add additional SETU document types to the codelist
    2. Update: Part of the v8.9 code list releases
    3. Responsible: Philip Helger
  13. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-315
    1. Information: Peppol Reporting name change
    2. Update: none
    3. Responsible: Philip Helger
  14. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-313
    1. Information: added Participant Identifier Scheme 0234 to the eDEC CodeList
    2. Decision: none
    3. Responsible: Philip Helger
  15. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-311
    1. Information: Use UTC for all Peppol publications date time
    2. Update: none
  16. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-310
    1. Information: Codelist alignment
    2. Update: none
  17. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-309
    1. Information: Codelist alignment
    2. Update: none
  18. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-308
    1. Information: internal activity: create AP Operational Guideline
    2. Update: none
  19. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-303
    1. Information: extract Business Card specification from Peppol Directory specification
    2. Update: none
  20. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-286

    1. Information: Suggestion on C4 Country Code
    2. Update: none
  21. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-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.
  22. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-284
    1. Information: AS4 inconclusive specification on signing of AS4 Error messages
    2. Update: none
    3. Responsible: Philip Helger
  23. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-282
    1. Update: Deprecate old Business Card Formats
    2. Update: none
    3. Responsible: Philip Helger
  24. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-269
    1. Information: Request to improve consistency in AS4 error handling
    2. Update: none
  25. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-263
    1. Information: Peppol Participant (Corner 4) served by more than one Access Point
    2. Update: none
    3. Responsible: Philip Helger
  26. 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. Update: none
    3. Responsible: Philip Helger
  27. 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
  28. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-226
    1. Information: New SMP API proposal (migration code exchange)
  29. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-225
    1. Information: New SMP API proposal (health check)
  30. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-224
    1. Information: New SMP API proposal (identify)
  31. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-223
    1. Information: Collection issue: Peppol, EESPA, BPC
  32. 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
  33. 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
  34. 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
  35. 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)
  36. 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
  37. 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
  38. 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
  39. 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
  40. Jira Legacy
    serverSystem JIRA
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-153
    1. Information: https for SMP
    2. Update: Part of the SMP 2.0 specification update
    3. Responsible: Philip Helger
  41. 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
  42. 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
  43. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-146
    1. Information: (Whitepaper) Creation of the Whitepaper.
    2. Responsible: Philip Helger
  44. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-142
    1. Information: (Whitepaper)
    2. Responsible: Philip Helger
  45. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-140
    1. Information: (Whitepaper)
    2. Responsible: Philip Helger
  46. 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: The version was accepted. The issue will be closed.
    3. Responsible: Philip Helger

Attachments


none