> -----Original Message-----
> From: Alan Kent [mailto:[log in to unmask]]
> Sent: Wednesday, September 25, 2002 9:44 PM
> To: [log in to unmask]
> Subject: Re: Expressing Term Structure
> I can understand the niceness in mapping to AA, but I am wondering how
> easy it will be for users to remember what all the symbols mean.
I think we've gotten to the point that we have to concede that we have not
built a language for end users. Client software is going to have to parse
the user's original query and rebuild it as a CQL query. So, this kind of
richness in the grammer is not really much of a problem.
> Note: for AND, I am not sure of operator precedence. In CCL
> title=john and smith
> needs to be entered as
> title=(john and smith)
> as by default it means
> (title=john) and (smith)
I don't think so. Parens are mandatory around operator triples and quotes
are mandatory around terms. The query could be (title="john" and "smith")
where smith is search using the default index or it could be (title="john"
and title="smith") or it could be title="john and smith". None of the above
examples are legal.
> For string search, I think a different field name can be used. I don't
> think it would be common that a field would be both word indexed and
> string indexed. So if the field is string, use that attribute
> by default.
I do both word and string indexing on nearly every field. Users want to
browse the complete phrase but search by words.