{"id":20777818,"url":"https://github.com/fiware/catalogue","last_synced_at":"2025-03-11T21:46:39.982Z","repository":{"id":41087473,"uuid":"147646906","full_name":"FIWARE/catalogue","owner":"FIWARE","description":"Curated framework of open source platform software components using 𝑭𝑰𝑾𝑨𝑹𝑬 which can be assembled together to accelerate the development of Smart Solutions.","archived":false,"fork":false,"pushed_at":"2024-06-11T02:14:24.000Z","size":42787,"stargazers_count":158,"open_issues_count":0,"forks_count":38,"subscribers_count":24,"default_branch":"master","last_synced_at":"2024-06-11T20:11:08.881Z","etag":null,"topics":["contextual-data","data-publication","fiware","generic-enablers","iot-agent","monetization","processing","robotics","security","smart-app"],"latest_commit_sha":null,"homepage":"https://www.fiware.org/developers/catalogue/","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"agpl-3.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/FIWARE.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":"security/README.md","support":null,"governance":null,"roadmap":"roadmap.md","authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2018-09-06T09:04:56.000Z","updated_at":"2024-06-17T09:54:02.050Z","dependencies_parsed_at":"2023-11-17T03:57:50.216Z","dependency_job_id":"24aa5919-54c5-4dd0-acf1-25ef771c4977","html_url":"https://github.com/FIWARE/catalogue","commit_stats":null,"previous_names":[],"tags_count":20,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/FIWARE%2Fcatalogue","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/FIWARE%2Fcatalogue/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/FIWARE%2Fcatalogue/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/FIWARE%2Fcatalogue/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/FIWARE","download_url":"https://codeload.github.com/FIWARE/catalogue/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":243119661,"owners_count":20239319,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["contextual-data","data-publication","fiware","generic-enablers","iot-agent","monetization","processing","robotics","security","smart-app"],"created_at":"2024-11-17T13:17:36.399Z","updated_at":"2025-03-11T21:46:39.963Z","avatar_url":"https://github.com/FIWARE.png","language":null,"readme":"# Catalogue\u003cimg src=\"https://fiware.github.io//catalogue/img/fiware-black.png\" width=\"145\" align=\"left\"\u003e\n\n![FIWARE Catalogue](https://nexus.lab.fiware.org/repository/raw/public/badges/chapters/cross-chapter.svg)\n[![License AGPL](https://img.shields.io/github/license/fiware/catalogue.svg)](https://opensource.org/licenses/AGPL-3.0)\n\nThis is an umbrella repository which briefly introduces each of the components (also referred as Generic Enablers) which\nare part of [FIWARE](https://www.fiware.org/developers/) and allow users and developers to easily navigate to the\nrelevant source code repositories, documentation and container registry images on **Docker Hub** or **quay.io**.\n\n\n\nMore information about what FIWARE is and how to use it can be found within the **FIWARE Tour Guide**, the **FIWARE\nAcademy** and the **Step-by-Step Tutorials**. Generic questions about FIWARE can be asked on **Ask.FIWARE** and\ndeveloper-based questions can be submitted on **Stack Overflow** using the FIWARE tag, and discussions raised on the\nFIWARE **Discord Channel**\n\n\n \n| \u003cimg src=\"https://fiware.github.io/catalogue/img/fiware-emoji.png\" height=\"20px\" width=\"20px\"/\u003e\u003cbr/\u003e [fiware.org](https://www.fiware.org/developers/) |:books: \u003cbr/\u003e [Tour Guide](https://fiwaretourguide.rtfd.io) | :mortar_board: \u003cbr/\u003e [Academy](https://fiware-academy.readthedocs.io) | :capital_abcd: \u003cbr/\u003e [Tutorials](https://fiware-tutorials.rtfd.io) | :question: \u003cbr/\u003e [Ask.\u0026ZeroWidthSpace;FIWARE](https://ask.fiware.org/questions/) | ![Support badge](https://img.shields.io/badge/tag-fiware-orange.svg?logo=stackoverflow) \u003cbr/\u003e [Stack Overflow](https://stackoverflow.com/questions/tagged/fiware) | \u003cimg width=\"18px\" src=\"https://cdn.jsdelivr.net/npm/simple-icons@v3/icons/discord.svg\" /\u003e \u003cbr/\u003e [Discord Channel](https://discord.gg/ZWvTUfepHr)\n| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | --------------------------------------------------------------------- | ------------------------------------------------------------------ | -------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | --- |\n\n---\n\n\u003c!--\n\u003cdiv align=\"center\"\u003e\n \n| \u003ca href=\"https://www.fiware.org/global-summit/\"\u003e\u003cimg src=\"https://fiware.github.io//catalogue/img/Summit24.png\" width=\"240\" height=\"70\" /\u003e\u003c/a\u003e | \u003ca href=\"https://www.eventbrite.de/e/fiware-tech-training-naples-tickets-920143322447\"\u003e\u003cimg src=\"https://fiware.github.io//catalogue/img/Training24.png\" width=\"240\" height=\"70\" /\u003e\u003c/a\u003e |\n| --- | --- |\n\n\u003c/div\u003e\n--\u003e\n\n## Contents\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cstrong\u003eDetails\u003c/strong\u003e\u003c/summary\u003e\n\n-   [Background](#background)\n-   [Installation](#installation)\n-   [Generic Enablers](#generic-enablers)\n    -   [Core Context Management](#core-context-management)\n    -   [Interface with IoT, Robots and Third-Party Systems](#interface-with-iot-robots-and-third-party-systems)\n    -   [Context Processing, Analysis and Visualization](#context-processing-analysis-and-visualization)\n    -   [Context Data/API Management, Publication and Monetization](#context-dataapi-management-publication-and-monetization)\n    -   [Deployment Tools](#deployment-tools)\n-   [Data Spaces](#data-spaces)\n-   [Management of FIWARE Releases](#management-of-fiware-releases)\n-   [Testing](#testing)\n-   [Contributing](#willing-to-contribute-your-technology-to-fiware)\n-   [License](#license)\n\n\u003c/details\u003e\n\n## Background\n\n[FIWARE](https://www.fiware.org) brings a curated framework of open source software platform components which can be\nassembled together and with other third-party components to build platforms that support the development of Smart\nSolutions faster, easier and cheaper. The main and only mandatory component of any _“Powered by FIWARE”_ platform or\nsolution is a FIWARE Context Broker Generic Enabler, supplying a cornerstone function required in any smart solution:\nthe need to manage context information, enabling to perform updates and bring access to context.\n\nFIWARE NGSI is the API exported by a FIWARE Context Broker, used for the integration of platform components within a\n_\"Powered by FIWARE\"_ platform and by applications to update or consume context information. FIWARE NGSI API\nspecifications have evolved over time, initially matching\n[NGSI-v2 specifications](http://fiware.github.io/specifications/ngsiv2/stable/), now aligning with the\n[ETSI NGSI-LD standard](https://www.etsi.org/committee/). The FIWARE Community plays an active role in the evolution\nof ETSI NGSI-LD specifications which were based on NGSI-v2 and commits to deliver compatible open source implementations\nof the specs.\n\n![](https://fiware.github.io/catalogue/img/catalogue.png)\n\nBuilding around the FIWARE Context Broker, a rich suite of complementary open-source FIWARE Generic Enablers are\navailable, dealing with the following:\n\n-   **[Core Context Management](./core/)** manipulates and stores context data so it can be used for further\n    processesing\n-   **Interfacing with the [Internet of Things](./iot-agents/) (IoT), [Robots](./robotics) and\n    [third-party systems](./third-party/)**, for capturing updates on context information and translating required\n    actuations.\n-   **[Processing, analysis and visualization](./processing/)** of context information, implementing the expected smart\n    behaviour of applications and/or assisting end users in making smart decisions.\n-   **[Context Data/API management](./api-management/), [Security](./security/),\n    [publication and monetization](./data-publication/)**, bringing support to usage control and the opportunity to\n    publish and monetize part of managed context data.\n-   **[Deployment Tools](#deployment-tools)** such as Docker images and Helm-chart recipes are available for each\n    Generic Enabler\n\nFIWARE is not about take it all or nothing. You are not forced to use these complementary FIWARE Generic Enablers but\nare free to use other third platform components as well to design the hybrid platform of your choice. As long as it uses\nthe FIWARE Context Broker technology to manage context information, your platform can be labeled as _“Powered by\nFIWARE”_ and solutions build on top as well. Listings of many FIWARE Ready devices and commercial _“Powered by FIWARE”_\nsolutions can be found on the [FIWARE Marketplace](http://marketplace.fiware.org/).\n\nTo be adopted as a Generic Enabler within FIWARE, each open source component must fulfil a number of **contribution\nrequirements**. The technical direction of FIWARE is governed by the **FIWARE Technical Steering Committee (TSC)**.\nDevelopers can also subscribe to the **FIWARE TSC mailing list**, join the FIWARE TSC regular confcalls as observer and\nfollow the progress of the discussions through the **FIWARE TSC meeting minutes**.\n\n| :clipboard: \u003cbr\u003e [Contribution Requirements](https://github.com/FIWARE/contribution-requirements) | :family: \u003cbr\u003e [Technical Steering Committee](https://www.fiware.org/foundation/technical-steering-committee/) | :mega: \u003cbr\u003e [Mailing list](https://lists.fiware.org/listinfo/fiware-technical-committee) | :open_file_folder: \u003cbr\u003e [Meeting minutes](https://docs.google.com/spreadsheets/d/11zZAv7l3FCr0a0I_UoC39S6dwdjC2x7ydmPeH61-X74/edit?usp=sharing) |\n| ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |\n\n\n## Installation\n\nTo obtain the latest codebase of all FIWARE Generic Enablers:\n\n```console\ngit clone https://github.com/FIWARE/catalogue.git\ncd catalogue/\ngit submodule update --init --recursive\ngit submodule update --recursive --remote\n```\n\n## Generic Enablers\n\nThe following sections describe the current list of Generic Enablers of the FIWARE platform structured into five\narchitectural chapters.\n\n### Core Context Management\n\n[![](https://nexus.lab.fiware.org/repository/raw/public/badges/chapters/core.svg)](./core/README.md)\n\n#### Core Context Broker components\n\nA Context Broker component is the core and mandatory component of any _“Powered by FIWARE”_ platform or solution. It\nenables to manage context information in a highly decentralized and large-scale manner.\n\n-   The [Orion Context Broker](https://github.com/telefonicaid/fiware-orion/) Generic Enabler currently provides the\n    FIWARE NGSI v2 API which is a simple yet powerful Restful API enabling to perform updates, queries or subscribe to\n    changes on context information.\n\nThe following Context Broker implementations, supporting the ETSI\n[NGSI-LD 1.3.1. API specification or higher](https://www.etsi.org/standards#page=1\u0026search=Context%20Information\u0026title=1\u0026etsiNumber=1\u0026content=1\u0026version=1\u0026onApproval=1\u0026published=1\u0026historical=1\u0026startDate=2020-01-01\u0026endDate=2021-11-23\u0026harmonized=0\u0026keyword=\u0026TB=854\u0026stdType=\u0026frequency=\u0026mandate=\u0026collection=\u0026sort=1)\nare available:\n\n-   The [Orion-LD Context Broker](https://github.com/FIWARE/context.Orion-LD) Generic Enabler is a NGSI-LD Broker, which\n    supports both NGSI-LD and the NGSI-v2 APIs.\n-   The [Scorpio Broker](https://github.com/ScorpioBroker/ScorpioBroker) Generic Enabler is an alternative NGSI-LD\n    Broker which can also be used in federated environments\n-   The [Stellio Context Broker](https://github.com/stellio-hub/stellio-context-broker) Generic Enabler is another\n    alternative NGSI-LD Broker\n    \n    \n##### NGSI-LD Context Broker Feature Comparison\n\nThe NGSI-LD Specification is regularly updated published by ETSI. The latest specification is [version 1.8.1](https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.08.01_60/gs_cim009v010801p.pdf) which was  published in **March 2024**. \n\n-   A spreadsheet detailing the current compatibility of the bleeding edge development version of each context broker (Orion-LD, Scorpio, Stellio) against the features of the 1.6.1 specification can be viewed and downloaded [here](https://docs.google.com/spreadsheets/d/e/2PACX-1vRxOjsDf3lqhwuypJ---pZN2OlqFRl0jyoTV0ewQ1WFnpe7xQary3uxRjunbgJkwQ/pub)\n    \n-   An Excel file detailing the compatibility of the latest FIWARE Release of each context broker (Orion-LD, Scorpio, Stellio) against the features of the 1.6.1 specification can be downloaded [here](https://fiware.github.io/catalogue/excel/NGSI-LD%20Brokers%20Implementation%20Status.xlsx)\n\n#### Core Data Connectors\n\nAccompanying a Context Broker component as part of Core Context Management, a number of Data Connectors are available:\n\n-   The [Cygnus](https://github.com/telefonicaid/fiware-cygnus) Generic Enabler is enables a means of managing the\n    history of context which is created as a stream of data and can be injected into multiple data sinks, including many\n    popular databases such as PostgreSQL, MySQL, MongoDB or AWS DynamoDB or as Big Data platforms such as Hadoop, Storm\n    or Spark. The component is based on Apache Flume\n-   The [Draco](https://github.com/ging/fiware-draco) Generic Enabler is an alternative data persistence mechanism for\n    managing the history of context. It is based on Apache NiFi and is a dataflow system based on the concepts of\n    flow-based programming. It supports powerful and scalable directed graphs of data routing, transformation, and\n    system mediation logic and also offers an intuitive graphical interface\n-   The [Cosmos](https://github.com/ging/fiware-cosmos) Generic Enabler enables simpler Big Data analysis over context\n    integrated with popular Big Data platforms (Spark and Flink).\n-   The [QuantumLeap](https://github.com/smartsdk/ngsi-timeseries-api/) Generic Enabler supports the storage of context\n    data into a time series database (CrateDB and Timescale)\n-   The [STH Comet](https://github.com/telefonicaid/fiware-sth-comet/) Generic Enabler brings the means for storing a\n    short-term history of context data (typically months) on MongoDB\n\nThe following is a list of Generic Enablers under incubation within the area of Core Data Connectors systems:\n\n-   [Mintaka](https://github.com/FIWARE/mintakas) is an add-on to the [Orion-LD Context Broker](https://github.com/FIWARE/context.Orion-LD) providing an\n    implementation of the NGSI-LD temporal retrieval API.\n-   The [Canis Major](https://github.com/fiware/CanisMajor) Generic Enabler is a blockchain adaptor that supports\n    various DLTs, the adaptor aims to submit the data to DLT using FIWARE Technologies\n-   The [NGSI.js Library](https://github.com/ficodes/ngsijs) provides a series of JavaScript functions allowing\n    developers to connect and push context data to any NGSI compliant context broker\n-   The [PySpark Connector](https://github.com/Engineering-Research-and-Development/fiware-orion-pyspark-connector)\n    Generic Enabler creates a data bridge between context brokers and PySpark\n-   The [O2K Connector](https://github.com/Engineering-Research-and-Development/o2k-connector)\n    Generic Enabler that enables context data sharing from any NGSI Context Broker towards Apache Kafka\n-   The [Apollo](https://github.com/FIWARE/apollo) Generic Enabler creates entities based on notifications\n\nFurther information can be found on dedicated pages linked to [Core Context Management](./core/README.md)\n\n### Interface with IoT, Robots and Third-Party Systems\n\n[![](https://nexus.lab.fiware.org/repository/raw/public/badges/chapters/iot-agents.svg)](./iot-agents/README.md)\n[![](https://nexus.lab.fiware.org/repository/raw/public/badges/chapters/robotics.svg)](./robotics/README.md)\n[![](https://nexus.lab.fiware.org/repository/raw/public/badges/chapters/third-party.svg)](./third-party/README.md)\n[![](https://nexus.lab.fiware.org/repository/raw/public/badges/chapters/media-streams.svg)](./iot-agents/README.md)\n\nA number of Generic Enablers are available making it easier to interface with the Internet of Things (IoT), Robots and\nThird-party systems for the purpose of gathering valuable context information or trigger actuations in response to\ncontext updates:\n\n-   The **IDAS** Generic Enabler offers you a wide range of IoT Agents making it easier to interface with devices using\n    the most widely used IoT protocols (LWM2M over CoaP, JSON or UltraLight over HTTP/MQTT, OPC-UA, Sigfox or LoRaWAN)\n\n    -   [IoT Agent for JSON](https://github.com/telefonicaid/iotagent-json) - a bridge between HTTP/MQTT messaging (with\n        a JSON payload) and NGSI\n    -   [IoT Agent for LWM2M](https://github.com/telefonicaid/lightweightm2m-iotagent) - a bridge between the\n        [Lightweight M2M](https://www.omaspecworks.org/what-is-oma-specworks/iot/lightweight-m2m-lwm2m/) protocol and\n        NGSI\n    -   [IoT Agent for Ultralight](https://github.com/telefonicaid/iotagent-ul) - a bridge between HTTP/MQTT messaging\n        (with an UltraLight2.0 payload) and NGSI\n    -   [IoT Agent for LoRaWAN](https://github.com/Atos-Research-and-Innovation/IoTagent-LoRaWAN) - a bridge between the\n        [LoRaWAN](https://www.thethingsnetwork.org/docs/lorawan/) protocol and NGSI\n    -   [IoT Agent for OPC-UA](https://github.com/Engineering-Research-and-Development/iotagent-opcua) - a bridge\n        between the [OPC Unified Architecture](http://www.opcua.us/) protocol and NGSI\n    -   [IoT Agent for Sigfox](https://github.com/telefonicaid/sigfox-iotagent) - a bridge between the\n        [Sigfox](https://www.sigfox.com/en) protocol and NGSI\n    -   [IoT Agent for ISOXML](https://github.com/FIWARE/iotagent-isoxml) - a bridge between the ISOXML/ADAPT protocol\n        for agricultural machinery and NGSI\n    -   [IoT Agent library](https://github.com/telefonicaid/iotagent-node-lib/) - library for developing your own IoT\n        Agent.\n\n-   The [Kurento](https://github.com/kurento/) Generic Enabler enables real-time processing of media streams supporting\n    the transformation of video cameras into sensors as well as the incorporation of advanced application functions\n    (integrated audiovisual communications, augmented reality, flexible media playing and recording, etc)\n\nThe following is a list of Generic Enablers under incubation within the area of IoT, Robotics and third-party systems:\n\n-   The [OpenVidu](https://github.com/OpenVidu/openvidu/) Generic Enabler is an abstraction layer for Kurento, making\n    media processing easier to program.\n-   The [OpenMTC](https://github.com/OpenMTC/OpenMTC) Incubated Generic Enabler brings an open source implementation of\n    the [OneM2M](http://www.onem2m.org/) standard. A northbound interface with the Orion Context Broker is implemented\n    as part of the product.\n-   The [Fast DDS](https://github.com/eProsima/Fast-RTPS) Incubated Generic Enabler has been adopted as default\n    middleware in [ROS2](https://index.ros.org/doc/ros2/), the widely known Robot Operating System, therefore it helps\n    to interface with ROS2-based robotics systems.\n-   The [Micro XRCE-DDS](https://github.com/eProsima/Micro-XRCE-DDS) Incubated Generic Enabler is a lite version of the\n    [DDS](https://www.omg.org/spec/DDS) middleware, adapted to run in extremely constrained resource devices (e.g.\n    micro-controllers).\n-   The [FIROS](https://github.com/iml130/firos) Incubated Generic Enabler works as a translator between the robotics\n    domain and the cloud, transforming [ROS](https://www.ros.org/) messages into NGSI v2 and vice versa.\n-   The [Domibus](https://ec.europa.eu/cefdigital/code/projects/EDELIVERY/repos/domibus) Incubated Generic Enabler helps\n    users to exchange electronic data and documents with one another in a reliable and trusted way.\n-   The [Oliot](https://github.com/yalewkidane/FIWARE_EPCIS_Mediation_Gateway) Incubated Generic Enabler is a mediation\n    gateway which translates information from NGSI based platforms to [EPCIS based](https://www.gs1.org/epcis/epcis/1-1)\n    IoT platforms.\n\nFurther information can be found on dedicated pages linked to [IoT Agents](./iot-agents/README.md) and\n[Robotics](./robotics/README.md) and [Third-Party Systems](./third-party/README.md)\n\n### Context Processing, Analysis and Visualization\n\n[![](https://nexus.lab.fiware.org/repository/raw/public/badges/chapters/processing.svg)](./processing/README.md)\n[![](https://nexus.lab.fiware.org/repository/raw/public/badges/chapters/visualization.svg)](./processing/README.md)\n\nA number of Generic Enablers are available making it easier to process, analyze or visualize context information for the\npurpose of implementing the “smart behaviour” expected in any application:\n\n-   The [Wirecloud](https://github.com/Wirecloud/) Generic Enabler brings a powerful web mashup platform making it\n    easier to develop operational dashboards which are highly customizable by end users.\n-   The [FogFlow](https://github.com/smartfog/fogflow) Generic Enabler is a distributed execution framework to support\n    dynamic processing flows over cloud and edges.\n\nThe following is a list of Generic Enablers under incubation within the chapter:\n\n-   The [Perseo](https://github.com/telefonicaid/perseo-core/) Generic Enabler introduces Complex Event Processing (CEP)\n    defined using a rules-based system, enabling you to fire events which send HTTP requests, emails, tweets, SMS\n    messages etc.\n\nFurther information can be found on dedicated pages linked to\n[Context Processing, Analysis and Visualization](./processing/README.md)\n\n### Context Data/API Management, Publication and Monetization\n\n[![](https://nexus.lab.fiware.org/repository/raw/public/badges/chapters/api-management.svg)](./data-publication/README.md)\n[![](https://nexus.lab.fiware.org/repository/raw/public/badges/chapters/data-publication.svg)](./data-publication/README.md)\n[![](https://nexus.lab.fiware.org/repository/raw/public/badges/chapters/data-monetization.svg)](./data-publication/README.md)\n[![](https://nexus.lab.fiware.org/repository/raw/public/badges/chapters/security.svg)](./security/README.md)\n\nYou can implement secured access to components in the architecture of any “Powered by FIWARE” solution using Generic\nEnablers of the security chapter:\n\n-   The [Keyrock Identity Management](https://github.com/ging/fiware-idm) Generic Enabler brings support to secure and\n    private OAuth2-based authentication of users and devices, user profile management, privacy-preserving disposition of\n    personal data, Single Sign-On (SSO) and Identity Federation across multiple administration domains.\n-   The [Wilma PEP Proxy](https://github.com/ging/fiware-pep-proxy) Generic Enabler brings support of proxy functions\n    within OAuth2-based authentication schemas. It also implements PEP functions within an XACML-based access control\n    schema.\n-   The [AuthZForce PDP/PAP](https://github.com/authzforce/server) Generic Enabler brings support to PDP/PAP functions\n    within an access control schema based on the XACML standard.\n\nThe incorporation of components and features to support **Advanced Data Usage Control** have been introduced as part of\nFIWARE Release 7.7. For a summary of vision and current status of work in this area, please visit the usage control\npages found at: [https://github.com/ging/fiware-usage-control](https://github.com/ging/fiware-usage-control)\n\nThis area also contains a chapter for the publication and monetization of context data resources, available through the\ncore Orion Context Broker component of your platform:\n\n-   The [CKAN extensions](https://github.com/conwetlab/FIWARE-CKAN-Extensions) Generic Enabler brings a number of\n    add-ons enabling to extend current capabilities of the world-leading CKAN Open Data publication platform to allow\n    publication of datasets matching right-time context data, the assignment of access terms and policies to those\n    datasets and the assignment of pricing and pay-per-use schemas to datasets.\n-   The [Biz Framework](https://github.com/FIWARE-TMForum/Business-API-Ecosystem) Generic Enabler brings backend support\n    to Context API/Data monetization based on open TM Forum Business APIs.\n-   [Idra](https://github.com/OPSILab/Idra) is able to federate existing Open Data Management Systems based on\n    heterogeneous technologies (e.g. CKAN, SOCRATA, DKAN etc.) providing a single API and a standard metadata format\n    (DCAT-AP) to discover open datasets.\n\nThe following is a list of Generic Enablers under incubation within the area of API management, publication and\nmonetization:\n\n-   [APInf](https://github.com/apinf/platform) API Management Framework is a tool for API owners to manage their APIs.\n    It provides all the necessary features to run business with APIs and makes it easy for API consumers to find and\n    start using the standard APIs.\n-   [CoatRack](https://github.com/coatrack/coatrack/) is a third-party backend-to-backend communications framework\n    facilitating API access, monitoring and monetization.\n-   [Endpoint-Auth-Service](https://github.com/FIWARE/endpoint-auth-service) transparently adds\n    authentication/authorization information to outgoing http-requests\n-   [Kong Plugins](https://github.com/FIWARE/kong-plugins-fiware) extends the functionality of the\n    [Kong](https://github.com/kong/kong) API Gateway to cover additional PEP scenarios applicable to context data\n    sharing\n\nThe following is a list of Generic Enablers under incubation within the area of Security:\n\n-   [Keystone SPASSWORD](https://github.com/telefonicaid/fiware-keystone-spassword) is an OpenStack Keystone extension\n    that enables extra security checks over user passwords\n-   [FIWARE TRUE Connector](https://github.com/Engineering-Research-and-Development/fiware-true-connector) enables\n    trusted data exchange in order for context brokers to be able to become an active part of an\n    [International Data Spaces](https://internationaldataspaces.org/) (IDS) Ecosystem\n-   [Steelskin PEP](https://github.com/telefonicaid/fiware-pep-steelskin) is a PEP proxy meant to secure independent\n    FIWARE components, by intercepting every request sent to the component, validating it against an Access Control\n    component such as Keypass\n-   [Keypass](https://github.com/telefonicaid/fiware-keypass) is multi-tenant XACML server with PAP and PDP\n    capabilities.\n-   [Keystone SCIM](https://github.com/telefonicaid/fiware-keystone-scim) is an OpenStack Keystone extension that\n    enables the management of User, Groups and Roles using the\n    [SCIM v1.1](https://developer.okta.com/docs/reference/scim/scim-11/) standard\n-   [Keystone SPASSWORD](https://github.com/telefonicaid/fiware-keystone-spassword) is an OpenStack Keystone extension\n    that enables extra security checks over user passwords\n-   [Anubis](https://github.com/orchestracities/anubis) is an RBAC Policy Execution Point that makes easier to reuse security\n    policies across different services\n-   [Trusted Issuers List Service](https://github.com/FIWARE/trusted-issuers-list) provides an EBSI Trusted Issuers Registry\n    implementation to act as the Trusted-List-Service in the DSBA Trust and IAM Framework.\n-   [DSBA PDP](https://github.com/FIWARE/dsba-pdp) is a Policy-Desicion Point, evaluating Json-Web-Tokens\n    containing VerifiableCredentials in an DSBA-compliant way. It also supports the evaluation in the context of i4Trust.\n-   [VC-Verifier](https://github.com/FIWARE/VCVerifier) provides the necessary endpoints to offer SIOP-2/OIDC4VP\n    compliant authentication flows. It exchanges VerfiableCredentials for JWT, that can be used for authorization and authentication\n-   [Keycloak VC-Issuer](https://github.com/FIWARE/keycloak-vc-issuer) is a plugin for Keycloak to support SIOP-2/ OIDC4VP\n    clients and issue VerifiableCredentials through the OIDC4VCI-Protocol to compliant wallets.\n-   [Credentials Config Service](https://github.com/FIWARE/credentials-config-service) manages and provides information about\n    services and the credentials they are using. It returns the scope to be requested from the wallet per service and the credentials\n    and issuers that are considered to be trusted for a certain service.\n-   [Trusted Issuers Registry](https://github.com/FIWARE/trusted-issuers-registry) provides both an EBSI Trusted Issuers\n    Registry implementation and an iShare implementation.\n\nFurther information can be found on dedicated pages linked to [Context Data/API Management](./api-management/README.md),\n[Publication and Monetization](./data-publication/README.md) and [Security](./security/README.md)\n\n### Deployment Tools\n\n![FIWARE Catalogue](https://nexus.lab.fiware.org/repository/raw/public/badges/chapters/deployment-tools.svg)\n\nMost FIWARE components are available as [Docker Images](https://hub.docker.com/u/fiware), direct links can be found\nwithin the descriptions of each generic enabler. A `docker-compose.yml` may also be available within the GitHub\nrepository, but these should only be used in development environments. For fully scalable production-ready instances of\nFIWARE Generic Enablers please refer to the repository holding the FIWARE\n[Helm Chart recipes](https://github.com/FIWARE/helm-charts/) or find FIWARE Helm Chart receipes directly on\n[ArtifactoryHub](https://artifacthub.io/packages/search?page=1\u0026ts_query_web=fiware)\n\n## Data Spaces\n\nFIWARE brings the essential building blocks helping to create Data Spaces enabling access and share of data in an\neffective and trustworthy manner. The open source nature of FIWARE technologies foster creation of these data spaces as\nfederated infrastructures where multiple providers can be involved and not just a few players. FIWARE is bringing today\nmature technologies, compatible with IDS and CEF Building Blocks, that may accelerate the delivery of data spaces to the\nmarket and the materialization of initiatives like GAIA-X in Europe.\n\nThe concrete selection of FIWARE components proposed as building blocks for the creation of Data Spaces can be found on\ndedicated pages linked to [FIWARE for Data Spaces](./data-spaces).\n\n## Management of FIWARE Releases\n\nThe individual components within the FIWARE catalogue are free to make\n[semantic versioned](https://semver.org/spec/v2.0.0.html) releases at any time. Additionally, a labelling of the whole\nFIWARE catalogue takes place at regular intervals where all components are collected together and a FIWARE label added\naccording to a set of\n[well-defined rules](https://fiware-requirements.readthedocs.io/en/latest/GE_Requirements/#software-releases). The\nFIWARE catalogue release schedule follows a strict\n[timetable](https://fiware-requirements.readthedocs.io/en/latest/release/index.html). Versions of components with the\nsame FIWARE release label should be completely interoperable and work nicely with each other.\n\n| :dart: \u0026nbsp; [Roadmap](./roadmap.md) | :rocket: \u0026nbsp; [Release Notes](https://github.com/FIWARE/catalogue/releases) |\n| ------------------------------------- | ----------------------------------------------------------------------------- |\n\n\nAs well as source-code repositories and binaries, relevant components are available as container registry images and Helm-chart\nrecipes for Kubernetes. Smart Data Models for NGSI-v2 and NGSI-LD help to define harmonised representation formats and\nsemantics that will be used by applications both to consume and to publish data.\n| ![](https://nexus.lab.fiware.org/repository/raw/public/badges/docker/fiware.svg)\u003cbr\u003e[Docker Hub](https://hub.docker.com/u/fiware) | ![](https://img.shields.io/badge/quay.io-fiware-grey?logo=red%20hat\u0026labelColor=EE0000)\u003cbr\u003e[quay.io](https://quay.io/organization/fiware) | ![](https://img.shields.io/endpoint?url=https://artifacthub.io/badge/repository/fiware)\u003cbr\u003e[Artifact Hub](https://artifacthub.io/packages/search?repo=fiware) | :globe_with_meridians:\u003cbr\u003e [Helm Charts](https://github.com/FIWARE/helm-charts/) | \u003cimg src=\"https://json-ld.org/favicon.ico\" align=\"center\" height=\"25\"\u003e \u003cbr\u003e [Smart Data Models](https://smartdatamodels.org) |\n| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | --- | --- |\n\n\n## Testing\n\nFIWARE is ready to work in industrial environments. A continuous quality assurance process is running to warranty the\nlevel of reliability in FIWARE Generic Enablers. Following the energy labelling system applied by European Union for\ndevices, each Generic Enabler is assigned with an overall label in the Catalogue (A+++, A++, A+, A, B, C) according to\nthe obtained results in testing different aspects.\n\nA testing method has been defined to conduct documentation verification, functional tests (verification of Generic\nEnablers specifications and APIs testing) and non-functional tests such as performance, stability and scalability. The\ntests are executed for every new version of the Generic Enablers, providing valuable insights to the Generic Enabler\nowners for improving the next Generic Enabler release.\n\nAll the tests can be conducted by anyone since the files for defining and running the tests have been published in an\nopen source repository.\n\nFull details of the test results can be found on the\n[FIWARE site](https://www.fiware.org/developers/qa-labeling-of-fiware-components/) - a summary of the test results is\npresented for each enabler within the submodules below.\n\nMature Generic Enablers have been thoroughly tested and have already demonstrated useful role accepted within the FIWARE\nframework. Incubated Generic enablers (annotated with :seedling:) have also been tested, but are still in the process of\nmaturing to full acceptance with the FIWARE system. Recent applicants to FIWARE (annotated with :new:) are new to FIWARE\nand will undergo testing in the forthcoming release.\n\n## Willing to contribute your technology to FIWARE?\n\nThe application process for joining the FIWARE Initiative is described in the links below. To be adopted as a Generic\nEnabler within FIWARE, each open source component must fulfill a number of\n[contribution requirements](https://fiware-requirements.readthedocs.io), follow common\n[Open Source Best Practice](https://bestpractices.coreinfrastructure.org/en/signup) and sign-up to the harmonized FIWARE\n[Entity Contributor License Agreement](https://fiware.github.io/contribution-requirements/entity-cla.pdf). The technical\ndirection of FIWARE is governed by the FIWARE Technical Steering Committee (TSC).\n\nYou can contribute to FIWARE technically by different means: contributing code for a given FIWARE component, helping to\ndevelop tutorials/training material which are made freely available to developers, supporting QA activities or\nsupporting the operations of the FIWARE Lab.\n\n| :inbox_tray: \u003cbr\u003e [**Application Form**](https://docs.google.com/forms/d/e/1FAIpQLSdp_QkAG8p5XJK-WDB1xPNY9e4VCvNEJyxwugBvMI6uSPe3fA/viewform?c=0\u0026w=1) | :clipboard: \u003cbr\u003e [Contribution Requirements](https://fiware-requirements.readthedocs.io) | \u003cimg src=\"https://fiware.github.io/catalogue/img/fiware-emoji.png\" height=\"20px\" width=\"20px\"/\u003e :heavy_plus_sign: :computer:\u003cbr\u003e [Entity CLA](https://fiware.github.io/contribution-requirements/entity-cla.pdf) | :wrench: \u003cbr\u003e [Active Contributors](https://docs.google.com/forms/d/e/1FAIpQLSfYfHWqE54jmeUR_xLMyRdQ-QxyZ92CNskUiRT5MQsiRp95XA/viewform?c=0\u0026w=1) | \u003cimg src=\"https://fiware.github.io/catalogue/img/fiware-emoji.png\" height=\"20px\" width=\"20px\"/\u003e :heavy_plus_sign: :bust_in_silhouette:\u003cbr\u003e [Individual CLA](https://fiware.github.io/contribution-requirements/individual-cla.pdf) |\n| ----------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n\n\n## License\n\n[License: AGPL-3.0](LICENSE) © 2018-2023 FIWARE Foundation e.V.\n\nThe FIWARE Catalogue includes additional submodules which have been obtained under license - check the `README` of each\nsubmodule for more details. Some of these elements are available under a more permissive license than Affero General\nPublic License.\n\nAdditional permission is given to reproduce the texts found within the root project under the Creative Commons\n[CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/) License.\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cstrong\u003eFurther information on the use of the GPL or AGPL open source license\u003c/strong\u003e\u003c/summary\u003e\n\n### Some FIWARE Components are distributed under GPL or AGPL open source licenses … Is it safe for me to use?\n\nAbsolutely. Issues with GPL (or AGPL) licenses are mostly related with the fact that different people assign different\ninterpretations on the meaning of the term “derivate work” used in these licenses. Due to this, some people understand\nthat there is a risk in just using software under GPL or AGPL licenses (even without modifying it).\n\nIn order to avoid any issue, FIWARE Generic Enabler owners who have decided to release their software using a GPL or\nAGPL license are required to make a public statement that states:\n\n\u003e Please note that software derived as a result of modifying the source code of this software in order to fix a bug or\n\u003e incorporate enhancements is considered a derivative work of the product. Software that merely uses or aggregates (i.e.\n\u003e links to) an otherwise unmodified version of existing software is not considered a derivative work.\n\nThe public statement above is aimed at giving users confidence they can use FIWARE components even if they have been\nlicensed under a copyleft license without this requiring that their applications have to be released as open source. The\nFIWARE Foundation has sought legal advice regarding this statement and has been told that incorporation of this\nparagraph is valid for this purpose as per the report produced by Across Legal/ID law partners (see\n[summary report](https://fiware.github.io/contribution-requirements/opinion-summary.pdf)).\n\nThis means that there is absolute no risk that you are forced to release the software that you may have developed using\nFIWARE Generic Enablers under a GPL, AGPL or any other open source license.\n    \n\u003c/details\n","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ffiware%2Fcatalogue","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Ffiware%2Fcatalogue","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ffiware%2Fcatalogue/lists"}