>> Why shouldn't this be allowed?
> For reasons outline that this leads to queries involving serverChoice
> which cannot be performed by explicitly requesting indexes.
> It isn't the default value that is at issue, it is that the default
> value in cases ii,iii,v and vi are values which would not normally be
> allowed in CQL queries sent to that server.
Okay... and why shouldn't /that/ be allowed?
> My view would be that if a server returns simple Dublin Core when the
> recordSchema is omitted by the client, then I don't see why the client
> can't explicitly request that record schema and expect to get it.
Then you're also arguing against
cql.allKnown/adlib.whateverHedzerCallsHisIndex, which searches indexes
which are otherwise unsearchable?
> Similarly if the server uses a particular index when
> omitted/serverChoice I don't see why the client can't explicitly ask for
> for that index in a query.
That could be done, but what gain is there by making it mandatory to do
it? I just don't see one when you can get it by using cql.serverChoice.
,'/:. Dr Robert Sanderson ([log in to unmask])
,'--/::(@)::. 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