Re: Interpretation of service and action elements

[David O'Riordan <dave@bindsys.com>]

Hi Himagiri,

We interpret the Action element in an ebXML request or response message  
to map to the name of the associated RequestingBusinessActivity or  
RespondingBusinessActivity, and Service to map to the Service element 
of  the ServiceBinding associated with the role supported by the 
receiver  party in the CPA. This I believe aligns with the definitions 
given in  the messaging (section 8.4.4) and CPP/CPA specs (section 
7.5.7), as  well as the TRP minutes.

Granted the specs could be better aligned here. For example, the BPSS 
spec includes a sample which has empty  RequestingBusinessActivity and 
RespondingBusinessActivity names. This  would imply (on our 
interpretation) empty action elements in the message  headers: not 
helpful for routing. We assume real BPSSs will have  distinct activity 
names here.

As for a nested collaboration, we see that the Service name for the  
nested collaboration being the same as for the enclosing collaboration.  
Having a different service name would require an extra entry in the CPA  
for the nested collaboration, which seems unnecessary.

Cheers
David O'Riordan

Bind Systems
www.bindsys.com <http://www.bindsys.com>

> Q. from Sybase.
>
> ----- Original Message ----- From: "Himagiri Mukkamala" 
> <himagiri@sybase.com> <mailto:himagiri@sybase.com>
> To: <ebxml-dev@lists.ebxml.org> <mailto:ebxml-dev@lists.ebxml.org>
> Sent: Wednesday, July 11, 2001 10:48 PM
> Subject: Interpretation of service and action elements
>
>
> I'd like to get vendors and implementors
> interpretation of service and action elements
> to be included in an ebxml message.
>
> Basically the correlation between
>
> service, action
>
> and
>
> colloboration name, BusinessTransactionActivity and
>
> serviceBinding name in the CPA.
>
> Probably with a nested collaboration in perspective.
>
> Thanks
> himagiri
>
>
>