This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
There is no reason why weight should have to be specified with a numeric literal, much less a decimal one. Proposal: Change the FTSelection production to: FTSelection ::= FTOr (FTMatchOption | FTProximity)* ("weight" ExprSingle)? with the constraint that the ExprSingle must resolve to a numeric value. It also looks like a section on weights is missing from 3.1 (2.2.1 promises such a section, but it doesn't materialize); either put this constraint there, or put it in 2.2.1 and remove the vacuous forward reference.
The dangling forward reference still exists in the latest draft and the requirement that weights be literals also still exists in the latest draft. If the WG decided to keep weights as literals we would appreciate a rationale (and the bug should be more properly marked as WONTFIX), but in any case the editorial part of this comment needs to be addressed.