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

[Bug 2287] [xqueryx] forclause and letclause

From: <bugzilla@wiggum.w3.org>
Date: Thu, 22 Sep 2005 13:39:21 +0000
To: public-qt-comments@w3.org
Message-Id: <E1EIRIH-0007Ok-6q@wiggum.w3.org>


           Summary: [xqueryx] forclause and letclause
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQueryX
        AssignedTo: jim.melton@acm.org
        ReportedBy: davidc@nag.co.uk
         QAContact: public-qt-comments@w3.org

The XQuery concrete syntax allows multiple for (or similarly let) bindings in a
FLWOR expression to be separated by either "for" or "," however there is no
semantic distinction between these two cases. In Xquery you need to use "for"
rather than "," for the first binding, and the for the first binding
after a let, but in XQueryX even this distinction is not required as the
named elements remove any ambiguity anyway.

I think that the schema can be simplified (and improved) by dropping
forClauseItem and letClauseItem and instead using these definitions as the
definitions of forClause and letClause.

Received on Thursday, 22 September 2005 13:39:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:08 UTC