W3C home > Mailing lists > Public > www-rdf-interest@w3.org > August 2001

Re: Using urn:publicid: for namespaces

From: Sean B. Palmer <sean@mysterylights.com>
Date: Tue, 14 Aug 2001 00:33:20 +0100
Message-ID: <03e301c12452$d4f79c80$43dd93c3@z5n9x1>
To: <kstar@cpan.org>
Cc: "Stephen Cranefield" <SCranefield@infoscience.otago.ac.nz>, <www-rdf-interest@w3.org>
> > TimBL even appears to believe (according to [1]) that
> > HTTP URLs can only identify generic documents, and
> > therefore all namespaces in HTTP space must end in a "#".
>     What is [1]?  You didn't appear to have a footnote in
>      your email.

Oops; many apologies.

[1] [[[
It is important, on the Semantic Web, to be clear about what is
identified. An http: URI (without fragment identifier) necessarily
identifies a generic document. This is because the HTTP server
response about a URI can deleiver a rendition of (or location of, or
apologies for) a document which is identified by the URI requested. A
client which understands the http: protocol can immediately conclude
that the fragementid-less URI is a generic document. This is true even
if the publisher (owner of the DNS name) has decided not to run a
server. Even if it just records the fact that the document is not
available online, still a client knows it refers to a document. This
means that identifiers for arbitrary RDF concepts should have fragment
identifiers. This in term means that RDF namespaces should end with
]]] - http://www.w3.org/DesignIssues/Fragment

Kindest Regards,
Sean B. Palmer
@prefix : <http://webns.net/roughterms/> .
:Sean :hasHomepage <http://purl.org/net/sbp/> .
Received on Monday, 13 August 2001 19:49:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:44:31 UTC