This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 20902 - [XQ30] Incompatibilities
Summary: [XQ30] Incompatibilities
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3.0 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Jonathan Robie
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-08 10:51 UTC by Tim Mills
Modified: 2013-05-07 17:42 UTC (History)
1 user (show)

See Also:

Attachments

Description Tim Mills 2013-02-08 10:51:48 UTC 
In XQ10, the reserved-function-names extra-grammatical constraint only applied to FunctionCall.

In XQ30, the constraint also applies to NamedFunctionRef and FunctionDecl.  This means that some valid XQ10 queries now raise errors, for example:

    declare default function namespace "http://www.w3.org/2005/xquery-local-functions";
    declare function attribute() { fn:true() };
    local:attribute()

This should be listed in the XQ30 incompatibilities.

I have already committed test cases for reserved function names.
Comment 1 Jonathan Robie 2013-03-19 16:37:35 UTC 
Yes, this should be listed as an incompatibility.
Comment 2 Michael Kay 2013-05-07 17:42:00 UTC 
Noted during discussion today that the resolution of this bug represents an official interpretation of the XQuery 1.0 specification, to the effect that the prohibition of reserved function names applies only to their use in function calls, and not to their use in function declarations.