Place up to three profiles side by side. Compare their architectural role, lifecycle reach, and first limitation to test. No single standard covers every layer.
Working set
Choose profiles
1 of 3 selected
01
DSPStandard
Decision lens
Compare roles before choosing an implementation.
The useful question is not “Which standard wins?” It is “Which job must this part of the architecture perform, and what remains uncovered?”
01
Start with the job
Decide whether you need guidance, a domain payload, exchange, semantics, governance, or a reusable release.
02
Map lifecycle reach
Use the matrix to see where each profile has a direct role. A filled cell is coverage, not a quality score.
03
Test the boundary
Read what each option leaves unresolved before judging maturity or implementation fit.
Assessment
Review lifecycle coverage and practical fit.
Read left to right. Lifecycle reach comes first; a maturity label never overrides a scope mismatch.
01 · Lifecycle reach
Where each profile contributes directly
Coverage shows a recorded role at that readiness stage. It does not imply end-to-end implementation.
No direct role is recorded for Plan, Acquire, Harmonize.
Known 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.
03 · Detailed assessment
Check the fit and source behind the map
Use the official source, version, and limitation together. A higher maturity label does not erase a scope mismatch.
Web-based schemas and protocols for entities to publish data, negotiate usage-controlled agreements, and access data within a federation of technical systems called a dataspace.
Best fitGoverned exchange across organizational and cloud boundaries where discovery, contract negotiation, and transfer must interoperate without centralizing all data.
Readiness stages
ExchangeLearn + reuse
AI-ready contribution
Enables agents to discover and negotiate governed access to distributed data, while authorization, policy enforcement, semantic compatibility, and fitness checks remain mandatory.
First limitation to test
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.
Maturity
Scaling
Stable first Eclipse release with a conformance test kit; broader cross-implementation evidence is still scaling