RE: FW: adding addressing capabilities to the DOM

>
> Caveat: You're going to get strong pushback if you advocate the use of
> NodeLists for this purpose.  Remember, the Traversal chapter was
> originally
> designed specifically because we wanted better return objects for queries
> and other filtered views. Some of us VERY strongly prefer these to
> NodeLists.
>

I think it's a great idea to combine XPath with the Traversal API (maybe as
a parameter type to createNodeIterator/createTreeWalker). Nevertheless, it
would also be useful as part of the Core API. This way it doesn't place as
big of a burden on implementations that don't wish to address the Traversal
API. I see NodeList as a very *natural* implementation of the XPath node-set
abstraction. I don't see why you would need or want anything more in this
case.

XPath expressions accomplish the same purpose as a custom NodeFilter without
explicitly writing the code. XPath users only care about the result node-set
from the expression.

-aaron

Received on Monday, 17 April 2000 21:47:02 UTC