OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

search-ws message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [search-ws] multiple query types


I'd suggest

(5) Use (2) and the server can define an additional local name for the
parameter in their Explain record. (reserving 'query' for CQL). This
would be like Context Sets and their local names.  We'd have an
unambiguous, interoperable version of the parameter name and allow
servers to define something shorter and pithier.

Ralph

> -----Original Message-----
> From: Ray Denenberg, Library of Congress [mailto:rden@loc.gov]
> Sent: Thursday, September 18, 2008 3:58 PM
> To: search-ws@lists.oasis-open.org
> Subject: [search-ws] multiple query types
> 
> I propose that we face up to the issue of query type, and try to come
> to a
> consensus within the TC, to present to the rest of the world.
> 
> I suppose everyone agrees that the "new" SRU should support multiple
> query
> types.  Right? We never decided how to do it, but we did talk alot
> about it.
> To review, there are two basic approaches: a query-type parameter, or
a
> separate parameter name for each query type.  More specifically and
> fleshing
> this out, there are four approaches:
> 
> (1) use the query parameter to carry queries of all types and add a
> queryType parameter to specify how the query is to be interpreted.
> Explain
> records list the types of queries supported by the server.
> 
> (2) use the name of the query parameter itself to indicate the type of
> query.  For instance,  the current query parameter (for the CQL query)
> might
> be renamed CQLQuery and a new query parameter of luceneQuery might be
> specified to support Lucene queries. (No 'query' parameter, and no
> 'queryType parameter.)
> 
> (3) Use (1) with the additional stipulation that queryType is
optional,
> and
> it defaults to CQL.
> 
> (4) Use (4) except there is no standard default, the default is sever
> dependent and exposed via explain.
> 
> For discussion at (and before) Monday's call.
> 
> --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
> 




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]