Linked Open Vocabularies

scovo - The Statistical Core Vocabulary

http://vocab.deri.ie/scovo

A vocabulary for representing statistical data on the Web. Note :The SCOVO vocabulary is deprecated. We strongly advise to use the Data Cube Vocabulary instead. @en

incident - Vocabulary to describe incident response by emergency services

http://vocab.resc.info/incident

Vocabulary to describe the response to a incident by emergency services. This is NOT intended to describe the incident itself, it describes the response @en

vrank - Vocabulary for Ranking

http://vocab.sti2.at/vrank

The Vocabulary for Ranking (vRank) is an RDF Schema vocabulary for materializing ranking computations. @en

ceon-processODP - Circular Economy Ontology Network (CEON) - Process ODP

http://w3id.org/CEON/ontology/processODP/

A core ODP of the CEON ontology network, defining aspects of the process concept. @en

ceon-plan - Circular Economy Ontology Network (CEON) - Plan Module

http://w3id.org/CEON/ontology/plan/

The Plan module of CEON (Circular Economy Ontology Network). @en

ceon-process - Circular Economy Ontology Network (CEON) - Process Module

http://w3id.org/CEON/ontology/process/

The Process module of CEON (Circular Economy Ontology Network). @en

ioc - IOC: Internet of Construction Ontology

http://w3id.org/ioc

The Internet of Construction Ontology (IoC) construction process ontology is intended to represent a comprehensive solution of how processes in the construction industry can be modelled. Due to the iterative nature of creating an ontology, the construction process ontology presented here can at best be considered a working state at the time of publication. Our approach emphasizes the simplest and most comprehensive mapping possible, which is only extended based on insights from practical use when otherwise compelling limitations in usability and applicability arise. Thus, the extension and refinement of the developed construction process ontology strongly depends on the integration of further areas of the construction value chain and the connection of further domain ontologies. @en

dt - Data Template (DT) Ontology

http://w3id.org/dt

The Data Template (DT) Ontology is based on concepts and principles for creating templates from ISO 23387 and the associated XML data schema, which is currently under development. @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

dk - The Data Knowledge Vocabulary

http://www.data-knowledge.org/dk/

The Data Knowledge Vocabulary allows for a comprehensive description of data assets and enterprise data management. It covers a business data dictionary, data quality management, data governance, the technical infrastructure and many other aspects of enterprise data management. The vocabulary represents a linked data implementation of the Data Knowledge Model which resulted from extensive applied research. @en

sport - BBC Sport Ontology

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

A simple ontology for representing competitive sports events. @en

music - Music Vocabulary

http://www.kanzaki.com/ns/music

A vocabulary, or music ontology, to describe classical music and performances. Classes (categories) for musical works, events, instruments and performers, as well as related properties are defined. Make sure to distinguish musical works (e.g. Opera) from performance events (Opera_Event), or works (String_Quartette) from performer (StringQuartetEnsemble in this vocab), whose natural language terms are used interchangeblly. The present version experiments more precise model to describe a musical work, its representations (performances, scores, etc) and a musical event to present a representation (a concert). Includes 30 keys as individuals. @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

SAN - SAN (Semantic Actuator Network)

http://www.irit.fr/recherches/MELODI/ontologies/SAN

This ontology is intended to describe Semantic Actuator Networks, as a counterpoint to SSN definition of Semantic Sensor Networks. An actuator is a physical device having an effect on the world (see Actuator for more information). It is worth noticing that some concepts are imported from SSN, but not SSN as a whole. This is a design choice intended to separate as much as possible the definition on actuator from the definition of sensor, which are completely different concept that can be used independantly from each other. This ontology is used as a ontological module in IoT-O ontology. @en

onc - Open NEE Configuration Model

http://www.ics.forth.gr/isl/oncm/core

The Open NEE Configuration Model defines a Linked Data-based model for describing a configuration supported by a Named Entity Extraction (NEE) service. It is based on the model proposed in "Configuring Named Entity Extraction through Real-Time Exploitation of Linked Data" (http://dl.acm.org/citation.cfm?doid=2611040.2611085) for configuring such services, and allows a NEE service to describe and publish as Linked Data its entity mining capabilities, but also to be dynamically configured. @en

Patterns?:	type name both
Flatten?:	yes no

How to