...
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
- News from the Peppol Network
- Open Tasks
- New Tickets
- Other
Approval of Minutes
eDelivery CMB meeting 2024-04-25
Status: approved
Information/Discussion items
- Organisational topics
- News
- News from the Peppol Network
- PoAC is planning a new BIS "Billing with Invoice Response" as well as "PINT Self Billing"
- 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
- Peppol - EESPA/GENA consolidation
- CIWG
- Service Provider Identification Scheme (identify C2 and C3)
- SMP 2.0 WG
- MLA work group (for MLS)
- Philip to circulate the work group draft document to eDEC CMB for reading and further discussion in the next eDEC CMB
- OO Internal Peppol Directory Initiative
- News from the Peppol Network
- Open Tasks Philip Helger
- Finalize TICC-19
- Version 2024-04-10 was accepted as version 1.0. Ticket to be closed
- Code List alignment
- eDEC Specifications
- Add that new specifications take effect at 00:00 UTC unless noted otherwise
- Finalize TICC-19
- Activities for this year
- Initial draft for Activities 2024 was ciruclated internally
- Published
- Progress alignment with change and release management based on new agreement change processes
- Continue Peppol specification upgrade based on latest version of underlying standard e.g., OASIS
- Commence work on future of SML – defining business requirements followed by solution implementation in due course
- Documentation of Peppol eDelivery Network Architecture
- Ensure and maintain safe & secure operation over Peppol eDelivery Network
- Resource problem is still pressing
- Ad activity 2: Discussion on the comparison of new and existing standards should be done in a less "ad hoc way"
- Start documenting findings in a more structured way
- Ad activity 3: Brainstorming for Peppol Architecure v2 has been started
- Check if a restricted Confluence page can be used instead
- Crosscheck with the long term tasks
- Changes to eDEC internal guidelines
- 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".
- Next meeting(s)
- 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
...
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-345 - Information: request to remove Participant Identifier schemes 0037, 0212, 0213, 0215
- Decision: none yet
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-343 - Information: remove Japan busdox document type identifiers from Code Lists
- Decision: Approved by eDEC CMB with a specific supporting activity described in the ticket
- Responsible: Philip Helger
- TICC-335 to TICC-341 are related to the new Enhanced B2B domain
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-333 - Information: Addition of Italy specific Invoice identifiers
- Update: this is extended use and requires prior MC approval
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-332 - Information: RFC to convert the output of the MLA work group (the Message Level Status) into an eDEC specification
- Update: Information to be circulated to the group; will be discussed in next eDEC CMB meeting
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-331 - Information: Add new document types for Norwegian "INNBYGGERPOST"
- Decision: approved by F2F eDEC CMB. Will be part of Code Lists v8.9
- Reponsible Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-330 - Information: Mandatory use of same identifier in recipient field of SBDH and endpointID in document
- Update: none
- Responsible:
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-327 - Information: Error correction for Reporting Specification needed
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-325 - Information: Create official clarification between the use of a Participant Identifier and a Legal Identifier
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-323 - Information: Change Lower boundary of Business Entity within Business Card
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-322 - Information: Ambiguity of Participant Identifier Casing between POLICY 1 and POLICY 2
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-319 - Information: add additional SETU document types to the codelist
- Update: Part of the v8.9 code list releases
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-315 - Information: Peppol Reporting name change
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-313 - Information: added Participant Identifier Scheme 0234 to the eDEC CodeList
- Decision: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-311 - Information: Use UTC for all Peppol publications date time
- Update: none
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-310 - Information: Codelist alignment
- Update: none
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-309 - Information: Codelist alignment
- Update: none
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-308 - Information: internal activity: create AP Operational Guideline
- Update: none
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-303 - Information: extract Business Card specification from Peppol Directory specification
- Update: none
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-286 - Information: Suggestion on C4 Country Code
- Update: none
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-285 - Proposal to make mandatoriness of Directory API in SMP specification more clear
- Update: none
- Decision: OO to clarify on the mandatory use of Business Cards.
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-284 - Information: AS4 inconclusive specification on signing of AS4 Error messages
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-282 - Update: Deprecate old Business Card Formats
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-269 - Information: Request to improve consistency in AS4 error handling
- Update: none
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-263 - Information: Peppol Participant (Corner 4) served by more than one Access Point
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-235 - Information: Start definining potential actions for removing identifiers in the Code List States Document. Start with TICC-228
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-233 - Information; Its about a wording issue in the Peppol Envelope Policy (SBDH)
- Update: none
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-226 - Information: New SMP API proposal (migration code exchange)
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-225 - Information: New SMP API proposal (health check)
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-224 - Information: New SMP API proposal (identify)
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-223 - Information: Collection issue: Peppol, EESPA, BPC
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-218 - Information: Clarify case sensitivity of Peppol Seat ID
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-206 - Information: Number of retries on an AS4 level
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-202 - Information: Information about caching of SMP results for usage in a Peppol AP is missing
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-187 - Information: Allow 0080 as new Participant Identifier scheme
- Update: none
- Responsible: Elly Stinchcombe (Unlicensed)
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-174 - 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.
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-168 - Information: Have a separate participant identifier prefix for testing purposes.
- Update: none
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-167 - Information: regarding joint information on news and noteworthy
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-166 - Information: Clarification on the words "custom validation" in the AS4 profile was sought.
- Update: none
- Responsible: Philip Helger
Jira Legacy server System JIRA serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-153 - Information: https for SMP
- Update: Part of the SMP 2.0 specification update
- Responsible: Philip Helger
Jira Legacy server System JIRA serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-151 - Information: (Whitepaper) Enforce people to use SMK for testing?
- Update: none
- Responsible: Philip Helger
Jira Legacy server System JIRA serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-149 - Information: add a Schematron for verifying the AS4 headers. Updates directly in the issue.
- Update: none
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-146 - Information: (Whitepaper) Creation of the Whitepaper.
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-142 - Information: (Whitepaper)
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-140 - Information: (Whitepaper)
- Responsible: Philip Helger
Jira Legacy server System Jira serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-19 - Information: Information on how to determine and handle inactive SMP providers
- Update: The version was accepted. The issue will be closed.
- Responsible: Philip Helger
Attachments
none