RE: [search-ws] queryn: Some further comments

["Hammond, Tony" <t.hammond@nature.com>]

Title: RE: [search-ws] queryn: Some further comments

Agreed. Why I prefer to use queryn as the natural mirror to the query parameter.

What I do think is improper is to use the query parameter in one case to signal a searchRetrieve operation, and a queryType in another csse to do the same. The same parameter (or parameter twin) should do the same job.

And then what happens if one has queryType=cql and no query parameter?

I would hope that operation is inferred on basis of a single parameter. query/queryn seem to me to be naturally twinned. query/queryType are more distantly related.

Tony


-----Original Message-----
From: LeVan,Ralph [mailto:levan@oclc.org]
Sent: Thu 12/16/2010 3:16 PM
To: Hammond, Tony; Hammond, Tony; Ray Denenberg, Library of Congress; Matthew Dovey; OASIS SWS TC
Subject: RE: [search-ws] queryn: Some further comments

I do not want to see empty query parameters signaling searchingRetrieve!



I see no problem with a rule that says either the presence of a query
parameter or a queryType parameter signals that we have a query.  The
queryType will then have some associated parameter(s) that carry the
query.  That parameter might even be the query parameter.



Ralph



From: Hammond, Tony [mailto:t.hammond@nature.com]
Sent: Thursday, December 16, 2010 6:08 AM
To: Hammond,Tony; Ray Denenberg, Library of Congress; Matthew Dovey;
LeVan,Ralph; OASIS SWS TC
Subject: RE: [search-ws] queryn: Some further comments



Hi:

Some further comments.

1. On reflection I guess that "queryn" could be dispensed with as long
as an empty "query" parameter were present in the query to a) signal the
searchRetrieve operation, and b) to receive the assembled query.

2. I had earlier proposed briefer forms of the parameters which would
make the querystring more manageable.

Instead of

"q1.idx", "q1.rel", "q1.trm", "q1.bln"

I proposed

"qi1", "qr1", "qt1", "qb1"

which are cleaner (half the length) and slighly easier to manipulate
(only prefix and index to manage instead of prefix, index, and suffix).

3. Since the query parameters are built with integers they are
arbitrarily extensible (do not require a fixed length form) and sort
order is completely in hands of the form generator. Doesn't matter where
the parameters appear on the form - just their call order. And then they
can be simply iterated over.

4. My preference is still for an explicit count (queryn) as I think this
is easier than trying to compute the number of clauses. And the count is
already known to the form generator since it is adding an index to the
clause parameters. Would almost seem to be a no-brainer.

5. Because of the boolean coupling of search clauses we require a
boolean associated with the search clause which for convenience we take
to be trailing - i.e. operates between this clause and any subsequent
clause. The final boolean in the series will always be omitted.

Tony


************************************************************************
******** 
DISCLAIMER: This e-mail is confidential and should not be used by anyone
who is
not the original intended recipient. If you have received this e-mail in
error
please inform the sender and delete it from your mailbox or any other
storage
mechanism. Neither Macmillan Publishers Limited nor any of its agents
accept
liability for any statements made which are clearly the sender's own and
not
expressly made on behalf of Macmillan Publishers Limited or one of its
agents.
Please note that neither Macmillan Publishers Limited nor any of its
agents
accept any responsibility for viruses that may be contained in this
e-mail or
its attachments and it is your responsibility to scan the e-mail and
attachments (if any). No contracts may be concluded on behalf of
Macmillan
Publishers Limited or its agents by means of e-mail communication.
Macmillan
Publishers Limited Registered in England and Wales with registered
number 785998
Registered Office Brunel Road, Houndmills, Basingstoke RG21 6XS 
************************************************************************
********

********************************************************************************   
DISCLAIMER: This e-mail is confidential and should not be used by anyone who is
not the original intended recipient. If you have received this e-mail in error
please inform the sender and delete it from your mailbox or any other storage
mechanism. Neither Macmillan Publishers Limited nor any of its agents accept
liability for any statements made which are clearly the sender's own and not
expressly made on behalf of Macmillan Publishers Limited or one of its agents.
Please note that neither Macmillan Publishers Limited nor any of its agents
accept any responsibility for viruses that may be contained in this e-mail or
its attachments and it is your responsibility to scan the e-mail and 
attachments (if any). No contracts may be concluded on behalf of Macmillan 
Publishers Limited or its agents by means of e-mail communication. Macmillan 
Publishers Limited Registered in England and Wales with registered number 785998 
Registered Office Brunel Road, Houndmills, Basingstoke RG21 6XS   
********************************************************************************