This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The XQuery 3.0 states in 4.20 that "A require-feature option declaration provides a list of named features" and it provides an example query declare option require-feature "schema-aware higher-order-function"; declare option prohibit-feature "static-typing"; ... but there seems to be no test cases that check such feature lists. Apart from that, the spec. does not clarify how the lexical syntax of a "list" looks like.
Looking at the specification, I agree with the points raised in comment #0. Anyone can easily add tests in regards to the first point, but I think the Working Group needs to clear up the second point on clarifying what is the the lexical syntax of a "list". There I am requesting this bug be added to the WG agenda for discussion.
I will add the phrase "whitespace-separated list" to the spec.
If I correctly remember, the original intent was to support a list of QNames consistently with an XML Schema list of QNames.
I confirm test cases have already been added. The WG have decided that further text should be added to the specification which details the lexical syntax of a 'feature list'. I am switching this to a bug against the spec.
(In reply to comment #4) > I confirm test cases have already been added. The WG have decided that > further text should be added to the specification which details the lexical > syntax of a 'feature list'. I am switching this to a bug against the spec. I just checked in this change: A require-feature option declaration provides a <add>whitespace-delimited</add> list of named features that must be enabled for the module in which the option declaration occurs; if any declaration requires a feature that the implementation does not support, a static error [err:XQST0120] is raised.