2007/9/14, Arun Raghavan <<a href="mailto:arunisgod@gmail.com">arunisgod@gmail.com</a>>:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 9/14/07, Mikkel Kamstrup Erlandsen <<a href="mailto:mikkel.kamstrup@gmail.com">mikkel.kamstrup@gmail.com</a>> wrote:<br><snip><br>> Man I love speaking to myself :-) Anyways, I just completed (4). Check it
<br>> out at <a href="http://wiki.freedesktop.org/wiki/XesamQueryLanguage">http://wiki.freedesktop.org/wiki/XesamQueryLanguage</a><br>> and gimme the flames...<br><br>Looks good!<br><br>One question -- is:<br><br><fullText>
<br> ...<br></fullText><br><br>equivalent to<br><br><equals><br> <fullTextFields/><br> ...<br></equals><br><br>or<br><br><contains><br> <fullTextFields/><br> ...<br><contains>
<br><br>or neither? If either. isn't <fullText> redundant?<br><br>Also, I think some more documentation (or an example) of what the<br>vendor.extensions property is supposed to look like would be nice.</blockquote>
<div><br>It would most closely match the example with the contains selector i guess. The point in the fullText selector is that it is weakly defined. It can do more elaborate matching than the straight contains selector. Some implementations could incur some level of fuzziness or something.
<br><br>Maybe the fullText description should stress this. Something like: <br><br>"Search in everything that makes sense and match to the best of the engines ability. The most basic matching would be equivalent to the contains selector, but more elaborate matching, fx via fuzzyness, is also allowed."
<br></div><br></div>I will put up an example of vendor.extensions usage.<br><br><br>Cheers,<br>Mikkel<br>