This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
(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.