Re: XSL and the DOM
From: Kay Michael <Michael.Kay@xxxxxxx> > There were two main reasons I moved away from using DOM as my native tree > format in SAXON: firstly, the lack of extensibility (no standard way of But that's my point. DOM2 is in working draft stage currently and it doesn't seem to be addressing any of the needs of the XSLT implementers. DOM2 appears to be focused on the browser DOM not the server-side DOM. Core DOM2 should have XPath support. A node extensibility mechanism would be good too. What other things are missing? Are the W3C members working one XSLT taking to the DOM2 group? As an XSLT user I'm not happy with this situation since it forces me to build a tree one way and then convert it to SAX events just to build the tree again another way. Jon Smirl jonsmirl@xxxxxxxxxxxx XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format