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 9934 - [FT] Need static error for unsupported FTMatchOptions combinations
Summary: [FT] Need static error for unsupported FTMatchOptions combinations
Status: CLOSED WORKSFORME
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Full Text 1.0 (show other bugs)
Version: Candidate Recommendation
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Jim Melton
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-16 00:11 UTC by Paul J. Lucas
Modified: 2010-12-29 17:02 UTC (History)
1 user (show)

See Also:


Attachments

Description Paul J. Lucas 2010-06-16 00:11:28 UTC
If an implementation does not support a particular combination of FTMatchOptions in a single query, it should raise a static error.  However, the specification does not currently provide such an error.

For example, given a query like:

    $x contains text ".*volv.*"
    using stemming
    using wildcards

it's not clear what that means, what a correct answer would be, or even how to implement it.
Comment 1 Mary Holstege 2010-07-06 18:20:18 UTC
The WG discussed this bug at the 2010-07-06 telcon.

We believe that the current specification gives implementations sufficient latitude to handle such cases without error and we do not wish to give implementations license to throw an error in such as case, as it imposes an undue burden on users in constructing error-free queries. It is quite likely, for example, that stemming could be a global option, which would create the same conflict.  

Stemming, tokenization, and matching are already all implementation dependent, so the implementation can choose to define the effect in such cases in a suitable manner. While it is unlikely that stemming will perform any meaningful operation on a wildcarded token (just as it will not for a numeric token, for example) in the query, stemming can still be applied meaningfully to the document content and it is possible that the wildcarded token could be matched in a stem-aware fashion. 

In summary, we are closing this bug with no further action.  If you are satisfied with this resolution, please close the bug.