On Thu, Feb 18, 2010 at 10:28 PM, Brad Fitzpatrick <[email protected]> wrote:
> I hadn't heard that it was being actually considered. I don't think it was beyond the thread proposing to wrap JSON in Atom (ugh). That said, I don't think it would be too complex. > There's a serious complexity and thus adoption cost to every new optional > feature added, so we're going out of our way to keep the core minimal. > It seems like you'd need to specify a discovery mechanism (section 5) and then the semantics around content distribution (section 7.3). Aggregation (section 7.5) already has a note saying it's only for Atom feeds anyway. For discovery, what about requiring root elements named pubsubhubbub.hub and pubsubhubbub.self. They'd have the same meaning as the fields in Atom or RSS. What would JSON provide other than syntactic preference? > The Activity Streams group is also starting to work on a JSON version (based on implementor feedback), but losing push would be a poor tradeoff. Another use case would be letting people subscribe to changes in a user's Portable Contacts file. I update my photo and that's pushed out to sites who have subscribed to it. Best Buy also has a products API which I could subscribe to inventory changes of iPod stock near me: http://api.remix.bestbuy.com/v1/stores(area(94158,10))+products(name=ipod*touch* 32gb*)?apiKey={API KEY HERE}&format=json --David > On Tue, Feb 16, 2010 at 4:41 PM, Wei Zhu (Facebook) > <[email protected]>wrote: > >> Hi, >> >> I'd like to know what the current status is in terms of supporting >> JSON as a response format in Pubsubhubbub spec. I had heard there was >> some talk about adding this support in the spec and would love to see >> it happen. >> >> Thanks. >> >> Wei >> > >
