<?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: More on Needless Elaboration</title>
	<atom:link href="http://www.adamsdrafting.com/2007/08/06/more-on-needless-elaboration/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamsdrafting.com/2007/08/06/more-on-needless-elaboration/</link>
	<description></description>
	<lastBuildDate>Fri, 19 Mar 2010 12:50:33 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: D. C.</title>
		<link>http://www.adamsdrafting.com/2007/08/06/more-on-needless-elaboration/comment-page-1/#comment-19805</link>
		<dc:creator>D. C.</dc:creator>
		<pubDate>Mon, 26 Nov 2007 14:21:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/08/06/more-on-needless-elaboration/#comment-19805</guid>
		<description>The conventional wisdom, of course, is that most such elaborations arose to try to block &quot;creative&quot; lawyering, usually on the part of litigation counsel. At some point lost in the mists of time, a contract said (let&#039;s say) &quot;neither party is allowed to eat fish.&quot;   But then later some litigator noticed that the parties&#039; business together involved salt-water fish only. So he tried to argue that the parties never contemplated being prohibited from eating &lt;em&gt;fresh&lt;/em&gt;-water fish. 

Litigators are &lt;em&gt;always&lt;/em&gt; going to look for possible arguments like that. Their thinking goes something like this (I speak as a former litigator): There&#039;s no cost to me or my client if I make this argument. If the judge buys it, my client is ahead of the game. So hell yes, I&#039;m going to take the shot; in fact, I&#039;m ethically compelled to do so.

As a drafter, the trick is to try to think like a litigator, and like a judge, to assess where elaboration language is needed to cover a genuine risk of &quot;creative&quot; lawyer, and where it&#039;s a waste of pixels and toner.</description>
		<content:encoded><![CDATA[<p>The conventional wisdom, of course, is that most such elaborations arose to try to block &#8220;creative&#8221; lawyering, usually on the part of litigation counsel. At some point lost in the mists of time, a contract said (let&#8217;s say) &#8220;neither party is allowed to eat fish.&#8221;   But then later some litigator noticed that the parties&#8217; business together involved salt-water fish only. So he tried to argue that the parties never contemplated being prohibited from eating <em>fresh</em>-water fish. </p>
<p>Litigators are <em>always</em> going to look for possible arguments like that. Their thinking goes something like this (I speak as a former litigator): There&#8217;s no cost to me or my client if I make this argument. If the judge buys it, my client is ahead of the game. So hell yes, I&#8217;m going to take the shot; in fact, I&#8217;m ethically compelled to do so.</p>
<p>As a drafter, the trick is to try to think like a litigator, and like a judge, to assess where elaboration language is needed to cover a genuine risk of &#8220;creative&#8221; lawyer, and where it&#8217;s a waste of pixels and toner.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
