Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xsl] alternative to repeatedly walking the ancestor axis in 1.0

From: "Michael Kay" <mike@------------>
To:
Date: 8/4/2008 3:03:00 PM
> Out of interest, I wonder how in-scope-prefixes() works - 
> does any tree walking need to take place? 

I think that it's almost certainly the case that a system that explicitly
stores all the in-scope namespaces with every element is likely to be very
inefficient.

Saxon stores the differences between the inscope namespaces of an element
and those of the parent element (in effect, it stores namespace declarations
and undeclarations) - and therefore walks the ancestor axis when necessary.

However, there are other implementation choices that could work well, for
example storing at document level all the distinct sets of in-scope
namespaces, and storing with each element node a pointer to one of these
sets. I've been thinking about using that strategy for the Saxon linked
tree, as it might work better for XQuery Update.

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