21717 2013-04-16 13:21:51 +0000 Not used: XQST0124 2013-06-04 16:39:08 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 3.0 Candidate Recommendation PC Windows NT RESOLVED FIXED P2 normal --- 1 christian.gruen jonathan.robie public-qt-comments oldest_to_newest 86288 0 christian.gruen 2013-04-16 13:21:51 +0000 Error code XQST0124 is not used anywhere in the current XQ30 specification. It states that "It is a static error if the name of a feature in require-feature or prohibit-feature is not recognized by the implementation." Instead, the description of XQST0123 is referenced once: "It is a static error if the name of a feature in require-feature is not recognized by the implementation." Next, there seems to be no dedicated error code for options in the "http://www.w3.org/2012/xquery" namespace. Maybe one of the two above was supposed to fill this gap? 87654 1 jonathan.robie 2013-05-14 15:34:34 +0000 This is no longer in the internal XQuery 3.0 text. I checked in a query that looks for unused error codes or references to error codes that do not exist, and removed these. 87674 2 christian.gruen 2013-05-14 18:04:05 +0000 Thanks for the removal. I believe that it still needs to be clarified what is going to happen if an option in the default options namespace ("http://www.w3.org/2012/xquery") is unknown. An example: declare option unknown "x"; () Maybe XQST0124 could be used for that case? 88621 3 jonathan.robie 2013-06-04 15:18:49 +0000 (In reply to comment #2) > Maybe XQST0124 could be used for that case? Sounds good to me. 88632 4 jonathan.robie 2013-06-04 16:39:08 +0000 (In reply to comment #3) > (In reply to comment #2) > > Maybe XQST0124 could be used for that case? > > Sounds good to me. The Working Group agrees. I will change this in the spec.