<?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: Yahoo! Research + MicroSoft Research vs. Google Research</title>
	<atom:link href="http://www.midasoracle.org/2007/07/16/yahoo-research-microsoft-research-vs-google-research/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.midasoracle.org/2007/07/16/yahoo-research-microsoft-research-vs-google-research/</link>
	<description>Prediction Markets, etc.</description>
	<lastBuildDate>Thu, 02 Feb 2012 23:13:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Test for Prediction Markets: They Say Obama, but Polls Say It&#8217;s Tied &#171; Shepherd&#8217;s Pi</title>
		<link>http://www.midasoracle.org/2007/07/16/yahoo-research-microsoft-research-vs-google-research/#comment-20392</link>
		<dc:creator>Test for Prediction Markets: They Say Obama, but Polls Say It&#8217;s Tied &#171; Shepherd&#8217;s Pi</dc:creator>
		<pubDate>Sun, 13 Jul 2008 08:43:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.midasoracle.org/2007/07/16/yahoo-research-microsoft-research-vs-google-research/#comment-20392</guid>
		<description>[...] running an internal one as the &#8220;Information Forecasting Exchange&#8221; from 2003-2006.Â Internal efforts at Yahoo and Google have also been noted. But frankly, I&#8217;m not actively promoting PM&#8217;s to government friends, as I don&#8217;t [...]</description>
		<content:encoded><![CDATA[<p>[...] running an internal one as the &#8220;Information Forecasting Exchange&#8221; from 2003-2006.Â Internal efforts at Yahoo and Google have also been noted. But frankly, I&#8217;m not actively promoting PM&#8217;s to government friends, as I don&#8217;t [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

