You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by il...@ca.ibm.com on 2002/10/21 23:45:53 UTC

Do we need the org.w3c.dom.xpath package?

Hi,

The org.w3c.dom.xpath package contains the DOM L3 XPath API interfaces.  It
is not built in any targets.

I was thinking of deleting this package from XalanJ.   We have another copy
of these interfaces in the org.apache.xalan.dom3.xpath package. The
prototype implementation of the API is in the org.apache.xpath.domapi
package and uses the org.apache.xalan.dom3.xpath package. The reason the
renamed package is used is to avoid any conflicts with other versions of
the API that may exist in the classpath of an application using Xalan.
This package is intended to be temporary until the DOM L3 XPath API
specification becomes a recommendation.  At that time, I think the
interfaces should be moved somewhere else (as org.w3c.dom.xpath), probably
to xml-commons.

Does anyone have concerns about the removal of org.w3c.dom.xpath package
from XalanJ?


 Ilene.



Re: Do we need the org.w3c.dom.xpath package?

Posted by Joseph Kesselman <ke...@us.ibm.com>.
Sounds good to me, pending DOM XPath becoming a REC and our cutting over 
to it at that time.

______________________________________
Joe Kesselman  / IBM Research