2776 2006-01-27 19:07:30 +0000 Allow weight to be any numeric value 2006-05-01 18:28:29 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Full Text 1.0 Working drafts PC Windows XP CLOSED FIXED P2 normal --- 1 holstege sihem public-qt-comments oldest_to_newest 8008 0 holstege 2006-01-27 19:07:30 +0000 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. 9415 1 holstege 2006-04-24 15:47:22 +0000 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.