71
results
How to
  • aeros - aerOS Continuum Ontology
    https://w3id.org/aerOS/continuum#
    Ontology for the orchestration of the aerOS continuum. @en
  • cocoon - Cloud Computing Services Ontology
    https://w3id.org/cocoon/v1.0
    Simple ontology for Cloud Computing Services. This ontology allows to define model of prices used in large cloud computing providers such as Google, Amazon, Azure, etc., including options for regions, type of instances, prices specification, etc. @en
  • dio - The Design Intent Ontology
    https://w3id.org/dio
    The scope of the DIO is the domain of design intent or design rationale that needs to be documented while undertaking the design of any artifact @en
  • dg - DINGO Ontology
    https://w3id.org/dingo/
    The DINGO ontology (Data Integration for Grant Ontology) defines the terms of the DINGO vocabulary and provides a machine readable extensible framework to model data relative to projects, funding, project and funding actors, and, notably, funding policies. It is designed to yield high modeling power and elasticity to cope with the huge variety in funding and project practices, which makes it applicable to many areas where funding is an important aspect: first of all research, but also the arts, cultural conservation, and many others. @en
  • dseco - The DNS Security Ontology
    https://w3id.org/dseco/ontology/
    The DNS Security Ontology (DSecO) project is a data model for representing and reasoning on Domain Name System (DNS) data. The ontology is developed using web technologies (e.g. RDF, OWL, SKOS) and is intended as a structure for realizing a DNS Knowledge Graph (KG) for administration and security assessment applications. The model has been developed in collaboration with operational teams, and in connection with third parties linked vocabularies. Alignment with third parties vocabularies is implemented on a per class or per property basis when relevant (e.g. with `rdfs:subClassOf`, `owl:equivalentClass`). Directions for direct instanciation of these vocabularies are provided for cases where implementing a class/property alignment is redundant. Alignment holds for the following vocabulary releases: - [ORG](https://www.w3.org/TR/vocab-org/) 0.8 - [UCO](https://github.com/ucoProject/uco) Release-0.8.0 @en
  • hpont - The Heat Pump Ontology (HPOnt).
    https://w3id.org/hpont
    The Heat Pump Ontology (HPOnt) aims to formalize and represent all the relevant information of Heat Pumps. The HPOnt has been developed as part of the REACT project which has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement no. 824395. @en
  • ctrl - CTRLont - An ontology to formally specify the control domain
    https://w3id.org/ibp/CTRLont
    CTRLont specifies concepts and relationships of control actors on a high level @en
  • ids - IDS Information Model
    https://w3id.org/idsa/core
    This ontology defines classes and properties for describing participants, infrastructure, data and services of the International Data Spaces (formerly known as Industrial Data Space). @en
  • otl - The Open Traffic Lights ontology
    https://w3id.org/opentrafficlights
    This ontology provides the terms necessary to describe the status of traffic lights. @en
  • ofo - Occupant Feedback Ontology
    https://w3id.org/ofo#
    The aim of the Occupant Feedback Ontology is to semantically describe passive and active occupant feedback and to enable integration of this feedback with linked building data. @en
  • pep - Process Execution ontology.
    https://w3id.org/pep/
    The process execution ontology is a proposal for a simple extension of both the [W3C Semantic Sensor Network](https://www.w3.org/TR/vocab-ssn/) and the [Semantic Actuator Network](https://www.irit.fr/recherches/MELODI/ontologies/SAN.owl) ontology cores. @en
  • rdfc - RDF Connect Ontology
    https://w3id.org/rdf-connect/ontology
    An ontology for describing programming language-specific runners, processors and pipelines in RDF-based data processing frameworks. @en
  • sbeo - SBEO: Smart Building Evacuation Ontology
    https://w3id.org/sbeo
    Smart Building Evacuation Ontology (SBEO) is an ontology that couples the information about any building with its occupants such that it can be used in many useful ways. For example, indoor localization of people, detection of any hazard, a recommendation of normal routes such as shopping or stadium seating routes, or safe and feasible emergency evacuation routes or both of them all together. The core SBEO covers the concepts related to the geometry of building, devices and components of the building, route graphs correspondent to the building topology, users' characteristics and preferences, situational awareness of both building (hazard detection, status of routes in terms of availability and occupancy) and users (tracking, management of groups, status in terms of fitness), and emergency evacuation. @en
  • rto - Rail Topology Ontology
    https://w3id.org/rail/topo#
    The Rail Topology Ontology models foundational rail topology concepts.. @en
  • todo - TODO: Task-Oriented Dialogue management Ontology
    https://w3id.org/todo
    With the aim of enhancing natural communication between workers in industrial environments and the systems to be used by them, TODO (Task-Oriented Dialogue management Ontology) has been developed to be the core of task-oriented dialogue systems. TODO is a core ontology that provides task-oriented dialogue systems with the necessary means to be capable of naturally interacting with workers (both at understanding and at ommunication levels) and that can be easily adapted to different industrial scenarios, reducing adaptation time and costs. Moreover, it allows to store and reproduce the dialogue process to be able to learn from new interactions. @en