I just posted a reasonably detailed overview of the situation.

http://lists.w3.org/Archives/Public/www-forms-editor/2002Jan/0005.html

.micah

-----Original Message-----
From: Evan Lenz [mailto:elenz@[...].com]
Sent: Monday, January 28, 2002 1:10 PM
To: xml-dev@[...].org
Subject: [xml-dev] QNames in attribute values


I believe that XSLT 1.0 was the original culprit, but I could be wrong. Now
XML Schemas, Canonical XML, and other specs rely on the prefixes and scope
of namespace declarations as significant information to be passed to the
application, rather than just a lexical mechanism to resolve element and
attribute names. This has introduced an amazing amount of complexity. In
fact, XML Namespaces are actually getting a worse rap than they deserve,
thanks to this increasingly common and fully-W3C-sanctioned practice.

Is it too late to fix this? W3C specs would have to change. My question is:
who else uses QNames in attribute values? Is there no turning back?

Note that there are precedents for application-level namespace declarations
(e.g. XPointer and XQuery).

Evan Lenz
XYZFind Corp.


-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org> , an
initiative of OASIS <http://www.oasis-open.org> 

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl> 

-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org> , an
initiative of OASIS <http://www.oasis-open.org> 

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>