[ebxml-cppa-negot] Re: Hima'sNegotiation BPSS Instance

["Himagiri(Hima) Mukkamala" <himagiri@sybase.com>]

CPA would not have a action for the collaboration
"CPA Counter Offer 1 BTA" by itself. It will be included
only as part of the nested collaboration.

Ideally there would be a precondition that CPA Counter Offer 1 BTA
is part of CPA_Negotiation_BC, but due to lack of expression
of such condition, cannot be expressed.

I think the intent of the BPSS spec was to allow nested collaboraitons
and that was the reason for CollaborationActivities which
are BinaryCollaborations...

-hima

Martin W Sachs wrote:

> The Negotiation BPSS instance contains two Binary Collaborations, each with
> a Start element.  I can't find anything that unambiguously specifies that
> the choreography begins with the "CPA Offer BTA"  business transaction
> activity under the "CPA_Negotiation_BC" binary collaboration. As far as I
> can tell, it might equally well begin with the "CPA Counter Offer 1 BTA"
> business transaction acvitity uner the "CPA Negotiation CounterOfferBC"
> binary collaboration.
>
> Of course, we all know from the semantics of what we are doing that  the
> "CPA Offer BTA" business transaction activity has to start things off, but
> a BPSS deployment tool won't know that.  What determines where the
> choreography actually begins when there is more than one binary
> collaboration in the instance document?
>
> I suspect that the BPSS designers intended that each binary collaboration
> be independent, with its own choreography.  If I am right, we are violating
> that assumption because the two binary collaborations in this instance
> document are very definitely connected into a single choreography.
>
> 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
> *************************************************************************************