Lists Home |
Date Index |
> > yes, if the value has been blindly copied by an application
> that didn't know
> > that the value had a dependency on the context. That's
> exactly what the
> > whole XSLT-namespace problem is about.
> yes, but what value has been "blindly copied". where those attributes
> values or element content which are declared to be in the QName domain
> are processed in the parser's context, there are no lexical values -
> which could exhibit a dependancy - to copy. where the application
> introduces values it must introduce values in the correct domain.
What has been blindly copied is a text node.
(a) XML Schema wasn't around at the time XSLT was invented
(b) Even if it were, there is even today no way to declare an attribute as
containing an "XPath expression" (or a "list of namespace prefixes", to take
another example that XSLT uses).
A solution based on declaring those elements or attributes that contain
namespace prefixes in their content might have been workable if it had been
invented at the start. It now falls into the category of 20:20 hindsight.