Versions Compared

Key

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

Date: 2024-04-11

Time: 09:00-1110:00 45 CEST

Type of meeting: Teams

Participants and absents


Chair

Elly Stinchcombe (Unlicensed) as eDelivery Community Leader

...

Elected members (with voting right)

Bård Langöy (Pagero) (apologies received)

Risto Collanus (Visma)

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

...

Seong Wah (upcoming eDEC Leader)

Agenda

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

Approval of Minutes

eDelivery CMB meeting 2024-03-27

Status: ???approved

Information/Discussion items

  1.  Organisational topics 
      ...
    1. Today's Ellys last eDEC CMB meeting as eDEC leader; Seong listens in
    2. Next GA is next Tuesday, April 16th, 9:00 to 12:30 CEST
    3. eDEC CMB schedule overlaps with PAC meeting
      1. Next meeting stays on April 25th, 8:30 to 10:30 CEST - discuss the exact schedule for upcoming meetings; Klaus Vilstrup to send out invite
  2. News
    1. News from the Peppol Network
      1. ...The Finnish PA had a "Peppol Day" yesterday. Feature request: on eOrdering the "current stock" level is needed - a respective message is missing in PoAC
      2. Agenda for the Peppol Conference was sent out
        1. Participants from eDEC CMB: Seong, Klaus, Risto (28th, 6:15pm to 31st, 7pm), Iacopo? (remotely), Philip?, Bard?, Arun?
    2. Peppol - EESPA/GENA consolidation
      1. ...No real update. Prepare for Peppol Conference
    3. Service Provider Identification Scheme
      1. Finalize before next meeting. No external input received. No public review envisioned.
      2. Klaus Vilstrup and Philip Helger to finalize asap
    4. MLA work group (for MLS)
      1. ...Philip Helger to check with Simon on the status and provided materials
    5. Reporting
      1. ..Reporting moved from Development to Operations.
      2. To be removed from the recurring agenda.
    6. SMP 2.0.0
      1. ...Kick-Off meeting for the public Work Group was last Wedndesday
      2. Confluence space: PS2W
      3. Recurring meetings every second Wednesday from 9:00 to 10:00 CEST
    7. CIWG
      1. Initial meeting took place. 3 sub groups are in place
        1. Sub group A: short term activities on SML issue resolution
        2. Sub group B: technical / architectural team; first work meeting next Monday
        3. Sub group C: data sovereignity and business requirements; plan to have a paper in 6 weeks
      2. Additional participant from Australia: Mark Stockwell
    8. Internal Peppol Directory Initiative
      1. Not yet. To be started soon.
  3. Open Tasks Philip Helger
    1. Finalize TICC-19
      1. Updated for another round of review
      2. Please provide feedback until next CMB meeting so that it can be finalized
    2. Code List alignment
      1. 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, 98:00 30 to 1110:00 30 CEST

SPC relevant

...


  • CIWG + SMP 2.0 WG have been started
  • SMP 1.3.0 specification becomes mandatory by June 1st - switch from SHA-1 to SHA-256
  • Eventually: SP Identification Scheme

Netx pre-brief: Mon April 15th, 10:00am CEST (8:00am UTC)

Next SPC meeting: Tue April 23rd, 9:00am (7:00am UTC) to 10:15am CEST

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-327
    1. Information: Error correction for Reporting Specification needed
    2. Decision: Specification needs improvements. Details in the ticket.
    3. Responsible: Philip Helger
  2. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-326
    1. Information: Add new column to identify abstract document type identifiers
    2. Update: none
    3. Responsible: Philip Helger
  3. 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
  4. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-324
    1. Information: New profile for "Adviseringsmelding" (Customs Advice) in Norway
    2. Decision:  Postponed for internal clarification
    3. Responsible: Philip Helger
  5. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-323
    1. Information: Change Lower boundary of Business Entity within Business Card
    2. Decision:  Agreed to implement in next major version of Business Card format
    3. Responsible: Philip Helger
  6. 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
  7. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-319
    1. Information: add additional SETU document types to the codelist
    2. Update: Requires MC approval
    3. Responsible: Philip Helger
  8. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-316
    1. Information: Clarification on the Peppol AS4 profile on the usage of BinarySecurityToken
    2. Decision: No updatenone
    3. Responsible: Philip Helger
  9. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-315
    1. Information: Peppol Reporting name change
    2. Update: No update none
    3. Responsible: Philip Helger
  10. 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
  11. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-311
    1. Information: Use UTC for all Peppol publications date time
    2. Update: none
  12. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-310
    1. Information: Codelist alignment
    2. Update: none
  13. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-309
    1. Information: Codelist alignment
    2. Update: none
  14. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-308
    1. Information: internal activity: create AP Operational Guideline
    2. Update: none
  15. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-305
    1. Information: About certain points in the SBDH specification
    2. Update: none
  16. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-303
    1. Information: extract Business Card specification from Peppol Directory specification
    2. Update: none
  17. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-286

    1. Information: Suggestion on C4 Country Code
    2. Update: none
  18. 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.
  19. 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
  20. 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
  21. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-269
    1. Information: Request to improve consistency in AS4 error handling
    2. Update: none
  22. 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
  23. 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
  24. 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)
  25. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-226
    1. Information: New SMP API proposal (migration code exchange)
  26. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-225
    1. Information: New SMP API proposal (health check)
  27. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-224
    1. Information: New SMP API proposal (identify)
  28. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-223
    1. Information: Collection issue: Peppol, EESPA, BPC
  29. 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
  30. 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
  31. 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
  32. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-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)
  33. 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)
  34. 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
  35. 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
  36. 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
  37. 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
  38. Jira Legacy
    serverSystem JIRA
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-153
    1. Information: https for SMP
    2. Update: none - will be part Part of the SMP 2.0 specification update
    3. Responsible: Philip Helger
  39. 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
  40. 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
  41. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-146
    1. Information: (Whitepaper) Creation of the Whitepaper.
    2. Responsible: Philip Helger
  42. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-142
    1. Information: (Whitepaper)
    2. Responsible: Philip Helger
  43. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-140
    1. Information: (Whitepaper)
    2. Responsible: Philip Helger
  44. 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:  New draft version 0.7 circulated. For review until next eDEC CMB
    3. Responsible: Philip Helger

Attachments


none