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 as if an implementation of XPath in Xerces-proper will
be free of overhead.  However, the choice is certainly yours.

Dave



                                                                                       
                       
                    Don Mastrovito                                                     
                       
                    <dmastrovito@marathontechnol        To:     
[EMAIL PROTECTED]                   
                    ogies.com>                          cc:     (bcc: David N 
Bertoni/CAM/Lotus)              
                                                        Subject:     RE: Xerces-C 
XPath module                
                    11/08/2001 10:38 AM                                                
                       
                    Please respond to                                                  
                       
                    xerces-c-dev                                                       
                       
                                                                                       
                       
                                                                                       
                       



I agree with Martin and Chris.  I'd like to be able to do a simple XPath
query on a DOM tree.  I grew used to having that ability with MSXML.  Quite

frankly, it's hard to justify the added overhead of Xalan in this
situation.

Don

At 03:27 PM 11/8/2001 +0000, you wrote:
> > 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 internally for a while and have found many
>handy uses for it. For example, we have a 'grep' like tool which takes an
>XPath expression and an XML document, and returns all the matched nodes.
>         This implementation also conforms to the W3C's DOM3-XPath
>Specification Working Draft. It allows people to experiment with this
>spec. As well, it supports namespace nodes, which I believe Xalan doesn't
>support.
>         The suggestion of it being used as a basis for XQuery is
>interesting. We have our own XML-based scripting language that uses this
>module, so I can see it being as a basis for XQuery.
>         Our implementation is also bison/flex based, and so might be
>easier to develop and bug fix, if need be.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to