>We have dc and cql - so not sure whether we need another cross-domain
> set rather than put the cross-domain stuff in one of those (probably cql
> as putting something in dc which isn't in Dublin Core may not be a good
> idea!)

More concretely, I suggest a "utility set". If, for example, we want a
general "country" index, we cannot put it in the DC set, and we certainly
don't want to put it in the CQL set. I agree that we don't want to define a
set and call it "cross domain" given that DC exists, so why not call it
"utility"?

--Ray