Slashdot Mirror
Creative Commons License Upheld by Dutch Court
musicon writes "As seen on Groklaw, a recent court decision upheld the the Creative Commons license in the Netherlands: 'The Creative Commons licenses are quite new, so there has been very little in the way of case law so far, so this is a significant development. The ruling rejected a 'the license wasn't clear' defense, particularly for sophisticated entities, and it upheld the license as binding without the licensee having to agree or even to have knowledge of the terms of the license.' You can read successful plaintiff Adam Curry's blog on the ruling too."
You're liable for copyright infrigement if you copy a copyrighted work, whether or not you knew that work was protected by copyright law.
If in doubt about the license of content, assume it's copyrighted. The CC licenses only grant you rights beyond what copyright does.
The difference, and I'd suggest it is a big one, is that the CC license grants the user EXTRA rights over and above the default copyright situation. "Evil" shrinkwrap licenses take them away.
An individual who doesn't know the precise details of the copyright status on file (because they don't have the license that should accompany it) won't get burned by assuming that the default applies. They just aren't aware of all the things they can do.
"I Know You Are But What Am I?"
But those are bad, and the CC license is good, and they share the same ambush-applicability feature.
I'm sure it's because I'm too simpleminded to comprehend the difference, but it seems to me that poison for the goose ought to be poison for the gander.
Not simple-minded. You just don't know how the license works. Just a lack of information, which is not a bad thing, and easily remedied. To wit:
CC licenses do not restrict the behavior of anyone who obeys traditional copyright. That is, you cannot, without authorization, redistribute the copyrighted material. In this case, the magazine in question did redistribute the material in question.
So what does the CC license have to do with it then? isn't it a simple copyright case?
In this case, the owner of the copyrighted material offered additional rights. The owner effectively said, "Under certain conditions, I will grant you authorization to redistribute this material."
That is, copyright says what you can and cannot do with the material, and you are free to treat CC'd material 100% according to copyright law. No problem.
If, however, you would like to do something that is not allowed by copyright law but is granted by the CC license, then you must abide by the conditions set out in the license.
Shrinkwrap agreements are different. They say that you are not allowed treat the product according to copyright law.
Stop-Prism.org: Opt Out of Surveillance
Show #351, specifically.
A Copyright is a license that applies to a work and allows the copyright holder to dictate the circumstances upon which a work may be copied. Examples of copyrights are the GPL, LGPL, Creative Commons, and the good old "All rights reserved" which is the default. A copyright can ONLY state conditions regarding copying. It cannot state anything about reverse-engineering, reselling, writing reviews of the product, disclosing benchmarks, etc.
A Contract is a license that applies to anything at all and allows the two parties to agree to anything at all, but requires legally-binding proof that both parties agree (such as a signature, witnesses, etc). Examples of contracts are employment contracts, purchase orders, etc. A contract can state anything. In the case of software, a contract could state that the user cannot reverse-engineer it, publish benchmarks about it, write revews, etc.
Granting of rights:
Suppose I write some software, copyright it, and I give you a copy. You can do anything you want with it EXCEPT copy it.
A copyright grants rights to the consumer. My copyright could say that "The author grants you the right to make infinite copies" or "The author grants you the right to make copies so long as you include the source code" or "The author grants you the right to make copies so long as you don't reverse-engineer it." In neither case did copyright place any restrictions upon you. You can still reverse-engineer the software if you want! You just can't copy it if you do.
A contract removes rights from the signer. If I make you sign a contract, that contract could say that "The author denies you the right to reverse-engineer this software." In this case the contract took away a right you already had. You can't reverse-engineer the software at all.
Your original question - why is this good news? Yes, the CC license is good because copyrights are good, because they grant rights to the users of the work. You buy the product from the store without knowing about the copyright. So you must assume you cannot copy the product at all in any way because that is the default rights you have. But you open the package and are ambushed with the good news that it is GPL so you CAN copy it so long as you give out the source code along with it. Yaaaay!
But shrink-wrap licenses are bad because you buy the product from the store without knowing about the license. So you assume that you can reverse-engineer the application and write a benchmark on it. But you open the package are are ambushed with the bad news that you CANNOT benchmark it or reverse-engineer it. Booo!
Adam Curry was one of the first MTV VJs. You can hear his podshow and a bunch of his MTV colleagues on Sirius Satellite radio.
Where does the school board find them and why do they keep sending them to ME?
Not to mention that the CC licenses have that nifty little "actual, human-readable English" version as well as the legalese. Anyone failing to understand the legalese, fair enough, but "You may copy this content and reproduce it, but not for profit" (or whatever) couldn't get much clearer.
How are sites slashdotted when nobody reads TFAs?
Well.. the creative commons licence is available in a whole bunch of languages.. no problem if you're Dutch..
http://www.creativecommons.nl/