Add a few resources on licensing

choose_license.qmd

@@ -89,7 +89,7 @@ One solution is to make such a work simultaneously available under two (or more)
 > The Quarto files in this project are made available under CC0\ 1.0 or (at your option) under the terms of the Apache Software License\ 2.0.
 :::
 
-Note, that for data there is, at least in principle, the possibility that a different license applies to the individual entries than to the collective database. For example, if you were to create a database of artworks by others, those artworks would be licensed individually as chosen by the artists, but the license for the database as a whole could be chosen by you. The latter includes the selection of entries, field names and any _sui generis_ database rights. However, if the content was created by you, we recommend you to choose the same license for both content and database. Factual data (like measurements or metadata) should be licensed under [CC0\ 1.0](https://creativecommons.org/publicdomain/zero/1.0/) -- otherwise, consult @nte-other-work-types for some caveats.
+Note, that for data there is, at least in principle, the possibility that a different license applies to the individual entries than to the collective database. For example, if you were to create a database of artworks by others, those artworks would be licensed individually as chosen by the artists, but the license for the database as a whole could be chosen by you. The latter includes the selection of entries, field names and any _sui generis_ database rights. However, if the content was created by you, we recommend you to choose the same license for both content and database. Factual data (like measurements or metadata) should be licensed under [CC0\ 1.0](https://creativecommons.org/publicdomain/zero/1.0/) [@Villa2016Copyleft; @Villa2016CC0] -- otherwise, consult @nte-other-work-types for some caveats.
 
 ::: {#fig-flowchart-simple}
 ```{mermaid}
@@ -168,7 +168,7 @@ From the Creative Commons licenses, only [CC0\ 1.0](https://creativecommons.org/
 ::: {#nte-silos .callout-note collapse="true"}
 ### Other Restrictions
 
-As indicated before, a free/open license must allow creating derivative works and must allow exercising the rights granted by it _for any purpose_, including commercial use. There are a few good resources on the reasoning behind that [e.g., see @Klimpel2013; @ODI2015; @Stallman2022NoLimit; @Moller2023], but we would like to highlight one reason in particular.
+As indicated before, a free/open license must allow creating derivative works and must allow exercising the rights granted by it _for any purpose_, including commercial use. There are a few good resources on the reasoning behind that [e.g., see @Klimpel2013; @ODI2015; @Stallman2022NoLimit; @Moller2023; @Vezina2020; @WikimediaCommons2009], but we would like to highlight one reason in particular.
 
 With the rights provided by free/open licenses comes the possibility to build on and combine multiple works by different authors, which is essential for any cultural and scientific activity. However, this is only possible if the various licenses involved are compatible with each other. For example, one is allowed to remix two figures if the first is licensed under CC\ BY\ 4.0 and the second under CC\ BY-SA\ 4.0 because the licenses were written to be compatible with each other [compare @CC2024FAQ]. Also note that CC\ BY-SA\ 4.0 is [one-way compatible](https://creativecommons.org/compatiblelicenses) with the GPLv3, which in turn is compatible with the AGPLv3.
 
@@ -190,7 +190,7 @@ Having selected the licenses of your choice -- again, you might need multiple on
 ::: {#cau-license-versions .callout-caution}
 ### License Versions Are Important
 
-You may have noticed that we mostly refer to licenses using a name _and_ a version number. This is because the organizations that created the licenses sometimes publish updated versions to accommodate for developments in copyright law and the communities that use the licenses. For example, the Creative Commons licenses (that start with `CC`) were first published in 2002. Since then, the possibility to relicense under compatible licenses has been added ([v3.0](https://creativecommons.org/2007/02/23/version-30-launched/)), a 30-day window to correct license violations has been established to combat [copyleft trolls](https://commons.wikimedia.org/wiki/Commons:Copyleft_trolling), and _sui generis_ database rights are covered explicitly ([v4.0](https://creativecommons.org/version4/)). There are many more [subtle differences between license versions](https://wiki.creativecommons.org/wiki/License_Versions), therefore it is important to indicate which license version exactly one is referring to, as the license of a work does not "update" automatically.
+You may have noticed that we mostly refer to licenses using a name _and_ a version number. This is because the organizations that created the licenses sometimes publish updated versions to accommodate for developments in copyright law and the communities that use the licenses. For example, the Creative Commons licenses (that start with `CC`) were first published in 2002. Since then, the possibility to relicense under later ([v2.0](https://creativecommons.org/2004/05/25/announcingandexplainingournew20licenses/#:~:text=Share%20Alike%20Across%20Borders)) and compatible licenses ([v3.0](https://creativecommons.org/2007/02/23/version-30-launched/)) has been added, a 30-day window to correct license violations has been established to combat [copyleft trolls](https://commons.wikimedia.org/wiki/Commons:Copyleft_trolling), and _sui generis_ database rights are covered explicitly ([v4.0](https://creativecommons.org/version4/)). There are many more [subtle differences between license versions](https://wiki.creativecommons.org/wiki/License_Versions), therefore it is important to indicate which license version exactly one is referring to, as the license of a work does not "update" automatically.
 
 For the AGPLv3 it is even recommended to state whether a work is licensed under exactly the indicated version of the license or, alternatively, also under newer versions of the license [@Stallman2022Version].
 :::

literature.bib

@@ -714,4 +714,45 @@ @article{Smith2016
 	urldate = {2024-11-28},
 	date = {2016-09-19},
 	langid = {english},
+}
+@online{Villa2016Copyleft,
+	title = {Copyleft, attribution, and data: other considerations},
+	url = {https://lu.is/2016/09/copyleft-attribution-and-data-other-considerations/},
+	shorttitle = {Copyleft, attribution, and data},
+	abstract = {Public licenses for databases don’t work well. Before going into solutions to that problem, though, I wanted to talk briefly about some things that are important to consider when thinking abo…},
+	titleaddon = {Luis Villa: Open Tech and Policy},
+	author = {Villa, Luis},
+	urldate = {2024-12-04},
+	date = {2016-09-21},
+	langid = {american},
+}
+@online{Villa2016CC0,
+	title = {Public licenses and data: So what to do instead?},
+	url = {https://lu.is/2016/09/public-licenses-and-data-so-what-to-do-instead/},
+	shorttitle = {Public licenses and data},
+	abstract = {I just explained why open and copyleft licensing, which work fairly well in the software context, might not be legally workable, or practically a good idea, around data. So what to do instead? tl;d…},
+	titleaddon = {Luis Villa: Open Tech and Policy},
+	author = {Villa, Luis},
+	urldate = {2024-12-04},
+	date = {2016-09-26},
+	langid = {american},
+}
+@online{Vezina2020,
+	title = {Why Sharing Academic Publications Under “No Derivatives” Licenses is Misguided},
+	url = {https://creativecommons.org/2020/04/21/academic-publications-under-no-derivatives-licenses-is-misguided/},
+	abstract = {Using “No Derivatives” ({ND}) licenses on academic publications is ill-advised for policing academic fraud and unhelpful to the dissemination of research.},
+	titleaddon = {Creative Commons},
+	author = {Vézina, Brigitte},
+	urldate = {2024-12-04},
+	date = {2020-04-21},
+	langid = {american},
+}
+@online{WikimediaCommons2009,
+	title = {Licensing/Justifications},
+	url = {https://commons.wikimedia.org/w/index.php?title=Commons:Licensing/Justifications&oldid=917608913},
+	titleaddon = {Wikimedia Commons},
+	author = {{Wikimedia Commons contributors}},
+	urldate = {2024-12-04},
+	date = {2009-06-30},
+	langid = {english},
 }