Linked Open Vocabularies

ccp - Vocabulary for prices options in Cloud Computing Services

http://cookingbigdata.com/linkeddata/ccpricing

Simple and direct pricing ontology for Cloud Computing Services. This ontology allows to define model of prices used in large cloud computing providers such as Amazon, Azure, etc., including options for regions, type of instances, prices specification, etc. @en

ccr - Vocabulary for Regions and Zones on Cloud Computing

http://cookingbigdata.com/linkeddata/ccregions

Ontology for the definition of regions and zones of availability on CloudComputing platforms and services. This ontology allows to define model of regions used in large cloud computing providers such as Amazon, Azure, etc. @en

cci - Ontology for Cloud Computing instances

http://cookingbigdata.com/linkeddata/ccinstances

Ontology for Cloud Computing Instances. Instance are classes of VM that comprise varying combinations of CPU, memory, storage, and networking capacity. This ontology allows to define the instantiation model of MVs used in large cloud computing providers such as Amazon, Azure, etc. @en

ebg - euBusinessGraph ontology

http://data.businessgraph.io/ontology#

The euBusinessGraph (`ebg:`) ontology represents companies, type/status/economic classification, addresses, identifiers, company officers (e.g., directors and CEOs), and dataset offerings. It uses `schema:domainIncludes/rangeIncludes` (which are polymorphic) to describe which properties are applicable to a class, rather than `rdfs:domain/range` (which are monomorphic) to prescribe what classes must be applied to each node using a property. We find that this enables more flexible reuse and combination of different ontologies. We reuse the following ontologies and nomenclatures, and extend them where appropriate with classes and properties: - W3C Org, W3C RegOrg (basic company data), - W3C Time (officer membership), - W3C Locn (addresses), - schema.org (domain/rangeIncludes and various properties) - DBpedia ontology (jurisdiction) - NGEO and Spatial (NUTS administrative divisions) - ADMS (identifiers), - FOAF, SIOC (blog posts), - RAMON, SKOS (NACE economic classifications and various nomenclatures), - VOID (dataset descriptions). This is only a reference. See more detail in the [EBG Semantic Model](https://docs.google.com/document/d/1dhMOTlIOC6dOK_jksJRX0CB-GIRoiYY6fWtCnZArUhU/edit) google document, which includes an informative description of classes and properties, gives examples and data provider rules, and provides more schema and instance diagrams. @en

vdpp - Vocabulary for Dataset Publication Projects

http://data.lirmm.fr/ontologies/vdpp

The Vocabulary of Dataset Publication Projects (VDPP) allows to represent the status of a dataset publication project. It is mainly based on the Provenance Vocabulary (PRV), the Dataset Provenance Vocabulary (VOIDP), the Vocabulary of Interlinked Datasets (VoID), and the Description of a Project (DOAP) vocabulary. @en

food - Food Ontology

http://data.lirmm.fr/ontologies/food

This ontology models the Food domain. It allows to describe ingredients and food products. Ontology used by the Open Food Facts dataset @en

dq - OWL representation of ISO 19115 (Geographic Information - Metadata - Data quality package)

http://def.seegrid.csiro.au/isotc211/iso19115/2003/dataquality

An OWL representation of parts of the Geographic Metadata model described in ISO 19115:2003 with Corrigendum 2006 - DQ Package @en

r4r - Relations for Reusing (R4R) Ontology

http://guava.iis.sinica.edu.tw/r4r

R4R is a light-weight ontology for representing general relationships of resource for publication and reusing. It asserts that a certain reusing context occurred and determined by its two basic relations, namely, isPackagedWith and isCitedBy. The isPackagedWith relation declares the resource is ready to be reused by incorporating License and Provenance information. The Cites relation is an exceptional to isCitedBy which occurs only two related objects cite each other at the same time. Five resource objects including article, data, code, provenance and license are major class concepts to represent in this ontology. The namespace for all R4R terms is http://guava.iis.sinica.edu.tw/r4r/ @en

dogont - Ontology Modeling for Intelligent Domotic Environments

http://elite.polito.it/ontologies/dogont.owl

The DogOnt ontology supports device/network independent description of houses, including both controllable and architectural elements. @en

eupont - EUPont: an ontology for End User Programming of the IoT

http://elite.polito.it/ontologies/eupont.owl

EUPont is an ontology to model high level rules for Internet of Things End User Programming (IoT-EUP). @en

kdo - The Knowledge Diversity Ontology

http://kdo.render-project.eu/kdo#

The Knowledge Diversity Ontology aims at providing a vocabulary that describes different dimensions of knowledge diversity of the Web. To support the representation of diversity information, the conceptual model of the Knowledge Diversity Ontology includes concepts and relations that were identified and modelled by focusing on real world scenarios in context of customer feedback, news, and Wikipedia opinion mining as well as content and sentiment analysis. @en

spfood - SmartProducts Food Domain Model

http://kmi.open.ac.uk/projects/smartproducts/ontologies/food.owl

Defines concepts and properties specific for the SmartProducts Philips use case (cooking domain). @en

pmlp - PML2 provenance ontology

http://inference-web.org/2.0/pml-provenance.owl

The provenance part of PML2 ontology. It is a fundamental component of PML2 ontology. @en

veo - Vehicle Emissions Ontology

http://linkeddata.finki.ukim.mk/lod/ontology/veo#

An ontology for describing vehicles and their emissions. @en

kees - KEES Ontology

http://linkeddata.center/kees/v1

KEES (Knowledge Exchange Engine Schema ) ontology describes a knowledge base configuration in terms of ABox and TBox statements together with their accrual and reasoning policies. This vocabulary is designed to drive automatic data ingestion in a graph database according KEES and Linked (Open) Data principles. @en

Patterns?:	type name both
Flatten?:	yes no

How to