• To: <lists@j...>,"'Uche Ogbuji'" <uche.ogbuji@f...>
• Subject: RE: More on taming SAX (was Re: ANN: Amara XML Toolkit 0.9.0)
• From: "Michael Kay" <mike@s...>
• Date: Thu, 23 Dec 2004 19:35:05 -0000
• Cc: <xml-dev@l...>
• In-reply-to: <41CB11D1.50600@j...>
• Thread-index: AcTpH4uvjbQ2lbi+SUGxlhEsLOvysgABphkg

> So when the event stream reached /foo/bar2/baz2/text() you would have 
> the following in a DOM like structure:
> 
>    foo
>      \
>       bar1 (... no children)
>       bar2
>         \
>          baz1 (... no children, just the previous sibling and attrs)
>          baz2 (only the StartTag)
> 
> I am not sure that the preceding siblings would be very 
> useful and have 
> more chances for pathological cases but when I construct 
> mini-trees this 
> is the subset I find handy. 

This is exactly what I did in early versions of Saxon, in the pre-XSLT days
when it was an entirely serial event-based processor. It worked quite well -
but eventually I decided you couldn't mix this with XSLT processing in the
same framework, and scrapped it for that reason.

Michael Kay

• References:
  • Re: More on taming SAX (was Re: ANN: Amara XMLToolkit 0.9.0)
    • From: Jeff Rafter <lists@j...>

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