143
results
-
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
-
PROV extension for linking Plans and parts of plans to their respective executions. @en
-
OWL ontology for the IFC conceptual data schema and exchange file format for Building Information Model (BIM) data @en
-
The Ontology for Property Management (OPM) extends the concepts introduced in the Smart Energy Aware Systems (SEAS) Evaluations ontology. @en
-
This ontology describes the components, failures, sensors, and events related to offshore wind platforms. @en
-
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
-
This ontology defines: - a set of subclasses of `seas:Evaluation` to better interpret evaluations of quantifiable properties. - a set of sub properties of `seas:hasProperty` to qualify time-related properties. @en
-
The SEAS Device ontology defines `seas:Device` as physical system that are designed to execute one or more procedures that involve the physical world. @en
-
The SEAS Forecasting ontology extends the [Procedure Execution ontology (PEP)](https://w3id.org/pep/) @en
-
This ontology defines batteries and their state of charge ratio property. @en
-
The REACT ontology aims to represent all the necessary knowledge to support the achievement of island energy independence through renewable energy generation and storage, a demand response platform, and promoting user engagement in a local energy community. The REACT ontology 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
-
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
-
Quality, architecture, and process are considered the keystones of software engineering. ISO defines them in three separate standards. However, their interaction has been poorly studied, so far. The SQuAP model (Software Quality, Architecture, Process) describes twenty-eight main factors that impact on software quality in banking systems, and each factor is described as a relation among some characteristics from the three ISO standards. Hence, SQuAP makes such relations emerge rigorously, although informally. SQaAP-Ont is an OWL ontology that formalises those relations in order to represent and reason via Linked Data about software engineering in a three-dimensional model consisting of quality, architecture, and process characteristics. @en
-
A vocabulary specifying concepts and structures needed to represent different data cubes needed for the Smart Readiness Indicator. @en
-
The Gouda Time Machine Ontology describes the geo-temporal classes and properties used within the Gouda Time Machine. @en