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

[Bug 24521] New: xsl:evaluate prohibits use of math and map functions

From: <bugzilla@jessica.w3.org>
Date: Wed, 05 Feb 2014 17:21:19 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-24521-523@http.www.w3.org/Bugs/Public/>

            Bug ID: 24521
           Summary: xsl:evaluate prohibits use of math and map functions
           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

Currently, under 10.4.1 Static context for the target expression
(http://www.w3.org/TR/xslt-30/#evaluate-static-context), sixth dot, we say:

"Function signatures: All core functions; constructor functions for named
simple types included in the in-scope schema definitions; all user-defined
functions and accumulator functions present in the containing package provided
their visibility is not hidden or private; and an implementation-defined set of
extension functions."

In the spec, core functions are defined as the set of functions in the standard
function namespace "http://www.w3.org/2005/xpath-functions".

I think this is too strict. I don't see any reason to disallow math functions
or map functions.

In addition, I would like to have the ability to limit the range of functions.
I.e., I can imagine that implementations would like to prevent usage of doc()
and unparsed-text() for obvious security reasons. This, of course, could be a
totally implementation defined user option, but it should be possible to have
this restriction on by default.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 5 February 2014 17:21:21 UTC

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