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

[Bug 16149] New: Context-dependent constructor functions

From: <bugzilla@jessica.w3.org>
Date: Tue, 28 Feb 2012 15:17:08 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-16149-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16149

           Summary: Context-dependent constructor functions
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XPath 3.0
        AssignedTo: jonathan.robie@gmail.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org


In section 3.1.6 (named function references) we say

If the function referenced by a NamedFunctionRef is a context-dependentFO30
built-in function [err:XPST0112].

[which is not the usual editorial style, but that's by-the-by]

Similarly in 3.1.5: It is a static error if a static function call is a partial
function application and the identified function is a context-dependentFO30
built-in function [err:XPST0112].

Constructor functions for xs:QName, xs:NOTATION, and other namespace-sensitive
types should also be included in this category. 

The spec for function-lookup does not restrict the rule to built-in functions:

If the function that is identified is ·context-dependent·, fn:function-lookup
returns a function 

but it would be useful to add an example to demonstrate that
namespace-sensitive constructors are also affected.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 28 February 2012 15:17:14 UTC

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