- From: Vambenepe, William N <vbp@hp.com>
- Date: Wed, 25 Feb 2004 14:13:14 -0800
- To: "Mark Baker" <distobj@acm.org>, "Jonathan Marsh" <jmarsh@microsoft.com>
- Cc: <www-ws-desc@w3.org>
Hi Mark, > 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); Clearly this is not acceptable. The example I gave assumed that the same entity that produced the first WSDL (and has access to the domain name used for the namespace) produced the "versioned" WSDL. The way I understand versioning, this is the most common scenario. Someone who defined an interface later decides to update it with a new version. I can see some senarios where the "new" interface is defined by someone else, but at this point are we really talking about versioning or a more general concept of compatibility. I think this is stretching the definition of versioning. I would suggest (again) that people who need support for expressing relationships between services, between interfaces and between services and interfaces look into the work of the OASIS WSDM TC instead of trying to get this out of WSDL 2.0. In any case, if this was to be supported in WSDL, one could imagine a URI creation rule that would make me create a URI that looks like http://vambenepe.com/newVersionOfWSDL?base=http://www.markbaker.ca/my-se rvice/namespace/&version=3/2/1/2. So the URI would be in my domain but reference one in your domain. In any case, in no way do I suggest that people can create URIs without the agreement of the owner of the domain name used. Regards, William
Received on Wednesday, 25 February 2004 17:13:16 UTC