Re: ATOM representation of search result facets
Erlend Hamnaberg <[email protected]>
| Newsgroups | gmane.comp.web.services.rest |
|---|---|
| Message-ID | <CAKj3E3Zm-HJFtJo1NcNO_quasdA94LgcqWcMmPKtAESmDfj5Fw@mail.gmail.com> |
> > > > 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. > > I am sort of agreeing with Peter here. Atompub allows adding a app:collection to any feed, allowing the semantics of atompub being carried into any type of feed. that's an interesting way to look at it. are you suggesting that if a > feed is requested/served with application/atom+xml it should be > considered a non-atompub feed, and if it's requested/served with > application/atom+xml;type=feed it should be considered an > atompub-capable feed? that's not how i have read the spec so far, but > maybe that's what it says; anybody else having an opinion about this one? > > thanks and cheers, > > > dret. > > See: http://tools.ietf.org/html/rfc5023#section-8.3.5 -- Erlend