RE: ATOM representation of search result facets

Hi Dret,

>> 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.

>i'd suggest to use profiles
>(http://tools.ietf.org/html/draft-wilde-profile-link-02) to signal that
>overloading of the media type, and ideally a new version of OpenSearch
>would make that explicit by adding a profile URI for OpenSearch.

How does the client signal to the server that it wants and understands the extended semantics? 

BTW, you mention in http://tools.ietf.org/html/draft-wilde-profile-link-02#section-5.4 that the client has no way to request and the server no way to communicate that it supports atompub.  The atompub spec defines the application/atom+xml;type=feed media type (and others, such as service documents).  So I don't see a need for profiles there.

Regards,
Peter