Showing posts with label Official Notice. Show all posts
Showing posts with label Official Notice. Show all posts

Wednesday, December 10, 2014

Board finds no inconsistency with relying on Official Notice for a claimed feature while also asserting that this feature isn't supported by Applicant's sparse description

Takeaway: The Examiner denied the Applicant's priority claim to a provisional, for failure to adequately describe a claim limitation. According to the Examiner, some description was present, but not in the context claimed. The Examiner then used Official Notice for this same feature in an obviousness rejection. On appeal, the Applicant argued the "facial inconsistency" of these two positions: "asserting the feature was unquestionably and notoriously known in the prior art (which was silent about the feature), while contending that the applicant's provisional application, which provided textual support for the feature, nevertheless was not sufficient to establish a priority for the feature." The Board was not persuaded by the inconsistency argument, and cited to Vas-Cath Inc. v. Mahurkar to explain that "a claimed feature that is common knowledge in the art must nevertheless have adequate written description support in the specification to demonstrate to a person of ordinary skill in the art that the inventors had possession of the claimed invention at the time of the filing of the application." (Ex parte Timbadia, PTAB 2013.)

Details:
Ex parte Timbadia
Appeal 2010002877; Appl. No. 10/712,938; Tech. Center 3700
Decided: March 25, 2013

The application was directed to automated test-taking. During prosecution, the Applicant amended to add these limitations:
     delivering a changed state object at the same time that a triggering event occurs on the testing station;
     upon failure of the testing station, the [state objects] ... are used to recreate the examination on the testing station ... and
     wherein the user will not be penalized for the time that questions are not available.
(Emphasis added for limitations at issue.)
In response, the Examiner switched to a different secondary reference in the obviousness rejection (Ashley)of all independent claims. The Examiner relied on this secondary reference for the "at the same time" feature, and took Official Notice of the new "not penalized" feature. At the same time, the Examiner denied the priority claim because the newly added "at the same time" and "not penalized" features were allegedly not present in the provisional. However, Examiner did not reject any claims under written description or enablement.

In an After Final response, the Applicant argued that the Ashley reference was not prior art because the Applicant's provisional did provide an enabling disclosure for the newly claimed features. In support of this argument, the Applicant pointed to to specific passages in the provisional and explained their relevance. The Applicant also traversed the Official Notice as follows:
Applicants cannot fail to note that this portion of the claims so evidently and precisely enabled by the provisional application is also the same portion of the claims for which the Examiner has relied upon official notice. Per MPEP 2144.03, Applicants thus traverse such taking of official notice as improper as lacking sufficient documentary evidence. Citation of a post-dated alleged prior art reference by the Examiner is erroneous not only for the obviousness rejection presented, but also as grounds for taking official notice that the claimed feature is of such notorious character as capable of instant and unquestionable demonstration as to defy dispute. See In re Zurko, 258 F.3d at 1386.
The Applicant appealed. In the Brief, the Applicant specifically traversed the issue of the priority claim. The Applicant explained that the provisional application described using a test state to recover an exam after testing station failure, and this test state includes an elapsed test time that takes into consideration the amount of time that a test is unavailable to the user. Thus, Ashley was not prior art. In the obviousness section of the Brief, the Applicant also argued that Ashley did not teach the "at the same time" limitation. Notably, this section did not discuss the "not penalized" claim limitation or the Examiner's reliance of Official Notice for this feature.

In the Answer, the Examiner maintained the obviousness rejection of all independent claims. The Examiner discussed the denial of priority in the obviousness rejection. The Examiner acknowledged that the "not penalized" claim language was present in the provisional, but noted this was in the context of accounting for transmission latency rather than in the context of a recovery function (as claimed). In a Response to Arguments section, the Examiner noted there were "significant modifications" and "stark differences" between the provisional and the application on appeal. Also, the Applicant had failed to adequately traverse the Official Notice during prosecution, thus admitting that the "not penalized" feature was well-known.

The Applicant filed a Reply Brief which included a section titled "the Examiner's use of Official Notice was properly traversed, is improper and is Squarely Inconsistent with the Office's Contention that Subject Matter at Issue is Not Supported by Applicants'Own Provisional Application." The Applicant argued that the traversal was proper, as follows:
[T]he traversal highlighted the facial inconsistency in the examiner's logic of asserting that the feature was unquestionably and notoriously known in the prior art (which was silent about the feature), while contending that the applicant's provisional application, which provided textual support for the feature, nevertheless was not sufficient to establish a priority for the feature.
On appeal, the Board made findings with regard to "Claims 1 and 13 – Written Description Support" since this issue was contested and impacted the obviousness rejection. The Board found that all features recited in claims 1 and 13 were adequately described in the provisional, so that Ashley was not prior art. With regard to the "not penalized feature," the Board found that the Examiner’s interpretation of what the provisional application describes was "unreasonably narrow." The Examiner incorrectly focused on the provisional's teachings about accounting for transmission latency, but a person of ordinary skill reading the document as a whole "would conclude that recreating the test based on the state of the test at the time of a testing station failure would require not penalizing the user for time lost due to this failure."

Since Ashely was not prior art for claims 1 and 13, the Board reversed the obviousness rejection of these claims. However, claim 20 used slightly different language to describe the "initial state object" feature, which the Board found was not adequately described in the provisional. The Board therefore considered the obviousness rejection of claim 20 on the merits, and affirmed.

With regard to the "at the same time" feature, the Board found no error in the Examiner's finding that Kershaw taught this feature. With regard to the "not penalized" feature, the Board found that the Applicant had not properly traversed the taking of Official Notice because it did not "explain why the noticed fact is not considered to be common knowledge or well-known in the art" (citing In re Boon, 439 F.2d 724, 728 (CCPA 1971)).

The Board also commented on the Applicant's inconsistency argument – that the Notice'd feature was completely missing in the reference yet textually supported by Applicant's provisional:
Appellants have not provided persuasive argument as to why the Examiner’s findings are inconsistent. A claimed feature that is common knowledge in the art must nevertheless have adequate written description support in the specification to demonstrate to a person of ordinary skill in the art that the inventors had possession of the claimed invention at the time of the filing of the application. See Vas-Cath Inc. v. Mahurkar, 935 F.2d 1555, 1562-63 (Fed. Cir. 1991).
Finally, the Board noted that any alleged inconsistency was resolved by the Board's finding that the subject of the Official Notice ("not penalized" feature) was indeed properly supported in the provisional application.


My two cents: The Applicant's inconsistency argument has intuitive appeal, but is ultimately flawed. The argument goes like this: "Surely the Examiner's characterization of a feature as 'well-known' indicates that very little description is needed, in which case a sparse description of the same feature by the Applicant shouldn't result in a denial of the priority claim." However, this argument is flawed because it confuses enablement and written description.

A reference has only to enable. Since this can take into account the background knowledge of a POSITA, a sparse description may indeed be enough for enablement. On the other hand, the Applicant's spec has to comply with both the enablement and the written description requirement. And written description "must clearly allow persons of ordinary skill in the art to recognize that [the inventor] invented what is claimed." (Ariad Pharm., Inc. v. Eli Lilly & Co., 598 F.3d 1336, 1351 (Fed.Cir.2010) (en banc)).

Unfortunately, when you have a sparse description of a particular embodiment that falls within the claim scope, then try to argue that a POSITA can fill in the rest, the case law on written description goes against you:
The question is not whether a claimed invention is an obvious variant of that which is disclosed in the specification. Rather, a prior application itself must describe an invention, and do so in sufficient detail that one skilled in the art can clearly conclude that the inventor invented the claimed invention as of the filing date sought.
Lockwood v. American Airlines, Inc., 107 F. 3d 1565 (Fed. Cir. 1997).
Or, put another way:
A description of one method . . . does not entitle the inventor . . . to claim any and all means for achieving that objective."
LizardTech v. Earth Resource Mapping, Inc., 424 F.3d 1336, 1346 (Fed. Cir. 2005).

Monday, December 28, 2009

Examiner affidavit of personal knowledge

I've seen plenty of file histories where the Examiner says an element is known or well-known instead of providing a reference, and the Applicant responds by saying "since the Examiner appears to be relying on personal knowledge, Applicant demands that the Examiner provide an affidavit attesting to these facts."

According to some practitioners, this is a good strategy to force the Examiner to provide a reference, because Examiners don't want to be bothered with an affidavit. Since I'm as annoyed as the next guy by allegations that elements are "known", "well-known," "notoriously well-known," and "extremely well known," I was curious to know a) the legal basis for the demand for an affidavit and b) whether or not it's a good way to force the Examiner to provide a reference.

37 CFR 1.104(d)(2) really does say that the Examiner must provide an affidavit when relying on personal knowledge:

When a rejection in an application is based on facts within the personal knowledge of an employee of the Office, the data shall be as specific as possible, and the reference must be supported, when called for by the applicant, by the affidavit of such employee, and such affidavit shall be subject to contradiction or explanation by the affidavits of the applicant and other persons.

I found a few instances where this "personal knowledge" issue has been raised at the BPAI. Only one of these Board decisions said that the Examiner should have provided an affidavit, and in this one the Examiner really did state that the element came from "facts within his personal knowledge". The other cases were found to be instances of Official Notice, and in most of them the Examiner made the Official Notice explicit.

Takeaway: The rules for traversing Official Notice are very specific, and not doing so properly is an admission that the element is known. So, instead of arguing "Examiner didn't provide a reference, so must have been relying on personal knowledge," it seems much more productive to instead assume that the Examiner is invoking Official Notice when no reference is provided, and to properly traverse the Official Notice. Sure, there are decisions where the Board treated the real issue as Official Notice rather than personal knowledge, and didn't punish the Applicant for not properly traversing — but why rely on the Board's generosity?

Here's a Summary of the Board's findings on the "personal knowledge" issue.

Ex parte Hull: The Examiner really did use personal knowledge! The final Office Action said: "The examiner has personal knowledge...In September, 1998, the examiner cut hyperlinks from a web browser and pasted said hyperlinks into an email. While composing an email message in Microsoft Outlook within the Windows operating environment, the examiner cut URLs of online documents from Internet Explorer and pasted them into said email message. Thus, the limitation of Claim 59 reads on this personal knowledge of the examiner." The Applicant argued that it was improper to reject a claim based on personal knowledge. The Board found in favor of the Applicant: "Therefore, we decline to consider the examiner’s personal knowledge as evidence because the examiner has failed to provide an affidavit or declaration setting forth specific factual statements with an explanation to support the finding of record."

Ex parte Trans Texas Holding Corp.: The Examiner didn't use the magic words "Official Notice" but the Board read it that way. The first Office Action alleged that "the deposit account being secured by property of the institution" was "implicit" in the reference "because this was a well-known method of running a bank." The Applicant responded by disagreeing that this was well-known, referencing the "personal affidavit" rule, and requesting that the PTO "make of record whatever evidence it might have in this regard." The Board found that the request for a personal affidavit "is clearly inappropriate because the examiner is relying not on personal knowledge but on the general knowledge of persons having ordinary skill in the banking art that it was standard practice to provide security for deposit accounts."

Ex parte Duck: The Examiner asserted that a feature was "well-known" instead of using the magic words "Official Notice." The Applicant argued that the examiner did not provide either a reference or a personal affidavit in support of this assertion. The Board didn't comment on the appropriateness of an affidavit, but did find that the Examiner's assertion was based on speculation "and thus fails to provide sufficient reasons for finding [the claim to be] obvious." [My take on this: the problem wasn't the lack of an affidavit, it was the type of facts that the Examiner was asserting to be well-known.]

Ex parte Moitra: The first Office Action said: "The Examiner takes official Notice that is is old and well-known in the art to track costs." The Applicant responded by arguing that the Examiner had cited no source for this finding, and alleged that the "Examiner states that this comes from his personal knowledge." The Board found that the requirement for a personal affidavit was inapplicable, because "this section only requires that facts that are within the personal knowledge of the Examiner be supported. The facts taken under Official Notice here were explicitly found to be common knowledge, and were not based on the Examiner’s personal knowledge."

Ex parte Trajkovic: The Examiner took Official Notice that it was well known in the art that windows are represented on the taskbar by icons and that windows were reactivated by activating these icons. The Applicant argued that the Examiner was required to submit a reference or a personal affidavit to establish facts within personal knowledge. The Board found that:
The use of status buttons on the taskbar (or status bar) in a windows environment to represent windows was so notoriously well known that it cannot be seriously in dispute (although it always would be better for an Examiner to provide a reference where it would be easily available). Such status buttons change appearance to indicate the active window and it was well known to reactivate an inactive window by activating a status button. Anyone who used a computer with Microsoft Windows before 2002 would know these facts.

Sunday, October 11, 2009

Improper to take Official Notice of legal conclusion (Ex parte Yardley)

Ex parte Yardley
Decided July 21, 2009
(Appeal 2009-001146; Appl. No. 10/689,379; Tech. Center 3700)

Ex parte Yardley reminds us that Official Notice is limited to facts, and taking Official Notice OF a legal conclusion is improper.

Some of the claims at issue here were directed to a method of making a paper napkin, and included limitations for dimensions and weight. The Examiner admitted that the reference did not teach ranges of dimensions, nor the weight of the product, but took Official Notice that "it would have been obvious to one of ordinary skill in the art to apply the folding method of [the reference] to various sizes and weights of webs including those of claims 82 and 87." (Decision, pp. 15-16.)

The Board held that Official Notice of obviousness is improper:
[Here] the assertion of official notice is not directed to establishing evidentiary facts, but is rather an attempt to establish the ultimate legal conclusion of obviousness as to the rejected claims. The procedures setting forth the circumstances in which official notice may properly be taken do not recognize any basis for the taking of official notice of a legal conclusion (MPEP § 2144.03), nor do we believe that this would be proper under any circumstances.
(Decision, p. 16.)
The way I understand this, taking Official Notice of a fact is acceptable because a fact is a Premise from which a Conclusion is drawn. Thus, taking Official Notice is a merely a short cut to proving the fact with real evidence — a shortcut that is permissible in limited circumstances. On the other hand, short-cutting the entire analysis by taking Official Notice of the Conclusion itself is not acceptable. 

Based on my own experience, and the BPAI cases I've read, it's pretty hard to traverse an assertion of Official Notice in a way that convinces the Board that you've complied with the law (see MPEP 2144.03(c), for starters). But if you ever see the Examiner taking Official Notice of a legal conclusion, argue that the MPEP § 2144.03 does not provide for this.

Obviousness is probably the strongest form of an "ultimate legal conclusion". But I think other aspects of obviousness analysis could be described as legal conclusions.

For example, I think you could traverse the following statement on the same grounds: "Official Notice is taken that it would be an obvious design choice to use an LCD display instead of a CRT display".

Or even this one: "Official Notice is taken that it's merely a matter of design choice to use an LCD display instead of a CRT display".