<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://groups.rkmc.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>APaTS : Invalidity</title><link>http://groups.rkmc.com/apats/archive/tags/Invalidity/default.aspx</link><description>Tags: Invalidity</description><dc:language>en</dc:language><generator>CommunityServer 2007 (Build: 20416.853)</generator><item><title>Yours, Mine and Ours</title><link>http://groups.rkmc.com/apats/archive/2009/06/10/yours-mine-and-ours.aspx</link><pubDate>Wed, 10 Jun 2009 18:29:00 GMT</pubDate><guid isPermaLink="false">d33a4eb4-9582-4bcc-a5fc-ab6291262ba2:62</guid><dc:creator>admin</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Sometimes, the merger of two companies requires a sorting of the Cinderellas from the ugly stepsisters when it comes to pre-existing contractual relationships. &amp;nbsp;The decision in &lt;b&gt;&lt;i&gt;Epistar Corp. v. International Trade Commission&lt;/i&gt;&lt;/b&gt; involves one such blended family tale.&amp;nbsp; There, after a merger, the alleged infringer found itself with separate licensing agreements that both prohibited and allowed invalidity challenges in future litigation with the same patent holder. &amp;nbsp;The patent holder claimed the agreement that precluded invalidity challenges governed and the International Trade Commission agreed.&amp;nbsp; The Federal Circuit reversed and remanded, finding that the merger, in and of itself, was not enough to prevent the invalidity defense from coming to the dance. &lt;/p&gt;
&lt;p&gt;The patent at issue in &lt;b&gt;&lt;i&gt;Epistar &lt;/i&gt;&lt;/b&gt;covered technology for LEDs. &amp;nbsp;Both alleged infringer Epistar and the company with which it merged (UEC) had entered into settlement agreements with the patent holder in prior infringement actions. &amp;nbsp;Epistar agreed to pay a licensing fee for certain products, but retained the right to challenge the patent if the patent holder sued Epistar in the future.&amp;nbsp;&amp;nbsp;In its license, UEC agreed (prior to the merger) that neither it, nor its successors, could&amp;nbsp;challenge the validity of the patent at issue.&lt;/p&gt;
&lt;p&gt;The International Trade Commission ruled that the agreement UEC had with the patent holder precluded Epistar from contesting the validity of the patent at issue with respect to&amp;nbsp;any UEC or Epistar product.&amp;nbsp; However, the Commission failed to acknowledge the separate agreement Epistar had with the patent holder which preserved Epistar&amp;#39;s right to challenge patent validity with respect to Epistar&amp;#39;s products.&amp;nbsp; The Commission later explained that though it had failed to take into account the Epistar license, Epistar could not challenge the decision because it became final when the Commission declined review.&lt;/p&gt;
&lt;p&gt;On appeal, the Federal Circuit overturned the Commission&amp;#39;s final determination&amp;nbsp;and found that the agreement Epistar had with the patent holder governed its right to contest the validity of the patent with respect to its products. &amp;nbsp;The patent holder could not use the UEC agreement to gain any further preclusion because that agreement only covered UEC product lines. &amp;nbsp;Because Epistar&amp;#39;s separate agreement clearly preserved Epistar&amp;#39;s right to contest the validity of the patent in other contexts, the patent holder could only limit Epistar from asserting patent invalidity as to the product lines it acquired from UEC.&amp;nbsp; It could not use the UEC preclusion agreement to reach products that agreement didn&amp;#39;t cover. &amp;nbsp;In other words, the patent holder could only preclude Epistar to the extent which UEC was formerly limited.&lt;/p&gt;
&lt;p&gt;&lt;b&gt;&lt;i&gt;Epistar&amp;#39;s &lt;/i&gt;&lt;/b&gt;moral? &amp;nbsp;You can&amp;#39;t use a merger to cram one license agreement&amp;#39;s claim preclusions into a separate agreement in order to encompass a successor&amp;#39;s products. &amp;nbsp;Instead, both sides to a license agreement (even one negotiated in the throes of litigation) need to remember that corporate mergers, marriages, dissolutions and divorces are a fact of modern life and to plan accordingly.&amp;nbsp; Then, one hopes, patent holders and the alleged infringers who have become their licensees will have an agreement that fits so that both can live happily ever after.&lt;/p&gt;&lt;img src="http://groups.rkmc.com/aggbug.aspx?PostID=62" width="1" height="1"&gt;</description><category domain="http://groups.rkmc.com/apats/archive/tags/Licensing/default.aspx">Licensing</category><category domain="http://groups.rkmc.com/apats/archive/tags/Invalidity/default.aspx">Invalidity</category><category domain="http://groups.rkmc.com/apats/archive/tags/Merger/default.aspx">Merger</category><category domain="http://groups.rkmc.com/apats/archive/tags/Settlement+Agreement/default.aspx">Settlement Agreement</category><category domain="http://groups.rkmc.com/apats/archive/tags/Epistar/default.aspx">Epistar</category></item><item><title>Tilt</title><link>http://groups.rkmc.com/apats/archive/2008/10/15/tilt.aspx</link><pubDate>Wed, 15 Oct 2008 01:00:00 GMT</pubDate><guid isPermaLink="false">d33a4eb4-9582-4bcc-a5fc-ab6291262ba2:43</guid><dc:creator>admin</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;In &lt;b&gt;&lt;i&gt;
Aristocrat Technologies, Inc. v. International Game Technology&lt;/i&gt;&lt;/b&gt;, 
the accused infringer thought they&amp;#39;d hit the jackpot by convincing the 
district court to hold a patent invalid due to &amp;quot;Improper Revival&amp;quot; 
during patent prosecution.&amp;nbsp; The district court paid out on the 
defense and granted summary judgment on the defendant&amp;#39;s behalf.&amp;nbsp; 
On appeal, the Federal Circuit invoked house rules and held that procedural 
irregularities in the prosecution of a patent just isn&amp;#39;t in the hopper 
of defenses available under § 282 of the patent code--and took the 
win away.
&lt;/p&gt;&lt;p&gt;The 
patents at issue in &lt;b&gt;&lt;i&gt;Aristocrat &lt;/i&gt;&lt;/b&gt;
covered electronic slot machines technologies. During prosecution, the 
patent holder missed a payment by one day and the PTO mailed a notice 
of abandonment.&amp;nbsp; The patent holder filed a petition to revive the 
application, claiming that the delay was &amp;quot;unintentional.&amp;quot;&amp;nbsp; 
The PTO granted the petition, the first patent issued, and then a related 
second patent subsequently issued.&amp;nbsp; &lt;/p&gt;
&lt;p&gt;The 
patent holder sued for infringement of both patents.&amp;nbsp; The accused 
infringer argued that the patent holder had failed to show an &amp;quot;unavoidable 
delay&amp;quot; (required by the regulations) when it revived its patent.&amp;nbsp; 
It claimed this failure meant the patent application had been improperly 
revived and that the application should be deemed abandoned, thereby 
invalidating the first patent and anticipating the second one.&amp;nbsp; 
The district court agreed and entered its summary judgment ruling.&lt;/p&gt;
&lt;p&gt;Reversing, 
the Federal Circuit held that an &amp;quot;Improper Revival&amp;quot; defense 
wasn&amp;#39;t in the cards.&amp;nbsp; The &lt;b&gt;&lt;i&gt;Aristocrat &lt;/i&gt;&lt;/b&gt;
court said that prosecution defects aren&amp;#39;t available as an invalidity 
defense because such defenses are expressly limited to novelty, utility 
and non-obviousness, the &amp;quot;conditions of&amp;nbsp; patentability.&amp;quot;&amp;nbsp; 
Nor could the defendants avail themselves of § 282&amp;#39;s catch-all provision.&amp;nbsp; 
The court ruled that the provision--which&amp;nbsp; covers &amp;quot;any other 
fact or act made a defense by this title&amp;quot;--applied only to an action &lt;i&gt;
made&lt;/i&gt; a defense by the title, and nothing in the code expressly recognized 
Improper Revival of an abandoned application as a defense.&amp;nbsp; &lt;/p&gt;
&lt;p&gt;The 
court emphasized that its ruling was not intended to excuse conduct 
rising to the level of prosecution laches or inequitable conduct, particularly 
when the conduct alleged includes any affirmative misrepresentation 
of material fact coupled with an intent to deceive.&amp;nbsp; Interestingly, 
the Federal Circuit expressly avoided the question of whether an &amp;quot;unintentional&amp;quot; 
delay amounts to an &amp;quot;unavoidable&amp;quot; delay under the code.&amp;nbsp; &lt;/p&gt;
&lt;p&gt;For 
the &lt;b&gt;&lt;i&gt;Aristocrat&lt;/i&gt;&lt;/b&gt; court, the defendant&amp;#39;s argument turned 
out to be no better than a wooden nickel.&amp;nbsp; The decision shows that 
to have a winning combination, creative requests to extend the law need 
to be grounded on a proper consideration of the entire statutory framework 
and the canons of statutory construction.&amp;nbsp; &lt;b&gt;&lt;i&gt;Aristocrat&lt;/i&gt;&lt;/b&gt; 
also shows the importance of &lt;i&gt;not&lt;/i&gt; gaming the PTO system.&amp;nbsp; 
Here, there was ample evidence that the patent holder&amp;#39;s failure to make 
the timely payment was an honest mistake--not an effort to get around 
procedural rules the Federal Circuit respects.&amp;nbsp; Other facts may 
have edged the court into a consideration of the equities involved--even 
in light of the court&amp;#39;s recent decision in &lt;b&gt;&lt;i&gt;Star Scientific Inc. 
v. R.J. Reynolds Tobacco Co.&lt;/i&gt;&lt;/b&gt;&lt;/p&gt;And 
all patent gamers should take note of what&lt;b&gt;&lt;i&gt; Aristocrat &lt;/i&gt;&lt;/b&gt;
&lt;i&gt;didn&amp;#39;t&lt;/i&gt; decide.&amp;nbsp; Did the patentee&amp;#39;s conduct truly satisfy 
the code?&amp;nbsp; Is something &amp;quot;unintentional&amp;quot; sufficiently 
&amp;quot;unavoidable&amp;quot; to satisfy the Patent&amp;#39;s Office regulatory requirements?&amp;nbsp; 
These questions remain unanswered and a defense of &amp;quot;Improper Revival&amp;quot; 
may be available before the PTO, even if it isn&amp;#39;t in district court.&amp;nbsp; 
This may give new impetus to reexamination proceedings as accused infringers 
may be willing to wager that &amp;quot;Improper Revival&amp;quot; will become 
patent law&amp;#39;s latest one-armed bandit - at least in the right casino. &amp;nbsp;

&lt;img src="http://groups.rkmc.com/aggbug.aspx?PostID=43" width="1" height="1"&gt;</description><category domain="http://groups.rkmc.com/apats/archive/tags/Invalidity/default.aspx">Invalidity</category><category domain="http://groups.rkmc.com/apats/archive/tags/Improper+Revival/default.aspx">Improper Revival</category><category domain="http://groups.rkmc.com/apats/archive/tags/Unavoidable+Delay/default.aspx">Unavoidable Delay</category><category domain="http://groups.rkmc.com/apats/archive/tags/Slot+Machines/default.aspx">Slot Machines</category><category domain="http://groups.rkmc.com/apats/archive/tags/Aristocrat/default.aspx">Aristocrat</category></item><item><title>The Sound of One Patent Clapping</title><link>http://groups.rkmc.com/apats/archive/2008/01/29/the-sound-of-one-patent-clapping.aspx</link><pubDate>Tue, 29 Jan 2008 18:52:00 GMT</pubDate><guid isPermaLink="false">d33a4eb4-9582-4bcc-a5fc-ab6291262ba2:24</guid><dc:creator>admin</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;In &lt;a class="" title="CAFC court opinion (PDF document)" href="http://www.cafc.uscourts.gov/opinions/07-1065.pdf"&gt;&lt;b&gt;&lt;i&gt;SRI Int&amp;#39;l&lt;/i&gt;&lt;/b&gt;&lt;b&gt;&lt;i&gt; v. Internet Security Systems&lt;/i&gt;&lt;/b&gt;&lt;/a&gt;&lt;b&gt;&lt;i&gt;,&lt;/i&gt;&lt;/b&gt; the district court heard what it needed to grant summary judgment of invalidity.&amp;nbsp; The district court found that a paper that had been published more than a year prior to the patent application invalidated the patents under review.&amp;nbsp; The Federal Circuit didn&amp;#39;t chime in. Why? Because in this electronic world what is &amp;quot;publicly accessible&amp;quot; has taken on new and different aspects from our previous hardcopy days. &lt;/p&gt;
&lt;p&gt;The patents at issue involve technology for cyber security and network intrusion detection. Patent holder SRI actively participated in work-shops involving peer review and posted two papers describing details of its inventions to a FTP server more than a year prior to filing its patent application. When SRI brought suit against Internet Security Systems (&amp;quot;ISS&amp;quot;), ISS used the papers as the basis of an invalidity counter claim. ISS argued, and the district court agreed, that each of the two papers were anticipatory prior art which rendered SRI&amp;#39;s patents invalid. &lt;/p&gt;
&lt;p&gt;However, the Federal Circuit found questions of fact regarding the publication of one of the papers-known as the &amp;quot;Live Traffic&amp;quot; paper. Specifically, the question became whether posting the Live Traffic paper to the FTP site met the &amp;quot;public accessibility&amp;quot; requirement under §102 (b). The Federal Circuit noted that public accessibility is determined on a case by case basis. Here, there was no index or catalog to the directory on the FTP site where the paper was located. The court felt that nothing in the file placement or name used to describe the paper would have allowed one skilled in the art to navigate through the directory structure to the specific paper in question and cited the fact that the inventor provided the conference chair with the full FTP address in order for him to access it. Second, the only person outside SRI who knew of the existence of the paper on the FTP server was the conference chair-a fact confirmed by evidence that no one actually accessed the paper during the seven days it was posted to the site.&lt;/p&gt;
&lt;p&gt;In the Federal Circuit&amp;#39;s view, these facts were equivalent to putting up posters at a conference which no one advertises and to which no one goes. Vacating the grant of summary judgment, the Federal Circuit remanded the case with instructions to the district court to conduct a more thorough determination of the factual questions regarding public accessibility of the Live Traffic paper based on additional evidence and the Court&amp;#39;s opinion. &lt;/p&gt;
&lt;p&gt;Judge Moore, dissenting, strongly disagreed. Judge Moore cited evidence that the inventor had directed people to other locations on the FTP site at least seven times and that the site had been referenced by relevant Google user groups more than 70 times. Asserting that the community of interest would have no difficulty navigating through the FTP site&amp;#39;s hierarchies, she concluded that the posting of the Live Traffic to the FTP site was the equivalent of placing a book with an obscure title on the shelf of library with a specific subject matter. Because of the internet, Judge Moore said, anyone, anywhere, could access, download and/or print a copy of the paper during the seven days the paper remained on the site. Enough, according to the dissent, for publication to have occurred. &lt;/p&gt;
&lt;p&gt;SRI illustrates how new methodologies of information dissemination continue to impact inventions and patentability-particularly in emerging industries. Leading edge innovators must balance the credibility (and funding) that often ensues from peer review and approval with the very real risk that disclosures made during that process can impact patent validity. Inventors on the road to a patent application will want to heed the warning inherent in the SRI decision-pay attention to both the timing and methods by which key invention information is transmitted or risk future challenges to patent validity. On the other hand, those facing infringement claims may wish to broaden the scope of their discovery inquiries in order to assess whether a valid patent actually exists by asking to whom, when and just how inventors communicated key invention information. &lt;/p&gt;
&lt;p&gt;With ever-emerging mediums by which information can be transmitted, shared and reviewed, we predict disputes regarding public accessibility to continue. After &lt;b&gt;&lt;i&gt;SRI&lt;/i&gt;&lt;/b&gt; we wonder if emerging technology publications will be like trees falling in the forest - &amp;nbsp;impacting a patent&amp;#39;s validity only if someone is there to see them.&lt;/p&gt;&lt;img src="http://groups.rkmc.com/aggbug.aspx?PostID=24" width="1" height="1"&gt;</description><category domain="http://groups.rkmc.com/apats/archive/tags/Invalidity/default.aspx">Invalidity</category><category domain="http://groups.rkmc.com/apats/archive/tags/Prior+Art/default.aspx">Prior Art</category><category domain="http://groups.rkmc.com/apats/archive/tags/Internet+Security+Systems/default.aspx">Internet Security Systems</category><category domain="http://groups.rkmc.com/apats/archive/tags/Public+Accessibility/default.aspx">Public Accessibility</category><category domain="http://groups.rkmc.com/apats/archive/tags/SRI+Int_2700_l/default.aspx">SRI Int'l</category></item><item><title>Quantity 10; Quality 0</title><link>http://groups.rkmc.com/apats/archive/2007/12/07/quantity-10-quality-0-z4-technologies-inc-v-microsoft-corp.aspx</link><pubDate>Fri, 07 Dec 2007 19:10:00 GMT</pubDate><guid isPermaLink="false">d33a4eb4-9582-4bcc-a5fc-ab6291262ba2:22</guid><dc:creator>admin</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;In &lt;b&gt;&lt;i&gt;z4 Technologies Inc.&lt;/i&gt;&lt;/b&gt;&lt;b&gt;&lt;i&gt; v. Microsoft Corp&lt;/i&gt;&lt;/b&gt;., Microsoft learned that the rules for mud and appellate arguments aren&amp;#39;t always the same-at least not in the Federal Circuit. Apparently, following the old adage that something should stick if enough is flung, Microsoft offered up a bevy of alleged errors, arguments and attacks on appeal in an effort to defeat z4&amp;#39;s $115 million patent infringement verdict. &amp;nbsp;The Federal Circuit acknowledged that many of Microsoft&amp;#39;s arguments were technically correct.&amp;nbsp; Nonetheless, it affirmed the jury&amp;#39;s verdict because it found that all the issues raised by Microsoft were either harmless or not substantial enough to overturn the verdict-holding fast instead, it appears, to that one about the wheat and the chaff.&amp;nbsp; &lt;/p&gt;
&lt;p&gt;At issue was z4&amp;#39;s patent for technology that prevents software piracy and illicit copying and unauthorized use of computer software.&amp;nbsp; Specifically, z4&amp;#39;s invention created a multi-step user authorization scheme requiring users to re-register their software after an initial grace period.&amp;nbsp; Users had the option of re-registering manually or &amp;quot;automatically&amp;quot; using an electronic mode.&amp;nbsp; Both systems enabled the comparison of key information from the initial and secondary registrations in order to verify the registrant as an authorized user. &lt;/p&gt;
&lt;p&gt;z4 sued Microsoft, alleging that the &amp;quot;Product Activation&amp;quot; feature in Microsoft&amp;#39;s &amp;quot;Office&amp;quot; and &amp;quot;Windows&amp;quot; application software infringed its patent. &amp;nbsp;(Similar claims against Autodesk were settled before trial).&amp;nbsp; Microsoft denied infringement and sought to invalidate the relevant patents on grounds of obviousness and anticipation.&amp;nbsp; After a lengthy trial, the jury returned a verdict of willful infringement and awarded damages in the amount of $115 million, which the trial court enhanced by $25 million, along with an award of attorneys&amp;#39; fees.&amp;nbsp; After bringing, and losing, various post-trial motions, Microsoft appealed on a multiplicity of issues.&lt;/p&gt;
&lt;p&gt;The Federal Circuit systematically dismantled each issue Microsoft raised.&amp;nbsp; Microsoft challenged the district court&amp;#39;s construction of the term &amp;quot;user&amp;quot; to mean a person or a computer.&amp;nbsp; Agreeing with Microsoft that under the terms of the patent a &amp;quot;user&amp;quot; couldn&amp;#39;t be a computer, the court went on to reject as &amp;quot;artificial and inconsequential&amp;quot; the non-infringement argument Microsoft had attached to the construction of the term.&amp;nbsp; The patent specifications described a methodology based on computer specific information and other claim language referenced using computer specific information as a basis for the authorization code.&amp;nbsp; Ample evidence, the Federal Circuit found, for a jury to conclude that Microsoft had infringed the patent. &lt;/p&gt;
&lt;p&gt;Next, Microsoft challenged whether there was sufficient evidence for the jury to conclude that its software did not have the requisite &amp;quot;authorization code&amp;quot; because there was not a unique code for each copy of the software; &lt;i&gt;i.e.,&lt;/i&gt; one authorization code could be used with a number of revisions/versions of the software.&amp;nbsp; The court side-stepped the question of whether the claim required the particular one-for-one relationship by characterizing Microsoft&amp;#39;s argument as at best identifying non-infringing modalities, stating:&amp;nbsp; &amp;quot;We are unpersuaded by Microsoft&amp;#39;s assertion that it does not infringe because a single copy of the accused software can be installed on an unlimited number of machines using a single product key.&amp;quot;&lt;/p&gt;
&lt;p&gt;Microsoft&amp;#39;s invalidity defenses faired no better.&amp;nbsp; Microsoft founded its anticipation argument on one of its own products -a Licensing Verification Program (&amp;quot;LVP&amp;quot;) embedded within a 1998 software product called Brazilian Publisher (&amp;quot;BP 98&amp;quot;). &amp;nbsp;Microsoft alleged that the district court erred when it required that BP 98 &amp;quot;stop piracy&amp;quot; in order to qualify as invalidating art for purposes of anticipation. &amp;nbsp;It claimed that BP 98&amp;#39;s intended purpose of &amp;quot;reducing piracy&amp;quot; should have been sufficient. &amp;nbsp;The Federal Circuit agreed--but then went on to find &amp;quot;substantial evidence&amp;quot; from which the jury could find that BP 98 failed even that purpose because the product never actually worked.&amp;nbsp; (Interestingly, the key evidence regarding the problems with BP 98 came from a document which Microsoft was found to have &amp;quot;improperly withheld&amp;quot; until the day before trial started).&lt;/p&gt;
&lt;p&gt;The Federal Circuit also rejected any claim of error based on jury instructions, including an instruction regarding obviousness based on the pre-&lt;i&gt;KSR&lt;/i&gt; &amp;quot;teaching, suggestions or method&amp;quot; (TSM) standard.&amp;nbsp; Microsoft claimed the holding of &lt;i&gt;KSR&lt;/i&gt; required a new trial because of &lt;i&gt;KSR&amp;#39;s &lt;/i&gt;broader considerations regarding obviousness. &amp;nbsp;Not so, the Federal Circuit held.&amp;nbsp; Even under &lt;i&gt;KSR &lt;/i&gt;(and the factors enumerated in &lt;i&gt;Graham v. John Deere&lt;/i&gt;),&lt;i&gt; &lt;/i&gt;a prima facie case of obviousness requires something more than the conclusory testimony of an expert-evidence, the court found, Microsoft had failed to produce or identify.&lt;/p&gt;
&lt;p&gt;Perhaps most painfully, the Federal Circuit refused Microsoft&amp;#39;s request for a reconsideration of foreign sales damages in light of the Supreme Court&amp;#39;s decision in &lt;i&gt;Microsoft&lt;/i&gt;&lt;i&gt; v. AT&amp;amp;T.&lt;/i&gt;&amp;nbsp; Significant questions existed whether Microsoft had properly preserved a §271(f) question for appeal in the district court. &amp;nbsp;However, the Federal Circuit chose to address the issue on substantive grounds.&amp;nbsp; The record showed that the jury did not and could not have relied on §271(f)&amp;#39;s provision in determining damages.&amp;nbsp; Both the complaint and jury instruction were based on the provisions of&amp;nbsp; §271(a), which addresses infringing products made, used or sold in the United States and z4 never argued any §271(f) type infringement.&amp;nbsp; Though Microsoft claimed that the same &amp;quot;golden master&amp;quot; distribution system at issue in &lt;i&gt;AT&amp;amp;T&lt;/i&gt; was in use here, it never offered evidence segregating foreign sales from domestic sales at trial and it never argued against the appropriateness of including foreign sales damages under §271(a).&amp;nbsp; Without such evidence, there was no properly argued or preserved foreign sales issue.&lt;/p&gt;
&lt;p&gt;Admittedly, one would expect a litigant faced with an adverse verdict in the amount of $115 million to marshal an aggressive, all encompassing appeal.&amp;nbsp; Nevertheless, it is clear that in its efforts to scour the record for every conceivable error, Microsoft based its arguments more on formalities and linguistic technicalities than on the substance of the technology at issue.&amp;nbsp; In its effort to be comprehensive, Microsoft appears to have ignored the fact that appellate courts - like juries - respond to themes and can and will focus upon the essentials of the patent over its less relevant technicalities. &lt;/p&gt;
&lt;p&gt;Our take away?&amp;nbsp; Only an idiom would lose the forest for the trees.&lt;/p&gt;&lt;img src="http://groups.rkmc.com/aggbug.aspx?PostID=22" width="1" height="1"&gt;</description><category domain="http://groups.rkmc.com/apats/archive/tags/Microsoft/default.aspx">Microsoft</category><category domain="http://groups.rkmc.com/apats/archive/tags/Invalidity/default.aspx">Invalidity</category><category domain="http://groups.rkmc.com/apats/archive/tags/KSR/default.aspx">KSR</category><category domain="http://groups.rkmc.com/apats/archive/tags/Software/default.aspx">Software</category><category domain="http://groups.rkmc.com/apats/archive/tags/Willful+infringement/default.aspx">Willful infringement</category><category domain="http://groups.rkmc.com/apats/archive/tags/z4+Technologies+Inc.+v.+Microsoft+Corp_2E00_/default.aspx">z4 Technologies Inc. v. Microsoft Corp.</category><category domain="http://groups.rkmc.com/apats/archive/tags/Security/default.aspx">Security</category><category domain="http://groups.rkmc.com/apats/archive/tags/Claim+of+Error/default.aspx">Claim of Error</category></item><item><title>Beeeep Beeeep Beeeep</title><link>http://groups.rkmc.com/apats/archive/2007/08/23/beeeep-beeeep-beeeep.aspx</link><pubDate>Thu, 23 Aug 2007 15:07:00 GMT</pubDate><guid isPermaLink="false">d33a4eb4-9582-4bcc-a5fc-ab6291262ba2:17</guid><dc:creator>admin</dc:creator><slash:comments>0</slash:comments><description>&lt;em /&gt;Benitec Australia, Ltd. v. Nucleonics, Inc.&lt;/em&gt;...(&lt;a href="http://groups.rkmc.com/apats/archive/2007/08/23/beeeep-beeeep-beeeep.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://groups.rkmc.com/aggbug.aspx?PostID=17" width="1" height="1"&gt;</description><category domain="http://groups.rkmc.com/apats/archive/tags/Declaratory+Judgment/default.aspx">Declaratory Judgment</category><category domain="http://groups.rkmc.com/apats/archive/tags/MedImmune/default.aspx">MedImmune</category><category domain="http://groups.rkmc.com/apats/archive/tags/Covenant+Not+to+Sue/default.aspx">Covenant Not to Sue</category><category domain="http://groups.rkmc.com/apats/archive/tags/Invalidity/default.aspx">Invalidity</category><category domain="http://groups.rkmc.com/apats/archive/tags/Infringement/default.aspx">Infringement</category><category domain="http://groups.rkmc.com/apats/archive/tags/Biotechnology/default.aspx">Biotechnology</category><category domain="http://groups.rkmc.com/apats/archive/tags/Super+Sack/default.aspx">Super Sack</category><category domain="http://groups.rkmc.com/apats/archive/tags/Nucleonics/default.aspx">Nucleonics</category><category domain="http://groups.rkmc.com/apats/archive/tags/Benitec/default.aspx">Benitec</category></item><item><title>How Sweet Is It?</title><link>http://groups.rkmc.com/apats/archive/2007/08/03/how-sweet-is-it.aspx</link><pubDate>Fri, 03 Aug 2007 18:08:00 GMT</pubDate><guid isPermaLink="false">d33a4eb4-9582-4bcc-a5fc-ab6291262ba2:16</guid><dc:creator>admin</dc:creator><slash:comments>0</slash:comments><description>&lt;em /&gt;Takeda Chemical Ind., Ltd. v Alphapharm Pty., Ltd.&lt;/em&gt;...(&lt;a href="http://groups.rkmc.com/apats/archive/2007/08/03/how-sweet-is-it.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://groups.rkmc.com/aggbug.aspx?PostID=16" width="1" height="1"&gt;</description><category domain="http://groups.rkmc.com/apats/archive/tags/Invalidity/default.aspx">Invalidity</category><category domain="http://groups.rkmc.com/apats/archive/tags/KSR/default.aspx">KSR</category><category domain="http://groups.rkmc.com/apats/archive/tags/Obviousness/default.aspx">Obviousness</category><category domain="http://groups.rkmc.com/apats/archive/tags/Takeda/default.aspx">Takeda</category><category domain="http://groups.rkmc.com/apats/archive/tags/TSM+Test/default.aspx">TSM Test</category><category domain="http://groups.rkmc.com/apats/archive/tags/Chemistry/default.aspx">Chemistry</category><category domain="http://groups.rkmc.com/apats/archive/tags/Alphapharm/default.aspx">Alphapharm</category></item></channel></rss>