LogoLogo
How to Build Dataspaces?Main IDSA AssetsOther ResourcesManifesto for International Data Spaces
IDS-G
IDS-G
  • Changelog
  • Code of Conduct
  • Contributing to IDS-G-pre
  • LICENSE
  • International Data Spaces Global (IDS-G)
  • Overview
    • Message Structure/Format
    • Message Types
    • media
    • Communication Protocols
      • IDS REST
        • header
        • IDS Linked Data Notification (IDS-LDN)
          • IDS-REST requests
            • IDS-LDN, send a PUT request
      • IDS Communication Protocol Version 2 (IDSCP2)
        • IDSCP2 Application Layer
          • Examples
        • IDSCP2 Transport Layer
          • Examples
      • multipart
    • sequence-diagrams
      • Message Flows for Connector to Clearing House Communication
      • IDS Connector Communication
        • images
      • IDS Metadata Broker Communication
  • Components
    • IDS App Store (IDS-CH)
    • ClearingHouse
    • IDS Connector
    • IDS Identity Provider
      • Connector Identifiers (Connector IDs)
      • Certificate Authority (CA)
      • Dynamic Attribute Provisioning Service (DAPS)
        • requests
          • DAPS DAT request (root POST)
      • ParIS
        • ParIS requests
          • IDS-ParIS GET root request
    • IDS Meta Data Broker
      • General Overview
      • Introduction
      • Annex
        • HTTP API
        • Removed Requirements
      • Functions and Correlated Messages
        • Messages received by a Broker
        • Messages send by a Broker as Response
      • IDS Meta Data Broker Profiles
        • Advanced Information Profile
        • Usage Control Profile
      • IDS Meta Data Broker Requirements
        • Behavioral Requirements
        • Business Requirements
        • Conditional Requirements
        • Connector Requirements
        • Functional Requirements
        • Informational Requirements
        • Interface Requirements
        • Message Requirements
        • Role of an IDS Meta Data Broker
      • IDS-MDB requests
        • IDS-MDB GET root request
  • Glossary
    • IDS Shortcuts
  • Handbook to IDS-G
    • Specification
  • IDS Information Model
    • ids:Message
      • DescriptionRequestMessage POST
      • Message requests
  • Overview of the IDS Architecture
    • References
    • Relevant Documents
      • IDS Repositories
  • IDS Usage Control
    • IDS Usage Control Contract
      • Policies
      • images
    • IDS Policy Enforcement
      • System Adapter Technical Documentation
      • Concepts
        • Concepts for Data Sharing
    • Specification
      • Concepts
        • Access Control for the Contract Metadata
        • T7_ODRL_policies
        • Interfaces Standardization for Context Information (PIPs) and Actions to be Performed (PXPs)
        • Concepts for Participant-restricted policies and reselling data
  • .github
    • ISSUE_TEMPLATE
      • content-change-request
      • epic
      • feature-request
      • topic--code
      • topic--documentation
      • topic--quickfix
      • topic--structure
Powered by GitBook

Links:

  • IDSA Website
  • IDSA Github
  • Legal Notice
  • Privacy Policy

© 2016 – 2025 | All Rights Reserved | International Data Spaces Association

On this page
  • IDS Clearing House (IDS-CH)
  • Introduction
  • IDS Clearing House Architecture
  • Overview
  • Clearing House API
  • Data Protection and Integrity
Edit on GitHub
  1. Components

ClearingHouse

Last updated 1 year ago

IDS Clearing House (IDS-CH)

  • Shortcut: IDS-CH


Introduction

The IDS Clearing House acts as an intermediary in the IDS ecosystem. All IDS Connectors may log information in the Clearing House to support any process that requires an auditable logging mechanism. This includes e.g., the following processes in the IDS:

  • data sharing between a Data Provider (DP) and a Data Consumer (DC)

  • data usage according to Usage Contracts or Data Usage Policies

More information on the Clearing House is provided in

IDS Clearing House Architecture

Overview

The IDS Clearing House is an IDS Connector that runs the Clearing House Container as one of its services. As such, the connector part of the Clearing House is responsible for communication with other IDS Connectors. The architecture follows the IDS Connector architecture as presented in RAM 3.0 (see Section 3.5.1).

Clearing House API

Data Protection and Integrity

Details on further requirements for the Clearing House, in particular with regards to data protection and integrity, will be added in the future.

The IDS Clearing House provides an HTTP API for IDS Connectors to communicate with, i.e. to log and query information. The API is described in detail in .

Clearing House Communication
IDSA Clearing House Specification 1.0
IDS Clearing House Data App running on IDS Connector
Glossary "Clearing House"