RE: [search-ws] generalizing cql-form to parameterized queries

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

Ok moving forward with this, assuming Ralph's approach....

 The parameter 'query' will be struck from the SRU specification. (It will
need to be added to the cql spec, as the one parameter that cql imposes on
an SRU request, but it need not be mentioned in the SRU protocol. Except
perhaps as a commentary, but not in the parameter tables.)

The parameter queryType, if omitted from an SRU request, it's value is
assumed to be 'cql'. If included, it may be 'cql' or it may be some other
query type. 

Whatever the query type is, cql, cql-form, or some other query type, there
will be some specification for that query type which will indicate one or
more parameters that will be included on an SRU request.

And as I suggested earlier: Every query type (other than well-known querie
types, e.g. 'cql') 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.  

Everyone agree with all this?

--Ray


> -----Original Message-----
> From: LeVan,Ralph [mailto:levan@oclc.org]
> Sent: Tuesday, December 28, 2010 3:45 PM
> To: OASIS SWS TC
> Subject: RE: [search-ws] generalizing cql-form to parameterized queries
> 
> Why do we need this?
> 
> SRU defines the optional parameter queryType.  SRU has a distinguished
> queryType, CQL.  When queryType is absent, its default value is CQL.
> SRU no longer defines the query parameter.
> 
> Every queryType defines the parameters it needs.  CQL defines the query
> parameter.  Cql-form defines an open-ended raft of parameters.
> 
> I see no value in the concepts of parameterized and string queries.
> 
> Ralph
> 
> -----Original Message-----
> From: Denenberg, Ray [mailto:rden@loc.gov]
> Sent: Tuesday, December 28, 2010 2:57 PM
> To: 'OASIS SWS TC'
> Subject: [search-ws] generalizing cql-form to parameterized queries
> 
> 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
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php