This is confusing to me. Feeds are, basically, "stuff happens over time for a specific topic, identified by a URL; we show it to you in reverse chronological order so you can see the last few things; and we give you timestamps and unique IDs so you can make sense of the data".
PubSubHubbub is "stuff happens over time for a specific topic, identified by a URL; we push it to you in chronological order so you can see the things as they happen; and we give you timestamps and unique IDs so you can make sense of the data". Which part of the former doesn't translate to the latter? Or are you saying that you only want a subset of what PubSubHubbub gives you? You can also have the very simple case of "a single thing is changing over time, its unique ID is just its URL, and its timestamp is the last modified date in the headers, so don't worry about anything else" and that's a fine use case to support too and I think we're close to just doing it with the arbitrary-content support. What am I missing? -- John Panzer / Google [email protected] / abstractioneer.org <http://www.abstractioneer.org/> / @jpanzer On Fri, Feb 25, 2011 at 11:34 AM, Jeff Lindsay <[email protected]> wrote: > As I understand it, the issue is not format (that's just an > implementation issue), but the dedication to the semantics of feeds. I > don't see any reason why this needs to be enforced. It seems like a > religious debate, "but they should be using feed semantics!" Well, no, > not if they don't want to. And if that's the case, they'll either not > use PubSubHubbub or continue bastardizing it. > > -jeff > > On Fri, Feb 25, 2011 at 9:27 AM, Tamer Yousef <[email protected]> > wrote: > > I'm supporting Julien and the rest of you, just support both: > > Putting extra parameters in the subscription request to tell the HUB your > > desired format, JSON or XML. > > -Tamer > > > > On Fri, Feb 25, 2011 at 7:15 AM, Julien Genestoux > > <[email protected]> wrote: > >> > >> Just to make it even more clear : I'm not fighting for either XML or > >> against JSON. > >> I'm just fighting for a common data representation model that can be > used > >> for heterogenous data. > >> I don't care if it's XML based, JSON based, YAML based, HTML based or > >> anything. I just want to make sure that the apps consuming it can > blindly > >> consume it whether it's coming from github, facebook, instagram, > nytimes, > >> etsy or anything else. > > > > > > -- > Jeff Lindsay > http://progrium.com >
