Altova Mailing List Archives

Re: [xml-dev] ANN: xpath1() scheme for XPointer

From: Uche Ogbuji <uche.ogbuji@-----------.--->
To: "Simon St.Laurent" <simonstl@--------.--->
Date: 10/27/2002 12:07:00 AM
> At 02:33 PM 10/26/2002 -0400, Elliotte Rusty Harold wrote:
> >Another tricky bit about using XPaths on post-included documents is that 
> >you can get very different documents depending not only on whether the 
> >XIncludes are resolved but how the different fallbacks play out. The most 
> >obvious case is something like //chapter[1] which could select different 
> >chapters depending on which includes got resolved or not. Furthermore, 
> >they're a lot of XPath functions like string() or number() that take a 
> >node-set as an argument, but really only operate on the first node in that 
> >set, so which node is first can be very important, even if you don't see 
> >an explicit positional dependence.
> >
> >I also suspect the following, sibling, following-sibling, and 
> >preceding-sibling axes could well give significantly different results 
> >depending on which includes got resolved and which didn't. I don't think 
> >the ancestor, child, descendant, self, attribute, namespace etc. axes 
> >would be affected.
> I think I'm just going to have to note that these are possibilities in the 
> I-D, and let people sort them out in their own processing systems.

This is best.  After all, you needn't introduce XInclude to see the issues 
Elliotte mentions.  XML's optional entity and DTD processing puts paid to 
that.  The return value of count(@*) will never be an invariant across all 
XPath processors for a large class of docuemnts.  This fact has not, as far as 
I know, put anyone's eye out.

Uche Ogbuji                                    Fourthought, Inc.
Python&XML column: 2. Introducing PyXML -
The Past, Present and Future of Web Services 1 -
The Past, Present and Future of Web Services 2 - '
Serenity through markup -
Tip: Using generators for XML processing -


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.