Consider non time oriented feeds (like top 10 lists). They exist; a change could be just a reordering...
On Tuesday, June 15, 2010, Kevin Marks <[email protected]> wrote: > Existing practice for exporting blogs is often a whole feed, but I agree it > isn't a common case; on the other hand with something like a contacts list > completeness is important. > There is an assumption with PUSH at the moment that you can always fetch the > original feed. With Monica's addition of the REST verbs, this gets a little > more tricky. > On Jun 15, 2010 8:16 PM, "Martin Atkins" <[email protected]> wrote: > > On 06/15/2010 06:49 PM, Monica Keller wrote: >> >> >> Do we think that people will ever want "whole" re... > I don't see any reason why someone would use a whole-resource subscription > for an Atom feed but the ability to express it comes from the fact that a > Link header indicates a hub that accepts whole-resource subscriptions, and a > Link header can be published on any resource. Really I was just trying to be > clear about the meaning of this rather than suggesting that you would > actually do it in practice. > > The other alternative would be to say that you are simply not allowed to > publish a Link header if your resource is a stream/feed resource, but I don't > think that restriction would really buy us much. > > > > > > -- -- John Panzer / Google [email protected] / abstractioneer.org / @jpanzer
