>Bah. I'm reconvinced. I'd rather add a one line '<supports
>type="structure">keyword</supports>' to each index than duplicate it and
>tack 'Word' on the end of the name. Then it's up to the server to use
>the most appropriate method to fulfil the query rather than the client
>telling the server which index it thinks it wants based on Explain.
I am totally confused (and I have to implement the stuff next week):
(1) The world has many index types two of them are string and word. A server
might implement multiple index methods for the same marc tag (titleWord,
titleString and many more) The server decides upon the names. Probably the
server among others supports "Bath" names.
(2) String and word are different. If a client tells us to use string then
that is most appropriate.
(3) One syntax with extra elements to auto differentiate between string and
word indexes is cute but serves nobody.
title= "the x? a ?y * of ?z? book"
title= "the new a b c book of john and mary"
Both queries easy for "string" indexes and rather hard for "word" indexes.
(4) Nobody can (or should) force servers to always implement String and
Word. (and in practice "string" is only useful for scanning)
>Then the query, I would assume to be: title="|aardvark|" ?
I assume we now write:
title= "|war|" and "|peace|" and "|iraq|" ?
The only sense I see for "|" is: titleString="suse linux 7.0|". (hm and try
that with word indexes if you use "." as word separator)