Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Version 1.0 | This Business Plan was approved on DD MMMM YYYY.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This section provides all the information about the Data-Centric Digital Rights initiative's business plan.
[Work in Progress]
This business plan is fully compliant with The IO Foundation's policies.
[Work in Progress]
This budgeting plan is fully compliant with The IO Foundation's policies.
Version 1.0 | This Theory of Change was approved on DD MMMM YYYY.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This section describes the Theory of Change that guides the Data-Centric Digital Rights initiative and its impact.
The IO Foundation has observed the following problem:
The current state of technology is not conducive to designing digital spaces that are transparently protected
The extra weight on citizen’s shoulders
The ridiculous difference between tech and the rest of the industries
Impossibility of adherence to compliance
Impossibility for agencies to verify and enforce compliance
Leaving behind major stakeholder: programmers
The IO Foundation proposes the following solutions to the observed problems.
[Work in Progress]
The IO Foundation proposes the following Theory of Change to address the observed problems.
[Work in Progress]
ShortURL | Playbook | Assistant
This website contains the documentation relative to the Data-Centric Digital Rights (DCDR) Initiative from The IO Foundation.
You may be looking for:
To learn how to navigate this documentation, please check the HELP section.
Data-Centric Digital Rights (DCDR), an initiative from The IO Foundation, is the advocacy by which it aims at protecting citizens' Rights by transparently implementing in their daily technology the regulations that should protect them.
TIOF views the technology as currently non-correlated with all working understandings and practices as to how any public-consumption industry functions traditionally where a clear separation is made between:
Experts, who understand the complexities to design and build products that are compliant with applicable legislation and
Citizens, who are solely tasked for being responsible users of the product
As core stakeholders, technologists play a critical role as the Next Generation of Rights Defenders and need to orient themselves through new design and implementation paradigms focused on protecting data. The DCDR Principles put forward by The IO Foundation are concepts that help them navigate the intricacies of applying Human and Digital Rights in digital infrastructures, products and services.
In essence, DCDR is a framework for technologists composed by Principles, Taxonomies and other technical tools. It enables them to develop a deeper understanding about the nature of data, the digital twins that emerge from it and make possible for them to embrace their role as NextGen Rights Defenders.
By understanding that we are our data, technologists may architect Digital Spaces that aim at ending remedy and build it so that they implement Rights by design.
The DCDR initiative aims at encouraging a shift in the current technology paradigms by providing
Generating the necessary body of work for
A set of taxonomies for
While the DCDR initiative is designed in order to support TIOF's mission and to achieve its vision, it nonetheless also formulates its own Mission & Vision.
To provide technologist with a clear framework and taxonomies to embed Data-Centric Digital Rights into technology and enable their role as Next Generation of Rights Defenders.
A world where technology protects digital citizens and their digital twins transparently and by design.
The DCDR initiative adheres to the same values as The IO Foundation to deliver its mission.
The IO Foundation regularly publishes articles, research papers and other documents such as comments on public consultations related to its advocacy. Check out DCDR's publications.
The IO Foundation regularly organizes events and participates in international fora where the organization puts forward its advocacy and engages with all stakeholders. TIOF's handles all of its events through its TechUp initiative. Check out DCDR's events.
The advancement of TIOF's DCDR advocacy is made possible with the collaboration of a number of partner and supporting organizations, funders and individual citizens.
You can support The IO Foundation by
Check our Partners and Collaborators.
This documentation page is under construction. Should you want to be notified once it's published, .
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This section provides a list of Frequently Asked Questions about the DCDR advocacy.
ShortURL | Playbook | Assistant
The IO Foundation is always looking for talented individuals wishing to make an impact in technology through its DCDR advocacy initiative.
Do you share the DCDR's Mission & Vision?
Do you have a passion towards the development and support of the Data-Centric Digital Rights advocacy?
Together we can work towards protecting citizens' Data-Centric Digital Rights.
Let’s talk!
Contributing in the DCDR advocacy is easy!
There are 2 ways to proceed:
By joining as a TIOF Member you will officially join one of the DCDR Teams, participate in organized tasks and have access to tools and other resources as well as training.
TIOF Members can be:
As an active TIOF Member, you must be able to commit according to the responsibilities acquired.
Commitment means staying loyal to what you said you were going to do long after the mood you said it in has left you.
Orebela Gbenga
It is not necessary to be a Member to participate and make a meaningful contribution to the DCDR advocacy.
There are plenty of ways that you can support it without requiring to dive into its complexities.
Participating sporadically is also possible and always welcomed.
In response to your commitment towards our values (and in the measure of our capacities), The IO Foundation publishes all ongoing tasks for the DCDR advocacy initiative in its public repository.
Check out what are we up to and pick tasks you feel you can contribute with.
How to contribute on tasks? Check the Tasks Handbook.
Version 1.0 | This Media Kit was approved on 01 February 2022.
ShortURL | Playbook | Assistant | Slides Repository
This document employs terms related to TIOF's DCDR Advocacy that can be found in the TIOF terminology as well as the DCDR Terminology.
For a structure of The IO Foundation and the DCDR initiative, please visit
The IO Foundation's Organizational Chart
The IO Foundation's Organizational Taxonomy
This document describes all the elements that conform the Data-Centric Digital Rights' initiative identity (aka Branding Guidelines) and their usage rules on any generated content, by either TIOF Members, Contributors or any other third parties.
It is a reference document to which all DCDR productions, either for internal or external use, must refer and adhere.
You should familiarize yourself with this 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 the initiative's Team Comms Manager.
A document summarizing The IO Foundation's Branding Guidelines is also available.
A full Media Kit set is available for download in TIOF's Media Package, which includes DCDR materials.
The following forms are authorized when referring to TechUp:
Please note the capitalization
Data-Centric Digital Rights
DCDR
Abbreviation: DCDR (Example: [TIOF DCDR])
The following is the official tagline of DCDR.
Guiding technologists to build safe technology for digital twins.
While the DCDR initiative is designed in order to support TIOF's mission and to achieve its vision, it nonetheless also formulates its own Mission & Vision.
Mission: To provide technologist with a clear framework and taxonomies to embed Data-Centric Digital Rights into technology and enable their role as Next Generation of Rights Defenders.
Vision: A world where technology protects digital citizens and their digital twins transparently and by design.
The DCDR initiative adheres to the same values as The IO Foundation to delivers its mission.
The following are the official definitions to be used when describing or referencing DCDR. A number of variations are provided in an attempt to fit different character limitations.
When describing DCDR, please use these official descriptions.
Data-Centric Digital Rights (DCDR), an initiative from The IO Foundation, is a framework for technologists composed of Principles, Taxonomies and other technical tools. It enables them to develop a deeper understanding about the nature of data, the digital twins that emerge from it and make possible for them to embrace their role as NextGen Rights Defenders.
By understanding that I am my data, technologists may design solutions that aim at ending remedy by architecting and building technology that observers Rights by Design.
Data-Centric Digital Rights (DCDR), an initiative from The IO Foundation, is a framework for technologists composed of Principles, Taxonomies and other technical tools enabling them in their role as NextGen Rights Defenders.
Data-Centric Digital Rights, an initiative from The IO Foundation, provides a framework for technologists that enables them to embrace their role as NextGen Rights Defenders.
DCDR provides a framework for technologists that enables them to embrace their role as NextGen Rights Defenders.
The following are the official logos for the DCDR initiative.
The DCDR are currently being designed and shall be released as soon as possible.
For more information, please refer to TIOF's Branding Guidelines.
A full Media Kit set is available for download in TIOF's Media Package, including TechUp materials.
The following are the official formulations of the 3 DCDR Principles that The IO Foundation puts forward to guide technologist in their role as NextGen Rights defenders.
A full Media Kit set is available for download in TIOF's Media Package, including DCDR materials.
DCDR follows the same font guidelines as The IO Foundation.
For more information, please refer to TIOF's Media Kit.
DCDR follows the same color palette as The IO Foundation.
For more information, please refer to TIOF's Media Kit.
The following are the official QR Codes to link DCDR's online resources.
All QR Codes are available in TIOF's Media Package, which includes TechUp materials.
Aside from the #Tags defined in TIOF's Media Kit, the following are the official #Tags used by DCDR.
#DCDR
#DigitalHarms
#DigitalRights
#IamMyData
#EndRemedy
#RightsByDesign
Each TIOF initiative has its own set of #Tags. Please refer to the corresponding initiative's Media Kit for their #Tags list.
The following are the official, sanctioned, Media Channels used by the DCDR advocacy for its activities.
Any other Media Channel not listed here is to be considered not affiliated with TechUp and therefore any opinions expressed are not to be associated with it.
The following is the official website for TechUp.
The following is the official documentation site for The IO Foundation and its initiatives.
DCDR uses the same URL shortener as The IO Foundation.
For more information, please refer to TIOF's Media Kit.
The following are the official repositories used by The IO Foundation.
The following are the official email domains used by the DCDR advocacy.
Only email received from these domains are to be considered originated by DCDR or its members.
The following are the official public email addresses used by TechUp.
The following are the official social media platforms where DCDR has some sort of active presence.
The IO Foundation, in general, uses social media reluctantly.
To learn more about TIOF's position on this matter, check our Hey Big Tech! declaration.
The DCDR advocacy currently uses the same Media Channels as The IO Foundation.
For more information, please refer to TIOF's Media Kit.
The IO Foundation has profiles in other platforms, sometimes in preparation for its use, sometimes to avoid impersonation.
The following is the official calendar through which the DCDR advocacy publishes events:
organized by the DCDR initiative team (including all TIOF's and its initiatives')
those it may participate in
other events that are deemed relevant
The IO Foundation accepts financial donations on both Fiat and Crypto currencies.
The DCDR currently uses the same Donation & Crowdfunding platforms as The IO Foundation.
For more information, please refer to TIOF's Media Kit.
The following is the official recruitment platform through which the DCDR initiative publishes its open positions.
The following is a list of TIOF's initiatives and a quick link to their corresponding Media Kit.
TechUp Full Logo
[PENDING]
[PENDING]
Format
Full Color
White Variant
Usage
General use
Monochromatic or dark backgrounds
Full URL
Alternative URLs
None
Short URL
Contents
General information about DCDR
Full URL
Alternative URLs
None
Short URL
Contents
Publishing of all documentation relative to DCDR + Research + Reference materials
Full URL
Alternative URLs
None
Short URL
Content
Public repository showcasing DCDR's advocacy work
Usage
Initiative Management + Community Collaboration + Transparency platform
Domains
@TheIOFoundation.org
Alternative Domains
None
Usage
Official communications from DCDR Members both internally and externally
DCDR@TheIOFoundation.org
Usage
Official communications and inquiries
Platform
Google Calendar
Short URL
Content
Events calendar
Usage
Public events calendar
Platform
QPage
Full URL
Short URL
Content
Posting of open positions for DCDR
ShortURL | Playbook | Assistant
The DCDR advocacy initiative has not received any award to this date.
Suggesting an Award
If you are aware of an award or competition that we should explore, let us know.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
This section contains an archive of all media participations and mentions about the DCDR Advocacy.
Principle I
Principle II
Principle III
I Am My Data
End Remedy
Rights By Design
Treat their data as you'd want to be treated.
Adopt designs that minimize grievances.
Leave no protection uncoded behind.
DCDR Principles
Principle I
Principle II
Principle III
The IO Foundation
[PENDING]
DCDR
This document
BHR in Tech
CrowdShape
Project Lockdown
TechUp
UDDR
Version 0.1
NOTICE
The DCDR Framework is currently a work in progress.
The DCDR Framework is the basis for TIOF's DCDR advocacy.
The DCDR Framework is composed of a number of components that are interconnected and building upon each other.
Combined, they provide the necessary tools to support technologists in understanding the underlying interactions between the physical and the digital worlds.
The DCDR Framework provides the foundation for the rest of the DCDR components
The DCDR Framework is structured upon 3 Levels representing different conceptualizations. Each Level helps sustaining the propositions made in the upper level.
Citizen-centric [WHY?]
Digital Spaces (which can be many) are a result, and thus dependent of the Physical Space (which is unique) [WHY?]
This level provides an structure on the nature of a Space. It describes the fundamentals of what composes a Space and the interactions happening within it.
This level provides a list of DCDR Components on the bases of the objects existing in a Space.
This level describes the DCDR Framework, a macro view of how the DCDR Components are to interact to architect digital spaces that respond to the DCDR Principles.
As all materials created by The IO Foundation, the DCDR Framework is published under TIOF Public Licensing Model.
Establish a working group to research on the DCDR Framework
Produce a research paper documenting the DCDR Framework
Design a syllabus for the dissemination of the DCDR Framework
Promote the awareness and understanding of the research results
| Playbook | Assistant |
The DCDR Framework, as any other component of the , is subjected to improvements.
Anyone wishing to submit an improvement to the DCDR Framework, can do so via the folder in the .
Serve as the basis for the
Incorporate the research's results in the
Version 0.1
ShortURL | Playbook | Assistant | Contribute
NOTICE
The DCDR Framework is currently a work in progress.
The Physical Space (PS) is the environment inside which humans live. For all intents and purposes of this Framework, there is only one single Physical Spaces.
The Physical Space is regulated by laws of physics that we can discover and utilize for our benefit yet not modify.
I would love to change the world but no one gives me the source code.
Anonymous
The Physical Space produces objects, humans and otherwise. Humans organize in societies which handle the difficulties of managing groups of people through algorithms that we call laws.
Through the biology of their bodies, Humans create Mental Spaces.
Through the process of invention/innovation, Humans (through their Mental Spaces) create Digital Spaces.
Version 0.1
ShortURL | Playbook | Assistant | Contribute
NOTICE
The DCDR Framework is currently a work in progress.
Spaces are the environments in which a number objects interact with each other through events by means of messages that are exchanged through channels at a given cost.
Spaces differentiate through their properties. The DCDR Framework consisders 3 Spaces, which provide a global working area in the objective of protecting people's rights and their data, namely:
The Physical Space
Mental Spaces
Digital Spaces
An initial comparison of Spaces would provide the following insights:
Source: Determines from which space a given space is derived and its nature.
Dimensions: The list of applicable dimensions that affect the objects in a given space.
Shared: Is the data in the twin shared by several algorithms at a time? In other words, can the twin be isolated from external access?
Relay: Responds to the question "Can you stop information existing in a twin to be replicated elsewhere?".
Space | Physical | Mental | Digital |
---|---|---|---|
Physical | Mental | Digital | |
---|---|---|---|
Source
Itself
Physical (Organic)
Mental (Synthetic)
Dimensions
X, Y, Z, Time
Time
Operations
Shared
No
Potentially
Create
TBD
By communicating with others. Success uncertain.
Dependent on algorithmic capacities.
Read
TBD
By asking. Authenticity/Accuracy can't be ascertained.
Dependent on algorithmic capacities.
Update
TBD
By communication. Success is uncertain.
Dependent on algorithmic capacities.
Delete
TBD
By request. Pretty much impossible. Would require demise.
Dependent on algorithmic capacities.
Relay*
TBD
Nearly impossible to stop.
can be stopped depending on the algorithm.
Version 0.1
ShortURL | Playbook | Assistant | Contribute
NOTICE
The DCDR Framework is currently a work in progress.
A Mental Space (MS) is the representation of the Physical Space that every human has in their head. There are as many Mental Spaces are there are humans.
Each Mental Space is can be understood by a black box that runs an algorithm (MSA) over the data received through interaction with the Physical Space (MSD).
The algorithm (Mental Algorithm - MA) is composed, among others, by inherited mechanisms and learned knowledge.
The MS produces Mental Twins (MT) that represent the different objects we interact in the shape of models upon which we apply our MA.
Mental spaces are usually overlooked when interpreting the impact of technology. Nonetheless, the DCDR Framework relies on this concept to explain how certain mechanisms function.
Version 0.1
ShortURL | Playbook | Assistant | Contribute
NOTICE
The DCDR Framework is currently a work in progress.
A Digital Space (MS) is the representation of the Physical Space through the use of digital technology. There are as many Digital Spaces are there are digital systems.
Each Digital Space is composed of algorithms (DA) that represent actions applied over digital data (DD) that is either obtained by measuring a properly in the Physical Space (authentic data) or synthetically manufactured (non-authentic data).
The algorithms (Digital Algorithm - DA) are built through hardware and software with the former establishing the range of possibilities served to the user through the latter.
The DS produces Digital Twins (DT) that represent objects, both build with authentic and non-authentic (more often than not a combination of both), upon with DAs are applied.
Version 0.1
ShortURL | Playbook | Assistant | Contribute
NOTICE
The DCDR Framework is currently a work in progress.
A research focused on establishing a technical description on the nature of data and its lifecycle.
The DCDR Data Lifecycle is based on the DCDR Framework.
A core component of the DCDR Framework and its implementation is to provide clarity concerning the nature of data and its lifecycle. The objective is to ensure a baseline model to identify the Digital Harms that data can undergo during said lifecycle so that technologists can use it as a reference.
Data exists in a fully digital space. Understanding data manipulation requires understanding its lifecycle.
The DCDR Data Lifecycle informs the work for the DCDR Digital Harms.
As all materials created by The IO Foundation, the Data Lifecycle, a component of the DCDR Framework, is published under TIOF Public Licensing Model.
The Data Lifecycle, as any other component of the DCDR advocacy, is subjected to improvements.
Anyone wishing to submit an improvement to the Data Lifecycle, can do so via the Data Lifecycle folder in the DCDR repository.
Establish a working group to research on the Data Lifecycle
Produce a research paper documenting the Data Lifecycle
Design a syllabus for the dissemination of the Data Lifecycle
Promote the awareness and understanding of the research results
Incorporate the research's results in the Universal Declaration of Digital Rights
Version 0.1
ShortURL | Playbook | Assistant | Contribute
NOTICE
The DCDR Framework is currently a work in progress.
A research focused on describing a taxonomy of data Use Cases on the basis of the DCDR Framework.
The following components inform the work for the DCDR Use Cases Taxonomy:
DCDR Framework
Digital Harms
Digital Rights
In order to understand how the DCDR Framework can be implemented in daily technology it is fundamental to analyze the different Use Cases that a data structure will go through its lifecycle and model them through the DCDR Components.
The Use Cases Taxonomy enables the work on the UDDR's DR SDK.
[Work in Progress]
As all materials created by The IO Foundation, the Use Cases Taxonomy, a component of the DCDR Framework, is published under TIOF Public Licensing Model.
The Use Cases Taxonomy, as any other component of the DCDR advocacy, is subjected to improvements.
Anyone wishing to submit an improvement to the Use Cases Taxonomy, can do so via the Use Cases Taxonomy folder in the DCDR repository.
Establish a working group to research on the Use Cases Taxonomy based on the DCDR Framework and its components
Produce a research paper documenting the Use Cases taxonomy
Design a syllabus for the dissemination of the Use Cases taxonomy
Promote the awareness and understanding of the research results
Incorporate the research's results in the Universal Declaration of Digital Rights
Version 0.1
ShortURL | Playbook | Assistant | Contribute
NOTICE
The DCDR Framework is currently a work in progress.
A research focused on establishing a technical description of the Rights that need to be applied to data to extend its lifecycle.
The DCDR Digital Harms informs the work for the DCDR Digital Rights.
The next step in the DCDR Framework is establishing the different Rights to be proactively applied over a data structure to expand an object's lifecycle to and arrange it under a taxonomy.
For technologists to adopt a Rights-protecting paradigm, they need to be able to technically describe the different Digital Harms they will want to avoid and, as a result the, Digital Rights they wish to observe.
The DCDR Digital Rights enables
establishing the DCDR Use Cases Taxonomy
In the DCDR Framework, a Right is any OPERATION that does not result in a HARM over an OBJECT Lifecycle (in TIME).
As all materials created by The IO Foundation, the Digital Rights Taxonomy, a component of the DCDR Framework, is published under TIOF Public Licensing Model.
The Digital Rights Taxonomy, as any other component of the DCDR advocacy, is subjected to improvements.
Anyone wishing to submit an improvement to the Digital Rights Taxonomy, can do so via the Digital Rights Taxonomy folder in the DCDR repository.
Establish a working group to research on the Digital Rights Taxonomy based on the Digital Harms Taxonomy
Produce a research paper documenting the Digital Rights taxonomy
Design a syllabus for the dissemination of the Digital Rights taxonomy
Promote the awareness and understanding of the research results
Incorporate the research's results in the Universal Declaration of Digital Rights
Version 0.1
ShortURL | Playbook | Assistant | Contribute
The Sagan Oath is an attempt to fill a disturbing void in the tech sector where technologists do not have a method to verbalize what is their purpose from the perspective of being active contributors of Digital Spaces and platforms that protect their users.
In the same spirit of the modern Hippocratic Oath (in which it is directly inspired at the time of its conception), the Sagan Oath attempts to express verbally the responsibilities that technology engineers should embrace.
The existence of the Hippocratic Oath allows doctors to understand what is it that they are protecting in a way that is relatable: Life - for which the concept of borders are unknown. As a result, doctors can pledge their knowledge to protect their patients, anywhere in the world they may be needed.
In the absence of such a covenant, technologists have struggled to generate the same global movement. The consequences have been painfully observed: technology is not currently designed with the objective to protect its users at its core.
The IO Foundation aims at complementing the DCDR Framework with an Oath that can help technologists to understand their fundamental role as Next Generation of Rights Defenders.
I swear to fulfill, to the best of my ability and judgment, this covenant:
I will respect my fellow citizens, for their problems and data, which is them in essence, are not disclosed to me that the world may know. Most especially must I tread with care in matters of life and death. If it is given me to save a digital twin, all thanks. But it may also be within my power to erase a digital twin; this awesome responsibility must be faced with great humbleness and awareness of my own technical prowess. Above all, I must not play at Digital God.
I will remember that I do not treat a dataset, a schema, but a citizen and their authentic digital twins, whose improper manipulation may affect the citizen’s family’s safety and economic stability. My responsibility includes these related problems, if I am to care adequately for people’s data.
I will strive to design architectures and to implement technology that embeds all existing protections whenever I can, for prevention is preferable to cure.
I will remember that I remain a member of society, with special obligations to all my fellow human beings, those with access to technology and those who don’t.
If I do not violate this oath, may I enjoy life and art, respected while I live and remembered with affection thereafter. May I always act so as to preserve the finest traditions of my calling and may I long experience the joy of building digital spaces that encourage societal growth while ensuring safety by design.
[Work in progress]
As all materials created by The IO Foundation, the Sagan Oath is published under TIOF Public Licensing Model.
The Sagan Oath, as any other component of the DCDR advocacy, is subjected to improvements.
Anyone wishing to submit an improvement to the Sagan Oath, can do so via the Sagan Oath folder in the DCDR repository.
Indeed there were.
Finding a suitable name for an Oath is no obvious task and no matter the final decision it will inevitably be subject to differences of opinion.
In the spirit of naming this Oath upon a inspiring, recognizable name, the following options were considered:
A scientist, in appreciation to his or her contributions in the domain of technology
A technological turning point in the shape of an invention or an event
Many names were considered such as Asimov, Babbage, ENIAC, Feynman, Tesla, von Newmann, Turing, Cray, Shannon or Postel. All of them contributed to the history of the technology we enjoy nowadays.
The final decision, albeit seemingly simplistic, was based solely in the recognition of what Carl Sagan represented in the dissemination of science to the general public. He was an expert that explained the necessary to citizens so that they could be informed and responsible users.
We live in a society exquisitely dependent on science and technology, in which hardly anyone knows anything about science and technology.
ShortURL | Playbook | Assistant
NOTICE
This section contains a list of the published books on the subject of the Data-Centric Digital Rights subject.
The IO Foundation is currently developing an introduction book exploring the deep interconnection and shared intricacies between the physical and the digital worlds and introducing the DCDR advocacy in an attempt to make the case for the necessary paradigm shifts in technology.
This documentation page is under construction. Should you want to be notified once it's published, .
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
The following section provides a comprehensive list of the Data-Centric Digital Rights' advocacy Teams and their descriptions.
A full taxonomy of TIOF Teams can be found in the Organization's Taxonomy.
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
ShortURL | Playbook | Assistant | Slides Repository
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
ShortURL | Playbook | Assistant
The following section contains the list of official operational handbooks (Standard Operational Procedures - SOPs) for the DCDR Advocacy initiative.
All SOPs need to comply with TIOF's Policies at all times.
These guidelines are to be followed by all TIOF Members participating in this initiative at all times.
For specific handbooks relative to other initiatives from The IO Foundation, please refer to their corresponding documentation space.
Handbooks are updated on-the-go as needs arise and comply at all times with TIOF's Policies.
ShortURL | Playbook | Assistant
NOTICE
This Handbook responds to the following Policies:
This handbook provides you with the necessary information to prepare and run an email campaign (EDM).
See General Structure in TIOF's Handbook.
You can always opt-out from any of these lists here:
Intended Audience:
Topics covered:
CTAs
See the Donors List on TIOF.
See corresponding Lists for each Initiative in their own in Handbook. TIOF - DCDR - BHR in Tech - CrowdShape - Project Lockdown - UDDR
See the Basic Structure in TIOF's Handbook.
This documentation page is under construction. Should you want to be notified once it's published, .
This documentation page is under construction. Should you want to be notified once it's published, .
Audience | Intended Audience | Topics Covered |
---|
Audience | Intended Audience | Topics Covered |
---|
|
|
|
|
Sponsors (Active) | Offers to sponsor TechUp |
Sponsors (Pending) | Offers to sponsor TechUp |
ShortURL | Playbook | Assistant
Data-Centric Digital Rights (DCDR) is the advocacy of protecting citizens' Rights by transparently implementing the regulations that should protect them.
As core stakeholders, technologists play a critical role as the NextGen Rights Defenders and need to orient themselves through new design and implementation paradigms focused on protecting citizen's digital twins.
The DCDR Principles put forward by The IO Foundation are concepts that help them navigate the intricacies of applying Human and Digital Rights in digital infrastructures, products and services.
Establish an easy reference guidance for technologists
Establish the premises for the conceptualization of the DCDR Framework
Design a syllabus for the dissemination of the DCDR Framework
Promote the awareness and understanding of the DCDR Principles
Serve as the basis for the Sagan Oath
Incorporate the DCDR Principles in the Universal Declaration of Digital Rights
ShortURL | Playbook | Assistant
The IO Foundation relies on funding support to advance its DCDR advocacy and develop its initiatives.
Your contribution goes straight to our work ensuring new technologies are architected and built to protect digital citizens.
We thank you for your support and for helping making possible a world where Human Rights and Data-Centric Digital Rights are one and the same.
IMPORTANT
As per The IO Foundation's Funding Policy, please note that donations are made without strings attached.
TIOF is an independent civil society organization and will remain so regardless of the contributions received and their origin.
You can donate using fiat currencies.
You can donate using crypto currencies.
ShortURL | Playbook | Assistant | Slides Repository
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
The following section provides a comprehensive list of terms employed in The IO Foundation's Data-Centric Digital Rights initiative.
Note to TIOF Members
A number of terms in this Terminology have a slide ready for presentations.
Please check the corresponding Slides Repository and remember to follow the Presentations guidelines when using them.
Acronym: | DCDR Framework: Layer X - Definition
See also:
A finite sequence of instructions that transform input data, and in turn generate output data, in order to perform a task or solve a problem.
Acronym: | DCDR Framework: Layer X - Definition
See also:
Source Entities exist in the analog space.
Acronym: AS | DCDR Framework: Layer X - Definition
See also: Digital Space
Ensemble of regulations that apply to all objects in a transaction in the DCDR Framework. These regulations can be established by any governance body or Community.
Acronym: | DCDR Framework: Layer X - Definition
See also:
Data conforming a Digital Twin component that maintains its entanglement with its source entity component.
Acronym: AD | DCDR Framework: Layer X - Definition
See also: Non-Authentic Data
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
In a spawning operation, Parent is the originating Object that is spawned and Child is the resulting spawn.
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Expression of agreement that grants permission to proceed with a certain proposal.
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
A collection of discrete meaningful values, collected or deduced, that can be stored, processed or transmitted.
Quantified information representing properties of a source entity.
A set of data, either authentic or non-authentic, arranged under a certain schema conforms a Digital Twin.
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Legal mechanism that aims at the protection of individuals with regard to the processing of Personal Data.
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: DCDR | DCDR Framework: Layer X - Definition
See also:
The advocacy bringing forward the observance of the Rights to be applied over data to protect it from its undue usage or extinction.
The basic principles protecting Representational Entities in Digital Spaces.
Acronym: DCDR | DCDR Framework: Layer X - Definition
See also:
A set of guiding concepts around which the conversation of DR is constructed.
Acronym: DCDR Principles | DCDR Framework: Layer X - Definition
See also:
Acronym: DCDR Framework | DCDR Framework: Layer X - Definition
See also:
Acronym: DL | DCDR Framework: Layer X - Definition
See also:
Acronym: DL | DCDR Framework: Layer X - Definition
See also:
A collection of interconnected hardware Nodes that collaborate to perform tasks where none of the parties is irreplaceable for a proper functioning. / to perform its expected SERVICES.
Acronym: DL | DCDR Framework: Layer X - Definition
See also:
The Representational Entity for any non-human Source Entity.
Assets are owned by Digital Communities.
Acronym: DA | DCDR Framework: Layer X - Definition
See also:
A collection of one or more Representational Entities, organized around a common objective.
Acronym: DC | DCDR Framework: Layer X - Definition
See also:
@@@Definition of the digital world from the perspective of the technology.
Acronym: DD | DCDR Framework: Layer X - Definition
See also:
Any algorithmic action that may bring closer the extinction of a given data point.
Acronym: DH | DCDR Framework: Layer X - Definition
See also:
Any algorithmic decision that will result in the occurrence of a Digital Harm.
Acronym: DHA | DCDR Framework: Layer X - Definition
See also:
The resulting damaging outcome, be it over the Representational Entity or its Source Entity, that will result in Digital or Physical Harm.
Acronym: DHO | DCDR Framework: Layer X - Definition
See also:
The Representational Entity for any human Source Entity.
Acronym: | DCDR Framework: Layer X - Definition
See also:
An algorithmic action that proactively prevents the occurrence of a Digital Harm on a given data point.
Digital Rights: Always use “Digital Rights” and not “digital rights”.
Digital Rights are the basic principles protecting Representational Entities in Digital Spaces. By extension, protecting Digital Rights is the way to observe Human Rights.
The collection of Digital Right
The basic principles protecting Representational Entities in Digital Spaces.
Acronym: DR | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Digital Spaces are, beyond the Internet, the collection of networks that, whether public or private, hold data representing a Source Entity which may be stored for digital processing with or without their consent and/or knowledge.
The collection of digital mediums, whether public or private, that may store digital twins in any way that conforms their identities, with or without their consent and/or knowledge.
The collection of digital mediums, whether public or private, that may store digital twins in any way that conforms their identities, with or without their consent and/or knowledge.
The collection of digital mediums, whether public or private, that may store users' Data in any way that conforms their identities, with or without their consent and/or knowledge.
Acronym: DS | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Digital replica of a living or non-living physical entity, organized around a schema.
Acronym: DT | DCDR Framework: Layer X - Definition
See also:
Acronym: DT | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
A distributed database that is used to maintain a list of records, called Blocks, which store an amount of data. By design, blockchains are resistant to modification of said data once recorded. Blocks and Envelopes are the building units of blockchain structures in 1Persona.
Acronym: DLT | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
A unique identifier that allows an emitter A to send a message to a receptor B unequivocally. Examples:
Email address
Telegram username
Mobile number
Physical address
Acronym: EID | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Human Rights: Always use “Human Rights” and not “human rights”.
Human Rights are the basic rights and freedoms to which all humans are considered to be entitled to.
Acronym: HR | DCDR Framework: Layer X - Definition
See also:
The advocacy bringing forward the observance of the Human Rights that are conferred to people.
Acronym: | DCDR Framework: Layer X - Definition
See also:
@@@The people who make possible the design, implementation and maintenance of the Digital Domain from the Analog Domain.
Acronym: | DCDR Framework: Layer X - Definition
See also:
Development and application of principles, policies, standards, decision-making procedures and programs that shape the evolution and use of the Internet.
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Format
Acronym: | DCDR Framework: Layer X - Definition
See also:
The collection of all States an object goes through from its genesis to its end.
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
A list of instructions, encoded using BPMN, that determines the behavior of Layer III objects and their Interactions.
Acronym: | DCDR Framework: Layer X - Definition
See also:
Any collection of Nodes is called a Mesh. When comparing two Meshes, one will be determined as SuperMesh (or Parent Mesh) while the other one will be labeled as SubMesh (Child Mesh). From the perspective of a Node, the Mesh it belongs to is always named OwnMesh. The Mesh that represents the ensemble of the running Network is called PrimeMesh.
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: NAD | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also: List of Objects per Space & Layer >> Taxonomy / Schema
A desired modification of one or more states measured by a set of KPIs.
Acronym: NAD | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Any harm received by a physical entity.
Any harm applied, be it Physical (PH) or Digital (DH).
What you seek to protect.
Acronym: PH | DCDR Framework: Layer X - Definition
See also:
Any harmful action, be it Physical (PHA) or Digital (DHA).
Acronym: PHA | DCDR Framework: Layer X - Definition
See also:
Any harmful outcome, be it Physical (PHO) or Digital (DHO).
Acronym: PHO | DCDR Framework: Layer X - Definition
See also:
Acronym: PL | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
The required number of Nodes in a Mesh to ensure its proper and full functionality.
Acronym: RT | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
A templated organization of data that provides an understanding about the nature and the utility of a given set of data.
Acronym: | DCDR Framework: Layer X - Definition
See also:
Analyzing a system by removing a number of objects and discarding a number of dimensions in order to understand something.
Acronym: | DCDR Framework: Layer X - Definition
See also:
Source Entities are any Analog object that is susceptible to be represented in any digital shape by ways of data that defines its characteristics.
Acronym: SE | DCDR Framework: Layer X - Definition
See also:
A Space object always acts as the Genesis Object for all its contained objects.
Acronym: | DCDR Framework: Layer X - Definition
See also:
The action of creating a replica of an Object that remains linked over the course of its usage.
Acronym: | DCDR Framework: Layer X - Definition
See also:
The outcome of the division of the Internet due to various factors, such as technology, commerce, politics, nationalism, religion and divergent national interests.
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Representational Entities are the resulting digital model obtained from data from any Source Entity.
The digital representation of people and objects in Digital Spaces.
Acronym: RE | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
The UDHR is the international document reference, proclaimed by the United Nations, that serves as the foundation to the observance of Human Rights worldwide.
A set of legal and technical standards to ensure the observance, compliance and implementation of Digital Rights.
Acronym: UDHR | DCDR Framework: Layer X - Definition
See also:
The UDDR is a set of legal definitions and technical standards to ensure the observance, compliance and implementation of Data-Centric Digital Rights.
Acronym: UDDR | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
Acronym: | DCDR Framework: Layer X - Definition
See also:
ShortURL | Playbook | Assistant
NOTICE
This documentation page is under construction. Should you want to be notified once it's published, let us know.
Version 0.1
ShortURL | Playbook | Assistant | Contribute
NOTICE
The DCDR Framework is currently a work in progress.
A research focused on establishing a technical description of the Harms that can be applied to data across its lifecycle.
The DCDR Data Lifecycle informs the work for the DCDR Digital Harms.
The next step in the DCDR Framework is establishing the different Harms a data structure can be subjected to and arrange it under a taxonomy.
For technologists to adopt a Rights-protecting paradigm, they need to be able to technically describe the different Digital Harms they will want to avoid and, as a result the, Digital Rights they wish to observe.
In the DCDR Framework, a Harm is any OPERATION that shortens an OBJECT Lifecycle (in TIME).
The DCDR Digital Harms informs the work for the DCDR Digital Rights.
As all materials created by The IO Foundation, the Digital Harms Taxonomy, a component of the DCDR Framework, is published under TIOF Public Licensing Model.
The Digital Harms Taxonomy, as any other component of the DCDR advocacy, is subjected to improvements.
Anyone wishing to submit an improvement to the Digital Harms Taxonomy, can do so via the Digital Harms Taxonomy folder in the DCDR repository.
Establish a working group to research on the Digital Harms Taxonomy based on the Data lifecycle
Produce a research paper documenting the Digital Harms taxonomy
Design a syllabus for the dissemination of the Digital Harms taxonomy
Promote the awareness and understanding of the research results
Incorporate the research's results in the Universal Declaration of Digital Rights
ShortURL | Playbook | Assistant
Treat other people's data the same way you want to be treated.
The traditional understanding of data as separate entities from their users is anchored in past perceptions and the use of legacy technologies.
The reality is much different: The data representing users (and of which they should have control of consent) is intimately and inextricably linked to them; it models them, creating an accurate representation that loses all value should that contextualization ever be severed.
The direct consequence is that a user’s data IS the user itself.
REMARKS
Do note that this understanding has crucial consequences as the same duties of care that apply by constitutional laws to citizens should equally apply to the data representing them.
In this sense, the necessary infrastructures that governments put in place to protect their citizens (hospitals, highways, the judiciary and so forth) should also be extended to the management and protection of their data with a national cloud system based on open standards and governed by a framework on Data-Centric Digital Rights.
ShortURL | Playbook | Assistant
Adopt designs that minimize grievances.
This DCDR principle represents the embodiment of the proactive planification, architecture and implementation of all necessary mechanisms, both in policy and technology, to avoid grievances to ever happen during the use of a product or a service, in turn minimizing the need for legal actions.
REMARKS
In the context of Data Protection Laws, it implies the design of policies that protect Data Subjects and the implementation of such provisions in a transparent, trustworthy and safe manner where legal remedies, while defined, are only employed as a safety net.
ShortURL | Playbook | Assistant
Leave no policy uncoded behind.
This DCDR Principle responds to the need for policies and tech to be designed and implemented as one: the former establishes what is to be respected and the latter ensures that the compliance is built in the infrastructure so that users are protected automatically and transparently.
On other words, any protection a citizen or its digital twins are subjected to under a specific jurisdiction should be transparently implemented inside the technology itself, by design.
REMARK
Do note that this is a concept that is evidently applicable beyond the domain of technology, which is highly