<?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: Released SEO No Duplicate Version 0.2</title>
	<atom:link href="http://omninoggin.com/wordpress-posts/released-seo-no-duplicate-version-02/feed/" rel="self" type="application/rss+xml" />
	<link>http://omninoggin.com/wordpress-posts/released-seo-no-duplicate-version-02/</link>
	<description>WordPress and Web Dev From the Ground Up</description>
	<lastBuildDate>Fri, 05 Mar 2010 03:40:58 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: googlechromedownload</title>
		<link>http://omninoggin.com/wordpress-posts/released-seo-no-duplicate-version-02/#comment-1946</link>
		<dc:creator>googlechromedownload</dc:creator>
		<pubDate>Mon, 16 Feb 2009 19:19:10 +0000</pubDate>
		<guid isPermaLink="false">http://omninoggin.com/?p=455#comment-1946</guid>
		<description>is this version tested with wordpress yet? </description>
		<content:encoded><![CDATA[<p>is this version tested with wordpress yet?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: redwall_hp</title>
		<link>http://omninoggin.com/wordpress-posts/released-seo-no-duplicate-version-02/#comment-1929</link>
		<dc:creator>redwall_hp</dc:creator>
		<pubDate>Sun, 15 Feb 2009 23:47:30 +0000</pubDate>
		<guid isPermaLink="false">http://omninoggin.com/?p=455#comment-1929</guid>
		<description>That&#039;s what I use too, but I normally start at 1.0.0. Then I up the second digit for the major releases, the third digit for bug fixes. The first digit will change after a &quot;major architectural change&quot; or when the second digit surpasses 9, whichever happens first. </description>
		<content:encoded><![CDATA[<p>That&#039;s what I use too, but I normally start at 1.0.0. Then I up the second digit for the major releases, the third digit for bug fixes. The first digit will change after a &quot;major architectural change&quot; or when the second digit surpasses 9, whichever happens first.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thaya Kareeson</title>
		<link>http://omninoggin.com/wordpress-posts/released-seo-no-duplicate-version-02/#comment-1925</link>
		<dc:creator>Thaya Kareeson</dc:creator>
		<pubDate>Sun, 15 Feb 2009 22:22:54 +0000</pubDate>
		<guid isPermaLink="false">http://omninoggin.com/?p=455#comment-1925</guid>
		<description>:) I like the x.x.x version system. 
1st digit for major architectural changes 
2nd digit for enhancements 
3rd digit for bug fixes </description>
		<content:encoded><![CDATA[<p> <img src='http://omninoggin.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  I like the x.x.x version system.<br />
1st digit for major architectural changes<br />
2nd digit for enhancements<br />
3rd digit for bug fixes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: redwall_hp</title>
		<link>http://omninoggin.com/wordpress-posts/released-seo-no-duplicate-version-02/#comment-1924</link>
		<dc:creator>redwall_hp</dc:creator>
		<pubDate>Sun, 15 Feb 2009 22:13:28 +0000</pubDate>
		<guid isPermaLink="false">http://omninoggin.com/?p=455#comment-1924</guid>
		<description>0.2... Would that make it a beta? :) 
 
Nice to see you&#039;ve implemented my suggestion, as well as Yoast&#039;s. I may have to move to this instead of the code snippet you had in your original post about Canonical URLs. </description>
		<content:encoded><![CDATA[<p>0.2&#8230; Would that make it a beta? <img src='http://omninoggin.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  </p>
<p>Nice to see you&#039;ve implemented my suggestion, as well as Yoast&#039;s. I may have to move to this instead of the code snippet you had in your original post about Canonical URLs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
