Lists Home |
Date Index |
Dare Obasanjo wrote:
> What you've described is akin to the IXPathNavigable interface which is the primary input of the XslTransform class that Michael Kay was deriding. The other input overloads to the method are primarily for usability (XmlReader, string, etc) as opposed to being an implication that there is some fundamental missing abstraction in the .NET model.
That may also be similar to the Jaxen Navigator interface, though so far
that's only been implemented on top of tree-models. I don't think
anyone's tried to implement a SAX navigator. I wonder if that could be
done? Probably only by building an intermediate tree representation first.
Elliotte Rusty Harold email@example.com
XML in a Nutshell 3rd Edition Just Published!