Print

Print


> I was looking at the semantic distinction between "cql.anywhere"
> and "cql.serverChoice", defined in the CQL Context Set at
> http://www.loc.gov/z3950/agency/zing/cql/context-sets/cql.html
> It seems  "cql.anywhere" tells the server to search all of its
> indexes, though unspecified as to which those may be. On the
> other hand, "cql.serverChoice" tells the server to search just
> one index, though also unspecified as to which one.

Correct.

"Search all indexes you have, from all context sets"
"Search any index of your choice"

> I cannot imagine any searcher needing to insist that the server
> limit its search to exactly one, unspecified index.

The server can have an experimentation period before choosing an index
though :)  It doesn't have to arbitrarily always select the dc.title
index, it could try that, if there aren't any matches it can try subject,
and then it can try description (etc)

Equally, it might select the cql.anywhere 'index' and then proceed to
search everything.  Equally the server might have a
'internal.titleDescriptionAndSubject' index to search...

Which isn't to say that I disagree with your conclusion that the
definition should be clarified.

Rob

       ,'/:.          Dr Robert Sanderson ([log in to unmask])
     ,'-/::::.        http://www.o-r-g.org/~azaroth/
   ,'--/::(@)::.      Dept. of Computer Science, Room 805
,'---/::::::::::.    University of Liverpool
____/:::::::::::::.  L5R Shop: http://www.cardsnotwords.com/
I L L U M I N A T I