Choreography: Narrowing Down the Requirements

Hi,
   In response to the WSCG's request that we narrow down the requirements 
before presenting our recommendation to the AC, I'd like to float a trial 
balloon. The proposal would be to insert into the previous draft of the 
proposed charter the text specified below (or something real close to it). 
In addition, along the lines of our previous discussions and votes, I'd 
suggest restricting the input documents to the one's we agreed were most 
essential. I'll post a complete draft charter before the (Halloween) telecon.

The choreography specification(s) shall define (at a minimum) the behavior 
and language constructs for the following key concepts:

     * Composition features
           o The ability to define a choregraphy as a web service, i.e. a
             recursive composition model.
           o Definition of the choreography's externally observable behavior.
           o Ability to represent stateful choreographies.
           o Definition of the identity of a choreography instance.
           o Lifecycle management (e.g. creation, termination, etc.)
     * Associations
           o Roles based on web service use.
           o Linkages between web services.
           o References to web services.
     * Message exchanges
           o Conversations - correlated message exchanges that define
             interactions between web services.
           o Correlations and their life cycle management.
           o Correlation relationships with choreography instances and state.
     * Activities
           o Message exchange interactions between web services (e.g. receive,
             invoke, etc.).
           o Behavior definitions (e.g. sequencing , looping, concurrent
             execution, etc.).
           o Assignment semantics.
           o Relationships between activities.
           o Scoping Rules.
           o Nesting Rules.
     * State Management
           o Definition, manipulation, and query capabilities