- From: <bugzilla@jessica.w3.org>
- Date: Fri, 19 Jul 2013 07:49:10 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22732 --- Comment #1 from Michael Kay <mike@saxonica.com> --- To restore what I think we intended when we wrote this rule, I suggest we change it to say: If the function that is retrieved by fn:function-lookup has *dynamic* dependencies on the static or dynamic context.... and then think about how to define what "dynamic dependencies" are. What we want here is to allow static binding to the things that you would normally expect to be statically bound (like namespaces), and dynamic binding to the things that can't be statically bound (like a decimal format, or a collation whose value is not known until run-time.) I can't think of any way of doing this other than enumerating which context dependencies are considered dynamic. This might not be easy: for example the collation name in "order by" is fixed statically, and we would presumably like to bind it statically, whereas collation names passed to functions are in general only known dynamically. For variables (consider my original example) there is the complication that we would really like f to be able to bind both to the (static) declaration of $v, and to its (dynamic) value (3). This is tricky to achieve because our current semantics for variable references speak as if we did a run-time lookup of the variable name. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 19 July 2013 07:49:11 UTC