Changes

= License =

= License =

== Data license ==

== Data license ==

Our data content (in the Item and Property namespaces) is covered by the Creative Commons CC0 Waiver (see {{Q|38}}), which states that you are free to share (copy, distribute and transmit) and remix (adapt) the work. '''Our [[Project:Terms_of_use|terms of use]] covers the ethical and social norms for attribution that we expect from research, journalistic and activist communities'''. For any reuse or distribution, we would appreciate that you make clear to others the CC0 terms for the work. The best way to do this is with a link to this web page. Again, this license is fairly permissive, so you shouldn't feel paralyzed by legalese if you are interested in using or redistributing our data content. Just be sure to read the [[Project:Terms_of_use|terms of use]] and if you have any questions about fair use, don't hesitate to contact us. A detailed FAQ on CC0 can be found [https://wiki.creativecommons.org/wiki/CC0_FAQ here], which was written by the Wikimedia community.  

Our data content (in the Item and Property namespaces) is covered by the Creative Commons CC0 Waiver (see {{Q|38}}), which states that you are free to share (copy, distribute and transmit) and remix (adapt) the work. '''Our [[Project:Terms_of_use|terms of use]] page covers the ethical and social norms for attribution that we expect from research, journalistic and activist communities'''. For any reuse or distribution, we would appreciate that you make clear to others the CC0 terms for the work. The best way to do this is with a link to this web page. Again, this license is fairly permissive, so you shouldn't feel paralyzed by legalese if you are interested in using or redistributing our data content. Just be sure to read the [[Project:Terms_of_use|terms of use]] and if you have any questions about fair use, don't hesitate to contact us. A detailed FAQ on CC0 can be found [https://wiki.creativecommons.org/wiki/CC0_FAQ here], which was written by the Wikimedia community.  

=== Why not a copyleft license on data? ===

=== Why not a copyleft license on data? ===

We came to the conclusion that this was the best licensing model after some hesitation. This hesitation stemmed from the hope that it would be possible to construct a copyleft data license, or reuse the only existing one ({{Q|1583}}). We became convinced this was futile and thus a bad idea through reading these references: {{Q|2008}}.

We came to the conclusion that this was the best licensing model at this stage after some hesitation. This hesitation stemmed from the hope that it would be possible to construct a copyleft data license, or reuse the only existing one ({{Q|1583}}). We became convinced this was futile, at least for now, and thus a bad idea through reading these references: {{Q|2008}}. This decision is - in this direction at least - reversible. We can switch to a copyleft license later.  

We want to highlight a key quote from {{Q|2906}}:

We want to highlight a key quote from {{Q|2906}}:

=== But you could have used my favorite license instead! ===

=== But you could have used my favorite license instead! ===

This is unlikely:

This is unlikely:

* '''ODbL''' (copyleft database licensed, used by OpenStreeMap):  

* '''ODbL''' (copyleft database licensed, used by OpenStreeMap), had - [https://joemorrison.medium.com/openstreetmap-is-having-a-moment-dcc7eef1bb01 until very recently but it might be changing] - not had a successful run. See this quote:  

{{Quote

{{Quote

|text=

|text=

ODbL is probably the most blatant example of this: even at the time, Science Commons correctly pointed out that ODbL’s attempt to create database rights by contract outside of the EU was a bad idea.

ODbL is probably the most blatant example of this: even at the time, Science Commons correctly pointed out that ODbL’s attempt to create database rights by contract outside of the EU was a bad idea.

Unfortunately, well-intentioned people (including me!) pushed it through anyway. Similarly, open hardware proponents have tried to stretch copyright to cover functional works, with predictably messy results."

Unfortunately, well-intentioned people (including me!) pushed it through anyway. Similarly, open hardware proponents have tried to stretch copyright to cover functional works, with predictably messy results."

|author={{Q|2906}}, one of the authors of the ODbL, who worked for OpenStreetMap at the time}}

|author={{Q|2906}}, who worked for OpenStreetMap at the time}}

* '''CC-BY-SA''' is likely to work against your goals if you are based in Europe and select countries:  

* '''CC-BY-SA''' is likely to work against your goals if you are based in Europe and select countries:  

{{Quote

{{Quote

Note that if you are using a database in a jurisdiction where you must respect database rights, and you receive a CC-licensed work from someone located in a jurisdiction without database rights, you should determine whether database rights exist and have been licensed."

Note that if you are using a database in a jurisdiction where you must respect database rights, and you receive a CC-licensed work from someone located in a jurisdiction without database rights, you should determine whether database rights exist and have been licensed."

|author=[https://wiki.creativecommons.org/wiki/Data#What_constitutes_a_.E2.80.9Csubstantial_portion.E2.80.9D_of_a_database.3F Creative Commons Official FAQ]}}

|author=[https://wiki.creativecommons.org/wiki/Data#What_constitutes_a_.E2.80.9Csubstantial_portion.E2.80.9D_of_a_database.3F Creative Commons Official FAQ]}}

=== Other datasets ===

=== Other datasets ===