No, I don’t think that’s right. XSLT 1.0 allows the use of current() within any
XPath expression, and says that it returns the same value as the context item
for the outermost containing expression. So it’s perfectly OK to use it within
xsl:key/@use.
The main change between 1.0 and 2.0 was that 1.0 banned the use of current() in
a pattern, whereas XSLT 2.0 allows it, and defines it to return the node being
matched against the pattern. This affects the match attribute of xsl:key, but
not the use attribute.
Michael Kay
Saxonica
On 29 Oct 2015, at 20:12, Ihe Onwuka ihe(_dot_)onwuka(_at_)gmail(_dot_)com
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> wrote:
Would I be right in concluding that XSLT 1.0 restricts the availability of
current() to where apply-templates or for-each have been invoked, which would
mean it can't be invoked in the use attribute of xsl:key.
Would it further be accurate to say this restriction is lifted in XSLT 2.0.
ihe
XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
EasyUnsubscribe <-list/293509> (by email <>)
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--