> isn't any application better off processing the specialized values in
> the parser's dynamic context than trying to resolve the conflicts
> inherent in dragging that context around indefinitely? from the
> descriptions which i have seen, the status of such values is known at
> the point where they are parsed. are there cases where that
> is not true?
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.
Michael Kay
Software AG
home:
work:
