W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2011

[Bug 12109] [FT] StopWord Option

From: <bugzilla@jessica.w3.org>
Date: Mon, 04 Apr 2011 12:38:29 +0000
To: public-qt-comments@w3.org
Message-Id: <E1Q6j37-0000TI-3M@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12109

Tim Mills <tim@cbcl.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WORKSFORME                  |

--- Comment #2 from Tim Mills <tim@cbcl.co.uk> 2011-04-04 12:38:27 UTC ---
While I'm happy with the response, I still think the text should make this
explicit.

There should at least be one example using stopwords not sandwiched between
non-stopwords.

Our implementation ignores stopwords at query time (i.e. they are handled in
our implementation of matchTokenInfos).  Where S is a stopword and C is a
non-stopwor, we treat:

S+ as a query matching no results.
S* T+ S* as if the query were T* (i.e. strip head and teal stopwords)
T+ S+ T+ as if the query were T+ .+ (for each S) T+

This interpretation allows us to pass the XQFTTS tests.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 4 April 2011 12:38:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:35 UTC