You are right, we will change it.
>>> [log in to unmask] 25-6-04 11:40:48 >>>
> > Actually we do not use the index prefixes, they are stripped
> > immediately from the index names, but to define them in
> explain they
> > need to be part of a set with a name.
> Yup. It is good ZeeRex citizenship to hide your dirty
> laundry this way :-)
I'm not sure I approve of just stripping the index prefixes (do you
check that they are valid first?). It's a little too close to z39.50
targets that ignored the attribute set specified and assumed it was
Of course a client *shouldn't* send a prefix not specified in the
record, but if I did send
mySillySet.creator where in mySillySet, creator is the index for the
Content Registration Extended Access Token Originating Resource (OK,
very contrived!) the query should be rejected with the appropriate
diagnostic rather than the prefix mySillySet being stripped unchecked
and a search on dc.creator/author being performed.