...

Klaus Vilstrup (OpenPeppol OO)

Agenda

1. Approval of minutes
2. New tasks and Issues
3. Actions
4. Information items
5. Input from emailProgress alignment with change and release management based on new agreement change processes
6. Continue Peppol specification upgrade based on latest version of underlying standard e.g., OASIS
7. Commence work on future of SML – defining business requirements followed by solution implementation in due course
8. Documentation of Peppol eDelivery Network Architecture
9. Ensure and maintain safe & secure operation over Peppol eDelivery Network
10. Other

Approval of Minutes

eDelivery CMB meeting 2023-05-11 minutes

Status: Approved ????moved to next meeting

Information/Discussion items

1. Next meeting Monday (!) 2023-06-06, 9:00 to 11:00 CET
   1. Moved due to overlap with the OpenPeppol GA
2. Reporting
   1. ..
3. Policy for use of Identifiers Update v4.2.0 for Peppol Wildcard [Document Type Identifier] Scheme (previously DDTS)
   1. ..
4. SMP 2.0 internal Work group
   1. Working progresses in Google Docs
   2. Next meeting: ..., 2023
5. Code List release process
   1. ...
6. Peppol in France
   1. ..

Internal priorities

...

Issues 

1. Progress alignment with change and release management based on new agreement change processes
   1. Status and questions around specifications and codelists.
   2. Mostly we believe we are following these processes.
   3. Need to ensure POAC use the same definition of major v minor changes.
   4. Need to ensure good coordination between POAC and eDEC i.e.alignment of codes list release times and alignment of codes.
   5. Do we have a discussion group to coordinate? OO to assist (Klaus Vilstrup).
2. Continue Peppol specification upgrade based on latest version of underlying standard e.g., OASIS
   1. Internal WG is in place and work is progressing well with clearly defined scope and outcomes
   2. High level timeline to be developed with some key milestones (while keeping group informal)
   3. Invite to be extended to Klaus Vilstrup, Klaus talks to Philip Helger  about this group.
3. Commence work on future of SML – defining business requirements followed by solution implementation in due course
   1. Need to dig out previous commentary from eDec discussions on this topic (on Google Drive – (Bård Langöy)
   2. BPC have done a POC on a federated/distributed SML – We need details and the results (Philip Helger was a part of the WG). 
   3. Need to ensure we properly understand expectation of MC
   4. Need to define business requirements and understand various options and their pros/cons
   5. Kick this work off once SMP work is done, Klaus Vilstrup to take the lead
4. Documentation of Peppol eDelivery Network Architecture
   1.  Low priority
   2. Recommend to be done post SMP and SML work
   3. Revisit when ready
5. Ensure and maintain safe & secure operation over Peppol eDelivery Network  
   1. Our BAU work, we need to look at open tickets on this and see what needs to be done
   2. Are we hooked into Security WG? Arun participates irregularly
   3. Interconnected with number 2: Need for an architecture overview of existing and future technologies.
6. Other
   1. Consider SBDH and XHE? Should this go in SMP WG or run it separately?
   2. What is future state of Peppol Directory e.g. do we make Peppol Directory mandatory and switch from an opt-in to an opt-out process, and is this an eDec responsibility to progress?
   3. Technology review (Klaus Vilstrup)
   4. Resourcing view (Klaus Vilstrup)
   5. Philip Helger - a reminder of the action from last CMB to speak to Didier and ask if he can present the French PoC to the eDEC CMB for 10 to 15 minutes

SPC relevant

• Nothing atm

New tasks and Issues (from last meeting)

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

...