<?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: Belgian newspapers seeking £39m damages from Google</title>
	<atom:link href="http://blogs.journalism.co.uk/2008/05/28/belgian-newspapers-seeking-39m-damages-from-google/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.journalism.co.uk/2008/05/28/belgian-newspapers-seeking-39m-damages-from-google/</link>
	<description>Online journalism news</description>
	<lastBuildDate>Tue, 24 Jan 2012 19:16:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Journalism.co.uk Editors&#8217; Blog &#187; Blog Archive &#187; Belgian newspaper group to take European Commission to court again after its first challenge over news aggregator fails</title>
		<link>http://blogs.journalism.co.uk/2008/05/28/belgian-newspapers-seeking-39m-damages-from-google/comment-page-1/#comment-5623</link>
		<dc:creator>Journalism.co.uk Editors&#8217; Blog &#187; Blog Archive &#187; Belgian newspaper group to take European Commission to court again after its first challenge over news aggregator fails</dc:creator>
		<pubDate>Thu, 03 Jul 2008 10:04:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.journalism.co.uk/editors/2008/05/28/belgian-newspapers-seeking-39m-damages-from-google/#comment-5623</guid>
		<description>[...] newspaper group Copiepresse – yes, the one that’s in that legal wrangle with Google – is about to re-enter a copyright battle with a second online publisher – this time it’s the [...]</description>
		<content:encoded><![CDATA[<p>[...] newspaper group Copiepresse – yes, the one that’s in that legal wrangle with Google – is about to re-enter a copyright battle with a second online publisher – this time it’s the [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

