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] Groups - sru-2-0-draft-oct-19.doc uploaded


11.1.1: Change "UI" references to "Application"

11.1.3: Really?  Aren't we past that now?  I can imagine an SRU server that is compliant in all other ways but has no business reason to return XML.

11.1.4: I know this is late to bring this up, but our wording on Diagnostics is very much XML oriented.  I know I said we could continue to use XML for modeling purposes, but we can't do that in a conformance statement.

11.1.5:  This should not be a requirement.  I've got lots of Application code that doesn't use the Explain record.

11.2.2: Like 11.1.3, I'm not sure CQL is a requirement.

11.2.3: See 11.1.3.

11.2.3: See 11.1.4.

11.2.5: I'm okay with an Explain record requirement, even for non-XML servers.  But, the assumption that the Explain record is at the base URL is too restrictive.  The Explain record points at the database, so they don't need to be at related URLs.  We probably ought to have a way to say in an Explain record that there is an OpenSearch description document associated with the database as well.  Then a minimal Explain record can be exposed for conformance purposes and just point to the OpenSearch description document.

Annex A: The GET and POST bindings don't specify how the response is returned.  We know it is in the content body, but we need to say that.

A.3: line 883: The response to a GET or POST request need not be XML.  Refer instead to the SRU schema.

There's no mention of our WSDL here.  Seems like a flaw.

Does an SRU server that only supports the SOAP binding fail the SRU conformance test because it doesn’t support requests for application/sru+xml?  Yet another reason to reconsider 11.1.3.

Annex D doesn’t say anything, it just has an ATOM record.  You need to say that an ATOM response supports the inclusion of elements from other schemas and that SRU elements can be used, even where their use would be non-conformant with the SRU schema.  You should specifically highlight the namespace issue.

Thanks, Ray!

Ralph


> -----Original Message-----
> From: rden@loc.gov [mailto:rden@loc.gov]
> Sent: Monday, October 19, 2009 4:45 PM
> To: search-ws@lists.oasis-open.org
> Subject: [search-ws] Groups - sru-2-0-draft-oct-19.doc uploaded
> 
> Please review the following sections carefully:
> 
> - Model, section 1.
> - conformance, section 11.
> - Bindings to Lower Level Protocol, Annex A.
> - Extensions for Alternative Response Formats, Annex D.
> 
>  -- Ray Denenberg
> 
> The document named sru-2-0-draft-oct-19.doc has been submitted by Ray
> Denenberg to the OASIS Search Web Services TC document repository.
> 
> Document Description:
> 
> 
> View Document Details:
> http://www.oasis-open.org/committees/document.php?document_id=34751
> 
> Download Document:
> http://www.oasis-open.org/committees/download.php/34751/sru-2-0-draft-oct-
> 19.doc
> 
> 
> PLEASE NOTE:  If the above links do not work for you, your email application
> may be breaking the link into two pieces.  You may be able to copy and paste
> the entire link address into the address field of your web browser.
> 
> -OASIS Open Administration


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