2007/1/29, Jean-Francois Dockes <<a href="mailto:jean-francois.dockes@wanadoo.fr">jean-francois.dockes@wanadoo.fr</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;"> Mikkel Kamstrup Erlandsen writes:<br> > Hi All,<br> ><br> > I put together a first take on formalizing an end user search language.<br> ><br> > <a href="http://wiki.freedesktop.org/wiki/WasabiUserSearchLanguage"> http://wiki.freedesktop.org/wiki/WasabiUserSearchLanguage</a><br><br> - Which of OR and AND has priority ? (does (A AND B OR C) mean<br>   ((A AND B) OR C) or (A AND (B OR C)) ?</blockquote><div><br>I guess it is standard that AND takes precedence over OR, but maybe it makes sense to reverse that in our case. Think of the case <br><br>type:audio hendrix OR beatles<br></div><br>In this case I would assume the user wants "audio files matching hendrix or beatles", and not "audio files matching hendrix, or anything that matches beatles"... I think it is non-standard however... <br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> - What should happen when an entry does not make sense? For example you<br>   say that <= is "undefined but allowed" for strings ? So what should the <br>   implementation do ? Take this as an equivalent for ':'. Or ignore the<br>   entry ? Or what ?</blockquote><div><br>Anything conforming to the spec should parse as a rule of thumb. What exact action to take is up to the implementation. You suggest replacing "<=" with ":", and that is probably a good idea. <br><br>Some search engines might be able to handle ">=" as "the metadata property value is *contained* in the value string". I don't have a use case for this though.<br><br>Maybe it is a bad idea to have loose ends like this. <br></div><br></div>Cheers,<br>Mikkel<br>