Re: Draft - v7

Hugo,

I can't comment on why others didn't reply to your earlier email.  For 
myself, I didn't have the same heartburn as you about the word 
"activities" and was quite ready to defer to the group consensus.  I 
have a slight preference for your restructured wording (fewer words, a 
bit clearer).

thanx,
    doug

Hugo Haas wrote:

>Hi Jeff.
>
>* Jeff Mischkinsky <jeff.mischkinsky@oracle.com> [2002-11-07 07:09-0800]
>  
>
>>   I've updated the draft, major changes underlined, along with some other 
>>minor typos/changes, as well as fixing the dates so that they proceed in a 
>>monotonic increasing sequence.
>>    
>>
>
>I don't see anything about my comments[81]. Is that because you
>disagreed with them or because you didn't see them?
>
>Concretely, what I proposed doing was replacing:
>
>  
>
>>   The choreography specification(s) shall define (at a minimum) the
>>   behavior and language constructs for the following key concepts:
>>     * Composition features
>>
>>     * The ability to define a choregraphy as a web service, i.e. a
>>       recursive composition model.
>>     * Definition of the choreography's externally observable behavior.
>>     * Ability to specify externally defined constraints.
>>     * Ability to represent stateful choreographies.
>>     * Definition of the identity of a choreography instance.
>>     * Lifecycle management (e.g. creation, termination, etc.)
>>
>>     Associations
>>     * Roles based on web service use.
>>     * Linkages between web services.
>>     * References to web services.
>>
>>     Message exchanges
>>     * Conversations - correlated message exchanges that define
>>       interactions between web services.
>>     * Correlations and their life cycle management.
>>     * Correlation relationships with choreography instances and state.
>>
>>     Activities
>>     * Message exchange interactions between web services (e.g. receive,
>>       invoke, etc.).
>>     * Behavior definitions (e.g. sequencing , looping, concurrent
>>       execution, etc.).
>>     * Relationships between activities.
>>     * Scoping Rules.
>>     * Nesting Rules.
>>
>>     State Management
>>     * Definition, manipulation, and query capabilities
>>    
>>
>
>with:
>
>|   The choreography specification(s) shall define (at a minimum) the
>|   behavior and language constructs for the following key concepts:   
>|     * Composition features
>|          + The ability to define a choregraphy as a web service, i.e. a
>|            recursive composition model.                                
>|          + Definition of the choreography's externally observable
>|            behavior.
>|          + Ability to represent stateful choreographies.
>|          + Definition of the identity of a choreography instance.
>|          + Lifecycle management (e.g. creation, termination, etc.)
>|          + Message exchange interactions between web services (e.g.
>|            receive, invoke, etc.).
>|          + Behavior definitions (e.g. sequencing , looping, concurrent
>|            execution, etc.).
>|     * Associations
>|          + Roles based on Web service use.
>|          + Linkages between Web services.
>|          + References to Web services.
>|     * Message exchanges               
>|          + Conversations - correlated message exchanges that define
>|            interactions between web services.
>|          + Correlations and their life cycle management.
>|          + Correlation relationships with choreography instances and
>|            state.
>|     * State Management
>|          + Definition, manipulation, and query capabilities
>
>Regards,
>
>Hugo
>
>  81. http://lists.w3.org/Archives/Public/www-ws-arch/2002Nov/0024.html
>  
>