Versions Compared

Old Version 1

changes.mady.by.user Klaus Vilstrup

Saved on

compared with

New Version Current

changes.mady.by.user Klaus Vilstrup

Saved on

Key

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

...

Time: 09:00-11:00 CEST

Type of meeting: MS Teams

Participants and absents


Chair

Elly Stinchcombe (Unlicensed) as eDelivery Community Leader

...

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

Arun Kumar Sharma (Basware) (apologies received)


Guests (without voting right)

...

Klaus Vilstrup (OpenPeppol OO)

Agenda

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

Approval of Minutes

eDelivery CMB meeting 2023-08-31

Status: approved

Information/Discussion items

  1. Organisational topics
    1. Moving October 26h 26th eDEC CMB meeting
      1. Moving it to Monday October 23rd, same timeslot
      2. Apologies from Klaus noted
    2. Daylight savings
      1. Europe: October 29th from CEST to CET (+2 to +1)
      2. No daylight savings in Brisbane (+9)
      3. Proposal to start the meetings from November 2023 to May 2024 half an hour earlier (8:30 am CET, 9:30 am EET, 5:30 pm AEST)
      Last CC meeting was on Monday September 11th - see /wiki/spaces/CCS/pages/996835424
      2. Information sharing across all communities
      3. Rotating chair was rejected - OO does it
      4. Think on the operational plan for 2024
      5. eDEC Resource problem was mentioned again
      6. Not all eDEC CMB members have access to the CC Confluence space yet
  2.  News
    1. News from the Peppol network
      1. On September 19th, 9:00 to 10:00 CEST a Reporting Webinar will take place - 2nd webinar on EUSR 1.1 update - same that was presented in July
      2. On September 26th, 10:30 to 11:30 CEST an MLS work group meeting takes placeSPC meeting: MLR, SMP 1.3.0
      3. Danish Nemhandel update by Risto Collanus and Arun Kumar Sharma
    2. Reporting
      1. Beta testing for Peppol Reporting for SP started (6 SP already joined), beta testing for PAs will start a bit later
    3. MLS work group
      1. MLS will have impact on Reporting specification
        1. MLS messages should be counted in TSR; country code handling needs to be figured out
        2. MLS messages should not be counted in EUSR, because they are not End User related messages
      2. Current MLS work group status would also foresee SBDH changes - no final decision made yetNo news
    4. Peppol - EESPA consolidation
      1. Ongoing work
  3. Open Tasks Philip Helger
    1. SMP 1.3.0 Update (Main document changes were done)
      1. Get it out for review asap - without the statement on Directory API being mandatory
      2. Create a migration plan for SMP 1.3.0 specification (gradual implementation on SMP side should work, no big bang)
      3. Provide a plan how to monitor SMP 1.3.0 implementation progress (based on Peppol Analytics)
      4. Collect comments
      5. Publish final version
      6. Discussion on Directory API is postponed
    2. PPFUOI 4.2.0
      1. Create an impact analysis on PPFUOI 4.2.0
    3. Finalize TICC-19
      1. Add hint on upcoming SMP 2.0 specification
  4. Activities for this year
    1. 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 
    2. Resource problem is still pressing
    3. 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
    4. 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
    1. Thursday September 28October 12th, 9:00 to 11:00 CEST (might be changed or cancelled)

SPC relevant

  • Next SPC meeting: 2023-09-26, 9:00 to 10:30 CEST
  • eDEC will take responsibility for the MLS specification/BIS
  • SMP 1.3.0 update
  • #

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-297
    1. -
    2. Decision: Accepted
  2. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-296
    1. -
    2. Decision: Accepted
  3. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-295
    1. -
    2. Decision: Minor change and accepted
  4. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-292
    1. Fix removal date of 9956 in a hotfix release to 2024-01-01
    2. Decision: Agreed to be changed
  5. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-291
    1. Addition of XRechnung 3.0 CIUS Document Types to the code list, if the additional to the National Rules in BIS Billing fails
    2. Decisiion: Agreed to be added, if the rules don't make it in the POAC November 2023 release
  6. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-290
    1. Addition of XRechnung 3.0 Extension Document Types to the code list
    2. Decision: Agreed to be added
  7. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-286

    1. Suggestion on C4 Country Code
    2. Decision: wait for Arun to be here to discuss itWait for full CMB group participation
  8. 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. Decision: Further discussion is necessaryHandling: divide it in two: a policy issue and how Business Card is presented in the Reporting Guideline. 
    3. Decision: OO to clarify on the mandatory use of Businees Cards.
  9. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-284
    1. Information: AS4 inconclusive specification on signing of AS4 Error messages
    2. Decision: AS4 Error Messages should be signed. A way forward was sketched
    3. Responsible: Elly Stinchcombe (Unlicensed)
  10. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-282
    1. Information: Deprecate Business Card formats v1 and v2 and requrest to support only v3
    2. Decision: RFC accepted
    3. Responsible: PH
  11. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-269
    1. Information: Request to improve consistency in AS4 error handling
    2. Update: none
  12. 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
  13. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-259
    1. Information: Request to add Participant Identifier scheme 0218
    2. Update: none
    3. Responsible: Philip Helger
  14. 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. Update: none
    3. Responsible: Philip Helger
  15. 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
  16. 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)
  17. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-226
    1. Information: New SMP API proposal (migration code exchange)
  18. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-225
    1. Information: New SMP API proposal (health check)
  19. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-224
    1. Information: New SMP API proposal (identify)
  20. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-223
    1. Information: Collection issue: Peppol, EESPA, BPC
  21. 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
  22. 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
  23. 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
  24. 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
  25. 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)
  26. 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)
  27. 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
  28. 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
  29. 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
  30. 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
  31. 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
  32. Jira Legacy
    serverSystem JIRA
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-153
    1. Information: https for SMP
    2. Update: none
    3. Responsible: Philip Helger
  33. 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
  34. 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
  35. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-146
    1. Information: (Whitepaper) Creation of the Whitepaper.
    2. Responsible: Philip Helger
  36. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-142
    1. Information: (Whitepaper)
    2. Responsible: Philip Helger
  37. Jira Legacy
    serverSystem Jira
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-140
    1. Information: (Whitepaper)
    2. Responsible: Philip Helger
  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: work in progress
    3. Responsible: Philip Helger

Attachments


none