W3C home > Mailing lists > Public > public-qt-comments@w3.org > November 2010

[Bug 11209] New: [FT] Wildcard and thesaurus options in combination

From: <bugzilla@jessica.w3.org>
Date: Wed, 03 Nov 2010 15:57:30 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-11209-523@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11209

           Summary: [FT] Wildcard and thesaurus options in combination
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Full Text 1.0
        AssignedTo: jim.melton@acm.org
        ReportedBy: tim@cbcl.co.uk
         QAContact: public-qt-comments@w3.org


Suppose an implementation's default thesaurus expands each of the tokens
"three" and "3.0" to the two query items "three" and "3.0".

Consider queries such as:

"version 3.0" contains text "three" 
using wildcards 
using default thesaurus

and

"version three" contains text "3.0" 
using wildcards 
using default thesaurus

It seems that thesaurus expansion can occur even when the wildcard option is
enabled.  However, in:

 fts:lookupThesaurus( $queryTokens,
                           $matchOption/fts:thesaurusName,
                           $matchOption/@language,
                           $matchOption/fts:relationship,
                           $matchOption/fts:range )

it appears that the thesaurus won't know whether characters in the query tokens
should be interpreted as wildcards or not.  Also the thesaurus might need to
escape its results ("three" expanding to "3\.0") to avoid triggering wildcard
matching.

-- 
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 Wednesday, 3 November 2010 15:57:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:15:08 GMT