The Eclipse Dataspace Protocol Is Pioneering Interoperability and Standardisation in Dataspaces

In an era where data is the new currency, the seamless and secure exchange of information between different entities is paramount. In this context, the Eclipse Dataspace Working Group is proud to unveil the Eclipse Dataspace Protocol (DSP). This initiative is a significant leap towards achieving robust interoperability and standardisation in dataspaces and alignment with global standards and emerging legislation.

Efforts Aligned With International Developments

The Eclipse Dataspace Protocol is a culmination of extensive efforts by the International Data Spaces Association (IDSA) and builds upon its foundational work, including the IDS-Reference Architecture Model (v4.0) and IDSA Rulebook. 

The primary objective of the DSP is to standardise the core fundamentals required for the implementation of dataspaces, ensuring a unified and interoperable framework for data sharing across various entities (Figure 1). This standardisation effort is also aligned with the work conducted in ISO/IEC JTC1 SC38 (cloud computing and distributed platforms), further cementing its relevance and applicability on a global scale.

Figure 1: The fundamental components required for a unified and interoperable data sharing framework. (Source: IDSA)

Comprehensive Specifications Govern Publishing, Usage, and Data Access

The DSP is designed to facilitate interoperable data sharing between entities, governed by stringent usage control measures, and is grounded in web technologies. The protocol encompasses specifications defining how entities can publish data, negotiate usage agreements, and access data within a federation of technical systems known as a dataspace (Figure 2). 

Figure 2: How specifications within the protocol interact and interrelate. (Source: IDSA) 

Key aspects covered by the DSP include:

• Metadata provisioning: Using data transfer protocols to facilitate the transfer of assets by provisioning metadata.
• Usage control policies: Defining how data assets are deployed as DCAT Catalogs and usage control is expressed through ODRL Policies.
• Contract agreements: Establishing syntactical expressions and electronic negotiation mechanisms for contract agreements governing data usage.
• Data access: Outlining protocols for accessing data assets using established data transfer protocols.

The DSP specifications are meticulously organised into several key documents, each addressing different facets of the protocol:

• Dataspace Model and Dataspace Terminology: These documents define the foundational terms and concepts.
• Catalog Protocol and Catalog HTTPS Binding: These specifications describe how DCAT Catalogs are published and accessed via HTTPS endpoints.
• Contract Negotiation Protocol and Contract Negotiation HTTPS Binding: These detail the procedures for conducting and requesting contract negotiations through HTTPS endpoints.
• Transfer Process Protocol and Transfer Process HTTPS Binding: These outline how transfer processes are governed via HTTPS endpoints.

Core Features of the Eclipse Dataspace Protocol

The DSP is built around five core features that provide the fundamental basis for standardised, interoperable, and secure data sharing within dataspaces:

• Interoperability at its core: The DSP fosters technical interoperability among participants in dataspaces. This is achieved by providing a clear framework for how data interactions should be conducted, ensuring that different systems can communicate seamlessly.
• Metadata provisioning: DSP facilitates the transfer of data assets by making use of standardised metadata provisioning. This is crucial for maintaining the integrity and usability of data as it moves between different entities.
• Usage control and agreements: The protocol allows for the electronic negotiation of data usage agreements. By using state machines to manage these negotiations, DSP ensures that all interactions are robust and traceable.
• Data transfer protocols: While DSP does not cover the data transfer process itself, it provides guidelines on how to control this process via the Transfer Process Protocol. This ensures that data transfer is secure and efficient, with clear handling of technical exceptions.
• Trust and security: Identity Providers play a crucial role in maintaining trust within dataspaces. They validate the identities and claims of participant agents, ensuring that only authorised entities can access and share data.

DSP Is Aligned With EU Initiatives and the Data Act

In the context of global data governance, the European Commission’s Data Act is a significant legislative effort aimed at ensuring fair access to data and promoting a thriving data economy. Hence, aligning the Eclipse Dataspace Protocol with the Data Act is a critical aspect of our mission.

Chapter VIII of the Data Act is especially relevant, as it emphasises the importance of standards and interoperability for seamless data exchange within and between dataspaces. This chapter lays the groundwork for effective collaboration and innovation across various sectors by mandating common standards and protocols. These requirements are in perfect harmony with the goals of the DSP, which is designed to facilitate interoperable data sharing governed by usage control, ensuring secure and efficient data transfer.

Interoperability is crucial for enabling different systems and platforms to communicate effectively, thereby amplifying the value of shared data assets. By adhering to the interoperability standards outlined in Chapter VIII, the DSP ensures that dataspaces can function as interconnected ecosystems, promoting synergy and innovation.

Furthermore, the Data Act’s focus on data security, privacy, and fair business practices aligns with the DSP’s objectives. Chapters III and IV of the Data Act address mandatory business-to-business data sharing and protection against unfair contractual terms, respectively, ensuring that data holders and recipients operate on fair and reasonable terms. Chapter VII safeguards data against unlawful access by third-country governments, emphasising the importance of data security — a core component of the DSP.

Dataspaces are a vital mechanism for implementing the Data Act’s vision. They must be built on interoperable and scalable technologies, adhere to open standards, and foster open and trusted ecosystems. The Eclipse Dataspace Working Group, through the DSP is committed to advancing these principles, ensuring that dataspaces not only comply with but also thrive under the regulatory framework established by the Data Act.

Project Proceeding Toward ISO Submission This Year

The development and implementation of the DSP are well on track, with significant milestones set for 2024:

• Q1 2024: Initial contribution of the specification document, test compatibility kits (TCKs), and association with a compliant implementation (e.g., EDC).
• Summer 2024: Finalisation of the specification document and TCK.
• Late Summer 2024: Completion of a compliant implementation in EDC.
• Post-Summer 2024: Submission of the specification to ISO for PAS consideration.

Join the Forefront of a Groundbreaking Transition

The Eclipse Foundation offers an excellent platform for the development and standardisation of the DSP. With its robust governance framework, the Eclipse Foundation supports the creation of comprehensive specifications, TCKs, and compliant implementations. The Eclipse Dataspace Components project, under the Eclipse Dataspace Working Group, is already working on implementing the DSP, furthering its adoption and integration.

The Eclipse Dataspace Protocol is a testament to our commitment to fostering interoperability and standardisation in dataspaces. By joining our Dataspace Working Group, you can be at the forefront of this groundbreaking transition. We invite all stakeholders, from technical experts to organisational leaders, to collaborate with us in refining and promoting the DSP. Together, we can ensure that data sharing is seamless, secure, and beneficial for all parties involved.

For more details and to get involved, visit our GitHub repository. Let’s take this significant step towards a future where data interoperability and standardisation are the norms, not the exceptions.