Additional requirements [was RE: Requirements: extracts from minu tes 20030408]

I would like to suggest the following additional requirement:

A choreography will express the types of messages a participant
may send, and the types of messages/responses the participant should
anticipate receiving from the other participant(s) (including
time-outs) based on the apparent state of the exchange.

Fred

> -----Original Message-----
> From: Martin Chapman [mailto:martin.chapman@oracle.com]
> Sent: Thursday, April 17, 2003 3:05 PM
> To: public-ws-chor@w3.org
> Subject: Requirements: extracts from minutes 20030408
> 
> 
> 
> As per my action point here is a list of proposed 
> requirements extracted
> from the minutes of the tues 8 April con call.
> 
> 1. A Choreography should be independent of message formats
> 
> 2. A Choreography may have run time changes:
>    a. the actual participants can vary
>    b. the actual choreography can vary [ed: I think we ruled this out
> but have listed it for completeness]
> 
> 3. It should be possible to query the state of a Choreography
> 
> 4. Error/fault handling and compensation features need to be 
> able to be
> expressed in the language.
> 
> 5. Choreographies should be composable (into a hierarchy)
> 
> 
> Martin.
> 
> _________________________________________________________________
> Martin Chapman                                 500 Oracle Parkway
> Consulting Member of Technical Staff           Ms 4op990
> Oracle                                         Redwood Shores,
> P: +1 650 506 6941                             CA 94065
> e: martin.chapman@oracle.com                   USA
>

Received on Thursday, 17 April 2003 17:58:20 UTC