<?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: The Biggest Unanswered Questions in Electronic Discovery</title> <atom:link href="http://denniskennedy.com/blog/2007/01/the-biggest-unanswered-questions-in-electronic-discovery/feed/" rel="self" type="application/rss+xml" /><link>http://denniskennedy.com/blog/2007/01/the-biggest-unanswered-questions-in-electronic-discovery/</link> <description>Legal technology, technology law and other musings.</description> <lastBuildDate>Tue, 19 Feb 2013 04:08:56 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.5.1</generator> <item><title>By: Jeff Carr</title><link>http://denniskennedy.com/blog/2007/01/the-biggest-unanswered-questions-in-electronic-discovery/comment-page-1/#comment-181</link> <dc:creator>Jeff Carr</dc:creator> <pubDate>Wed, 07 Feb 2007 14:22:11 +0000</pubDate> <guid
isPermaLink="false">http://denniskennedy_com.innosoftware.net/?p=1191#comment-181</guid> <description><![CDATA[Dennis -- it strikes me that from the corporate perspective, the biggest ediscovery question has nothing to do with ediscovery but rather with digital domain management.  Ediscovery poses the same 6 questions relevant to any data -- what to keep, why, where, how long, how do you find it, and how do you deliver it.  Whether answering a ediscovery request (find and deliver), or limiting data exposure through the safe harbor provions (why and how long), finding the 12 contracts with the same customer throughout the company (what, where, why, deliver), the issues all do to domain architecture and search tools.  I&#039;m quite frankly tired of the endless ediscovery vendor calls and conferences about the &quot;y2k&quot;, &quot;SOX,&quot; or &quot;CD&amp;A&quot; issue of 2006-07.  I&#039;m looking much deeper that ediscovery but rather into enterprise-wide digital domain management tools.  The learning corporation leverages it&#039;s digital domain for many purposes -- only one of which is litigation.  Remember, unless the company is a lawfirm or a patent troll, it&#039;s buseiness is making and selling stuff or providing services -- it&#039;s not to win cases, answer interesting questions of law, or be great at e-discovery.  Indeed, a truly high performance company wouldn&#039;t have much of an e-discovery issue becuase it would use many tools to avoid litigation in the first place.
]]></description> <content:encoded><![CDATA[<p>Dennis &#8212; it strikes me that from the corporate perspective, the biggest ediscovery question has nothing to do with ediscovery but rather with digital domain management.  Ediscovery poses the same 6 questions relevant to any data &#8212; what to keep, why, where, how long, how do you find it, and how do you deliver it.  Whether answering a ediscovery request (find and deliver), or limiting data exposure through the safe harbor provions (why and how long), finding the 12 contracts with the same customer throughout the company (what, where, why, deliver), the issues all do to domain architecture and search tools.  I&#8217;m quite frankly tired of the endless ediscovery vendor calls and conferences about the &#8220;y2k&#8221;, &#8220;SOX,&#8221; or &#8220;CD&#038;A&#8221; issue of 2006-07.  I&#8217;m looking much deeper that ediscovery but rather into enterprise-wide digital domain management tools.  The learning corporation leverages it&#8217;s digital domain for many purposes &#8212; only one of which is litigation.  Remember, unless the company is a lawfirm or a patent troll, it&#8217;s buseiness is making and selling stuff or providing services &#8212; it&#8217;s not to win cases, answer interesting questions of law, or be great at e-discovery.  Indeed, a truly high performance company wouldn&#8217;t have much of an e-discovery issue becuase it would use many tools to avoid litigation in the first place.</p> ]]></content:encoded> </item> </channel> </rss>