generalizing cql-form to parameterized queries

["Denenberg, Ray" <rden@loc.gov>]

These are the changes to SRU, as I see it, to accommodate cql-form. Please comment, as I want to write this into the draft I am working on. 


The specific name CQL-form need not be mentioned in SRU (except perhaps by example), however we do need to generalize it, for other similar query types that come in parameterized form and we need a name for this generalization so that we can talk about it in SRU. 

Can we call it "parameterized query"?

So there will be a class of queries distinguished as Parameterized Queries. CQL-forms will be in this class. Thus, two classes of queries 'string' and 'parameterized'.   (Hopefully we won't later discover that we need yet a third class.)

I think every query (other than well-known) will need a URI and in explain you assign it a short name that is to be used in the queryType parameter when accessing that server. That would mean, for example then, that CQL-Forms is just a local name anyway (unless we decide it is well-known).  And you indicate in the explain file whether the query is of class 'string' or 'parameterized'.

Thus for any request

- If there is a query parameter:
The query is of class 'string', and the value of the query parameter is the query string. The parameter queryType will be included if the query is of type other than cql and may be omitted or included for a cql query but in any case it will be of class 'string'.
 
- If there is no query parameter:
 The query is of class 'parameterized'. The queryType parameter MUST occur and there MUST be one or more parameters in the request as specified by the specification for that query.

Anything else?


--Ray