<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" version="2.0">

<channel>
	<title>Seattle Patents</title>
	
	<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>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/SeattlePatents" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="seattlepatents" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<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>USPTO says some random dudes invented podcasting</title>
		<link>http://seattlepatents.com/2009/07/podcast-patent/</link>
		<comments>http://seattlepatents.com/2009/07/podcast-patent/#comments</comments>
		<pubDate>Fri, 31 Jul 2009 21:38:33 +0000</pubDate>
		<dc:creator>Chad Kirby</dc:creator>
				<category><![CDATA[Patent Prosecution]]></category>
		<category><![CDATA[patent]]></category>
		<category><![CDATA[podcast]]></category>
		<category><![CDATA[prior art]]></category>

		<guid isPermaLink="false">http://seattlepatents.com/?p=159</guid>
		<description><![CDATA[On July 28, 2009, the USPTO issued patent number 7,568,213, the so-called &#8220;podcasting patent.&#8221;
Claim 1 is directed to
A method for providing episodic media, the method comprising:
providing a user with access to a channel dedicated to episodic media, wherein the episodic media provided over the channel is pre-defined into one or more episodes by a remote publisher of [...]]]></description>
			<content:encoded><![CDATA[<p>On July 28, 2009, the USPTO issued patent number <a class="wpgallery" title="US Pat No 7568213" href="http://patft1.uspto.gov/netacgi/nph-Parser?Sect1=PTO1&amp;Sect2=HITOFF&amp;d=PALL&amp;p=1&amp;u=%2Fnetahtml%2FPTO%2Fsrchnum.htm&amp;r=1&amp;f=G&amp;l=50&amp;s1=7568213.PN.&amp;OS=PN/7568213&amp;RS=PN/7568213" target="_blank"><span style="color: #000080"><span style="text-decoration: none">7,568,213</span></span></a>, the so-called &#8220;<a title="VoloMedia Awarded Patent for Podcasting" href="http://theappleblog.com/2009/07/30/volomedia-awarded-patent-for-podcasting/" target="_blank"><span style="color: #000080"><span style="text-decoration: none">podcasting patent</span></span></a>.&#8221;</p>
<p><span id="more-159"></span>Claim 1 is directed to</p>
<p style="padding-left: 30px">A method for providing episodic media, the method comprising:</p>
<p style="padding-left: 60px">providing a user with access to a channel dedicated to episodic media, wherein the episodic media provided over the channel is pre-defined into one or more episodes by a remote publisher of the episodic media;</p>
<p style="padding-left: 60px">receiving a subscription request to the channel dedicated to the episodic media from the user;</p>
<p style="padding-left: 60px">automatically downloading updated episodic media associated with the channel dedicated to the episodic media to a computing device associated with the user in accordance with the subscription request upon availability of the updated episodic media, the automatic download occurring without further user interaction; and</p>
<p style="padding-left: 60px">providing the user with:</p>
<p style="padding-left: 90px">an indication of a maximum available channel depth,</p>
<p style="padding-left: 90px">the channel depth indicating a size of episodic media yet to be downloaded from the channel and size of episodic media already downloaded from the channel, the channel depth being specified in playtime or storage resources, and</p>
<p style="padding-left: 90px">the ability to modify the channel depth by deleting selected episodic media content, thereby overriding the previously configured channel depth.</p>
<p>The &#8220;podcasting patent&#8221; is a continuation of an application filed November 19, 2003. Applicants filed the continuation less than a year ago, in October 2008, and after one false start, successfully petitioned for accelerated examination.</p>
<p>One of the most striking things about the prosecution of this application is that it appears that Applicant did not submit (and the Examiner did not consider) a single piece of &#8220;non-patent literature.&#8221; In other words, when determining whether these claims were patentable, <strong>neither the Applicant, nor the USPTO appears to have considered any publications except patents and patent applications</strong>.</p>
<p>As a result, the Examiner never looked at any publications from <a title="Scripting News" href="http://scripting.com/" target="_blank"><span style="color: #000080"><span style="text-decoration: none">Dave Winer</span></span></a>, who was a major contributor to the development of <a title="Wikipedia RSS article" href="http://en.wikipedia.org/wiki/RSS" target="_blank"><span style="color: #000080"><span style="text-decoration: none">RSS</span></span></a> in the years prior to November 2003. For example, in October 2002 (more than a year before the podcasting patent&#8217;s earliest priority date), Dave <a title="Saturday, October 12, 2002 " href="http://archive.scripting.com/2002/10/12" target="_blank"><span style="color: #000080"><span style="text-decoration: none">wrote</span></span></a> about &#8220;a new tool called <em>RSS Explorer.</em> &#8230;. It allows you to browse another Radio user&#8217;s subscriptions, and click checkboxes to subscribe.&#8221; And by at least mid-2003, the RSS 2.0 specification supported media &#8220;<a title="How to support enclosures in aggregators  " href="http://cyber.law.harvard.edu/rss/enclosuresAggregators.html" target="_blank"><span style="color: #000080"><span style="text-decoration: none">enclosures</span></span></a>.&#8221; Indeed, the Radio Userland application, which shipped in January 2002, was &#8220;<a title="Did VoloMedia invent Podcasting?" href="http://www.scripting.com/stories/2009/07/29/didVolomediaInventPodcasti.html" target="_blank"><span style="color: #000080"><span style="text-decoration: none">both a podcast distributor and a podcast client</span></span></a>.&#8221;</p>
<p>Would an examiner have considered a big chunk of Claim 1 to be obvious considering a combination of these references? Maybe, maybe not. But it seems clear that a giant swath of relevant prior art was never considered during examination, and now that the patent has issued, it&#8217;ll cost someone a lot of money to undo that.</p>
<p>In this case, it looks like the applicants effectively used the pre-exam search and support documents to frame the examination around just a few patent applications that the applicants thought (correctly, as it turns out) they could distinguish. As a result, some random dudes you never heard of were granted a probably-undeserved monopoly over a big chunk of an incredibly common mode of media distribution.</p>
<p>Seems likely that the only people who are going to end up benefitting from this patent are the lawyers who will get paid to wrangle over it for the next few years.</p>
]]></content:encoded>
			<wfw:commentRss>http://seattlepatents.com/2009/07/podcast-patent/feed/</wfw:commentRss>
		<slash:comments>4</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>
		<item>
		<title>Prediction: Supreme Court to embrace software patents</title>
		<link>http://seattlepatents.com/2009/06/supreme-court-to-embrace-software-patents/</link>
		<comments>http://seattlepatents.com/2009/06/supreme-court-to-embrace-software-patents/#comments</comments>
		<pubDate>Tue, 02 Jun 2009 23:22:08 +0000</pubDate>
		<dc:creator>Michael Rice</dc:creator>
				<category><![CDATA[Legal Update]]></category>
		<category><![CDATA[Litigation]]></category>
		<category><![CDATA[Patent Prosecution]]></category>
		<category><![CDATA[Recent Cases]]></category>
		<category><![CDATA[Bilski]]></category>
		<category><![CDATA[federal circuit]]></category>
		<category><![CDATA[In re Bilski]]></category>
		<category><![CDATA[Supreme Court]]></category>

		<guid isPermaLink="false">http://seattlepatents.com/?p=136</guid>
		<description><![CDATA[Last year, Axios's managing partner, Adam Philipp, cautioned that Bilski hardly spelled the demise of software patents. And now I’m predicting that the Supreme Court is about to overturn Bilski and emphasize that software is still patentable in the process. Allow me to explain . . .]]></description>
			<content:encoded><![CDATA[<p>Last year, Axios&#8217;s managing partner, <strong><a href="http://www.axioslaw.com/attorneys-and-staff/adam-lk-philipp/">Adam Philipp</a></strong>, cautioned <a href="http://seattlepatents.com/2008/11/software-and-business-method-patents-update/">that Bilski hardly spelled the demise of software patents</a>. And now I’m predicting that the Supreme Court is about to overturn <em>Bilski</em> and <strong>rule conclusively that software is quite patentable</strong> in the process. Allow me to explain . . .</p>
<p><span id="more-136"></span></p>
<p>If you recall, the <a href="http://www.cafc.uscourts.gov/">Federal Circuit</a> (a court that issues most key patent law rulings) released an important decision, <a href="http://www.cafc.uscourts.gov/opinions/07-1130.pdf"><em>In re Bilski</em></a>, last October. Initially, many commentators erroneously opined that the decision invalidated software patents. <strong>It didn’t.</strong> While <em>Bilski</em> curtailed “pure” business method patents (e.g., a method for preparing a tax return), it had very little impact on the ability of an innovator to obtain a patent on software through a careful patent attorney. Indeed, I’ve even seen some office actions in which the examiner himself offered changes to claim language to make the software patent-oriented claim conform to <em>Bilski</em>.</p>
<p>Yesterday, the Supreme Court “granted cert.” This means the Supreme Court wants to review the decision, and <strong>it likely also means the Supreme Court was dissatisfied with <em>Bilski</em></strong>.</p>
<p>Indeed, the <a href="http://blogs.wsj.com/law/2009/06/01/bilski-supremes-grant-cert-on-business-method-patent-case/">Wall Street Journal Law Blog quoted Laurence Rogers</a>, an E.E. patent lawyer at Ropes and Gray as saying, “The Supreme Court doesn’t get involved in patent cases unless it sees something it doesn’t like.”</p>
<p>In addition, <a href="http://thepriorart.typepad.com/the_prior_art/2009/06/handicapping-bilski-at-the-supreme-court.html">Joe Mullin at The Prior Art quotes <strong>Mark Lemley</strong></a>—intellectual property law glitterati and Stanford law professor—as saying, “They either looked at the <em>Bilski</em> legal test <strong>and said it&#8217;s an unworkable test</strong>, or they looked at their own precedent and decided they didn’t like that.” Prof. Lemley goes on to say, “If you look at other Supreme Court patent cases in recent years, they show no compunction about overturning settled wisdom in the Federal Circuit and courts of appeals.”</p>
<p>Thus, I’m predicting that the Supreme’s Court’s willingness to hear <em>Bilski</em> may be just that—an indicator they’ll overturn it.</p>
]]></content:encoded>
			<wfw:commentRss>http://seattlepatents.com/2009/06/supreme-court-to-embrace-software-patents/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Bilski’s “blank slate” is bad news for Every Penny Counts</title>
		<link>http://seattlepatents.com/2009/05/bilskis-blank-slate-is-bad-news-for-every-penny-counts/</link>
		<comments>http://seattlepatents.com/2009/05/bilskis-blank-slate-is-bad-news-for-every-penny-counts/#comments</comments>
		<pubDate>Fri, 29 May 2009 19:58:29 +0000</pubDate>
		<dc:creator>Chad Kirby</dc:creator>
				<category><![CDATA[Patent Prosecution]]></category>
		<category><![CDATA[Recent Cases]]></category>
		<category><![CDATA[Bilski]]></category>
		<category><![CDATA[federal court]]></category>
		<category><![CDATA[means-plus-function]]></category>
		<category><![CDATA[patent]]></category>

		<guid isPermaLink="false">http://seattlepatents.com/?p=132</guid>
		<description><![CDATA[Over at the 271 Patent Blog, Peter Zura summarizes Every Penny Counts, Inc. v. Bank of America Corp., 2-07-cv-00042 (M.D. Fla. May 27, 2009, Order) (Magnuson, J.). In this case, the district court holds that, under Bilski, the claimed system is not patentable subject matter under § 101.

In Every Penny Counts, the district court uses Bilski as Judge Newman predicted in her Bilski dissent: "each trial court… will have a blank slate on which to uphold or invalidate claims based on whether there are sufficient 'meaningful limits'" imposed on the claim by the use of a particular machine.]]></description>
			<content:encoded><![CDATA[<p>Over at the <a title="271 Patent Blog" href="http://271patent.blogspot.com" target="_blank">271 Patent Blog</a>, Peter Zura summarizes <strong><em><a title="Every Penny Counts v. Bank of America Corp." href="http://271patent.blogspot.com/2009/05/process-requiring-machine-doesnt.html" target="_blank">Every Penny Counts, Inc. v. Bank of America Corp.</a>,</em></strong> 2-07-cv-00042 (M.D. Fla. May 27, 2009, Order) (Magnuson, J.). In this case, the district court holds that, under <em>Bilski</em>, the claimed system is not patentable subject matter under § 101.</p>
<p>In <em>Every Penny Counts</em>, the district court uses <em>Bilski</em> as Judge Newman predicted in her <em>Bilski</em> dissent: &#8220;each trial court… will have a blank slate on which to uphold or invalidate claims based on whether there are sufficient &#8216;meaningful limits&#8217;&#8221; imposed on the claim by the use of a particular machine.</p>
<p><span id="more-132"></span>In <em>Every Penny Counts</em>, the district court analogizes the claimed system to that of <a title="Gottschalk v. Benson" href="http://supreme.justia.com/us/409/63/case.html" target="_blank"><em>Gottschalk v. Benson</em></a>, 409 U.S. 63, 64-66 (1972), in which a method of programming a digital computer to convert signals from binary-coded decimal to pure binary form was found to be unpatentable. In <em>Gottschalk</em>, the Supreme Court reasoned that because converting binary-coded decimal to pure binary form had no use outside a computer, allowing the patent to stand would &#8220;<span class="headertext">wholly preempt the mathematical formula and, in practical effect, would be a patent of the algorithm itself.&#8221;</span></p>
<p><span class="headertext">In <em>Every Penny Counts</em>, the district court quotes </span><em>Gottschalk, </em><span class="headertext">stating, in a conclusory manner, that the system at issue &#8220;&#8216;has no substantial practical application except in connection with&#8217; computers, cash registers, and networks&#8230;.&#8221; </span></p>
<p><span class="headertext">However, this reasoning misses the mark because unlike <em>Gottschalk</em>&#8217;s binary conversion algorithm, many of the claimed elements could </span><span class="headertext">certainly</span><span class="headertext"> have practical application outside a computer. For example, a computer is not practically required to &#8220;determin[e] an excess payment on the basis of the determinant established by the payor,&#8221; nor is a computer practically required to &#8220;apportion[] at least a part of the excess payment amount said accounts on the basis of the excess determined.&#8221; </span></p>
<p><span class="headertext">On this point, at least, </span><span class="headertext"><em>Gottschalk</em> seems distinguishable. </span><span class="headertext">In </span><em>Gottschalk, </em><span class="headertext">the Supreme Court implicitly recognized that entities other than digital computers by and large have little need to engage in a binary decimal conversion process. For example, few of us humans routinely deal with raw binary representations of numbers or other data</span><em>. </em>However,<span class="headertext"> human beings do routinely perform such accounting tasks as those performed by the claimed </span>computing means in<span class="headertext"> </span><em>Every Penny Counts</em>.<span class="headertext"> Thus, unlike the claims at issue in </span><em>Gottschalk</em><span class="headertext">, the claims at issue here would arguably <strong>not</strong> be in practical effect a patent of the algorithm itself. </span></p>
<p><span class="headertext">Admittedly, in a credit card system as large as Bank of America&#8217;s, it may not be cost-effective to have a human perform the claimed elements. Accordingly, the claims at issue may indeed cover most <em>commercially feasible</em> implementations of a process, but that still seems to be a far cry </span><span class="headertext">from </span><span class="headertext"><em>Gottschalk</em>, in which the claims would have completely preempted a mathematical formula.</span></p>
<p><span class="headertext">In the end, maybe the district court reached the right outcome, and maybe it did not. However, the claims at issue seem distinguishable from those of </span><span class="headertext"><em>Gottschalk</em>, and if the district court had not employed this faulty analogy, it is not clear that it could have reached the same outcome.<br />
</span></p>
]]></content:encoded>
			<wfw:commentRss>http://seattlepatents.com/2009/05/bilskis-blank-slate-is-bad-news-for-every-penny-counts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New limits on divisional applications from European Patent Office</title>
		<link>http://seattlepatents.com/2009/03/new-limits-on-divisional-applications-from-european-patent-office/</link>
		<comments>http://seattlepatents.com/2009/03/new-limits-on-divisional-applications-from-european-patent-office/#comments</comments>
		<pubDate>Sat, 28 Mar 2009 00:39:20 +0000</pubDate>
		<dc:creator>Chad Kirby</dc:creator>
				<category><![CDATA[International]]></category>
		<category><![CDATA[Patent Prosecution]]></category>
		<category><![CDATA[EPO]]></category>
		<category><![CDATA[patent]]></category>

		<guid isPermaLink="false">http://seattlepatents.com/?p=124</guid>
		<description><![CDATA[This week, over protests from European patent practitioners, the EPO decided to add new limitations on when a divisional application may be filed, beginning next April. Of late, the EPO has become increasingly hostile towards what it regards as "abusive" filing of divisionals—practices such as repeatedly re-filing a divisional patent applications to avoid the effects of a rejection, or filing a divisional before an allowed application issues to pursue broader claims than were allowed.

]]></description>
			<content:encoded><![CDATA[<p>This week, over protests from European patent practitioners, the EPO decided to add new limitations on when a divisional application may be filed, beginning next April. Of late, the EPO has become increasingly hostile towards what it regards as &#8220;abusive&#8221; filing of divisionals—practices such as repeatedly re-filing a divisional patent applications to avoid the effects of a rejection, or filing a divisional before an allowed application issues to pursue broader claims than were allowed.</p>
<p><span id="more-124"></span>To address these &#8220;abusive&#8221; practices, as of April 2010, the EPO will require that a divisional application be filed either:</p>
<ul>
<li>within two years of the <strong>first communication</strong> from the Examining Division regarding the <strong>earliest</strong> application in a family; or</li>
<li>within two years of any objection from the Examining Division regarding a lack of unity of invention for any application within the family.</li>
</ul>
<p>In Europe, a divisional application is the only allowed form of &#8220;continuing&#8221; application,  so the new rules will force patent applicants to identify discrete patentable inventions disclosed within their specification somewhat earlier than the current rules allow. The new rules may also make it difficult for patent applicants to spread out prosecution costs in Europe.</p>
]]></content:encoded>
			<wfw:commentRss>http://seattlepatents.com/2009/03/new-limits-on-divisional-applications-from-european-patent-office/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Trade Secret Review</title>
		<link>http://seattlepatents.com/2009/03/trade-secret-review/</link>
		<comments>http://seattlepatents.com/2009/03/trade-secret-review/#comments</comments>
		<pubDate>Wed, 25 Mar 2009 00:15:55 +0000</pubDate>
		<dc:creator>Thomas Loop</dc:creator>
				<category><![CDATA[Trade Secret]]></category>
		<category><![CDATA[miappropriation]]></category>
		<category><![CDATA[secret]]></category>

		<guid isPermaLink="false">http://seattlepatents.com/?p=117</guid>
		<description><![CDATA[Trade secret law is concerned with the protection of technological and commercial information not generally known in the trade against unauthorized commercial use by others. The policy basis for trade secret protection is the desire to encourage research and development by providing protection for the originator of business information, and also to maintain proper standards of business ethics. See Kewanee Oil Company v. Bicron Corp., 416 U.S. 470 (190). The trade secret owner is not granted exclusivity to the information, but rather is only protected against improper acquisition and/or use of the information. As a result, others are free to discover a trade secret by any fair means.]]></description>
			<content:encoded><![CDATA[<p>Trade secret law is concerned with the protection of technological and commercial information not generally known in the trade against unauthorized commercial use by others. The policy basis for trade secret protection is the desire to encourage research and development by providing protection for the originator of business information, and also to maintain proper standards of business ethics. <em>See Kewanee Oil Company v. Bicron Corp.</em>, 416 U.S. 470 (190). The trade secret owner is not granted exclusivity to the information, but rather is only protected against improper acquisition and/or use of the information. As a result, others are free to discover a trade secret by any fair means.</p>
<p><span id="more-117"></span></p>
<p><strong>I. LEGAL BASIS</strong></p>
<p><strong></strong></p>
<p>Until relatively recently, trade secret protection had been based on common law principles; namely, trade secrets had been protected under contract, quasi-contract, and property theories. Protection of trade secrets under contract theories includes instances in which there existed an express contract concerning non-disclosure or use of a trade secret, or there existed a confidential relationship giving rise to a duty no to disclose or use the trade secret – such as an employer-employee relationship. The quasi-contract basis of trade secret protection includes avoidance of unjust enrichment from trade secret misappropriation. And the property theory, the “property” ceases to exist upon disclosure of the trade secret.</p>
<p>Perhaps the most widely used common law definition of a trade secret was found in the Restatement of Torts, § 757 comment b (1939):</p>
<p>[A trade secret is] [a]ny formula, pattern, device or compilation of information which is used in one’s business, and which gives him an opportunity to obtain an advantage over competitors who do not know or use it.</p>
<p>The Restatement also lists six factors to be considered in determining the existence of a trade secret:</p>
<ol>
<li>the extent to which the information is known outside the business;</li>
<li>the extent to which it is known by employees and other involved in his business;</li>
<li>the extent of measure taken by him to guard the secrecy of the information;</li>
<li>the value of the information to him and to his competitors;</li>
<li>the amount of efforts or money expended by him in developing the information; and</li>
<li>the ease or difficulty with which the information could be properly acquired or duplicated by others.</li>
</ol>
<p>These factors are “[t]he most-cited listing of the objective criteria for determining the existence of a trade secret.” M. Jager, Trade Secrets Law § 5.05 (1995). Note that this definition is still widely used in spite of he decision of the authors of the Restatement (Second) of Torts (1979) to omit any discussion of trade secrets.</p>
<p>In recent years, trade secret law has become largely statutory. The Uniform Trade Secret Act (UTSA) has now been adopted (sometimes with modifications) in 42 states. M. Jager, <em>supra</em>, at § 3.05 (1996). Washington adopted the UTSA as of January 1, 1982. RCW 19.108 <em>et seq.</em></p>
<p>The UTSA defines a trade secret as information, including a formula, pattern, compilation, program, device, method, technique, or process, that: (i) derives independent economic value, actual or potential, from not being generally known to, and not being readily ascertainable by proper means by, other persons who can obtain economic value from its disclosure or use; and (ii) is the subject of efforts that are reasonable under the circumstances to maintain its secrecy.</p>
<p><strong>II. ELEMENTS OF A TRADE SECRET</strong></p>
<p>Under both the old Restatement of Torts and the current statutory definition, to establish the existence of a trade secret one much show that the information or item alleged to be a trade secret is: (1) of an appropriate subject matter to be protected as a trade secret; (2) not a matter of common knowledge in the trade and not readily ascertainable by proper means; (3) of value; and (4) the object of reasonable precautions taken under the circumstances to maintain secrecy.</p>
<p><strong>1. Protectable Subject Matter</strong></p>
<p>Under the common law and the Washington statutory definition, almost any knowledge or information used in conjunction with one’s business may be held as a trade secret. Specific examples include:</p>
<p>1. Formulas for chemicals, drugs, cosmetics, foods, et cetera.</p>
<p>2. Industrial Processes. <em>E.I. duPont de Nemours &amp; Company, Inc. v. Christopher</em>, 431 F.2d 1012 (5<sup>th</sup> Cir. 1970).</p>
<p>3. Know-how, <em>i.e.</em>, technical information relating to the practical application of patented or unpatented inventions.</p>
<p>4. Blueprints, such as for a building or machinery.</p>
<p>5. Computer software, to the extent it cannot be reverse engineered.</p>
<p>6. Sources of supply, pricing information, identity of vendors or suppliers, and customer lists.</p>
<p>In addition and contrary to common belief, trade secrets are not limited to technical items, know-how and related matters, but include a wide variety of business information (<em>i.e.</em>, employee benefit information and financial statements and projections). Under the Washington statute, a trade secret can include information that has commercial value from a negative standpoint (<em>e.g.</em>, knowledge that a particular process cannot be used to produce a certain product).</p>
<p><strong>2. Not Generally Known or Readily Ascertainable</strong></p>
<p>Trade secret protection is available only for information not generally known (<em>i.e.</em>, secret information), and is not available for information which is common knowledge. And in addition to not being generally known, a trade secret must not be readily ascertainable by proper means. The comments to the UTSA indicates that information is “readily ascertainable” if it’s available in trade journals, reference books or other published materials.</p>
<p>Note that secrecy is not lost if the possessor of the information disclosed it to another in confidence or under an express or implied obligation not to disclose it. Accordingly, information can be disclosed, for example, to prospective purchasers of the trade secret, or to employees involved in a manufacturing process which utilizes the trade secret, without destroying the trade secret. These types of disclosures comport with commercial reality.</p>
<p><strong>3. Independent Economic Value</strong></p>
<p>To be protectable, the trade secret information must provide a competitive advantage over others who are unaware of the secret information. Earlier decisions required that for a trade secret to have value, the information must be regularly used in the proponent’s business. This requirement, which could post a problem during research and development, has been rejected by the UTSA.</p>
<p><strong>4. Reasonable Efforts to Maintain Secrecy</strong></p>
<p>The requirement that the possessor of a trade secret must make reasonable efforts to maintain secrecy is based on the rationale that if the possessor does not treat the information as a trade secret, then the law also should not. The degree of secrecy required is that which is reasonable under the circumstances and may include:</p>
<p>1. advising employees of the existence of trade secrets;</p>
<p>2. limiting access to the trade secret on a “need-to-know-basis”;</p>
<p>3. controlling plant access;</p>
<p>4. central control of blueprints and drawings;</p>
<p>5. use of security guards; and</p>
<p>6. locked storage of laboratory notebooks.</p>
<p><strong>III. TRADE SECRET MISAPPROPRIATION</strong></p>
<p>Under the common law, liability for trade secret misappropriation required acquisition by another by improper conduct or unfair means together with the use or disclosure by such person to the trade secret owner’s detriment. Under the UTSA, the definition of misappropriation is much broader; it can include simple acquisition of a trade secret by a person who knows or has reason to know that the trade secret was acquired by improper means – no subsequent or impending use of the trade secret is required.</p>
<p>The UTSA specifies that “improper means” includes theft, bribery, misrepresentation, breach or inducement of a breach of a duty to maintain secrecy, or espionage through electronic or other means. Again, one of the broadly stated policies behind trade secret law is the maintenance of standards of commercial ethics. Thus, improper means could include otherwise lawful conduct which is improper under the circumstances; <em>e.g.</em>, an airplane overflight used as aerial reconnaissance to determine the competitor’s plant layout during construction of the plant. <em>E.I. duPont de Nemours &amp; Co., Inc. v. Christopher</em>, 431 F.2d 1012 (CA5, 1970).</p>
<p><strong>IV. RELIEF AVAILABLE</strong></p>
<p><strong></strong></p>
<p><strong>1. Injunctive Relief</strong></p>
<p>Once it has been established that a trade secret has been misappropriated, injunctions to enjoin further use of a trade secret generally have been issued by the courts. This remedy is expressly provided under the UTSA. Under the common law, there were several different views concerning the duration of prohibitory injunction. Under one doctrine, the defendant could be permanently enjoined from using the misappropriated trade secret, even if it later became public knowledge. <em>Allen-Qualia Co. v. Shellmar Products Co.</em>, 87 F.2d 104 (7<sup>th</sup> Cir. 1936). This view was based on the theory that the defendant by her own inequitable conduct had permanently deprived herself of the right to employ the trade secret. Under a second doctrine, the injunction is terminated once the information becomes available to the public. <em>Conmar Products Corp. v. Universal Slide Fastener Co.</em>, 172 F.2d 150 (2d. Cir. 1949). And under a third doctrine, the duration of the injunction is limited to the period of time it would have taken the defendant either by reverse engineering or by independent development to develop its product or process without the use of the trade secret. <em>K-2 Ski Company v. Head Ski Co., Inc.</em>, 506 F.2d 471 (9<sup>th</sup> Cir. 1974).</p>
<p>UTSA adopts the <em>K-2</em> rule; injunctive relief terminates once a trade secret ceases to exist – however, the injunction may be continued for an additional length of time to eliminate any commercial advantage derived from the misappropriation. As such, the maximum duration of an injunction is the period of time it would have taken the defendant to lawfully discover the trade secret either through independent development or reverse engineering.</p>
<p><strong>2. Damages and Attorney’s Fees</strong></p>
<p>The UTSA provides that in addition to or in lieu of injunctive relief, damages of the actual loss caused by the misappropriation may be awarded. In addition to damages, the complainant may recover the unjust enrichment resulting from the misappropriation, provided that such amount is not taken into account in computing the actual loss. If willful or malicious misappropriation is found, the court can award exemplary damages in an amount not to exceed twice actual damages, together with recovery for unjust enrichment. In such circumstance, the court may also award attorney’s fees. The comments to the UTSA indicate that the patent laws are followed in determining whether attorney’s fees should be provided.</p>
<p><strong>3. Statue of Limitations</strong></p>
<p>The UTSA specifies that an action for misappropriation must be brought within three years after the misappropriation is discovered or reasonably should have been discovered.</p>
]]></content:encoded>
			<wfw:commentRss>http://seattlepatents.com/2009/03/trade-secret-review/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>One of the hidden (literally!) values of method claims</title>
		<link>http://seattlepatents.com/2009/03/method-claims-marking-requirements/</link>
		<comments>http://seattlepatents.com/2009/03/method-claims-marking-requirements/#comments</comments>
		<pubDate>Thu, 19 Mar 2009 02:00:49 +0000</pubDate>
		<dc:creator>Michael Rice</dc:creator>
				<category><![CDATA[Recent Cases]]></category>
		<category><![CDATA[35 U.S.C. § 287]]></category>
		<category><![CDATA[enforcement]]></category>
		<category><![CDATA[federal circuit]]></category>

		<guid isPermaLink="false">http://seattlepatents.com/?p=105</guid>
		<description><![CDATA[Yesterday, the Federal Circuit reminded us of another reason why method claims are so valuable. In Crown Packaging Technology, Inc. v. Rexam Beverage Can Co., No. 08-1284 (Fed. Cir. Mar. 17. 2009), the court held, among other things, that a method claim does not require markings to enforce the patent in litigation.]]></description>
			<content:encoded><![CDATA[<p>Yesterday, the <a href="http://www.cafc.uscourts.gov/">Federal Circuit</a> reminded us of another reason why method claims can be so valuable. In <a href="http://www.cafc.uscourts.gov/opinions/08-1284.pdf"><em>Crown Packaging Technology, Inc. v. Rexam Beverage Can Co.</em></a>, No. 08-1284 (Fed. Cir. Mar. 17. 2009), the court held, among other things, that a method claim does not require markings to enforce the patent in litigation.</p>
<p><span id="more-105"></span>In <em>Crown Packaging</em>, the plaintiff (the patent holder), in brief, did not mark its products with a patent number as required by <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/appxl_35_U_S_C_287.htm">35 U.S.C. § 287(a)</a> for most patented products. You&#8217;ve seen these markings on, for example, a Starbucks coffee sleeve (Pat. Nos. <a href="http://www.google.com/patents?id=e2olAAAAEBAJ&amp;dq=5,205,473">5,205,473</a> and <a href="http://www.google.com/patents?id=62wUAAAAEBAJ&amp;dq=6,863,644">6,863,644</a>, to be precise).</p>
<p>Nevertheless, the court, consistent with precedent, allowed the patent holder to enforce its method claims. Method claims are used extensively in patents on software products, so this is good news for many of our clients.</p>
<p>For more about the decision, I&#8217;d refer you to Patently-O&#8217;s post on the case <a href="http://www.patentlyo.com/patent/2009/03/improper-summary-judgment-on-doctrine-of-equivalents-marking-products-that-perform-method-claims.html">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://seattlepatents.com/2009/03/method-claims-marking-requirements/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What it looks like to win a patent infringement case</title>
		<link>http://seattlepatents.com/2009/03/what-it-looks-like-to-win-a-patent-infringement-case/</link>
		<comments>http://seattlepatents.com/2009/03/what-it-looks-like-to-win-a-patent-infringement-case/#comments</comments>
		<pubDate>Thu, 12 Mar 2009 18:44:43 +0000</pubDate>
		<dc:creator>Michael Rice</dc:creator>
				<category><![CDATA[Litigation]]></category>

		<guid isPermaLink="false">http://seattlepatents.com/?p=93</guid>
		<description><![CDATA[This is a Portland case, but I thought you'd find it interesting anyway. The plaintiffs, a Portland chain maker called Blount, Inc., sued a handful of defendants for patent infringement. The jury returned a $2m verdict a few days ago, so I thought I'd show you what $2m looks like on a special verdict form.]]></description>
			<content:encoded><![CDATA[<p>This is a Portland case, but I thought you&#8217;d find it interesting anyway. The plaintiffs, a Portland chain maker called Blount, Inc., sued a handful of defendants for patent infringement. The jury returned a $2m verdict a few days ago, so I thought I&#8217;d show you what $2m looks like on a special verdict form.</p>
<p><span id="more-93"></span>Oftentimes, the litigants will ask for a &#8220;special verdict.&#8221; This requires the jury to answer specific questions to determine exactly what their findings of fact were. That is to say, the jury doesn&#8217;t just say &#8220;you win&#8221; or &#8220;you lose,&#8221; they tell you why. I uploaded it for your review.</p>
<p>What I found particularly interesting is what the jury determined about the level of &#8220;ordinary skill in the art.&#8221; This was a factual determination they had to make to help determine whether the chain was legally obvious under <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/appxl_35_U_S_C_103.htm">35 U.S.C. 103</a>. The jury rejected either the plaintiff&#8217;s or defendant&#8217;s position on this point, and instead it looks like they took both! They said:</p>
<blockquote><p>A minimum of three years of technical engineering experience in the design and use of of outdoor power equipment; or a technical education in mechanical engineering and one year of experience in the design of outdoor power equipment and use.</p></blockquote>
<p>What you&#8217;ll likely find more interesting, however, is the bottom line. Notice the plaintiffs are recovering for both royalties and price erosion. Here it is:</p>
<p style="text-align: center;"><img class="size-full wp-image-94 aligncenter" title="Jury's verdict form in Blount" src="http://seattlepatents.com/wp-content/uploads/2009/03/blount-sv-damages.jpg" alt="Jury's verdict form in Blount" width="372" height="274" /></p>
<p>All in all, it looks like the litigants had a thoughtful jury. Here&#8217;s the full form:<br />
<a style="margin: 12px auto 6px auto; font-family: Helvetica,Arial,Sans-serif; font-style: normal; font-variant: normal; font-weight: normal; font-size: 14px; line-height: normal; font-size-adjust: none; font-stretch: normal; -x-system-font: none; display: block; text-decoration: underline;" title="View Blount Verdict Form on Scribd" href="http://www.scribd.com/doc/13180090/Blount-Verdict-Form">Blount Verdict Form</a> <object width="100%" height="500" data="http://d.scribd.com/ScribdViewer.swf?document_id=13180090&amp;access_key=key-1q7hhf51ji4vj4ezqtxb&amp;page=1&amp;version=1&amp;viewMode=" type="application/x-shockwave-flash"><param name="id" value="doc_720578488161937" /><param name="name" value="doc_720578488161937" /><param name="align" value="middle" /><param name="quality" value="high" /><param name="play" value="true" /><param name="loop" value="true" /><param name="scale" value="showall" /><param name="wmode" value="opaque" /><param name="devicefont" value="false" /><param name="bgcolor" value="#ffffff" /><param name="menu" value="true" /><param name="allowFullScreen" value="true" /><param name="allowScriptAccess" value="always" /><param name="src" value="http://d.scribd.com/ScribdViewer.swf?document_id=13180090&amp;access_key=key-1q7hhf51ji4vj4ezqtxb&amp;page=1&amp;version=1&amp;viewMode=" /><param name="allowfullscreen" value="true" /></object></p>
<div style="margin: 6px auto 3px auto; font-family: Helvetica,Arial,Sans-serif; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal; -x-system-font: none; display: block;"><a style="text-decoration: underline;" href="http://www.scribd.com/upload">Publish at Scribd</a> or <a style="text-decoration: underline;" href="http://www.scribd.com/browse">explore</a> others:            <a href="http://www.scribd.com/browse/Spreadsheets/Politics-Government?style=text-decoration%3A+underline%3B">Politics &amp; Governmen</a> <a style="text-decoration: underline;" href="http://www.scribd.com/tag/form">form</a> <a style="text-decoration: underline;" href="http://www.scribd.com/tag/tax">tax</a></div>
]]></content:encoded>
			<wfw:commentRss>http://seattlepatents.com/2009/03/what-it-looks-like-to-win-a-patent-infringement-case/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>The geeks were right…</title>
		<link>http://seattlepatents.com/2009/03/the-geeks-were-right/</link>
		<comments>http://seattlepatents.com/2009/03/the-geeks-were-right/#comments</comments>
		<pubDate>Thu, 05 Mar 2009 21:36:11 +0000</pubDate>
		<dc:creator>Michael Rice</dc:creator>
				<category><![CDATA[Portfolio Management]]></category>

		<guid isPermaLink="false">http://seattlepatents.com/?p=78</guid>
		<description><![CDATA[Yesterday, I was looking at an old InterTrust patent application. It was a continuation of an application filed back in Silicon Valley's dot-com boom times. InterTrust had then, like a lot of our clients do today, very ambitious goals. In this case, those goals didn’t materialize, and InterTrust morphed in to (what I call) a pure innovation company. And it still became very successful because of the value of its intellectual property.]]></description>
			<content:encoded><![CDATA[<h2>&#8230;so were their lawyers</h2>
<p>Yesterday, I was looking at an old <a href="http://www.intertrust.com">InterTrust</a> patent application. It was a continuation of an application filed back in Silicon Valley&#8217;s dot-com boom times. InterTrust had then, like a lot of our clients do today, very ambitious goals. In this case, those goals didn’t materialize, and InterTrust <a href="http://query.nytimes.com/gst/fullpage.html?res=9401E4D81231F935A15753C1A9659C8B63">morphed in to (what I call) a pure innovation company</a>. And it still became very successful because of the value of its intellectual property.<span id="more-78"></span></p>
<p>The reason InterTrust could pull this off was that they invested wisely in their intellectual property portfolio, and they took care to protect it. In other words, the geeks did great work, and so did their lawyers.</p>
<p>That memory fact got me thinking. Most of our clients are high-tech companies. And high-tech companies do at least two things simultaneously: (1) they are building markets, customers, and businesses; and (2) they are building an intellectual property portfolio. Even though many of them consider them one and the same, they are really two independently valuable things.</p>
<p>Unfortunately, as the current economic times will attest (not unlike the dot com implosion that continues to inform my thinking), markets come and go—that’s just a part of the creative destruction that is capitalism. Your innovation, however, might just outlast all of this.</p>
<p>You may not, or may not, agree with InterTrust&#8217;s new business model, but as a high-tech innovator, surely you must agree that your work has strong value independent of it’s current economic incarnation. In other words, think of the business the IP&#8217;s current shell.</p>
<p>Recognizing that distinction, the independent value, and helping you make the most of it is the role of your intellectual property counsel.</p>
]]></content:encoded>
			<wfw:commentRss>http://seattlepatents.com/2009/03/the-geeks-were-right/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
