RE: Collaboration Services (was: Business Service Interface)

["Welsh, David" <David.Welsh@nordstrom.com>]

So ... in simple terms ...
we should have "collaborating workflows" representing (core) business
processes (expressed in XML and made from core components) hosted in the
Registry/Repository and normally 'qualified thru some standard methods' when
a trading part??? (with all respect to party or partner) agreement is
automatically negotiatied ?

Is that what you meant ?


-----Original Message-----
From: Krishna Sankar [mailto:ksankar@cisco.com]
Sent: Sunday, October 22, 2000 4:30 PM
To: Nikola Stojanovic; ebxml-tp@lists.ebxml.org
Cc: 'ebXML-BP@llists.ebxml.org'
Subject: RE: Collaboration Services (was: Business Service Interface)


Hi all,

	Now we are in the workflow realm ! Isn't workflow an interactive
machine
with interaction policies ? If so, we should be looking at the workflow
space for ideas. A better way would be to see if we can leverage a workflow
standard for solving the ordering and related challenges.

cheers

-----Original Message-----
From: Nikola Stojanovic [mailto:nhomest1@twcny.rr.com]
Sent: Sunday, October 22, 2000 2:54 PM
To: ebxml-tp@lists.ebxml.org
Cc: 'ebXML-BP@llists.ebxml.org'
Subject: Re: Collaboration Services (was: Business Service Interface)


<Bob Haugen>
The ordering or choreography relationships that are most interesting to me
are those that have clear business logic behind them, often in the form of
pre and post conditions. For example, a prepayment business collaboration
contract would mean the payment must arrive before the delivery. Economic
events that fulfill commitments would be expected to occur after their
respective commitments. Or another way, the states of a negotiation could be
choreographed by a state machine.

</Bob Haugen>

I would say that "ordering or choreography relationships" like "must arrive
before" and "expected to occur after"  are "Temporal constraints". Also,
would we agree that it might be rather "Interactive machines, Interaction
policies, ..." then "State machines"?
Yes, ordering might not be enough for constraints like:
- max, min or exact time between event a and event b has to be n time
units",
- choice -> branching/merging for "Conctrained forests",
- potential eventuality.

Regards,
Nikola