Introduce `participantId` on `Catalog` level

International-Data-Spaces-Association / ids-specification

The Dataspace Protocol is a set of specifications designed to facilitate interoperable data sharing between entities governed by usage control and based on Web technologies. These specifications define the schemas and protocols required for entities to publish data, negotiate Agreements, and access data in a data space

https://docs.internationaldataspaces.org/dataspace-protocol/

Apache License 2.0

26 stars 14 forks source link

Introduce `participantId` on `Catalog` level #196

Closed matgnt closed 4 months ago

matgnt commented 5 months ago

For #195 we need a participantId on the Catalog level. This gives context to dataset->has_policy and will be used e.g. in ContractRequestMessage->dspace:offer->assigner

-- Matthias Binzer

matgnt commented 5 months ago

TODO: check if and what is the difference compared to dct:publisher: https://github.com/International-Data-Spaces-Association/ids-specification/blob/e87eb2a352ec89e6b8c1e26809d8b60c33d002c6/catalog/message/example/catalog.json#L12

matgnt commented 5 months ago

EDC seems to have this:

Only problem: this is not standardized in DSP.

sebbader-sap commented 5 months ago

to be started after https://github.com/International-Data-Spaces-Association/ids-specification/pull/184

ssteinbuss commented 5 months ago

We should explain the relationship to the ODRL attributes 'assigner' and 'assignee'
This might not be just a string, but an IRI
Check also the relationship to 'dct:publisher' (see above)