01
Where it fits and where it does not
Use these four checks before committing implementation time.
- Use it when
- Governed exchange across organizational and cloud boundaries where discovery, contract negotiation, and transfer must interoperate without centralizing all data.
- Limits
- DSP does not define scientific schemas, data quality, federation governance, identity assurance, or every transfer protocol; current implementation evidence is concentrated in the Eclipse dataspace ecosystem.
- Best for
- Cross-cutting teams working across Exchange → Learn + reuse.
- Maturity
- ScalingUsable now, but adoption or tooling is still developing. Pilot the exact stack first.
02
See it in the workflow
This view shows the input, the change the standard introduces, and the resulting output.
- InputWhat starts
Cross-cutting source data, metadata, and local mappings
- DSPWhat changes
Use DSP as a pinned standard across Exchange → Learn + reuse
- OutputWhat becomes possible
A handoff the next system or team can validate against the same release
03
A concrete example
Expose a participant catalog, negotiate a versioned agreement, record the resulting contract and policy decisions, initiate an agreed transfer process, and retain protocol events as evidence linked to the dataset release.
Why it matters: Enables agents to discover and negotiate governed access to distributed data, while authorization, policy enforcement, semantic compatibility, and fitness checks remain mandatory.
04
What it fits with
Complements DCAT catalog metadata and ODRL usage policies; identity, trust, transfer implementations, and dataset semantics remain companion layers.
- FrameworkFAIR
Both support Cross-cutting work and meet around Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - Ontology / data modelPROV-O
Both support Cross-cutting work and meet around Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - Metadata profileBioschemas
Both support Cross-cutting work and meet around Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - Data model / schemaRO-Crate
Both support Cross-cutting work and meet around Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship
05
Implementation starter
Start with one bounded handoff. Pin, test, and review it before scaling.
Define one handoff, its accountable owner, and the decision DSP must support.
Pin the exact version and companion artifacts: 2025-1 · stable; Eclipse 1.0.0 release · 2025-07-23.
Map one representative input to the required standard artifacts.
Test the result against the canonical source and record every exception.
Preserve the source data, mappings, and review evidence before scaling.
06
Test the main limitation
DSP does not define scientific schemas, data quality, federation governance, identity assurance, or every transfer protocol; current implementation evidence is concentrated in the Eclipse dataspace ecosystem.
Run one representative end-to-end pilot and record exactly where DSP loses context, needs an extension, or depends on another standard.
Machine-readable output may still be unfit for analysis or ML.
Test the output for missing context, provenance, terminology alignment, time leakage, and the intended downstream decision. Enables agents to discover and negotiate governed access to distributed data, while authorization, policy enforcement, semantic compatibility, and fitness checks remain mandatory.
07
Official resources
Specifications, diagrams, examples, and guides from the organizations that maintain them.
Stable Dataspace Protocol 2025-1
Official publisher or steward guidance for this standard profile.
- Publisher
- Eclipse Dataspace Working Group