Licenses

Menu

Loading wiki pages...

View
Wiki Version:
<h1>Introduction and license of this document</h1> <p>When publishing products of a scientific endeavour, it is wise to make a deliberate choice as to which license you wish to instate. This document is meant to provide a brief introduction intro licensing.</p> <p>This document is written by Gjalt-Jorn Peters and licensed under the Creative Commons Zero license (CC0; click <a href="https://creativecommons.org/publicdomain/zero/1.0/" rel="nofollow">this link</a> for more information). If you would like to contribute, please use <a href="http://help.osf.io/m/collaborating/l/878767-request-access-to-a-public-project" rel="nofollow">OSF's "Request Access" functionality</a> so you can edit this wiki page.</p> <h1>License basics</h1> <p>A license governs what people are allowed to do with a product. Licenses are intended to save time and effort: people will know the rights they have without having to bother you. However, licenses don't normally restrict <em>you</em> from granting additional rights. As a backdrop for the discussion of licenses, it is useful to start with the two most well-known licenses, because these can be considered useful extremes on the 'licensing scale'.</p> <h2>Public domain</h2> <p>The first one is the most basic license, and its existence is more a formality than anything else: the so-called Public Domain license. If something is in the public domain, that means everybody can do with it whatever they want (within legal constraints; see Other Information at <a href="https://creativecommons.org/publicdomain/zero/1.0/" rel="nofollow">this page</a>). If intellectual property law would not exist, everything that would be produced or invented would be in the public domain. So, on the one hand this "public domain license" is definitely the license most people are most familiar with; but on the other hand, most people will not even be aware that this is a license. The public domain license can be considered the most 'permissive' license: it's the license with the least restrictions imposed.</p> <h2>Copyright</h2> <p>Intellectual property (IP) law turns things around (in most countries) by introducing the second well-known license: copyright. IP legislation usually holds that anything that is produced is copyrighted by the creator unless specified otherwise (data being the notable exception; data are defined as facts, and <a href="https://www.newmediarights.org/business_models/artist/are_facts_copyrighted" rel="nofollow">facts cannot be copyrighted</a>, but are legally defined as existing in the public domain in most jurisdictions). The copyright license is the opposite of the public domain license, in that it is one of the least permissive licenses. It basically gives the creator of a product the exclusive rights to determine whether, and under what conditions, a product can be used by others. Therefore, unless accompanied by such a specification, this means that the product cannot be used by anybody else (unless this falls under, for example, 'fair use').</p> <h2>Creative Commons</h2> <p>The Free and Open Source Software community has already spawned a number of other licenses (such as the MIT license or the Apache license), but these were quite specifically geared towards software. In 2002, the <a href="https://creativecommons.org" rel="nofollow">Creative Commons</a> licenses were published, which make it easy to license your work more permissively than under the traditional copyright license, in a way that's accessible but flexible, without needing to consult a lawyer. These licenses are very applicable to products of a scientific endeavour. These licenses combine four specific (limitations to) rights and conditions:</p> <ul> <li>Attribution (BY): Anybody using the product must attribute the original creator.</li> <li>No derivative works (ND): Nobody may take this product and change it; so it may only be copied/distributed 'as is'.</li> <li>Non-commercial (NC): This product may not be copied, distributed or altered for commercial purposes.</li> <li>Share-Alike (SA): This product may be copied, distributed, and changed, but any derivative products must be published under the same (Share-Alike) license. This boils down to a 'pay it forward' model of sharing.</li> </ul> <p>These features combine into six specific licenses (and a 'name' for releasing something into the public domain):</p> <ul> <li>CC-BY: Attribution</li> <li>CC-BY-ND: Attribution-NoDerivs</li> <li>CC-BY-NC: Attribution-NonCommercial</li> <li>CC-BY-SA: Attribution-ShareAlike</li> <li>CC-BY-NC-SA: Attribution-NonCommercial-ShareAlike</li> <li>CC-BY-NC-ND: Attribution-NonCommercial-NoDerivs</li> <li>CC0: You can use this license to release something into the public domain (i.e. waiving all rights).</li> </ul> <p>These Creative Commons licenses are listed <a href="https://creativecommons.org/licenses/" rel="nofollow">here</a>.</p> <h1>Links to more information</h1> <p>Lists of licenses:</p> <ul> <li><a href="https://creativecommons.org/" rel="nofollow">https://creativecommons.org/</a></li> <li><a href="https://choosealicense.com/" rel="nofollow">https://choosealicense.com/</a></li> <li><a href="https://opensource.org/licenses" rel="nofollow">https://opensource.org/licenses</a></li> </ul>
OSF does not support the use of Internet Explorer. For optimal performance, please switch to another browser.
Accept
This website relies on cookies to help provide a better user experience. By clicking Accept or continuing to use the site, you agree. For more information, see our Privacy Policy and information on cookie use.
Accept
×

Start managing your projects on the OSF today.

Free and easy to use, the Open Science Framework supports the entire research lifecycle: planning, execution, reporting, archiving, and discovery.