- From: <bugzilla@jessica.w3.org>
- Date: Wed, 05 Jun 2013 12:08:22 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19597
--- Comment #24 from Christian Gruen <christian.gruen@gmail.com> ---
I think this should be fixed before finalizing XQuery 3.0. It know I’m late
with this, but I believe that the require/prohibit feature is more than just an
option. Maybe we could add the grammar rule...
FeatureDecl ::= "declare" "feature" ("required" | "prohibited") StringLiteral
...which is only allowed in the first part of the prolog...
Prolog ::= ((FeatureDecl | DefaultNamespaceDecl | NamespaceDecl |
Import | Setter ) Separator)*
((ContextItemDecl | AnnotatedDecl | OptionDecl) Separator)*
..and add an extra-grammatical constraint which requires FeatureDecl to appear
before Import (and maybe Setters)? This solution would both be 1.0 compliant
and allow namespaces as feature names.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 5 June 2013 12:08:27 UTC