Data Transaction concept from DSSC Blueprint V0.5

[ssteinbuss]

In the IDSA Rulebook we do not mention the concept of a data transaction. This is an element of the DSSC Conceptual Model of the Blueprint 0.5 Section 3.1 p 140.

IDSA Rulebook has a section on Data Sharing, should we extend this section with Data Transactions? Would this imply the need to also define Data Products in the IDS Rulebook, like in the conceptual model?

[ssteinbuss]

We park this to be discussed with the DSSC as clarification is needed with the DSSC conceptual model.

The Dataspace Protocol has a certain understanding of transactions, but we are not sure if the definition of data transaction is the same between Dataspace Protocol and the DSSC definition

[ssteinbuss]

This should also include a discussion on the definition of "consent" and if it is included in the transaction as a mandatory or optional aspect.

[PeterKoen-MSFT]

I would argue against the creation of the Data Transaction and Data Product concept in the IDSA Rulebook. Those are very specific business processes and are not normative at the level of IDS. There can be many dataspaces that do not use this concept, it is rather limited in scope to a specific type of business models built on top of dataspaces and thus I would argue for not using those terms.
It can be included as an optional way to implement Data Marketplaces as an optional service but both concepts do not exist at the basic dataspace technology layer.

[PeterKoen-MSFT]

This should also include a discussion on the definition of "consent" and if it is included in the transaction as a mandatory or optional aspect.

"Consent" is an attribute of a data contract related to the data being shared and is not an inherent concept of dataspaces. Most dataspace use cases will not require consent (e.g. industrial data) and thus it should not be included as a foundational concept. Especially as it is perfectly accounted for through optional contract metadata.