Pros and cons of contributing data public domain

From OpenStreetMap Wiki
Jump to navigation Jump to search

two merging arrows

It has been proposed that this page or section be merged with Optional public domain licensing. (Discuss)

This document is a work in progress - Consider improving

OpenStreetMap's license is a free share-alike license. I.e. you are more or less allowed to do what ever you want with OpenStreetMap's data under the one condition that you agree that any modifications or additions again are under the same free license.

In the eyes of many people, this share-alike clause - which limits your freedom in certain ways - is necessary for a greater good, which is generally seen as spreading the freedom and openness of data. The plan is to force people (rather than just encourage them) to contribute improvements back so that anyone can benefit from them just like they benefited from OpenStreetMap.

Other people however think that this forced share-alike property is an undesirable reduction of freedom, and would thus rather see their contributions under a full free for all, or Public Domain license. The question of share-alike vs public domain is mostly a question of personal taste and often very controversially debated. For every "reason for PD" that you find listed below, there is also a "reason against PD", and it is unlikely that both sides will ever agree. Thus OpenStreetMap gives its users a choice to express their personal preference on this topic.

If you declare your contributions to be in the Public Domain, you are thereby making a statement only. You will not actually be changing the license or what people can do with your data, because database law still overrides the protection of individual items. People will have to adhere to ODbL when they want to use OSM, even if a majority of contributions should be declared PD. But nonetheless such statements can be powerful. How many people choose the PD option will influence the way we think about OSM licensing in the future. Nothing is ever black and white; even ODbL can be enforced strictly or handled leniently. By selecting the PD option, you basically say: "Do this ODbL thing if you must but don't go over board with it, I consider my contributions PD and would rather get mapping than think about what is allowed and what not."

Public Domain is the idea that a work can exist without anyone claiming any rights to it. In some jurisdictions you can create something and place it in the Public Domain explicitly; in other jurisdictions your right as an author cannot be signed away, so in these jurisdictions Public Domain is understood as a shorthand for "Yes I may be the author of that but you just do whatever you please with it." (In lawyer's terms this sounds something like "I grant anyone a permanent and irrevocable license to use my work for any purpose, without any conditions, unless such conditions are required by law.").

Declaring your contributions to be public domain is up to your free choice. Not selecting this option will not prevent your account creation or effect your contributions to OSM negatively in any other way.

Reasons why some people consider Public Domain superior to more restrictive forms of licensing, while others prefer more viral style licensing, include:

Practical reasons for PD

  • PD is simple for users and providers of data. Users need not be concerned with legal details, and providers need not spend time to find out whether a certain use case is acceptable. ODbL is the best license that a number of very good people could come up with, but it still is a complex piece of work to laymen and professionals alike; there are a number of use cases where it is very hard to determine from the license alone whether they are allowed or not. Thus, additional documentation has already been provided on subtle questions like "what is a database", "what is a substantial extract" and so on, and this will have to be maintained and refined in the future.
  • PD aims to be fair. The aim of releasing data into the "Public Domain" is for the geodata to be usable by everyone all over the planet in exactly the same fashion. Under ODbL, certain use cases of our data are possible in some countries of the world and not possible in others. The likelyhood of someone "getting away" with an ODbL violation in the USA is different from the likelyhood of getting away with the same violation in Europe because the legal concepts ODbL has to employ are different in these jurisdictions, dependent on if they have "database law".

Practical reasons against PD

  • PD is fairer to some more than others, as some could use this as the basis for their map data and extend it with their own data and not give back anything to the thousands of people that gave in contributing in the first place when they publish their map on the internet.

Moral reasons for PD

  • Releasing your data PD means that you opt out of the "intellectual property game". Rather than fighting owners and purveyours of proprietary data (like map data providers, record labels, or film studios) on their own terms by using copyright or database right to force people to adhere to your conditions, someone who goes PD asserts, by example, that knowledge and data should be free and not encumbered by EULAs, lawyer work and the like, no matter how well-intended these rules are.

Moral reasons for not PD'ing

  • Releasing your data under ODBL/DBCL requires anyone improving the data to give back changes, under PD no such requirement exists so while your work might "opt out of the intellectual property game" the next person to come along can simply take your work, extend it and claim it as their own and the data immediately enters the intellectual property game under that person's rules instead of yours. Your data will remain in the public domain.
  • By requiring changes be given back to the community at large this then helps foster better competition via services, privacy and other offerings from map companies by giving everyone a level playing field from starting with a consistent data set.

Also See