MyDataSpace
A data space to publish, discover, negotiate and consume data between organizations. Every participant runs its own Eclipse EDC connector, and access is governed with verifiable identity, policies and contracts: once the contract is accepted, the consumer's connector downloads the data over DSP from the provider's connector.
Data space catalogue
This view brings together the assets every participant of publishes from its own connector. The home page is browse-only; contract acceptance and download happen from authenticated connectors.
Ask the catalogue
Tell me what data you need, or what for, and I'll suggest the best fits. I only answer about this data space's catalogue.
Gaia-X Danube compliance
Participants holding a valid compliance label, issued by the local Gaia-X Danube clearing house gxdch.mygovernance.es. Registration number verified by MyDataSpace (the data space notary), not by an official register. Clearing house not recognised by Gaia-X AISBL.
What this data space is
MyDataSpace is a data space open to any organization, with no closed theme: each entity publishes its own. What is in the catalogue today is real open data about mobility and traffic —urban traffic cameras, road traffic counts, origin-destination mobility matrices and real-time traffic—, published by the entities that operate or reuse them, citing their source and licence.
Nothing downloaded here is made up: the provider's connector fetches the file from its source and delivers it as it is.
Every participant of has its own Eclipse EDC connector, with a
did:web identity and a membership credential issued by the data space, and publishes to the shared
catalogue. Negotiations, downloads and sends are recorded as signed events at .
There are three ways in: as an individual, as an entity, or as a user of an entity already registered, which is then the one that approves the sign-up and sets the profile.
Go to login Go to registerWhat happens when someone takes a dataset
A download is not a link: it is a real negotiation over the Dataspace Protocol between two independent connectors that identify each other with verifiable credentials. The consumer accepts the published policy, a contract agreement is signed, and only then does the data leave the provider's data plane. It reaches the consumer through the portal's connector gateway, which passes it on in transit and does not store it.
What the connectors enforce is membership of the data space. The policy's usage clauses —purpose, geographic scope, retention, AI use, licence— are stored and published as information for the parties, but they are not technically enforced.
The completed negotiation, the completed download and every send to a destination are kept as signed events outside the connector, and every downloaded file also goes through the document audit. The console's catalogue, negotiation, download and send requests are also written to the portal's state-transition log. So both provider and consumer can later show what was shared, under which agreement and with whom.
Current architecture
MyDataSpace is a single data space. It is not federated with other data spaces: catalog, negotiation and download happen between its own participants.
- One connector per participant: every approved sign-up gets its own Eclipse EDC 1.0 connector —control plane, data plane and IdentityHub— with a did:web identity and a membership credential issued by the data space.
- Data space catalog: brings together the offers each connector publishes, with DCAT-AP metadata and ODRL policies.
- Negotiation and transfer: the consumer's connector negotiates with the provider's over the Dataspace Protocol; the data leaves the provider's data plane and the portal's gateway delivers it in transit, without storing it, to the user's browser or Databricks.
- Gaia-X compliance: the data space acts as notary and issues each participant its legal person and registration number credentials, which a Gaia-X Danube clearing house turns into a compliance label.
- Governance: receives the signed audit traces, keeps the evidence and analyses documents with Mistral.
Institutional alignment and standards
MyDataSpace implements the standards and principles of data sovereignty defined by leading organizations in the data spaces ecosystem:
IDSA
International Data Spaces Association defines the reference architecture and technical standards for sovereign data spaces that ensure interoperability, security and governance.
internationaldataspaces.org →Eclipse Foundation
Maintains the Eclipse Dataspace Components (EDC), the open-source implementation of the Dataspace Protocol that every connector in this data space runs.
projects.eclipse.org/transit.edc →Gaia-X
European initiative for a sovereign and trustworthy digital infrastructure. This data space issues credentials following its compliance framework, with its own Danube clearing house, which is not recognised by Gaia-X AISBL.
gaia-x.eu →DSSC
Data Spaces Support Centre provides guidance, best practices and support for data space deployment in Europe, aligned with Gaia-X.
dssc.eu →Design pillars
- Data sovereignty: each participant decides what it publishes from its own connector and under which policy; the connectors enforce membership of the data space, and the usage clauses are informative
- Interoperability: Based on open standards from IDSA and Eclipse Foundation
- Trust: connectors identify each other with verifiable credentials (DCP); people reach their console through Keycloak
- The data does not stay in the middle: the download runs from the provider's data plane to the consumer through the portal's gateway, which does not store it, with an accepted contract behind it
- Operational traceability: a signed record of negotiations, downloads and sends, kept outside the connector that produced it