This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In section 4.2.4 formal semantics function: fts:wordDistance() is defined as $tokenInfo2/@startPos - $tokenInfo1/@endPos -1 This is consistent with 4.2.7.9 FTDistance section on how fts:wordDistance() is invoked with fts:tokenInfo is ordered by ('$fts:tokenInfo/@startPos, fts:tokenInfo/@endPos). However, such consistency is not followed for sentence & paragraph computation. fts:sentenceDistance() is defined as $tokenInfo2/@startSent - $tokenInfo1/@endSent -1 in section 4.2.4. However, fts:sentenceDistance() is involked in section 4.2.7.9 with fts:tokenInfo is order by ('$fts:tokenInfo/@startPos, fts:tokenInfo/@endPos) instead of ($fts:tokenInfo/@startSent, fts:tokenInfo/@endSent). The same inconsistency applies to paragraph as well. The seciton 4.2.7.9 should invoke fts:paraDistance() with fts:tokenInfo ordered by ($fts:tokenInfo/@startPara, fts:tokenInfo/@endPara).
(In reply to comment #0) > > However, fts:sentenceDistance() is involked in section 4.2.7.9 with > fts:tokenInfo is order by ('$fts:tokenInfo/@startPos, fts:tokenInfo/@endPos) > instead of ($fts:tokenInfo/@startSent, fts:tokenInfo/@endSent). Can you give an example where these two orderings would lead to different sentence-distances?
Per group discussion, we found the distance computation algorithm needs to be revisited as action item 169-01 by Mary Holstege. So we close this bug as invalid.