<?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: Learning Python</title>
	<atom:link href="http://rossshannon.com/2005/12/06/learning-python/feed/" rel="self" type="application/rss+xml" />
	<link>http://rossshannon.com/2005/12/06/learning-python/</link>
	<description>Researchin' the day away...</description>
	<lastBuildDate>Thu, 12 Jan 2012 21:49:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Aaron</title>
		<link>http://rossshannon.com/2005/12/06/learning-python/comment-page-1/#comment-5</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Fri, 09 Dec 2005 02:18:59 +0000</pubDate>
		<guid isPermaLink="false">http://yourhtmlsource.com/phdblog/?p=12#comment-5</guid>
		<description>I go with Joe... ;-) 

Try to thing about this assignment in terms of the software engineering involved. ie. an interface between components that can change where you would like to automatically detect this and perhaps loads up an alternate scrapper component as a result, perhaps a simpler one. ie. you have a tailored scrapper but you never know when or where the content publishers will mess with the interface so you ripple back to a more basic scrapper at each stage being able to test that what you scrap is content and not noise... 

Aaron.</description>
		<content:encoded><![CDATA[<p>I go with Joe&#8230; <img src='http://rossshannon.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>Try to thing about this assignment in terms of the software engineering involved. ie. an interface between components that can change where you would like to automatically detect this and perhaps loads up an alternate scrapper component as a result, perhaps a simpler one. ie. you have a tailored scrapper but you never know when or where the content publishers will mess with the interface so you ripple back to a more basic scrapper at each stage being able to test that what you scrap is content and not noise&#8230; </p>
<p>Aaron.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
