<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: RSS &amp; Atom specifications</title>
	<atom:link href="http://toxicsoftware.com/rss_atom_specifications/feed/" rel="self" type="application/rss+xml" />
	<link>http://toxicsoftware.com/rss_atom_specifications/</link>
	<description>RANDOMIZE USR 0</description>
	<lastBuildDate>Thu, 17 Dec 2009 15:12:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Two different approaches to setting up RSS feeds in ASP.Net MVC &#171; Redditech &#8216;Ground Zero&#8217; Blog</title>
		<link>http://toxicsoftware.com/rss_atom_specifications/comment-page-1/#comment-22235</link>
		<dc:creator>Two different approaches to setting up RSS feeds in ASP.Net MVC &#171; Redditech &#8216;Ground Zero&#8217; Blog</dc:creator>
		<pubDate>Fri, 30 Jan 2009 15:42:07 +0000</pubDate>
		<guid isPermaLink="false">http://toxicsoftware.com/blog/rss_atom_specifications/#comment-22235</guid>
		<description>&lt;p&gt;[...] So that means there are still merits of using the 1st link&#8217;s method, since you as the developer, are in essence, in full control of ensuring that the View renders the proper parameters and that all ViewData is in the appropriate locations within it. This has its benefits, in cases for example where the standard may change or be upgraded before the Framework objects themselves have had a chance to be updated as well. The counter to this is, of course, that you are also fully responsible for a shoddy implementation of the XML specification if you are not thorough with the RSS and ATOM specification guidelines. [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] So that means there are still merits of using the 1st link&#8217;s method, since you as the developer, are in essence, in full control of ensuring that the View renders the proper parameters and that all ViewData is in the appropriate locations within it. This has its benefits, in cases for example where the standard may change or be upgraded before the Framework objects themselves have had a chance to be updated as well. The counter to this is, of course, that you are also fully responsible for a shoddy implementation of the XML specification if you are not thorough with the RSS and ATOM specification guidelines. [...]</p>]]></content:encoded>
	</item>
</channel>
</rss>
