> I think it is reasonable to have CQL accommodate current
> practice in the naming of indexes for existing communities
> of practice.

Yes, and it does, but the _recommendations_ are:

*  If there is an existing index that meets your requirements, and there
is no overwhelming reason to not use it, then please use it

*  If there are two names for the same access point in your community,
then the community should pick one to standardise on.


> If CQL is to also be used for the searching of news stories,
> we can anticipate that there will be a "news context set"
> wherein the index named "byline" would have the same semantics
> as "author" and the index named "headline" would have the same
> semantics as "title".

And we would politely suggest that they use the existing names, much as we
are doing in this case :)

The main problem is a cross community client trying to metasearch.  Is
news.headline the same as dc.title, when the end user said "book keyword
in title"?

Another example,  my CCG context set does not define a 'name' for cards,
the profile uses dc.title.  It also doesn't define a card 'type', the
profile uses the equivalent dc index.

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