9540 2010-04-16 15:51:13 +0000 QueryTokenInfo definition seems wrong 2011-01-06 01:28:07 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Full Text 1.0 Proposed Recommendation All All CLOSED FIXED P2 normal --- 1 paul jim.melton holstege jmdyck public-qt-comments oldest_to_newest 35104 0 paul 2010-04-16 15:51:13 +0000 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. 35822 1 holstege 2010-05-25 15:53:55 +0000 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. 35825 2 jmdyck 2010-05-25 16:11:54 +0000 queryPos is used by fts:ApplyFTOrder(). 35826 3 holstege 2010-05-25 19:37:31 +0000 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. 36028 4 jmdyck 2010-06-08 02:32:17 +0000 (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. 36189 5 holstege 2010-06-15 15:01:29 +0000 Fixed definition to refer to only one position. Please indicate your satisfaction with this resolution by closing the bug. 43638 6 paul 2010-12-29 16:57:00 +0000 I'd be happy to mark this as CLOSED but I can't see the updated spec from the "outside". 43841 7 paul 2011-01-06 01:28:07 +0000 Verified as fixed.