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

RE: Revised: Mission Statement

From: Yaron Y. Goland <ygoland@bea.com>
Date: Tue, 1 Jul 2003 11:04:11 -0700
To: <Daniel_Austin@grainger.com>, <public-ws-chor@w3.org>
Message-ID: <GMEOJGJFKALPDCNPFMDOOEPLDEAA.ygoland@bea.com>

Since I don't know what it means to compose a web service I cannot agree
with you that it is a problem that needs to be solved.

> -----Original Message-----
> From: Daniel_Austin@grainger.com [mailto:Daniel_Austin@grainger.com]
> Sent: Tuesday, July 01, 2003 10:55 AM
> To: ygoland@bea.com; public-ws-chor@w3.org
> Subject: RE: Revised: Mission Statement
>
>
>
> 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.
>
> 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
>
>
>
>
>                       "Yaron Y. Goland"
>
>                       <ygoland@bea.com>         To:
> public-ws-chor@w3.org
>                       Sent by:                  cc:
>
>                       public-ws-chor-req        Subject:  RE:
> Revised: Mission Statement
>                       uest@w3.org
>
>
>
>
>
>                       07/01/2003 12:33
>
>                       PM
>
>
>
>
>
>
>
>
>
>
> 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
> with
> 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
> composition.
> > >  Monica
> > >
> >
> >
>
>
>
>
>
>
>
>
Received on Tuesday, 1 July 2003 14:04:13 GMT

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