89
results
How to
  • s4city - SAREF extension for Smart City
    https://saref.etsi.org/saref4city/
    This ontology extends the SAREF ontology for the Smart City domain. This work has been developed in the context of the STF 534 (https://portal.etsi.org/STF/STFs/STFHomePages/STF534.aspx), which was established with the goal to create three SAREF extensions, one of them for the Smart City domain. @en
  • pubsub - Eccenca Publish-Subscribe Vocabulary
    https://vocab.eccenca.com/pubsub/
    The eccenca Publish-Subscribe Vocabulary defines concepts and relations to create statements about publishers, subscribers and their subscriptions in a Publish-Subscribe environment based on the PubSubHubbub Core 0.4 specification. @en
  • 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
  • arco - Core Ontology (ArCo network)
    https://w3id.org/arco/ontology/core
    The Core module represents general-purpose concepts orthogonal to the whole network, which are imported by all other ontology modules (e.g. part-whole relation, classification). @en
  • 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
  • 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