On Thu, 25 Jan 2007, Mike Taylor wrote:

> Ray Denenberg, Library of Congress writes:
> > The SRU Editorial Board is developing a draft specification for SRU
> > version 1.2, which is near completion.

> Please remind me -- once the "exact" relation is eliminated, how will
> CQL express an exact search?  As in
> 	cql.title exact jaws
> to find "Jaws" but not "The Jaws of Death"?

cql.title eq jaws

> What was the motivation for CQL change 7?
> 	Proximity. Defaults are now server defined, not standard
> 	defined. Hence "prox" can be anything the server wants to do
> 	proximately, not necessarily with a default of adjacency.

Because it was inconsistent with the rest of the specification, but also 
because proximity can be used for non textual relationships -- we 
already have examples/implementations of element based proximity, and 
many others could be imagined such as geospatial proximity (x building 
is adjacent to y building) and to force a client interacting with such a 
database to always specify that the unit = building, when that is the 
only unit the server accepts seems to be against the spirit of previous 
CQL decisions.

HTH :)

Rob