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


Help: OASIS Mailing Lists Help | MarkMail Help

search-ws-comment message

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

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

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.

My SRW/U code is available under the Apache 2 license at http://code.google.com/p/oclcsrw/.


-----Original Message-----
From: Oliver Schonefeld [mailto:schonefeld@ids-mannheim.de] 
Sent: Thursday, June 14, 2012 5:33 AM
To: search-ws-comment@lists.oasis-open.org
Subject: [search-ws-comment] SRU/CQL: clarification about fatal diagnostics

Hello SRU/CQL working group,

currently, I am writing a Java implementation for a SRU server and a SRU
client (for now only Version 1.1/1.2) and from reading the specs it is
not quite clear to me how the exact XML serialization for fatal
diagnostics should look like.
E.g, if a client tries to perform a "searchRetrieve" operation and omits
the query parameter, shall the fatal diagnostic be wrapped inside a
<searchRetrieveResponse> element, like:
<sru:searchRetrieveResponse xmlns:sru="..">
     <diag:diagnostic xmlns:diag="..">

And if so, should a fatal diagnostic for e.g. a "scan" operation than
analogously be wrapped inside a <scanResponse> element?
Or is the server supposed to return the diagnostics element? Or any
other serialization?
Various currently existing servers have a different behavior. E.g, the
Oxford English Dictionary[1] wraps in the <searchRetrieveResponse>
element, while the Library of Congress[2] puts the diagnostic in the
<diagnostics> element of a <explainResponse> and the German National
Library[3] just sends the diagnostics. What is the correct behavior?
The available XML schemas for SRU don't really provide better insights.
Maybe the section in the spec can be made more definite, maybe with an
explicit example of the complete XML serialization of a fatal diagnostic
for a, e.g. "searchRetrieve" operation.

Btw, IMHO the behavior of the Oxford English Dictionary makes most sense.

Thanks and best regards,

[1] http://www.oed.com/srupage
[2] http://z3950.loc.gov:7090/voyager
[3] http://services.dnb.de/sru/dnb
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/

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