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

[Himagiri Mukkamala <himagiri@sybase.com>]

But the same (role name, service name) combination could exist!
Like you said this is cause the service name is not unique and
hence you cannot uniquely identify the deliveryChannel without
knowing which processSpecification these are related to

-hima

Arvola Chan wrote:

Hima:

Each CollaborationRole has its own ServiceBinding and
Service sub-elements.

You should be able to use the Service element in the
message header to look up the proper ServiceBinding.
However, there is no current requirement that the Service
(name) be unique. Rather than having Service as a
sub-element of ServiceBinding with its own type attribute,
we may want to declare Service as an ID attribute for
ServiceBinding and declare ServiceType as an attribute
of ServiceBinding.

-Arvola

-----Original Message-----
From: Himagiri Mukkamala <himagiri@sybase.com>
To: ebxml-cppa@lists.oasis-open.org <ebxml-cppa@lists.oasis-open.org>
Date: Thursday, October 18, 2001 3:29 PM
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?

Onlyinformation to identify these properties from the message header is

CPAID, FromPartyId, ToPartyId, From Role, To Role

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>