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

RE: Revised: Mission Statement

From: <Daniel_Austin@grainger.com>
Date: Tue, 1 Jul 2003 12:54:37 -0500
To: ygoland@bea.com, public-ws-chor@w3.org
Message-ID: <OF0CAED4EC.1B1D00E5-ON86256D56.0061CC24@grainger.com>

Hi Yaron,

      I understand what you are getting at - however, at this point in
time, I don't think that anyone knows the scope of this aspect of our work.
I don't think it's important to know ahead of time. The Big-Design-Up-Front
methodology is broken; we need to do this iteratively, and leave the
mission statement with some "creative ambiguity" that leaves us room to
maneuver in response to the unknown.
When faced with an unknown problem domain, iterate, iterate, iterate - and
don't paint yourself into a corner. I have no idea just yet as to *how*
choreographies may be composed. But I do know that this is a necessary
problem to solve. I included it in the revised MS I sent out today.



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."

                      "Yaron Y. Goland"                                                                                          
                      <ygoland@bea.com>         To:       public-ws-chor@w3.org                                                  
                      Sent by:                  cc:                                                                              
                      public-ws-chor-req        Subject:  RE: Revised: Mission Statement                                         
                      07/01/2003 12:33                                                                                           

The key issue for me is what does it mean to compose a web service? Does
this mean a new WSDL with some computer behind it that then forwards
requests to existing web services? Does this mean that a client is expected
to send messages to different WS who all have some kind of relationship
each other? It's so vague that I'm not sure what scope we would be signing
up for.

> -----Original Message-----
> From: Monica J. Martin [mailto:monica.martin@sun.com]
> Sent: Monday, June 30, 2003 2:22 PM
> To: Yaron Y. Goland
> Cc: Francis McCabe; Burdett, David; Bonneau, Richard; Assaf Arkin;
> Jean-Jacques Dubray; public-ws-chor@w3.org
> Subject: Re: Revised: Mission Statement
> >
> >
> >Goland: I don't understand what the terms service composition
> and service semantics
> >mean. Could someone please define them? Monica provides a whole mess of
> >definitions but having 10 definitions is just as bad as having none.
> >
> >mm1:  The definitions were a compilation on various types of
> composition from the team.  We have not settled on one
> definition, although I have provided one below that seems
> appropriate here for consideration.  The definitions provided
> span different areas of composition, and whether the team agrees
> they are all the same, I can not speculate on.  I think it
> evidences the multiple levels of discussions that are occurring.
> Don't shoot the messenger. I would propose: **A service
> composition is a composition of services that results in a new
> service. The new service can be the combination of distinct parts
> to form a whole of the same generic type. The web services could
> be combined to achieve a specific goal.*  *This integrates parts
> of the definitions of recursive, web service and choreography
> >  Monica
> >
Received on Tuesday, 1 July 2003 13:55:49 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:01:00 UTC