Linked Open Vocabularies

eclap - ECLAP, Performing Arts Vocabulary

http://www.eclap.eu/schema/eclap/

The ECLAP vocabulary provide classes and properties for the description of multimedia content related with performing arts. @en

gn - The Geonames ontology

http://www.geonames.org/ontology

The Geonames ontology provides elements of description for geographical features defined in the geonames.org data base @en

mod - MOD: Metadata for Ontology Description and publication

http://www.isibang.ac.in/ns/mod

This specification describes MOD, a metadata vocabulary to describe and publish ontologies @en

ivoam - Messengers

http://www.ivoa.net/rdf/messenger

A vocabulary of particles used for observations in astronomy. This list started its existence as the controlled vocabulary for VODataService's vs:Waveband type; the machine-readable identifiers are in upper case for backwards compatibility. @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

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

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

oae - Open NEE Model

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

The Open NEE Model defines an extension of the Open Annotation Data Model (http://www.openannotation.org/spec/core) that allows describing in RDF the result of a Named Entity Extraction (NEE) process, enabling thereby an application to run advanced (SPARQL) queries over the annotated data. The model also exploits the Open NEE Configuration Model (http://www.ics.forth.gr/isl/oncm) for relating the output of a NEE process with an applied configuration (serving provenance information to the output of the entire NEE process). @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

identity - Ontology of digital identity.

http://www.identity.org/ontologies/identity.owl

v.2.0 based on P3P1.0 Specification http://www.w3.org/TR/P3P/ @en

whois - Who's who description vocabulary

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

A vocabulary to describe a person's profile and history @en

lexinfo - LexInfo Ontology

http://www.lexinfo.net/ontology/2.0/lexinfo

Version 2.0 of LexInfo Ontology, based on Lemon @en

semio - Semio, an ontology of signs

http://www.lingvoj.org/semio.rdf

A vocabulary to describe signs in a semiotic approach @en

dtype - Datatype Ontology

http://www.linkedmodel.org/schema/dtype

The ontology 'dtype' provides a specification of simple data types such as enumerations. These are needed in support of the conversion of XML Schemas and UML Models to OWL. Codelists are also defined in 'dtype'. @en

Patterns?:	type name both
Flatten?:	yes no

How to