This looks interesting! Here are some thoughts I had while reading through it:
* It would be nice if there was a Content-Type required (or at least encouraged) for topics, so that hubs wouldn't have to infer the content type from the content. This would make it more efficient for a single hub to support both Atom/RSS and JSON streams. * What's the relation between the Discovery Document and the Notification Message? It seems like it's two different names for what amounts to the same format, that's just used differently between the publisher->hub and the hub->subscriber. * In section 5, it says "Implementations MUST ignore properties that they do not understand." Do you mean ignore and drop these properties, or ignore and preserve? I feel like it could be read either way. * Section 6: "This section defines a message format that can be used by the publisher..." <- should that be subscriber, or am I misreading this entirely? * Section 7 doesn't feel right to me. What you want is an equivalence comparison for JSON objects; what you're describing is a specific optimized algorithm for one. This is just an implementation detail for the hub; it doesn't need to be part of the spec. * What are the pros and cons of this proposal, versus wrapping JSON objects in an Atom feed? --Ravi On Sat, Jun 5, 2010 at 12:33 PM, Martin Atkins <[email protected]> wrote: > > Hi all, > > Today I wrote up a first draft for a variation on PubSubHubbub for JSON-based > applications: > > http://martin.atkins.me.uk/specs/pubsubhubbub-json > > As noted in the specification document, the goal is to make the hub as dumb > as possible, having the payloads just be opaque JSON objects as far as the > hub is concerned. This means that this can be used for multiple JSON-based > applications without changing the hub. > > The near-term goal is to allow the fledgling "Activity Streams API" spec to > use this as a transport, but I also want to make it useful for delivering > other content and for proprietary payloads like those used in Facebook's > real-time notifications API. > > It'd be nice if this format could be supported alongside Atom and RSS in the > App Engine hub reference implementation, though I've not yet dug deeply into > the code to figure out how hard that might be. > > >
