- From: Mark Baker <distobj@acm.org>
- Date: Thu, 14 Mar 2002 19:33:16 -0500 (EST)
- To: Hao.He@thomson.com.au (Hao He)
- Cc: www-ws-arch@w3.org
This is an excellent comment. It's analogous to how Web resources aren't limited to identifying "documents", but can instead identify anything with identity (people, places, things). The "documents" are representations of the things with identity, not the things themselves (except when the document really is the thing 8-). But tather than try and get concensus on a change now though, so soon after we reached concensus on the current working definition, I suggest we keep this potential addition in mind for the next iteration. > Currently, both definitions define web services as a software component. > > This may sound silly but a web service to me is just a service. It may be > provided by one or more software components or even by people but it is not > the component itself. For example, when one wants to convert a doc into xml > using a web service, the person does not really care whether the conversion > is done by a software component or a group of people. > > The question is: do we really care if a web service is a service or a > software component? IMHO, we do. The former prompts light binding and loose > coupling while the later encourages more traditional RPC way of thinking. > > Please shine your thoughts on this subject. MB -- Mark Baker, Chief Science Officer, Planetfred, Inc. Ottawa, Ontario, CANADA. mbaker@planetfred.com http://www.markbaker.ca http://www.planetfred.com
Received on Thursday, 14 March 2002 19:28:47 UTC