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
Exactly, so as a software developer | 256 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Exactly, so as a software developer
Authored by: Anonymous on Friday, August 03 2012 @ 02:39 AM EDT

I've got no problems with people patenting THEIR inventions if that is what they are patenting. If I was to patent a new kind of mouse trap in the style of a software patent, all further mouse traps would be in breach of my invention because they catch mice.

Software patents are so woolly even sheep have difficulty recognising the animal underneath.

The USPTO requires:

The specification must include a written description of the invention and of the manner and process of making and using it, and is required to be in such full, clear, concise, and exact terms as to enable any person skilled in the technological area to which the invention pertains, or with which it is most nearly connected, to make and use the same.
And yet most of the software patents that have been passed are nowhere near this requirement. As a programmer I would expect the blueprints for how to build it, ie an exact, clear, concise, detailed description of the algorithm for the mechanism to achieve the output from the inputs, included in the patent. Instead, all I see is a patent on the output given the inputs (sometimes not even them) regardless of the black box in between. It's like a patent on software for adding large multi-storage numbers where the input and outputs are given and the bit that does the actually adding is a black box labelled "+"; then when someone implements such a function, the patent holder screams that they've breached their patent even though they've done all the hard work working out the black "+" box with no help whatsoever from the patent. (It may not even be the same black box that the patent holder originally [may] have had.)

So, yes, if you are willing to patent /your/ invention and ONLY your invention, I have no problem, but if it's going to be made so woolly that it covers all implementations of the inputs -> output, even if the algorithm used is totally different to what you may have discovered, then I do have a problem.

The biggest problem is the re-writing from computer speak into legalese for the patent application; trying to use the patent requires another translation from legalese back into computer speak.

An example of a problem using Google translate:

Starting with the French "Il pleut des hallebardes", get it translated into English and it becomes "It's raining cats and dogs" (correctly); now translate it back into French and you get "Il pleut des chats et des chiens" - total nonsense.

Don't think the conversion between computer speak and legalese is immune to such errors; in fact, I'd go as far as to say that based on the comments here of someone whose software was "translated" for patenting when presented with clear, concise, detailed details of the invention in computer speak, the legalese was unrecognisable as (a) the invention and (b) so woolly to cover much more than the original invention without being specific.

[ 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 )