- From: Sean B. Palmer <sean@mysterylights.com>
- Date: Mon, 15 Oct 2001 16:58:04 +0100
- To: "Patrick Stickler" <Patrick.Stickler@nokia.com>
- Cc: <www-rdf-logic@w3.org>, <www-rdf-interest@w3.org>
> Following from all of the recent discussions regarding > literals and data types, [...] I humbly submit the attached > publication for your consideration and comments. The first thing of note is that it ignores the recent URI IG publication, by sticking to the classical view of URIs rather than the contemporary view:- [[[ Over time, the importance of this additional level of hierarchy seemed to lessen; the view became that an individual scheme does not need to be cast into one of a discrete set of URI types such as "URL", "URN", "URC", etc. Web-identifer schemes are in general URI schemes; a given URI scheme may define subspaces. ]]] - http://www.w3.org/TR/uri-clarification/ Also, you wrote:- [[[ URNs are similar to URLs in that they are expected to resolve to a web resource; ]]] I think that you should put "URNs are similar to URLs in that they are expected to identify a Web resource;" to reduce confusion. As to the URP/URT distinction, I guess that "data:" is a URP scheme then, yes? It beats the old "URL" definition that the RFC ascribes to it. Overall, I like the draft. > It is a working draft of a document that I eventually plan > to publish in more polished form, [...] You'll be wanting to do in plain text, then. This reminds me a little of my URN proposal for exivars. That didn't get very far, but is a valid principle, and one that RDF needs to be aware of: if it decides to use URI/URI-views for identifying resources, then it should fear the wrath of those those seek to encode it's idioms in new URI schemes. Cheers, -- Kindest Regards, Sean B. Palmer @prefix : <http://webns.net/roughterms/> . :Sean :hasHomepage <http://purl.org/net/sbp/> .
Received on Monday, 15 October 2001 11:59:03 UTC