Law Documents in a Nutshell
Ramakrishnan M writes "LawMeme has a two part article (more to come) on reading and interpreting Legalese for geeks, titled "Law School in a nutshell". Here is the Part 1 and part 2"
← Back to Stories (view on slashdot.org)
I appreciate the attempt to inform, but it seems to me this falls into the category of "a little bit of knowledge is dangerous". The pages bill themselves as "3 years of law school in a nutshell", as if you'd get a quick overview of relevant law for geeks. However, it is an analysis of one particular court filing, and based on my 15+ years dealing with legal docs and lawyers (as a techie, IASNAL), I didn't find a scrap of it relevant to software licensing, employment contracts, stock option agreements, or confidentiality agreements. You may find it entertaining, but it's not going to help you deal with the legal issues that you come across in the real world.
The more people who think they know the law but are unaware of its subtleties and precedants make for a less intelligent exchange of ideas and more "I know what I'm talking about, listen to me, not them" type of exchanges.
I know this for two reasons: I come from a family of lawyers and legal experts, and I tend to fall into the "I'm correct, damnit!" category I just mentioned. Therefore, I'm usually shot down by the legal minds in my family, even when I'm being particularly intelligent in my own right, or *cough* quoting a piece of "+5 Insightful" legal advice gleaned from slashdot.
There is no substitute for a real legal education and pursuing real-world applications (be you a judge, law professor, trial lawyer or law clerk). I guess what I'm really attempting to say is that thinking you know something is no replacement for actually knowing that thing. Not that having a law degree makes you eligable to offer legal advice (I wouldn't ask an IP lawyer for help with closing on a house), but it does place you in better standing.
Use this article to help you better understand the legal document you are reading, do NOT use it to further legal advice to others -- that is not what this article, or any other like it, is meant for.
</rant>
---
"Of course, that's just my opinion. I could be wrong." --Dennis Miller
What we really need is a tutorial on GeekSpeak for lawyers. That would teach them things like:
I enjoyed the article, but I dislike the fact that this tends to enforce the idea that code==law.
Code isn't law. Protocols are like law. Code that follows (or breaks) the protocols is not law, but more like agents under the law. Saying that code==law is like saying that drivers are the motor vehicle code.
Now, certainly it should be illegal to misrepresent code as being compliant to a protocol when it isn't (e.g., MSFT Kerberos). However, the code itself shouldn't be illegal--only the misrepresentation.
The distinction is important, because certain Free Software zealots are trying to use the code==law argument to convince people that software should be Public (they like to say Free when what they really mean is Public, like the Public School System), and perhaps even that private software should be outlawed.
For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?