W3C home > Mailing lists > Public > www-tag@w3.org > April 2005

[httpRange-14] Namespace names, Namespace Documents and HTTP URI.

From: Williams, Stuart (HP Labs, Bristol) <skw@hp.com>
Date: Wed, 6 Apr 2005 14:53:20 +0100
Message-ID: <8D5B24B83C6A2E4B9E7EE5FA82627DC994B2FD@sdcexcea01.emea.cpqcorp.net>
To: <timbl@w3.org>
Cc: <www-tag@w3.org>

Hello Tim,

I'm curious about you view on the common use of #-less http URI to name
namespaces in *XML* documents. It seems to me that the deployment of
namespace documents at namespace URI is potentially just a problematic
(for you) as the deployment descriptive/depictive representations of a
material thing (person, dog, vase, car, brick, house...).  A picture of
a dog is not a dog. A namespace document is not a namespace.

Your position wrt to http URI to name namespaces in RDF, that they
should end in a '#' leads to a convenient distinction between the URI
(with the '#') which identifies the namespace and the same URI stripped
of the '#' to identify something else, most likely a
document/informationResource with RDF, RDDL, XML Schema or plain HTML
representations that describes the namespace.

These thoughts were prompted by Norm's recent posting [1] of a namespace
document for XSLT/Xquery functions and operators. Using the example from
his posting: if http://www.w3.org/2005/04/xpath-functions/#local-name
identifies a particular F&O function, what URI identifies the fragment
of text that my browser references when I dereference the URI above...
and of course,  because document does exist at the truncted URI its
media-type plays a role in determining what the full URI identifies.


[1] http://lists.w3.org/Archives/Public/www-tag/2005Apr/0028.html
Received on Wednesday, 6 April 2005 13:53:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:08 UTC