| Full Name | Acronym | General Category | Purpose | Description | Relevant WP | Available Implementation(s) |
|---|---|---|---|---|---|---|
| Open Policy Agent | OPA | Policy-based control for cloud native environments | 3.3.3 | Alternatives: Pulumi Crossguard, Kyverno | ||
| Terminology Service | Dienst | Service that will be integrated in the FAIR-DS demonstrators | The Terminology Service of TIB – Leibniz Information Centre for Science and Technology and University Library is a single-point-of-entry web-service providing access to terms from generic and domain-specific controlled vocabularies and ontologies. TIB Central Terminology Service is the backbone of all the Terminology Services presented by TIB. It hosts and stores the terminologies of various research communities mainly through this web site. | 3.6 | https://github.com/TIBHannover/OLS | |
| Sovereign Cloud Stack | SCS | Modular Open Source Software Stack to provide Infra Mgmt, IaaS, CaaS, KaaS, PaaS. Standard implementation for GAIA-X compliant nodes and basic services. | 3.2 | https://github.com/SovereignCloudStack/ | ||
| SNOMED CT | Ontology | Terminology used by NFDI4Health | SNOMED CT based clinical information benefits individual patients and clinicians as well as populations while supporting evidence-based care. | 3.6 | ||
| LOINC | Terminology used by NFDI4Health | LOINC is a common language (set of identifiers, names, and codes) for identifying health measurements, observations, and documents. If you think of an observation as a "question" and the observation result value as an "answer." | 3.6 | |||
| ICD-10-GM | Terminology used by NFDI4Health | Die Internationale statistische Klassifikation der Krankheiten und verwandter Gesundheitsprobleme, 10. Revision, German Modification (ICD-10-GM) ist die amtliche Klassifikation zur Verschlüsselung von Diagnosen in der ambulanten und stationären Versorgung in Deutschland. | 3.6 | |||
| OrphaNet | Terminology used by NFDI4Health | Orphanet is the international reference knowledge base for rare diseases and orphan drugs. Orphanet provides freely-accessible information on rare diseases with the aim of helping improve the diagnosis, care and treatment of patients with rare diseases. | 3.6 | http://www.orphadata.org/cgi-bin/index.php#ontologies | ||
| Human Phenotype Ontology | HPO | Ontology | Terminology used by NFDI4Health | The Human Phenotype Ontology (HPO) provides a standardized vocabulary of phenotypic abnormalities encountered in human disease. Each term in the HPO describes a phenotypic abnormality, such as Atrial septal defect. | 3.6 | https://hpo.jax.org/app/download/ontology |
| Operationen- und Prozedurenschlüssel | OPS | Terminology used by NFDI4Health | The German procedure classification (Operationen- und Prozedurenschlüssel - OPS) is the official classification for the encoding of operations, procedures and general medical measures. The currently valid version is OPS 2021. | 3.6 | ||
| Unified Code for Units of Measure | UCUM | Terminology used by NFDI4Health | The Unified Code for Units of Measure (UCUM) is a code system intended to include all units of measures being contemporarily used in international science, engineering, and business. The purpose is to facilitate unambiguous electronic communication of quantities together with their units. The focus is on electronic communication, as opposed to communication between humans. A typical application of The Unified Code for Units of Measure are electronic data interchange (EDI) protocols, but there is nothing that prevents it from being used in other types of machine communication. UCUM support EDI protocols for the quantities and units in the domains of knowledge specified in ISO 80000 standards parts 2-14 above | 3.6 | ||
| OpenSCENARIO | Ontology | Terminology used by NFDI4Ing | 3.6 | |||
| OpenDRIVE | Ontology | Terminology used by NFDI4Ing | 3.6 | |||
| Coscine | Software | Plattform for research data management, especially metadata management and quota management | 3.5, 3.6 | |||
| GitLab | Software | Plattform used in AP 4.2 | GitLab is a complete DevOps platform delivered as a single application, fundamentally transforming the way development, security, ops, and product teams collaborate. Build, test, and deploy software faster with just one solution. | 4.2 | ||
| Metadata for Machines | M4M | Set of practices to implement machine readible FAIR metadata | Typically, the FAIRification process begins when a community of practice considers its domain-relevant metadata requirements and other policy considerations, and formulates these considerations as machine-actionable metadata components. These considerations can be guided in Metadata for Machines (M4M) Workshops. | 3.4 | ||
| FAIR Implementation Profile | FIP | Documentation guideline for Interfaces that provide FAIR Data | The re-usable metadata schemata produced in the M4M compose part of the larger FAIR Implementation Profile (FIP). | 3.4 | ||
| FAIR Data Point | FDP | Specification | Specification for FAIR data and metadata exchange based on existing (web) standards | A FAIR Data Point (sometimes abbreviated to FDP) is the realisation of the vision of a group of authors of the original paper on FAIR on how (meta)data could be presented on the web using existing standards, and without the need of APIs. A FAIR Data Point ultimately stores information about data sets, which is the definition of metadata. And just like the webserver in the WWW in the beginning of the 1990s brought the power of publishing text to anyone, a FAIR data point aims to give anyone the power of putting their own data on the web. The system is called a FAIR data point because it takes care of a lot of the issues that need to be taken care of to make data FAIR; especially with the metadata needed for Findability and Reusability, and a uniform open way of Accessing the data. The FAIR data point also addresses the Interoperability of the metadata it stores, but it leaves the Interoperability aspects for the data itself to the data provider. | 3.4, 3.6 | |
| Linked Data Platform | LDP | W3C Standard for exchange of Linked Data and Binary Data, likely to be used by NFDI4Ing | ||||
| DFN-AAI | AAI-Federation of German Higher Education and Research Facilities | 3.5 | ||||
| edugain-AAI | AAI-Federation of Worldwise Higher Education and Research Facilities | 3.5 | ||||
| Research Organization Registry | ROR | Registry with PIDs for Research Organizations | 3.5 | |||
| Open Researcher and Contributor ID | ORCID | Registry with PIDs for researchers, can be used as Open ID provider | 3.5 | |||
| IDSA Dataspace Connector | DSC | Software | Connector for participation in dataspaces | NOTE: The DSC will be migrated to the Eclipse Dataspace Connector in the future The Eclipse Dataspace Connector provides a framework for sovereign, inter-organizational data exchange. It will implement the International Data Spaces standard (IDS) as well as relevant protocols associated with GAIA-X. The connector is designed in an extensible way in order to support alternative protocols and integrate in various ecosystems. | 3 | https://github.com/International-Data-Spaces-Association/DataspaceConnector |
| Eclipse Dataspace Connector | EDC | Software | Connector for participation in dataspaces | The Eclipse Dataspace Connector provides a framework for sovereign, inter-organizational data exchange. It will implement the International Data Spaces standard (IDS) as well as relevant protocols associated with GAIA-X. The connector is designed in an extensible way in order to support alternative protocols and integrate in various ecosystems. | 3 | https://github.com/eclipse-dataspaceconnector/DataSpaceConnector |
| EOSC Datasets Minimum Information | EOSC-EDMI | Ontologie | Dataset metadata vocabulary used in EOSC | A minimum information metadata guideline to help users and services to find and access datasets reusing existing data models and interfaces. | 3.1 | |
| IDS Information Model | Ontologie | Information model for the International Data Spaces | 3.1 | https://github.com/International-Data-Spaces-Association/InformationModel/tree/develop/model |
