- From: <bugzilla@jessica.w3.org>
- Date: Tue, 26 Feb 2013 21:19:20 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21130 Bug ID: 21130 Summary: [XQ30] require-feature Classification: Unclassified Product: XPath / XQuery / XSLT Version: Candidate Recommendation Hardware: Other OS: All Status: NEW Severity: normal Priority: P2 Component: XQuery 3.0 Assignee: jonathan.robie@gmail.com Reporter: tim@cbcl.co.uk QA Contact: public-qt-comments@w3.org The specification makes provision for a processor to disable a feature which it supports in response to a prohibit-feature declaration, but there is no corresponding provision for a processor to enable a feature in response to a require-feature declaration which it supports but which is not enabled by default. In general, this isn't a problem. Most optional features do 'no harm' if enabled, I.e. enabling a feature will not cause the failure of query to compile. A notable exception is the static typing feature. A processor which supports (has an implementation of) the static typing feature might wish to operate with the feature disabled by default, since most queries are likely to fail static type checking. It would be enabled expliitly with a require-feature declaration. It would be unreasonable to expect library authors to include an explicit prohibition of the static typing feature. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 26 February 2013 21:19:22 UTC