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

[Dale Moberg <dmoberg@cyclonecommerce.com>]

Marty writes:

"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?"

Here is a thought: there is a "preCondition" attribute defined
for the BinaryCollaboration element. Maybe the
CounterOfferBinaryCollaboration
could have a preCondition requiring that a CPAOfferBinaryCollaboration
instance has occurred ? 

Dale