W3C home > Mailing lists > Public > public-qt-comments@w3.org > August 2008

[Bug 5975] FT and FTUC: Attribute tokenization and searching

From: <bugzilla@wiggum.w3.org>
Date: Tue, 19 Aug 2008 17:13:23 +0000
To: public-qt-comments@w3.org
Message-Id: <E1KVUln-0001jg-Ta@wiggum.w3.org>


Michael Dyck <jmdyck@ibiblio.org> changed:

           What    |Removed                     |Added
                 CC|                            |jmdyck@ibiblio.org
         AssignedTo|jim.melton@acm.org          |jmdyck@ibiblio.org

--- Comment #1 from Michael Dyck <jmdyck@ibiblio.org>  2008-08-19 17:13:21 ---
[Personal response]

(In reply to comment #0)
> Please clarify in the specification whether attribute tokenization and
> searching is supported or not:

The value of an attribute is tokenized and searched when it is in the
string value of a search content item, which I believe is only the case
when the attribute *is* the search context item. That is, the attribute
node must be an item in the value of the FTContainsExpr's RangeExpr.

> - in the FT Candidate Recommendation in 3.6.3. Distance Selection it is
> written (after the second example): "The phrase "Improving Web Site
> Usability" would satisfy the given full-text selection, but it occurs in
> an attribute value, and so is not subject to tokenization"

That sentence should probably have ended with "in this example". Would that
have sufficed to preempt this issue?

The wording around that example is being changed for Bug 5886, and will
make this point clearer too.

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, 19 August 2008 17:13:57 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:37 UTC