EDC Connector API
Concepts

Core Concepts

Understanding the fundamental concepts of the Eclipse Dataspace Connector

Core Concepts

The Eclipse Dataspace Connector (EDC) is built around several core concepts that enable secure, sovereign data exchange between organizations. Understanding these concepts is essential for effectively using the Management API.

Data Space Principles

A Data Space is a virtual environment where organizations can share data while maintaining control over their data assets. Key principles include:

  • Data Sovereignty: Data owners retain control over who can access their data and under what conditions
  • Decentralization: No central authority controls the data; it flows directly between participants
  • Interoperability: Standard protocols enable different systems to communicate
  • Trust: Participants can verify each other's identity and policies

EDC Architecture Overview

┌─────────────────────────────────────────────────────────────────┐
│                        EDC Connector                             │
├─────────────────────────────────────────────────────────────────┤
│  ┌─────────────┐  ┌─────────────┐  ┌─────────────────────────┐  │
│  │   Assets    │  │  Policies   │  │  Contract Definitions   │  │
│  └─────────────┘  └─────────────┘  └─────────────────────────┘  │
│                           │                                      │
│                           ▼                                      │
│  ┌─────────────────────────────────────────────────────────────┐│
│  │                    Federated Catalog                        ││
│  └─────────────────────────────────────────────────────────────┘│
│                           │                                      │
│                           ▼                                      │
│  ┌─────────────────────────────────────────────────────────────┐│
│  │               Contract Negotiation                          ││
│  └─────────────────────────────────────────────────────────────┘│
│                           │                                      │
│                           ▼                                      │
│  ┌─────────────────────────────────────────────────────────────┐│
│  │                  Transfer Process                           ││
│  └─────────────────────────────────────────────────────────────┘│
└─────────────────────────────────────────────────────────────────┘

Key Components

ComponentDescription
AssetA digital resource with metadata and a data address
PolicyRules governing access and usage of data
Contract DefinitionLinks assets to access and contract policies
Contract NegotiationProcess of agreeing on terms between provider and consumer
Contract AgreementThe finalized, binding agreement
Transfer ProcessThe actual data exchange workflow
CatalogFederated listing of available data offers

Data Exchange Flow

  1. Provider creates an Asset and defines Policies
  2. Provider creates a Contract Definition linking the Asset to Policies
  3. Consumer discovers the offer through the Catalog
  4. Consumer initiates Contract Negotiation
  5. Both parties reach a Contract Agreement
  6. Consumer initiates a Transfer Process
  7. Data flows from Provider to Consumer according to the agreement

Learn More

On this page