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 3898 - [FT] Semantics of FTProximity requires changes to use spans as result of sub-expressions
Summary: [FT] Semantics of FTProximity requires changes to use spans as result of sub-...
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Full Text 1.0 (show other bugs)
Version: Working drafts
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Jochen Doerre
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-31 00:16 UTC by Joaquin Delgado
Modified: 2007-04-20 15:40 UTC (History)
0 users

See Also:


Attachments

Description Joaquin Delgado 2006-10-31 00:16:01 UTC
We need to make changes to FTProximity semantics to allow "grouping" for the evaluation of sub-expressions in nesting situations.

The solution involves the use of spans (contiguous block of tokens with start/end positions) as the result of the sub-expression to be used in the evaluation of outer expressions.

e.g.

/books ftcontains (((richard && nixon) distance at most 2) && ((george && bush) distance at most 2) distance at least 20)

This would always return empty results in the current semantics because the "at least 20" would be violate the internal "at most 2" condition when applied to any continuous tokens. The desired result treates the result the result of the sub-expression as a span, pretty much like we do with phrases, thus allowing results that find elements that contain  "richard m. nixon"  and "george w. bush" at least 20 words apart.

-- Joaquin
Comment 1 Jim Melton 2007-04-20 14:56:34 UTC
The TF agreed with your comment and has adopted changes to both the Distance Selection and Window Selection parts of the Full-Text spec to address the comment. The bug is therefore being marked FIXED.  If you are satisfied with the changes, please mark the bug CLOSED.  If you are not satisfied, please enter a response here in Bugzilla explaining your concerns.  If we do not receive a response within 14 days from the date of this response, we will mark the bug CLOSED unilaterally. 
Comment 2 Jim Melton 2007-04-20 15:40:07 UTC
Because you participated in the TF when this bug was resolved, we presume that
your concerns are addressed appropriately.  We are therefore marking this bug
as CLOSED.