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

[Bug 9858] New: [FT] FTStopWordOption and FTCaseOption interaction clarification

From: <bugzilla@jessica.w3.org>
Date: Sat, 05 Jun 2010 00:17:11 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-9858-523@http.www.w3.org/Bugs/Public/>

           Summary: [FT] FTStopWordOption and FTCaseOption interaction
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Full Text 1.0
        AssignedTo: jim.melton@acm.org
        ReportedBy: paul@lucasmail.org
         QAContact: public-qt-comments@w3.org

I originally sent this an an ordinary (non-bug) e-mail to the
public-qt-comments@w3.org list hoping for some kind of comment.  I prefer not
to write bugs willy-nilly, but get at least one other person who agrees with me
before filing a bug.  However, in this case, after having gotten no comments,
I'm submitting this as a bug anyway because I think it's warranted.  That

As far as I can tell, nowhere in the spec does it say anything specifically
about case sensitivity and the FTStopWordOption.

Does the value of FTCaseOption affect stop-word comparisons?  E.g.:

    let $x := <p>BEST OF TIMES</p>
    return $x contains text "BEST ANY TIMES"
      using stop words ("any")
      using case sensitive

Should that query return true or false?

The spec should say explicitly what the interaction between those two match
options is supposed to be or at the very least explicitly state that it's

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 Saturday, 5 June 2010 00:17:12 UTC

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