LogoLogo
How to Build Dataspaces?Main IDSA AssetsOther ResourcesManifesto for International Data Spaces
OPEN DEI Building Blocks Catalog
OPEN DEI Building Blocks Catalog
  • Building-Blocks-Catalog
  • Access and usage control
  • Business building blocks
  • Continuity model
  • Data Exchange APIs
  • Data Models and Formats
  • Data Usage Accounting
  • Identity Management (IM)
  • Metadata and Discovery Protocol
  • Organisational/operational building blocks
  • Provenance and traceability
  • Publication and Marketplace Services
  • Trusted Exchange
  • other_building_blocks
    • Data Analytics Engine (DAE)
    • Data Processing
    • Data Routing and Preprocessing (DR&P)
    • Data-, Service-, Privacy- and Monitoring.
    • Data Visualization
    • Marketplace Data Lifecycle Process
    • System Adaptation
    • Workflow Management Engine (WME)
  • Contributing to Building Blocks Catalog
Powered by GitBook

Links:

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

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

On this page
  • Definition
  • Role and Scope
  • Features
  • Components and Technologies
  • Technical Reference Implementation
  • Business Use Cases Implementation
  • Best practices identification and recommendations
  • Gap or what is missing?
  • TRL
  • Comments
  • Additional Information
Edit on GitHub

Business building blocks

Definition

Business building blocks are artifacts that regulate the business relationships between the different roles in a data-driven business ecosystem: Data Owner, Data Acquirer or Data provider, Data Processor, Data Marktplace Operator.

Role and Scope

Features

Design Principles Position Paper
  • Operational Service Level Agreement (SLA)

  • Accounting Scheme

  • Billing/Charging Scheme

  • Data valuation method

  • Smart Contracts

Components and Technologies

i3-Market Project
  • Notification Manager

  • Smart Contract Generator

Datavillage
  • Consent receipt management, which is a consent template based on Gconsent ontology that can be used by the organsation to define the purpose and the data that will be used for data processing.

  • The consent receipt is then used within a data consent wizard to request consent to the end user.

Technical Reference Implementation

Business Use Cases Implementation

Datavillage
  • TAILORED CONTENT DISCOVERY FOR END-USERS

Enable the analysis and processing of sensitive personal data aiming better content recommendation through data sourced directly by your users in a compliant and secure way. Let users consume online content on multiple platforms with their own reputation, identity and history.

Best practices identification and recommendations

Datavillage
  • Using standard ontology as Gconsent is perfect and covers a lot of use cases.

Gap or what is missing?

TRL

Comments

Additional Information

Last updated 1 year ago