OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-tp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

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.


-----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
- choice -> branching/merging for "Conctrained forests",
- potential eventuality.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC