<?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: Text mining and search, joined at the hip</title>
	<atom:link href="http://www.texttechnologies.com/2006/11/11/text-mining-and-search-joined-at-the-hip/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.texttechnologies.com/2006/11/11/text-mining-and-search-joined-at-the-hip/</link>
	<description>Understanding technology ... in both senses of the phrase</description>
	<lastBuildDate>Sun, 12 Feb 2012 01:32:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.3</generator>
	<item>
		<title>By: Text Technologies&#187;Blog Archive &#187; The text mining vendors continue to lack constructive vision</title>
		<link>http://www.texttechnologies.com/2006/11/11/text-mining-and-search-joined-at-the-hip/#comment-29067</link>
		<dc:creator>Text Technologies&#187;Blog Archive &#187; The text mining vendors continue to lack constructive vision</dc:creator>
		<pubDate>Wed, 19 Dec 2007 02:39:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/2006/11/11/text-mining-and-search-joined-at-the-hip/#comment-29067</guid>
		<description>[...] active in text search, except to some extent in the custom-publishing vertical, despite the huge reliance of search vendors on text mining technologies. They aren&#8217;t getting traction in the archiving/compliance area. There don&#8217;t seem to be [...]</description>
		<content:encoded><![CDATA[<p>[...] active in text search, except to some extent in the custom-publishing vertical, despite the huge reliance of search vendors on text mining technologies. They aren&#8217;t getting traction in the archiving/compliance area. There don&#8217;t seem to be [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paolo Cavone</title>
		<link>http://www.texttechnologies.com/2006/11/11/text-mining-and-search-joined-at-the-hip/#comment-5689</link>
		<dc:creator>Paolo Cavone</dc:creator>
		<pubDate>Fri, 16 Mar 2007 16:10:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/2006/11/11/text-mining-and-search-joined-at-the-hip/#comment-5689</guid>
		<description>I&#039;m agree with Patrick. Text mining should (or must!) in effect *learn* (and store semantic structures)

[quote]
...Yes search engines like Google already return both documents and extracted elements from them. But these search engines don’t appear to have semantics built into them.
[/quote]

until the semantic structures are (too much) detected from the anchors of the backlink...</description>
		<content:encoded><![CDATA[<p>I&#8217;m agree with Patrick. Text mining should (or must!) in effect *learn* (and store semantic structures)</p>
<p>[quote]<br />
&#8230;Yes search engines like Google already return both documents and extracted elements from them. But these search engines don’t appear to have semantics built into them.<br />
[/quote]</p>
<p>until the semantic structures are (too much) detected from the anchors of the backlink&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Herron</title>
		<link>http://www.texttechnologies.com/2006/11/11/text-mining-and-search-joined-at-the-hip/#comment-2166</link>
		<dc:creator>Patrick Herron</dc:creator>
		<pubDate>Sat, 11 Nov 2006 19:52:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/2006/11/11/text-mining-and-search-joined-at-the-hip/#comment-2166</guid>
		<description>You got me, that&#039;s for sure.

I understand that search and text mining are related and overlap.  Part of what&#039;s commonly called text mining--information extraction (IE)--powers some advanced features of search engines.  Sure enough.  But search engines take keywordese input, do some sort of finding operation, and return relevant documents.  That&#039;s the purpose of information retrieval.  The most promising, interesting, and innovative applications of text mining are not information extraction engines but rather systems that do operations and return results not at the document level nor even at the extraction level but rather at the level of synthesis.  Such applications take extracted elements and put them together in order to generate new information.  They use inductive logic or some set of domain rules (taxonomic rules, if you like) to create information that did not previously exist.  That&#039;s not information-finding/search but information-generating.   Some positive examples include Arrowsmith, the Robot Scientist, BioPubMiner, and pieces of Etzioni&#039;s Machine Reading (MR) research.  While many of technologies that power search are present in good text mining applications, text mining applications should do a whole lot more.  I mean, look at how token-driven Google is.   Search regurgitates.  Text mining should in effect *learn*.

Numerous credible sources consider IE applications to be text mining, or more oxymoronically, &quot;knowledge discovery.&quot;  Heart&#039;s widely-read essays, or Weiss et al.&#039;s definitive text mining text, place IE under the text mining umbrella.  But IE is really just search taken one more step, from returning documents to returning document elements.  Yes search engines like Google already return both documents and extracted elements from them.  But these search engines don&#039;t appear to have semantics built into them.

If anything, the relationship started very tightly and has separated over the years.  Text mining will likely change names, as it already appears to be doing, thus making the process of separation somewhat more difficult to interpret.</description>
		<content:encoded><![CDATA[<p>You got me, that&#8217;s for sure.</p>
<p>I understand that search and text mining are related and overlap.  Part of what&#8217;s commonly called text mining&#8211;information extraction (IE)&#8211;powers some advanced features of search engines.  Sure enough.  But search engines take keywordese input, do some sort of finding operation, and return relevant documents.  That&#8217;s the purpose of information retrieval.  The most promising, interesting, and innovative applications of text mining are not information extraction engines but rather systems that do operations and return results not at the document level nor even at the extraction level but rather at the level of synthesis.  Such applications take extracted elements and put them together in order to generate new information.  They use inductive logic or some set of domain rules (taxonomic rules, if you like) to create information that did not previously exist.  That&#8217;s not information-finding/search but information-generating.   Some positive examples include Arrowsmith, the Robot Scientist, BioPubMiner, and pieces of Etzioni&#8217;s Machine Reading (MR) research.  While many of technologies that power search are present in good text mining applications, text mining applications should do a whole lot more.  I mean, look at how token-driven Google is.   Search regurgitates.  Text mining should in effect *learn*.</p>
<p>Numerous credible sources consider IE applications to be text mining, or more oxymoronically, &#8220;knowledge discovery.&#8221;  Heart&#8217;s widely-read essays, or Weiss et al.&#8217;s definitive text mining text, place IE under the text mining umbrella.  But IE is really just search taken one more step, from returning documents to returning document elements.  Yes search engines like Google already return both documents and extracted elements from them.  But these search engines don&#8217;t appear to have semantics built into them.</p>
<p>If anything, the relationship started very tightly and has separated over the years.  Text mining will likely change names, as it already appears to be doing, thus making the process of separation somewhat more difficult to interpret.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

