• To: Dare Obasanjo <dareo@m...>
• Subject: Re: What should TrAX look like? (Was: Re: Articleon JAXP 1.3 "Fast and Easy XML Processing")
• From: Elliotte Harold <elharo@m...>
• Date: Thu, 17 Feb 2005 13:20:34 -0500
• Cc: XML Developers List <xml-dev@l...>
• In-reply-to: <830178CE7378FC40BC6F1DDADCFDD1D1027673D5@R...>
• References: <830178CE7378FC40BC6F1DDADCFDD1D1027673D5@R...>
• User-agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041217

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  elharo@m...
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim

• References:
  • RE: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
    • From: "Dare Obasanjo" <dareo@m...>

• Prev by Date: RE: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
• Next by Date: Re: What should TrAX look like? (Was: Re: Articleon JAXP 1.3 "Fast and Easy XML Processing")
• Previous by thread: RE: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
• Next by thread: RE: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
• Index(es):
  • Date
  • Thread