W3C home > Mailing lists > Public > public-qt-comments@w3.org > March 2015

[Bug 28122] New: [xslt 3.0] the function xsl:original

From: <bugzilla@jessica.w3.org>
Date: Mon, 02 Mar 2015 09:03:38 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28122-523@http.www.w3.org/Bugs/Public/>

            Bug ID: 28122
           Summary: [xslt 3.0] the function xsl:original
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: mike@saxonica.com
        QA Contact: public-qt-comments@w3.org

We say in

Within the declaration of an overriding component (that is, a component whose
declaration is a child of xsl:override), where the overridden component has
public visibility, it is possible to use the name xsl:original as a symbolic
reference to the overridden component:

* Within an overriding stylesheet function, xsl:original() may be used to call
the overridden stylesheet function.


There's a need for more precision here.

(a) a function call on xsl:original will usually have arguments

(b) symbolic references to functions may also appear in the form of partial
function application (e.g. xsl:original(?, 3)), or named function references
(e.g. xsl:original#2). We need to make it clear that these are legal.

(c) we should make it clear that xsl:original cannot be used in static
expressions, e.g. within use-when. (This also applies to the variable reference

(d) we should make it clear that dynamic references to xsl:original, e.g in
function-available(), function-lookup(), or xsl:evaluate, will not succeed.
Again this also applies to the variable reference $xsl:original.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 2 March 2015 09:03:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:53 UTC