Using MyData Usage Control: Error while reading contract agreement file from dataLakeDirectory {}

[tharindupr]

I have been following the documentation on switching to MyData Usage Control.

I can observe that the contract agreement we set when creating the offered resources is not automatically picked by the MyData service. So, I manually added the contract policy to MyData. Still, contract negotiation seems not to be working correctly as the createContractAgreementMyData() function on the provider data app needs to be implemented.

I just wanted to know whether you are planning to extend the support for MyData usage control in the near future?

[IgorBalog-Eng]

Hello Tharindu,

MyData as UsageControl service is supported, and if you check DataApp repository line: https://github.com/Engineering-Research-and-Development/true-connector-basic_data_app/blob/master/src/main/java/it/eng/idsa/dataapp/handler/ContractRequestMessageHandler.java#L149

you will see that it reads contract_agreement.json file from file system. Issue with MyData support is that it is not compatible with information model and contract offer needs to be provided like this.

Is there specific reason why you are using MyData and not provided open source, free for use Platoon Usage Control app? You can try example contract_agreement.json file from link you sent. Last time we verified MyData was 3+ years ago. When we switched to Platton Usage Control app, all development and support for MyData was put on hold, and probably we will not sync with MyData latest changes.

[tharindupr]

Hello Igor,

Thanks for the reply. I see its incompatibility with the information model. I will proceed as you suggested.

The reason that we are considering MyData is hugely based on the IDSA Usage Control position paper . And when I explored more I could find rich documentation for the SDK if we want to use it within the Data App. And I think the source code is now open as well. I may be wrong because I'm currently evaluating these technical components.

[IgorBalog-Eng]

Please double check in license folder in source code link you shared, if it is free or not. Depending on the need for policy I agree that MyData has more policies implemented, but this comes with this info model incompatibility (this might be fixed in past 3 years, we did not check because of license for MyData - cannot be used commercially unless paid first.).

If you need to setup Dataspace, we provide "out of the box" solution, please check TRUEConnector MVDS. There you have instructions for connectors, identity provider, certificates, broker.

[tharindupr]

Thanks for your input. We will indeed consider them in our decision to use MyData.

TRUEConnector MVDS is great. This will surely accelerate our data space implementation.