< Import
Import/ODbL Compatibility
This is a matrix for quickly checking compatibility of data released under certain common licenses with the ODbL.
If you are interested in background information and past discussions regarding this topic, one possible source is the legal-talk mailing list archive.
Note that while declared license of dataset may be compatible there may be still problems due to different jurisdiction and/or ignoring copyright issues. For example, Wikidata declares itself to be CC0 but includes location data copied from Google Maps, OpenStreetMap and other copyrighted sources.
Note that any license with commercial use prohibition (for example "The works shall be used only for nonprofit purposes.") or forbidding modification (for example "It is prohibited to modify the work, or change it to create a secondary work.") is clearly incompatible with ODBL.
| License (link to full text or overview) | ODbL compatibility | Contributor Terms compatibility | Notes | wiki.osmfoundation |
|---|---|---|---|---|
| fully compatible licenses | ||||
| OK| | OK | intellectual property rights are expired or forfeited or are not applicable | ||
| OK| | OK | License terms are compatible, but the licenser does not guarantee for it. 4c of the license explicitly states: "Affirmer disclaims responsibility for clearing rights of other persons that may apply to the Work or any use thereof, including without limitation any person's Copyright and Related Rights in the Work. Further, Affirmer disclaims responsibility for obtaining any necessary consents, permissions or other rights required for any use of the Work." | Licence Compatibility - CC0 at wiki.osmfoundation.org | |
| OK| | OK | - | ||
| OK| | OK | - | ||
| compatible but with problems | ||||
| OK | problematic in case of future license change if incompatible new license is chosen | - | ||
| OK | problematic in case of future license change if incompatible new license is chosen | The licence text explicitly says that it is forwards compatible with the ODbL. | ||
| OK | Inherits problem from OGL | 9. Licence compatibility lists OGL 3.0 as compatible. | ||
| not OK but might be 'fixable' | ||||
| incompatible attribution requirements and other terms | problematic in case of future license change if incompatible new license is chosen | Terms have never been vetted for inclusion in OSM | ||
| incompatible attribution requirements and other terms | problematic in case of future license change if incompatible new license is chosen | Read this LWG blog post for their evaluation of CC-BY 4.0 | ||
| incompatible attribution requirements and other terms | problematic in case of future license change if incompatible new license is chosen | Read this LWG blog post for their evaluation of CC-BY 4.0 | ||
| incompatible attribution requirements and other terms | problematic in case of future license change if incompatible new license is chosen | Read this LWG blog post for their evaluation of CC-BY 4.0 | ||
| likely incompatible attribution requirements and other terms; additional waivers required for reasonable attribution and unrestricted distribution | problematic in case of future license change if incompatible new license is chosen | Read this LWG blog post for their evaluation of CC-BY 4.0 and why an additional agreement (see the cover letter and waiver form) is requested. | ||
| not OK and likely not 'fixable' | ||||
| incompatible share-alike and attribution requirements | problematic in case of future license change if incompatible new license is chosen | cannot be made ODbL compatible, consider contacting rights holder(s) for explicit permission to integrate data into OSM | ||
| incompatible share-alike and attribution requirements | problematic in case of future license change if incompatible new license is chosen | cannot be made ODbL compatible, consider contacting rights holder(s) for explicit permission to integrate data into OSM | ||
| incompatible share-alike and attribution requirements | problematic in case of future license change if incompatible new license is chosen | cannot be made ODbL compatible, consider contacting rights holder(s) for explicit permission to integrate data into OSM | ||
| incompatible share-alike and attribution requirements | problematic in case of future license change if incompatible new license is chosen | cannot be made ODbL compatible, consider contacting rights holder(s) for explicit permission to integrate data into OSM | ||
| incompatible share-alike and attribution requirements | problematic in case of future license change if incompatible new license is chosen | cannot be made ODbL compatible, consider contacting rights holder(s) for explicit permission to integrate data into OSM | ||
| incompatible non-commercial and attribution requirements| | incompatible because right of commercial use is not granted | cannot be made ODbL compatible, consider contacting rights holder(s) for explicit permission to integrate data into OSM | ||
| incompatible non-commercial, attribution and no derivative works requirements| | incompatible because right of commercial use and to modify data is not granted | cannot be made ODbL compatible, consider contacting rights holder(s) for explicit permission to integrate data into OSM | ||
| incompatible non-commercial, attribution and share-alike requirements| | incompatible because right of commercial use is not granted | cannot be made ODbL compatible, consider contacting rights holder(s) for explicit permission to integrate data into OSM | ||
| incompatible no derivative works and attribution requirements| | incompatible because right to modify data is not granted | cannot be made ODbL compatible, consider contacting rights holder(s) for explicit permission to integrate data into OSM |
This article is issued from Openstreetmap. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.