Thursday, February 23, 2006, 6:37:50 AM, you wrote:
> Does someone who has access to an MSFT system care to take a > look at this? I have been playing with IE7, and it is interesting to see what happens when you click on a feed and "view source". If the feed hasn't been subscribed to, you just see the feed source as you would expect. If you have subscribed to the feed however, you see Windows's internal representation of the feed, which is normalised to a sort of RSS2++. I assume that this is what is exposed when you use the APIs to access the XML. (Hmm - giving access to the XML in this way is a brave move, XML has a huge surface area for an API, practically any change to the XML produced by Windows could break client applications, and I didn't find any documentation for the normalised RSS2++ ). What is interesting is that Atom is handled (reasonably well), by converting the Atom to RSS2. The logic seems to replace atom elements with there RSS2 equivalents and the loss in fidelity is not too great (eg atom:updated -> pubDate), and to leave the Atom as-is for awkward (eg: [EMAIL PROTECTED]/xml) There is definitely some loss in fidelity though. It would be nice to run an extreme Atom feed through the process to see what gets lost. xml:base appears to get corrupted, and unless the API provides access to the baseURI of each entry there is a risk of data loss (as the xml:base at feed level may change between polls it therefore needs to be preserved with each entry.) Does anyone have a bad-ass atom feed with IRIs, binary content, atom:source, xml:base, xml:lang, extensions etc for testing? -- Dave
