[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: OpenSearch relationship to Search-WS
rden@loc.gov wrote: > Please give special consideration to the new Annex D: OpenSearch > Presently, I am not yet getting the relationship between Appendix D and the rest of the spec. It is either not obvious or perhaps it is work that remains to be done. As I understand things, Cql expressions are the central thing in performing a search operation in a serach engine that implements Search-WS interface. A key info I am missing is how does an opensearch client use open search interface to issue a Cql query? What is the use model for such an opensearch client? Although I like opensearch, I am concerned about an OASIS spec having a normative dependency on a spec that is not even on a standards-track. I can see that we are copying OpenSearch spec content into our spec to work around this. This seems very inadvisable. An alternative way to deal with opensearch would to: * Make Appendix D Informative / Non-normative. * Remove the duplication of opensearch content from Appendix D and just reference: <http://www.opensearch.org/Specifications/OpenSearch/1.1> * Add content that describes: o How a Search-WS server *MAY* implement support for OpenSearch based search clients o How an OpenSearch Client *MAY* search a Search-WS server using opensearch BTW, FWIW, I am trying to deal with the same issue (how to support opensearch) in RegRep 4.0, OGC Catalog, OGC Web Registry Service specs and that is the direction I am leaning towards at present. I would like to understand the rationale for the approach taken in Search-WS. Ideally, these various specs should address the opensearch issue in a consistent manner. -- Regards, Farrukh Web: http://www.wellfleetsoftware.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]