<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Seattle Patents &#187; Uncategorized</title>
	<atom:link href="http://seattlepatents.com/category/uncategorized/feed/" rel="self" type="application/rss+xml" />
	<link>http://seattlepatents.com</link>
	<description>Patent law updates from Seattle-based Axios Law</description>
	<lastBuildDate>Thu, 03 Sep 2009 23:38:28 +0000</lastBuildDate>
	
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title></title>
		<link>http://seattlepatents.com/2009/09/170/</link>
		<comments>http://seattlepatents.com/2009/09/170/#comments</comments>
		<pubDate>Thu, 03 Sep 2009 23:38:28 +0000</pubDate>
		<dc:creator>Chad Kirby</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://seattlepatents.com/?p=170</guid>
		<description><![CDATA[I have a guest post today over at TechFlash about  Apple&#8217;s recent rejection of my iPhone programmer&#8217;s calculator app, Calc 0&#215;0. In rejecting my app submission, Apple&#8217;s review team objected to my use of a generic keyword (&#8220;bitwise&#8221;) to describe a prominent feature of the app (bitwise operations). According to Apple, I cannot use this term [...]]]></description>
			<content:encoded><![CDATA[<p>I have a <a href="http://www.techflash.com/seattle/2009/09/why_apple_rejected_my_iphone_app.html"><span style="text-decoration: none"><span style="color: #0000ff">guest post</span></span></a> today over at <a title="Why Apple nixed my iPhone app" href="http://www.techflash.com/"><span style="text-decoration: none"><span style="color: #0000ff">TechFlash</span></span></a> about  Apple&#8217;s recent rejection of my iPhone programmer&#8217;s calculator app, <a title="Calc Zero" href="http://calczero.uplakemedia.com/" target="_blank"><span style="text-decoration: none"><span style="color: #0000ff">Calc 0&#215;0</span></span></a>. In rejecting my app submission, Apple&#8217;s review team objected to my use of a generic keyword (&#8220;bitwise&#8221;) to describe a prominent feature of the app (bitwise operations). According to Apple, I cannot use this term as a keyword because there is another application that uses the term as its name (an apparent reference to the IM client for OSX named &#8220;Bitwise&#8221;). I note that Apple&#8217;s keyword policy appears to prohibit the descriptive use of generic terms, use that would clearly be allowed by accepted trademark doctrine.</p>
<div id="attachment_171" class="wp-caption aligncenter" style="width: 170px"><img class="size-medium wp-image-171 " src="http://seattlepatents.com/wp-content/uploads/2009/09/Programmer-Mode-208x300.png" alt="Calc 0x0 interface" width="160" height="230" /><p class="wp-caption-text">Calc 0x0 interface</p></div>
]]></content:encoded>
			<wfw:commentRss>http://seattlepatents.com/2009/09/170/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nit Picking for $2M</title>
		<link>http://seattlepatents.com/2009/06/nit-picking-for-2m/</link>
		<comments>http://seattlepatents.com/2009/06/nit-picking-for-2m/#comments</comments>
		<pubDate>Thu, 04 Jun 2009 21:43:13 +0000</pubDate>
		<dc:creator>Chad Kirby</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[contract]]></category>
		<category><![CDATA[grammar]]></category>

		<guid isPermaLink="false">http://seattlepatents.com/?p=142</guid>
		<description><![CDATA[This is not strictly patent related, except that it highlights the importance of careful drafting. As illustrated by this cautionary tale, imprecise language can occasionally come back with a vengeance to bite you and/or your client.

The Globe and Mail reports on "the most costly piece of punctuation in Canada," in which one ambiguously drafted clause costs Rogers Communications over $2M in a contract dispute. (Actually, the culprit is not exactly the punctuation per se, but rather a poorly drafted sentence.)]]></description>
			<content:encoded><![CDATA[<p>This is not strictly patent related, except that it highlights the importance of careful drafting. As illustrated by this cautionary tale, imprecise language can occasionally come back with a vengeance to bite you and/or your client.</p>
<p>The <a title="Comma quirk irks Rogers" href="http://www.theglobeandmail.com/report-on-business/article838561.ece" target="_blank">Globe and Mail</a> reports on &#8220;the most costly piece of punctuation in Canada,&#8221; in which one ambiguously drafted clause costs Rogers Communications over $2M in a contract dispute. (Actually, the culprit is not exactly the punctuation <em>per se</em>, but rather a poorly drafted sentence.)</p>
<p><span id="more-142"></span>Page 7 of the contract at issue states that the agreement &#8220;shall continue in force for a period of five years from the date it is made, and thereafter for successive five year terms, <strong>unless and until terminated by one year prior notice in writing by either party</strong>.&#8221;</p>
<p>According to this sentence, when does the termination option apply?</p>
<p>Apparently Rogers intended that the termination option apply only in the &#8220;successive five year terms.&#8221; However, there&#8217;s a very good argument to be made that the &#8220;unless and until&#8221; clause applies any time the agreement is in force. The writer chose to draft the sentence almost as if he or she were presenting a list of independent clauses setting out conditions under which the agreement shall continue in force: it shall continue for five years; it shall continue thereafter for successive five year terms; and it shall continue unless and until terminated.</p>
<p>Although the sentence, as drafted,  is somewhat ambiguous, I think the Canadian Radio-television and Telecommunications Commission (CRTC)  probably parsed the sentence correctly.</p>
<p>Rogers could have eliminated the ambiguity by not trying to pack so much information into a single sentence. One possible re-draft might read as follows:</p>
<p style="padding-left: 30px;">The agreement &#8220;shall continue in force for a period of five years from the date it is made. Thereafter, the agreement shall continue in force for successive five year terms, unless and until terminated by one year prior notice in writing by either party.&#8221;</p>
<p>This re-draft is somewhat more verbose, as the subject (&#8220;the agreement&#8221;) is repeated in successive sentences. However, this more verbose formulation eliminates the ambiguity that was present in the original. When the first five year period and the subsequent five year periods are addressed in separate sentences, it becomes clear that the termination clause applies only &#8220;[t]hereafter&#8230; for successive five year terms&#8230;.&#8221;</p>
<p>Thanks to <a title="TidBITS" href="http://db.tidbits.com/" target="_blank">TidBITS</a> for bringing the story to my attention.</p>
]]></content:encoded>
			<wfw:commentRss>http://seattlepatents.com/2009/06/nit-picking-for-2m/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
