Re: Paul has volunteered (was Re: Overloaded URIs must GO!)
> James said: > When I proposed pretty much the same thing to TimBL at WWW8, he didn't like [it], > Rohit Khare didn't like [it] and RK said Roy Fielding wouldn't like it. > Good luck, Paul :-) > > Didier says: > What did all these guys wouldn't like: > > a) the usage of URN? > b) the "hname" NID? They just didn't seem to have a problem with the notion that a single URL scheme would be used for both retrieving machine readable information and for an irretrievable unique name. I used the example of the XSLT namespace URI: http://www.w3.org/XSL/Transform/1.0 The URI above currently gives a 404. It is an irretrievable unique name. Point to note at this stage: I don't have a problem with irretrievable unique name URIs. *However*, I asked TimBL why on earth use an http URI for this. He and Rohit both chimed that, some time down the track, it will the URL for a document describing the namespace. I told them that my problem with that is that is then you have the *same* URI being used for both the namespace itself and a document describing the namespace. Both TimBL and Rohit (who invoked Roy Fielding's PhD thesis) said they didn't see that there was any distinction that warranted different URIs. It occurred to me that maybe namespaces were a bad example, so I used the example from the RDF model and syntax REC of an http URL being used to uniquely identify a person: http://www.w3.org/staffId/85740 That URI can be used in RDF to uniquely identifier someone. You can make assertions about that URI and thereby make assertions about the person. Fine, I can buy that. But is there a retrievable document at the end of that URL? If not, why use an http scheme? Ah, but there *will* be a document at the other end: something describing the irretrievable resource to which the URI refers. But hang on, how then do you distinguish between talking about the irretrievable resource (the person) and the document *about* the resource. What would it mean to assert the "Creator" of http://www.w3.org/staffId/85740 ? (Is it the creator of the document about the person or the Creator Himself :-) ?) I was arguing for a URI scheme that resembled http in it form but the was not designed to be retrieved. I was agnostic as to the actual scheme identifier but basically, "hname" is what I want. I want to be able to use hname://www.w3.org/staffId/85740 as my irretrievable resource to avoid confusion as to what it is I'm talking about when I make RDF assertions, etc. Maybe I've just missed something. When TimBL, Rohit Khare and (by proxy) Roy Fielding disagree with you on a URI matter, it is worth being nervous. JamesT xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1 To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format