Description of the building blocks needed to operationalise the governance. They are more technically detailed in Chapter 8.
6.4.1. Personal Data Intermediary Building block #
This section details the description and key functionalities of building blocks ensuring the well-functioning of a Personal Data Intermediary and thus ensuring people oversee the use of their data.
Table 25: Personal data intermediary.
Personal Data Intermediary # |
|
Description | Ensuring that human centricity aspect is taken care of in every decision. |
Key Elements & Key Functions | · The Personal Data Intermediary (PDI) enables individual end users to control their data in the data space.
· It allows them to manage consents and authorisations, be informed on the usage of their data, the value, and risks of sharing it. · It can be integrated into the interfaces of the participants and individual end users can also access it through a central interface. · It represents the individual in the data space and can have the authority, granted by the individual to exercise its rights on its data. · It is composed itself of several building blocks to enable its functionalities such as: consent management, identity management. |
Table 26: PDI Consent building block.
PDI Consent Building block # |
|
Description | Ensuring that human centricity aspect is taken care of in every decision. |
Key Elements & Key Functions | · The consent service allows participants of the data space to generate a consent towards an end user to share their data with another participant of the data space.
· People can manage their consent from the services concerned in the data exchange or from their Personal Data Intermediary where they can find and manage all their consents from a single place. · The consent is generated from a data sharing agreement existing between the parties sharing the data; the consent triggers the real data exchange or access. |
Table 27: PDI Identity building block.
PDI Identity Building Block # |
|
Description | Ensuring that human centricity aspect is taken care of in every decision. |
Key Elements & Key Functions | · Ensuring interoperability across personal identities, providers and standards, including identity delivery tools that are compatible with the use of wallets.
|
Table 28: PDI Decentralised AI training.
PDI Decentralised AI Training # |
|
Description | Ensuring that human centricity aspect is taken care of in every decision. |
Key Elements & Key Functions | · This BB supports AI training in the cases that uses personal data directly from PDI.
· The users give or revoke the right to mobilize their data, wherever it is stored, to train AI models. · A decentralized federated learning protocol allows to train AI models without disclosing users’ contributions. Whereas today, the training of AI imposes the need to provide the data in clear to a central actor. Individuals no longer have to arbitrate between altruism and confidentiality. Since data is no longer shared, AI researchers can focus on their core business because they no longer have to spend time on compliance for data access. · By mobilizing data at its source, decentralized learning increases the relevance of AIs by allowing them to train on more transversal, sensitive and up-to-date data, from multiple sources: data is no longer shared to benefit from the service. · AI and/or language models for Personal Data intermediaries can be developed in many ways. There are many scientifically, legally and ethically valid methods to train AI / language models with personal data that can be used in Data Spaces context. Such AIs should follow PDI Trustworthy Algorithm guidelines as well as guidelines described for AI Building Blocks in the section 7.3.2 |
Table 29: PDI Distributed Data Visualisation.
PDI Distributed Data Visualisation # |
|
Description | Ensuring that human centricity aspect is taken care of in every decision. |
Key Elements & Key Functions | · Allowing recommendations to be shown to people in any UI of the data space
· The data model that is built/constructed/manipulated in the service layer (data storages, APIs, AIs, service providers, etc) and/or in the edge and finally passed to the UI/visualization component in client side. · Visualization component that can be embedded into any application like Google Ad -plugin component can be embedded into any web page or app. This Google Ad -type of approach is meant to ensure the UI & visualization mechanism is embeddable to any part of the data space. |
Table 30: PDI Catalogue.
PDI Catalogue # |
|
Description | Ensuring that human centricity aspect is taken care of in every decision. |
Key Elements & Key Functions | · Allowing people to have a user-friendly catalogue of data users and sources of their personal data space and interact with them from a single point.
· Allowing people to easily navigate and find the apps, data users and data sources of their personal data space and be matched with the most relevant applications according to their needs and preferences. · Allowing people to be informed on the risks and value of sharing their personal data with the data space participants. |
Table 31: PDI Trustworthy AI Assessment.
PDI Trustworthy AI Assessment # |
|
Description | Ensuring that human centricity aspect is taken care of in every decision. |
Key Elements & Key Functions | · Fairness: Ensure that decisions made by the AI system are not biased towards a particular group or individual. This ensures that the person is treated fairly and does not face discrimination or unfair treatment due to their race, gender, or any other attribute.
· Explainability: Provide transparency in the consequential decision-making process, explaining how the AI system arrived at a particular decision. This helps people understand why a particular decision was made and provides clarity and assurance in the decision-making process. |
6.4.2. General Governance Building blocks #
This section details the description and key functionalities of building blocks ensuring the implementation of the governance model previously described and of the responsibilities of each role.
Table 32: Rulebook and Rolebook
Rulebook and Rolebook # |
|
Description | Allow rules, and obligations to be respected across the data space and data space use cases. |
Key Elements & Key Functions | · The Rulebook of an ecosystem is a set of common rules & policies for data access that apply within that particular ecosystem.
· A Rulebook contains rules coming from: hard law, soft law, and the ecosystem internal decision-making. · All bodies involved in the definition or application of rules, at all levels including outside the ecosystem, are part of the Rolebook. · Rules within the Rulebook can refer to or apply to bodies and roles defined in the Rolebook. · The Rolebook is an open, transparent, and dynamic registry of functions (roles) and decision-making entities (bodies) for data sharing. · PDI, which are part of the Rolebook, allow individuals to participate in the governance of the different ecosystems handling their data sharing use cases. |
Table 33: Contractual Framework.
Contractual Framework # |
|
Description | · Allow standardized negotiations and agreements between the parties.
· Collect all core aspects of a use case implementation in written form, establish valid legal commitments for data sharing and promote standardized ways of operation. · Bind the data consumer to data producer to a written agreement defining who can access what of how the data is to be used. · Minimize transaction costs. · Ensure fair, transparent, and compliant agreements in data spaces. · Support interoperability. |
Key Elements & Key Functions | · Templates for different use cases and mechanisms to allow automated agreements based on technical policies.
· Dynamic links to the regulatory framework & regulatory changes to allow compliance with upcoming rules. · Proposes a set of clauses for use case implementation with European wide applicability. · General code of conduct to ensure the data space participants follow similar values and principles. · Policy enforcement. · Protect individual rights. · Specify access rights. · Specify usage patterns/outcomes. |