Re: Updated Choreography concept/relationship proposal

Hi Mike.

* Champion, Mike <Mike.Champion@SoftwareAG-USA.com> [2003-07-09 18:59-0400]
> XXX Choreography
> XXX.1 Definition
> A Web Services Choreography is a formal model of the pattern of possible web
> service invocations among a set of service providers and consumers.  The

Minor tweak: there is no service consumer concept, but a service
requester one -> s/consumers/requesters/

> choreography must specify the set of messages that may be sent, the set of
> publicly observable states that each participant in the choreography may be
> in, and the transitions from one state to another to be expected upon
> receipt of the defined messages.  There is no requirement that the parties
> literally implement the shared state machine described by the formal model,
> only that the choreography provides an abstract description of the sequence
> of legal interactions and their consequences.
> 
> XXX.2  Relationships to other elements
> 
> A choreography defines the pattern of possible interactions between a set of
> SERVICES
> 
> The primitive interactions in a choreography are MESSAGE EXCHANGE PATTERNS
> 
> A choreography may be expressed in a CHOREOGRAPHY DESCRIPTION LANGUAGE.
> 
> XXX.3 Discussion
> 
> SOAP and WSDL by themselves can describe only very simple Web services
> consisting of a single interaction between a consumer and provider pair.
> The SOAP Recommendation formally specifies only two MEPs, "Request-Response"
> and "SOAP Response."

You seem to be suggesting here that SOAP is a description language. I
would only talk about WSDL here.

[..]
> YYY Choreography Description Language
[..]
> A choreography description language much be minimally capable of formally
> describing the interactions in known Message Exchange Patterns.

Typo: s/much/must/

Regards,

Hugo

-- 
Hugo Haas - W3C
mailto:hugo@w3.org - http://www.w3.org/People/Hugo/

Received on Friday, 11 July 2003 09:29:45 UTC