W3C home > Mailing lists > Public > public-qt-comments@w3.org > October 2014

[Bug 27125] New: [XSLT30] Rules of override-extension-functions and xsl:override

From: <bugzilla@jessica.w3.org>
Date: Wed, 22 Oct 2014 14:11:51 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-27125-523@http.www.w3.org/Bugs/Public/>

            Bug ID: 27125
           Summary: [XSLT30] Rules of override-extension-functions and
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org

This is a bug report that covers the unresolved part of
https://lists.w3.org/Archives/Member/w3c-xsl-wg/2014Sep/0036.html and
https://lists.w3.org/Archives/Member/w3c-xsl-wg/2014Sep/0039.html (member only)
and related mail discussion.

Summary of that part:

The XSLT30 LCWD (Oct 2014) says that when you override an xsl:function and that
function has override-extension-functions="no", then the overriding function
must also specify override-extension-functions="no".

Use-case summary:

Package A:
<xsl:function name="exsl:random-sequence" 
       custom implementation, but if exsl:random-sequence (EXSLT.org)
       is supported, then processor should use internal version

Package B:
    <xsl:function name="exsl:random-sequence" 
          User wants to make use of the new fn:random-sequence of XP31
          implementation using XPath 3.1 random sequence

[ERR XTSE3070] It is a static error if the signature of an overriding component
is not compatible with the signature of the component that it is overriding.

Relevant spec part:

Definition of "compability":
(member only), item 4 of the second bullet:

If the overridden function specifies override-extension-functions="no" (or the
equivalent using the deprecated override attribute) then the overriding
function also specifies override-extension-functions="no" (or the equivalent).

Proposed solution:

Remove this rule (not the error), because it limits users choosing to switch to
(new) internal XPath 3.1 or later, or XSLT 3.x or later functions as a
preference over internal implementations and as such, limits extensibility and
more importantly, inter-processor compatibility.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 22 October 2014 14:11:52 UTC

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