[
Lists Home |
Date Index |
Thread Index
]
> You agreed earlier with Jonathan that:
>
>> > What I said. The _namespace_ is the resource, the _namespace name_ is the
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> > identifier of the resource. Don't conflate the name with the thing.
No I only agreed with the last part (not conflating names with things)
I admit that that wasn't at all clear in the way I quoted it (although
it may have been clear from the rest of my message that I didn't agree
that the namespace is the resource)
> >From this I can only conclude that the URI must identify
> at least two *different* resources: one which is a namespace
> and another one which -- as you have asserted -- is not.
> Is that right?
Yes but using "identify" in that way makes it appear confusing as only
one of those 2 is identification in the sense of UR_I_.
The URI RFCs specify a mapping from strings (called URI references) to resources.
The Namespace Rec specifies a mapping from the same strings to namespaces.
(Given that one can say just about anything is a resource then one can
also say a namespace is a resource, but even if you do that the
second mapping is in principle a different mapping)
Both mappings are restricted to strings that obey the lexical
constraints on URI references. But they are different mappings.
http://www.example.com/example.html#
identifies (I think) the same resource as
http://www.example.com/example.html
as empty fragment identifiers are explictly mentioned in the URI specs
as refering to the base.
But the Namespace spec goes to some lengths to stress that the
namespaces named by these two strings are different.
You see the quoted "bottom line" has no weight
> Bottom line:
>
> well known URI: http://www.w3.org/1999/XSL/Transform
> what is the identified resource? surely the XSLT namespace (just ask the URI
> by GETting it -- it says so)
If I GET
http://www.w3.org/1999/XSL/Transform
then it says it is the XSLT namespace.
If I GET
http://www.w3.org/1999/XSL/Transform#
then it says the same thing.
The first one is right and the second one is wrong (try writing an XSLT
stylesheet with that namespace) I know which is right from reading the
XSLT REC, and that's the only way.
What I get back from dereferencing the namespace name as a URI
may be a hint as to what the namespace is about but it can, as
demonstrated, be wrong.
David
_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.
|
