> ".... including random order".   (I don't believe there is such a thing as
> "no ordering whatsoever".)

Changed to:
"The default ordering of a result set is left up to the server, including
a lack of any explicit ordering."

> "This is addressed in SRW through the use of the sortKeys parameter,
> however, for sophisticated relevance based ranking,  boolean operands might
> be treated differently, and specific methods might be requested to combine
> the results of evaluating each operand."

I've made this change, but as it's a Context Set, it does require being
part of the query! :)

Any algorithm that has a term frequency component must obviously be able
to refer to the search terms, and hence should be able to be part of the
query for optimization, as per sort being part of the search request.

Rob

--
      ,'/:.          Dr Robert Sanderson ([log in to unmask])
    ,'-/::::.        http://www.o-r-g.org/~azaroth/
  ,'--/::(@)::.      Special Collections and Archives, extension 3142
,'---/::::::::::.    University of Liverpool
____/:::::::::::::.
I L L U M I N A T I  L5R Shop: http://www.cardsnotwords.com/