<?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: Things that shouldn&#8217;t count as force majeure</title>
	<atom:link href="http://www.licensinghandbook.com/2010/01/05/things-that-shouldnt-count-as-force-majeure/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.licensinghandbook.com/2010/01/05/things-that-shouldnt-count-as-force-majeure/</link>
	<description>The companion site to the Software Licensing Handbook</description>
	<lastBuildDate>Wed, 06 Jan 2010 00:13:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Chris Lemens</title>
		<link>http://www.licensinghandbook.com/2010/01/05/things-that-shouldnt-count-as-force-majeure/comment-page-1/#comment-1073</link>
		<dc:creator>Chris Lemens</dc:creator>
		<pubDate>Wed, 06 Jan 2010 00:13:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.licensinghandbook.com/?p=1264#comment-1073</guid>
		<description>Ken:

In some special circumstances, I could see wanting a force majeure provision protecting me if my only real obligation was the payment of money. If I was entering a long-term strategic deal where the parties&#039; interests could diverge significantly over time and I was afraid that the other party would seize upon a failed payment as grounds to terminate even under a properly drafted termination-for-material-breach clause, then I would include one, especially if I was located some place where a natural disaster could affect the banking industry (many third-world countries, for example).

An example might be where you get an exclusive license to an intellectual property for an extended period of time and make the investment in marketing it; you would not want to lose your license for a failure to make a royalty payment that was outside of your control. In a bad enough disaster, you might lose the ability to even calculate the amount of the payment.* (That said, much of the risk for the situation could be removed through a sufficiently long cure period, or perhaps an extension to the cure period in the case of disaster, etc.) 

But I agree with you that it should be far from the norm.

Chris Lemens

* This reminds me of a story my dad told me about when he was working for the Texas attorney general&#039;s office defending state litigation. Apparently, their office caught fire; the damage to the building spread a fine layer of asbestos on everything. The government prohibited anyone from going into the building, even to get their files. This was before computers, so the state had no way to know anything -- even what cases it had -- until it got notices of default from the courts.</description>
		<content:encoded><![CDATA[<p>Ken:</p>
<p>In some special circumstances, I could see wanting a force majeure provision protecting me if my only real obligation was the payment of money. If I was entering a long-term strategic deal where the parties&#8217; interests could diverge significantly over time and I was afraid that the other party would seize upon a failed payment as grounds to terminate even under a properly drafted termination-for-material-breach clause, then I would include one, especially if I was located some place where a natural disaster could affect the banking industry (many third-world countries, for example).</p>
<p>An example might be where you get an exclusive license to an intellectual property for an extended period of time and make the investment in marketing it; you would not want to lose your license for a failure to make a royalty payment that was outside of your control. In a bad enough disaster, you might lose the ability to even calculate the amount of the payment.* (That said, much of the risk for the situation could be removed through a sufficiently long cure period, or perhaps an extension to the cure period in the case of disaster, etc.) </p>
<p>But I agree with you that it should be far from the norm.</p>
<p>Chris Lemens</p>
<p>* This reminds me of a story my dad told me about when he was working for the Texas attorney general&#8217;s office defending state litigation. Apparently, their office caught fire; the damage to the building spread a fine layer of asbestos on everything. The government prohibited anyone from going into the building, even to get their files. This was before computers, so the state had no way to know anything &#8212; even what cases it had &#8212; until it got notices of default from the courts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: uberVU - social comments</title>
		<link>http://www.licensinghandbook.com/2010/01/05/things-that-shouldnt-count-as-force-majeure/comment-page-1/#comment-1072</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Tue, 05 Jan 2010 21:06:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.licensinghandbook.com/?p=1264#comment-1072</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by negot8or: New post at licensinghandbook.com : Things that shouldn&#039;t count as force majeure http://bit.ly/6safHk...</description>
		<content:encoded><![CDATA[<p>&lt;strong&gt;Social comments and analytics for this post&#8230;&lt;/strong&gt;</p>
<p>This post was mentioned on Twitter by negot8or: New post at licensinghandbook.com : Things that shouldn&#8217;t count as force majeure <a href="http://bit.ly/6safHk.." rel="nofollow">http://bit.ly/6safHk..</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.licensinghandbook.com/2010/01/05/things-that-shouldnt-count-as-force-majeure/comment-page-1/#comment-1071</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Tue, 05 Jan 2010 18:08:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.licensinghandbook.com/?p=1264#comment-1071</guid>
		<description>Jeff: Your &quot;foreseeable&quot; test is rather tough, as many disasters are foreseeable. For example, I know that I should plan for the possibility of a hurricane hitting Long Island at some point. Perhaps what&#039;s more significant is the consequences of the event in question.

Force majeure provisions originated in contracts providing for future performance where hurricances and such like could directly impede performance--for example, construction contracts. Now you find them, unhelpfully, in all sorts of other contexts.

I&#039;m not sure it makes sense for a party to want the benefit of a force majeure provision even if their performance consists only of making payments. On that basis, you&#039;d have force majeure provisions in pretty much every contract.

Ken</description>
		<content:encoded><![CDATA[<p>Jeff: Your &#8220;foreseeable&#8221; test is rather tough, as many disasters are foreseeable. For example, I know that I should plan for the possibility of a hurricane hitting Long Island at some point. Perhaps what&#8217;s more significant is the consequences of the event in question.</p>
<p>Force majeure provisions originated in contracts providing for future performance where hurricances and such like could directly impede performance&#8211;for example, construction contracts. Now you find them, unhelpfully, in all sorts of other contexts.</p>
<p>I&#8217;m not sure it makes sense for a party to want the benefit of a force majeure provision even if their performance consists only of making payments. On that basis, you&#8217;d have force majeure provisions in pretty much every contract.</p>
<p>Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://www.licensinghandbook.com/2010/01/05/things-that-shouldnt-count-as-force-majeure/comment-page-1/#comment-1070</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Tue, 05 Jan 2010 16:39:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.licensinghandbook.com/?p=1264#comment-1070</guid>
		<description>Thanks Tom!  I agree.  I didn&#039;t mention those topics and I should&#039;ve.  Do you have recommendations on timing and notification that you&#039;d be willing to share?</description>
		<content:encoded><![CDATA[<p>Thanks Tom!  I agree.  I didn&#8217;t mention those topics and I should&#8217;ve.  Do you have recommendations on timing and notification that you&#8217;d be willing to share?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://www.licensinghandbook.com/2010/01/05/things-that-shouldnt-count-as-force-majeure/comment-page-1/#comment-1069</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Tue, 05 Jan 2010 16:38:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.licensinghandbook.com/?p=1264#comment-1069</guid>
		<description>Love it!  Thanks Chris!</description>
		<content:encoded><![CDATA[<p>Love it!  Thanks Chris!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Fox</title>
		<link>http://www.licensinghandbook.com/2010/01/05/things-that-shouldnt-count-as-force-majeure/comment-page-1/#comment-1068</link>
		<dc:creator>Tom Fox</dc:creator>
		<pubDate>Tue, 05 Jan 2010 16:34:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.licensinghandbook.com/?p=1264#comment-1068</guid>
		<description>Jeff-good and thoughtful article. After Hurricane Katrina, my employer, a major multi-national oilfield service company, instituted a company wide review of all FM clauses in all contracts. We found that there was no consistency among our own form contracts. In addition to the excellent points you raise, we had to tackle such things as how long the event be in place before an FM is declared and even how do you notify a counter-party of an FM event. FM clauses should be given more scrutiny as they are a significant part of risk management. Tom</description>
		<content:encoded><![CDATA[<p>Jeff-good and thoughtful article. After Hurricane Katrina, my employer, a major multi-national oilfield service company, instituted a company wide review of all FM clauses in all contracts. We found that there was no consistency among our own form contracts. In addition to the excellent points you raise, we had to tackle such things as how long the event be in place before an FM is declared and even how do you notify a counter-party of an FM event. FM clauses should be given more scrutiny as they are a significant part of risk management. Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arnoud Engelfriet</title>
		<link>http://www.licensinghandbook.com/2010/01/05/things-that-shouldnt-count-as-force-majeure/comment-page-1/#comment-1067</link>
		<dc:creator>Arnoud Engelfriet</dc:creator>
		<pubDate>Tue, 05 Jan 2010 16:10:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.licensinghandbook.com/?p=1264#comment-1067</guid>
		<description>Thanks for the explanation, Jeff. It&#039;s always fun to pick apart these clauses and to see the other party squirm because he doesn&#039;t understand why he has &quot;acts of the Public Enemy&quot; in the clause but doesn&#039;t want to give in as a general principle. 

It took me some digging to figure out what the public enemy is - apparently it means &quot;the other side in case of war&quot;. I don&#039;t know why &quot;war&quot; and &quot;acts of the public enemy&quot; need to be listed as two items then.</description>
		<content:encoded><![CDATA[<p>Thanks for the explanation, Jeff. It&#8217;s always fun to pick apart these clauses and to see the other party squirm because he doesn&#8217;t understand why he has &#8220;acts of the Public Enemy&#8221; in the clause but doesn&#8217;t want to give in as a general principle. </p>
<p>It took me some digging to figure out what the public enemy is &#8211; apparently it means &#8220;the other side in case of war&#8221;. I don&#8217;t know why &#8220;war&#8221; and &#8220;acts of the public enemy&#8221; need to be listed as two items then.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Lemens</title>
		<link>http://www.licensinghandbook.com/2010/01/05/things-that-shouldnt-count-as-force-majeure/comment-page-1/#comment-1066</link>
		<dc:creator>Chris Lemens</dc:creator>
		<pubDate>Tue, 05 Jan 2010 15:45:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.licensinghandbook.com/?p=1264#comment-1066</guid>
		<description>Jeff:

Another example of context-dependent force majeure clauses: Never allow &quot;government regulation&quot; to be force majeure in your contract with the government.

Chris</description>
		<content:encoded><![CDATA[<p>Jeff:</p>
<p>Another example of context-dependent force majeure clauses: Never allow &#8220;government regulation&#8221; to be force majeure in your contract with the government.</p>
<p>Chris</p>
]]></content:encoded>
	</item>
</channel>
</rss>

