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
Edit on GitHub
  1. Components
  2. IDS Meta Data Broker

General Overview

Last updated 1 year ago

The International Data Spaces Reference Architecture Model (version 3.0) describes several components:

  • International Data Spaces Connector

  • International Data Spaces App Store

  • International Data Spaces Meta Data Broker

  • International Data Spaces Clearing House

  • International Data Spaces Identity Provider

The IDS Meta Data Broker is a service for publishing and searching metadata of Connectors and resources between International Data Spaces Participants. In order to ensure the necessary interoperability and general interactions, an IDS Meta Data Broker (like the App Store) is also defined as a specialized IDS Connector. The communication between an IDS Connector and an IDS Meta Data Broker is based on the same principles as any other Connector-Connector communication within the International Data Spaces. Still, an IDS Meta Data Broker provides a collection of additional functionalities:

  • Indexing services in order to effectively and efficiently respond to queries and present known Connectors and other resources

  • Interfaces for Users or IDS-Messages to ensure access to the stored information.

This document serves as a specification defining what an IDS Meta Data Broker is, which functionalities it must support and which services other IDS components can expect. The described content is aligned with the explanations of the IDS-RAM 3.0 and complements the.

A software component is allowed to describe it self as an IDS Connector only after an IDS compliant Certification Body verified that the necessary capabilities are in place and operate in IDS conformant manners. The list of certification criteria () contains the respective requirements. The same procedure is valid for an IDS Meta Data Broker, with additional requirements for broker-functionalities as documented in this list. After a successful certification of the relevant Criteria of an IDS Connector and as an IDS Meta Data Broker, a software component can include the following RDF statement into its Self-Description:

<Connector/Broker URI> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://w3id.org/idsa/core/Broker> .

However, no other entity is obliged to believe this claim without further proof. The IDS way for a trustworthy information provision is the Dynamic Attribute Token (), provided by IDS Dynamic Attributes Provisioning Service (). A certified IDS Meta Data Broker can ask for a DAT at its responsible DAPS. The necessary interactions are specified in and The . Only if a correctly signed DAT from a trustworthy DAPS includes the above claim, other IDS entities should accept the claim of a potential IDS Meta Data Broker.

In accordance to the thereby directly included guaranteed features, an IDS Meta Data Broker may provide significantly more services. Several options to include broker features in an International Data Space are possible:

  • only mandatory IDS Meta Data Broker features

  • mandatory and profile features:

    • any set of additional features from the “UsageControl Enabled” and “Advanced Information” profiles

    • all additional features from the “Usage Control Enabled” or/and “Advanced Information” profiles.

  • general features supporting publication, indexing and discovery which are not mentioned in this specification (not applicable as an IDS Meta Data Broker), or

  • any combination of the categories above.

“The IDS Communication Guide”
Certification Criteria -Components v2.1.2
DAT
DAPS
The IDS Communication Guide
IDS Handshake