<?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"
	>
<channel>
	<title>Comments on: Autonomy on text mining</title>
	<atom:link href="http://www.texttechnologies.com/2006/07/23/autonomy-on-text-mining/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.texttechnologies.com/2006/07/23/autonomy-on-text-mining/</link>
	<description>Understanding technology ... in both senses of the phrase</description>
	<pubDate>Fri, 04 Jul 2008 05:36:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Text Technologies&#187;Blog Archive &#187; Application processes in text mining – finding warning signs</title>
		<link>http://www.texttechnologies.com/2006/07/23/autonomy-on-text-mining/#comment-1657</link>
		<dc:creator>Text Technologies&#187;Blog Archive &#187; Application processes in text mining – finding warning signs</dc:creator>
		<pubDate>Thu, 27 Jul 2006 09:37:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/2006/07/23/autonomy-on-text-mining/#comment-1657</guid>
		<description>[...] 3. In other cases, one is looking for trouble even before one has found some. Compliance often falls into this category, as does web-crawling reputation management. One process, favored by Autonomy, is simply to monitor document flow for all important themes, and hope that the trouble signs jump out at you. Alternatively, one can monitor documents for known bad event flags – vehicle malfunctions, drug side effects, angry customers, whatever. If there are only a few documents with such flags, one can read them directly If there are too many for humans to just read and digest in a timely manner – well, then you’ve transitioned into Case 1 or Case 2!      &#8226; &#8226; &#8226; [...]</description>
		<content:encoded><![CDATA[<p>[...] 3. In other cases, one is looking for trouble even before one has found some. Compliance often falls into this category, as does web-crawling reputation management. One process, favored by Autonomy, is simply to monitor document flow for all important themes, and hope that the trouble signs jump out at you. Alternatively, one can monitor documents for known bad event flags – vehicle malfunctions, drug side effects, angry customers, whatever. If there are only a few documents with such flags, one can read them directly If there are too many for humans to just read and digest in a timely manner – well, then you’ve transitioned into Case 1 or Case 2!      &#8226; &#8226; &#8226; [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.136 seconds -->
