W3C home > Mailing lists > Public > www-tag@w3.org > July 2002

TAG Finding: Using Qualified Names (QNames) as Identifiers in Content

From: Michael Kay <michael.h.kay@ntlworld.com>
Date: Tue, 9 Jul 2002 10:14:24 +0100
To: <www-tag@w3.org>
Cc: <DPawson@rnib.org.uk>
Message-ID: <000701c22729$04f431d0$6401a8c0@pcukmka>

I have just read this [1], thanks to Dave Pawson who drew it to my

The document takes a reasonably pragmatic approach, recognizing that the
horse has already bolted and it's too late to lock the door.

I think that identifying QNames using the schema type xs:QName is a very
partial solution, as the document notes, it fails to catch many cases
where QNames (or more generally, namespace prefixes) are used in element
and attribute content.

A more powerful approach would be for XML Schema to introduce a boolean
facet, "uses-namespace-prefixes", which could be attached to any value
that depends on the namespace context. This still doesn't fix the whole
problem, of course, because when copying such a value you still don't
know precisely which namespaces it depends on, so you have to copy them
all, just in case. But at least it would indicate that copying the value
without the namesapce context is unsafe, as is changing namespace

Another way of mitigating the problem is to define a lexical
representation of the value space of QNames, for example the form
"{namespace-uri}local-name", that is independent of the namespace
declaration context. (The above form has been adopted in the Java JAXP
interface.) If this form were accepted in any context where a QName is
allowed (including perhaps even XML element and attribute names!) many
of the problems of context-dependency could be solved more easily, for
example this could form the basis of a context-free syntax for XPath

Michael Kay

[1] http://www.w3.org/2001/tag/doc/qnameids
Received on Tuesday, 9 July 2002 05:12:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:55:52 UTC