Posts Tagged: "specification"

Does the term “Invention” in the Specification Limit the Claims?

There are some that will tell you that the use of the term “invention” or “present invention” in the specification will limit the claims. This misguided belief suggests that merely using the word “invention” or the phrase “present invention” in the specification creates a problem for the claims. I have heard this numerous times over the years. Every time I hear this it is like fingers on a chalkboard.

Working with Patent Illustrations to Create a Complete Disclosure

What you are looking at here is something that is similar to a Big Mac because it has two beef patties, which are identified by reference numeral 10. It isn’t quite a Big Mac through because there is no special sauce, and there are tomatoes 18 added. Having a drawing like this makes it easy to describe the hamburger, but it also makes it easy to describe more than what is shown in the drawing. Allow me to illustrate. In a patent application you might describe this drawing as follows…

Santarus v. Par Pharmaceutical: Rader and Newman Disagree on Written Description Support for Negative Limitations

Last week the Federal Circuit decided the case of Santarus, Inc. v. Par Pharmaceutical, Inc., which dealt with whether a drug covered by an Abbreviated New Drug Application (ANDA) infringed the patents owned by that patent owner relative to the proton pump inhibitors (PPI) product omeprazole. The big issue in the case is what might at first glance seem to be a rather innocuous statement relative to the support necessary in a patent specification for a negative claim limitation. But after reading the Newman dissent (which joins in the other aspects of the Court’s decision) it starts to become clear that this could be a much larger issue of significant consequence.

Building Better Software Patent Applications: Embracing Means-Plus-Function Disclosure Requirements in the Algorithm Cases

The disclosure requirements for these types of patent applications has been a moving target for years, which means that whatever the most stringent disclosure requirements are should become the target regardless of the types of claims you file. To ensure your software patent application has appropriate disclosure of the invention you should accept — even embrace — the requirements for having an appropriate means-plus-function disclosure. By meeting the strict standards set forth in the mean-plus-function algorithm cases you will file more detailed applications that have better disclosure and which will undoubtedly support more claims, thus making the resulting patent or patents more valuable.

Patent Drafting: Describing What is Unique Without Puffing

Although a patent application is not a sales pitch per se, most inventors will find it quite helpful to list as many descriptive objectives of the invention as is possible. As a general rule you should, however, stay away from laudatory language and puffery (e.g. “the best gadget known to man” or “the perfect solution” or “using this tool is unquestionably the choice any professional would make”). When you puff the tendency is to skimp on the descriptive details, which are essential to an appropriate patent application. Further, is anyone really likely to take your word for it being “the best”? That is why infomercials demonstrate the functional capabilities of an invention. In a patent application you need to describe the functionality and leave the selling to the salespeople later.

Federal Circuit on Software Patents: Show Me the Algorithms

Earlier today the United States Court of Appeals for the Federal Circuit issued a decision in Noah Systems, Inc. v. Intuit, Inc. According to the Federal Circuit the specification of the ’435 patent must contain an algorithm that performs the function associated with the “access means” limitation, otherwise the limitation is indefinite and the claim invalid. Ultimately, the Federal Circuit would determine that the algorithm disclosed was incomplete. This lead the Court to explain that when the specification discloses an algorithm that only accomplishes one of multiple identifiable functions performed by a means-plus-function limitation, the specification is treated as if it disclosed no algorithm. An incomplete algorithm means no algorithm as all, which means that what one of ordinary skill in the art would understand from the disclosure is no longer relevant. This is where I would depart from the Federal Circuit and think that the law as it relates to means-plus-function claiming of computer software is all wrong. Means-plus-function claims has always been about what someone of ordinary skill in the art would appreciate (see, for example, USPTO 112 guidelines, 76 Fed. Reg. 7162 (9 February, 2011) so why is that not the case with respect to computer software?

Patent Drafting: Drilling Down on Variations in a Patent Application

One of the challenges that a drafter faces when trying to satisfy the enablement requirement is with respect to describing things that can and will vary depending on the circumstances. What you want to do is follow up by explaining the various permutations to help the reader more readily understand what facts, choices or circumstances will have impact.

An Introduction to Patent Claims

Why are we talking about this in a claims primer? There is a difference between adding what we call “new matter” and adding patent claims. New matter, which is prohibited, is defined by first viewing whatever is present at the time of the original filing of the patent application. In determining the breadth of what is covered by that initial patent filing you rely not only on the description contained in the specification and any drawings filed but also on the originally filed claims. Thus, new matter is defined in the negative. If it wasn’t there in the specification, drawings or originally filed claims then it is new matter. If it was present somewhere in what you filed it is not new matter.

Patent Drafting: Language Difficulties, Open Mouth Insert Foot

What I refer to as “experimental language” either explicitly or implicitly suggests that further experimentation is or will be necessary in order to: (1) realize or perfect the invention; or (2) realize or perfect an intermediate or component. Resist the temptation to have your patent application read like a diary of thoughts and/or personal observations regarding future research and goals. This type of language is usually not found in a patent application because it suggests that your invention is not yet completed, which could be used as an admission that the invention is not enabled and/or that you have not satisfied the written description requirement.

The Key to Drafting an Excellent Patent – Alternatives

The trick with drafting a patent application is to describe anything that will work, no matter how crude, no matter how defective. You want to capture everything. This is because the only power of a patent is to prevent others from doing what is covered in the patent. If you are making money there will be others who want to do what you are doing. Your patent can prevent them from doing what you are doing, but a strong patent will also prevent would-be-competitors from doing anything that is close. You want to prevent would-be-competitors from directly competing and from competing with substitutes, even substitutes that are inferior.