Re: [ebxml-cppa] Issue with ProcessSpecification, CollaborationRole

[Martin W Sachs <mwsachs@us.ibm.com>]

Himagiri,

Please see my responses below.

Regards,
Marty

*************************************************************************************

Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287;  IBM tie line 863-7287
Notes address:  Martin W Sachs/Watson/IBM
Internet address:  mwsachs @ us.ibm.com
*************************************************************************************



Himagiri Mukkamala <himagiri@sybase.com> on 10/18/2001 06:33:39 PM

To:    "ebxml-cppa@lists.oasis-open.org" <ebxml-cppa@lists.oasis-open.org>
cc:
Subject:    [ebxml-cppa] Issue with ProcessSpecification, CollaborationRole



Anybody think this is a problem?

CPAs PartyInfo has multiple collaboration roles which maps to roles in
BPSS.
This is the RoleName being used in the message header.

WHat if the CPA has multiple collaboration roles with same "Role" from
multiple BPSS documents in the  CPA for a  PartyInfo?

E.g. If a Party with PartyId "SellerPartyID" plays the same role
"Seller" in two process specifications
"http://www.sybase.com/processes/OrderManagement1.
xml" and http://www.sybase.com/processes/OrderManagement2.xml"

For a particular ServiceBinding, which deliveryChannel or other
characteristics do you pick?

MWS:  The From party application chooses the To party's delivery channel
based on which Process Specification it is executing.  The
ProcessSpecification
and ServiceBinding elements are both child elements of the same
CollaborationRole element.  The From party application must pass either
the delivery channel identification or its endpoint address to the MSH
along
with the message.



Onlyinformation to identify these properties from the message header is

CPAID, FromPartyId, ToPartyId, From Role, To Role

MWS: The message header also contains the conversationId.  This should
be sufficient to select the correct CollaborationRole element.  Service
and Action then provide the correct software entry point.

This may not be a good way for someone to design their architecture, but
there is scope for this to happen using CPA.
-hima


-----------------------------------------------------------------------------


<PartyInfo>
<PartyId>SellerPartyID</PartyId>
<PartyRef xlink_href = "http://aaaa/ebXML/msh"/>
<CollaborationRole id = "SellerRole1">
<ProcessSpecification version = "1.0" name = "Order Management1"
   xlink_type = "simple"
xlink_href="http://www.sybase.com/processes/OrderManagement1.
xml"/>
<Role name = "Seller" xlink_type = "simple"
xlink_href =
"http://www.sybase.com/processes/OrderManagement1.xml#Seller"/>
<ServiceBinding channelId = "N04" packageId = "N0402"
            name = "Product Purchase1">
<Service type = "string">Product Purchase1</Service>
</ServiceBinding>
</CollaborationRole>

<CollaborationRole id = "SellerRole2">
<ProcessSpecification version = "1.0" name = "Order Management2"
   xlink_type = "simple"
xlink_href="http://www.sybase.com/processes/OrderManagement2.
xml"/>
<Role name = "Seller" xlink_type = "simple"
xlink_href =
"http://www.sybase.com/processes/OrderManagement2.xml#Seller"/>
<ServiceBinding channelId = "N04" packageId = "N0402" name = "Produc
t Purchase2">
<Service type = "string">Product Purchase2</Service>
</ServiceBinding>
</CollaborationRole>
.....
......
</PartyInfo>


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>