Eclipse Dataspace

The Eclipse Dataspace Working Group will encourage, develop, and promote open-source solutions that will enable the development, as well as the participation in dataspaces for organizations of all types and sizes. It does not favor a specific industry or type of organization and is fully dedicated to enable global adoption of dataspace technologies to foster the creation and operation of trusted data sharing ecosystems. The working group will have a strong focus on participating in standards development, implementation and onboarding of existing open-source projects and providing guidance to associated projects on alignment of supporting a broad ecosystem of interoperable dataspaces.

Eclipse Dataspace Components

Eclipse Dataspace Components (EDC) A dataspace is both a multi-organizational agreement and a supporting technical infrastructure that enables data sharing between two or more participants

Eclipse Dataspace Decentralized Claims Protocol

Technical DetailsDCP defines the following protocol flows.1. Base Identity Protocol (BIP)The *Base Identity Protocol* defines how to obtain and communicate participant identities and claims using self

Eclipse Dataspace Protocol

The Eclipse Dataspace Protocol is used in the context of data spaces as described and defined in the subsequent sections with the purpose to support interoperability. In this context, the

Eclipse Conformity Assessment Policy and Credential Profile

The Eclipse Conformity Assessment Policy and Credential Profile defines a specification for expressing and verifying policies through verifiable credentials and conformity assessment vocabularies (ISO

Eclipse Dataspace TCK

The Eclipse Dataspace TCK will consist of a modular test harness that can be extended to verify multiple Dataspace protocols and standards. The core framework is written in Java but can verify

Eclipse Data Rights Policies Profile (DRP)

Trust forms the basis for any data exchange transactions to occur. However, the control and transfer as well as claims protocols are trust agnostic and they are expected to connect to (one or multiple