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".
custom implementation, but if exsl:random-sequence (EXSLT.org)
is supported, then processor should use internal version
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.
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).
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.