FAQ

Why can't I just use EDC Connector?

Unfortunately the Eclipse Dataspace Components Connector is not compatible with MDS central components, i.e. Broker and Clearing House. Therefore, we developed extensions which allow an interaction between the EDC and the MDS Broker or the MDS Clearing House. Additionally, the MDS EDC Frontend provides several enhancements, necessary for MDS interaction (it is also part of docker-compose services).

What should the variable EDC_OAUTH_CLIENT_ID look like?

EDC_OAUTH_CLIENT_ID: 7X:7Y:...:B2:94:keyid:6A:2B:...:28:80

Which meta information attributes can be sent to the MDS Broker?

In the following, you find a map how values are mapped from frontend (right hand side) to backend (left hand side). Frontend variables are to be used along with the EDC API (e.g, Postman collection). EDC maps automatically the values to the IDS message format variable names (left hand side).

- id: "asset:prop:id"
- name: "asset:prop:name"
- contentType: "asset:prop:contenttype"
- description: "asset:prop:description"
- version: "asset:prop:version"
- keywords: "asset:prop:keywords"
- language: "asset:prop:language"
- publisher: "asset:prop:publisher"
- standardLicense: "asset:prop:standardLicense"
- endpointDocumentation: "asset:prop:endpointDocumentation"

MDS-specific attributes:
- dataCategory: 'http://w3id.org/mds#dataCategory'
- dataSubcategory: 'http://w3id.org/mds#dataSubcategory'
- dataModel: 'http://w3id.org/mds#dataModel'
- geoReferenceMethod: 'http://w3id.org/mds#geoReferenceMethod'
- transportMode: 'http://w3id.org/mds#transportMode'

For the example of how the API calls are to be made, see the postman collection, where examples of the attributes are also shown.

Postman collection

Use Postman and import the collection located at docs/postman_collection.json. Depending on your configuration changes, you need to adjust variables on collection MDV > Variables > Current Value. Please note, that api_key needs to be aligned with EDC_API_AUTH_KEY in the docker-compose.yaml

To test the Broker functionalities, simply execute the following steps

1. 1 Create Asset MDS
2. 2 Create Policy
3. 3 Create ContractDefinition: You will see a notification about registering resource at the Broker, which will then be reflected at the MDS Test Environment Broker.
4. Delete ContractDefinition: You will see a notification about unregistering the resource at the Broker.

Can I run a connector locally and consume data from an online connector?

No, it is not possible. Either both connectors should run locally or both connectors should be online to exchange data.

Can I consume data from my own connector?

No, you need two connectors in the same environment to test the provider-consumer chain. However you can use the permanently available MDS connector as provider in the test environment (just insert the address https://connector-mds-test-001.prod-sovity.azure.sovity.io/control/api/v1/ids/data in the field Catalog Browser/Connector Endpoint of your connector).

Do you have any further questions?

Please don't hesitate to contact us via the MDS Support System or via support@mobility-dataspace.eu