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

Cross data space communication "in scope"? #23

Closed matgnt closed 1 year ago

matgnt commented 1 year ago

I also learned that the cross data space communication is out of scope (at least for the major implementation EDC) and therefore it seems to me important to explicitly point this out in the Introduction, whether cross data spcace communiction is in scope or out of scope for the IDS protocol specification. https://github.com/International-Data-Spaces-Association/ids-specification/blob/main/README.md

jimmarino commented 1 year ago

It depends on what you mean by "cross-data space communication."

For EDC and the new IDS Information Model, connectors always participate in a dataspace. Data sharing outside a dataspace is not defined. Therefore, two connectors always exchange data in the context of a dataspace. In this conceptual model, there is no such thing as "cross-dataspace" communication. Either the two connectors participate in a pre-existing, common dataspace, or a new one is created. Connectors can participate in multiple dataspaces.

ssteinbuss commented 1 year ago

Most of this should go to the primer that explains more about the structure of a data space and how to federate and if to federate. Here the communication in a given data space, what could be multiple is in scope.

PeterKoen-MSFT commented 1 year ago

Cross dataspace Communication happens at the Organizational and the Legal level. At the level of the protocol the communication is always within one trust context (which usually is one dataspace, but can be established cross-dataspace in special situations).

If two dataspaces use the same version of the protocol they are technically interoperable. If two dataspaces use the same semantic model for their trust framework they are interoperable on trust. If two dataspaces have business processes that are interoperable then they are interoperable on an organizational level. If two dataspaces agree to each others legal contracts as being equivalent then they are legally interoperable.

Only if all 4 layers are satisfied data can be shared between two participants that reside in the contexts of those two dataspaces.

However, technically it is still a data contract/sharing between two participants and not between the dataspaces. And that scenario is perfectly covered by the protocol.