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
ccsla- Service Level Agreement for Cloud Computing
http://cookingbigdata.com/linkeddata/ccsla
Service Level Agreement for Cloud Computing Services. This ontology allows to define model of SLA/SLO used in large cloud computing providers such as Amazon, Azure, etc., including terms, claims, credit, compensations, 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
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
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
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
txn- TaxonConcept Ontology
http://lod.taxonconcept.org/ontology/txn.owl
This ontology and the related TaxonConcept data set mints identifiers that are tied to a specific species concept which can have several names and classifications. @en
edupro- EduProgression Ontology
http://ns.inria.fr/semed/eduprogression/
The EduProgression ontology formalizes the educational progressions of the French educational system, making possible to represent the existing progressions in a standard formal model, searchable and understandable by machines (OWL). @en
omnfed- Open-Multinet Upper Federation Ontology
http://open-multinet.info/ontology/omn-federation
This ontology defines concepts related to federation of internet infrastructures. @en
of- Open Fridge vocabulary
http://owlrep.eu01.aws.af.cm/fridge
Ontology for Open Fridge project @en
obo- Ontology for Biomedical Investigation
http://purl.obolibrary.org/obo/obi.owl
The Ontology for Biomedical Investigations (OBI) is build in a collaborative, international effort and will serve as a resource for annotating biomedical investigations, including the study design, protocols and instrumentation used, the data generated and the types of analysis performed on the data. This ontology arose from the Functional Genomics Investigation Ontology (FuGO) and will contain both terms that are common to all biomedical investigations, including functional genomics investigations and those that are more domain specific. @en
coll- Collections Ontology
http://purl.org/co
The Collections Ontology (CO) defines unordered collections (Set and Bag) and ordered collections (or List). This ontology has been inspired by the work "Putting OWL in Order: Patterns for Sequences in OWL" by Drummond et al. (OWL-ED 2006). @en
dpn- Data Provider Node ontology
http://purl.org/dpn
This ontology is being developed by CSIRO under the eReefs project for describing data provider nodes, web services available and datasets that are hosted by them. This ontology features a module for describing Datasets. It does not however describe geospatial, temporal, organisational or domain concepts as these are intended to be included from other ontologies via the imports statement. Other modules complementary to the DPN ontology are http://purl.org/dpn/dataset and http://purl.org/dpn/services. This version aligns DCAT and DC terms and imports DPN services. @en
coo- Car Options Ontology
http://purl.org/coo/ns#
The COO provides a vocabulary for exposing available configuration options for car models. It allows indicating choices that can be made as well as compatibility, dependency, and inclusion information. The ontology imports and extends the GoodRelations ontology for e-commerce @en