A protocol built for real-world use
The Dataspace Protocol defines how data space connectors communicate within a data space. It covers essential functions like data catalog access, contract negotiation, and data transfer management, all built on proven HTTPs technologies and fully RESTful.
But there’s more to it. The protocol has been designed with flexibility in mind. For example, it allows various authorization mechanisms. It works with the Decentralized Claims Protocol, but an extension to other protocols – for example OAuth2, OpenID Connect, and even no authentication for public datasets could be possible. That makes it usable across a wide range of use cases, from industrial platforms to open government data portals.
Another important addition is the support for multi-tenant deployments. This means a single organization can now host multiple connectors for different clients or business units on one infrastructure. The need for such flexibility became clear during implementation in real-world initiatives like Cofinity-X and Catena-X.
Clarity and confidence for developers
To support adoption, the team behind DSP developed a Technology Compatibility Kit (TCK) – a set of automated tests that verify whether a connector complies with the DSP.
This test suite checks implementations against more than 140 test cases. It covers metadata formats, catalog endpoints, contract flows, and transfer protocols. The TCK is open source and designed to be used in continuous integration environments, making compliance easier to maintain over time.
Two implementations have already passed the TCK and published their test reports:
- Eclipse Dataspace Components (EDC)
- TNO Secure Gateway (TSG)
Both projects are public and well-documented, making them useful references for others. The EDC, in particular, has been a key contributor throughout the process and is the compatible implementation in the Eclipse Specification process.
Call to action: test, report, share
To support transparency, IDSA encourages all connector developers to test their solutions with the TCK and share the results. Even partial compliance is welcome, as long as it is documented.
A central listing of these results will be published in the updated Data Space Connector Report. This document will include configurations, testing outcomes, and links to source code or test logs – helping others understand what works, what needs attention, and who’s working on what.
Future-ready
Another major achievement: The DSP defines its versioning and supports backward and future compatibility. That means changes in future versions won’t break existing implementations. This is especially helpful for large ecosystems, where connectors evolve at different speeds.
The final version of the specification is expected to be released by mid-July 2025. Looking further ahead, the ambition is to bring DSP to ISO. Whether or not it becomes a formal international standard, the protocol is already shaping how data spaces are being built – across Europe and beyond.
