<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Google-DoubleClick Merger Encounters More Setbacks On Capitol Hill</title>
	<atom:link href="http://paidcontent.org/2007/12/13/419-google-doubleclick-merger-encounters-more-roadblocks-in-washington/feed/" rel="self" type="application/rss+xml" />
	<link>http://paidcontent.org/2007/12/13/419-google-doubleclick-merger-encounters-more-roadblocks-in-washington/</link>
	<description>The economics of digital content</description>
	<lastBuildDate>Thu, 23 May 2013 13:16:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Jeffrey Chester</title>
		<link>http://paidcontent.org/2007/12/13/419-google-doubleclick-merger-encounters-more-roadblocks-in-washington/#comment-55676</link>
		<dc:creator><![CDATA[Jeffrey Chester]]></dc:creator>
		<pubDate>Thu, 13 Dec 2007 12:20:53 +0000</pubDate>
		<guid isPermaLink="false">http://paidcontent.wp.gostage.it/2007/12/13/419-google-doubleclick-merger-encounters-more-roadblocks-in-washington/#comment-55676</guid>
		<description><![CDATA[My group opposes the merger on both competition and privacy grounds.  Besides, as we have explained to the FTC and others, the data collection and targeted use intrinsic to the business goals of the merger and protecting user privacy are inextricably linked.]]></description>
		<content:encoded><![CDATA[<p>My group opposes the merger on both competition and privacy grounds.  Besides, as we have explained to the FTC and others, the data collection and targeted use intrinsic to the business goals of the merger and protecting user privacy are inextricably linked.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
