Comment on page
The following sections outline the Dataspace Information Model, which form the foundation of this specification.
The relationships between the primary dataspace entities are defined as follows:
Note that all relationships are multiplicities unless specified.
Dataspace Authoritymanages one or more
Dataspaces. This will include participant registration and may entail mandating business and/or requirements. For example, a Dataspace Authority may require participants to obtain some form of business certification. A Dataspace authority may also impose technical requirements such as support for the technical enforcement of specific usage policies.
Participantis a member of one or more
Dataspaces. A participant registers
Participant Agentsthat perform tasks on its behalf.
Participant Agentperforms tasks such as publishing a catalog or engaging in an asset transfer. In order to accomplish these tasks, a participant agent may use a verifiable presentation generated from a credential obtained from a third-party issuer. A participant agent may also use an ID token issued by a third-party identity provider. Note that a participant agent is a logical construct and does not necessarily correspond to a single runtime process.
Identity Provideris a trust anchor that generates
ID tokensused to verify the identity of a
Participant Agent. Multiple identity providers may operate in a dataspace. The types and semantics of ID tokens are not part of this specification. An identity provider may be a third-party or a participant itself (for example, in the case of decentralized identifiers).
Credential Issuerissues verifiable credentials used by participant agents to allow access to assets and verify usage control.
The diagram below depicts the relationships between
Participant Agentthat performs
Asset Transferoperations with another connector. An outcome of a
ContractNegotiationmay be the production of an
Agreement, which is an ODRL Agreement defining the usage control policy agreed to for an asset.
Not all dataspace entities have a concrete technical materialization; some entities may exist as purely logical constructs. For example, a
Participant Agenthave no representation in the protocol message flows that constitute dataspace interactions. This section outlines the classes that comprise the concrete elements of the model, i.e. those that are represented in protocol message flows.
Note 1: The classes and definitions used in the dataspace protocol are reused from different standards and specifications as much as possible, in particular, DCAT and ODRL. As, however, the external definitions allow different interpretations or provide more attributes than required, the dataspace protocol is leveraging profiles of the original definitions rather than the complete original expressiveness. A profile in this sense is a restriction or subset of an external definition, enforcing that every occurance of an externally defined class is always conformant with the original definition. However, not every standard-compliant class might be compliant to the dataspace profile.
Asset Entries. Since a catalog may be dynamically generated for a request based on the requesting participant's credentials it is possible for it to contain 0 matching asset entries. (DCAT PROFILE)
hasPolicyattributes that contain an ODRL
Offerdefining the usage control policy associated with the asset. Offers must NOT contain any target attributes. The target of an offer is the asset associated with the containing asset entry. (ODRL PROFILE)
- 1..N DCAT Distributions. Each distribution must have at least one
DataServicewhich specifies where the distribution is obtained. Specifically, a
DataServicespecifies the endpoint for initiating a
AssetTransfer. (DCAT PROFILE)
- An ODRL
uidis represented as an "@id" that is a unique UUID. (ODRL PROFILE)
Offermust be unique to a dataset since the target of the offer is derived from its enclosing context.
Offermust NOT include an explicit
Agreementclass must include one
targetattribute that is the UUID of the asset the agreement is associated with. An agreement is therefore associated with EXACTLY ONE asset. (ODRL PROFILE)
Last modified 2mo ago