Engineering-Research-and-Development / true-connector

TRUE (TRUsted Engineering) Connector for the IDS (International Data Space) ecosystem
GNU Affero General Public License v3.0
24 stars 13 forks source link

Adding domain specific meta data to resource description #39

Open tharindupr opened 3 months ago

tharindupr commented 3 months ago

Hi,

Is there any documentation on extending the Information Model to add domain-specific metadata on an asset? And can you please let me know the best practices for doing that?

Thanks.

IgorBalog-Eng commented 3 months ago

Hello, as we are aware of, you cannot change Information Model and add domain-specific metadata. If you do so, you will not be compliant with other connectors. With metadata fields provided by IM (info model) you will have to use only provided. Here I'm referring to those messages that are transferred in header part of multipart/form message and self description json. They are created using IM library and you cannot change it (unless you use something yourself, but then this is not compliant with other implementations, and it will require to change also TRUE Connector)

What you might do is to use payload part of multipart/form request, and pass additional data with payload, modify dataApp on provider side, to read payload and apply additional logic.

tharindupr commented 3 months ago

Thanks for the reply. That perfectly makes sense in terms of interoperability with other connectors. How about scenario where a data consumer needs to query for a data asset based on domain- specific meta data on a broker? I suppose the current version of True Connector will only push connector self descriptions to a broker?

IgorBalog-Eng commented 3 months ago

You have QuerryMessage, that will be sent to the Broker (there is example in TC repo, and example request with simple query to get all registered connector ID's.) It is out of the scope for TRUE Connector project to implement Broker query logic. Payload of multipart/form request will contain necessary data needed by the Metadata Broker, to perform that search. This will be defined by the Broker itself, if Broker supports such filtering of the data.