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

RE: Revised: Mission Statement

From: Martin Chapman <martin.chapman@oracle.com>
Date: Tue, 1 Jul 2003 12:27:46 -0700
To: "Steve Ross-Talbot" <steve@enigmatec.net>, "Yaron Y. Goland" <ygoland@bea.com>
Cc: <public-ws-chor@w3.org>
Message-ID: <PEEBJKKCFNCENDPJDEMICEFEDGAA.martin.chapman@oracle.com>

I thought by our discussion at the F2F that the "in the middle of all of
them" is not what we are after, and in effect equates to the O word. So I
would be interested in a better understanding of what composition means,
given that this approach would not really support a wrapper wsdl. I'm not
arguing against composition here, just asking for some clarity.

Martin.

> -----Original Message-----
> From: public-ws-chor-request@w3.org
> [mailto:public-ws-chor-request@w3.org]On Behalf Of Steve Ross-Talbot
> Sent: Tuesday, July 01, 2003 10:52 AM
> To: Yaron Y. Goland
> Cc: public-ws-chor@w3.org
> Subject: Re: Revised: Mission Statement
>
>
>
> +1
>
> Having some understanding of the achitecture of this thing that we are
> doing
> would help us stay on the same page.
>
> If we have a global model then where does it sit with respect to any N
> participants.
> Is it in the middle of all of them?
> Is it at each one's site?
> Is it a proxy sort of thing?
> Is it a web service itself?
>
> What happens when we have two of them and we wish to compose?
> What happens to the originals?
> Where does the new one reside?
>
> I could go on. It would just be nice to get a common understanding. I
> have mine
> but I'm not sure it's the same as other peoples.
>
> Cheers
>
> Steve T
>
> On Tuesday, July 1, 2003, at 06:33  pm, Yaron Y. Goland wrote:
>
> >
> > 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
> >>>
> >>
> >>
> >
> > This email is confidential and may be protected by legal privilege. If
> > you are not the intended recipient,  please do not copy or disclose
> > its content but  delete the email and contact the sender immediately.
> > Whilst we run antivirus software on all internet emails we are not
> > liable for any loss or damage. The recipient is advised to run their
> > own antivirus software.
> >
>
> This email is confidential and may be protected by legal
> privilege. If you are not the intended recipient,  please do not
> copy or disclose its content but  delete the email and contact
> the sender immediately. Whilst we run antivirus software on all
> internet emails we are not liable for any loss or damage. The
> recipient is advised to run their own antivirus software.
>
>
Received on Tuesday, 1 July 2003 15:28:32 GMT

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