W3C home > Mailing lists > Public > www-ws-arch@w3.org > October 2002

RE: Definition of Choreography

From: Champion, Mike <Mike.Champion@SoftwareAG-USA.com>
Date: Sat, 19 Oct 2002 14:23:22 -0400
Message-ID: <9A4FC925410C024792B85198DF1E97E4042DE0CE@usmsg03.sagus.com>
To: www-ws-arch@w3.org



> -----Original Message-----
> From: Ricky Ho [mailto:riho@cisco.com]
> Sent: Friday, October 18, 2002 9:17 PM
> To: Burdett, David; 'Champion, Mike'; www-ws-arch@w3.org
> Subject: RE: Definition of Choreography
> 
> 
> Can the public protocol be just an XML 
> representation of a state machine.  Each state constraint 
> what event can  happen (event can be what SOAP message to send or what
SOAP 
> message to  receive).  Each event defines the next state.  Effectively, 
> we are defining  what are the possible message exchange sequence without 
> describing the  internal decision making process.

I like this idea a lot.  Can anyone sketch out an example of how one might
model a little corner of one of the choreography specs using a state machine
notation?
Received on Saturday, 19 October 2002 14:23:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:09 GMT