Sunday 15 April 2012

rest - RESTful URLs for a search service with an arbitrary number of filtering criteria -


I want to create a permanent web service that implements a search interface for the database of biological data

A specific search request can include a dozen or more features of the data. For example, search for the scientific name, preventing the depth of water below 100 meters. The first trend is to have all the attributes in the query string eg Search Type = Scam and Skin = Mile + Milea and McDaypt = 100 and DyenPath = 0

However, query strings are considered non-silk, see

As the discussions and I am still not clear at this point, my question:

Is there an acceptable standard or pattern for a blank URL for a search service, where a benchmark number can be a filtering value is?

In the rest of the web:

  • component recognizes a special resource.
  • The request-uri's query-string component identifies changes made during a specific filter or presentation
  • Accept The title identifies a particular content-type in which the given resource should be filtered as specified.
  • Acceptable-language header identifies a particular language in which the given resource, file must be presented as a specification.

Then to answer your question:

  GET / species? SearchType = sciname & amp; Scenemon = mola + mola & maxdepth = 100 & amp; Mindepth = 0  

is absolutely appropriate.


No comments:

Post a Comment