Sean Lyndersay wrote: > > The normalized XML that you're seeing in View Source is also > accessible from the feed APIs, so the XML we generate is a format we > expect to support in perpetuity. > > It's designed to be a relatively simple format that application > developers can rely on in the same way that they rely on APIs in the > object model, so we map all common elements from other formats into > RSS 2.0 (the basis for our native format). Why RSS 2.0? Because it's > the format used by the majority of feeds on the web.
>From reports I have seen, you are doing things like adding type attributes on the description element? If so, it isn't RSS 2.0. How do you plan to handle multiple enclosures? How about HTML in titles? On Feed-Tech I saw a post by Phil Stanhope indicating the importance of sub-second times in certain scenarios. How will this be expressed in RFC 822 format? How about content that is in a binary format? I can go on... > Any case of data-loss is a bug that we'll address If that is a blanket statement, then I expect that you will be seeing a lot of bug reports. - Sam Ruby
