search

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
30 stars 14 forks source link

Why `ContractNegotiation` states report `PROVIDER` and `CONSUMER` while `TransferProcess` ones not? #63

Closed ndr-brt closed 1 year ago

ndr-brt commented 1 year ago

Looking at the specifications, for transfer process states are: https://github.com/International-Data-Spaces-Association/ids-specification/blob/3f9fc7c776bc9273f4df32b49c90c910df23b1fb/transfer/transfer.process.protocol.md?plain=1#L57-L63

While for contract negotiation are: https://github.com/International-Data-Spaces-Association/ids-specification/blob/3f9fc7c776bc9273f4df32b49c90c910df23b1fb/negotiation/contract.negotiation.protocol.md?plain=1#L21-L31

Is there a reason why on contract negotiation the states strictly related to consumer activities are marked with the CONSUMER_ prefix and the provider ones with PROVIDER_ while in the transfer process this convention is not used? In fact TransferProcess REQUESTED is representing a consumer activity, while STARTED is representing a provider action.

I would propose to remove these prefix from the Contract Negotiation states where the part that triggered it, e.g.:

while the CONSUMER_AGREED and PROVIDER_AGREED are the only states that effectively need the prefix.