• To: xml-dev@l...
• Subject: Re: XPath and XPattern (was Re: More on taming SAX)
• From: David Megginson <david.megginson@g...>
• Date: Thu, 23 Dec 2004 18:05:13 -0500
• Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=CGvcIqjbT8AGih65kkP0lrJwqCZWu2QumrPbH3rBwiR5Nr9MJPXJZdW9dKCw00ibzV/p/6V3Op3S/yEdBoVyqrxqD0tUibPvs7r77wfDtwdxMfCqssvFMoMgoh6cgfN1CtByS3rKenD6PmgeLqzNFOo6nJC9+WDvYsxGrr78WgA=
• In-reply-to: <E1ChbCh-0006NX-00@u...>
• References: <75cb920c041223124846b805a9@m...> <E1ChbCh-0006NX-00@u...>
• Reply-to: David Megginson <david.megginson@g...>

On Thu, 23 Dec 2004 22:12:57 -0000, Michael Kay <mike@s...> 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.

If there were a public XPath-subset streaming spec, maybe together
with a simply library, is that something Saxon might support, or have
you gone too far down the XSLT route now?


All the best,


David

-- 
http://www.megginson.com/

• References:
  • Re: XPath and XPattern (was Re: More on taming SAX)
    • From: David Megginson <david.megginson@g...>
  • 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 taming SAX)
• Index(es):
  • Date
  • Thread