Skip to content

Architecture Principles

This chapter provides architectural insights on the main technical concepts of data spaces described in the IDSA Knowledgebase and in the IDSA Rulebook and explains how to realize them using technical specifications such as the Dataspace Protocol (DSP) and the Decentralized Claims Protocol (DCP).

Introduction - Starting with the main concepts

The IDSA Rulebook and the ISO/IEC 20151-1 Standard "Information technology — Cloud computing and distributed platforms — Dataspace concepts and characteristics" define Data Spaces as:

Environment enabling trusted data sharing between participating parties, based on an agreed governance framework, along with an agreed set of policies, semantic models, standardized protocols, processes, and facilitating services.

Based on this, data spaces have the following main concepts and characteristics, as explained in further detail in the IDSA Rulebook and ISO/IEC 20151-1:

Figure 1: Data space concepts from the IDSA Rulebook and ISO/IEC 20151.

The following diagram maps the relationships between these concepts, not intending to follow a process/runtime flow order, but focusing on highlighting relationships and dependencies between them.

Figure 2: Visual Map for Data Space Concepts from IDSA Rulebook and ISO/IEC 20151-1

Please note that some essential characteristics such as maintaining control and interoperability are not depicted in this picture, as these are cross-cutting concepts which require actions in almost each block. They have been omitted from the diagram for the sake of readability.

Multi-level policies (e.g., membership policies at data space level, access policies for controlled discovery of metadata, data sharing contract policies, data use policies) needed in a data space are depicted vertically in this picture to express how they are applied in an overarching way across different levels.

IDS-RAM Architectural Capabilities - Turning data space concepts into technical guidance

While the IDSA Rulebook defines the essential data space concepts, the IDS-RAM operationalizes these high-level principles into technical guidance in the form of logical components and behavioural patterns.

The architectural capabilities defined in IDS-RAM represent the functional building blocks necessary for interoperable and trusted data sharing. These are based on the current technical approaches at hand and are centered around the following key technical specifications and standardization work items to ensure interoperability:

However, the architectural capabilities can be implemented in other approaches. Future versions of the IDS-RAM may include such approaches.

The visual map of data space concepts provided earlier then evolves into the following view of architectural capabilities:

Figure 3: IDS-RAM Architectural Capabilities

A. Data Space Governance Authority

Sets the overall framework for data sharing between participants by establishing a trust framework, roles, processes, and rules.

Note

The DSGA is not a technical artefact for the IDS-RAM, but a functional role described in the IDSA Rulebook. IDS-RAM focuses mostly on the participant side; however, the governance framework is included for the sake of completeness.

See also

IDSA Rulebook pages on DSGA and IDS-RAM Architectural patterns for DSGA.

B. Credentials & Claims

Establish trust-relevant identity and attributes used throughout subsequent capabilities on the participant side. This capability is closely linked with the DCP specification.

See also

IDSA Rulebook pages on Trust, Dataspace Trust Frameworks, Attributes and claims, Identity, Decentralized onboarding and working draft paper on Identifiers in Data Spaces.

C. Cataloging

Supports the discovery of data and services through metadata publication and controlled visibility.

Cataloging capability is based on the DSP Catalog Protocol specification, which makes use of DCAT and application profiles.

See also

IDSA Rulebook page Data Discovery Services and IDS-RAM Architectural patterns for Catalogs.

D. Contract Negotiation

Formalizes rights and obligations into enforceable data sharing agreements.

This capability is realized by the DSP Contract Negotiation Protocol.

See also

IDSA Rulebook page Data Sharing.

E. Control Plane & Policy Enforcement

Orchestrates and authorizes the execution of agreements and coordinates with data plane mechanisms using interoperable protocol bindings.

The control plane part of the DSP Transfer Process Protocol and Data Plane Signaling specifications enable this capability.

See also

IDSA Rulebook pages Data Sharing, Planes and Policies.

F. Data Plane

Executes data transfer/access under the constraints of the data sharing agreement and orchestration decisions.

This corresponds to the data plane referred to in the DSP Transfer Process Protocol specification.

Note

Since actual data sharing happens outside of the data space, in a peer-to-peer manner between participants, this block is out of scope for IDS-RAM but remains part of the end-to-end story of data sharing.

See also

IDSA Rulebook pages Data Sharing and Planes.

G. Observability

Provides evidence and accountability for actions taken during Contract negotiation, Orchestration (control plane), Data access and use (data plane). Observing actions supports trust frameworks and compliance needs without requiring centralization of data content. Observability may also provide inputs to optional services such as auditing.

For simplicity, the diagram only depicts the relationship with the Control Plane capability.

See also

IDSA Rulebook page Observability and IDSA position paper Observability in Data Spaces.

H. Optional Services

Represents ecosystem extensions (e.g., marketplaces, processing services, auditing services, escrow/confidential compute), which may be provided by participants subject to the data space governance framework. In the diagram, optional services “execute and enforce” the data plane and “provide inputs” into governance and framework elements.

Optional services are out of scope for IDS-RAM, while still relevant for the overall landscape of data spaces.

See also

Focus paper Value adding services

Mapping to technical specifications

A mapping of the RAM capabilities to technical specifications may be found in the article on the mapping to technical specifications.