Lists Home |
Date Index |
> > In other words, what should happen is that any code that moves DOM to
> > some other model such as SAX, XPath, or a text file should insert the
> > necessary namespace declarations. What actually does happen though,
> > is that such code often neglects to insert them ...
> The only sane approach I've found is to use a visitor class to traverse
> the document and maintain a list of namespace declarations that have
> been made, so that when a new declaration is needed, it appears.
Permit me to disagree that's the "only" sane approach.
Counter-example: SAX pipeline components can monitor namespace
usage and declarations, patching in new prefix declarations as needed.
I happen to prefer that approach; it's generally useful, since DOM isn't
the only framework that's "low fidelity" with respect to such information.
Components like that (not necessarily, or IMO desirably an XMLFilter)
are good to re-use...