<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>YegorKuznetsov:comments</title><link>http://www.redherring.com/Home/</link><description>Home</description><language>en-us</language><image><url>http://www.redherring.com/logo/32.jpg</url><link>http://www.redherring.com/Home/</link><title>Home</title></image><copyright>RedHerring</copyright><managingEditor>managing_editor</managingEditor><webMaster>webmaster</webMaster><pubDate>Mon, 23 Nov 2009 00:40:03 GMT</pubDate><lastBuildDate>Mon, 23 Nov 2009 00:40:03 GMT</lastBuildDate><generator>BlogTronix RSS Generator v.1.0</generator><ttl>20</ttl><item><title>
Ken, great story on Endeca!

We will ...</title><link>http://www.redherring.com/Home/23564#3769</link><description><![CDATA[
Ken, great story on Endeca!

We will probably see more activity in this space, and major players wiil be looking for totally new search technologies. Endeca and other vendors it competes with in the enterprise search space have one limitation in common. They all base their search on keyword recognition, inverted indexes, linguistic and semantic ...]]></description><author>Yegor Kuznetsov</author><category>Finance</category><category>Internet</category><category>General news</category><category>Archives</category><pubDate>Thu, 24 Jan 2008 05:49:22 GMT</pubDate><guid>http://www.redherring.com/Home/23564#3769</guid></item><item><title> Tomio, great story on Semantra! As far ...</title><link>http://www.redherring.com/Home/22582#151</link><description><![CDATA[ Tomio, great story on Semantra! As far as I understand, Semantra’s semantic search solution is still based on keyword recognition (like solutions of other players – Google, FAST or Convera). 
But what if the keyword is misspelled? Will the semantic search work in this case? Or if you do not know exactly what you are looking for, just have a vague ...]]></description><author>Yegor Kuznetsov</author><category>Internet</category><pubDate>Fri, 17 Aug 2007 05:50:27 GMT</pubDate><guid>http://www.redherring.com/Home/22582#151</guid></item></channel></rss>