<?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: A Voice in Favor of Ambiguity?</title>
	<atom:link href="http://www.adamsdrafting.com/2010/01/22/a-voice-in-favor-of-ambiguity-question-mark/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamsdrafting.com/2010/01/22/a-voice-in-favor-of-ambiguity-question-mark/</link>
	<description></description>
	<lastBuildDate>Tue, 31 Jan 2012 01:23:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2010/01/22/a-voice-in-favor-of-ambiguity-question-mark/comment-page-1/#comment-94726</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Tue, 26 Jan 2010 14:15:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/?p=2127#comment-94726</guid>
		<description>Gil: Thanks; this is a great example of an instance where in not addressing an issue the parties may have bungled the cost-benefit analysis. Ken</description>
		<content:encoded><![CDATA[<p>Gil: Thanks; this is a great example of an instance where in not addressing an issue the parties may have bungled the cost-benefit analysis. Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gil</title>
		<link>http://www.adamsdrafting.com/2010/01/22/a-voice-in-favor-of-ambiguity-question-mark/comment-page-1/#comment-94725</link>
		<dc:creator>Gil</dc:creator>
		<pubDate>Tue, 26 Jan 2010 11:35:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/?p=2127#comment-94725</guid>
		<description>Ken, your comment about parties &#039;creating a void that the parties can fill with their competing interpretations&#039; reminds me of Apple Corps Ltd. v Apple Computer Inc. which was heard in the High Court of England in February 2004.

This was a Trademark dispute in which the court had to decide both the jurisdiction and the governing law in circumstances where the parties had not provided expressly for these - due to their inability to agree. Therefore, the parties conducted elaborate steps to execute the contract (allegedly) so that it could not be said that it was made in one jurisdiction before it was made in the other.

As the judge said: &#039;If their intention in doing so was to create obscurity and difficulty for lawyers to debate in future years, they have succeeded handsomely.&#039;

In the end the judge conducted a balancing exercise and narrowly decided that the appropriate jurisdiction and governing law were England. However, the reasoning is a joy to read.

http://www.hmcourts-service.gov.uk/judgmentsfiles/j2468/apple-v-apple.htm</description>
		<content:encoded><![CDATA[<p>Ken, your comment about parties &#8216;creating a void that the parties can fill with their competing interpretations&#8217; reminds me of Apple Corps Ltd. v Apple Computer Inc. which was heard in the High Court of England in February 2004.</p>
<p>This was a Trademark dispute in which the court had to decide both the jurisdiction and the governing law in circumstances where the parties had not provided expressly for these &#8211; due to their inability to agree. Therefore, the parties conducted elaborate steps to execute the contract (allegedly) so that it could not be said that it was made in one jurisdiction before it was made in the other.</p>
<p>As the judge said: &#8216;If their intention in doing so was to create obscurity and difficulty for lawyers to debate in future years, they have succeeded handsomely.&#8217;</p>
<p>In the end the judge conducted a balancing exercise and narrowly decided that the appropriate jurisdiction and governing law were England. However, the reasoning is a joy to read.</p>
<p><a href="http://www.hmcourts-service.gov.uk/judgmentsfiles/j2468/apple-v-apple.htm" rel="nofollow">http://www.hmcourts-service.gov.uk/judgmentsfiles/j2468/apple-v-apple.htm</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Anderson</title>
		<link>http://www.adamsdrafting.com/2010/01/22/a-voice-in-favor-of-ambiguity-question-mark/comment-page-1/#comment-94705</link>
		<dc:creator>Mark Anderson</dc:creator>
		<pubDate>Sat, 23 Jan 2010 20:40:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/?p=2127#comment-94705</guid>
		<description>Ken, as you say, choosing not to address an issue is not the same as ambiguity in a term that is included in the contract.

My sense is that &quot;constructive ambiguity&quot; arises where parties find it difficult to agree on the wording of a clause/section.  One or both parties allows imperfect wording to be included, hoping that any ambiguity: (a) gives them a plausible argument, and therefore a bargaining position, in negotiations if the issue becomes important, and/or (b) will be decided in their favour by the Court.

As legal advisers to a commercial client, we should focus on (b).  The contra proferentem rule (which seems to have developed in subtly different ways in the US and the UK) points towards advising clients against relying on (b), and instead making the wording clear and unambiguous, even if this requires more negotiating effort.</description>
		<content:encoded><![CDATA[<p>Ken, as you say, choosing not to address an issue is not the same as ambiguity in a term that is included in the contract.</p>
<p>My sense is that &#8220;constructive ambiguity&#8221; arises where parties find it difficult to agree on the wording of a clause/section.  One or both parties allows imperfect wording to be included, hoping that any ambiguity: (a) gives them a plausible argument, and therefore a bargaining position, in negotiations if the issue becomes important, and/or (b) will be decided in their favour by the Court.</p>
<p>As legal advisers to a commercial client, we should focus on (b).  The contra proferentem rule (which seems to have developed in subtly different ways in the US and the UK) points towards advising clients against relying on (b), and instead making the wording clear and unambiguous, even if this requires more negotiating effort.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2010/01/22/a-voice-in-favor-of-ambiguity-question-mark/comment-page-1/#comment-94704</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Sat, 23 Jan 2010 02:28:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/?p=2127#comment-94704</guid>
		<description>Mike: My default mode is to address in a contract all signficant issues that might arise. I leave to those who actually do deals the question of whether in a given context leaving an issue to one side is a valid approach.

But as a general matter, I could imagine a situation where the parties decide that skirting an issue is the best approach, given (1) the high transaction costs involved in negotiating that issue and (2) the fact that the issue is unlikely to arise.

Ken</description>
		<content:encoded><![CDATA[<p>Mike: My default mode is to address in a contract all signficant issues that might arise. I leave to those who actually do deals the question of whether in a given context leaving an issue to one side is a valid approach.</p>
<p>But as a general matter, I could imagine a situation where the parties decide that skirting an issue is the best approach, given (1) the high transaction costs involved in negotiating that issue and (2) the fact that the issue is unlikely to arise.</p>
<p>Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.adamsdrafting.com/2010/01/22/a-voice-in-favor-of-ambiguity-question-mark/comment-page-1/#comment-94703</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Fri, 22 Jan 2010 18:08:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/?p=2127#comment-94703</guid>
		<description>One of the things that bothers me about these strategic drafting considerations is that it assumes someone later will be able to discern your intent from the four corners of the document or, for that matter, that you remember why you chose x and y word to preserve an argument.

Moreover, if it is an issue about which strategic drafting is worthwhile, then it&#039;s very likely the other side can see your game, if not play right along with you. As I see it there are a few applicable scenarios that make strategic drafting an option rather than specifically adding it to the contract, none of which favor strategic drafting:
1. You asked, but were rejected
2. The parties cannot agree and remaining silent is an option
3. You think that asking directly will doom the agreement

In each case, there is a &quot;bonus&quot; to your side if you can sneak the idea into the contract in some other manner to fight about it later.  In cases 1 and 2, the party is already on to you so they are likely planning the same game. In the case of 3, you have to somehow add (or omit) some clause without tackling the issue directly such that a judge/jury will understand that the parties intended there to be this unwritten (or not expressly stated) something. It could happen, but is that really a effective?

And leaving notes in a file is not likely to help your side at litigation since a judge/jury will see your strategic preservation of an argument as not good faith (if not fully bad faith).

I think that the Conan example is illustrative. The post hoc analysis reads into the absence of a time as strategic drafting. But that&#039;s pure speculation. It&#039;s almost as likely that no one considered that they&#039;d move the time of the Tonight Show--it had been in relatively the same time slot since at least Johnny Carson. It seems to me that Conan&#039;s position would be greatly strengthened if he could say, &quot;uh no, you can&#039;t move my time slot because you&#039;d breach section 9.12(B)(i)(2). Now give me $300M.&quot; And, if they had asked during negotiation, Conan would know, going into the contract, that there&#039;s a good chance that they&#039;d bounce him to a later time slot (again) if they chose and he should ask for some more $ or other guarantees.

I&#039;m dubious.</description>
		<content:encoded><![CDATA[<p>One of the things that bothers me about these strategic drafting considerations is that it assumes someone later will be able to discern your intent from the four corners of the document or, for that matter, that you remember why you chose x and y word to preserve an argument.</p>
<p>Moreover, if it is an issue about which strategic drafting is worthwhile, then it&#8217;s very likely the other side can see your game, if not play right along with you. As I see it there are a few applicable scenarios that make strategic drafting an option rather than specifically adding it to the contract, none of which favor strategic drafting:<br />
1. You asked, but were rejected<br />
2. The parties cannot agree and remaining silent is an option<br />
3. You think that asking directly will doom the agreement</p>
<p>In each case, there is a &#8220;bonus&#8221; to your side if you can sneak the idea into the contract in some other manner to fight about it later.  In cases 1 and 2, the party is already on to you so they are likely planning the same game. In the case of 3, you have to somehow add (or omit) some clause without tackling the issue directly such that a judge/jury will understand that the parties intended there to be this unwritten (or not expressly stated) something. It could happen, but is that really a effective?</p>
<p>And leaving notes in a file is not likely to help your side at litigation since a judge/jury will see your strategic preservation of an argument as not good faith (if not fully bad faith).</p>
<p>I think that the Conan example is illustrative. The post hoc analysis reads into the absence of a time as strategic drafting. But that&#8217;s pure speculation. It&#8217;s almost as likely that no one considered that they&#8217;d move the time of the Tonight Show&#8211;it had been in relatively the same time slot since at least Johnny Carson. It seems to me that Conan&#8217;s position would be greatly strengthened if he could say, &#8220;uh no, you can&#8217;t move my time slot because you&#8217;d breach section 9.12(B)(i)(2). Now give me $300M.&#8221; And, if they had asked during negotiation, Conan would know, going into the contract, that there&#8217;s a good chance that they&#8217;d bounce him to a later time slot (again) if they chose and he should ask for some more $ or other guarantees.</p>
<p>I&#8217;m dubious.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

