> Robert Sanderson wrote:
> > But is there a requirement for the /distinction/ or can we just say 'Sort
> > should be treated as case insensitive' ?
> I thought the solution we agreed upon was that this and other features would
> be implicit in the sort key name.
Yes, but under duress :) Or more accurately, that it works if the key
only has one thing tacked on the end, but will we end up with monsters
In terms of Theo's desire for having one request to send to many servers,
this is undesirable unless there are specific regulations on what sort
keys can be called (eg AuthorAscCase might be AscendingSensitiveAuthor on
a different server). And if there's restrictions on what they can be
called, it would be neater to have them as parameters.
Personally, I can live with a single sort key which encodes in
implementation dependant ways the information needed as there's always the
Explain/ZeeRex information to inform clients of what is available.
,'/:. Rob Sanderson ([log in to unmask])
,'--/::(@)::. Special Collections and Archives, extension 3142
,'---/::::::::::. Twin Cathedrals: telnet: liverpool.o-r-g.org 7777
____/:::::::::::::. WWW: http://liverpool.o-r-g.org:8000/
I L L U M I N A T I