RE: JW10: QSD usage

> I would have thought that the use of QSD is too obvious to explain.
> The client UI could offer pulldowns for properties, operators, etc.
> if QSD provided such information. Pulldowns could be used to
> preclude typing and spelling errors, etc.

I don't buy this.  If I'm writing a client, do I really want to allow random
search operators into my user interface, where there will be an expectation
on the part of customers that I will provide customer support for operators
I never developed?  It seems more likely that I will only understand a
limited set of operators, and provide a user interface for just those
operators, ignoring all others that happen to be present.  In fact, in this
case I'm likely to never do QSD, instead just sticking to the base set of
operators supplied for a given schema.

- Jim

Received on Thursday, 24 June 1999 20:03:27 UTC