60
results
How to
  • s4ener - SAREF4EE: the EEbus/Energy@home extension of SAREF
    https://saref.etsi.org/saref4ener/
    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
  • 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
  • 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
  • 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
  • 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
  • tddm - TODODM: Dialogue Management Module for Task-Oriented Dialogue management Ontology (TODO)
    https://w3id.org/todo/tododm
    Module for dialogue process and system output management. @en
  • tddt - TODODT: Dialogue Tracing Module for Task-Oriented Dialogue management Ontology (TODO)
    https://w3id.org/todo/tododt
    Module for dialogue tracing. @en
  • km4c - km4city, the DISIT Knowledge Model for City and Mobility
    http://www.disit.org/km4city/schema
    A Knowledge Model to describe a smart city, that interconnect data from infomobility service, Open Data and other source @en
  • lifecycle - IoT-Lifecycle
    http://www.irit.fr/recherches/MELODI/ontologies/IoT-Lifecycle
    This ontology is a specialization of the lifecycle vocabulary (http://purl.org/vocab/lifecycle/schema) meant to be used in the context of IoT. It is used as a module in the IoT core domain ontology IoT-O (www.irit.fr/recherches/MELODI/ontologies/IoT-O). IoT-Lifecycle adds a specific state definition (ParametrizedState) and a specific transition (Update) that is useful to model actuators. @en
  • ioto - IoT-O
    http://www.irit.fr/recherches/MELODI/ontologies/IoT-O
    IoT-O is a core domain Internet of Things ontology. It is intended to model horizontal knowledge about IoT systems and applications, and to be extended with vertical, application specific knowledge. It is constituted of different modules : - A sensing module, based on W3C's SSN (http://purl.oclc.org/NET/ssnx/ssn) - An acting module, based on SAN (http://www.irit.fr/recherches/MELODI/ontologies/SAN) - A service module, based on MSM (http://iserve.kmi.open.ac.uk/ns/msm/msm-2014-09-03.rdf) and hRest (http://www.wsmo.org/ns/hrests) - A lifecycle module, based on a lifecycle vocabulary (http://vocab.org/lifecycle/schema-20080603.rdf) and an iot-specific extension (http://www.irit.fr/recherches/MELODI/ontologies/IoT-Lifecycle) - An energy module, based on powerOnt (ttp://elite.polito.it/ontologies/poweront.owl) IoT-O developping team also contributes to the oneM2M IoT interoperability standard. @en
  • ccsla - Service Level Agreement for Cloud Computing
    http://cookingbigdata.com/linkeddata/ccsla
    Service Level Agreement for Cloud Computing Services. This ontology allows to define model of SLA/SLO used in large cloud computing providers such as Amazon, Azure, etc., including terms, claims, credit, compensations, etc @en
  • cci - Ontology for Cloud Computing instances
    http://cookingbigdata.com/linkeddata/ccinstances
    Ontology for Cloud Computing Instances. Instance are classes of VM that comprise varying combinations of CPU, memory, storage, and networking capacity. This ontology allows to define the instantiation model of MVs used in large cloud computing providers such as Amazon, Azure, etc. @en
  • trao - Transport Administration Ontology
    http://linkeddata.finki.ukim.mk/lod/ontology/tao#
    Transport Administration Ontology (TAO) for describing data from Swedish Transport Administration Web site. @en
  • kees - KEES Ontology
    http://linkeddata.center/kees/v1
    KEES (Knowledge Exchange Engine Schema ) ontology describes a knowledge base configuration in terms of ABox and TBox statements together with their accrual and reasoning policies. This vocabulary is designed to drive automatic data ingestion in a graph database according KEES and Linked (Open) Data principles. @en