<?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 for Technology Law Notes</title>
	<atom:link href="http://www.techlawnotes.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.techlawnotes.com</link>
	<description>On contracts, intellectual property, and startup companies. By D. C. Toedt</description>
	<lastBuildDate>Tue, 24 Jan 2012 14:07:07 -0600</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>Comment on A cautionary tale:  Don&#8217;t say &#8220;renew&#8221; when you mean &#8220;extend&#8221; by Koncision » A Reminder of the Limitations of Terms of Art</title>
		<link>http://www.techlawnotes.com/a-cautionary-tale-dont-say-renew-when-you-mean-extend/comment-page-1/#comment-11383</link>
		<dc:creator>Koncision » A Reminder of the Limitations of Terms of Art</dc:creator>
		<pubDate>Tue, 24 Jan 2012 14:07:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.techlawnotes.com/?p=9643#comment-11383</guid>
		<description>[...] A Reminder of the Limitations of Terms of Art  Posted on January 23, 2012 by Kenneth A. Adams    var addthis_product = &#039;wpp-261&#039;; var addthis_config = {&quot;data_track_clickback&quot;:true};Reader D.C. Toedt let me know about the recent opinion of the Eighth Circuit Court of Appeals in Camelot LLC v. AMC ShowPalace Theatres, Inc., and he wrote about it himself here. [...]</description>
		<content:encoded><![CDATA[<p>[...] A Reminder of the Limitations of Terms of Art  Posted on January 23, 2012 by Kenneth A. Adams    var addthis_product = &#039;wpp-261&#039;; var addthis_config = {&quot;data_track_clickback&quot;:true};Reader D.C. Toedt let me know about the recent opinion of the Eighth Circuit Court of Appeals in Camelot LLC v. AMC ShowPalace Theatres, Inc., and he wrote about it himself here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ouch! Judge Posner eviscerates both a damages expert and the trial judge who let him testify against FedEx by Posner: Plaintiff&#8217;s Regression Analysis has as many Bloody Wounds as Julius Caesar &#171; Science Bar</title>
		<link>http://www.techlawnotes.com/ouch-judge-posner-eviscerates-both-a-damages-expert-and-the-trial-judge-who-let-him-testify-against-fedex/comment-page-1/#comment-9561</link>
		<dc:creator>Posner: Plaintiff&#8217;s Regression Analysis has as many Bloody Wounds as Julius Caesar &#171; Science Bar</dc:creator>
		<pubDate>Mon, 09 Jan 2012 20:30:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.lawnotes.com/?p=9509#comment-9561</guid>
		<description>[...] Airlines v. FedEx (7th Cir. Dec. 27, 2011). Via D.C. Toedt&#8217;s Excellent Law Notes Blog. Share this:TwitterFacebookLinkedInTumblrLike this:LikeBe the first to like this post.  Tags: [...]</description>
		<content:encoded><![CDATA[<p>[...] Airlines v. FedEx (7th Cir. Dec. 27, 2011). Via D.C. Toedt&#8217;s Excellent Law Notes Blog. Share this:TwitterFacebookLinkedInTumblrLike this:LikeBe the first to like this post.  Tags: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why you should draft contracts with long, run-on paragraphs by Lynne Sears Williams</title>
		<link>http://www.techlawnotes.com/why-you-should-draft-contracts-with-long-run-on-paragraphs/comment-page-1/#comment-9139</link>
		<dc:creator>Lynne Sears Williams</dc:creator>
		<pubDate>Fri, 06 Jan 2012 02:41:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.lawnotes.com/?p=9549#comment-9139</guid>
		<description>Very funny. Best laugh today goes to D.C. Toedt!</description>
		<content:encoded><![CDATA[<p>Very funny. Best laugh today goes to D.C. Toedt!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why you should draft contracts with long, run-on paragraphs by Tom Bowden</title>
		<link>http://www.techlawnotes.com/why-you-should-draft-contracts-with-long-run-on-paragraphs/comment-page-1/#comment-9084</link>
		<dc:creator>Tom Bowden</dc:creator>
		<pubDate>Thu, 05 Jan 2012 17:03:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.lawnotes.com/?p=9549#comment-9084</guid>
		<description>Nice try, but surely you could have extended their amateurish efforts by tossing in a few more &quot;in the event thats&quot; and the obligatory &quot;&quot;For the avoidance of doubt...&quot;  I love those, because they are so slyly insincere.  Avoidance of doubt?  I mean seriously, we&#039;ve got a business to run here and if we draft contracts for the avoidance of doubt, whose gonna pay the mortgage?  You don&#039;t expect Jiffy lube to let you bring your own oil to their shop do you?  What makes clients think they should be able to read their own contracts?  Or judges for that matter?</description>
		<content:encoded><![CDATA[<p>Nice try, but surely you could have extended their amateurish efforts by tossing in a few more &#8220;in the event thats&#8221; and the obligatory &#8220;&#8221;For the avoidance of doubt&#8230;&#8221;  I love those, because they are so slyly insincere.  Avoidance of doubt?  I mean seriously, we&#8217;ve got a business to run here and if we draft contracts for the avoidance of doubt, whose gonna pay the mortgage?  You don&#8217;t expect Jiffy lube to let you bring your own oil to their shop do you?  What makes clients think they should be able to read their own contracts?  Or judges for that matter?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Brevity in contracts isn&#8217;t always the supreme virtue by D. C. Toedt</title>
		<link>http://www.techlawnotes.com/brevity-in-contracts-is-not-the-supreme-virtue/comment-page-1/#comment-2927</link>
		<dc:creator>D. C. Toedt</dc:creator>
		<pubDate>Thu, 20 Oct 2011 17:14:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.ontechnologylaw.com/?p=7658#comment-2927</guid>
		<description>Tom, I use &quot;For the avoidance of doubt&quot; quite a bit. Mainly it&#039;s to try to nip in the bud any attempt by the other side&#039;s trial counsel to argue a different implied meaning of the preceding term.
Here are two examples, from a services agreement form I recently did for a client:
&lt;blockquote&gt;
(4) For the avoidance of doubt, each Statement of Work will be construed as requiring Provider to perform all individual tasks necessary for the proper rendering of the relevant services, even if one or more such individual tasks is not expressly stated there.
(5) For the avoidance of doubt, Provider is under no obligation to provide services not described in a Statement of Work unless the parties have expressly agreed otherwise in writing.
&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<p>Tom, I use &#8220;For the avoidance of doubt&#8221; quite a bit. Mainly it&#8217;s to try to nip in the bud any attempt by the other side&#8217;s trial counsel to argue a different implied meaning of the preceding term. </p>
<p>Here are two examples, from a services agreement form I recently did for a client: </p>
<blockquote><p>
(4) For the avoidance of doubt, each Statement of Work will be construed as requiring Provider to perform all individual tasks necessary for the proper rendering of the relevant services, even if one or more such individual tasks is not expressly stated there. </p>
<p>(5) For the avoidance of doubt, Provider is under no obligation to provide services not described in a Statement of Work unless the parties have expressly agreed otherwise in writing.
</p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Brevity in contracts isn&#8217;t always the supreme virtue by Tom Bowden</title>
		<link>http://www.techlawnotes.com/brevity-in-contracts-is-not-the-supreme-virtue/comment-page-1/#comment-2924</link>
		<dc:creator>Tom Bowden</dc:creator>
		<pubDate>Thu, 20 Oct 2011 15:09:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.ontechnologylaw.com/?p=7658#comment-2924</guid>
		<description>DC - What is your opinion on the now nearly ubiquitous language &quot;For the avoidance of doubt.....&quot;?  I was taught to say things once, and say it right the first time, rather than restate the same concept in a different way.  This is a recipe for ambiguity in my opinion.  On the other hand I do agree with using formulas and calculations to demonstrate precisely what is intended.</description>
		<content:encoded><![CDATA[<p>DC &#8211; What is your opinion on the now nearly ubiquitous language &#8220;For the avoidance of doubt&#8230;..&#8221;?  I was taught to say things once, and say it right the first time, rather than restate the same concept in a different way.  This is a recipe for ambiguity in my opinion.  On the other hand I do agree with using formulas and calculations to demonstrate precisely what is intended.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PRECUT free, balanced, curated technology contracts by mechatars</title>
		<link>http://www.techlawnotes.com/precut/comment-page-1/#comment-2761</link>
		<dc:creator>mechatars</dc:creator>
		<pubDate>Sun, 16 Oct 2011 04:59:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.ontechnologylaw.com/#comment-2761</guid>
		<description>Thanks,
I just downloaded the Nondisclosure agreement.
Great share!</description>
		<content:encoded><![CDATA[<p>Thanks,<br />
I just downloaded the Nondisclosure agreement.</p>
<p>Great share!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Title change by Gerben Schoorl</title>
		<link>http://www.techlawnotes.com/title-change/comment-page-1/#comment-2280</link>
		<dc:creator>Gerben Schoorl</dc:creator>
		<pubDate>Wed, 28 Sep 2011 19:31:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.dctoedt.com/?p=8259#comment-2280</guid>
		<description>Dear Mr. Toedt,
Since Google recognized your name halfway my typing it, I&#039;m quote sure that THE difference Will be negligable.
Writing this on an iPad allows me to convey another, progressing, thought. There are à few notable errors in this reply, caused solely by automatic language correction. Where this Will take us and NeXT generations can only be guessed.
Kind regards,
Gerben Schoorl</description>
		<content:encoded><![CDATA[<p>Dear Mr. Toedt,</p>
<p>Since Google recognized your name halfway my typing it, I&#8217;m quote sure that THE difference Will be negligable.<br />
Writing this on an iPad allows me to convey another, progressing, thought. There are à few notable errors in this reply, caused solely by automatic language correction. Where this Will take us and NeXT generations can only be guessed.</p>
<p>Kind regards,</p>
<p>Gerben Schoorl</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Seven ways to be a stand-up guy at work by David Healey</title>
		<link>http://www.techlawnotes.com/seven-ways-to-be-a-stand-up-guy-at-work/comment-page-1/#comment-2054</link>
		<dc:creator>David Healey</dc:creator>
		<pubDate>Sat, 06 Aug 2011 22:41:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.ontechnologylaw.com/?p=8116#comment-2054</guid>
		<description>Good advice, if more people followed it, we would have stronger firms and happier people.</description>
		<content:encoded><![CDATA[<p>Good advice, if more people followed it, we would have stronger firms and happier people.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Negotiating contractual limitations of liability:  Do it risk by risk, not one-size-fits-all by D. C. Toedt</title>
		<link>http://www.techlawnotes.com/negotiating-contractual-limitations-of-liability-do-it-risk-by-risk-not-one-size-fits-all/comment-page-1/#comment-2052</link>
		<dc:creator>D. C. Toedt</dc:creator>
		<pubDate>Fri, 29 Jul 2011 18:28:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.ontechnologylaw.com/?p=5627#comment-2052</guid>
		<description>Good point, Patrick&#160;&#8212; the first column should probably be re-labeled &quot;Harm &lt;em&gt;[vice Damages]&lt;/em&gt; arising from the breach.&quot;</description>
		<content:encoded><![CDATA[<p>Good point, Patrick&nbsp;&mdash; the first column should probably be re-labeled &#8220;Harm <em>[vice Damages]</em> arising from the breach.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

