- From: Assaf Arkin <arkin@intalio.com>
- Date: Tue, 03 Jun 2003 00:56:15 -0700
- To: Hao He <Hao.He@thomson.com.au>
- CC: "Cutler, Roger (RogerCutler)" <RogerCutler@chevrontexaco.com>, www-ws-arch@w3.org
Hao He wrote: ><hh>Well said. In a company environment or even cross-company situation, >people have detailed ideas about web applications they already have and >those to be built. In those cases, they know exactly what they will get >from their HTTP responses. </hh> > > ><hh>I think many of us agreed sometime ago that by exchanging design >documents among developers is also one form of publish and discovery. </hh> > > I agree. I use the term publish and discovery very liberally and exchanging design documents falls in this category. And knowing what the service does a priori is also an option. But now the question becomes, how do you scale that to a larger Web of services. If you exchange design documents or you know all the details by some other means then you can't grow organically. Think what the World Wide Web would be if each server used its own variant of HTTP, or if you have URLs but no way of linking from HTML pages. When you describe a Web you describe something that grows organically and that means it has to interoperate in very specific ways. A service for which you know the definition is a service, but is there anything Web-like about it? arkin >Hao > >
Received on Tuesday, 3 June 2003 03:56:41 UTC