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

[Bug 28175] New: [XP3.1] Statically known functions, and XSLT 3.0 packages

From: <bugzilla@jessica.w3.org>
Date: Mon, 09 Mar 2015 12:05:01 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28175-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28175

            Bug ID: 28175
           Summary: [XP3.1] Statically known functions, and XSLT 3.0
                    packages
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XPath 3.1
          Assignee: jonathan.robie@gmail.com
          Reporter: mike@saxonica.com
        QA Contact: public-qt-comments@w3.org

The description of the static context in XPath 3.1 says:

<quote>
[Definition: Statically known function signatures. This is a mapping from
(expanded QName, arity) to function signatureDM31. ] The entries in this
mapping define the set of statically known functions — those functions that are
available to be called from a static function call, or referenced from a named
function reference. Each such function is uniquely identified by its expanded
QName and arity (number of parameters). Given a statically known function's
expanded QName and arity, this component supplies the function's signatureDM31,
which specifies various static properties of the function, including types.
</quote>

Most of the time, the spec is careful to make clear that it is only the
function signatures that are present in the static context -- not actual
function implementations.

For XSLT 3.0 packages, this is essential. For example, XSLT 3.0 makes it
possible to reference an abstract function whose implementation will be
supplied later in a different package. The function signature is known
statically, but the implementation is not.

The only place where the XPath 3.1 spec slips up on this distinction is in fact
in the paragraph cited above, which is the only place that talks of "statically
known functions" rather than statically known function signatures.

Suggested rewording:

<quote>
[Definition: Statically known function signatures. This is a mapping from
(expanded QName, arity) to function signatureDM31. ] The entries in this
mapping define the signatures of the functions that are available to be called
from a static function call, or referenced from a named function reference.
Each such function signature is uniquely identified by its expanded QName and
arity (number of parameters). The function signatureDM31 defines various static
properties of the function, including types.
</quote>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 9 March 2015 12:05:09 UTC

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