- From: <bugzilla@jessica.w3.org>
- Date: Wed, 12 Oct 2011 23:35:06 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14439 Michael Kay <mike@saxonica.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mike@saxonica.com --- Comment #2 from Michael Kay <mike@saxonica.com> 2011-10-12 23:35:05 UTC --- This is partly covered by the non-normative J.2 in XQuery 1.0: "it is suggested that in such cases implementations should require the names of global variables and functions to be unique within the query as a whole: that is, if two modules with the same module URI participate in a query, the names of their global variables and functions should not overlap." We added this in the second edition and made it non-normative because we didn't want to invalidate existing implementations. However, we have made the text normative in XQuery 3.0 (see 4.12.2), as we reasoned that interoperability across implementations in this area is more important than backwards compatibility. I think the statement "The names of public global variables and public functions must be unique within the query as a whole" justifies a processor in rejecting the example given, even though it's not covered by the elaboration that follows: ("that is, if two modules with the same module URI are used in the same query, the names of their global variables and functions must not overlap") -- Configure bugmail: http://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 Wednesday, 12 October 2011 23:35:18 UTC