Glossary

UID

A Kubernetes-generated string is used to identify objects in a unique manner. Each object that is created throughout the entire lifespan of a Kubernetes cluster has a unique UID. This UID is designed to differentiate between similar entities that may have occurred at different times in the past.

Upstream (disambiguation)

The term "upstream" can have different meanings depending on the context. It can refer to the core Kubernetes codebase or the source repository from which another repository was forked. Within the Kubernetes community, "upstream" typically refers to the core Kubernetes codebase that serves as the foundation for other tools and code in the ecosystem. Community members may suggest moving a feature upstream, which means incorporating it into the core codebase instead of relying on a plugin or third-party tool. In GitHub or git, "upstream" conventionally refers to the source repository, while the forked repository is considered downstream.

Usage Contract

Set of conditions and rules corresponding to one or more transactions in the IDS

Usage Control

Usage control is focused on setting and enforcing limitations on how data can (or cannot) be handled, rather than controlling data access. Its main objective is to regulate data processing requirements, known as obligations. In contrast to access control, which deals with granting or denying access to data, usage control comes into play after access has been granted, with the goal of ensuring that data usage restrictions are adhered to. The ultimate aim of usage control is to link policies to the data being shared.

Usage Plane

One of the three levels of interoperability represented by the Gaia-X framework is captured by its three planes, which includes technical interoperability, specifically between different Service Offerings.

Usage Policy

A set of regulations outlined by the Data Owner that limits the usage of their data, including factors such as time-to-live and forwarding conditions such as anonymization or scope of usage. These rules are transmitted along with the data and are enforced while the data resides on the Data Consumer's Connector.

Use Case

A Gaia-X use case refers to a potential application for innovation that utilizes and is based on the Gaia-X Federation Services, catering to cross-sector or industry-specific needs. These use cases come from various domains and are submitted to the Gaia-X hubs, highlighting the benefits of having a data infrastructure. They showcase the importance of the ecosystem and the dependencies involved, while also describing the advantages of (cross-)domain exchange, all supported by Gaia-X. Additionally, these use cases help in identifying domain-specific and cross-domain requirements, which are incorporated into the development of Gaia-X.

Use Case / Usecase

The term refers to a concept within the IT sector used to describe requirements for a software system.

User

A participant in the Gaia-X ecosystem can be an individual, entity or organization that uses services provided by Gaia-X to connect their applications within the ecosystem.

User and Role management

Enables customers to manage user accounts that have access to the User Interface, including the ability to invite, update, and remove user accounts. Customers can also define which users are authorized to perform specific functions.

User interface

Configuring the data transformation process using a browser-based User Interface.

User Namespace

User namespaces are a Linux kernel feature that enables a non-root user to simulate superuser privileges, also known as "rootless containers." This feature is particularly useful for running containers without requiring superuser access outside of the container. By utilizing user namespaces, potential damage caused by container break-out attacks can be mitigated. It's important to note that the term "namespace" in the context of user namespaces refers to a Linux kernel feature, and should not be confused with namespaces in the context of Kubernetes.