Open Data Licensing
Back at the end of September we finally got to the point of releasing the first draft of the Open Data Commons License. This is work I've been involved in since Ian's first draft of the TCL about a year and a half ago.
It's great to see this license come to fruition, having argued about the need for this more than once.
It's interesting to see the conversation happening around LibraryThing's Common Knowledge and the Open Library project. Both of these are collections of factual data, I've been speaking to people involved in both and both have a clear desire to protect the data and ensure that it's available for the community into the future.
Licensing is critical to that - as I said in Banff (listen) at the start of the year.
Back then we were concerned with navigating the difference in protection afforded to database in the EU and the US. In essence, databases have protection in the EU, but have no protection on the US. The reason we were looking at that was because the natural thinking goes something like this:
Creative Commons extends Copyright to allow you to easily position yourself on the spectrum of 'All Rghts reserved' to 'Public Domain'.
Therefore Open Data Commons must need to extend a Database Right to allow to position your data on the same spectrum.
Well, the Open Data Commons license gets around that by being couched in contract law. This seems like a great way to license data for open use and prevent it being locked away in future.
With all that's been going on then, it's no surprise that I missed the Model Train Software case that could have a big impact on how Open-Source software licenses are drafted. A San Francisco judge ruled that the Artistic License was a contract - meaning that breach of the license did not necessarily mean infringing the copyright. That changes the legal redress and potential penalties available for breaching a license.
Technorati Tags: licensing, open-data, open-source, opendatacommons, law