- From: Mark Baker <distobj@acm.org>
- Date: Tue, 6 Jul 2004 15:28:22 -0400
- To: David Orchard <dorchard@bea.com>
- Cc: www-ws-arch@w3.org
On Tue, Jul 06, 2004 at 11:41:39AM -0700, David Orchard wrote: > Either it's OK to create URIs on the client, or not. It's ok. > For a client to create a URI, it needs data + metadata on how to create the URI. By definition, if the client doesn't know the URI construction rules metadata, it can't construct a URI. Hence Google, or any other site for that matter, can never construct a client side URI without the metadata/algorithm. Correct. > Whether the metadata or URI is sent as a response to a request (your HEAD + InterfaceDescription header response), or as a normative specification asserted by the authority ( it supports ?wsdl), is optimization. I believe that to be incorrect; REST requires the former, and precludes the latter. It is also not optimization, it is architecture; the former has superior visibility and evolvability properties than the latter, since it's possible for new relationships between resources to be communicated without requiring software modifications; something that isn't possible if the relationship is declared in some separate specification. Mark. -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca Seeking work on large scale application/data integration projects and/or the enabling infrastructure for same.
Received on Tuesday, 6 July 2004 15:28:02 UTC