I suggest an additional section titled tools. These tools really helped me in gaining a better understanding of structuring attributions etc.

The Attribution Builder is really helpful when there is uncertainty as to how to proceed with citing sources, especially as citing CC Licenses seems different from scholarly practices.

1. Open Attribution Builder, by WA SBCTC, [n.d.]. The Open Attribution Builder is licensed under CC BY 4.0.
2. CC “Select your License” tool logic - Beta version, by Wyblib40, 2020. Licensed under CC BY 4.0. (Please note that this workflow logic diagram I created myself in order to get a feel for the new License Chooser tool (2020)

Useful article that outlines how incompatible licensing can occur, despite original best intentions of the creators. Also demonstrates how time consuming and problematic it can be to resolve. (June 2020 cohort CC Cert)

Note: article needs to be hyperlinked.

This resource is one that I have already passed on to colleagues, I found it very helpful from the outset. I feel it clearly explains some of the key information to discuss with authors when considering Open Access publishing, especially when addressing common questions, such as "why should I publish OA?".

Additional Resource: I would like to recommend adding:

Is it possible to decolonize the Commons? An interview with Jane Anderson of Local Contexts

https://creativecommons.org/2019/01/30/jane-anderson/

This interview expands on TK (traditional knowledge) labels and Cultural Heritage. The interview came about after a panel the CC Global Summit, where the panelists discussed "the need for practical strategies for Indigenous communities to reclaim their rights and assert sovereignty over their own intellectual property.".

Additional Resource: I would like to recommend adding:

Editorial: Open for Business - why The Library in the Lead Pipe in moving to CC-BY licensing

http://www.inthelibrarywiththeleadpipe.org/2014/open-for-business/

A library specific example of how an Open Access journal changed their licensing practices for contributed articles, this outlines why and how they made these changes.

I found this to be a very interesting article, exploring the line between copyright and licensing of physical objects vs. the code (or digital file) used to create the object. This paper delves into a range of questions - what is being licensed, what is copyrightable, what is covered under a patent, what is a creative work, what is a functional work. Although this paper was published in early 2015, the content remains relevant now. (June 2020 Cohort CC Certificate)

Additional Resource: I would like to recommend adding:

How Creative Commons works, and why it enables access to knowledge by Denise Rosemary Nicholson (author) and Paul G West (contributor)

https://theconversation.com/how-creative-commons-works-and-why-it-enables-access-to-knowledge-125895

Clear & accessible description of CC and relevance to knowledge, and this article also demonstrates how CC is impacting legal changes to Copyright in other counties ( e.g. South Africa).

The compatibility chart is an excellent resource for visually identifying the scope of resuse. Most importantly, this chart shows the product of remixing licenses. This is another resource that will be employed for future reference.

Ironically this book is licensed "non-commercial." I personally like that license but after years of folks arguing against that license, I would love to hear the rationale behind it.

This is still the most helpful visual I have seen thus far to help explain and clarify compatibility of CC licenses.

Adobe Software's Education Licensing webpage

Microsoft Licensing Site lists different types of licenses for products including Volume Licensing and Academic Licensing

Types of software licenses and what they mean

Having a forklift license in New Jersey is mandatory for operators to operate forklifts. Call (800) 381-5729 to join our forklift certification NJ training and become a certified operator.

The CC team was key in this decision of ours. This gh issue was where the discussion happened. https://github.com/hypothesis/h/issues/1257#issuecomment-57957198

test ve development da kullanılabilir

It's stored in a [COPYRIGHT](https://github.com/gittip/aspen-python/blob/master/COPYRIGHT) file rather than a LICENSE one, but it's well licensed, all the same. :)

note "fair", open to interpretation