W3C home > Mailing lists > Public > public-qt-comments@w3.org > February 2009

[Bug 6469] [FT] TestSuite issues

From: <bugzilla@wiggum.w3.org>
Date: Mon, 16 Feb 2009 17:30:50 +0000
To: public-qt-comments@w3.org
Message-Id: <E1LZ7Iw-0003E7-Js@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6469





--- Comment #9 from Pat Case <pcase@crs.loc.gov>  2009-02-16 17:30:50 ---
Hi Christian.

Re:
[18] ftwildcard-q2.xq
[19] ftwildcard-q5.xq

> --This query looks for "site." site followed a period (not an indicator). 
> There is a sites. The title ends in site but does not end in a period. I 
> don't see "site." in Book 2. [...]

This is an interesting point for discussion. I had another look into the XQFT
Tokenization section (4.1). If I get it right, the tokenizer won't care about
characters which are not part of tokens; so I would expect the two following
queries to return true:

  'a b' ftcontains 'a.b' 
  'a.b' ftcontains 'a b' 

This is why I would expect the dot in "site." to be ignored in the default
(without wildcards) mode. - Please tell me if I got something wrong.

--I see your point. I am an end user and I sometimes project my preferences
where they don't belong. I would love to have search engine that can find
special characters, in this case to allow me to fund "site." as a token. But
you are absolutely correct that depending on the tokenization, finding "site"
would be just as valid, and that would return Books 1 and 2. So I have added a
qualifier to the descriptions, changed the comparator values to Inspect, and
added second output files to q2 and q5.

Thanks again for your comments. It is very important to get this right.

Pat


-- 
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 Monday, 16 February 2009 17:31:01 UTC

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