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
not following you | 279 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
not following you
Authored by: BJ on Friday, October 19 2012 @ 04:08 PM EDT
Please don't react so strongly. I wasn' attacking any person, let alone you
personally. For all I know we may be on 'they same side' in this (let's be
general and call it the side of sense and rationality).

All I'm saying is that you, as a technician (software engineer, whatever -- at
least not an attorney) are to decide on the novelty of a certain let us say
'procedure' or 'process' or 'approach' or 'design'.

That judgement on novelty, by you, is now going to have a new life, having been
adopted by attorneies, and being used in a /judicial process/.

The engineer doesn't know all the intricacies of how judicial judgements are
made and (more inportantly) how they will stand up, what is and isn't important,
where the pitfalls are, you name it.

The attorney doesn't know about the intricacies of the engineering process
(let's say computer programming, and/or the general design of computer <->
human interfaces). We have seen Oracle vs. Google and the difficulty that
cropped up in the courtroom of a term that might seem very clear to you and me,
but apparently can lead to a lot of confusion and misuse and outright abuse (to
advance one's side): runtime.

Anyways, some result of the coming together of these two is brought in front of
the USPTO. At best, there the problem repeats. Is it programmer that review?
Are they attornies. Can you insist on one or the other? Are they hybrids? Who
knows!

So the result is a toss up, as we have seen -- and little should we be
surprised, really.

That should encourage us to be critical of the process, examine why and where it
goes wrong (it could be an outrageous amount of expertise being required for any
application, these days), and subsequently seek to formulate fixes and/or
alternatives.

bjd


[ Reply to This | Parent | # ]

not following you
Authored by: Anonymous on Friday, October 19 2012 @ 11:49 PM EDT
Thing is, the same kind of junk that shows up in software patents also shows
up in non-software patents.

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