Lists Home |
Date Index |
>I _think_ it's because of QNames in attribute/element values
Yes. If QNames were only used for element and attribute names, they
could be (as indeed they are) resolved at parse-time and there would be
no need to keep the prefix -> namespace-name map around afterwards.
But many systems build on top of XML+namespaces - notably XPath - want
to interpret QNames in element content and attribute values, so the
map has to be available in some form or other. (There is of course
no need to use the Infoset's description of [in-scope namespaces] as
an implementation specification!)
To get around this, you would have to either
- not use QNames in content, but use some more direct form such as
- be able to reliably recognise QNames in content (e.g. a hypothetical
version of XML might have a syntax for it).