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

RE: Significant W3C Confusion over Namespace Meaning and Policy

From: John Boyer <JBoyer@PureEdge.com>
Date: Thu, 10 Feb 2005 09:22:42 -0800
Message-ID: <7874BFCCD289A645B5CE3935769F0B5275079B@tigger.pureedge.com>
To: <paul.downey@bt.com>, <www-tag@w3.org>
Cc: <derhoermi@gmx.net>

>I'm puzzled how XML base should change it's namespace given 
>it's the addition of a name into the reserved set of names 
>beginning with the characters 'x' 'm' 'l' that's at stake. 

Well, in trying not to repeat the entire thread that occurred
on the xml id list, I omitted this because I thought members
of the tag might be more aware of what the namespace rec 
says than others.

Does not reserve a set of names that begin with xml.  It
reserves a set of *namespace prefix* names that begin with
xml.  It does not reserve the list of names associated with the
namespace URI assigned to the prefix xml for future use of
xml-related specifications.

On the other hand the namespaces rec does define a namespace
as a collection of names plus a uri.  So whether or not the
uri changes when the list of names changes, the namespace is
changed when the list of names changes.

So, adding base or id to the xml namespace changes the namespace.

Now the separate discussion arises whether this should be allowed.

Thing is, the URI "identifies" the collection of names.  Since you 
can't have two different collections of names that are identical,
changing the collection of names should imply the obligation to 
change the URI too.  The W3C pub rules have supported this 
interpretation when it says that namespaces should not be changed
in this way in order to "give a specification the necessary stability."

John Boyer, Ph.D.
Senior Product Architect and Research Scientist
PureEdge Solutions Inc.
Received on Thursday, 10 February 2005 17:24:31 UTC

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