141
results
-
OPMW is a OPMV profile to model the executions and definitions of scientific workflows. @en
-
Defines types of connectivity used in communication and bearer services accessible in certain connectivity. @en
-
The Measurement Ontology is an ontology in which measurements may be rendered @en
-
This ontology covers the domain of security in the field of mobile applications. @en
-
ML-Schema is a collaborative, community effort with a mission to develop, maintain, and promote standard schemas for data mining and machine learning algorithms, datasets, and experiments @en
-
This ontology describes sensors, actuators and observations, and related concepts. It does not describe domain concepts, time, locations, etc. these are intended to be included from other ontologies via OWL imports. @en
-
Web Of Trust (wot) RDF vocabulary, described using W3C RDF Schema and the Web Ontology Language. @en
-
This ontology is based on the SSN Ontology by the W3C Semantic Sensor Networks Incubator Group (SSN-XG), together with considerations from the W3C/OGC Spatial Data on the Web Working Group. @en
-
This document describes functions which transform HTTP representations, i.e., the actual literal payloads of HTTP messages. @en
-
An Ontology for representing EDIFACT Messages. @en
-
This ontology extends the SAREF ontology for the water domain. This work has been developed in the context of the STF 566, which was established with the goal to create three SAREF extensions, one of them for the water domain. @en
-
This is the extension of SAREF for the EEBus and Energy@Home project. The documentation of SAREF4EE is available at http://ontology.tno.nl/SAREF4EE_Documentation_v0.1.pdf. SAREF4EE represents 1) The configuration information exchanged in the use case 'Remote Network Management' according to the EEBus Technical Report, Protocol Specification- Remote Network Management, version 1.0.0.2, 2015-09-19; 2) The scheduling information about power sequences exchanged in the use cases Appliance scheduling through CEM and remote start' and 'Automatic cycle rescheduling', according to the message structures described in General Message Structures, version 0.1.1, 2015-10-07; 3) The monitor and control information exchanged in the use case 'Communicate appliance status and info on manually planned cycles', according to the monitoring and control part of the Energy@Home Data Model, version 1.0; and 4) the event-based data exchanged in the use case 'Demand Response', according to General Message Structures, version 0.1.1, 2015-10-07. @en
-
This ontology extends the SAREF ontology for the environment domain, specifically for the light pollution domain, including concepts like photometers, light, etc. @en
-
The Crime Event Model is an ontology for the representation of crime events extracted from local newspapers. It could be employed for Crime Analysis purposes: extracting crime information from newspapers and enriching them with proper machine-readable semantics is a critical task to help law enforcement agencies at preventing crime, supporting criminal investigations and evaluating the action of law enforcement agencies themselves. The model is based on the fundamental 5W1H journalistic questions, that are Who?, What?, When?, Where?, Why? and How?. Another important requirement was the attempt to exploit existing knowledge graphs and ontologies such as the Simple Event Model (SEM) Ontology and the Schema.org data model for interoperability and interconnection. @en
-
This document is a vocabulary to describe compound measures, i.e. measures with several metric or item that are organized with serveral dimensions. The description of such a measure relies on a Tree-Structure of Requirement (TSoR): a set of requirements structured hierarchicaly with analysis element. A TSoR represents the main measure. Several information may be added to explicitely indicate how the overall score on the measure should be calculated based on the hierarchy, relative importance of the node of the hierarchy and an aggregation function. The measure can be described completely and unambiguously from the organisation to the requirements and the implementation. @en