W3C home > Mailing lists > Public > public-ws-chor@w3.org > February 2004

Choreography and Semantic Web thoughts and ideas

From: Steve Ross-Talbot <steve@enigmatec.net>
Date: Mon, 2 Feb 2004 20:24:23 +0000
Message-Id: <CA5CF017-55BD-11D8-8439-000393D13C9A@enigmatec.net>
Cc: WS Choreography (E-mail) <public-ws-chor@w3.org>
To: <public-sws-ig@w3.org> <public-sws-ig@w3.org> <public-sws-ig@w3.org>

Dear colleagues,

Following on from an earlier email response to Dr. Dragoni Nicola I 
would like to raise some thoughts and ideas with respect to the work of 
the W3C Web Services Choreography working group.

Having spent the best part of one year scoping what the group is all 
about and, latterly, the last three months getting to grips with 
fundamental requirements and a base specification we are now far enough 
along the track to raise some thoughts and ideas with the IG.

The Choreography working group is specifying a language that describes 
the external observable interaction between peer-to-peer Web Services 
that act in concert to deliver some business goal. Central to this is 
the notion of a peer-to-peer global model in which no one party has 
overall control. A choreography description is just a description. It 
is not executable. However it plays a number of roles from the 
generation of code skeletons for prospective participants (that are Web 
Services) to being a potential input to tools that may execute at 
participant Web Service locations to enforce or monitor adherence to 
the choreography. In the latter sense a choreography description is a 
behavioral contract that is agreed to by the various participant 
organisations.

The first thought in all of this participants may change in 
choreography. That is a choreography is not bound to specific Web 
Service instances and can be reused against many candidate Web 
Services. One area of common interest is what properties should a 
choreography provide to help in the selection of Web Services that 
would like to participate in a choreography. We may, for example be 
able to offer properties such a lock freedom of any services 
participating in a choreography relative to each other. There could 
well be other properties too. In which case what role does a 
choreography play in Web Service selection - it too could be a property 
in and of it's own right.

As  early stabs in the dark the selection of a Web Service based on 
which choreographies it might be able to join (conformance to the 
contract) is perhaps a good place to start together with choreography 
location (since it may predicate service selection). Although the 
Choreography WG would be happy to entertain wider discussion.

Please ensure that any responses go to this list and 
public-ws-chor@w3.org.


Best Regards

Steve Ross-Talbot
Chief Scientist, Enigmatec Corporation
co-chair W3C Web Services Choreography
chair W3C Web Services Coordination


O: +44 207 397 8207
C: +44 7855 268 848
www.enigmatec.net

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 Monday, 2 February 2004 21:39:48 GMT

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