> -Original Message-
> From: Cornelius, Martin [mailto:[EMAIL PROTECTED]]
>
> IMHO, of course there is a need for this: There are many imaginable
> applications that need XPath to navigate documents but do not
> need XSLT. It may be possible to use the XALAN XPath component to navigate
> X
> > The Apache Xalan project already implements XPath, along with XSLT. Is
there
> > an advantage to incorporating another, either into Xerces itself, or
into
> > another Apache project?
>
> The advantage is when you want to use XPath on a DOM tree
without
> XSLT. We've been using this i
Developing a complete XPath implementation is a non-trivial task, and you
might soon find the "overhead" is equal to or exceeds the overhead of using
Xalan's XPath implementation. Not to mention the task of implementing
XPath/XQuery 2.0 when it reaches recommendation status.
After all, it's not
