A minimum viable data space (MVDS) is a combination of components to initiate a data space with just enough features to be usable for secure and sovereign data exchange, as specified by IDSA. It aims to facilitate the work of experimenters by shortening the implementation time (by avoiding lengthy details that would slow down the first release). This allows them to start with a first working version (where secure and sovereign data exchange is granted), where the development team can iterate, identify and respond to the assumptions about the requirements of the data space.
The MVDS is the unique solution provided by IDSA Head Office, as current best practice.
The IDS Deployment Scenarios act as best practices and sources of inspiration on building data spaces. There, you will find various examples of implementation, along with experiments also run with MVDS.
To find more information on implementing data spaces and a step-by-step classification of existing IDS documentation, you may check How to Build Data Spaces?.
A minimum viable data space consists of:
- Two or more IDS connectors
- The Certificate Authority (CA) granting X.509 certificates (not to be confused with certification)
- The Dynamic Attributes Provisioning Service (DAPS) to handle dynamic attributes and manage dynamic access tokens
- MetadataBroker which is a registry for IDS Connector self-description documents.
Certification of all components and the operational environments is an additional trust layer, since it ensures the functionality of components work in clearly specified boundaries.
To start with implementing a MVDS, you can check the list of IDS-compliant components that are listed on this page, which is part of the How to Build Data Spaces? section, that explains the process of building data spaces in five steps.