This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
I propose to also raise XQST0045 if the name of a function annotation or the function name in a function declaration is in the array or map namespace (http://www.w3.org/2005/xpath-functions/array, http://www.w3.org/2005/xpath-functions/map).
Thanks - I'll fix that.
The error code XQST0045 is used three times (for functions, function annotations, and function assertions). In each case there is a list of prohibited namespaces. The array and map namespaces have been added to one of these lists but not to the other two.
(In reply to Michael Kay from comment #2) > The error code XQST0045 is used three times (for functions, function > annotations, and function assertions). In each case there is a list of > prohibited namespaces. The array and map namespaces have been added to one > of these lists but not to the other two. Thanks. One more question: What is the particular reason for only adding it once? For example, the math namespace (http://www.w3.org/2005/xpath-functions/math) is also listed in all three cases, and I believe its similar to the map and array namespace.
I don't think there is a good reason for making the three lists different. That's why I reopened the bug. Sorry if this wasn't clear.
I got it! In this case, the definition of err:XQST0045 (F: Error Conditions) should probably be updated as well (or "reserved namespaces" could be listed once in the beginning of the spec).
Fixed.