<?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: Google Similar Images: Only 20%?!</title>
	<atom:link href="http://irgupf.com/2009/04/22/google-similar-images-only-20/feed/" rel="self" type="application/rss+xml" />
	<link>http://irgupf.com/2009/04/22/google-similar-images-only-20/</link>
	<description>Information Retrieval Research, Issues, and Discussion</description>
	<lastBuildDate>Tue, 14 Jun 2011 14:26:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: dinesh vadhia</title>
		<link>http://irgupf.com/2009/04/22/google-similar-images-only-20/comment-page-1/#comment-915</link>
		<dc:creator>dinesh vadhia</dc:creator>
		<pubDate>Tue, 28 Apr 2009 11:43:42 +0000</pubDate>
		<guid isPermaLink="false">http://irgupf.com/?p=524#comment-915</guid>
		<description>As it is still from Google Lab&#039;s it is probably still a 20% project.  I suspect that image (or content) search scalability is being worked on by most of the mainstream search engines as well as IBM.  Let&#039;s use images as the example: the extraction of features (also called the image signature) from images is not a problem these days though it does require considerable resources and time to process images to extract the features.  

Next, what search model (ie. algorithm) is going to be used to deliver the search results.  From this follows the scalability question.

This 2008 paper provides an almost up to date survey of the state of the art in image search:

Image Retrieval: Ideas, Influences, and Trends of the New Age - http://infolab.stanford.edu/~wangz/project/imsearch/review/JOUR/datta.pdf

Btw, did you have a look at our beta image search at http://www.xyggy.com/image.php ?

Dinesh</description>
		<content:encoded><![CDATA[<p>As it is still from Google Lab&#8217;s it is probably still a 20% project.  I suspect that image (or content) search scalability is being worked on by most of the mainstream search engines as well as IBM.  Let&#8217;s use images as the example: the extraction of features (also called the image signature) from images is not a problem these days though it does require considerable resources and time to process images to extract the features.  </p>
<p>Next, what search model (ie. algorithm) is going to be used to deliver the search results.  From this follows the scalability question.</p>
<p>This 2008 paper provides an almost up to date survey of the state of the art in image search:</p>
<p>Image Retrieval: Ideas, Influences, and Trends of the New Age &#8211; <a href="http://infolab.stanford.edu/~wangz/project/imsearch/review/JOUR/datta.pdf" rel="nofollow">http://infolab.stanford.edu/~wangz/project/imsearch/review/JOUR/datta.pdf</a></p>
<p>Btw, did you have a look at our beta image search at <a href="http://www.xyggy.com/image.php" rel="nofollow">http://www.xyggy.com/image.php</a> ?</p>
<p>Dinesh</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeremy</title>
		<link>http://irgupf.com/2009/04/22/google-similar-images-only-20/comment-page-1/#comment-892</link>
		<dc:creator>jeremy</dc:creator>
		<pubDate>Mon, 27 Apr 2009 18:12:06 +0000</pubDate>
		<guid isPermaLink="false">http://irgupf.com/?p=524#comment-892</guid>
		<description>I agree that scalability makes the problem difficult.  But that still doesn&#039;t address why the project only languished as a 20% project for however many years, rather than being promoted to a full 80% project.  If anything, one would think that the issue of scalability would be one of those core competencies in which Google would rise to the challenge; i.e. Google&#039;s competitive advantage is scalability, and so they&#039;d want to apply 80% effort to it, rather than 20% effort.</description>
		<content:encoded><![CDATA[<p>I agree that scalability makes the problem difficult.  But that still doesn&#8217;t address why the project only languished as a 20% project for however many years, rather than being promoted to a full 80% project.  If anything, one would think that the issue of scalability would be one of those core competencies in which Google would rise to the challenge; i.e. Google&#8217;s competitive advantage is scalability, and so they&#8217;d want to apply 80% effort to it, rather than 20% effort.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dinesh vadhia</title>
		<link>http://irgupf.com/2009/04/22/google-similar-images-only-20/comment-page-1/#comment-824</link>
		<dc:creator>dinesh vadhia</dc:creator>
		<pubDate>Sun, 26 Apr 2009 16:34:09 +0000</pubDate>
		<guid isPermaLink="false">http://irgupf.com/?p=524#comment-824</guid>
		<description>&quot;... why was this not somebody’s 80% project, rather than a 20% time project?&quot;

I&#039;ll hazard a guess - scalability.

Last year, Google estimated that there were approximately one trillion images on the web.  

Using image labels and associated data around the image on a web page gets you only so far.

Content-based image retrieval on the web poses a different set of problems than text based search of which, scalability is the most significant.</description>
		<content:encoded><![CDATA[<p>&#8220;&#8230; why was this not somebody’s 80% project, rather than a 20% time project?&#8221;</p>
<p>I&#8217;ll hazard a guess &#8211; scalability.</p>
<p>Last year, Google estimated that there were approximately one trillion images on the web.  </p>
<p>Using image labels and associated data around the image on a web page gets you only so far.</p>
<p>Content-based image retrieval on the web poses a different set of problems than text based search of which, scalability is the most significant.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

