>> I am still in favour of having a default srw indexset containing all
>> dc, dcterms and bath names. Especially when we are going to avoid
>> things like having gils.title and dc.title and bath.title.
> This is _good_ news for you, Theo. Although I think your idea is a
> bad one, there is nothing I or anyone else can do to stop you making
> the "theo" set, defined precisely how you wish (e.g. including
> synonyms for all the DC, Bath, etc. indexes) and making that the
> default context set for your application. Go nuts.
To clarify:
You could make a theo set -as well as- supporting the proper names for
these indexes.
For example you might have something like:
theo.title -> dc.title
theo.type -> dc.type
theo.choice -> cql.serverChoice
theo.hostname -> net.host
theo.portnumber -> net.port
But you should always support the original names as well so that other
clients can interoperate.
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
|