Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Date: 2024-11-07

Time: 9:00-11:00 CET

Type of meeting: Teams

Participants and absents


Chair

GEOK_Seong_Wah@imda.gov.sg 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)

Arun Kumar (Basware) (apologies received)


Guests (without voting right)

Philip Helger (OpenPeppol OO)

Klaus Vilstrup (OpenPeppol OO)

Agenda

  1. Open Tasks
  2. New Tickets
  3. Any other business

Approval of Minutes

eDelivery CMB meeting 2024-08-01

Status: approved

Information/Discussion items

  1.  Organisational topics 
  2. News
    1. News from the Peppol Network
    2. Peppol - GENA consolidation
    3. CIWG
    4. Service Provider Identification Scheme (identify C2 and C3)
    5. SMP 2.0 WG
    6. MLA work group (for MLS)
    7. OO Internal Peppol Directory Initiative
  3. Open Tasks Philip Helger
    1. Code List alignment
    2. eDEC Specifications
      1. Add that new specifications take effect at 00:00 UTC unless noted otherwise
    3. At least these tasks need to be discussed today:
      1. TICC-361 - Getting issue details... STATUS
      2. TICC-362 - Getting issue details... STATUS
      3. TICC-359 - Getting issue details... STATUS
      4. TICC-355 - Getting issue details... STATUS
      5. TICC-348 - Getting issue details... STATUS
      6. TICC-336 - Getting issue details... STATUS
      7. TICC-300 - Getting issue details... STATUS
  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 November 21st, 9:00 to 11:00 CET

SPC relevant

New tasks and Issues (from last meeting)

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


  1. TICC-362 - Getting issue details... STATUS
    1. Information: Request to add a new "Category" column in the Document Type Identifier Code List
    2. Decision:
    3. Responsible: 
  2. TICC-361 - Getting issue details... STATUS
    1. Information: Request to use NAPTR record lookup instead of CNAME lookup
    2. Decision:
    3. Responsible:
  3. TICC-360 - Getting issue details... STATUS
    1. Information: Request to add DICO MaintenanceStatus document to the code list.
    2. Decision:
    3. Responsible:
  4. TICC-359 - Getting issue details... STATUS
    1. Information: Request to add BIS Self Billing to the Code List
    2. Decision:
    3. Responsible: 
  5. TICC-355 - Getting issue details... STATUS
    1. Information: Request to add Participant Identifier scheme 0225 to the code list
    2. Decision:
    3. Responsible:
  6. TICC-354 - Getting issue details... STATUS
    1. Information: Clarification on PFUOI length of participant identifiers is requested (Policy 1)
    2. Decision:
    3. Responsible:
  7. TICC-352 - Getting issue details... STATUS
    1. Information: Error correction request in SMP specification
    2. Decision:
    3. Responsible:
  8. TICC-351 - Getting issue details... STATUS
    1. Information: Make identifier scheme mandatory in SBDH
    2. Decision:
    3. Responsible:
  9. TICC-348 - Getting issue details... STATUS
    1. Information: Request to add ICD code 0236 to eDEC Participant Identifier Scheme code list
    2. Updated: none
  10. TICC-347 - Getting issue details... STATUS
    1. Information: support for larger documents in the Peppol Network
    2. Update: none
  11. TICC-337 to TICC-341 are related to the new Enhanced B2B domain
  12. TICC-336 - Getting issue details... STATUS
    1. Information: Create a Service Provider Identification Scheme
    2. Update: 1.0.0-RC2 available
  13. TICC-332 - Getting issue details... STATUS
    1. Information: RFC to convert the output of the MLA work group (the Message Level Status, MLS) into an eDEC specification
    2. Update: none
  14. TICC-327 - Getting issue details... STATUS
    1. Information: Error correction for Reporting Specification needed
    2. Update: none
    3. Responsible: Philip Helger
  15. TICC-325 - Getting issue details... STATUS
    1. Information: Create official clarification between the use of a Participant Identifier and a Legal Identifier
    2. Update: none
    3. Responsible: Philip Helger
  16. TICC-323 - Getting issue details... STATUS
    1. Information: Change Lower boundary of Business Entity within Business Card
    2. Update: none
    3. Responsible: Philip Helger
  17. TICC-315 - Getting issue details... STATUS
    1. Information: Peppol Reporting name change
    2. Update: none
    3. Responsible: Philip Helger
  18. TICC-311 - Getting issue details... STATUS
    1. Information: Use UTC for all Peppol publications date time
    2. Update: none
  19. TICC-310 - Getting issue details... STATUS
    1. Information: Codelist alignment
    2. Update: none
  20. TICC-309 - Getting issue details... STATUS
    1. Information: Codelist alignment
    2. Update: none
  21. TICC-308 - Getting issue details... STATUS
    1. Information: internal activity: create AP Operational Guideline
    2. Update: none
  22. TICC-303 - Getting issue details... STATUS
    1. Information: extract Business Card specification from Peppol Directory specification
    2. Update: none
  23. TICC-300 - Getting issue details... STATUS
    1. Information: Request to add new document types
    2. Decision:
    3. Responsible: 
  24. TICC-285 - Getting issue details... STATUS
    1. Information: 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.
  25. TICC-284 - Getting issue details... STATUS
    1. Information: AS4 inconclusive specification on signing of AS4 Error messages
    2. Update: none
    3. Responsible: Philip Helger
  26. TICC-282 - Getting issue details... STATUS
    1. Update: Deprecate old Business Card Formats
    2. Update: none
    3. Responsible: Philip Helger
  27. TICC-269 - Getting issue details... STATUS
    1. Information: Request to improve consistency in AS4 error handling
    2. Update: none
  28. TICC-263 - Getting issue details... STATUS
    1. Information: Peppol Participant (Corner 4) served by more than one Access Point
    2. Update: none
    3. Responsible: Philip Helger
  29. TICC-235 - Getting issue details... STATUS
    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
  30. TICC-233 - Getting issue details... STATUS
    1. Information; Its about a wording issue in the Peppol Envelope Policy (SBDH)
    2. Update: none
  31. TICC-226 - Getting issue details... STATUS
    1. Information: New SMP API proposal (migration code exchange)
  32. TICC-225 - Getting issue details... STATUS
    1. Information: New SMP API proposal (health check)
  33. TICC-224 - Getting issue details... STATUS
    1. Information: New SMP API proposal (identify)
    2. Update: none
  34. TICC-223 - Getting issue details... STATUS
    1. Information: Collection issue: Peppol, EESPA, BPC
  35. TICC-218 - Getting issue details... STATUS
    1. Information: Clarify case sensitivity of Peppol Seat ID
    2. Update: none
    3. Responsible: Philip Helger
  36. TICC-206 - Getting issue details... STATUS
    1. Information: Number of retries on an AS4 level
    2. Update: none
    3. Responsible: Philip Helger
  37. TICC-202 - Getting issue details... STATUS
    1. Information: Information about caching of SMP results for usage in a Peppol AP is missing
    2. Update: none
    3. Responsible: Philip Helger
  38. TICC-187 - Getting issue details... STATUS
    1. Information: Allow 0080 as new Participant Identifier scheme
    2. Update: none
    3. Responsible:
  39. TICC-174 - Getting issue details... STATUS
    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
  40. TICC-168 - Getting issue details... STATUS
    1. Information: Have a separate participant identifier prefix for testing purposes.
    2. Update: none
  41. TICC-167 - Getting issue details... STATUS
    1. Information: regarding joint information on news and noteworthy
    2. Update: none
    3. Responsible: Philip Helger
  42. TICC-166 - Getting issue details... STATUS
    1. Information: Clarification on the words "custom validation" in the AS4 profile was sought.
    2. Update: none
    3. Responsible: Philip Helger
  43. TICC-153 - Getting issue details... STATUS
    1. Information: https for SMP
    2. Update: none
    3. Responsible: Philip Helger
  44. TICC-151 - Getting issue details... STATUS
    1. Information: (Whitepaper) Enforce people to use SMK for testing?
    2. Update: none
    3. Responsible: Philip Helger
  45. TICC-149 - Getting issue details... STATUS
    1. Information: add a Schematron for verifying the AS4 headers. Updates directly in the issue.
    2. Update: none
    3. Responsible: Philip Helger
  46. TICC-146 - Getting issue details... STATUS
    1. Information: (Whitepaper) Creation of the Whitepaper.
    2. Responsible: Philip Helger
  47. TICC-142 - Getting issue details... STATUS
    1. Information: (Whitepaper)
    2. Responsible: Philip Helger
  48. TICC-140 - Getting issue details... STATUS
    1. Information: (Whitepaper)
    2. Responsible: Philip Helger

Attachments


none

  • No labels