- From: <bugzilla@jessica.w3.org>
- Date: Fri, 19 Oct 2012 08:55:29 +0000
- To: public-qt-comments@w3.org
- Message-ID: <bug-19626-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19626
Priority: P2
Bug ID: 19626
Assignee: jonathan.robie@gmail.com
Summary: [XQ30] Awkward option declarations
QA Contact: public-qt-comments@w3.org
Severity: normal
Classification: Unclassified
OS: Windows NT
Reporter: tim@cbcl.co.uk
Hardware: PC
Status: NEW
Version: Working drafts
Component: XQuery 3.0
Product: XPath / XQuery / XSLT
Consider the following query.
import schema namespace s = "http://www.w3.org/XQueryTest/RequireProhibitF
eature";
declare function local:foo() as schema-element(s:foo)
{
...
}
declare option prohibit-feature "schema-aware";
local:foo()
It is not until we are well into parsing that the option prohibiting use of
import schema is encountered. This is quite annoying.
Consider also a processor which has schema awareness disabled by default.
import schema namespace s = "http://www.w3.org/XQueryTest/RequireProhibitF
eature";
declare function local:foo() as schema-element(s:foo)
{
...
}
declare option require-feature "schema-aware";
local:foo()
It is not until we are well into parsing that the option enabling use of import
schema is encountered. This is similarly annoying.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 19 October 2012 08:55:36 UTC