<?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: Two Aspects of &#8220;May&#8221;—A Case Study in Interpreting Contract Language</title>
	<atom:link href="http://www.adamsdrafting.com/2007/06/14/two-aspects-of-may/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamsdrafting.com/2007/06/14/two-aspects-of-may/</link>
	<description></description>
	<lastBuildDate>Thu, 18 Mar 2010 12:12:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Brian Day</title>
		<link>http://www.adamsdrafting.com/2007/06/14/two-aspects-of-may/comment-page-1/#comment-28435</link>
		<dc:creator>Brian Day</dc:creator>
		<pubDate>Thu, 03 Jan 2008 19:31:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/06/14/two-aspects-of-may/#comment-28435</guid>
		<description>This language strikes me as problematic for another reason. Does the royalty-reduction provision apply if the developer acts on its own? 

The &quot;subject to&quot; language could be read as a limitation on the developer&#039;s authority to cooperate with its partners. Consider the phrase, &quot;You may attend the party wearing a Speedo, but only if you pay a $5 charge.&quot; A reasonable interpretation of this phrase is that I am invited to the party, but must pay to wear my slinky swim trunks (a very low price in light of the emotional trauma that would be imposed on the other party-goers). In the same vein, a reasonable interpretation of the contract provision is that the developer is authorized to develop products, but must pay to work with third parties.

Obviously, any interpretation depends upon the context supplied by the rest of the contract. But taking this provision alone illustrates one of the principle problems of legal drafting--too much material in too little space.

There are three separate issues crammed into a single sentence: (i) the authority to develop products; (ii) the cooperation with third-parties; and (iii) the conditional royalty reduction. By dealing with these issues in two or even three sentences, the author would have been able to control the interplay between the three issues. By forcing them into one brief sentence, he or she has surrendered much of that control.</description>
		<content:encoded><![CDATA[<p>This language strikes me as problematic for another reason. Does the royalty-reduction provision apply if the developer acts on its own? </p>
<p>The &#8220;subject to&#8221; language could be read as a limitation on the developer&#8217;s authority to cooperate with its partners. Consider the phrase, &#8220;You may attend the party wearing a Speedo, but only if you pay a $5 charge.&#8221; A reasonable interpretation of this phrase is that I am invited to the party, but must pay to wear my slinky swim trunks (a very low price in light of the emotional trauma that would be imposed on the other party-goers). In the same vein, a reasonable interpretation of the contract provision is that the developer is authorized to develop products, but must pay to work with third parties.</p>
<p>Obviously, any interpretation depends upon the context supplied by the rest of the contract. But taking this provision alone illustrates one of the principle problems of legal drafting&#8211;too much material in too little space.</p>
<p>There are three separate issues crammed into a single sentence: (i) the authority to develop products; (ii) the cooperation with third-parties; and (iii) the conditional royalty reduction. By dealing with these issues in two or even three sentences, the author would have been able to control the interplay between the three issues. By forcing them into one brief sentence, he or she has surrendered much of that control.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
