Interwoven, Inc. v. Vertical Computer Systems, Inc., No. 3:2010cv04645 - Document 158 (N.D. Cal. 2013)

Court Description: ORDER DENYING PLAINTIFF'S MOTION FOR SUMMARY JUDGMENT. Signed by Judge Richard Seeborg on 1/4/13. (cl, COURT STAFF) (Filed on 1/4/2013)
Download PDF
Doc. 158 1 2 3 4 5 6 7 IN THE UNITED STATES DISTRICT COURT 8 FOR THE NORTHERN DISTRICT OF CALIFORNIA 9 SAN FRANCISCO DIVISION 10 11 For the Northern District of California United States District Court Interwoven, Inc. v. Vertical Computer Systems, Inc. 12 13 16 ORDER DENYING PLAINTIFF’S MOTION FOR SUMMARY JUDGMENT Plaintiff, 14 15 No. CV 10-04645 RS INTERWOVEN, INC., v. VERTICAL COMPUTER SYSTEMS, 17 18 Defendant. ____________________________________/ 19 20 21 22 I. INTRODUCTION On October 14, 2010, Interwoven, Inc. (“Interwoven”) filed a Complaint seeking a 23 declaratory judgment that the 6,826,744 (“the ‘744 patent”) and 7,716,629 (“the ‘629 patent”) 24 patents held by Vertical Computer Systems (“Vertical”) are invalid and unenforceable, or that no 25 valid, enforceable claim within the patents-in-suit is infringed by plaintiff’s software. An 26 Amended Complaint was later filed further seeking a declaration that the ‘744 patent and the 27 ‘629 patent are invalid due to inequitable conduct before the United States Patent and Trademark 28 NO. 10-CV-04645 RS ORDER Dockets.Justia.com Office (“PTO”) and enjoining defendant from prosecuting or instituting any action against 2 plaintiff claiming that the patents-in-suit are valid, enforceable, or infringed. Interwoven has 3 moved for summary judgment seeking: (1) a determination that the ‘744 patent is unenforceable 4 due to inequitable conduct based on the inventor’s alleged failure to disclose prior art to the 5 PTO; (2) that the child ‘629 patent is infected by the unenforceability of the parent ‘744 patent, 6 or, in the alternative, that the ‘629 patent is not entitled to the earlier filing date of the ‘744 7 patent; and/or (3) that the patents are invalid under the 35 U.S.C. §102(b) on-sale bar. For the 8 following reasons, Interwoven’s Motion for Summary Judgment is denied. II. 9 BACKGROUND1 The technology in this matter involves a system for generating software applications in 10 11 For the Northern District of California United States District Court 1 an “arbitrary object framework.” Aubrey McAuley is the inventor, and Vertical is the owner of 12 the ‘744 and ‘629 patents at issue in this suit. The ‘744 patent application was filed on October 13 1, 1999 and granted on November 30, 2004. The ‘629 patent is a continuation application filed 14 on November 29, 2004 and granted on May 11, 2010. McAuley drafted the specification for the 15 application and initially provided four drawings that now appear as Figures 1 through 4. Before 16 filing the ‘744 application, Figure 5 was added, describing an “embodiment” of the invention. 17 Figure 5 depicts a number of features of McAuley’s prior art WebOS product and was not 18 created for the patent application. McAuley’s Company, Adhesive, had been marketing and 19 selling its WebOS lines of products since as early as 1996. The WebOS User’s Guide, provided 20 to McAuley’s customers, is dated June 9, 1998. In 2007, Vertical filed an action for infringement against Microsoft in the Eastern District 21 22 of Texas. Microsoft answered the complaint and counterclaimed for inequitable conduct, 23 alleging that Figure 5 showed a prior art system that was available more than one year before the 24 25 26 27 28 1 Facts are drawn from the First Amended Complaint, Motion for Summary Judgment, Opposition, and Reply. Vertical objects to Interwoven’s Exhibits A-1 through A-5, referring to chapters of “The Complete Idiot’s Guide to Microsoft Visual InterDev,” and arguments in the Reply brief that allege Vertical did not disclose the WebOS system to the PTO. The Court has not relied on Exhibits A-1 through A-5 in coming to its decision. Whether the WebOS system was disclosed appears to be a fact in dispute, and thus not an appropriate basis on which to grant summary judgment. NO. 10-CV-04645 RS ORDER 2 filing date of the ‘744 patent application and was not an embodiment of the present invention. It 2 also alleged that McAuley should have submitted Figure 5 as prior art. After settling with 3 Microsoft, while the application for the ‘629 patent was pending, McAuley and Vertical changed 4 the label of Figure 5 on the ‘629 patent to describe an “environment,” rather than an 5 “embodiment” of the invention. They claim the original word choice was merely a 6 typographical error that they felt wasn’t necessary to change in the ‘744 patent. Additionally, 7 McAuley and Vertical state they disclosed as prior art a description of the WebOS system, from 8 which Figure 5 originated, and documentation of the WebOS system to the PTO. Interwoven 9 disputes that the WebOS system was ever disclosed to the PTO during the prosecution of the 10 ‘629 patent, saying the bits and pieces of documentation referring to WebOS could not provide 11 For the Northern District of California United States District Court 1 the public with notice and thus are insufficient to constitute a disclosure. During the prosecution 12 of the ‘629 patent, McAuley and Vertical also selectively disclosed to the PTO twenty-four 13 pieces of the over 60 pieces of prior art that had been identified over the course of the Microsoft 14 litigation. The PTO did not apply the WebOS reference to the claims of the ‘629 patent in 15 granting it. 16 The present case was filed in 2010. Following the 2011 Claim Construction Order issued 17 by this Court, Interwoven filed petitions for reexamination of the ‘744 and ‘629 patents, but did 18 not cite to the WebOS materials in its requests, nor seek to change the “typographical error” in 19 the ‘744 patent referring to “embodiment” rather than “environment.” The PTO undertook the 20 requested reexaminations. It subsequently issued a reexamination certificate for the ‘629 patent 21 and a notice of intent to issue a reexamination certificate for the ‘744 patent. 22 It is undisputed that, during the prosecution of the ‘744 patent, the inventor never 23 disclosed the WebOS system to the PTO. As a result, the PTO did not know that the WebOS 24 product, from which Figure 5 was taken, was on sale and available to the public more than a year 25 before filing the application leading to the ‘744 patent. Vertical states Figure 5 does not disclose 26 the inventions of the ‘744 or ‘629 patents and that the references to Figure 5 in those patents do 27 not discuss the claimed subject matter or the arbitrary objects, the claimed advance in the 28 NO. 10-CV-04645 RS ORDER 3 patents-in-suit. It asserts that the prior art references cited by the examiner in the ‘744 patent 2 show similar systems and are thus cumulative to Figure 5, as they make essentially the same 3 disclosure. According to Vertical, the WebOS system from which the diagram was taken did not 4 include arbitrary objects. Rather, the system suffered from the very inefficiencies arbitrary 5 objects are intended to fix. Vertical avers that it was not until Version 7 of WebOS was 6 introduced between 1999 and 2001, that the system utilized arbitrary objects. 7 Interwoven insists nonetheless that the WebOS product is material prior art of which 8 McAuley was aware and the existence of which he should have disclosed to the PTO upon filing 9 his application for the ‘744 patent. It contends Vertical’s position is contradictory: if it were true 10 that the WebOS product is unrelated to the patented invention, Figure 5 would be an irrelevant 11 For the Northern District of California United States District Court 1 diagram that should not have been included in the patent application. If the WebOS drawing is 12 part of the patented subject matter, on the other hand, it was on sale before the filing of the 13 patents-in-suit, rendering the patents invalid pursuant to the on-sale bar. Moreover, Interwoven 14 contends Figure 5 is not cumulative, as it discloses an object manager managing objects of 15 various types in an object library that no other figure depicts. Interwoven concludes that, had the 16 PTO known the WebOS product or its derivatives had been sold and in public use prior to the 17 filing of the ‘744 application and that a diagram of the WebOS product depicted an embodiment 18 of the invention, the patent would not have been granted. 19 III. LEGAL STANDARD 20 A. Summary Judgment 21 Summary judgment is appropriate “if the pleadings, depositions, answers to 22 interrogatories, and admissions on file, together with the affidavits, if any, show that there is no 23 genuine issue as to any material fact and that the moving party is entitled to a judgment as a 24 matter of law.” Fed. R. Civ. P. 56(c). The moving party bears the initial burden of 25 demonstrating the absence of a genuine issue of material fact. Celotex Corp. v. Catrett, 477 U.S. 26 317, 323 (1986). If the movant succeeds, the burden then shifts to the nonmoving party to “set 27 forth specific facts showing that there is a genuine issue for trial.” Fed. R. Civ. P. 56(e). See 28 NO. 10-CV-04645 RS ORDER 4 also Celotex, 477 U.S. at 323. A genuine issue of material fact is one that could reasonably be 2 resolved in favor of the nonmoving party, and which could affect the outcome of the suit. 3 Anderson v. Liberty Lobby, Inc., 477 U.S. 242, 248 (1986). The court must view the evidence in 4 the light most favorable to the nonmoving party and draw all justifiable inferences in its favor. 5 Id. at 255. 6 B. Inequitable Conduct 7 Inequitable conduct is a defense to patent infringement arising out of the doctrine of 8 unclean hands. To stem the tide of inequitable conduct claims, the Court of Appeals for the 9 Federal Circuit recently articulated a new, heightened standard for an inequitable conduct 10 defense. See Therasense v. Becton Dickinson and Co., 649 F.3d 1276 (Fed. Cir. 2011). To 11 For the Northern District of California United States District Court 1 prevail on a motion for inequitable conduct, a party must show that “the patentee acted with the 12 specific intent to deceive the PTO.” Id. at 1290 (citing Star Scientific, Inc. v. R.J. Reynolds 13 Tobacco Co., 537 F.3d 1365, 1366 (Fed. Cir. 2008)). A finding of gross negligence or that the 14 patentee “should have known” is not sufficient. Id. (citing Kingsdown, 863 F.2d at 876). Rather, 15 there must be clear and convincing evidence that the applicant made a deliberate decision to 16 withhold a known material reference. Id. A sliding scale should not be used in making a finding 17 of intent and materiality, nor can intent be inferred from materiality. Id.; See also Praxair, Inc. 18 v. ATMI, Inc., 543 F.3d 1306, 1313 (Fed. Cir. 2008) (explaining that “a showing of materiality 19 alone does not give rise to a presumption of intent to deceive.”). Nevertheless, because evidence 20 of direct intent is rare, intent may be inferred from indirect and circumstantial evidence. Id. 21 (citing Larson Mfg. Co. of S.D., Inc., v. Aluminart Prods. Ltd., 559 F.3d 1317, 1340 (Fed. Cir. 22 2009)). To meet the clear and convincing standard, the specific intent to deceive must be the 23 single most reasonable inference to be drawn from the evidence. Id. (citing Star, 537 F.3d at 24 1366). 25 The materiality required to establish inequitable conduct is “but-for” materiality. Id. at 26 1291. When an applicant fails to disclose prior art, it qualifies as “but-for” material if the PTO 27 would not have approved a claim if it had been aware of the prior art. Id. To determine whether 28 NO. 10-CV-04645 RS ORDER 5 the PTO would have issued the patent, a preponderance of the evidence standard applies, giving 2 the claims their broadest possible construction. Id. at 1291-92. An exception to the “but-for” 3 materiality standard exists for acts of affirmative egregious misconduct. Id. at 1292. One 4 example of such misconduct is the filing of an unmistakably false affidavit. Id. (citing Rohm & 5 Haas Co. v. Chrystal Chem. Co. 722 F. 2d 1556, 1571 (Fed. Cir. 1983). The remedy for inequitable conduct is the “atomic bomb” of patent law. Id. at 1288. 6 7 This is because, unlike invalidity defenses which render individual claims invalid, inequitable 8 conduct makes the entire patent unenforceable and can infect related patents and applications in 9 the same technology family. Id. Because it is an equitable doctrine, inequitable conduct should 10 only be found in instances where the patentee’s misconduct resulted in an unfair benefit from the 11 For the Northern District of California United States District Court 1 unwarranted claim. Id. at 1292. 12 C. On-Sale Bar 13 The on-sale bar prevents a person from acquiring a patent if the invention was “in public 14 use or on sale in this country, more than one year prior to the date of the application for patent in 15 the United States.” 35 U.S.C. §102(b). This serves as a limiting provision, both excluding ideas 16 that are already in the public domain from patent protection and confining patent protection to 17 the statutory term. Pfaff v. Wells Elecs., Inc., 525 U.S. 55, 64(1998). The Supreme Court has 18 articulated a two-part test to determine whether the on-sale bar applies: (1) the product must be 19 the subject of a commercial offer for sale; and (2) the invention must be ready for patenting. Id. 20 at 67. To overcome the presumption of validity, a challenger must demonstrate these factors by 21 clear and convincing evidence. i4i Ltd. P’ship v. Microsoft Corp., 598 F.3d 831, 846 (Fed. Cir. 22 2010). 23 To meet the first prong, the Federal Circuit has held that “the invention that is the subject 24 matter of the offer for sale must satisfy each claim limitation of the patent, though it may do so 25 inherently.” Scaltech, Inc. v. Retec/Tetra, LLC, 269 F.3d 1321, 1329 (Fed. Cir. 2001). 26 Nevertheless, it is not necessary to show that all embodiments were on sale more than one year 27 before the date of filing. Id. at 1330. The second condition may be satisfied by either proof of 28 NO. 10-CV-04645 RS ORDER 6 reduction to practice before the critical date or by proof that the inventor had, prior to the critical 2 date, described the invention in sufficient detail to enable a person skilled in the art to practice it. 3 Id. at 67-68. IV. 4 DISCUSSION 5 Specific Intent 6 Inventor McAuley declares he prepared the entire patent application himself. Originally, 7 he included the diagrams now labeled as Figures 1-4. When his patent attorney told him the 8 application needed more diagrams, he provided the WebOS diagram for inclusion as Figure 5. 9 There is no dispute that the drawing was a pre-existing diagram and was not created for the 10 patent application. McAuley maintains that he did not think the diagram was important to the 11 For the Northern District of California United States District Court 1 invention, and thus had not included it in his original submission. He further maintains that, at 12 the time he drafted the application, he did not appreciate the precise meaning that “embodiment” 13 has in patent law. As a result, he and his lawyer failed to catch what he alleges to be a 14 typographical error in the description of the diagram. 15 Interwoven contends that McAuley “should have been aware he needed to disclose his 16 prior art WebOS product” to the PTO during prosecution of his ‘744 patent. The inquiry into 17 what McAuley “should have” known, however, is irrelevant to the question of inequitable 18 conduct. Under the heightened intent requirements articulated by the Federal Circuit in 19 Therasense, Interwoven must show that McAuley made a deliberate decision to withhold a 20 known material reference. Interwoven has not met its burden. It presents no evidence from 21 which such deliberation can be inferred. Rather, the evidence proffered could suggest just as 22 easily that McAuley was mistaken, or at worse negligent, in his decision to disclose certain 23 pieces of prior art, but not his WebOS product. 24 Interwoven argues McAuley and Vertical’s behavior once the alleged error was 25 discovered is sufficient to infer intent to deceive the PTO. Specifically, Interwoven notes 26 Vertical chose to disclose WebOS during the prosecution of the ‘629 patent, but failed to correct 27 its disclosure for the ‘744 patent. It claims that hiding the WebOS product itself during the 28 NO. 10-CV-04645 RS ORDER 7 prosecution of the ‘744 patent can only be explained as specific intent to mislead the PTO. In 2 support of this argument, it relies on Aventis Pharma S.A. v. Hospira, Inc., 675 F.3d 1324 (Fed. 3 Cir. 2012), in which the court deemed selective concealment of prior art as sufficient to find 4 specific intent. Unlike the present case, however, Aventis, was decided after a trial on the merits, 5 not at the summary judgment stage. The court concluded that the inventor’s testimony for 6 withholding select prior art was simply not credible. Id. at 1235-36. Here, by contrast, 7 McAuley’s declarations that he maintained an honest belief the WebOS product was not relevant 8 to the patent has yet to be subject to examination. McAuley’s intent remains a fact that must be 9 found by the trier of fact. It is enough to defeat summary judgment that a question remains as to 10 11 For the Northern District of California United States District Court 1 the inventor’s credibility. Interwoven further asserts that Vertical never disclosed the WebOS Manual to the PTO, 12 indicating an intent to deceive. As noted above, it is undisputed that the product was not 13 disclosed during the prosecution of the ‘744 patent, but Vertical disputes the contention that the 14 WebOS product was not disclosed during the prosecution of the ‘629 patent. Interwoven insists 15 that, from the perspective of the PTO, the disclosure of the The Complete Idiot’s Guide to 16 Microsoft’s Visual InterDev was completely unrelated to the WebOS product. It is difficult, if 17 not impossible, however, to determine how the PTO interpreted the disclosures Vertical 18 provided. The Guide did refer to the WebOS product. It would thus be a stretch to conclude that 19 the PTO did not consider them in coming to its decision to issue the ‘629 patent. While 20 Interwoven accuses Vertical of assuming the WebOS system was disclosed and making “an 21 erroneous leap in logic” that only references specifically cited in the claims are material, 22 Interwoven is guilty of similar assumptions and leaps in concluding, as a matter of law, that the 23 WebOS system was not disclosed and that it is materially relevant to the claimed invention. 24 Interwoven next points to McAuley’s refusal to explain the claimed invention to 25 opposing counsel during his deposition as evidence of deceptive intent. It cites Advanced 26 Magnetic Closures, Inc. v. Rome Fasteners, 607 F.3d 817, 830-31 (Fed. Cir. 2010), to support 27 the proposition that deceptive intent can be premised on the inventor directing opposing counsel 28 NO. 10-CV-04645 RS ORDER 8 to read the patent, rather than explaining the invention himself. In that case, the question was 2 whether the named inventor was the exclusive inventor. Id. at 828. The court, after trial, found, 3 among other things, the named inventor was 1) either unable or unwilling to articulate his 4 claimed invention, 2) could not offer any scientific or technical explanation of his own patent, 5 and 3) offered evasive, argumentative, and sometimes contradictory testimony regarding his 6 status as the inventor. Id. at 830. The court thus concluded that his testimony bore indicia of 7 fabrication, and that the single most reasonable inference was intent to deceive the PTO. Id. 8 While it is true that, during his deposition, McAuley refused to elaborate on the information 9 contained within the specification of the patents-in-suit, the question of inequitable conduct in 10 this case has nothing to do with McAuley’s familiarity with the claimed invention. Indeed, it is 11 For the Northern District of California United States District Court 1 undisputed that he wrote the initial drafts of the patent application himself. Whether or not 12 McAuley was willing to expand upon the language set forth in the patent seems more a question 13 of litigation strategy than an indication of inequitable conduct before the PTO. Thus, specific 14 intent cannot be unambiguously inferred from any refusal to answer opposing counsel’s 15 questions. 16 Material Prior Art 17 Interwoven makes much of the fact that the inventor conceded Figure 5 depicts a number 18 of features of his prior WebOS product, including its ability to handle data objects, logic objects, 19 formatting objects and variables using an object manager, and an object library. Interwoven 20 contends that these features correspond to those of the patents-in-suit as disclosed in the ‘744 21 specification. Vertical counters by arguing that Figure 5 has nothing to do with arbitrary objects, 22 which are the most significant aspect of the claimed invention. Figure 5, McAuley insists, has 23 the same framework as the claimed invention, but the introduction of arbitrary objects changed 24 everything about the way the product worked. It was not until the introduction of WebOS 25 Version 7 around 2001, then renamed SiteFlash, that the WebOS program adopted the 26 improvements described in Vertical’s patent application. 27 28 NO. 10-CV-04645 RS ORDER 9 During Claim Construction, this Court noted that “the innovation of the patents is the 2 ability to separate form from function from content, but such separation is not required in every 3 instance.” This Court construed an “arbitrary object” to be “an object that can be created 4 independently by individual preference, are interchangeable, and that may be, but need not be, 5 accessed solely by name, the object being an entity that can have form, content, or functionality 6 or any combination of form, content and functionality.” While arbitrary objects and the ability to 7 separate form, content, and function were the focus of claim construction, Figure 5 does not 8 specifically reference any of these elements. Thus, Figure 5 does not, by its terms, encompass 9 the elements of the claimed invention. Interwoven, however, observes that a claimed advantage 10 of the invention is that it allows for personalization and profiling. It points out that this feature is 11 For the Northern District of California United States District Court 1 depicted only in the piece of Figure 5 labeled “User Profile and Password Database 70.” This 12 improvement, however, appears only in the description of the invention, not in the claims 13 themselves. Thus the reference contained in Figure 5 indeed may not be relevant to the claimed 14 aspects of the invention. In any event, it cannot be said at this stage that, as a matter of law, the 15 depicted improvement is “but for” material to the claimed invention. 16 Nevertheless, Interwoven contends that because the diagram was put forth as an 17 embodiment of the invention, the WebOS product is “clearly material prior art.” Embodiments, 18 however, need not be covered by the claims of the patent. See TIP Sys., LLC v. Phillips & 19 Brooks/Gladwin, Inc., 529 F.3d 1364, 1373 (Fed. Cir. 2008) (noting that, “read in the context of 20 the specification, the claims of the patent need not encompass all disclosed embodiments. 21 [citation omitted] Our precedent is replete with examples of subject matter that is included in the 22 specification, but is not claimed.”); Unique Concepts, Inc. v. Brown, 939 F.2d 1558, 1562-63 23 (Fed. Cir. 1991) (explaining that “subject matter disclosed but not claimed in a patent application 24 is dedicated to the public.”). Accordingly, the mere labeling of the diagram as an “embodiment” 25 is insufficient to make the reference per se material. 26 27 Interwoven insists Vertical’s explanation that the use of the word “embodiment” rather than “environment” was merely a mistake is implausible. Nevertheless, it contends that, even if 28 NO. 10-CV-04645 RS ORDER 10 WebOS had been accurately labeled as an “environment” in the ‘744 patent, as it is in the ‘629 2 patent, its disclosure would still have been materially relevant to the PTO’s determination. 3 Interwoven premises this assertion on the assumption that WebOS was never disclosed to the 4 PTO as prior art. Vertical, however, disputes that assumption, arguing it did in fact disclose the 5 WebOS product following the Microsoft litigation while the prosecution of the ‘629 patent was 6 still pending. The issue of disclosure therefore remains in dispute. Moreover, Interwoven 7 conceded at oral argument that, had Figure 5 been labeled as an “environment” in the ‘744 8 patent, it would have no claim for inequitable conduct. Rather, it would only have potential 9 claims of invalidity. The question of whether WebOS is material with respect to an 10 “environment” of the claimed invention is therefore not relevant to a determination of 11 For the Northern District of California United States District Court 1 inequitable conduct. 12 Vertical points out that Interwoven did not use the WebOS material in its request for 13 reexamination of the patent. It contends that this is evidence Interwoven itself did not believe its 14 assertion that WebOS and Figure 5 are material to the patents-in-suit, and that it knew the PTO 15 had considered the WebOS disclosure and not found it material. At oral argument, Interwoven 16 responded to this contention by saying it was not obligated to present all alleged prior art during 17 the reexamination process, and that it wanted to preserve the WebOS issue for trial. While true 18 that there is no requirement all prior art be presented at reexamination, this response cannot hold 19 water. The PTO determines materiality in the first instance; the courts are a last resort. If the 20 PTO had concluded the omission of WebOS as a prior art reference was material, this entire 21 litigation would have been avoided. Thus, to suggest Interwoven was holding the reference in its 22 back pocket for trial is nonsensical. Had it believed Figure 5 and the WebOS product to be 23 materially relevant to the validity of the patents-in-suit, it should have sought such a 24 determination from the PTO during their reexamination. 25 On-Sale Bar 26 The ‘744 patent was filed on October 1, 1999. Thus, the critical date is October 1, 1998. 27 If the claimed invention was on sale before this critical date, the patent is invalid under the on- 28 NO. 10-CV-04645 RS ORDER 11 sale bar doctrine. There is no dispute that the WebOS product was on sale well before this 2 critical date. Nevertheless, there is dispute as to whether that product anticipated or rendered 3 obvious the claimed invention. “The on-sale bar is evaluated on a claim-by-claim basis, so that 4 some claims of a patent may be found to be barred while others are not.” Allen Engineering 5 Corp. v. Bartell Indus., 299 F.3d 1336, 1353 (Fed. Cir. 2002). Thus each claim of the patents-in- 6 suit must be construed and specific findings of fact must link elements of the product on sale to 7 each claim limitation. Id. at 1355. 8 As discussed above, it is the challenger’s burden to prove, by clear and convincing 9 evidence, that each element of the claimed invention was on sale prior to the critical date. 10 Interwoven has not met this burden. Rather, it states generally that the WebOS product 11 For the Northern District of California United States District Court 1 embodies the claimed invention. This statement depends on the fact that Figure 5, originating 12 from the WebOS manual, is labeled as an “embodiment.” However, as discussed, there is 13 dispute as to whether Figure 5 actually is an embodiment of the invention, or if such labeling was 14 merely a typographical error. Interwoven does not identify the specific claims allegedly 15 anticipated or rendered obvious by the sale of the early versions of the WebOS product. Without 16 such specific claims, the on-sale bar cannot be adequately evaluated. Thus, on the evidence 17 presently available, the patents-in-suit do not fail by virtue of the on-sale bar. V. 18 19 CONCLUSION For the foregoing reasons, Interwoven’s Motion for Summary Judgment with respect to 20 inequitable conduct before the PTO, and invalidity due to the on-sale bar, is denied in its 21 entirety. 22 23 IT IS SO ORDERED. 24 25 26 Dated: 1/4/13 RICHARD SEEBORG UNITED STATES DISTRICT JUDGE 27 28 NO. 10-CV-04645 RS ORDER 12
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.