This proposal aims to bring the policies profile needed in any dataspace for establishing connections to the trust framework. This proposal complements the IDSA dataspace protocols and decentralised claims protocols that are under the Eclipse Dataspace Working Group.
It will enable organizations to perform data exchange/sharing by binding it to a specific trust framework and connecting the policies for different roles in the trust framework to the transactions.
The key enabler of data sharing is Trust and organizations have been not sharing their data as they lack trust on other organizations and lack control over the data they share with them. This has been addressed by iSHARE Framework and is in use by businesses and governments today to share data.
The Eclipse Data Rights policies profile provides a set of specifications designed to facilitate interoperable trust between entities that comply with Trust Frameworks and data spaces requirements. These specifications define the schemas required for entities to identify and authenticate each other to share/access data based on the authorisations given by the data rights holder.
- Defines a generic role model for participants of a dataspace and mapping to the protocol layers
- Defines schemas and requirements thereof for tokens necessary for data exchange between participants
- Linkage to a trust framework to enable trusted data exchange as authorised by data rights holder
- Linkage to further data space specific policies
Out of scope:
- Semantic models of various tokens
- Domain and/or region specific requirements
- iSHARE compliance
- Trust framework schema and specifications
The Eclipse Foundation provides the Eclipse Dataspace Working Group including the Eclipse Governance Framework a good foundation to create an Eclipse Specification in a Specification Project that combines the required assets, the specification document, a TCK, and a compliant implementation.
Although this specification is already implemented and proven in more than 36 dataspaces we think bringing it under eclipse foundation's specification process will help in evolving it further and accelerate the broader adoption.
The initial contribution of the specification document is created under the umbrella of the Stichting iSHARE Foundation. The IP remains under the Stichting iSHARE Foundation, however it grants usage rights to this specification project and implementations based on thereof
- Initial contribution of specification document in Q2 2024
- Initial contribution of TCK in Q2 2024
- Association of compliant Implementation, e.g. EDC in Q2 2024
- Association with EDWG in Q2 2024
- Finalize the Specification document until summer 2024
- Finalize the TCK until late summer 2024
- Compliant Implementation of the Specification in EDC until late summer 2024
- Pass Submission to ISO after Summer 2024
- Associate with the EDWG to promote the project(s) as soon as possible
Trust forms the basis for any data exchange transactions to occur. However, the control and transfer as well as claims protocols are trust agnostic and they are expected to connect to (one or multiple) trust frameworks.
Since each dataspace is free to choose its own topology as well as standards and trust frameworks it uses/requires, the participants must be able to establish trust and fulfill requirements of the trust framework in order to perform trusted data exchange.
The proposal aims to establish requirements in the form of profiles which enables organizations to use these profiles with any of the protocols underneath and complete the connection to trust framework.
In a Data exchange transaction there may be various parties involved in different roles as defined in the trust framework and the mapping to those roles in a transaction is necessary to understand how the compliance and other requirements of the trust framework apply.
Example:
-
A Connector that is requesting the data from another connector is acting on behalf of a participant and the policies of trust framework as well as dataspace apply to it.
The role model is used to determine the appropriate functions and requirements for those components in a given data exchange context.
iSHARE Foundation, International Data Spaces Association, Fraunhofer, Microsoft, Bosch, SAP, Tecnalia, Bosch, Catena-X, Data Spaces Support Centre, TNO, T-Systems and any organisation that wants data sovereignty.
The Eclipse Data Rights policies profile (DRP) is based on existing activities and usage of iSHARE trust framework under the maintenance of the Stichting iSHARE Foundation. All content was created by the iSHARE members/participants under the IP control and governance of Stichting iSHARE Foundation. The Stichting iSHARE Foundation holds the copyright of the repository. The contributors to the document will join the Eclipse Specification Project as contributors and will continue to work on the Specification Document, the Technology Compliance Kit and compliant implementations.
- Log in to post comments