Main problem with imposing is that Atom and RSS both allow for extensions. If Hubs normalise, presumably they can only do so to a comment subset of elements/namespaces. Not a huge deal for blogs perhaps, but even blogs use a lot of namespaced extensions these days. And blogs are not the only form of distributable content (e.g. media, podcasts, geographic info).
So it's very much up to individual Hubs to decide. Paddy Pádraic Brady http://blog.astrumfutura.com http://www.survivethedeepend.com OpenID Europe Foundation Irish Representative ________________________________ From: Matthew Terenzio <[email protected]> To: [email protected] Sent: Sun, December 27, 2009 11:15:56 PM Subject: Re: [pubsubhubbub] Normalizing Fat Pings to Atom Maybe some feed suppliers don't want hubs redistributing in other formats, for one reason or another. This could happen outside of their knowledge if hubs federate with each other, which seems to be acceptable. I don't have a good reason why anyone would care, but I'd bet someone would eventually have a problem with it. On Sun, Dec 27, 2009 at 5:08 PM, rcade <[email protected]> wrote: One of the design philosophies that I like about PubSubHubbub is the >>decision to put as much of the complexity in the hub as possible, >>making it simple for feed publishers and readers to support the >>protocol. For this reason, when I created a Java application that >>receives updates, I was surprised when some fat pings arrived in RSS >>2.0 format instead of Atom. > >>Is there a possibility that fat pings will be normalized to Atom, no >>matter what format the originating feed employs? > >>If you normalize the pings, PuSH clients only have to support one feed >>format. If you don't, clients have to support Atom, RSS 0.9, RSS 0.91 >>(Netscape), RSS 0.91 (UserLand), RSS 0.92, RSS 1.0 and RSS 2.0. > >>Although all current feed-reading applications must support all of >>those formats, if PuSH normalizes pings, it makes it possible for >>future applications to be developed that only have to support Atom. >>That would be a nice selling point for developers. >
