AW: [ebxml-cppa] OASIS ebXML CPPA core maintenance draft (2.1) and schema

["Sacha Schlegel" <sschlegel@cyclonecommerce.com>]

Hi Dale, hi group
 
I have the situation where we have more than one CollaborationRole in the CPA. In an ebXML message we have the CPA ID, converstaion ID, Service name and the Action name.
 
The question is how to assign an incoming ebXML message to the correct business process (CollaborationRole) within the CPA. To find the right CPA is easy, just to look up the CPA idīs. Just all CPA ids must be unique within one system.
 
The CPPA specification requests, that if the CPA is based on ebXML BPSS, then within a CollaborationRole the Service element has to be the uuid of the ProcessSpecification element (8.4.9). If the CPA is not based on ebXML BPSS, then the Service element can have whatever value. Further the specifiaction says in 8.4.16 that if the CPA is based on the ebXML BPSS, it must have the ActionContext element. 
 
I assume that the Action Context can also be used if the CPA is not based on the BPSS. So it looks that to really make sure that the CPA is based on ebXML BPSS the xlink of the business process definition file (in my case the bpss xml file) has to be followed.
 
It comes down to the question whether we reject a CPA which has non unique (non unique per CPA) Service elements in it.
 
Looks like its time to reread the whole CPPA spec again.
 
Regards
 
Sacha 
________________________________

Von: Dale Moberg [mailto:dmoberg@cyclonecommerce.com]
Gesendet: Mi 27.10.2004 15:27
An: ebxml-cppa@lists.oasis-open.org
Betreff: [ebxml-cppa] OASIS ebXML CPPA core maintenance draft (2.1) and schema



Hi,

 

Nov 12 we can begin to discuss aspects of the 2.1 maintenance release.

 

The main missing elements are the SOAP header and module descriptions.

 

The WSDL extensions need some final changes.

 

BPSS and Messaging 3.0 may give us some reasons to modify Action, Service, Role and Action Context.

 

In the hope of letting you look over these sections I am posting an editor's draft.

 

This draft should include all the errata we have noted so far.

 

The examples for alternative messaging, wsdl, and soap support are preliminary.

 

I will be traveling next week so I won't have time to edit too much until Nov 9. If you notice something let me know and I will start an issues list on the draft.

 

Thanks,

 

Dale Moberg

 

PS The appendices are getting numbered consecutively with the main sections. I will find out how to change this eventually, but there will be appendices similar to the 2.0 version.