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

[Bug 23631] New: [xslt 3.0] function-lookup() and XSLT extensions to the dynamic context

From: <bugzilla@jessica.w3.org>
Date: Fri, 25 Oct 2013 15:37:06 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-23631-523@http.www.w3.org/Bugs/Public/>

            Bug ID: 23631
           Summary: [xslt 3.0] function-lookup() and XSLT extensions to
                    the dynamic context
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          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

When function-lookup() is used to get a context-dependent function such as
position() or last(), it keeps the XPath dynamic context as part of the
closure, so the value of position() will be its value at the point where
function-lookup() was called.

To what extent should this also apply to the XSLT extensions to the XPath
dynamic context (listed in 5.4.4). The values that are accessible to functions

The current group and current grouping key (current-group(),

The current captured substrings (regex-group())

In addition, we have the current() function.

Some of this is fairly heavyweight stuff (non-trivial cost to compute the value
and to save it just on the off-chance that it might be needed). The current()
function is particularly awkward because of its effect on the ability to inline
or outline variables.

Functions that depend on the static context, such as type-available() are also
problematic: given that different types are available in different packages, it
may be significant work to retain information about the types that were
available at the point where function-available() was called.

My instinct is to say that none of these functions are "recognized" by
function-lookup; any attempt to lookup a function such as regex-group returns
"not found".

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 25 October 2013 15:37:07 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:54 UTC