This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
From section 4.1.2: [Definition: A QueryTokenInfo is the identity of a token inside a query string. ] Each QueryTokenInfo is associated with a starting and ending position that captures the relative position of the query string in the query. However, in section 4.2.1.3, the schema for queryTokenInfo has only queryPos, a single integer, and not "a starting and ending position," two integers, per the definition above.
In investigating this as directed by the WG, it appears that neither the queryPos attribute nor the described the starting and ending positions in the query are used directly in any of the semantic functions. However, a single queryPos is carried through the semantic functions (and the accompanying diagrams). I therefore propose to resolve the reported inconsistency by changing the definition of QueryTokenInfo.
queryPos is used by fts:ApplyFTOrder().
The queryPos in ApplyFTOrder is the stringInclude queryPos, which comes from the parameter passed through the call stack. Regardless, there is no call for startPos/endPos on a QueryTokenInfo, so the proposal stands.
(In reply to comment #3) > The queryPos in ApplyFTOrder is the stringInclude queryPos, which comes from > the parameter passed through the call stack. My mistake. In fact, neither of queryTokenInfo's attributes is referenced by any of the functions in section 4.
Fixed definition to refer to only one position. Please indicate your satisfaction with this resolution by closing the bug.
I'd be happy to mark this as CLOSED but I can't see the updated spec from the "outside".
Verified as fixed.