Capabilities and Requirements

Capability C1: Define governance rules for the data sharing ecosystem

Requirements for C1
RC1.1: The orchestrator of a data ecosystem should be able to define a governance model (e.g. rulebook) that outlines membership rules, the roles, responsibilities and obligations of ecosystem participants and overall principles that govern the data exchange between them.
RC1.2: Members who participate in a data ecosystem should be aware of its governance model and any changes made to it.
RC1.3: The governance model should be easily comprehensible by all ecosystem participants.

Capability C2: Define terms and conditions for data sharing.

Requirements for C2
RC2.1: Data providers are free to define terms and conditions under which they want their data to be exchanged. (Before sharing data assets, data providers should ensure they have adequate permission from data owners.)
RC2.2: Terms and conditions for a data exchange should be described clearly and unambiguously so that they are easily understandable for data users.
RC2.3: Terms and conditions for a data exchange should be expressed through data licenses/data sharing agreements based on well-defined templates or standards.
RC2.4: Terms and conditions should be in line with the overall governance model of the data ecosystem and not conflict with it. (Note: A data provider can decide not to participate in a data ecosystem if the underlying governance model is too restrictive or permissive.)

Capability 3: Validate compliance with data sharing terms and conditions

Requirements for C3
RC3.1: The orchestrator of a data ecosystem must be able to ascertain compliance of its participants with the underlying governance model.
RC3.2: Data providers should be able to ascertain that the use of data by a data user complies with previously agreed-upon terms and conditions.
RC3.3: Data users should be able to ascertain that the data provider's supply of data follows previously agreed-upon terms and conditions.

Capability 4: Discover available data assets

Requirements for C4
RC4.1: Data users should be able to discover what data is available in a data sharing ecosystem without prior knowledge of it.
RC4.2: Data assets should be adequately described with metadata so that data users can make reliable decisions about their further intended use.
RC4.3: Metadata used to describe data assets should be based on well-defined, easy-to-understand description formats that are both human—and machine-readable.

Requirements for C4
RC4.1: Data users should be able to discover what data is available in a data sharing ecosystem without prior knowledge of it.
RC4.2: Data assets should be adequately described with metadata so that data users can make reliable decisions about their further intended use.
RC4.3: Metadata used to describe data assets should be based on well-defined, easy-to-understand description formats that are both human—and machine-readable.

Capability 5: Discover ecosystem participants

Requirements for C5
RC5.1: Ecosystem participants (e.g., data users and providers) should be able to discover each other within a data-sharing ecosystem
RC5.2: Sufficient metadata about each ecosystem participant should be available to ascertain their trustworthiness relevant for data exchange.
RC5.3: Data providers should be able to reliably identify data users who want to access their data assets and verify their metadata before granting access to their data.
RC5.4: Data users should be able to identify data providers who share data in a data ecosystem before accessing or using data.
RC5.5: Ecosystem participants may also choose to remain anonymous if the governance model of the data-sharing ecosystem allows for it. In this case, RC5.1 to RC5.4 can be ignored.

Capability 6: Agree on data exchange

Requirements for C6
RC6.1: Data users and providers should be able to agree to a data exchange and the terms and conditions associated with it (e.g. acceptance of terms or the legal signature of the agreement, negotiations).
RC6.2: Data users and providers should be able to terminate a previously agreed-upon data exchange in accordance with the previously agreed-upon terms and conditions associated with the data exchange
RC6.3: Where possible, electronic means for agreement and termination of a data exchange may be provided.

Capability 7: Request new data currently not available

Requirements for C7
RC7.1: Data users should be able to express their interest in data assets currently unavailable in the data sharing ecosystem.
RC7.2: Data providers should be able to obtain requests made by data users for new data assets.