W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2005

[Bug 1520] New: Editorial & Suggestion: distinguish different QNames in EBNF

From: <bugzilla@wiggum.w3.org>
Date: Sun, 03 Jul 2005 18:19:51 +0000
To: public-qt-comments@w3.org
Message-Id: <E1Dp94J-0006tE-2J@wiggum.w3.org>


           Summary: Editorial & Suggestion: distinguish different QNames in
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P2
         Component: XPath
        AssignedTo: chamberl@almaden.ibm.com
        ReportedBy: frans.englich@telia.com
         QAContact: public-qt-comments@w3.org

As known, QNames receives different treatment depending on context -- what     
default namespace that should be used.     
This could be communicated in the EBNF by having two rules that both expand to     
the QName token, referenced from the appropriate productions. An example:     
FunctionQName         ::= QName     
ElementQName          ::= QName     
NameTest              ::= ElementQName | Wildcard     
FunctionCall          ::= <FunctionQName "("> (ExprSingle (","     
                                   ExprSingle)*)? ")"     
I would find the grammar useful in that way; the question is if that should be   
valued higher than the increased complexity, and change in EBNF at this stage   
of development. But it is also nothing more than a suggestion. 
Received on Sunday, 3 July 2005 18:19:53 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:25 UTC