<?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: Code to text ratio analysis</title>
	<atom:link href="http://www.sulumitsretsambew.org/code-to-text-ratio-analysis/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sulumitsretsambew.org/code-to-text-ratio-analysis/</link>
	<description>Sulumits Retsambew is entry by Evil Science for NetBuilders seo contest.</description>
	<lastBuildDate>Wed, 30 Mar 2011 10:03:54 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Brad</title>
		<link>http://www.sulumitsretsambew.org/code-to-text-ratio-analysis/comment-page-1/#comment-1150</link>
		<dc:creator>Brad</dc:creator>
		<pubDate>Thu, 26 Aug 2010 01:10:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.sulumitsretsambew.org/?p=513#comment-1150</guid>
		<description>Code to Text Ratio cannot be characterized in the same way for any site.
An informative site with no operative events besides navigation and links will probably have a higher Code to Text Ratio. However, for examle, a large e-commerce based web-site will have a great deal of action objects code for products selection, shopping cart, buy-now buttons etc&#039;.
So there is no real ground for comparison.</description>
		<content:encoded><![CDATA[<p>Code to Text Ratio cannot be characterized in the same way for any site.<br />
An informative site with no operative events besides navigation and links will probably have a higher Code to Text Ratio. However, for examle, a large e-commerce based web-site will have a great deal of action objects code for products selection, shopping cart, buy-now buttons etc&#8217;.<br />
So there is no real ground for comparison.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

