DPG Resources

  • Home
  • DPG Indicators

DPG Indicators

Below is a list of the 9 indicators and requirements that must be met in order for a nominated software, data, AI models, standards and/or content (described in the standard below as the “project”) to be considered a digital public good.

1. Relevance to Sustainable Development Goals

All projects must indicate which Sustainable Development Goals (SDGs) they are relevant to, in addition to providing links and documentation that support their relevance.

Read more

2. Use of Approved Open Licenses

Projects must demonstrate the use of an approved open license.
For Open Source Software, we only accept OSI approved licenses.

For Open Content, we require the use of a Creative Commons license and encourage projects to use a license which allows for both derivatives and commercial reuse (CC-BY and CC-BY-SA), or dedicate content to the public domain (CC0). We also accept licenses which do not allow for commercial reuse (CC-BY-NC and CC-BY-NC-SA).

For data we require an Open Data Commons approved license.

Read more

3. Clear Ownership

Ownership of everything the project produces must be clearly defined and documented. For example, through copyright, trademark, or other publicly available information.

Read more

4. Platform Independence

If the project has mandatory dependencies that create more restrictions than the original license, the project(s) must be able to demonstrate independence from the closed component(s) and/or indicate the existence of functional, open alternatives.

Read more

5. Documentation

All projects must have some documentation of the source code, use cases, and/or functional requirements. For content, this includes any relevant compatible apps, software, or hardware required to access the content and instructions on how to use it. For software projects, this includes technical documentation that would allow a technical person unfamiliar with the project to launch and run the software. For data projects, this includes documentation that describes all the fields in the set, and provides context on how the data was collected and how it should be interpreted.

Read more

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.

Read more

7. Adherence to Privacy & 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.

Read more

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.

Read more

9. Do No Harm

All projects must demonstrate that they have taken steps to ensure that the project anticipates, prevents and does no harm.

Read more

9.a) Data Privacy & Security

Project’s that collect data must identify the types of data collected and stored and demonstrate that the project ensures the privacy and security of this data and has taken steps to prevent adverse impacts resulting from it’s collection, storage and distribution.

Read more

9.b) Inappropriate & Illegal Content

Projects that collect, store or distribute content must have policies identifying inappropriate and illegal content such as child sexual abuse materials and mechanisms for detecting, moderating and removing inappropriate/illegal content.

Read more

9.c) Protection from Harassment

If the project facilitates interactions with or between users or contributors there must be a mechanism for users and contributors to protect themselves against grief, abuse, and harassment. The project must have a mechanism to address the safety and security of underage users.

Read more