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

RE: Definition of Choreography

From: Edwin Khodabakchian <edwink@collaxa.com>
Date: Wed, 16 Oct 2002 17:40:38 -0700
To: "'David Orchard'" <dorchard@bea.com>, <www-ws-arch@w3.org>
Message-ID: <018001c27575$d0bc4ce0$680aa8c0@collaxa.net>

Hi Dave,

Would you happen to know of an example of such a specification? 

Also who is the "client" of that specification? Meaning for example, 
it is:  
(1) a developer that reads it to get a getter undertanding 
    of how to interact with a node or how a collection of 
    node work together, 

(2) an engine that executes that specification and coordinates 
    interactions across the nodes.

(3) is it a tool that reads it an converts it into a "proxy" 
    that allows programmers to better interact/have conversation
    with the nodes. (WSDL would for example fall into this 
    category).

Finally, [how] is choreography different from workflow or routing?

Thank you,

Edwin


> -----Original Message-----
> From: www-ws-arch-request@w3.org 
> [mailto:www-ws-arch-request@w3.org] On Behalf Of David Orchard
> Sent: Wednesday, October 16, 2002 3:38 PM
> To: www-ws-arch@w3.org
> Subject: Definition of Choreography
> 
> 
> 
> Hi all,
> 
> With great trepidation, I provide a first cut at a choreography term
> definition:
> 
> The specification of the ordering of messages from one nodes 
> perspective or a collection of nodes.  May or may not include 
> turing complete logic in determination of the message 
> exchange pattern.
> 
> Cheers,
> Dave
> 
> 
Received on Wednesday, 16 October 2002 20:41:16 GMT

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