<?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: ZANTAZ Announces Desktop Legal Hold Solution and Takes on Guidance</title>
	<atom:link href="http://www.clearwellsystems.com/e-discovery-blog/2007/12/05/zantaz-announces-desktop-legal-hold-solution-and-takes-on-guidance/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.clearwellsystems.com/e-discovery-blog/2007/12/05/zantaz-announces-desktop-legal-hold-solution-and-takes-on-guidance/</link>
	<description>thoughts about the evolution of e-discovery</description>
	<pubDate>Sat, 22 Nov 2008 08:55:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Anonymous</title>
		<link>http://www.clearwellsystems.com/e-discovery-blog/2007/12/05/zantaz-announces-desktop-legal-hold-solution-and-takes-on-guidance/#comment-31</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 19 Dec 2007 14:15:00 +0000</pubDate>
		<guid isPermaLink="false">http://staging.clearwellsystems.com/wordpress/?p=34#comment-31</guid>
		<description>An interesting announcement but to me it seems shortsighted. Forensics professionals are a hard won group. AutonoZantaz/Zantonomy will have a hard replacing this group's proven and preferred tools for active content collection. Archrival Symantec has taken the opposite approach with a more open strategy by integrating collections from Guidance EnCase and Kazeon into their archive.</description>
		<content:encoded><![CDATA[<p>An interesting announcement but to me it seems shortsighted. Forensics professionals are a hard won group. AutonoZantaz/Zantonomy will have a hard replacing this group&#8217;s proven and preferred tools for active content collection. Archrival Symantec has taken the opposite approach with a more open strategy by integrating collections from Guidance EnCase and Kazeon into their archive.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
