<?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 Benefits of Sloppy Drafting?</title>
	<atom:link href="http://www.adamsdrafting.com/2007/12/12/sloppy-drafting/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamsdrafting.com/2007/12/12/sloppy-drafting/</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/2007/12/12/sloppy-drafting/comment-page-1/#comment-24115</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Tue, 18 Dec 2007 16:56:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/12/12/sloppy-drafting/#comment-24115</guid>
		<description>Stan, Fitz: I can understand the parties to a contract wanting to skirt a contentious issue, leaving it to the courts to handle should it ever becomes a source of contention.

But I think it unlikely that they&#039;d choose to accomplish that by including an ambiguity, namely a word or phrase to which one can attribute two or more meanings. That would be going out of your way to ask for trouble. (One party&#039;s sneaking ambiguity into a contract in order to be able to be able to invoke thereafter an alternative meaning is a different matter entirely, one that I discuss in &lt;a href=&quot;http://www.adamsdrafting.com/2007/10/29/gamesmanship-in-contract-drafting/&quot; rel=&quot;nofollow&quot;&gt;this blog post&lt;/a&gt;.)

It&#039;s more likely that they&#039;d accomplish that goal by being vague. (Vagueness is a function of imprecision.) Don&#039;t get me started on exactly what vagueness is—it&#039;s a question I&#039;ve been debating with a linguist. But the best-known vehicles of vagueness are words like &lt;em&gt;promptly&lt;/em&gt; and &lt;em&gt;material&lt;/em&gt;.

And vagueness certainly isn&#039;t sloppy. It&#039;s a legitimate drafting tool that has no bearing on the sort of incoherence and redundancy that Mark Salmon alluded to in his post.

Ken</description>
		<content:encoded><![CDATA[<p>Stan, Fitz: I can understand the parties to a contract wanting to skirt a contentious issue, leaving it to the courts to handle should it ever becomes a source of contention.</p>
<p>But I think it unlikely that they&#8217;d choose to accomplish that by including an ambiguity, namely a word or phrase to which one can attribute two or more meanings. That would be going out of your way to ask for trouble. (One party&#8217;s sneaking ambiguity into a contract in order to be able to be able to invoke thereafter an alternative meaning is a different matter entirely, one that I discuss in <a href="http://www.adamsdrafting.com/2007/10/29/gamesmanship-in-contract-drafting/" rel="nofollow">this blog post</a>.)</p>
<p>It&#8217;s more likely that they&#8217;d accomplish that goal by being vague. (Vagueness is a function of imprecision.) Don&#8217;t get me started on exactly what vagueness is—it&#8217;s a question I&#8217;ve been debating with a linguist. But the best-known vehicles of vagueness are words like <em>promptly</em> and <em>material</em>.</p>
<p>And vagueness certainly isn&#8217;t sloppy. It&#8217;s a legitimate drafting tool that has no bearing on the sort of incoherence and redundancy that Mark Salmon alluded to in his post.</p>
<p>Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: john fitz</title>
		<link>http://www.adamsdrafting.com/2007/12/12/sloppy-drafting/comment-page-1/#comment-24104</link>
		<dc:creator>john fitz</dc:creator>
		<pubDate>Tue, 18 Dec 2007 16:24:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/12/12/sloppy-drafting/#comment-24104</guid>
		<description>Stan is on to something... One man&#039;s &quot;sloppy&quot; is another&#039;s intentional ambiguity. I learned from a very seasoned litigator-turned-transactional attorney, who repeatedly told me that &quot;if a phrase is capable of more than one meaning, you must be certain that you intend this result - because in litigation all possible interpretations will be exposed&quot;.</description>
		<content:encoded><![CDATA[<p>Stan is on to something&#8230; One man&#8217;s &#8220;sloppy&#8221; is another&#8217;s intentional ambiguity. I learned from a very seasoned litigator-turned-transactional attorney, who repeatedly told me that &#8220;if a phrase is capable of more than one meaning, you must be certain that you intend this result &#8211; because in litigation all possible interpretations will be exposed&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stan</title>
		<link>http://www.adamsdrafting.com/2007/12/12/sloppy-drafting/comment-page-1/#comment-24075</link>
		<dc:creator>Stan</dc:creator>
		<pubDate>Tue, 18 Dec 2007 15:08:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/12/12/sloppy-drafting/#comment-24075</guid>
		<description>&quot;Sloppy drafting&quot; may also reflect &quot;intentional ambiguity&quot;.  Often, the parties to an agreement may settle on wording that is ambiguous or vague in order to conclude the matter, hoping (or trusting) that the sloppiness (i.e. ambiguity)will never have to be dealt with.  I would like to hear your musings on this.</description>
		<content:encoded><![CDATA[<p>&#8220;Sloppy drafting&#8221; may also reflect &#8220;intentional ambiguity&#8221;.  Often, the parties to an agreement may settle on wording that is ambiguous or vague in order to conclude the matter, hoping (or trusting) that the sloppiness (i.e. ambiguity)will never have to be dealt with.  I would like to hear your musings on this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2007/12/12/sloppy-drafting/comment-page-1/#comment-24067</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Tue, 18 Dec 2007 14:27:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/12/12/sloppy-drafting/#comment-24067</guid>
		<description>Anon.: Good point! I was a little too glib. Ken</description>
		<content:encoded><![CDATA[<p>Anon.: Good point! I was a little too glib. Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anon.</title>
		<link>http://www.adamsdrafting.com/2007/12/12/sloppy-drafting/comment-page-1/#comment-24065</link>
		<dc:creator>Anon.</dc:creator>
		<pubDate>Tue, 18 Dec 2007 14:24:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/12/12/sloppy-drafting/#comment-24065</guid>
		<description>&quot;[A] simpler explanation for sloppy drafting is sloppy drafters.&quot;

Additionally, sloppy drafting is often the result of a sloppy drafting process(which is something frequently discussed on this blog).</description>
		<content:encoded><![CDATA[<p>&#8220;[A] simpler explanation for sloppy drafting is sloppy drafters.&#8221;</p>
<p>Additionally, sloppy drafting is often the result of a sloppy drafting process(which is something frequently discussed on this blog).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

