Clarified wording around CC licenses

CHANGELOG.md

@@ -4,6 +4,11 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.0.2] 2020-10-20
+
+### Changed
+- Clarified wording around CC licenses (#11)
+
 ## [1.0.1] 2020-10-20
 
 ### Added
@@ -20,5 +25,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Added
 - Released first version of the Digital Public Good Standard in consultation with a number of key stakeholders at the intersection of open source and social good.
 
+[1.0.2]: https://github.com/unicef/publicgoods-candidates/compare/v1.0.1...v1.0.2
 [1.0.1]: https://github.com/unicef/publicgoods-candidates/compare/v1.0.0...v1.0.1
 [1.0.0]: https://github.com/unicef/publicgoods-candidates/releases/tag/v1.0.0

standard.md

@@ -7,7 +7,7 @@
 Indicator |	Requirement
 --- | ---
 **1. Relevance to Sustainable Development Goals** |	All projects must indicate the SDG(s) that they are relevant to and provide supporting links/documentation to support this relevance. 
-**2. Use of approved open source license** |	Projects must demonstrate the use of an approved open source license. For Open Source Software, we only accept [OSI approved licenses](https://opensource.org/licenses). For Open Content we require the use of a [Creative Commons license](https://creativecommons.org/licenses/). While we encourage projects to use a license which allows for both derivatives and commercial reuse or dedicate content to the public domain ([CC0](https://creativecommons.org/choose/zero/)) we also accept the following licenses which do not allow for commercial reuse: [CC-BY-NC](https://creativecommons.org/licenses/by-nc/4.0/) and [CC-BY-NC-SA](https://creativecommons.org/licenses/by-nc-sa/4.0/). For data we require a [Open Data Commons approved license](https://opendefinition.org/licenses/). *You can find [the full license list here](https://github.com/unicef/publicgoods-candidates/blob/master/docs/licenses.md).*
+**2. Use of approved open source license** |	Projects must demonstrate the use of an approved open source license. For Open Source Software, we only accept [OSI approved licenses](https://opensource.org/licenses). For Open Content we require the use of a [Creative Commons license](https://creativecommons.org/licenses/) while we encourage projects to use a license which allows for both derivatives and commercial reuse ([CC-BY](https://creativecommons.org/licenses/by/4.0/) and [CC-BY-SA](https://creativecommons.org/licenses/by-sa/4.0/)), or dedicate content to the public domain ([CC0](https://creativecommons.org/choose/zero/)); we also accept licenses which do not allow for commercial reuse ([CC-BY-NC](https://creativecommons.org/licenses/by-nc/4.0/) and [CC-BY-NC-SA](https://creativecommons.org/licenses/by-nc-sa/4.0/)). For data we require an [Open Data Commons approved license](https://opendefinition.org/licenses/).  *You can find [the full license list here](https://github.com/unicef/publicgoods-candidates/blob/master/docs/licenses.md).*
 **3. Documentation of ownership** |	Ownership of everything that the project produces must be clearly defined and documented i.e. through copyright, trademark or other publicly available information.
 **4. Mandatory dependencies** |	If the open source project has mandatory dependencies that create more restrictions than the original license the projects must be able to demonstrate independence from the closed component and/or indicate the existence of functional, open alternatives.
 **5. Documentation** |	The project must have some documentation of the source code, use cases, and/or functional requirements. For content, this should indicate any relevant compatible apps, software, hardware required to access the content and instructions about how to use it. For software projects, this should be present as technical documentation that would allow a technical person unfamiliar with the project to  launch and run the software. For data projects, this should be present as documentation that describes all the fields in the set, and provides context on how the data was collected and how it should be interpreted.