Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xsl] Context document with exsl:node-set()?

From: "Scott Trenda" <Scott.Trenda@-------->
To:
Date: 11/1/2007 9:43:00 PM
Believe me, I know the ins and outs of result-tree-fragments within
"pure" XSLT 1.0. My question was regarding how they behave when
converted with exsl:node-set(), which I do not know as much about, and
that was the context behind the statements in my reply.

> The result of exsl:node-set() has the same general structure as a
> document in that it has one root node, but that root node could have
> multiple element node children (unlike an XML document).

I was not asking about the structure of the exsl:node-set() result. I
was asking about its behavior with regards to document-sensitive XSLT
constructs, keys in particular. The behavior that I'm seeing so far
validates this.
<xsl:apply-templates select="exsl:node-set($rtf)"/>
is acting identically to this in my tests (with respect to keys and root
node references):
<xsl:apply-templates select="document(rtf.xml)"/>

where rtf.xml is an external document containing content identical to
that of $rtf at the time of the statement.


~ Scott


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