<?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: Costly Drafting Errors, Part 1—Rogers Communications and Aliant</title>
	<atom:link href="http://www.adamsdrafting.com/2006/08/07/costly-drafting-errors-part-1/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamsdrafting.com/2006/08/07/costly-drafting-errors-part-1/</link>
	<description></description>
	<lastBuildDate>Mon, 15 Mar 2010 01:58:43 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Art</title>
		<link>http://www.adamsdrafting.com/2006/08/07/costly-drafting-errors-part-1/comment-page-1/#comment-70238</link>
		<dc:creator>Art</dc:creator>
		<pubDate>Tue, 11 Nov 2008 12:01:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/08/07/costly-drafting-errors-part-1/#comment-70238</guid>
		<description>An old post, but worth a comment.

I don&#039;t think anyone has yet mentioned yet that the drafter has not correctly described the conceptual operation of the set terms (though Ken fixes the problem in his 2 sentence version).

Here, the contract terminates by itself if it is not extended (albeit it extends automatically). The notice is therefore more accurately described as a notice of non-extension than a notice of termination. Had the drafter used non-extension terminology rather than termination terminology, the regulators could never have interpreted the clause as they did, wherever the commas were.

So I see this as more of an issue of precise description than an issue of syntax.</description>
		<content:encoded><![CDATA[<p>An old post, but worth a comment.</p>
<p>I don&#8217;t think anyone has yet mentioned yet that the drafter has not correctly described the conceptual operation of the set terms (though Ken fixes the problem in his 2 sentence version).</p>
<p>Here, the contract terminates by itself if it is not extended (albeit it extends automatically). The notice is therefore more accurately described as a notice of non-extension than a notice of termination. Had the drafter used non-extension terminology rather than termination terminology, the regulators could never have interpreted the clause as they did, wherever the commas were.</p>
<p>So I see this as more of an issue of precise description than an issue of syntax.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Set in Style &#8212; Blog Archive &#187; Polishing Before Publishing</title>
		<link>http://www.adamsdrafting.com/2006/08/07/costly-drafting-errors-part-1/comment-page-1/#comment-26112</link>
		<dc:creator>Set in Style &#8212; Blog Archive &#187; Polishing Before Publishing</dc:creator>
		<pubDate>Wed, 26 Dec 2007 19:24:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/08/07/costly-drafting-errors-part-1/#comment-26112</guid>
		<description>[...] changes they are, but important. An erroneous comma can be very costly, and prospective clients might (should) be leary leery of attorneys that who don&#8217;t review [...]</description>
		<content:encoded><![CDATA[<p>[...] changes they are, but important. An erroneous comma can be very costly, and prospective clients might (should) be leary leery of attorneys that who don&#8217;t review [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2006/08/07/costly-drafting-errors-part-1/comment-page-1/#comment-760</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Fri, 22 Sep 2006 17:34:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/08/07/costly-drafting-errors-part-1/#comment-760</guid>
		<description>G.: Your view is that of the Canadian Radio-television and Telecommunications Commission. I happen to disagree. In due course I&#039;ll explain why. Ken</description>
		<content:encoded><![CDATA[<p>G.: Your view is that of the Canadian Radio-television and Telecommunications Commission. I happen to disagree. In due course I&#8217;ll explain why. Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: G. Northland</title>
		<link>http://www.adamsdrafting.com/2006/08/07/costly-drafting-errors-part-1/comment-page-1/#comment-759</link>
		<dc:creator>G. Northland</dc:creator>
		<pubDate>Fri, 22 Sep 2006 17:05:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/08/07/costly-drafting-errors-part-1/#comment-759</guid>
		<description>The original sentence is not flawed, though it is not as clear as we might wish.

The real issue is much simpler: if the second comma had been omitted, the final prepositional phrase would apply to only &quot;and thereafter for successive five (5) year terms&quot;; but with the comma, the final prepositional phrase applies to the whole sentence, allowing Aliant to give notice at any time.

With or without the second comma, the grammar is correct; but the meanings are very different.

The final prepositional phrase should have been written in a sentence of its own, with the author&#039;s intention made much clearer.</description>
		<content:encoded><![CDATA[<p>The original sentence is not flawed, though it is not as clear as we might wish.</p>
<p>The real issue is much simpler: if the second comma had been omitted, the final prepositional phrase would apply to only &#8220;and thereafter for successive five (5) year terms&#8221;; but with the comma, the final prepositional phrase applies to the whole sentence, allowing Aliant to give notice at any time.</p>
<p>With or without the second comma, the grammar is correct; but the meanings are very different.</p>
<p>The final prepositional phrase should have been written in a sentence of its own, with the author&#8217;s intention made much clearer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ray Kovarik</title>
		<link>http://www.adamsdrafting.com/2006/08/07/costly-drafting-errors-part-1/comment-page-1/#comment-667</link>
		<dc:creator>Ray Kovarik</dc:creator>
		<pubDate>Mon, 18 Sep 2006 18:21:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/08/07/costly-drafting-errors-part-1/#comment-667</guid>
		<description>Ken:  I look forward to your follow-up.  What we need to realize (and what I should have mentioned first but did not in the interests of space) is that my analysis was done on the principle of providing the best possible explanation as to the meaning of a sentence that it is in fact grammatically flawed.  Much like with run-on sentences or sentence fragments, they may be gramatically incorrect, but you can still derive meaning from them.  They do, however, present the problem that you can misinterpret them (or &quot;mis-analyze&quot; them).  The analysis I did, in fact, takes a flawed sentence and parses it in such a manner that it elucidates the most likely meaning intended by the authors.  I did not accept your analysis as it tries to fit formal rules to a sentence that is flawed in the first place.  Your response to my analysis would have to reconcile your formal approach (which works perfectly well with grammatically correct sentences) with the flawed nature of the sentence it analyzes.  I look forward to seeing how you will accomplish that.</description>
		<content:encoded><![CDATA[<p>Ken:  I look forward to your follow-up.  What we need to realize (and what I should have mentioned first but did not in the interests of space) is that my analysis was done on the principle of providing the best possible explanation as to the meaning of a sentence that it is in fact grammatically flawed.  Much like with run-on sentences or sentence fragments, they may be gramatically incorrect, but you can still derive meaning from them.  They do, however, present the problem that you can misinterpret them (or &#8220;mis-analyze&#8221; them).  The analysis I did, in fact, takes a flawed sentence and parses it in such a manner that it elucidates the most likely meaning intended by the authors.  I did not accept your analysis as it tries to fit formal rules to a sentence that is flawed in the first place.  Your response to my analysis would have to reconcile your formal approach (which works perfectly well with grammatically correct sentences) with the flawed nature of the sentence it analyzes.  I look forward to seeing how you will accomplish that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Day</title>
		<link>http://www.adamsdrafting.com/2006/08/07/costly-drafting-errors-part-1/comment-page-1/#comment-353</link>
		<dc:creator>Brian Day</dc:creator>
		<pubDate>Wed, 06 Sep 2006 19:36:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/08/07/costly-drafting-errors-part-1/#comment-353</guid>
		<description>I think that splitting the provision into two sentences is the best option here. It has been my experience that many, if not most, drafting errors are caused by the sloppy management of dependent clauses.

If, however, the author was intent on cramming everything into a single sentence, then a workable solution would be to change the order of the last two dependent clauses:

“shall continue in force for a period of five years from the date it is made and, thereafter, unless terminated by one-year prior written notice by either party, for successive five-year terms.”

This solution is a far cry from poetry, and two separate sentences would be best. But it would have avoided the bad result for Rogers in this case.</description>
		<content:encoded><![CDATA[<p>I think that splitting the provision into two sentences is the best option here. It has been my experience that many, if not most, drafting errors are caused by the sloppy management of dependent clauses.</p>
<p>If, however, the author was intent on cramming everything into a single sentence, then a workable solution would be to change the order of the last two dependent clauses:</p>
<p>“shall continue in force for a period of five years from the date it is made and, thereafter, unless terminated by one-year prior written notice by either party, for successive five-year terms.”</p>
<p>This solution is a far cry from poetry, and two separate sentences would be best. But it would have avoided the bad result for Rogers in this case.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2006/08/07/costly-drafting-errors-part-1/comment-page-1/#comment-265</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Fri, 01 Sep 2006 02:01:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/08/07/costly-drafting-errors-part-1/#comment-265</guid>
		<description>Ray: For reasons that it would take too long to explain in this comment, I don&#039;t agree with your analysis. I expect that at some stage I&#039;ll write some more about this dispute. Ken</description>
		<content:encoded><![CDATA[<p>Ray: For reasons that it would take too long to explain in this comment, I don&#8217;t agree with your analysis. I expect that at some stage I&#8217;ll write some more about this dispute. Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ray Kovarik</title>
		<link>http://www.adamsdrafting.com/2006/08/07/costly-drafting-errors-part-1/comment-page-1/#comment-180</link>
		<dc:creator>Ray Kovarik</dc:creator>
		<pubDate>Tue, 29 Aug 2006 01:15:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/08/07/costly-drafting-errors-part-1/#comment-180</guid>
		<description>The CRTC&#039;s decision is predicated on the mistaken grammatical analysis that yielded false conclusion that the presence of both commas in the contentious sentence creates a paranthetical clause within the sentence.  However, in this case, the phrase &quot;and thereafter for successive five (5) year terms&quot; is not a paranthetical clause.

Correct analysis of the contentious sentence is made easier if we do a high-level parsing of the sentence.  The sentence in its original form appears as follows:
&quot;. . . this agreement shall be effective from the date it is made and shall continue in force for a period of five (5) years from the date it is made, and thereafter for successive five (5) year terms, unless and until terminated by one year prior notice in writing by either party.&quot;

The sentence, when parsed, reads:

SUBJECT		VERB			COMPLEMENT

this agreement	shall be effective	C1
		and
		shall continue in force	C2.1
					and
					C2.2
					unless and until
					C2.3

C1 = from the date it is made
C2.1 = for a period of five (5) years from the date it is made
C2.2 = thereafter for successive five (5) year terms
C2.3 = terminated by one year prior notice in writing by either party

Now we see that the commas are in fact used to separate a list of complements to the verb phrase &quot;shall continue in force&quot;.

The only question left to be answered is &quot;one year prior to what?&quot;.  The meaning of the first part of the sentence makes it evident that it is &quot;one year prior to the end of the first five-year period or any of the successive five-year terms&quot;.  It would never mean &quot;one year prior to when the terminating party wishes the agreement to no longer be in force&quot; (which would then make mention of five-year periods meaningless).

The CRTC made an error in fact in their grammatical analysis.  Once the analysis is done correctly, interpretation of the meaning of the entire sentence is plain and simple.  In my opinion, should Rogers choose to appeal their ruling, they would be successful.</description>
		<content:encoded><![CDATA[<p>The CRTC&#8217;s decision is predicated on the mistaken grammatical analysis that yielded false conclusion that the presence of both commas in the contentious sentence creates a paranthetical clause within the sentence.  However, in this case, the phrase &#8220;and thereafter for successive five (5) year terms&#8221; is not a paranthetical clause.</p>
<p>Correct analysis of the contentious sentence is made easier if we do a high-level parsing of the sentence.  The sentence in its original form appears as follows:<br />
&#8220;. . . this agreement shall be effective from the date it is made and shall continue in force for a period of five (5) years from the date it is made, and thereafter for successive five (5) year terms, unless and until terminated by one year prior notice in writing by either party.&#8221;</p>
<p>The sentence, when parsed, reads:</p>
<p>SUBJECT		VERB			COMPLEMENT</p>
<p>this agreement	shall be effective	C1<br />
		and<br />
		shall continue in force	C2.1<br />
					and<br />
					C2.2<br />
					unless and until<br />
					C2.3</p>
<p>C1 = from the date it is made<br />
C2.1 = for a period of five (5) years from the date it is made<br />
C2.2 = thereafter for successive five (5) year terms<br />
C2.3 = terminated by one year prior notice in writing by either party</p>
<p>Now we see that the commas are in fact used to separate a list of complements to the verb phrase &#8220;shall continue in force&#8221;.</p>
<p>The only question left to be answered is &#8220;one year prior to what?&#8221;.  The meaning of the first part of the sentence makes it evident that it is &#8220;one year prior to the end of the first five-year period or any of the successive five-year terms&#8221;.  It would never mean &#8220;one year prior to when the terminating party wishes the agreement to no longer be in force&#8221; (which would then make mention of five-year periods meaningless).</p>
<p>The CRTC made an error in fact in their grammatical analysis.  Once the analysis is done correctly, interpretation of the meaning of the entire sentence is plain and simple.  In my opinion, should Rogers choose to appeal their ruling, they would be successful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2006/08/07/costly-drafting-errors-part-1/comment-page-1/#comment-108</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Wed, 16 Aug 2006 16:01:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/08/07/costly-drafting-errors-part-1/#comment-108</guid>
		<description>I recently noticed some perceptive comments by &quot;anonymous&quot; to a post by Wayne Schiess on this topic at legalwriting.net. Today I revised my version of the contract language at issue to reflect anonymous&#039;s first comment and I added a paragraph to address his/her third comment. Ken Adams</description>
		<content:encoded><![CDATA[<p>I recently noticed some perceptive comments by &#8220;anonymous&#8221; to a post by Wayne Schiess on this topic at legalwriting.net. Today I revised my version of the contract language at issue to reflect anonymous&#8217;s first comment and I added a paragraph to address his/her third comment. Ken Adams</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Singularity &#187; A Misplaced Comma Causes Big Trouble</title>
		<link>http://www.adamsdrafting.com/2006/08/07/costly-drafting-errors-part-1/comment-page-1/#comment-101</link>
		<dc:creator>Singularity &#187; A Misplaced Comma Causes Big Trouble</dc:creator>
		<pubDate>Wed, 09 Aug 2006 20:22:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/08/07/costly-drafting-errors-part-1/#comment-101</guid>
		<description>[...] One contract drafting expert had this to say on the issue: [...]</description>
		<content:encoded><![CDATA[<p>[...] One contract drafting expert had this to say on the issue: [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
