decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
You missed: software developers aren't qualified to understand them | 364 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
You missed: software developers aren't qualified to understand them
Authored by: Anonymous on Tuesday, January 08 2013 @ 01:36 PM EST
Actually - this is the first time I have heard this - and it seems
counter-intuitive that a patent that is supposed to teach practitioners in the
field should be unintelligible to them.

In fact, it seems pretty strange that lawyers would presume they will understand
patents about almost any modern engineering field other than their own without
the aid of expert witnesses.

[ Reply to This | Parent | # ]

  • No disagreement - Authored by: Anonymous on Tuesday, January 08 2013 @ 03:45 PM EST
You missed: software developers aren't qualified to understand them
Authored by: dio gratia on Tuesday, January 08 2013 @ 06:42 PM EST
From 35 USC § 112:
a) In General.— The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention.

(b) Conclusion.— The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.

...

There's this thing called a specification, which will include a written description "of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains" allowing someone having ordinary skill in the art to implement.

There's this conclusion to the specification comprised of one or more claims. You could rightly claim the written description is required to teach a PHOSITA, what's at issue is whether or not the ordinary practitioner needs to understand the claims.

We know the written description limits claims that could otherwise be interpreted over broadly. If the invention isn't described in the written description the claim lacks enablement. You could also note that prior art by reference and ordinary meaning without prior art are used to interpret claims based on the time the patent is filed. A post filing re-issued prior art patent reference, a non-patent prior art reference later amended or latter dictionary meaning can't expand claims.

From this we get the CAFC deciding claims construction is a matter of law, with the Supreme Court refusing to take up a countervailing argument. All this says you can't tell what the invention actually is authoritatively, although the entire specification limits the claim, without it being adjudicated by one of a District Court, the PTAB, the CAFC or the Supreme Court. A lawyer can of of course give you an opinion.

You would think that a PHOSITA would be capable of determining whether or not a provided constructed claim is supported by the written description or is otherwise indefinite based on terms of art. Such a person may not be qualified to interpret limiting prior art speaking directly to claims.

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )