Merge pull request #2 from DPGAlliance/Lucyeoh-patch-2-1

Update Language on 7

Author: lacabra

CHANGELOG.md

@@ -4,6 +4,12 @@ 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.4] 2020-10-20
+
+### Changed
+
+- Changed language on `7. Adherence to privacy and applicable laws` to include clarifying statement on **to the best of its knowledge** (#7)
+
 ## [1.0.3] 2020-10-20
 
 ### Added
@@ -33,6 +39,7 @@ 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.4]: https://github.com/DPGAlliance/DPG-Standard/compare/v1.0.3...v1.0.4
 [1.0.3]: https://github.com/DPGAlliance/DPG-Standard/compare/v1.0.2...v1.0.3
 [1.0.2]: https://github.com/DPGAlliance/DPG-Standard/compare/v1.0.1...v1.0.2
 [1.0.1]: https://github.com/DPGAlliance/DPG-Standard/compare/v1.0.0...v1.0.1

standard.md

@@ -12,7 +12,7 @@ Indicator |	Requirement
 **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.
 **6. Mechanism for Extracting Data** |	If this project has non personally identifiable information there must be a mechanism for extracting or importing non personally identifiable information (PII) data from the system in a non-proprietary format.
-**7. Adherence to privacy and applicable laws** |	The project must state that it complies with relevant privacy laws, and all applicable international and domestic laws.
+**7. Adherence to privacy and applicable laws** |	The project must state that to the best of its knowledge it complies with relevant privacy laws, and all applicable international and domestic laws.
 **8. Adherence to standards & best practices** |	Projects must demonstrate some adherence to standards, best practices and/or principles. i.e. the principles for digital development
 **9. Do No Harm** | 	All projects must demonstrate that they have taken steps to ensure that the project anticipates, prevents and does no harm. 
 **9a) Privacy & Freedom of Expression** |	All projects must have strategies in place to anticipate, respond to and minimize adverse impacts on privacy and freedom of expression where governments are believed to be using the project’s product or services for illegitimate or political purposes.