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
I have a problem with your example | 758 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
I have a problem with your example
Authored by: Anonymous on Monday, October 15 2012 @ 10:32 AM EDT

You posit a computer language algorithm that symbolises abacus beads in a frame and the arithmetic logic employed in using it.

Pardon the misunderstanding.

I propose the abacus to be "computer hardware", and the software to be "bead movement instructions written on paper".

Using this analogy, a lot of the complex and irrelevant machine and software layers can be ignored and we can examine more carefully what software exactly is and how it works.

I propose that the operator of the abacus take on the responsibilities of loading instructions (reading the paper), and executing them (manipulating the beads). In that way we have a complete computer system, A User, Hardware (the abacus), and software (the instructions on paper).

I then go on to stretch the software patent argument claiming that a software patent could apply to the abacus instruction. But I point out obvious fallacies, namely the presumption that the operator of the abacus plays a central role in in making the software a useful part of his reality.

Then I go on to point out that in a modern computer, that central role has been incorporated into the computer design. Now the presumptions have changed, that the algorithm no longer depends on the operator of a computer, that however is debatable because the operator still needs to turn the computer on and still needs to execute the program.

That additional issue of whether the computer can really execute anything without the aid of the operator is central because software patents can't be infringed upon if the infringing characteristics don't "manifest" themselves in the computer. I point out that courts presume infringement only based on the information that software with infringing characteristics is available. I suggest that both by the willful acts of the user and the decisions of the software writer are also enjoined in presumptions.

And lastly, is suggested that these presumptions be revisited as a possible remedy to the software patent fiasco that is occurring.

My discussions with OP are related to my own presumption in the idea I presented as they related to the concepts of execution of software and the implications of the underlying mathematics, and semantics, and the now useful application of what is otherwise mathematics (unpatentable).

I hope that helps.

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