Add references to licensing chapter

choose_license.qmd

@@ -33,9 +33,9 @@ For the purpose of this tutorial, by _license_ we mean _copyright license_.
 ::: {#wrn-exclusive-rights .callout-warning}
 ### Giving Publishers Exclusive Rights
 
-Some journals offer to publish your article under a Creative Commons license, but still demand an exclusive publishing and distribution license or a copyright assignment from you. This would give them more rights than the readers of the article have through the respective Creative Commons license [@Rumsey2022] and exceeds by far what is necessary to make publication possible [@Suber2022]. Consequently, authors should oppose this practice and grant publishers the same rights that every other reader of the article has. If your chosen publisher insists on an exclusive license, you may at least retain the copyright for your figures -- follow the guide "Retaining copyright for figures in academic publications to allow easy citation and reuse" by @Elson2016 to learn how to do that.
+Some journals offer to publish your article under a Creative Commons license, but still demand an exclusive publishing and distribution license or a copyright assignment from you. This would give them more rights than the readers of the article have through the respective Creative Commons license [@Rumsey2022] and exceeds by far what is necessary to make publication possible [@Suber2022]. Consequently, authors should oppose this practice and grant publishers the same rights that every other reader of the article has. To facilitate self-archiving, one can also modify the contract with publishers via a rights retention statement [@UKRN2023] / author's addendum [@SPARC2006]. If you have published a closed-access paper before, you can consult [ShareYourPaper](https://shareyourpaper.org/) for legal options to still make it available free of charge to readers.
 
-If you have published a closed-access paper before, you can consult [ShareYourPaper](https://shareyourpaper.org/) for legal options to still make it available free of charge to readers.
+If your chosen publisher insists on an exclusive license, you may at least retain the copyright for your figures -- follow the guide "Retaining copyright for figures in academic publications to allow easy citation and reuse" by @Elson2016 to learn how to do that.
 :::
 
 The licenses we discuss here mostly regard copyright. Therefore, recipients may lack other rights such as publicity, privacy, moral, patent,^[In fact, the software licenses we recommend on this page have been specifically selected to provide an express grant of patent rights.] or trademark rights. For example, sharing photos that depict people is not only a matter of copyright, but also of privacy rights. Conversely, the licenses do not apply if recipients are allowed to use the works for other reasons such as fair use, the right to quote, or because they made a different arrangement with the author.
@@ -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 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.
+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/weblog/entry/4216#:~:text=Share%20Alike%20Across%20Borders), 2004) and compatible licenses ([v3.0](https://creativecommons.org/weblog/entry/7249), 2007) 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/weblog/entry/40768), 2013). 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. CC0, officially introduced in 2009, is still at version [1.0](http://www.creativecommons.org/weblog/entry/13304).
 
 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

@@ -755,4 +755,27 @@ @online{WikimediaCommons2009
 	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},
+	url = {https://osf.io/2ajsg},
+	doi = {10.31219/osf.io/2ajsg},
+	shorttitle = {Rights Retention Strategy},
+	abstract = {This guide describes how authors can retain rights on their “author’s accepted manuscripts” using the Rights Retention Strategy.},
+	publisher = {Open Science Framework},
+	author = {{UK Reproducibility Network} and Eglen, Stephen},
+	urldate = {2024-12-10},
+	date = {2023-04-18},
+}
+
+@online{SPARC2006,
+	title = {Author Rights: Using the {SPARC} Author Addendum},
+	url = {https://sparcopen.org/our-work/author-rights/brochure-html/},
+	shorttitle = {Author Rights},
+	author = {{SPARC}},
+	urldate = {2024-12-10},
+	date = {2006},
+	langid = {american},
 }