This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 29474 - Named components and xsl:original
Summary: Named components and xsl:original
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-16 16:07 UTC by Max Toro
Modified: 2016-02-18 22:38 UTC (History)
0 users

See Also:


Attachments

Description Max Toro 2016-02-16 16:07:29 UTC
In https://www.w3.org/TR/xslt-30/#named-components it says:

"A named declaration, for example a named template, a function, or a global variable, may be overridden within the same package by another like-named declaration having higher import precedence. When a declaration is overridden in this way it cannot be referenced by name either from within its containing package or from outside that package; it can however be referenced from the overriding declaration using the special name xsl:original, as described in 3.5.3.4 Referring to Overridden Components."

I don't know if I'm missing something, but xsl:original refers to the declaration with highest import precedence, the other ones are not visible from a using package.
Comment 1 Michael Kay 2016-02-17 13:35:57 UTC
Thank you for the comment, which the WG reviewed today.

The text "; it can however be referenced from the overriding declaration using the special name xsl:original, as described in 3.5.3.4 Referring to Overridden Components" should be deleted.

We're not sure how the text got here: perhaps at one time we were intending that xsl:override should have this functionality, but in the current spec it clearly does not.
Comment 2 Michael Kay 2016-02-18 22:38:34 UTC
The offending text has been deleted.