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
  3. Annex

Removed Requirements

The following listed requirements have been introduced by version 1.0 of this document but needed to be removed in the further specification process. They are kept here for legacy reasons but have no normative meaning anymore.

No.
Description

B2

A broker can offer different services:

- Index service

- Clearing

- Marketplace

B9

If multiple broker index services exist

a) index services are isolated and ignore others

b) index services from a network and propagate data to others

c) combinations from a) and b) are allowed

B19

A Connector may only add or change his own metadata in the index service. The index service has to validate from the id token of the DataHeader, if the sender is authorized to request a specific action.

Attention: An Identity provider may use different keys than the International Data Spaces.

The index service therefore has to map IdP keys to IDS keys.

B22

A BrokerQueryRequest contains exactly one scope:

a) All (query all active or passive datasets)

b) Active (query only active datasets)

c) Access (query only active datasets, which are available for the questioner)

B32

An index service may also store metadata of data-apps.

B33

The BaseBroker is based on the BaseConnector and Ubuntu with Docker.

B34

The BaseBroker consists of this containers:

a) ExecutionCoreContainerwith ActiveMQ and Camel (App Store Image)

b) Broker-API(BaseBroker Image)

c) ApacheDS(DockerHub Image)

d) Keycloak (DockerHubImage)

B35

ApacheDS loads default and additional IDS index service schema for RDF file storage.

B36

Running Keycloak in the Connector is optional. A broker may use any Identity Provider.

B37

Keycloak and index service do not use a shared LDAP.

Keycloak just syncs with LDAP sources and uses an internal RDBMS for storage.

B39

Broker-API is a Spring Boot REST service, which parses incoming BrokerMessages and executed corresponding LDAP actions. The connection to LDAP is done with Spring LDAP (based on JNDI).

B41

A camel workflow connects the incoming queue BrokerRequest with Broker-API.

B42

The BaseBroker uses JMS Request/Response pattern for BrokerResponseMessage with a temporary queue.

Last updated 1 year ago