RE: [search-ws-comment] SRU/CQL: clarification about fatal diagnostics

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

For the SRU case, see section 11 (of SRU 2.0) "Diagnostics". There are
surrogate and non-surrogate diagnostics, and there are fatal and non-fatal
diagnostics. But a fatal diagnostic (which is what we're talking about) is
always non-surrogate.

Surrogate diagnostics go in <records>,  non-surrogate in <diagnostics>, thus
fatal diagnostics go in <diagnostics>.

The scan case is simpler because all diagnostics are fatal (there is no
concept of surrogate diagnostic in scan) so they go in <diagnostics>

And as Ralph said, If you don't know the operation, then the  response is an
explainResponse.

--Ray

> -----Original Message-----
> From: LeVan,Ralph [mailto:levan@oclc.org]
> Sent: Thursday, June 14, 2012 9:51 AM
> To: Oliver Schonefeld
> Cc: search-ws-comment@lists.oasis-open.org
> Subject: RE: [search-ws-comment] SRU/CQL: clarification about fatal
> diagnostics
> 
> If you know the operation, then the diagnostic is wrapped in the response
> appropriate for that operation.  If you don't know the operation, then the
> response is an explainResponse.
> 
> Ralph
> 
> -----Original Message-----
> From: Oliver Schonefeld [mailto:schonefeld@ids-mannheim.de]
> Sent: Thursday, June 14, 2012 9:48 AM
> To: LeVan,Ralph
> Cc: search-ws-comment@lists.oasis-open.org
> Subject: Re: [search-ws-comment] SRU/CQL: clarification about fatal
> diagnostics
> 
> Hi,
> 
> Am 14.06.2012 15:31, schrieb LeVan,Ralph:
> > In my implementation, if both the query and scanClause parms have been
> > omitted, then the operation is Explain and they get an explainResponse
> > with no diagnostics.
> 
> Ok, but what if, e.g. operation and version are nicely supplied by the
client,
> so the server could already know/infer, that the client wanted to perform
a
> specific operation?
> Or, what if the client did everything correctly when submitting the
response,
> but a fatal error occurred while the server performs the search request,
e.g.
> a (temporary) internal error in the search engine and the server wants to
> return a "info:srw/diagnostic/1.1" or "info:srw/diagnostic/1.2"
diagnostic?
> 
> Thanks and best regards,
>  Oliver
> --
> Oliver Schonefeld
> Institut für Deutsche Sprache, Zentrale Forschung R5, 6-13, D-68161
Mannheim
> +49-(0)621-1581-451 | http://www.ids-mannheim.de
> 
> 
> 
> --
> This publicly archived list offers a means to provide input to the
> OASIS Search Web Services TC.
> 
> In order to verify user consent to the Feedback License terms and
> to minimize spam in the list archive, subscription is required
> before posting.
> 
> Subscribe: search-ws-comment-subscribe@lists.oasis-open.org
> Unsubscribe: search-ws-comment-unsubscribe@lists.oasis-open.org
> List help: search-ws-comment-help@lists.oasis-open.org
> List archive: http://lists.oasis-open.org/archives/search-ws-comment/
> Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
> Committee:
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=search-
> ws
> Join OASIS: http://www.oasis-open.org/join/
> 
> 
> 
> 
> --
> This publicly archived list offers a means to provide input to the
> OASIS Search Web Services TC.
> 
> In order to verify user consent to the Feedback License terms and
> to minimize spam in the list archive, subscription is required
> before posting.
> 
> Subscribe: search-ws-comment-subscribe@lists.oasis-open.org
> Unsubscribe: search-ws-comment-unsubscribe@lists.oasis-open.org
> List help: search-ws-comment-help@lists.oasis-open.org
> List archive: http://lists.oasis-open.org/archives/search-ws-comment/
> Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
> Committee:
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=search-
> ws
> Join OASIS: http://www.oasis-open.org/join/