- From: <bugzilla@jessica.w3.org>
- Date: Tue, 06 Jul 2010 18:20:19 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9934
Mary Holstege <holstege@mathling.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |holstege@mathling.com
Resolution| |WORKSFORME
--- Comment #1 from Mary Holstege <holstege@mathling.com> 2010-07-06 18:20:18 ---
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.
--
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 Tuesday, 6 July 2010 18:20:21 UTC