Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xml-dev] Disk-based XPath Processing

From: "Michael Kay" <mike@--------.--->
To: "'Tatu Saloranta'" <cowtowncoder@-----.--->,"'Philippe Poulard'" <Philippe.Poulard@------.-----.-->,"'Uche Ogbuji'" <uche@------.--->
Date: 10/3/2006 8:07:00 AM
> On a related note: I noticed a reference (from Saxon-SA page, 
> I think) that implied that w3c schema specifies a n xpath 
> subset (perhaps for defining how key constraints can be 
> defined using subset of xpath?), like one that would be 
> useful for streaming access.
> Is this true?

This subset is specified at
http://www.w3.org/TR/xmlschema-1/#c-selector-xpath

(Actually it's two slightly different subsets, one for selectors and one for
fields. The general form of a uniqueness constraint in XML Schema is "within
every element E, each S must have a unique value for F": for example, within
every location, each employee must have a unique value for employee-number.
The "selector" is used to select S from E, the "field" is used to select F
from S.) 

The subsets are woefully small, unfortunately.

> Or are there other formal subset specifications, to make it 
> easier to know exactly what subset is (guaranteed to be) 
> supported by an implementation?

There are lots of academic papers on streaming XPath that have implemented
the parts of XPath that the researchers knew how to implement and left out
the bits they didn't (such is the privilege of academics). They aren't all
very good at revealing which bits they left out, but I don't think you'll
find one that can do preceding-sibling::*[3] or
following-sibling::*[last()-1].

Michael Kay
http://www.saxonica.com/


transparent
Print
Mail
Like It
Disclaimer
.

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 www.altova.com/list/index.html. 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.

.
.

transparent

transparent