• To: xml-dev@l...
• Subject: Re: QNames in attribute values
• From: Simon Fell <xml@z...>
• Date: Mon, 28 Jan 2002 13:25:11 -0800
• In-reply-to: <NEBBLOGPODFIFNJHLHBGAEBHEOAA.elenz@x...>
• References: <NEBBLOGPODFIFNJHLHBGAEBHEOAA.elenz@x...>

On Mon, 28 Jan 2002 13:09:55 -0800, in xml you wrote:

>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?


WSDL uses attribute values with QNames, and SOAP uses QNames in
element values.

Cheers
Simon

• References:
  • QNames in attribute values
    • From: "Evan Lenz" <elenz@x...>

• Prev by Date: QNames in attribute values
• Next by Date: Re: Auto-completion in editors (RE: ANN: XML Origin, the XML Editor & XSLT Debugger Released)
• Previous by thread: QNames in attribute values
• Next by thread: Re: QNames in attribute values
• Index(es):
  • Date
  • Thread