TICC-173 - Getting issue details... STATUS
1. Information: Peppol Process ID does not include AUNZ Self Billing
2. Update: If the additionally requested document types are in the code list, this request is approved. If the document type identifiers are missing in the code list, this ticket needs to be re-evaluated next CMB. If approved, would be part of Code List 7.5.
3. Decision:Wait for further input
4. Responsible: Philip Helger
TICC-171 - Getting issue details... STATUS
1. Information: add 0210 and 0211. 0210 can handle persons and legal entities.
2. Decision: Approved to add both identifiers in Code List v7.5.
3. Responsible: Philip Helger
TICC-170 - Getting issue details... STATUS
1. Information: add 0212 and 0213
2. Decision: Approved to add both identifiers in Code List v7.5.
3. Responsible: Philip Helger
TICC-169 - Getting issue details... STATUS
1. Information: Public code lists 7.4
2. Update: Publication package was sent to Jerry, but wasn't published yet.
TICC-168 - Getting issue details... STATUS
1. Information: Have a separate participant identifier prefix for testing purpises.
2. Decision: Should also be part of the Whitepaper.
TICC-167 - Getting issue details... STATUS
1. Information: regarding joint information on news and noteworthy
2. Decision: see ticket for details. OO to execute the actions.
TICC-166 - Getting issue details... STATUS
1. Information: Clarification on the words "custom validation" in the AS4 profile was sought.
2. Decision: A clarification was stated as a response to the ticket, that "custom validation" does NOT include business document validation. Improvement of the wording in the AS4 spec was put in the backlog.
TICC-162 - Getting issue details... STATUS
1. Information: Deprecate the AS2 transport protocol
2. Update: Questions have been designed by OO and agreed with the PA Community. Most suitable way forward is sought be OO. Waiting for the results.
TICC-158 - Getting issue details... STATUS
1. Information: Updated the issue
2. Decision: Further evaluate if ISO 6523 structuring can be used more efficiently (like in 9915:123456789:sadhjsadghas). Look into the ISO 6523 standard. Is most likely of strategic relevance.
3. Responsible: Martin Mane (Unlicensed)
TICC-153 - Getting issue details... STATUS
1. Information: https for SMP; Philip sent out an email (2020-11-18) with a decision basis paper
2. Update: CC action CC8-1 refers to this. On hold until the whitepaper is finished.
3. Responsible: Philip Helger
TICC-152 - Getting issue details... STATUS
1. Information: End to End security; in progress
2. Decision: closed - no further action
TICC-151 - Getting issue details... STATUS
1. Information: Enforce people to use SMK for testing?
2. Decision: Part of the Whitepaper.
3. Responsible: Philip Helger
TICC-149 - Getting issue details... STATUS
1. Information: add a Schematron for verifying the AS4 headers. Updates directly in the issue
2. Update: no update
3. Responsible: Philip Helger
TICC-146 - Getting issue details... STATUS
1. Information: Creation of the Whitepaper. No further updates.
2. Responsible: Philip Helger
TICC-142 - Getting issue details... STATUS
1. Information: Part of Whitepaper.
2. Responsible: Philip Helger
TICC-140 - Getting issue details... STATUS
1. Information: Part of Whitepaper
2. Responsible: Philip Helger
TICC-138 - Getting issue details... STATUS
1. Information: Updates received from GS1
2. Action:Add to Code List v7.5
3. Responsible: Philip Helger
TICC-133 - Getting issue details... STATUS
1. Update: No further update. Wait for OO polling the AS2 usage and than piggyback on this solution
2. Responsible: Martin Mane (Unlicensed)
TICC-132 - Getting issue details... STATUS
1. Information: Publication of the eDEC specification backlog.
2. Update: Open for feedback until 2021-03-18
3. Responsible: Martin Mane (Unlicensed)
TICC-98 - Getting issue details... STATUS
1. Update: none
TICC-19 - Getting issue details... STATUS
1. Update: Part of Whitepaper
2. Responsible: Philip Helger

Other:

Actions

Action log: eDelivery CMB action log

Actions handled in this meeting:

Actions not handled in this meeting:

Information/Discussion items

Next meeting on Thursday April 1st, 9:00 to 11:00 CET

Attachments

Browser not supported