122
results
-
Web Of Trust (wot) RDF vocabulary, described using W3C RDF Schema and the Web Ontology Language. @en
-
An ontology suitable for describing forms, sequences in widgets @en
-
Solid terms @en
-
Decision-making is a process that can result in some decision and decision is a situation of indicating one of the considered options. Decision Ontology provides means for precise distinguishing and distinct treatment of these two aspects. @en
-
APCO is an ontology that allows the description of public procurement terms @en
-
The AIRS Linked Open Vocabulary is a way to describe human services information and referral (I&R) concepts. AIRS is the Alliance of Information and Referral Services (airs.org), which possesses over 1,000 member agencies primarily in the United States and Canada. The AIRS LOV is based on the AIRS XML Schema, available at: https://airs-xml.googlecode.com/hg/tags/3.1/airs.xsd @en
-
The Smart Appliances REFerence (SAREF) ontology is a shared model of consensus that facilitates the matching of existing assets (standards/protocols/datamodels/etc.) in the smart appliances domain. The SAREF ontology provides building blocks that allow separation and recombination of different parts of the ontology depending on specific needs. @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
-
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
-
Ontology for the orchestration of the aerOS continuum. @en
-
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
-
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
-
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
-
The Data Privacy Vocabulary (DPV) provides terms (classes and properties) to represent information about processing of personal data, for example - purposes, processing operations, personal data, technical and organisational measures. @en
-
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