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

Re: Simple Choreography composition suggestion

From: Steve Ross-Talbot <steve@enigmatec.net>
Date: Fri, 18 Jul 2003 09:32:31 +0100
Cc: Ugo Corda <UCorda@SeeBeyond.com>, Assaf Arkin <arkin@intalio.com>, public-ws-chor@w3.org
To: "Cummins, Fred A" <fred.cummins@eds.com>
Message-Id: <5F70FB6E-B8FA-11D7-BE6A-000393D13C9A@enigmatec.net>

+2

On Thursday, July 17, 2003, at 10:02  pm, Cummins, Fred A wrote:

>
> Ugo,
>
> This seems to suggest that a choreograpy defines, or
> may define a web service.  On the contrary, I see
> a choreography as defining relationships between
> web services.
>
> Fred
>
>> -----Original Message-----
>> From: Ugo Corda [mailto:UCorda@SeeBeyond.com]
>> Sent: Thursday, July 17, 2003 1:07 PM
>> To: Assaf Arkin
>> Cc: public-ws-chor@w3.org
>> Subject: RE: Simple Choreography composition suggestion
>>
>>
>>
>>> A choreography as I understand if is a Web service only if
>> it has an
>>> entry point that is used by someone outside the
>> choreography to start
>>> it. If the choreography starts when A sends a message to B (A and B
>>> being roles covered by the choreography), then it's not a
>> Web service.
>>> But if the choreography starts by someone sending a message
>> to A, where
>>> that role is not otherwise covered by the choreography, then that
>>> choreography is a Web service. It has an externally
>> accessible entry
>>> point, or any other term we may opt to use.
>>>
>>> Since it's a Web service, it can further be used in a larger
>>> choreography that may or may not be a Web service. Such a
>> choreography
>>> would cover that additional role that starts the Web
>> service choreography.
>>
>> Yes, that's basically the point I was making with my BPEL example.
>>
>> It seems to me that, since choreographies are "made" of Web
>> services, establishing this relationship between a
>> choreography and the Web service that "encapsulates" that
>> same choreography (if any) would provide a way of talking
>> about choreographies composition.
>>
>> Ugo
>>
>>
>
> 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 Friday, 18 July 2003 04:32:37 GMT

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