Slashdot Mirror
What Is Public Domain?
whitefox writes: "The Seattle Times has an interesting article in today's edition on what is public domain. After sharing the experience one software writer had with businesses and people shying away from BitTorrent because they didn't understand the concept of 'public domain,' they take the reader on a tour of how public domain is being defined by groups such as Creative Commons and to the battle of copyright-extensions in Eldred v. Ashcroft."
They do.
However, public domain is a larger issue than that, and a very important one. Copyright law was originally drafted for the express purpose of enhancing the public domain, not destroying it, as recent laws have done.
LedgerSMB: Open source Accounting/ERP
Jessica Litman wrote an excellent book Digital Copyright, which I recomend everyone read.
In the book she references a discussion of copyright lawyers, many of whom hold the opinion that it is not legally possibla to place works in the public domain.
The problem with copyright is that is tries to accomplish two things: control distribution and maintain authenticity. These two goals need to be split up so that creative persons may choose to limit one or the other, or both, or neither.
For example, this post. I can care less how much this post is distributed. However, I do care that when it is distributed, it is distributed in verbatum, and that I am not bein misrepresented. I want to be able to control the authenticity of a work (to protect myself from libel and misrepresentation and plagarism, and to allow myself to receive credit for first stating an idea), but I do not want to inhibit the discussion or distribution of this post.
Another example - the ideal academic journal would allow me to maintain authenticity of my writings (so I can be credited with a discovery or recognised as an authority on a topic based on my work), but place no restrictions on the distribution of my academic publications. That way, more people can hear about my ideas and comment on them and build on them and apply those ideas.
Another example - a composer could write a song. Authenticity rights are granted. Distribution rights (or time-limited exclusive commercial distribution) are negotiated with a corporation willing to print CD's and ship them to stores around the world.
Maybe these are just rambling - post your comments below
The significant problems we face cannot be solved by the same level of thinking that created them. -Einstein
If not, maybe some of the movie copyrights can be invalidated -- don't you love irony?
Lauren Vanpelt has done the math and found that Mickey Mouse has already fallen into the public domain due to a faulty copyright notice. (Back then, "© 1929" wasn't enough; it had to be "© 1929 Walt Disney".)
Therefore, because there is a public domain DVD encrypted with CSS, and because the DMCA's circumvention ban (17 USC 1201) affects only "works protected under this title" (i.e. copyrighted works), DeCSS is now legal if marketed only to decrypt public domain content on DVDs (1201(a)(2); 1201(b)(1)). Good news for Charlie Chaplin DVD collectors.
Sonny Bono hit that tree, the concept of a vibrant public domain died.
Will I retire or break 10K?
Thankfully, I haven't gotten a single piece of mail pestering me about the license since I switched away from public domain, even though MIT is almost as permissive.
I did do one slightly controversial thing - I capitalized the legal discraimer properly. Usually it's all caps, which I think is ugly and pointless. I did leave the part where it says "AS IS" in caps though.
BitTorrent development, by the way, is proceeding apace. The first mature release, with a finalized protocol and no phoning home on startup to make sure it's still a current version, will probably be released within the next few weeks.
I would put most of my source code in the Public Domain, if I could.
I can't.
Not "I won't".
I *can't*.
My problem is that, without a license, I can't attach a "hold harmless", or prevent my name being used to sell code derived from it, but of which I personally would not approve.
So to keep rights to my good name, and protect myself (as much as possible) from litigation arising from the use of my gifts to the public, I have to attach the minimum possible license that still gets me these things (the BSD license).
It's not that I *want* to do this, it's that there are no implicit legal protections for the authors of works placed into the public domain.
Without such legal protections, I simply can't *afford* to make the gifts that I want to make to the public.
It's just too dangerous.
-- Terry
No. The GPL is expressly and explicitly not public domain.
The GPL grants a limited set of rights in exchange for a defined set of obligations. The copyright holder retains ownership.
Public domain grants nothing. The creator of a public domain work renounces all ownership or, by expiration of rights, loses ownership. Without ownership, you can not impose conditions.
That is what makes the public domain the only truly "free" province of Intellectual Property.
The GPL diverges from the public domain in order to insure certain behaviors that its drafters consider vital to the vitality of free software. They have placed limitations on some freedoms in order to protect others.