Is Putting Change.gov Under Creative Commons Really A Big Deal?
from the help-me,-I'm-missing-something... dept
There's been plenty of attention paid to the news that the website for President-Elect Obama's transition team, Change.gov has been placed under a Creative Commons license, allowing others to make use of the content with attribution. However, I'm a bit hard pressed to see how this actually is a big deal. The whole thing is made a bit odd by the fact that federal government content is not covered by copyright, so anything that comes out of the White House is in the public domain. But, apparently since Obama has not yet been inaugurated, the campaign can still claim copyright on the content. But, why would they? Rather than going with a CC license, why not go all the way and put the content in the public domain? After all, in two months, all such content will be in the public domain anyway? It seems a little odd, counterproductive and unnecessary to add more restrictions to the content than there will be once Obama is actually in office. If the Obama team really wanted to do something meaningful concerning the content on the site, they could follow the advice of Tim O'Reilly and go beyond just putting the content in the public domain and also add revision control, thereby committing to alerting people to any changes to the content. Now, that would be an impressive change.Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Filed Under: change.gov, copyright, creative commons, obama, public domain
Reader Comments
Subscribe: RSS
View by: Time | Thread
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
They want to control the content
[ link to this | view in chronology ]
Re: They want to control the content
[ link to this | view in chronology ]
Re: They want to control the content
[ link to this | view in chronology ]
Re: They want to control the content
[ link to this | view in chronology ]
User generated content and CC
Putting aside the issue of whether Obama's transition 501(c)4 corporation is entitled to copyright protection, the CC license choice matters for another reason: the general public should have the right to use the work created by citizens that is submitted to the site.
Because Change.gov now requires that all work be licensed under CC's Attribtuion license, it clears the way for the government and other citizens to build upon it without complications.
Instead of creating an onerous one-off Terms of Service forcing users to abdicate exclusive rights to their content, Change.gov simply drew a line in the sand (as Wikipedia and other free culture communities do) and ask users to agree to letting their work be free.
This policy also avoids asking thousands of citizens to relinquish all control over their work to the public domain.
Fred Benenson
Outreach Manager, Creative Commons
[ link to this | view in chronology ]
Credit where credit is due
I would speculate that the reason they went with CC is that a lot of the people who contributed want their name to get out there, so allowing the use of their work with attribution helps them, by making their name more recognizable. So in 4 years, when its time for another campaign, they can get a job easier with one of the lead dogs.
"Look at me. I helped put Obama in the white house. I can do the same for you."
[ link to this | view in chronology ]
Tax
[ link to this | view in chronology ]
Attribution No Derivatives
[ link to this | view in chronology ]
I'm Surprised You Even Have To Ask The Question
Nobody of sound mind and body should be putting anything in the public domain unless they are somehow covered against liability for doing so. Our society is too litigious, and while stock warranty disclaimers are fairly thin as a defense, they're better than nothing.
Given that, the CC-Attribution license has the fewest restrictions of any of the CC licenses, and it's probably better to use a CC license than to whip up yet another license.
[ link to this | view in chronology ]
Re: I'm Surprised You Even Have To Ask The Question
Nobody of sound mind and body should be putting anything in the public domain unless they are somehow covered against liability for doing so. Our society is too litigious, and while stock warranty disclaimers are fairly thin as a defense, they're better than nothing.
What an incredibly sad statement.
No offense, but to me that's the death of the entire reason for public domain works, to claim that putting stuff in the public domain leads to liability. I sincerely hope the world never actually reaches such a ridiculous point. That would truly be a sad state of affairs.
[ link to this | view in chronology ]
Re: Re: I'm Surprised You Even Have To Ask The Question
More accurately, failing to disclaim liability leaves you less protected than if you do disclaim liability. Since public domain offers no means of disclaiming liability (AFAIK), public domain is a riskier proposition than choosing a liberal license that contains warranty disclaimers.
I have had multiple "intellectual property" attorneys tell me as much with respect to public domain software -- you are better served using a liberal license that contains the warranty disclaimer. It won't harm use of the software, and you have at least some measure of protection against liability suits. While I can see greater odds of liability suits with "active" written works like software than ordinary prose, the principle still holds.
If you feel that CC-Attribution is still too restrictive, I encourage you to work with the Creative Commons to cook up a warranty-disclaimer-only license.
Um, we've been there since the invention of copyright and liability. All that's changed are the odds and impacts.
[ link to this | view in chronology ]
Clarification
[ link to this | view in chronology ]
Copyrighted by Default
What this really all means, as mentioned by others, is that there is someone in or working for the new administration that "gets it" when it comes to the modern internet world and economy.
[ link to this | view in chronology ]