Licence/About The Licence Change
About The OpenStreetMap License Change
The OpenStreetMap project is moving to a new license, known as the Open Database License (ODbL) which will replace the existing Creative Commons CC-BY-SA 2.0 license due to problems with the CC-BY-SA license when applied to data. The license is intended to clarify the terms under which people make contributions to the project and the terms under which people can use the data. It is a basically a share alike license for data.
The Foundation supports the adoption of this license and has reviewed it with their lawyers.
The license remains firmly rooted in the attribution, share-alike provisions of the existing Creative Commons License but the ODbL is far more suitable for open factual databases rather than the creative works of art. It extends far greater potential protection and is far clearer when, why and where the share-alike provisions are triggered. There are further reasons for moving away from CC BY-SA here.
Where we are now
OPENSTREETMAP DATA IS NOT YET AVAILABLE UNDER THE NEW LICENSE.
On Wednesday 5th September, the board of the OpenStreetMap Foundation resolved that the license change should go ahead. This was announced at State Of The Map Conference, Thursday 6th September. The exact date and time of the change-over will happen when our next planet dump, (a single publicly downloadable XML-based compressed file of our entire database) is published. This is likely to happen in the next few days.
Prior copies of the database will be continue to be available under CC BY SA as long as there is demand.
Our implementation plan provides more information about the history of the change-over process.
If you are looking for a final set of all the documents, here they are:
- Contributor Terms - Individual contributors need to agree to these terms before contributing.
- Human readable summary of the Contributor Terms
- Database Contents License (DbCL) - Contributors waive all rights in the individual Contents of a Database licensed under the ODbL. In the text, 'Licensor' means the contributor and 'You' means the Foundation. This effectively means that end users of data published by the Foundation need to study only the ODbL rather than worrying about any special copyrights on individual elements of the database.
- Open Database License (ODbL) 1.0 This is the license under which the Foundation will publish the entire geodata set. End users of OpenStreetMap need to comply with this license.
- Human readable summary of the ODbL license
-  - Some of the terms in the ODbL need further clarifying in terms of geodata. This is a guide to end users created by the OpenStreetMap contributor community. It will evolve over time.
- 'We Are Changing The License' - Existing contributors will be asked to re-license their data under the new license, this gives them an overview of why.
- 'License Change Proposal' - this document is out-dated by gives a fuller overview of the perceived need for a license change and the primary goals.
- 'Why would I want my contributions to be public domain'. When new contributors sign-up, they can optionally tick a box "I consider my contributions to be in the Public Domain". This document gives them more information.
History of Acceptance and Implementation Process
Over a two year period, the OpenStreetMap has worked with Open Data Commons to create the ODbL license itself and then to create internal Contribtutor Terms and other subsidiary documents.
The Foundation's License Working Group presented a proposal document to the members, who accepted it by vote in December 2009. A summary was also presented at the State Of The Map 2009 conference. This process is documented here. We also welcome any review and comment by other bodies working in the open intellectual properties rights arena, and have published an open letter asking for their views.
OSMF members have voted on whether they wish to put the current version of the new license to the community for adoption and then begin the adoption process itself. The results from 270 members polled are:
|Approved the process:||132|
|Did not approve the process:||16|
More information including use cases and open issues is available on the OSM wiki.