- Catchword: "Article 54(2) EPC does not exclude non-technical disclosures from the prior art, in disagreement with Catchword 2 of T 172/03."
- T 172/03, Headnote " anything which is not related to any technological field or field from which, because of its informational character, a skilled person would expect to derive any technically relevant information, does not belong to the state of the art to be considered in the context of Articles 54 and 56"
- The present decision makes me wonder what happened in T 172/03 to cause the Board in that decision to decide that disregard a prior art document, and to pronounce it as a rule in a headnote.
- The Board in T 172/03 was certainly not applicant-friendly and was in fact refusing a patent application for a business method. The written decision T 172/03 is however somewhat difficult to follow. In para. 5, the Comvik approach is briefly discussed. In para. 6, it is emphasized that the skilled person is a software engineer and not a businessman. In para. 7, this is connected to the Examining Division being composed of technically qualified Examiners. The core of the decision is however in para. 8. Therein, the Board disagrees with the ED, who took as closest prior art an existing "order placing mechanism", i.e. a known business method. The Board then recalls that in T 641/00 (Comvik), r. 2, it was said that the FR and DE version of Article 56 refer to (in English) that inventive step means that " if a skilled person cannot derive it in an obvious manner from the state of technology." The Board decides that the closest prior art is " a distributed information system comprising multiple general purpose computers at different locations and connected by a communication network". The distinguishing features are functional features, and the functional features of the claim are accodingly put in the "requirements specification" of the Comvik approach. The Board then finds that "the claimed technical solution does not go beyond the concept of a mere automation of constraints imposed by the business-related aspects. Such automation using conventional hardware and programming methods must be considered obvious to a skilled person."
- In the present case, the Board starts from what it considers to be common general knowledge of what a notary does, and reasons that the way of automation specified in claim 1 is obvious. The Board cites no document evidencing the work procedures of notaries. "The board however observes that the appellant has at no moment disputed that the [notary work process] above is indeed common general knowledge."
- As a comment, in the present case, claim 1 is apparently a 1:1 automation of a known business method. But perhaps a next time the business method is slightly adapted to the use of internet. The advantage of the normally used Comvik approach is that any business method features are put in the requirements specification, even if the (notional) business person has come up with a quite creative business method. I don't think that Comvik requires disregarding business method features of the prior art. Taking into account that a claim is not inventive if it is obvious from any document, it is not necessary to exclude "business method" prior art to say that a general purpose computer is the " closest" prior art (i.e. suitable starting point) for the problem-solution approach, more in particular for the Comvik approach.
EPO T 2101/12 - link
6.3 Instead, the board considers that the most suitable starting point is common general knowledge. The board considers it common general knowledge that documents, such as a will or a contract between parties, may be signed at a notary's office. The notary in such a case has the function of a "trusted third party". It is considered well known, and has not been denied by the appellant, that the whole process in the notary's office would typically comprise the following steps:
(a) A notary receives a document, which will need to be signed, from its author;
(b) the notary authenticates the document, e.g. by providing it with a seal;
(c) the notary presents ("displays") the document to a signatory (not necessarily, and indeed typically not, the same as the author), so that the signatory can gain knowledge of the document's content before signing it;
(d) the signatory signs the document;
(e) the notary authenticates the document together with the signature, i.e. the notary authenticates the fact that the given document was signed by the given signatory, linking the document and the signature together.
6.4 The appellant has submitted, both in the response to the summons (under I.A.1(a)) and during the oral proceedings, that something can only be state of the art if it is related to a technological field or a field from which, because of its informational character, a skilled person would expect to derive technically relevant information, referring to T 172/03.