Shorten section on other restrictions

- Make the argument more succinct
- Remove the references as they are
  not that good

choose_license.qmd

@@ -170,11 +170,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; @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.
-
-However, applying a restriction such as only permitting non-commercial use or not allowing derivative works creates _silos_ of works which are mutually incompatible with each other. Put differently, one cannot share a remix of two works where one is licensed under CC\ BY-SA\ 4.0 and the other only allows non-commercial use. In order to avoid silos, one should only choose licenses which are compatible with the dominant copyleft license in the respective community [@Lammerhirt2017; @Wheeler2014]. If you would like to learn more about the different types of compatibility, we recommend you to read the article "A Quick Guide to Software Licensing for the Scientist-Programmer" by @Morin2012. The following diagram provides an overview of the compatibility of various licenses:
+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. Otherwise, creating adaptations from multiple works by different authors would either limit commercial use for everybody (including the authors) or would not be possible at all (when including materials with a copyleft license), effectively creating _silos_ of works which are mutually incompatible with each other. This is especially relevant for work types for which adaptations are created frequently, such as text, data, and source code. In order to avoid silos, one should only choose licenses which are compatible with the dominant copyleft license in the respective community [@Lammerhirt2017; @Wheeler2014]. If you would like to learn more about the different types of compatibility, we recommend you to read the article "A Quick Guide to Software Licensing for the Scientist-Programmer" by @Morin2012. The following diagram provides an overview of the compatibility of various licenses:
 
 !["Open data-capable license interoperability" by Robbie Morrison [-@Morrison2024] licensed under [CC\ BY\ 4.0](https://creativecommons.org/licenses/by/4.0/)](images/Morrison2024.jpg){.lightbox}
 :::

literature.bib

@@ -213,35 +213,6 @@ @online{MadHatter2022
 	date = {2022-03-18}
 }
 
-@misc{Klimpel2013,
-	title = {Free knowledge based on {Creative Commons} licenses},
-	url = {https://meta.wikimedia.org/wiki/Free_knowledge_based_on_Creative_Commons_licenses},
-	publisher = {Wikimedia},
-	author = {Klimpel, Paul},
-	urldate = {2024-09-03},
-	date = {2013},
-	langid = {english}
-}
-
-@online{ODI2015,
-	title = {What are the impacts of non-open licences?},
-	url = {https://theodi.org/insights/guides/what-are-the-impacts-of-non-open-licences/},
-	abstract = {This guide outlines the key considerations that inform licensing decisions},
-	author = {{Open Data Institute}},
-	urldate = {2024-09-03},
-	date = {2015-09-22},
-	langid = {english}
-}
-
-@online{CC2024FAQ,
-	title = {Answer to 'Can {I} combine material under different {Creative Commons} licenses in my work?' in Frequently Asked Questions},
-	url = {https://creativecommons.org/faq/#can-i-combine-material-under-different-creative-commons-licenses-in-my-work},
-	author = {{Creative Commons}},
-	urldate = {2024-09-03},
-	date = {2024-06-03},
-	langid = {english}
-}
-
 @article{Morin2012,
 	title = {A Quick Guide to Software Licensing for the Scientist-Programmer},
 	volume = {8},
@@ -517,23 +488,6 @@ @report{ScienceEurope2021
 	howpublished = {\url{https://scienceeurope.org/our-resources/practical-guide-to-the-international-alignment-of-research-data-management/}}
 }
 
-@online{Stallman2022NoLimit,
-	title = {Why programs must not limit the freedom to run them},
-	url = {https://www.gnu.org/philosophy/programs-must-not-limit-freedom-to-run.html},
-	author = {Stallman, Richard},
-	urldate = {2024-09-21},
-	date = {2022-09-06},
-}
-
-@online{Moller2023,
-	title = {The case for Free use: reasons not to use a {Creative Commons} -{NC} license},
-	url = {https://freedomdefined.org/index.php?title=Licenses/NC&oldid=27327},
-	author = {Möller, Erik},
-	urldate = {2024-09-21},
-	date = {2023-12-15},
-	langid = {english},
-}
-
 @online{Fogel2006,
 	title = {The Surprising History of Copyright and The Promise of a Post-Copyright World},
 	url = {https://questioncopyright.org/promise/},
@@ -737,26 +691,6 @@ @online{Villa2016CC0
 	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},
-}
-
 @misc{UKRN2023,
 	title = {Rights Retention Strategy: a Primer from {UKRN}},
 	rights = {https://creativecommons.org/licenses/by/4.0/legalcode},