Common European data spaces are sector-specific frameworks, promoted by the European Union, that combine shared rules, governance bodies and technical infrastructure so that companies, public bodies and individuals can exchange and reuse data across borders under conditions they can trust. In data regulation, the term names the delivery mechanism of the European data strategy of 2020: instead of one central database, each data space is a federated ecosystem in which data stays with its holder and moves only under agreed terms.
The concept sits on top of horizontal legislation such as the Data Governance Act and the Data Act, and it gains its first binding sector law in the European Health Data Space. Data spaces are therefore partly a policy program, partly a legal framework and partly a reference architecture, which explains why the phrase is often used loosely in practice.
How a data space is built
A data space is defined less by where data is stored than by how participants agree to share it. Data remains in the systems of its holders, and a common layer of identity, cataloging, contract and usage-control services lets a recipient find a dataset, negotiate terms and receive the data peer to peer. This design avoids the trust and competition problems of a single central platform.
Most designs follow building blocks described by the EU support program for data spaces and by industry initiatives such as Gaia-X and the International Data Spaces Association. The table summarizes the main layers and the role each one plays.
| Building block | What it provides | Typical implementation |
|---|---|---|
| Governance framework | Membership rules, roles, dispute handling | Rulebook signed by all participants |
| Identity and trust | Verified identities of organizations | Trust anchors, verifiable credentials |
| Data catalog | Discovery of available datasets | Metadata in DCAT-AP style profiles |
| Connector | Controlled exchange between parties | Dataspace connector software |
| Usage policies | Machine-readable terms of use | Policy languages such as ODRL |
| Interoperability layer | Common formats and vocabularies | Sector data models and semantic standards |
The connector is the practical heart of the model. Each participant runs one, and connectors negotiate a contract agreement before any transfer, which allows a holder to attach conditions such as purpose limits, retention periods or a ban on onward sharing. Enforcement of those conditions after delivery remains partly technical and partly contractual.
The sectoral data spaces
The European data strategy named nine initial domains, and later work programs added more, so the list is open rather than fixed. Each data space progresses at its own speed, with different funding instruments, legal bases and maturity levels.
| Data space | Main data shared | Status of legal basis |
|---|---|---|
| Health | Electronic health records, research data | Dedicated regulation adopted |
| Mobility | Traffic, transport and logistics data | Builds on transport legislation |
| Energy | Grid, metering and flexibility data | Builds on energy market rules |
| Agriculture | Farm, soil and supply chain data | Mainly voluntary codes |
| Manufacturing | Production and product data | Mainly voluntary, Data Act relevant |
| Financial | Customer and market data | Linked to the proposed FIDA framework |
| Public administration | Public sector and procurement data | Open Data Directive and high-value datasets |
| Green Deal | Environmental and climate data | Builds on environmental reporting law |
Other domains, such as skills, media, tourism, cultural heritage, research and security, also have data space initiatives. The health data space stands out because it creates enforceable rights and obligations, including rules on secondary use of health data through national health data access bodies.
The legal framework behind data spaces
No single regulation creates all common European data spaces; the legal basis is a layer of horizontal acts plus sector rules. The Data Governance Act sets conditions for data intermediation services and data altruism organizations and creates the European Data Innovation Board, which advises on interoperability across data spaces.
The Data Act, applicable from September 2025, adds rights to access data generated by connected products, rules against unfair data-sharing terms, cloud switching obligations and essential requirements for the interoperability of data spaces and smart contracts. Personal data in any data space remains fully subject to the GDPR, which is often the hardest constraint in practice.
| Instrument | Contribution to data spaces | Key limitation |
|---|---|---|
| Data Governance Act | Trusted intermediaries, data altruism, board | Does not force anyone to share |
| Data Act | Access rights, interoperability requirements | Focus on connected product data |
| Open Data Directive | Reuse of public sector information | Covers public bodies only |
| European Health Data Space | Binding health data access rules | Limited to the health sector |
| GDPR | Lawful basis and rights for personal data | Applies regardless of the data space |
Data spaces compared with other sharing models
Data spaces are easiest to understand when contrasted with older ways of sharing data. The decisive difference is data sovereignty: the holder keeps control over who uses the data and for what purpose, rather than handing it to a platform operator.
| Approach | Where data sits | Control by the holder |
|---|---|---|
| Common European data space | With each holder, federated | High, through policies and contracts |
| Central data lake | In one shared repository | Low once data is uploaded |
| Commercial data marketplace | Often with the marketplace | Depends on platform terms |
| Open data portal | Published for anyone | None after publication |
| Bilateral data agreement | Transferred to one partner | Contractual only, hard to scale |
A data space can include a marketplace or an open data portal as one participant, so these models are not mutually exclusive. The added value lies in standard contracts and interoperable technology that lower the cost of each new sharing relationship.
Practical challenges and common misconceptions
Building a functioning data space is mostly an organizational problem, not a software problem. Participants must agree on who pays for infrastructure, how liability is allocated and which semantic standards to adopt, and these negotiations usually take longer than deploying connectors.
- Not a single database: a data space does not centralize data, and calling a shared repository a data space misrepresents the model.
- Not automatically compliant: joining a data space does not create a lawful basis for processing personal data under the GDPR.
- Not mandatory by default: outside health and certain Data Act rights, participation is largely voluntary and incentive-driven.
- Interoperability is the bottleneck: without shared vocabularies, data arrives technically but cannot be used meaningfully.
- Usage control has limits: once a recipient can read data, policies rely on audits and contracts as much as on technology.
A non-technical view
Imagine a large shared library where every book stays on its owner’s shelf at home. A common catalog shows what exists, a membership card proves who you are, and a lending agreement says how long you may keep a book and what you may do with it. Common European data spaces work in the same way for data.
The goal is to let hospitals, farms, factories and city authorities share useful data safely without giving up control. Everyone follows the same rules, so a new partner does not need to negotiate everything from scratch.
A concrete example
A regional cooperative of grain farmers wants to cut fertilizer costs. Its members hold soil sensor readings, yield maps and machinery logs, while a research institute holds weather models and a fertilizer supplier holds product composition data. Through an agricultural data space, each party runs a connector and publishes metadata in the shared catalog.
The institute requests three seasons of anonymized yield and soil data under a usage policy that allows research use only for 24 months and forbids resale. The farmers receive field-level nitrogen recommendations in return. Because the rulebook, contracts and data formats were already agreed, the exchange starts within weeks instead of months, and each farmer can withdraw future data at any time.