Hi Bob, > Definitely. Am already planning for the xpath impl to support > everything needed by a C14N impl. Ok. Could I help or should I try to get closer with XML Signature to build that on top of your Canonical implementation? > Just for clarification, is SAX-esque, not a SAX-basd xpath processor. > > It's for parsing stringified xpath expressions into an event/callback > model similar to the SAX API, but pretty much unreleated to SAX. Ah. You want to replace ANTLR with it, right? > Due to re-orderings/replacements of things in the XML stream, I don't > we can do a straight c14n filter on top of the SAX events. I think, > like XSLT, for the most part you need a fairly complete object-model. Agreed. > > Yah, I figure actually a C14N engine could eat a dom4j Document, > process it through the XPath engine, do some sorts and replacements, > and return the canonical dom4j Document. Cool. So we can apply the complete dom4j api on that canonical document and resue even the writer classes. -toby -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net -- GMX Tipp: Machen Sie Ihr Hobby zu Geld bei unserem Partner 1&1! http://profiseller.de/info/index.php3?ac=OM.PS.PS003K00596T0409a _______________________________________________ dom4j-dev mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dom4j-dev
