<?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: 7th Circuit Launches an Electronic Discovery Pilot Program</title>
	<atom:link href="http://www.clearwellsystems.com/e-discovery-blog/2009/10/15/7th-circuit-launches-an-electronic-discovery-pilot-program/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.clearwellsystems.com/e-discovery-blog/2009/10/15/7th-circuit-launches-an-electronic-discovery-pilot-program/</link>
	<description>thoughts about the evolution of e-discovery</description>
	<lastBuildDate>Sat, 28 Jan 2012 05:21:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: 7th Circuit Electronic Discovery Pilot Program and the Principles on ESI &#124; e-discovery 2.0</title>
		<link>http://www.clearwellsystems.com/e-discovery-blog/2009/10/15/7th-circuit-launches-an-electronic-discovery-pilot-program/comment-page-1/#comment-2641</link>
		<dc:creator>7th Circuit Electronic Discovery Pilot Program and the Principles on ESI &#124; e-discovery 2.0</dc:creator>
		<pubDate>Thu, 25 Aug 2011 15:34:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.clearwellsystems.com/e-discovery-blog/?p=688#comment-2641</guid>
		<description>[...] deal with the many vexing eDiscovery challenges in the courtroom. By way of background, the 7th Circuit Electronic Discovery Pilot Program Committee was formed in May 2009 and was chartered to conduct a multi-year, multi-phase project to [...]</description>
		<content:encoded><![CDATA[<p>[...] deal with the many vexing eDiscovery challenges in the courtroom. By way of background, the 7th Circuit Electronic Discovery Pilot Program Committee was formed in May 2009 and was chartered to conduct a multi-year, multi-phase project to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clearwell and Ediscovery Pilot Program &#124; Ediscovery Trends</title>
		<link>http://www.clearwellsystems.com/e-discovery-blog/2009/10/15/7th-circuit-launches-an-electronic-discovery-pilot-program/comment-page-1/#comment-1719</link>
		<dc:creator>Clearwell and Ediscovery Pilot Program &#124; Ediscovery Trends</dc:creator>
		<pubDate>Tue, 20 Oct 2009 23:45:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.clearwellsystems.com/e-discovery-blog/?p=688#comment-1719</guid>
		<description>[...] just reading the Clearwell Ediscovery blog and have to agree that the most significant rule of the new ediscovery pilot plan is one that creates an ediscovery liaison.  This pilot program is only being tested in the Seventh [...]</description>
		<content:encoded><![CDATA[<p>[...] just reading the Clearwell Ediscovery blog and have to agree that the most significant rule of the new ediscovery pilot plan is one that creates an ediscovery liaison.  This pilot program is only being tested in the Seventh [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: e-discovery 2.0 » Blog Archive » Electronic Discovery, EDiscovery &#8230; &#124; Newarticletoday.com Blog</title>
		<link>http://www.clearwellsystems.com/e-discovery-blog/2009/10/15/7th-circuit-launches-an-electronic-discovery-pilot-program/comment-page-1/#comment-1717</link>
		<dc:creator>e-discovery 2.0 » Blog Archive » Electronic Discovery, EDiscovery &#8230; &#124; Newarticletoday.com Blog</dc:creator>
		<pubDate>Fri, 16 Oct 2009 00:48:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.clearwellsystems.com/e-discovery-blog/?p=688#comment-1717</guid>
		<description>[...] the rest here: e-discovery 2.0 » Blog Archive » Electronic Discovery, EDiscovery &#8230;   Share and [...]</description>
		<content:encoded><![CDATA[<p>[...] the rest here: e-discovery 2.0 » Blog Archive » Electronic Discovery, EDiscovery &#8230;   Share and [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

