9448 2010-04-08 13:33:14 +0000 Some bugs with the FTScope in full text 2011-01-06 01:21:12 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Full Text 1.0 Candidate Recommendation PC Windows XP CLOSED FIXED P2 normal --- 1 xero_123 jim.melton jmdyck public-qt-comments oldest_to_newest 34657 0 xero_123 2010-04-08 13:33:14 +0000 I think that there is some bugs with the FTScope. Let we see the function fts:ApplyFTScopeDifferentSentence in the XQuery and XPath Full Text 1.0 W3C Candidate Recommendation 28 January 2010. OK! I think that if we have a stringInclude1 which tokenInfo/@startSent != tokenInfo/endSentSent in the match, and then this stringInclude1 will always be right ,no matter what the $stringInclude2 is. Right or not? On the other hand,if we have a stringInclude1 which tokenInfo/@startSent == tokenInfo/endSentSent in the match,and then this stringInclude1 will always be wrong ,because the $stringInclude2 maybe the same of stringInclude1. so I think we should change the 'where sub' is 'where every $stringInclude in $match/fts:stringInclude satisfies ($stringInclude1/fts:tokenInfo/@startSent != $stringInclude1/fts:tokenInfo/@endSent '. I am a chinese student.So there may be some grammatical errors, and I am sorry. MY EMail:guoxiaolei_neu@163.com Look forward to your reply!!!! Function Content: declare function fts:ApplyFTScopeDifferentSentence ( $allMatches as element(fts:allMatches) ) as element(fts:allMatches) { <fts:allMatches stokenNum="{$allMatches/@stokenNum}"> { for $match in $allMatches/fts:match where every $stringInclude1 in $match/fts:stringInclude, $stringInclude2 in $match/fts:stringInclude satisfies ($stringInclude1/fts:tokenInfo/@startSent != $stringInclude2/fts:tokenInfo/@startSent or $stringInclude1/fts:tokenInfo/@startSent != $stringInclude1/fts:tokenInfo/@endSent or $stringInclude2/fts:tokenInfo/@startSent != $stringInclude2/fts:tokenInfo/@endSent ) and $stringInclude1/fts:tokenInfo/@startSent > 0 and $stringInclude2/fts:tokenInfo/@endSent > 0 return <fts:match> { $match/fts:stringInclude, for $stringExcl in $match/fts:stringExclude where every $stringIncl in $match/fts:stringInclude satisfies ($stringIncl/fts:tokenInfo/@startSent != $stringExcl/fts:tokenInfo/@startSent or $stringIncl/fts:tokenInfo/@startSent != $stringIncl/fts:tokenInfo/@endSent or $stringExcl/fts:tokenInfo/@startSent != $stringExcl/fts:tokenInfo/@endSent ) and $stringIncl/fts:tokenInfo/@startSent > 0 and $stringExcl/fts:tokenInfo/@endSent > 0 return $stringExcl } </fts:match> } </fts:allMatches> }; 35715 1 jmdyck 2010-05-16 04:32:28 +0000 > I think that if we have a stringInclude1 which tokenInfo/@startSent != > tokenInfo/endSentSent in the match, and then this stringInclude1 will always be > right, no matter what the $stringInclude2 is. That depends on what you mean by "right". The condition in the QuantifiedExpr will be satisfied for that $stringInclude1 no matter what $stringInclude2 is. > On the other hand, if we have a stringInclude1 which tokenInfo/@startSent == > tokenInfo/endSentSent in the match, and then this stringInclude1 will always be > wrong, because the $stringInclude2 maybe the same of stringInclude1. Hmm. So when an "input" match contains a stringInclude that starts and ends within the same sentence, that match cannot succeed, because the QuantifiedExpr's condition will return false when $stringInclude1 and $stringInclude2 are both bound to that stringInclude. Yeah, that's a bug. (The condition used to begin with $stringInclude1 is $stringInclude2 or ... to "skip over" the cases where the two variables were bound to the same stringInclude, but that had a bug too: a match containing a single stringInclude would always succeed.) We'll have to take another crack at writing that function. 38493 2 jmdyck 2010-09-07 04:08:31 +0000 At meeting #437 on 2010-05-18, the Working Groups agreed to change the 'where' clause in fts:ApplyFTScopeDifferentSentence() as follows: where count($match/fts:stringInclude) > 1 and every $stringInclude1 in $match/fts:stringInclude, $stringInclude2 in $match/fts:stringInclude satisfies $stringInclude1 is $stringInclude2 or ( [pre-existing 'satisfies' condition] ) We believe this fixes the bug you discovered. Therefore, I am marking this bug resolved-FIXED. If you agree with this resolution, please mark it CLOSED. 43483 3 jmdyck 2010-12-20 20:28:11 +0000 (By the way, the function fts:ApplyFTScopeDifferentParagraph had the same bug as fts:ApplyFTScopeDifferentSentence, and was also fixed by the change in comment #2.)