Architecture overview - Mobility-Data-Space/mobility-data-space GitHub Wiki

A Connector is a software component used for data exchange in data spaces. As a dedicated point of data exchange and the enforcement of usage policies, the Connector is the central component of the data space concept. It enables a participant to access the data space.

The Connector-as-a-Service (CaaS) is a data space Connector that is provided as a service in the MDS design.
The CaaS is intended to simplify access to the data space for participants. If this offer is made use of, the participant does not have to install a Connector in their own environment.
The CaaS is based on the current operating version of the MDS Connector and has all its basic functionalities. The CaaS is currently provided in a free version to all MDS members one each in the test and productive environment. The CaaS can be easily requested via the user interface in the MDS portal.

The Federated Catalog is a crawling mechanism. It crawls all connectors registered in the MDS to retrieve the metadata of data offers hosted on them. This information is then displayed in the Data Catalogue within the Portal. The Federated Catalog is based on EDC components for its core functionality, while adding specific features using the EDC extensibility mechanism.
The Federated Catalog can only retrieve metadata for data offers that have been published for everyone ("publish unrestricted"). Data offers published only to specific connectors ("publish restricted" to "consumer's participant ID") cannot be retrieved by the Federated Catalog; therefore, they will not appear in the Data Catalogue in the Portal.

The Logging House (LH) acts as an intermediary in the data space ecosystem. Connectors can communicate with the logging house via an existing EDC extension. There is a legal obligation for Connectors used in the MDS to use this Logging House extension. The LH logs contract agreements and transactions. This means that the transaction partner, time and description of the asset (metadata) can be traced at the time the contract is signed. Both transaction partners and the MDS as Data Space Authority have access to the log files.

The DAPS is the attribute server that issues OAuth2 access tokens that you need to access the services and data of other Connectors. The protocol enables Connectors to authenticate themselves at the DAPS with their X509 certificate and in return receive an access token with which they can access other Connectors. The requested Connector itself always makes the decision about permitted access, not the DAPS. The DAPS only manages the attributes of the registered Connectors.

The MDS Portal provides essential functionalities for MDS members to manage their ecosystem activities:

• Organization & User Management: Organisation registration, user management, role and right management.
• Connector Management: Register connectors, order Connector-as-a-Service (CaaS), or remove existing connectors.
• Data Catalogue: Browse data offers within MDS.
• Networking: Access the MDS member directory and contact other members.