OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] XPath and XPattern (was Re: [xml-dev] More on taming SAX)

[ Lists Home | Date Index | Thread Index ]



> But when considering /foo/bar[baz3="test"]/baz1
> <foo>
>    <bar>
>      <baz1/>
>      <baz2/>
>      <baz3>test</baz3>
>    </bar>
> </foo>
> This predicate's value cannot be ascertained at the point of the baz1
> startElement event in a single event look ahead model. At least that is
> what I heard through the grapevine.

That is correct. The earlier drafts of STXPath disallowed the child
axis in predicates, allowing only ancestor:: and parent::. I don't
know when this was changed, or what the rationale is.. or whether it
is enforced through a static semantic constraint to simplify the
grammar. I vaguely remember something about user convenience, and
making sure people don't have to write backwards paths (because an
absolute path starting with / can be matched in a predicate).



News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS