- From: <bugzilla@jessica.w3.org>
- Date: Tue, 30 Nov 2010 05:36:43 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11209
Michael Dyck <jmdyck@ibiblio.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |jmdyck@ibiblio.org
Resolution| |FIXED
--- Comment #1 from Michael Dyck <jmdyck@ibiblio.org> 2010-11-30 05:36:43 UTC ---
At their joint 2010-11-23 meeting, the XQuery/XSL WGs approved the following
fix:
-- In 4.2.5.2, have fts:applyQueryTokensAsPhrase() pass
$noThesaurusOptions to fts:applyThesaurusOption().
-- In 4.2.5.7, have fts:applyThesaurusOption() accept
$noThesaurusOptions and pass it on to fts:lookupThesaurus().
-- In 4.2.5.3, have fts:lookupThesaurus() [an external
(implementation-defined) function] accept $noThesaurusOptions,
and in the prose, say something to the effect that by giving it
access to the other match options, we allow the implementation to
apply any of those match options (whichever it deems relevant) to
the input or output of the "actual" thesaurus lookup.
(They also approved the subsequent cleanup of eliminating the now-redundant
$thesaurusLanguage parameter from fts:lookupThesaurus(), and the
now-unnecessary "language" attribute from complexType ftThesaurusOption.)
I have made these changes to the editors' draft of the Full Text spec, and so
am marking this issue resolved-FIXED. Since you were at the meeting and
indicated that these changes would be satisfactory, I will also mark the issue
CLOSED.
--
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, 30 November 2010 05:36:45 UTC