> -----Original Message-----
> From: Ray Denenberg [mailto:[log in to unmask]]
> Sent: Thursday, May 16, 2002 10:22 AM
> We need to have a dc prefix, forthe 15 dc elements, with dc semantics.
> Whether or not we need in addition an un-prefixed list should
> be argued
> based on the above premise. What would it consist of? Obviously, it
> wouldn't simply be the 15 dc elements with dc semantics
> again. What then?
> Would it be the 15 dc element names with semantics even more
> ambiguous than
> dc? What would be the point?
I have no problem with a DC index set. I have little problem with the
recommendation that all SRW servers support the DC index set. I guess I
could even live with it being mandatory. (OAI mandates that all records be
returnable in DC. So do we.) I will resist a move to make DC be the
default Index Set when the user provides no prefix.
But, I'm in a compromising mood. How about a new optional SRU parameter to
specify the user's default IndexSet? Then the fixed part of the URL could
say DefaultIndexSet=dc and the user could say title=dog. This parameter is
not needed in SRW because the client software could stick the prefix on