Linked Open Vocabularies

fiesta-iot - FIESTA-IoT Ontology

http://purl.org/iot/ontology/fiesta-iot

The FIESTA-IoT ontology takes inspiration from the well-known Noy et al. methodology for reusing and interconnecting existing ontologies. To build the ontology, we leverage a number of core concepts from various mainstream ontologies and taxonomies, such as Semantic Sensor Network (SSN), M3-lite (a lite version of M3 ontology), WGS84, IoT-lite, Time, and DUL ontology. @en

fiesta-priv - FIESTA-Priv Ontology

http://purl.org/iot/ontology/fiesta-priv#

FIESTA-Priv Ontology @en

iottaxolite - The IoTTaxonomy-lite Taxonomy

http://purl.org/iot/vocab/iot-taxonomy-lite#

The IoT-Taxonomy-lite is adapted from M3-lite taxonomy. This taxonomy is refactored and defines many other concepts such as subclasses of Feature-of-Interest and Quality-of-Observation. @en

gufo - gUFO: A Lightweight Implementation of the Unified Foundational Ontology (UFO)

http://purl.org/nemo/gufo#

The objective of gUFO is to provide a lightweight implementation of the Unified Foundational Ontology (UFO) [1-5] suitable for Semantic Web OWL 2 DL applications. Intended users are those implementing UFO-based lightweight ontologies that reuse gUFO by specializing and instantiating its elements. There are three implications of the use of the term lightweight. First of all, we have employed little expressive means in an effort to retain computational properties for the resulting OWL ontology. Second, we have selected a subset of UFO-A [1, 2] and UFO-B [3] to include here. In particular, there is minimalistic support for UFO-B (only that which is necessary to establish the participation of objects in events and to capture historical dependence between events). Third, a lightweight ontology, differently from a reference ontology, is designed with the purpose of providing an implementation artifact to structure a knowledge base (or knowledge graph). This has driven a number of pragmatic implementation choices which are discussed in comments annotated to the various elements of this implementation. The 'g' in gUFO stands for gentle. At the same time, "gufo" is the Italian word for "owl". For the source repository, see: <https://github.com/nemo-ufes/gufo> @en

m3lite - The Machine-to-Machine Measurement (M3) Lite Ontology

http://purl.org/iot/vocab/m3-lite#

M3 lite taxonomy is designed for the FIESTA-IOT H2020 EU project. We refactor, clean and simplify the M3 ontology designed by Eurecom (Amelie Gyrard). M3 ontology lite is currently aligned with the quantity taxonomy used by several testbeds: SmartSantander (Spain), University of Surrey (United Kingdom), KETI (Korea) and Com4Innov (France). @en

cmo - Conceptual Model Ontology

http://purl.org/twc/ontologies/cmo.owl

An ontology to tie classes and properties to SKOS concepts @en

mv - MobiVoc: Open Mobility Vocabulary

http://schema.mobivoc.org/

Our goal is to significantly improve the data mobility between all stakeholders by providing a standardized vocabulary using Semantic Web technologies and ontologies. For the open vocabulary covering various mobility aspects we use RDF (Resource Description Framework) - a recommended specification of the World Wide Web Consortium (W3C) and the so-called lingua franca for the integration of data and web. We invite everyone who is interested to join our MobiVoc initiative and to participate in the development of the Open Mobility Vocabulary. @en

schema - Schema.org vocabulary

http://schema.org/

Search engines including Bing, Google, Yahoo! and Yandex rely on schema.org markup to improve the display of search results, making it easier for people to find the right web pages. @en

spt - SPITFIRE Ontology

http://spitfire-project.eu/ontology/ns

TheSPITFIRE Ontology (spt) is based on the alignment among Dolce+DnS Ultralite(dul), the W3C Semantic Sensor Network ontology (ssn) and the Event Model-F ontology (event). @en

dave - Data Value Vocabulary (DaVe)

http://theme-e.adaptcentre.ie/dave/dave.ttl

The Data Value Vocabulary (DaVe) is an extensible core vocabulary that allows user to use custom data value dimensions and metrics to characterise data value in a specific context. This flexibility allows for the comprehensive modelling of data value. As a data value model, DaVe allows users to monitor data value as it occurs within a data exploitation or value creation process (data value chain) @en

umbel - Upper Mapping and Binding Exchange Layer

http://umbel.org/umbel

UMBEL provides a general vocabulary of classes and predicates for describing domain ontologies, with the specific aim of promoting interoperability with external datasets and domains. @en

drm - Data Reference Model

http://vocab.data.gov/def/drm

A metamodel for government data @en

vocals - VoCaLS: A Vocabulary and Catalog for Linked Streams

http://w3id.org/rsp/vocals#

This ontology aims to model RDF streams, their metadata, and access endpoints for publishing and consuming these streams @en

bbccore - BBC Core Concepts

http://www.bbc.co.uk/ontologies/coreconcepts

The generic BBC ontology for people, places,events, organisations, themes which represent things that make sense across the BBC. This model is meant to be generic enough, and allow clients (domain experts) link their own concepts @en

crm - CIDOC Conceptual Reference Model

http://www.cidoc-crm.org/cidoc-crm/

This is the encoding approved by CRM-SIG in the meeting 21/11/2012 as the official current version for the CIDOC CRM namespace. Note that this is NOT a definition of the CIDOC CRM, but an encoding derived from the authoritative release of the CIDOC CRM v5.0.4 on http://www.cidoc-crm.org/official_release_cidoc.html @en

Patterns?:	type name both
Flatten?:	yes no

How to