W3C home > Mailing lists > Public > public-ws-chor@w3.org > June 2003

Re: Revised: Mission Statement

From: Assaf Arkin <arkin@intalio.com>
Date: Tue, 03 Jun 2003 20:44:02 -0700
Message-ID: <3EDD6B02.8070400@intalio.com>
To: Daniel_Austin@grainger.com
CC: public-ws-chor@w3.org

Daniel_Austin@grainger.com wrote:

><mission statement group = "ws-chor" type="CSF level 0" version = "1.0">
>The mission of the Web Services Choreography Working Group at W3C is to
>specify the means by  which Web Services may collaborate with external
>systems, specifically in the composition of multiple services and the
>sequencing of messages among them.
></mission statement>
>
I have a few comments on the specifics of the definition, but what I 
like about this definition is that it's so generic that it allows us to 
consider alternative outputs. Back in May, Mike Champion proposed the 
idea (quoted below) that we specify the way in which existing 
technologies should be used to handle choreographies. Considering all 
the discussions we've had on WSDL yes/no, XSDL good/bad, pi-calculus vs 
no-calculus, best practice and implementation nightmares, I think doing 
just that would by itself offer tremendous value to the community.

3. Basically do what WS Aarchitecture should do but doesn't really have the
focus or the expertise to do well: Make sense out of the bleedin' nightmare
that is WS Choroegraphy  / Orchestration / Business Process Execution /
Business Process Description / Workflow / etc.  Define the principles,
describe how they apply to the various "standards" out there now or in
production, and generally act as a referee in the food fight that is going
on.


><mission statement group = "ws-chor" type="CSF level 0" version = "1.1a">
>The mission of the Web Services Choreography Working Group at W3C is to
>specify one or more XML-based languages building on the foundation of WSDL
>1.2 to provide interoperability among Web Services in their communications
>and ordering of events.
></mission statement>
>  
>
That definition is not bad, just a bit too generic. WS-RM.1 and WS-RM.2 
already do that ;-)

arkin

><mission statement group = "ws-chor" type="CSF level 0" version = "1.1b">
>The mission of the Web Services Choreography Working Group at W3C is to
>specify the means by which Web Services interoperate, how composition of
>Web Services is performed, and how the sequencing of events among services
>may be regulated to ensure interoperability.
></mission statement>
>
>
>As always, just my US$0.02, YMMV.
>
>Regards,
>
>D-
>*************************************************
>Dr. Daniel Austin
>Sr. Technical Architect / Architecture Team Lead
>daniel_austin@notes.grainger.com <----- Note change!
>847 793 5044
>Visit http://www.grainger.com
>
>"If I get a little money, I buy books. If there is anything left over, I
>buy clothing and food."
>-Erasmus
>
>  
>


-- 
"Those who can, do; those who can't, make screenshots"

----------------------------------------------------------------------
Assaf Arkin                                          arkin@intalio.com
Intalio Inc.                                           www.intalio.com
The Business Process Management Company                 (650) 577 4700


This message is intended only for the use of the Addressee and
may contain information that is PRIVILEGED and CONFIDENTIAL.
If you are not the intended recipient, dissemination of this
communication is prohibited. If you have received this communication
in error, please erase all copies of the message and its attachments
and notify us immediately.
Received on Tuesday, 3 June 2003 23:44:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 01:00:21 GMT