W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2007

[Bug 4730] [FT] editorial: 5.2.14 Scoring

From: <bugzilla@wiggum.w3.org>
Date: Sat, 23 Jun 2007 10:15:34 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1I22eU-00065J-B7@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=4730

           Summary: [FT] editorial: 5.2.14 Scoring
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P2
         Component: Full Text
        AssignedTo: jim.melton@acm.org
        ReportedBy: jmdyck@ibiblio.org
         QAContact: public-qt-comments@w3.org


5.2.14 Scoring

[1]
"a combination of FTContainsExpr"
    s/FTContainsExpr/FTContainsExprs/

[2]
"formed with the XQuery Boolean operators 'and' and 'or'"
    What about "not" ?

[3]
why
    In the case of ForClause and SimpleForClause, the scoring restriction
    doesn't make much sense: if the ExprSingle satisfies the restriction,
    it can only return a boolean, and what's the point of iterating over a
    singleton boolean?
    Note that none of the ForClauses or SimpleForClauses in this spec's
    examples satisfy this restriction. Ditto in the Use Cases.
Received on Saturday, 23 June 2007 10:15:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:14:48 GMT