<?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: Lawsuit Asks Google to Reveal&#160;Algorithm</title>
	<atom:link href="http://www.searchenginejournal.com/lawsuit-asks-google-to-reveal-algorithm/3149/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.searchenginejournal.com/lawsuit-asks-google-to-reveal-algorithm/3149/</link>
	<description>Latest Search Engine News from the Search Engine Journal</description>
	<lastBuildDate>Sat, 20 Mar 2010 23:19:02 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Martin</title>
		<link>http://www.searchenginejournal.com/lawsuit-asks-google-to-reveal-algorithm/3149/comment-page-1/#comment-68750</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Tue, 21 Mar 2006 13:06:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/?p=3149#comment-68750</guid>
		<description>While I agree that KinderStart are unlikely to win this case, it will be interesting to see if they get Google&#039;s algorithm disclosed.

The claim that they are making is that Google targeted them specifically and without reason which could be seen as anticompetitive. If this were the case then Google could be in trouble.

The trouble is that without knowing exactly what Google&#039;s algorithm is it is impossible to prove one way or the other.

The court may see Google&#039;s secrecy as withholding evidence which is a big no no, especially for information that should be protectable using Intellectual Property laws.</description>
		<content:encoded><![CDATA[<p>While I agree that KinderStart are unlikely to win this case, it will be interesting to see if they get Google&#8217;s algorithm disclosed.</p>
<p>The claim that they are making is that Google targeted them specifically and without reason which could be seen as anticompetitive. If this were the case then Google could be in trouble.</p>
<p>The trouble is that without knowing exactly what Google&#8217;s algorithm is it is impossible to prove one way or the other.</p>
<p>The court may see Google&#8217;s secrecy as withholding evidence which is a big no no, especially for information that should be protectable using Intellectual Property laws.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian</title>
		<link>http://www.searchenginejournal.com/lawsuit-asks-google-to-reveal-algorithm/3149/comment-page-1/#comment-68661</link>
		<dc:creator>Christian</dc:creator>
		<pubDate>Mon, 20 Mar 2006 18:23:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/?p=3149#comment-68661</guid>
		<description>Here you go!
No need for a lawsuit :-)
Pagerank algorithm published:
http://www-db.stanford.edu/~backrub/google.html

http://dbpubs.stanford.edu:8090/pub/1999-66
Cheers!
- C</description>
		<content:encoded><![CDATA[<p>Here you go!<br />
No need for a lawsuit :-)<br />
Pagerank algorithm published:<br />
<a href="http://www-db.stanford.edu/~backrub/google.html" rel="nofollow">http://www-db.stanford.edu/~backrub/google.html</a></p>
<p><a href="http://dbpubs.stanford.edu:8090/pub/1999-66" rel="nofollow">http://dbpubs.stanford.edu:8090/pub/1999-66</a><br />
Cheers!<br />
- C</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: teddie</title>
		<link>http://www.searchenginejournal.com/lawsuit-asks-google-to-reveal-algorithm/3149/comment-page-1/#comment-68652</link>
		<dc:creator>teddie</dc:creator>
		<pubDate>Mon, 20 Mar 2006 17:44:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/?p=3149#comment-68652</guid>
		<description>I guess that invalid HTML and triple opening body tags, with one at the top that could easily be regexed by a crawler as a closing tag  in their code didn&#039;t have anything to do with it then?</description>
		<content:encoded><![CDATA[<p>I guess that invalid HTML and triple opening body tags, with one at the top that could easily be regexed by a crawler as a closing tag  in their code didn&#8217;t have anything to do with it then?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
