Techdirt’s Mike Masnick is perhaps the most prolific blogger on the ill impact of overly restrictive legal regimes ...
So it’s a little disappointing to read Masnick write:
I don’t use any of their licenses, because I don’t necessarily see the point. We’ve declared in the past that the content here is free for anyone to do what they want with it, and thus I feel no need for a Creative Commons license.
The need arises from the reality that sharing without standardized legal tools doesn’t scale. It doesn’t scale socially — if I wasn’t a regular Techdirt reader I wouldn’t know that Masnick had declared Techdirt content is free for anyone and for any purpose ... nor depending on wording would I know what that meant. It doesn’t scale technically — there’s no way for software such as search engines to recognize ad hoc declarations. It doesn’t scale legally — any community or institution that requires legal certainty (eg due to risk that the community’s work will be suppressed or that the institution will be financially liable) will avoid ad hoc declarations.
It’s no surprise that in the more developed field of free and open source software (which has a 10+ year head start on free culture/open content) anyone who claims that making an ad hoc declaration is good enough and did not release their code under an established license would be laughed at and their code not allowed in other projects, distributions, and repositories, not to mention getting no attention from IBM, Google, Red Hat and thousands of other corporate contributors to and adopters of open source software. ...
Posted by
Gavin Baker at 9/03/2009 08:08:00 PM.
The open access movement:
Putting peer-reviewed scientific and scholarly literature
on the internet. Making it available free of charge and
free of most copyright and licensing restrictions.
Removing the barriers to serious research.
I recommend the OA tracking project (OATP) as the best way to stay on top of new OA developments. You can read the OATP feed on a blog-like web page or subscribe to it by RSS, email, or Twitter. You can also help build the feed by tagging new developments you encounter.
