5574 2008-03-14 16:46:48 +0000 ApplyFTScopeDifferentSentence/Para usage of general comparison is not right 2008-03-17 21:34:15 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Full Text 1.0 Working drafts All All CLOSED FIXED P2 minor --- 1 zhen.liu jim.melton public-qt-comments oldest_to_newest 19480 0 zhen.liu 2008-03-14 16:46:48 +0000 We have the following xquery code to define scope for different sentence. The intension here is to make sure every StringIncludeMatch pair are in different sentences unless the two pair is identical. The XQuery code uses '$stringInclude1 = $stringInclude2' xquery general comparsion to make the two StringInclude matches are identical. The comparsion requires xquery atomization fn:data() to apply on $stringInclude1 and $stringInclude2. However, the problem is that $stringInclude1 and $stringInclude2 are of fts:stringMatch type which is a complex type with element-only. So this will cause it to raise FOTY0012. In any case, the proper way to avoid this issue is to do use 'is' xquery operator as '$stringInclude1 is $stringInclude2'. Same issue exists for ApplyFTScopeDifferentParagraph() func 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 = $stringInclude2 or $stringInclude1/fts:tokenInfo/@endSent < $stringInclude2/fts:tokenInfo/@startSent or $stringInclude2/fts:tokenInfo/@endSent < $stringInclude1/fts:tokenInfo/@startSent 19505 1 holstege 2008-03-17 19:36:37 +0000 Agreed. Fixed as proposed. Please close this bug if you are satisfied with the resolution. 19519 2 zhen.liu 2008-03-17 21:34:15 +0000 ok with the resolution.