On Tue, 18 Jul 2006, Jakob Voss wrote:
>Christophe Dupriez wrote:
>> You seem to propose that the user may wish to say
>> WHY (s)he searches and not HOW to search.
>> Anyone has done a list of the Use Cases for a search engine ?
>> that people are asking for. They want a "Do what I mean" simple search
>> completed with a more structured search form for advanced searches.
>Is there a way to return a "did you mean X" (spelling corrections,
>similar temrs etc)
Not yet, but there will be in version 1.2 (being written up at the
As there are as many different types of suggested actions as there are
search engine implementations, the approach being taken is to add
extension capabilites to the echoed query. Then if there are sufficient
implementations of a given extension, it will be raised into the
protocol proper in a future version (in the same way as the existing
For example, if you want to say that instead of the full search, you
should try a different one, it might be something like:
<my:suggestedQuery>dc.subject = dinosaur</my:suggestedQuery>
Other things you might want to return here:
* Number of hits for sub-queries (eg hits in search clauses linked by
booleans, rather than total hits for the entire query)
* Suggested replacement index, term, relation, modifiers, clause, query
* Identifier and idle time for sub-query result sets.
* The actual search performed for cql.serverChoice
* How tokenization was done for words (book-case ... one word or two?)
Hope that helps!