Linked Open Vocabularies

dfc-t - A common vocabulary for digital food platforms (Technical Part)

http://static.datafoodconsortium.org/ontologies/DFC_TechnicalOntology.owl

A common vocabulary for digital food platforms (Technical Part) @en

swrc - Semantic Web for Research Communities

http://swrc.ontoware.org/ontology-07

An ontology for modeling entities of research communities such as persons, organisations, publications (bibliographic metadata) and their relationship @en

vivo - VIVO Core Ontology

http://vivoweb.org/ontology/core

An ontology of academic and research domain, developed in the framework of the VIVO project @en

m4i - Metadata4Ing: An ontology for describing the generation of research data within a scientific activity.

http://w3id.org/nfdi4ing/metadata4ing#

Metadata4Ing defines classes and properties or reuses such classes and properties from other ontologies to describe research processes and research data management in NFDI4Ing. New concepts and properties are located in the namespace of Metadata4Ing. Metadata4Ing does not import complete ontologies for the sake of relevance, readability, understandability and usability by and for engineers. Instead, it tries to make re-use of existing identifiers for classes and properties by re-using all or a relevant subset of the axioms from the original ontology. These statements have been extracted in different ways, e.g. by using Protégé tools importing an ontology and copying axioms of relevant items to Metadata4Ing or by download from data services or raw files of ontologies and manual copypasting. In some cases there was a need to extend or modify the original set of statements about an entity, e.g. because labels and definitions were expressed with a different owl:AnnotationProperty than the rest of Metadata4Ing, or because a skos:preflabel or a skos:definition in any of the languages we would like to support was missing. Any editorial changes on elements from external ontologies are declared in Metadata4Ing by an annotation with skos:editorialNote at item-level. To get the original set of statements we encourage to visit the original namespace of the respective item. Metadata4Ing reuses elements from the following ontologies: - BIBO = Bibliographic Ontology - BIRO = Bibliographic Reference Ontology - DCAT = Data Catalog - DCTERMS = Dublin Core Terms - FOAF = Friend of a Friend - OWL = Web Ontology Language - PROV = Provenance Namespace - QUDT = Quantities, Units, Dimensions and Types - RDF = Resource Description Framework - RDFS = RDF Schema - SCHEMA = schema.org - SKOS = Simple Knowledge Organization System - SSN = Semantic Sensor Network Ontology - VANN = Vocabulary for Annotating vocabulary descriptions - XSD = XML Schema Definition - EMMO = European Materials and Modelling Ontology - BFO = Basic Formal Ontology - RO = Relation Ontology - PIMS-II = PIMS Interoperability Infrastructure - D-SI = Digital System of Units @en

akts - AKT Support Ontology

http://www.aktors.org/ontology/support

The AKT Reference Ontology has been designed to support the AKT-2 demonstrator ("AKTive Portal"), and subsequent activities @en

roh - The ASIO ontology

http://w3id.org/roh

An ontology to address the Research Management of the CRUE's Spanish University System (Sistema Universitario Español) by applying an encompassing model not only capable of addressing the universities of the CRUE but also more belonging to the European Union. @en

marl - Marl Ontology Specification

http://www.gsi.dit.upm.es/ontologies/marl/ns

Marl is a standardised data schema designed to annotate and describe subjective opinions expressed on the web or in particular Information Systems. @en

onyx - Onyx Emotion Ontology

http://www.gsi.dit.upm.es/ontologies/onyx/ns

Onyx is a vovabulary designed designed to annotate and describe the emotions expressed by user-generated content on the web or in particular Information Systems. @en

vag - The Vagueness Ontology

http://www.essepuntato.it/2013/10/vagueness

The Vagueness Ontology (VO) allows one to specify vagueness characterisations of the TBox entities of an ontology. @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

seq - Sequence Pattern

http://www.ontologydesignpatterns.org/cp/owl/sequence.owl

Intended to represent sequence schemas. It defines the notion of transitive and intransitive precedence and their inverses. It can then be used between tasks, processes, time intervals, spatially locate objects, situations, etc. @en

infor - Information Realization

http://www.ontologydesignpatterns.org/cp/owl/informationrealization.owl

Allows designers to model information objects and their realizations. This allows to reason about physical objects and the information they realize, by keeping them distinguished. @en

odpart - Ontology Design Pattern Participation

http://www.ontologydesignpatterns.org/cp/owl/participation.owl

The basic participation pattern, without temporal indexing. It clones equivalent elements from DOLCE-UltraLite. @en

hdo - HelpDesk support Ontology

http://www.samos.gr/ontologies/helpdeskOnto.owl

Simple ontology developed for integration purposes. Describe helpdesk entities used to record support tickets for diagnosis and resolve purpuses. The ontology re-uses a) W3C ORG and REGORG ontologies, b) DUL upper ontology, and c) GoodRelations ontology. @en

gso - Generic Specific Ontology

http://www.w3.org/2006/gen/ont

Ontology for Relating Generic and Specific Information Resources @en

Patterns?:	type name both
Flatten?:	yes no

How to