[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: XPath and XPattern (was Re: More on taming SAX)

• To: Michael Kay <mike@s...>
• Subject: Re: XPath and XPattern (was Re: More on taming SAX)
• From: Wolfgang Hoschek <whoschek@l...>
• Date: Thu, 23 Dec 2004 15:27:46 -0800
• Cc: <xml-dev@l...>, "'David Megginson'" <david.megginson@g...>
• In-reply-to: <E1ChbCh-0006NX-00@u...>
• References: <E1ChbCh-0006NX-00@u...>

For what it's worth, there's some documentation on 
applicability/limitations/usage scenarios of a streaming path filter at 
http://dsd.lbl.gov/nux/api/nux/xom/xquery/StreamingPathFilter.html

It's pretty much one of the simplest approach one could possibly take 
but nonetheless quite useful.

It supports the child axis only, but hands fully built element subtrees 
to an application defined callback handler, which makes writing even 
complex handlers rather straightforward.

Wolfgang.


On Dec 23, 2004, at 2:12 PM, Michael Kay wrote:

>> There's also the question of context -- would the only context be the
>> stack, or do people hope to have access to left siblings as well?
>
> I found it very useful also to have a one-event lookahead.
>

• Follow-Ups:
  • Re: XPath and XPattern (was Re: More on tamingSAX)
    • From: Uche Ogbuji <Uche.Ogbuji@f...>

• References:
  • RE: XPath and XPattern (was Re: More on taming SAX)
    • From: "Michael Kay" <mike@s...>

• Prev by Date: Re: XPath and XPattern (was Re: More on taming SAX)
• Next by Date: Re: XPath and XPattern (was Re: More on taming SAX)
• Previous by thread: Re: XPath and XPattern (was Re: More on taming SAX)
• Next by thread: Re: XPath and XPattern (was Re: More on tamingSAX)
• Index(es):
  • Date
  • Thread