| Name | Definition | Source |
|---|---|---|
| Access policy | Access policies are rules and conditions prepositioned as to how the Provider wants to control the service. The access policy allows you to configure operations, permissions, access rules and selection rules that restricts/allow certain access to a service. | Common policy concept definition |
| Applicant | An entity that submits an application or request to join, partake in, or receive something from a data space. This term is typically used in contexts where a selection or approval process is in place. Applicants are at the initial stage of engagement with the data space, seeking approval or acceptance which is based on the criteria and procedures set by the data space Governance Authority. | Based on DSSC Glossary |
| Application catalogue | A catalogue containing descriptions of applications (e.g., services, tools, workflows) provided within the data space. | Based on DSSC Glossary |
| Authentication provider federation | A federation of authentication service providers that enables End-Users to authenticate seamlessly across different systems or organisations using a unified and interoperable framework. This federation facilitates the sharing of authentication credentials and ensures a consistent and secure authentication experience across various platforms. | |
| Catalogue | A centralised repository or directory that stores and organises descriptions of a certain type of asset (e.g., data, applications, or infrastructure) to enable discovery by Participants. | Based on DSSC Glossary |
| Consent | Any freely given, specific, informed and unambiguous indication of the data subject's wishes by which they, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to them. | GDPR (Art. 4) |
| Consumer | A Participant that can access data, application, and infrastructure from the data space. They can interact with the Simpl in various ways: they can search for data or for other resources, such as algorithms and AI models in the data spaces; use them online by utilising the infrastructure and services provided by the Simpl middleware or if policy allows, download them for local usage. | Based on DSSC Glossary |
| Contract clause | A contract clause defines the terms and conditions for using an asset described in a resource description, as well as the terms and conditions to which the Provider commits. These clauses may include service level agreements, a license agreement, and a billing schema. The contract clauses are added when the resource description is created, based on its schema, and are later used when generating a usage contract offer for a Consumer. | Based on DSSC Glossary |
| Contract clause - Billing schema | Defines how service usage is tracked, priced, and billed. It covers pricing models, units of consumption, and billing cycles. | Based on DSSC Glossary |
| Contract clause - Service level agreement | Defines the expected performance and quality standards of a service, including metrics such as uptime, response time, and support provisions. | Based on DSSC Glossary |
| Contract clause - Licence | Defines the terms under which a resource (e.g., software or data) may be used, including allowed uses, usage restrictions, and intellectual property rights. | Based on DSSC Glossary |
| Contract issuer | The contract issuer is the entity or role that creates and issues a contract offering to another party. Typically, this is the Provider organisation (or its authorised Representative) drafting the initial terms for Consumer review. | DSSC Glossary |
| Data catalogue | A catalogue containing descriptions of data resources or services (e.g., data assets, schemas, metadata, access policies) provided within the data space. | Based on DSSC Glossary |
| Data orchestration platform | Defines a system that coordinates, manages, and automates data workflows. It enables the scheduling, execution, monitoring, and governance of data processing tasks, ensuring interoperability, reliability, and scalability in data spaces. The platform abstracts the complexity of underlying data sources and services, allowing Participants to design, deploy, and optimise workflows that integrate resources. | Internal definition (based on common data orchestration concepts) |
| Data policy | A set of rules, working instructions, preferences and other guidance to ensure that data is obtained, stored, retrieved, and manipulated consistently with the standards set by the governance framework or data rights holders. | DSSC Glossary |
| Data rights holder | A party that has (legal) rights and/or obligations to use, grant access to or share certain personal or non-personal data. Data rights holders may transfer such rights to others. | DSSC Glossary |
| Data sharing agreement | A data sharing agreement is a formal contract between parties defining how data will be shared and used. It outlines permissions, restrictions, and responsibilities for each party, ensuring legal and regulatory compliance. | General data handling term |
| Data space | A distributed system defined by a governance framework that enables secure and trustworthy data transactions between Participants while supporting trust and data sovereignty. A data space is implemented by one or more infrastructures and enables one or more use cases. | DSSC Glossary |
| Digital signer | The digital signer role is an extended role (in Tier 1) that identifies the End-Users who are able to digitally sign in on behalf of a Participant. Such signatures lend legal validity and are used to make contracts tamper-proof and verifiable. | Based on DSSC Glossary |
| End-User | An End-User is an ultimate User of the Simpl-Open agent, either a) a real person interacting with the Simpl-Open agent via a user interface, or b) an IT system interacting via agent APIs. | |
| Governance Authority | The data space Participant that is accountable for creating, developing, operating, maintaining and enforcing the governance framework for a particular data space, without replacing the role of public enforcement authorities. | DSSC Glossary |
| Governance framework | The set of principles, standards, policies (rules/regulations), agreements and practices that apply to the governance, management, and operations (including business and technology aspects) of a data space as well as to the enforcement thereof, and the resolution of any conflicts. | DSSC Glossary |
| Governance policy | A policy that defines the overall governance framework: decision-making bodies, roles, responsibilities, change-control and review cycles. | Common policy concept definition |
| Identity attribute | A characteristic or piece of information about an entity (End-User or Participant) used to make access control decisions. Examples include attributes like organisation, role, or access level associated with that entity. Identity attributes are used to enforce ABAC (attributes-based access control) in the agent-to-agent communication (tier 2). | |
| Identity provider federation | A collaborative arrangement among multiple identity providers to mutually recognise and share user identities across different organisations or services. It allows End-Users to use a single set of credentials to access multiple systems or services, thereby simplifying the authentication process and enhancing user convenience while maintaining security and trust. | |
| Infrastructure catalogue | A catalogue containing descriptions of infrastructure resources or services (e.g., compute, storage, network offerings) provided within the data space. | Based on DSSC Glossary |
| Participant | A party that has committed to the governance framework of a data space and has certain rights and obligations within it, may have one or more roles in it. They have successfully passed the approval or acceptance in the application process and are now actively involved or engaged in the services offered by the applied data space. Participants are either a Governance Authority, Provider or Consumer. | DSSC Glossary |
| Policy | Policies define rules that Providers want to enforce in order to control the access and usage of their resources. | Common policy concept definition; Gaia-X Glossary |
| Provider | A Participant that operates resources (such as data or application/infrastructure services) and offers them to others in the ecosystem, by publishing those resources in catalogues for discovery and access. | Based on DSSC Glossary |
| Representative | A human End-User acting on behalf of a data space Participant (such as a Provider, Consumer, or the Governance Authority). This person is authorised to perform actions in the data space for their organisation. | Based on DSSC Glossary |
| Resource description | Resource description refers to the metadata records that describe various resources, allowing identification, searchability, access management, preservation, and prediction of resource behaviour. These resources can include data, applications, or infrastructure. | Based on DSSC Glossary |
| Schema | The structure, format, and organisation of metadata that describes resources in a data space catalogue. The schema defines rules for how Providers must create resource descriptions by specifying which properties must be included, how they should be structured, and what values are permitted. Schemas are built upon one or more vocabularies and the schema constraints (e.g., data types, formatting, allowed values) that define the syntax of the metadata created based on the schema to allow validation. | Based on DSSC Glossary |
| Security attribute provider federation | A network of security attribute providers that collaborate to share and manage security-related attributes of End-Users across different domains or services. This federation facilitates a unified approach to attribute management, enhancing security, interoperability and user experience in various environments. | |
| Self-description | A metadata record that Providers use to describe themselves, their data product offerings, and the resources and services their data products are composed of. | DSSC Glossary |
| Semantic validation | The process of ensuring that data is meaningful and complies with a predefined set of vocabularies, rules, and models, defined within a specific context. | |
| Service contract | A service contract is a legal agreement that governs the provision and consumption of a service between a Provider and a Consumer. It specifies deliverables, performance levels (e.g. uptime), usage terms, and the obligations of each party. | Based on DSSC Glossary |
| Simpl-Open | Simpl-Open is an open source software stack that powers data spaces and other cloud-to-edge federations initiatives. Simpl-Open focuses on leveraging and collaborating with the data spaces and open source community through open source code. | Simpl Programme |
| Simpl-Open agent | A set of integrated software components deployed by a Participant, acting as a local gateway for data and service interactions. | |
| Syntax validation | The process of checking that a data structure or file conforms to the required format and grammar rules (for example, JSON or XML syntax). | |
| Transaction | The result of an interaction between two Participants with the purpose of sharing, accessing, exchanging resources. | Based on DSSC Glossary |
| Transaction Participant | A data space Participant, which directly participates in a transaction by providing a resource, providing permissions/consent related to a resource or by receiving/consuming a resource and/or permissions/consent to use a resource. | Based on DSSC Glossary |
| Usage contract | A usage contract is the signed agreement between a Provider and a Consumer, that stipulates the type of services a Provider offers to the Consumer and includes the conditions and policies the service, Provider and Consumer need to adhere to. The usage contract is formed and signed by both the Provider & Consumer during the contract negotiation process. The usage contract is afterwards used as an immutable credential by the Provider and the Consumer. | Based on DSSC Glossary |
| Usage contract offer | Usage contract offer is created based on the information available in the resource description for which the usage contract offer is requested. It is an initial proposal presented by the Provider, outlining the contract clauses, the usage policies, and the access policies for the Consumer usage. The usage contract offer remains unsigned and does not yet represent a binding agreement. | Based on DSSC Glossary |
| Usage policy | Policies defined by the Provider for the usage of their resource in a data space. The policies regulate the permissible actions and behaviours related to the utilisation of the accessed data/application/infrastructure. A usage policy defines what actions can be undertaken on a resource by what Consumers and under what constraints. | Common policy concept definition |
| Vocabulary | A set of standardised, machine-readable terms - including classes and properties - used to model the semantics of data and annotate datasets. Its primary purpose is to enable unambiguous, consistent interpretation and interoperability of data across multiple resources and participants. | Based on DSSC Glossary |
| Vocabulary management | Defines the governance and lifecycle of vocabularies within a data space. It ensures semantic interoperability of data structures across domains and data providers by managing native vocabularies and supporting the registration and use of external vocabularies. | Based on DSSC Glossary |
Simpl Programme
Please log in or sign up to comment.