- From: Mark Baker <distobj@acm.org>
- Date: Tue, 24 Sep 2002 01:41:55 -0400
- To: www-ws-arch@w3.org
Sorry, I figured we didn't want to talk about this ... > We will when someone responds effectively to the rest of Anne's point that > you didn't quote: "An SOA requires that a service be defined by a contract. > The Web has no such constraint. (HTTP GET tells an application how to get a > resource, but not how to use it once it has it.)" The Web is an SOA, it's just that all the services expose the same contract (I detect that this point isn't sinking in with people?). As I asked in my presentation, what is it about a generic interface that makes the service only fit for human consumption? Nothing, in fact. Tuples spaces have been used for app-to-app comms without anybody claiming that a human was required there. The point is that human or machine processability is a property of the contract *and* the information retrieved through it, not just the contract. So, on the Web, if you want a machine to be able to interact with a service, you just need to make sure your data is machine-processable. Or in other words, what's human-centric about the Web is HTML, not HTTP. MB -- Mark Baker, CTO, Idokorro Mobile (formerly Planetfred) Ottawa, Ontario, CANADA. distobj@acm.org http://www.markbaker.ca http://www.idokorro.com
Received on Tuesday, 24 September 2002 01:41:38 UTC