This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6335 - [FT] fts:ApplyFTContent definition
Summary: [FT] fts:ApplyFTContent definition
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Full Text 1.0 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Jim Melton
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL: http://www.w3.org/TR/xpath-full-text-...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-29 12:54 UTC by Petr Pleshachkov
Modified: 2011-01-06 15:44 UTC (History)
1 user (show)

See Also:


Attachments

Description Petr Pleshachkov 2008-12-29 12:54:41 UTC
Dear authors,

In section 4.2.7.7 FTContent you say:  "entire content is evaluated as distance exactly 0 words at start at end", but in the definition of fts:ApplyFTContent function you have the fragment:

      let $temp1 := fts:ApplyFTWordDistanceExactly(
                        $allMatches,
                        1)

where $temp1 is assigned the result of fts:ApplyFTWordDistanceExactly with distance 1. Is it correct ? It seems to me that the distance should be 0. 

Kind regards
Peter
Comment 1 Michael Dyck 2009-02-27 02:37:11 UTC
Indeed, that '1' should have been a '0'.

However, looking into the matter, the Task Force determined that
    distance exactly 0 words at start at end
did not correctly reflect the intended semantics of 'entire content'
given in section 3.6.5 (i.e., the idea of covering every token position in
the search context).  In the next version of the FT spec, the definition
of fts:ApplyFTContent will better reflect those semantics.

Consequently, I am marking this issue resolved-FIXED. If you accept this
resolution, please mark it CLOSED.