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

[Bug 4730] [FT] editorial: 5.2.14 Scoring

From: <bugzilla@wiggum.w3.org>
Date: Thu, 11 Oct 2007 22:28:32 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1Ig6W8-00025i-Pk@wiggum.w3.org>

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


mrys@microsoft.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED




------- Comment #1 from mrys@microsoft.com  2007-10-11 22:28 -------
(In reply to comment #0)
> 5.2.14 Scoring
> [1]
> "a combination of FTContainsExpr"
>     s/FTContainsExpr/FTContainsExprs/

this becomes mood with change for [3].

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

This becomes mood based on change for [3]. Also note that the set of supported
expressions is implementation-defined according to 3.2.

> [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.

Section 3.2 says that set of supported expression is implementation-defined.

The section will be reworded. The first paragraph will say that implementations
can restrict allowable expressions and they are implementation-defined.

The second paragraph gets removed and the third one gets a slight editorial
adjustment.

Since you were present when we discussed the changes I am resolving and closing
the bug.
Received on Thursday, 11 October 2007 22:28:40 UTC

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