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

Re: Revised: Mission Statement

From: Steve Ross-Talbot <steve@enigmatec.net>
Date: Sun, 6 Jul 2003 19:12:29 +0100
Cc: Nickolas Kavantzas <nickolas.kavantzas@oracle.com>, "Cummins, Fred A" <fred.cummins@eds.com>, Martin Chapman <martin.chapman@oracle.com>, "Yaron Y. Goland" <ygoland@bea.com>, public-ws-chor@w3.org
To: "Monica J. Martin" <monica.martin@sun.com>
Message-Id: <67BD94BC-AFDD-11D7-A96F-000393D13C9A@enigmatec.net>

Can't come up with any concrete issues with this. But I do have a 
question for the community at large.

I'm in the process of doing the requirements document with Daniel, Ed 
and Abbie. On my metaphorical travels I have yet to see a use case in 
support of composition that results in a web service. If a choroegraphy 
is created from some number of web services, then what would it's WSDL 
interface be? Is it some subset of the WSDL operation that are 
advertised by the web services that were directly used to construct it? 
Is it the same as this set of WSDL operations? Is it a subset of the 
operations of all the web services (direct and indirect) that were used 
to construct it?

My own thoughts are that there must be a scoping function that renames 
or hides operations that are offered by a choreography. It may be the 
case that it is a function of the events/messages that start a 
choreography. Any suggestions as to how to clear this up and make it 
fairly tight and yet expressive enough for the job?

Cheers

Steve T

On Sunday, July 6, 2003, at 06:48  pm, Monica J. Martin wrote:

> Nickolas Kavantzas wrote:
>
>> During the Chicago F2F, the W3C Choreography Group agreed and later 
>> presented to the BPEL TC chairs its mission statement.
>> This statement was presented by the BPEL TC chairs to the BPEL TC 
>> members, in last week's BPEL TC conf-call.
>>
>> I think we may want to revisit it only when we have a better 
>> understanding on the use cases and requirements, and have made some 
>> progress on the harvesting fronts. Then questions like 'what 
>> semantics of web services really means' will become more easier for 
>> us to answer.
>>
> mm1: +1, considering we have multiple types of composition, and have 
> not addressed which we will include within our scope (note previous 
> message on some definitions we have discussed and have been included 
> in the glossary).
>
> Has everyone considered the proposed overall definition I provided?
>
> **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 and doesn't specify the mechanism used for 
> composition (how).
>
>
>
>
> 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 Sunday, 6 July 2003 14:11:17 GMT

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