Pim van der Eijk
1) Status update
2) Adoption (users, reviewers, implementers to contact for
requirements and implementation)
3) Action items
1) Status update
We continued the discussion on scope for the TC, ambition
and interests of participants, and noted that the latest
draft of CPA 3.0 from the former ebXML CPP/CPA TC has been
uploaded to the SC's Kavi pages and is ready to be used as
input for work in this SC. The draft provides:
- Enhancements to support ebMS 3.0, Core. Now that ebMS
3.0 Part 2 is shaping up, the time is right to look at
extensions to support the enhancements of that part.
- Extensibility towards other B2B protocols: EDI-INT and
WSDL-based exchanges. REST is presumably covered too.
- Many examples, some also with an ebBP.
The RosettaNet MMS has profiled WS-I, AS2 and ebMS2 as
messaging protocols for RosettaNet. RosettaNet has one
active project, MCC, which has used a simple form of ebBP to
express PIPs. The ebBP quality of service attributes are
used to control configuration of MMS messaging protocols.
CPA is not in the first phase, but is being considered for a
second phase as it can be used for all three MMS protocols,
unlike any other agreement or policy specification
A variant of CPA has been used in Japan to configure some of
the newer ebMS 3.0 features, such as WS-Security,
WS-Reliability and Pull mode.
In Europe, a draft version of CPA 3.0 is used with an ebMS
3.0 implementation in the textile industry that is used by
various pilots/project. There are also a few research
projects in Europe that are looking at CPA.
A questionaire by GS1 indicates there is significant
interest in ebMS 3.0, especially in Asia, South America and
the automotive industry. CPA 3.0 could support this.
- Upload/complete an issue list covering known issues with
CPP/CPA 2.0 uncovered over the years (Dale)
- Post discussion document with various enhancements for
synchronous messaging and multihop (Pim)
- Contact potential contributors (or just reviewers) to
join or monitor the work of the SC (all)