- From: Mark Baker <distobj@acm.org>
- Date: Wed, 25 Feb 2004 15:08:42 -0500
- To: Jonathan Marsh <jmarsh@microsoft.com>
- Cc: www-ws-desc@w3.org
On Wed, Feb 25, 2004 at 10:48:18AM -0800, Jonathan Marsh wrote: > David's point about not actually munging the namespace URI is important > - the actual namespace URI may not be under the control of the author of > the WSDL. Whoa, I didn't realize that's what we were discussing. So you're saying that if I define a namespace; http://www.markbaker.ca/my-service/namespace/ and others want to create a revision of that, that they're going to mint markbaker.ca URIs like this; http://www.markbaker.ca/my-service/namespace/3/2/1/2/ If so, yuck, get your hands off my URIs[1]! 8-) That seems to be exactly what you're trying not to do when you wrote this (which I agree with completely); > We don't want to introduce a spec that forces > namespace URIs to be constructed in a way that violates the conventions > a domain owner may have in effect. If you want to do this in a more Web-friendly manner, I'd suggest treating the URIs as opaque and using the information returned from invoking GET on a URI to declare what other namespace it might be a revision of. For example, if this were a revision URI; http://joeschmoe.example.org/ns/2/3/1/4/ then a GET might return some RDF/RDDL with some embedded RDF which says; <Namespace rdf:about="http://joeschmoe.example.org/ns/2/3/1/4/"> <rdfs:subClassOf rdf:resource="http://www.markbaker.ca/my-service/namespace/"/> </Namespace> I *think* rdfs:subClassOf is the semantics you want, but if not, just define your own property, e.g. wsdl:revisionOf, or some such. [1] http://esw.w3.org/topic/UriSpaceSquatting Mark.
Received on Wednesday, 25 February 2004 15:07:40 UTC