Skip to main content

EU LDT Toolbox glossary

C

A layer within the EU LDT Use Cases & Scenarios tool that defines a specific urban scope, objectives, and problems, such as optimising traffic circulation or assessing the impact of a new housing project. Cases serve as a comprehensive record of urban challenges, encompassing relevant factors, scope, objective, and data. 

A module composed of key components including Case Controller, Scenario Controller, Experiment Manager, and Integration Controller, which manage the lifecycle of cases, scenarios, and experiments. 

Manages the lifecycle of cases, including creation, modification, deletion, and versioning, and validates case configurations to ensure data integrity. 

The document used to track and communicate changes made to a software project over time.

A user persona representing the end-user of the EU LDT Participate tool, who engages with participatory processes. 

A user persona responsible for creating, configuring, and managing participatory processes on the platform. 

A user persona responsible for sending mass email communications on the platform. 

An EU LDT Toolbox tool that can be integrated to visualise and select strategic objectives, initiatives, tasks, KPIs, and city maturity data. 

The user persona representing the target user of the EU LDT Use Cases & Scenarios tool, responsible for defining cases and scenarios, and executing related experiments to test solutions for city problems or to mitigate risks.

A component that provides logging, monitoring, and accountability services in a data space, ensuring transparency and auditability of data transactions. 

A software application or service that connects to EU LDT Toolbox and requires authentication and authorisation through Identity Manager. 

A group of physical or virtual machines (nodes) that work together to run containerised applications managed by Kubernetes. 

A Kubernetes Service type that exposes the service on an internal IP address within the cluster. This is the default service type and is used for internal service-to-service communication. 

The process of involving the public in decision-making processes. 

A configurable module within a participatory process, such as a Blog, Debates, Meetings, Page, Proposal, or Survey. 

A Kubernetes object used to store non-confidential configuration data in key-value pairs. ConfigMaps are used to configure applications without hardcoding configuration values. 

A component that facilitates secure data exchange between data space participants, often implementing identity, policy enforcement, and contract negotiation mechanisms. 

A lightweight, stand-alone, executable software package that includes all necessary components to run an application (code, runtime, system tools, libraries). 

The core component responsible for managing contextual entities in NGSI-LD format, including creation, update, retrieval, and deletion. 

The functionality that enables visualisation, filtering, and management of contextual entities and data received from devices or external sources. 

The process by which data sent by IoT devices (via HTTP or MQTT, using JSON or Ultralight formats) is received, validated, and transformed into NGSI-LD. 

A mechanism that allows users to subscribe to changes in entities or attributes and receive real-time notifications when updates occur. 

Temporal data that stores the historical evolution of entity attributes, including timestamps for each change. 

A small piece of data sent from a website and stored on the user's computer by the user's web browser while the user is browsing. 

A tabular file format used to store structured data separated by commas, commonly used for data export and interoperability.