W3C home > Mailing lists > Public > public-ws-chor@w3.org > April 2003

Re: Events and States (was: timeouts & states (was: Abstract Bindable Choreography))

From: Ricky Ho <riho@cisco.com>
Date: Fri, 11 Apr 2003 10:47:26 -0700
Message-Id: <>
To: Assaf Arkin <arkin@intalio.com>
Cc: jdart@tibco.com, Cummins Fred A <fred.cummins@eds.com>, public-ws-chor@w3.org

I understand the "nested state", basically you breakdown a state into finer 
grain, but this is still mutually exclusive.  You can only be at one of the 

In David's example, lets say the seller interact with the manufacturer as 
well as the credit check.  In the public state diagram, the seller want to 
express that the purchase order will be confirmed only when the credit 
check passes as well as the manufacturer have the product in stock.

So, does the seller has two non-exclusive states "credit-pass", 
"product-available" ?

or 4 mutually-exclusive states "credit-pass and product-available", 
"credit-pass and NOT product-available" .....

The latter is easier to understand.

Rgds, Ricky

At 10:15 AM 4/11/2003 -0700, Assaf Arkin wrote:
>Ricky Ho wrote:
>>In David's example, "State" is not mutually exclusive.  (Correct me if 
>>I'm wrong).  A role can have multiple "states" at the same time and each 
>>of this state can accept different events and transition to another 
>>states.  Somewhat similar to a multi-thread scenario.  So when one thread 
>>reaches an end state.  The choreography can still be active because of 
>>other threads.
>>This is quite different from the traditional state chart who try to avoid 
>>composite states.  Am I totally lost ?
>Some state transition models have mutually exclusive states.
>Statechart diagrams have composite states, so they allow for non-exclusive 
>states and multiple concurrent sub-states as part of the same parent state.
>>Rgds, Ricky
Received on Friday, 11 April 2003 13:47:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:30:00 UTC