> Date: Thu, 16 Dec 2004 15:34:25 -0500
> From: "Ray Denenberg, Library of Congress" <[log in to unmask]>
>
> > That's not really true, as the CQL context set provides some of
> > the key elements used in pretty much CQL queries, e.g. the meaning
> > of all the relations.  Probably the base profile should make this
> > explicit.
>
> Good point, but what exactly do we want to say in the base profile about the
> cql context set?
>
> http://www.loc.gov/z3950/agency/zing/cql/ states that it is the
> default context set for modifiers and relations, so that's
> covered. Are there any specific modifiers or relations not listed
> that should be mandated?  scr should be required (see below), but
> other than that, exact, all, and any are already listed.

Good point.

> For modifiers -- word and string?

The _concepts_ of word and string are very important, and should be
discussed more in the CQL specifications; but I don't think we should
mandate support for the relation modifiers, as relation modifiers are
sometimes perceived as esoteric.

> Actually, I think, first, we should say in
> http://www.loc.gov/z3950/agency/zing/cql/ in general rule 2 (search
> clause) that when the index and relation are omitted from a search
> clause then 'cql.serverChoice' applies and the relation is scr.  So
> we should say in the base profile that serverChoice and scr are
> required.

Agreed.

> Should resultSet be required?

Probably not.

 _/|_    _______________________________________________________________
/o ) \/  Mike Taylor  <[log in to unmask]>  http://www.miketaylor.org.uk
)_v__/\  "Users spend most of their time on _other_ sites" -- Jakob's
         Law of the Web User Experience.

--
Listen to free demos of soundtrack music for film, TV and radio
        http://www.pipedreaming.org.uk/soundtrack/