- From: <bugzilla@jessica.w3.org>
- Date: Tue, 24 Mar 2015 16:37:27 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28241 --- Comment #3 from Jonathan Robie <jonathan.robie@gmail.com> --- I think the root problem is that this is trying to define the lexical form of an expanded QName before we have defined that term. The solution is probably: (1) move the following text so that it occurs before the production (and modify it to make it a better definition), and (2) change the description of the EQName production to make use of this definition: <proposal> Names in XQuery 3.1 can be bound to namespaces, and are based on the syntax and semantics defined in [XML Names]. [Definition: An expanded QName consists of an optional namespace URI, a local name, and an optional namespace prefix.] In the XQuery 3.1 grammar, expanded QNames are represented by the EQName production. </proposal> Is that better? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 24 March 2015 16:37:29 UTC