141
results
-
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
-
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
-
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
-
The ontology of the taxonomy "European Skills, Competences, qualifications and Occupations". The ontology considers three ESCO pillars (or taxonomy) and 2 registers. The three pillars are: - Occupation - Skill (and competences) - Qualification For the construction and use of the ESCO pillars, the following modelling artefacts are used: - Facetting support to specialize ESCO pillar concepts based on bussiness relevant Concept Groups (e.g. species, languages, ...) - Conept Groups, Thesaurus array and Compound terms (as detailed in ISO 25964) to organize faceted concepts - SKOS mapping properties to relate ESCO pillar concepts to concepts in other (external) taxonomies (e.g. FoET, ISCO88 and ISCO08. More mappings can be added in the future.) - Tagging ESCO pillar concepts by other (external) taxonomies (NUTS, EQF, NACE, ...) - Capture gender specifics on the labels of the ESCO pillar concepts - Rich ESCO concept relationships holding a description and other specific characteristics of the relation between two ESCO pillar concepts. ESCO maintains two additional registers: - Awarding Body - Work Context Awarding Bodies typically are referenced by ESCO qualifications. Occupations can have one or more work context. @en
-
Description of French National Assembly @en
-
Extension of the Org ontology to make it suitable for the Spanish common registry of public entities. @en
-
Ontology of the Chamber of Deputies of the Italian Parliament. @en
-
The ontology aims at modelling the data on cultural institutes or sites such as data regarding the agents that play a specific role on cultural institutes or sites, the sites themselves, the contact points, all multimedia files which describe the cultural institute or site and any other information useful to the public in order to access the institute or site. Moreover, the ontology represents events that can take place in specific cultural institutes or sites. @en
-
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
-
MARC relators are defined as both RDF properties and SKOS concepts @en
-
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
-
Transport Administration Ontology (TAO) for describing data from Swedish Transport Administration Web site. @en
-
An ontology for natural language terms description, including scripts, languages and meanings. The Lexvo.org ontology is still under development and may not be able to address all needs. Please also consider using the Lingvoj Ontology and the GOLD ontology, whereever appropriate. @en
-
An OWL vocabulary to include and exploit probabilistic information in SHACL validation reports @en
-
The Open Provenance Model is a model of provenance that is designed to meet the following requirements: (1) To allow provenance information to be exchanged between systems, by means of a compatibility layer based on a shared provenance model. (2) To allow developers to build and share tools that operate on such a provenance model. (3) To define provenance in a precise, technology-agnostic manner. (4) To support a digital representation of provenance for any 'thing', whether produced by computer systems or not. (5) To allow multiple levels of description to coexist. (6) To define a core set of rules that identify the valid inferences that can be made on provenance representation. @en