> For the complete documentation index, see [llms.txt](https://discover.theiofoundation.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://discover.theiofoundation.org/the-io-foundation/institutional/policies/work-in-progress/intellectual-property.md).

# Intellectual Property

Version 1.0 | This Policy was approved on DD MMMM YYYY.

{% hint style="info" %}
**ShortURL | Playbook | Assistant**
{% endhint %}

## Introduction

### Definitions

This document employs terms related to the [DCDR Advocacy](https://TIOF.Click/DCDRAdvocacy) that can be found in the [TIOF terminology](https://TIOF.Click/TIOFTerminology).

For a structure of The IO Foundation, please visit

* The IO Foundation's [Organizational Chart](http://TIOF.Click/TIOFOrgChart)
* The IO Foundation's [Organizational Taxonomy](< https://TIOF.Click/OrgTaxonomy>)

### About this document

This document, hereinafter the Policy, sets out the position maintained by TIOF in matters of **Anti-corruption and Anti-bribery** that you will need to be aware of while being a TIOF Member. You should familiarize yourself with it and comply with it at all times. Any questions you may have with regard to its contents or what you have to do to comply with it should be referred to your corresponding Team Human Resources Manager.

Any Member who breaches this Policy will face disciplinary action, which could result in dismissal for gross misconduct. Any non-employee who breaches this Policy may have their contract (or equivalent official relationship with TIOF) terminated with immediate effect.

{% hint style="info" %}
This document complements [TIOF's Code of Conduct](https://TIOF.Click/TIOFPolicyCoC).
{% endhint %}

{% hint style="info" %}
This document does not form part of any [Engagement Document](https://TIOF.Click/TIOFTerminology#engagement-document) and we may amend it at any time following the procedures described in [TIOF's Statute](https://TIOF.Click/TIOFStatute).
{% endhint %}

### Scope

This document directly applies to:

* All [TIOF Members](https://TIOF.Click/TIOFTerminology#members)

This document indirectly applies to:

* All [TIOF Contributors](https://TIOF.Click/TIOFTerminology#contributors)

The policies set out in this document apply to all [TIOF Members](https://TIOF.Click/TIOFTerminology#members) unless otherwise indicated. They therefore apply to Members of the Boards ([Directors](https://TIOF.Click/TIOFTerminology#directors), [Advisers](https://TIOF.Click/TIOFTerminology#advisers), [Consultants](https://TIOF.Click/TIOFTerminology#consultants)), [Employees](https://TIOF.Click/TIOFTerminology#employees), [Volunteers](https://TIOF.Click/TIOFTerminology#volunteers) and [Interns](https://TIOF.Click/TIOFTerminology#interns); this is irrespective of their [engagement type](https://TIOF.Click/TIOFTerminology#engagement-type). They equally apply to all [Contributors](https://TIOF.Click/TIOFTerminology#contributors) and will be used as part of the selection criteria when engaging with them.

This Policy applies within all [TIOF Spaces](https://TIOF.Click/TIOFTerminology#spaces), including (although not limited to) management activities, contributions or events; it and also applies when an individual is officially representing the organization in public spaces. Examples of representing the organization include (although not limited to) using an official e-mail address, posting via any official channel or acting as an appointed representative at an event.

{% hint style="warning" %}
**Review and Amendments**\
This policy shall be reviewed regularly to ensure its continued relevance and effectiveness. Amendments may be made to adapt to new legal requirements, changing circumstances or to better serve the organization's Mission.
{% endhint %}

## Policy details

## Introduction

### Definitions

This document employs terms related to the [DCDR Advocacy](http://tiof.click/Advocacy) that can be found in the [TIOF terminology](http://tiof.click/Terminology).

For a structure of The IO Foundation, please visit

* The IO Foundation's [Organizational Chart](http://TIOF.Click/TIOFOrgChart)
* The IO Foundation's [Organizational Nomenclature](http://TIOF.Click/OrgNomenclature)

Back to top

### About this document

This document sets out the standards established by TIOF in matters of Intellectual Property you will need to be aware of while being a Member for TIOF. It establishes all necessary considerations in the creation of materials of different nature (including but not limited to documents, articles, books, images, videos and datasets) and how the applicable IP will be established and communicated. You should familiarize yourself with them and comply with them at all times. Any questions you may have with regard to its contents or what you have to do to comply with it should be referred to your corresponding Team Comms Coordinator, who is the ultimate responsible for its application.

Any Member who breaches this Policy will face disciplinary action, which could result in dismissal for gross misconduct. Any non-Member who breaches this Policy may have their contract (or equivalent official relationship with TIOF) terminated with immediate effect.

This document complements TIOF's [Code of Conduct](http://TIOF.Click/TIOFPolicyCoC)

This document does not form part of any [Engagement Document](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#engagement-document) and we may amend it at any time.

Back to top

### Scope

This document directly applies to:

* All [TIOF Members](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#member)

This document indirectly applies to:

* All [TIOF Contributors](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#contributors)

The policies and/or procedures set out in this document apply to all TIOF Members unless otherwise indicated. They therefore apply to Directors, Advisers, Counselors, Staff, Volunteers and Interns; this is irrespective of their part-time, fixed-term or casual status. They equally apply to all [Contributors](https://github.com/TheIOFoundation/TIOF/wiki/Terminology#contributors) and will be used as part of the selection criteria when engaging with them.

This document applies within all TIOF spaces, including (although not limited to) management activities, project contributions or events, and also applies when an individual is officially representing the broader community in public spaces. Examples of representing our community include (although not limited to) using an official e-mail address, posting via an official social media account or acting as an appointed representative at an event (online or offline).

Back to top

## Policy details

###

## Licensing Models

### Levels

The IO Foundation publishes information under the following levels:

|       | Public | Internal | Confidential |
| ----- | ------ | -------- | ------------ |
| Code  | \[P]   | \[I]     | \[C]         |
| Usage |        |          |              |
|       |        |          |              |

### Public Licensing

Each Organization and Initiative must have

* a clear License description for productions (research materials, articles, etc.)
  * based on an established model and tailored if necessary to provide public access and reuse
  * easily accessible through the corresponding documentation site
* a clear License description for code
  * based on an established Licensing Model
  * easily accessible through the corresponding Repository
* a shortURL for all the licenses

### Formatting

The Organization will strive to provide

* machine-readable formats
* user-friendly formats

of all of its productions, in particular:

* Policies
* Licensing models

### Licensing #exposure\#

Every production will showcase/signal its licensing by

* Indicating the Level in its (file)name
* Including the TIOF Licensing Signal (?) in the production:

| Type of production | Category    | Signal(?) |
| ------------------ | ----------- | --------- |
| Document           | Text        |           |
|                    | Spreadsheet |           |
|                    |             |           |
|                    |             |           |
| Video              |             |           |
|                    |             |           |
|                    |             |           |
| Music              |             |           |

## 3rd Party assets

Attributions need be mentioned

* In the Attributions section
* In the productions themselves

###

## Productions' Licenses

The IO Foundation is committed to its DCDR advocacy and to share all of its generated materials to be available and shareable by all under a licensing model that preserves and encourages their usage and benefit.

Currently, TIOF has adopted the following licenses:

#### Creative Commons

Applicable for: All productions such as documents, books, videos

### Text

| License                                  | Applicable since | Comments |
| ---------------------------------------- | ---------------- | -------- |
| <p>Creative Commons 4.0 <br>BY NC SA</p> | 1st April 2018   |          |
|                                          |                  |          |
|                                          |                  |          |

#### GNU

Applicable for: Software

#### ???

Applicable for: Datasets

#### Others

Should there be a type of material that is not listed above, please reach out to your corresponding Team Comms Coordinator for clarification and to update this document.

Back to top

### Creative Commons

Back to top

#### Current CC version

Back to top

### GNU

Back to top

### ???

Back to top

### Partnerships, collaborations and contracts

When engaging in collaborations of any sort, TIOF is mandated to comply with its IP Policy. While in occasions the engagement document may indicate a conflicting IP approach, TIOF must make all efforts to agree on an open modality akin to its own.

When such option is not possible, TIOF will not engage in said collaboration.

Exceptions Anything that does not generate materials that are related to the DCDR advocacy.

Back to top

Credits are to be always made.

### Consultations

How to participate

* Use the Comments tool to share your thoughts.
* We will review your inputs and decide which ones make sense in the context of our DCDR Framework and the Malaysian NAP.
* Should your inputs be included in the document and your name will be added as collaborator.
* Should your inputs not be included we will do our best to articulate the reasons that lead to that decision.
* Please consider that in any case The IO Foundation will need to make the final decision as we will have to defend the Policy Brief upon the group working on the NAP.

Timeline Beginning of the comments: 7th October at reception of this email. End of comments: 14th of October @ 18:00 Finalizing of Policy Brief: 16th of October Submission to BEEU, SUHAKAM and UNDP: 17th of October Submission to further relevant parties: 24th of October and onwards

### Notices and logos

All materials produced by TIOF, that are not under excluding terms as indicated in the @@@Exceptions, are to be published under Creative Commons. The licensing terms must be clearly indicated in the material and links to further information such as this policy and the terms of the licensing are to be made easily available.

Back to top


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://discover.theiofoundation.org/the-io-foundation/institutional/policies/work-in-progress/intellectual-property.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.