> Date: Tue, 24 Sep 2002 22:35:24 +0200
> From: Rob Koopman <[log in to unmask]>
>
>> dc.titleAllTheseWords
>> dc.titleAnyOfTheseWords
>> dc.titleAdjacentWords
>> dc.titleRelevantWords
>> dc.titleString
>>
>> I don't think dc.titleWord will be one of these.
>
> query = (dc.titleAllTheseWords="a b c")?
(Excuse me while I vomit.) We're back again to the question of
whether CQL is supposed to be human-writable (and readable) or not.
If it is, then this is something of a monstrosity. It's only a short
step from here to
bib1.u1003_r3_p3_s2_t101=kernig
Which I assume is _not_ where we want to get to :-)
> My logic tells me that this is mixing index type with default
> operator, resulting in an explosion of pseudo index types all
> translating to word.
Yes.
> I would prefer one of the following:
>
> query = ((titleWord="a") and (titleWord="b") and (titleWord="c"))
> query = (titleWord="a" and "b" and "c")
As Ray has said, that's fine for titleAllTheseWords, but doesn't work
for titleRelevantWords, and may not be widely implemented for
titleAdjacentWords.
(And, BTW., the parens in the second example -- and the outer parens
in the first example -- are redundant. I think what you meant in the
second example was ``titleWord=("a" and "b" and "c")'', which is
equivalent to the first example.)
> Whatever dc defined having a (virtual pseudo ) index
> dc.titleAnyOfTheseWords is mixing user interface and index
> definition.
I agree that this is all wrong. We're going to end up with a
rectangular field of qualfiers, much like those Chinese Takeaway menus
where you can have any main ingredient with any sauce:
titleAllTheseWords subjectAllTheseWords authorAllTheseWords
titleAnyOfTheseWords subjectAnyOfTheseWords authorAnyOfTheseWords
titleAdjacentWords subjectAdjacentWords authorAdjacentWords
titleRelevantWords subjectRelevantWords authorRelevantWords
titleString subjectString authorString
... ... ...
Now I'm aware that my last several hundred messages to this list have
been offensively critical of other people's work, and that I've hardly
said one constructive thing (apart from my alternative Qualifier
Semantics document). My apologies for this. I will try to remedy
that by proposing a constructive alternative in a separate message.
Stay tuned!
_/|_ _______________________________________________________________
/o ) \/ Mike Taylor <[log in to unmask]> www.miketaylor.org.uk
)_v__/\ "The best way to get information on Usenet isn't to
ask a question, but to post the wrong information" --
[log in to unmask]
|