You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* fix: change protocol version from 1.0 to 0.8
* chore: set protocol name and version in README
* fix(README): resolve typos
* fix: change data connector to connector
IDS is a set of specifications designed to facilitate interoperable data sharing between entities governed by usage control and based on Web technologies. These specifications
11
+
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
12
12
define the schemas and protocols required for entities to publish data, negotiate usage agreements, and access data as part of a federation of technical systems termed a
13
13
__*dataspace*__.
14
14
15
15
## Introduction
16
16
17
17
Sharing data between autonomous entities requires the provision of metadata to facilitate the transfer of assets by making use of a data transfer (or application layer) protocol.
18
-
IDS defines how this metadata is provisioned:
18
+
The __Dataspace Protocol__ defines how this metadata is provisioned:
19
19
20
20
1. How data assets are deployed as [DCAT Catalogs](https://www.w3.org/TR/vocab-dcat-3/) and usage control is expressed as [ODRL Policies](https://www.w3.org/TR/odrl-model/).
21
21
2. How contract agreements that govern data usage are syntactically expressed and electronically negotiated.
22
22
3. How data assets are accessed using data transfer protocols.
23
23
24
24
These specifications build on protocols located in the [ISO OSI model (ISO/IEC 7498-1:1994)](https://www.iso.org/standard/20269.html) layers, like HTTPS.
25
-
The purpose of this specification is to define interactions between systems independend of such protocols, but describing how to implement it in an unambigious and extensible way.
25
+
The purpose of this specification is to define interactions between systems independent of such protocols, but describing how to implement it in an unambiguous and extensible way.
26
26
To do so, the messages that are exchanged during the process are described in this specification and the states and their transitions are specified as state machines, based on the key terms and concepts of a data space.
27
27
On this foundation the binding to data transfer protocols, like HTTPS, is described.
28
28
29
29
The specifications are organized into the following documents:
30
30
31
-
*A __*Dataspace Information Model*__document that defines key terms.
31
+
*__*Dataspace Model*__and __*Dataspace Terminology*__ documents that define key terms.
32
32
*__*Catalog Protocol*__ and __*Catalog HTTPS Binding*__ documents that define how DCAT Catalogs are published and accessed as HTTPS endpoints respectively.
33
33
*__*Contract Negotiation Protocol*__ and __*Contract Negotiation HTTPS Binding*__ documents that define how contract negotiations are conducted and requested via HTTPS endpoints.
34
34
*__*Transfer Process Protocol*__ and __*Transfer Process HTTPS Binding*__ documents that define how transfer processes using a given data transfer protocol are governed via HTTPS
@@ -40,20 +40,20 @@ As an implication, the data transfer can be conducted in a separated process if
40
40
41
41
### Context of this specification
42
42
43
-
The __*Name of the protocol goes here*__is used in the context of data spaces as described and defined in the subequent sections with the purpose to support interoperability.
44
-
In this context, the specification provides fundamental technical interoperability for particiants in data spaces and therefore the protocol specified here is required to join any data space as specified [here]().
43
+
The __Dataspace Protocol__is used in the context of data spaces as described and defined in the subsequent sections with the purpose to support interoperability.
44
+
In this context, the specification provides fundamental technical interoperability for participants in data spaces and therefore the protocol specified here is required to join any data space as specified [here]().
45
45
Beyond the technical interoperability measures described in this specification, semantic interoperability should also be addressed by the participants. On the perspective of the data space, interoperability needs to be addressed also on the level of trust, on organizational level and on legal level.
46
46
The aspect of cross data space communication is not subject of this document, as this is addressed by the data spaces' organizational and legal agreements.
47
47
48
-
The interaction of participants in a data space is conducted by the participant agents, socalled Data Connectors, which implement the protocols described above.
49
-
While most interactions take place between data connectors, some interactions with other systems are required.
48
+
The interaction of participants in a data space is conducted by the participant agents, so-called Connectors, which implement the protocols described above.
49
+
While most interactions take place between Connectors, some interactions with other systems are required.
50
50
The figure below provides an overview on the context of this specification.
51
51
52
52
An Identity Provider realizes the required interfaces and provides required information to implement Trust Framework of a data space.
53
-
The validation of the identity of a given participant agent and the validation of addtional claims is the fundamental mechanism. The strucutre and content of such claims and identity may vary between different data spaces, as well as the structure of such an Identity Provider, e.g. a centralized system, a decentralized system or a federated system.
53
+
The validation of the identity of a given participant agent and the validation of additional claims is the fundamental mechanism. The structure and content of such claims and identity may vary between different data spaces, as well as the structure of such an Identity Provider, e.g. a centralized system, a decentralized system or a federated system.
54
54
55
-
A connector will implement addtional internal functionalities, like monitoring or Policy Engines, as appropriate. It is not covered by this specification, if a connector implements such or how.
55
+
A connector will implement additional internal functionalities, like monitoring or Policy Engines, as appropriate. It is not covered by this specification, if a connector implements such or how.
56
56
57
-
The same applies for the data, which is transfered between the systems. While this document does not define the transpprt protocol, the structure, syntax and semantics of the data, a specification for those aspects is required and subject to the agreements of the participants or the data space.
57
+
The same applies for the data, which is transferred between the systems. While this document does not define the transport protocol, the structure, syntax and semantics of the data, a specification for those aspects is required and subject to the agreements of the participants or the data space.
58
58
59
59
0 commit comments