Re: XML/XSL on the client for dynamic UI

DOM2 is only in working draft stage so why does this need to wait for DOM3?
XSL is gaining in popularity rapidly and not having sufficient DOM support
is a major drawback. Every single one of the XSL implementations has needed
to make their own private DOM.

It is very inefficient for server to build a tree in the standard DOM and
then walk it and send SAX events just to create another version of the same
tree. It would be best for XSL if this issue was addressed sooner rather
later after XSL has spread into everybody's app servers.

Is the W3C open to input on this subject?
Is it controversial to add XPath support to DOM2?
Can the developers of the XSL implementation agree on what is needed?
Is the W3C doing this and us outsiders just can't see what is going on?

Jon Smirl
jonsmirl@xxxxxxxxxxxx



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list