W3C home > Mailing lists > Public > www-tag@w3.org > January 2003

Re: Options for dealing with IDs

From: Jeni Tennison <jeni@jenitennison.com>
Date: Fri, 10 Jan 2003 15:29:20 +0000
Message-ID: <15022270623.20030110152920@jenitennison.com>
To: Chris Lilley <chris@w3.org>
CC: Robin Berjon <robin.berjon@expway.fr>, www-tag@w3.org

Hi Chris,

> On Thursday, January 9, 2003, 1:50:54 PM, Robin wrote:
> RB> Another issue is that they are normally (in all cases I've seen
> RB> them used in at least) sensitive to the default namespace.
>
> Sensitive in that they can't use it?

Sensitive in that they *do* use it. If, in XML Schema, you have:

<schema xmlns="http://www.w3.org/2001/XMLSchema">
  <element name="foo" type="string" />
</schema>

the type attribute holds an QName; the default namespace is used when
interpreting this QName; since the value of the type attribute doesn't
have a prefix, the processor uses the default namespace and recognises
the value of the type attribute as being
{http://www.w3.org/2001/XMLSchema}string.

This differs from XPath where the default namespace is *not* used to
resolve prefix-less QNames.

It sounds as if you're saying that the default namespace would not
apply when interpreting the value of the xml:idAttr attribute. This
means that the value of the xml:idAttr is not an xs:QName (per XML
Schema's definition), but a NameTest (per XPath's definition).

Cheers,

Jeni

---
Jeni Tennison
http://www.jenitennison.com/
Received on Friday, 10 January 2003 10:30:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:15 GMT