RE: ATOM representation of search result facets

"Rushforth, Peter" <[email protected]>
Newsgroups gmane.comp.web.services.rest
Message-ID <1CD55F04538DEA4F85F3ADF7745464AF1AE4ACF8@S-BSC-MBX1.nrn.nrcan.gc.ca>
Hi Erik,


>It's not interesting to ask if it is more or less RESTful to do things using OpenSearch.  I feel
>it's a way of decoupling the server and the client; the server may or may not include
><Query> elements, and the clients may or may not understand them if they do, and don't >break if they're not there.  It caters for evolvability in both, and that's a big benefit.

Rich did ask about REST.  You've given him suggestions about extending atom to include Opensearch markup, without mentioning how this impacts the RESTful-ness of the interactions.

If one extends or overloads atom content with Opensearch or elements in a custom or no namespace, you are still changing the semantics of the content.  To maintain the self-describing messages constraint, you need to do something about the media type, otherwise that content remains opaque, or out-of-band.

Peter
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.