Lists Home |
Date Index |
Paul Prescod wrote:
> Jonathan Borden wrote:
> > Yeah. What I understand is that the ability to locally bind namespaces
> > critical to the ability to stream process XML document composition, an
> > element can define its own namespace prefix binding context. We recently
> > went over this when I declared a namespace best practice of declaring
> > namespace bindings at the root element. ...
> Remember we just had an argument about whether to design for the common
> case or the special case? Have you ever done this in an application? I
> haven't. Still, every XML application in the world must handle namespace
Hey, I was the one who declared it against best practice. No I haven't done
this either, but then again despite the fact that I don't speak Python
either, I am genuinely glad it exists for those people who use it.
I think this is all water over the dam (or is that under the dam, hmmmph?)
the fact is that usage of QNames in attribute values is a fact of life and
has been since XSLT 1.0. I _have_ dealt with these issues when writing XSLT
transforms, and they can be a pain, yet the issues also can be dealt with. I
suppose the takehome message is that you cannot blindly rename prefixes,
even though this is against the intentions of XML namespaces, unless you can
be sure that the content of attributes will not be affected. Oh well.