130
results
-
nen2660- NEN 2660-2:2022 'Rules for information modelling of the built environment - Part 2: Practical configuration, extension and implementation of NEN 2660-1''Ontology which is a normative part of the Dutch NEN 2660-2 standard @en
-
The Ontology for Managing Geometry (OMG) is an ontology for describing geometry descriptions of objects. It provides means to support the application of multiple geometry descriptions of the same object as well as the description of the geometry evolution over time. The OMG is based the concepts introduced in the Ontology for Property Management (OPM) ontology. This ontology was created within the research project SCOPE, funded by the German Federal Ministry for Economic Affairs and Energy (BMWi). The initial version of the ontology (v0.0.1) is documented in: Wagner, Anna, Bonduel, Mathias, Pauwels, Pieter & Rüppel, Uwe(2019). Relating Geometry Descroptions to its Derivatives on the Web. In Proceedings of the European Conference on Computing in Construction (EC3 2019). Chania, Greece. @en
-
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
-
This vocabulary is version v0.1 of the ITEA2 Smart Energy Aware Systems project vocabulary. It enables the description of electricity measurements of a site using the Data Cube W3C vocabulary. @en
-
This ontology defines batteries and their state of charge ratio property. @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 Operating Ontology defines evaluations of operating features of interest. @en
-
This ontology defines proposed alignemnts with the QUDT ontology. @en
-
This ontology defines common evaluation interpretation concepts for statistics. @en
-
The System Ontology defines Systems, Connections between systems, and Connection Points at which systems may be connected. This ontology is then specialized for multiple domains. For example: - In electric energy: - power systems consume, produce, store, and exchange electricity; - power connections are where electricity flows between systems; - power connection points are plugs, sockets, or power busses. - In the electricity market: - players and markets are systems; - connections are contracts or transactions between two players, or between a player and a market; - connection points include offers and bids. @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 Trading Ontology defines concepts and relations to describe ownership, trading, bilateral contracts and market licenses: - players own systems and trade commodities, which have a price; - bilateral electricity contracts are connections between electricity traders at which they exchange electricity; - electricity markets are connections between electricity traders at which they exchange electricity, using a market license; - electricity markets can be cleared, and balanced; - evaluations can have a traded volume validity context @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
-
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
-
Module for Action (and Frame) modelling inside domain. @en