[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [search-ws] Explain Conformance
In that case I'd rather drop the sentence. I don't think SHOULD is appropriate in a conformance clause. An alternative approach would be to define conformance levels, two levels, 0 and 1, where in level 1 we require a schema (and other important features, if any). Does anyone want to think about that? --Ray From: LeVan,Ralph [mailto:levan@oclc.org] A client can get along just fine without specifying a schema in the request, so having schemas mandatory in explain seems excessive. Ralph From: Ray Denenberg, Library of Congress [mailto:rden@loc.gov] How about if we make <shemaInfo> a MUST rather than SHOULD. -Ray From: LeVan,Ralph [mailto:levan@oclc.org] An SRU server MUST provide an Explain document. The Explain document MUST contain a <serverInfo> element with <host>, <port> and <database> subelements. An HTTP URL constructed from the <host>, <port> and <database> elements must provide a sufficient base URL from which Explain and SearchRetrieve URLs can be built. An SRU server SHOULD provide a <schemaInfo> element. Even if the server does not allow clients to specify returned record schemas, it SHOULD specify the default schemas that records will be returned in, in a <schema> subelement. Ralph |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]