106
results
  • 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
  • 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
  • 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
  • IT Service Management Ontology (ITSMO) provides the vocabulary for annotating resources related to IT Service Management. ITSMO tries to be consistent with 2011 ITIL glossary. @en
  • This ontology defines the most abstract concepts and properties that are needed to semantically manage resource within federated infrastructures @en
  • The NLP Interchange Format (NIF) is an RDF/OWL-based format that aims to achieve interoperability between Natural Language Processing (NLP) tools, language resources and annotations. @en
  • This ontology is a reduced-in-scope version of the [W3C Decisions and Decision-Making Incubator Group](https://www.w3.org/2005/Incubator/decision/)'s Decision Ontology (DO) which can be found at <https://github.com/nicholascar/decision-o>. It has been re-worked to align entirely with the W3C's [PROV ontology](https://www.w3.org/TR/prov-o/) since it is widely recognised that analysing the elements of decisions *post hoc* is an exercise in provenance. Unlike the original DO, this ontology cannot be used for *normative* scenarios: it is only capable of recording decisions that have already been made (so-called *data-driven* use in the DO). This is because PROV, to which this ontology is completely mapped, does not have a templating system which can indicate what *should* occur in future scenarios. This ontology introduces only one new element for decision modelling over that which was present in the DO: an Agent which allows agency in decision making to be recorded. @en
  • This Agreements Ontology is designed to model 'agreements' which are social contracts that include licenses, laws, contracts, Memoranda of Understanding, standards and definitional metadata. Its purpose is to support data sharing by making explicit the relationships between agreements and data and agreements and Agents (people and organisations). Eventually it will also help with the interplay between different classes of agreements. @en
  • The GVP Ontology defines classes, properties and values (skos:Concepts) used in GVP LOD. It is complete regarding AAT and TGN (as of version 2.0), and will be extended in time with more elements needed for the other GVP vocabularies (ULAN, CONA). @en
  • This vocabulary is intended to describe all the aspects which are needed to communicate incident related information for fire department services @en
  • The AMLO-core is the main module of the AMLO projects that extends the Financial Industry Business Ontology (FIBO) with some concepts to describe the Anti Money Laundering (AML) knowledge and facts. @en
  • This RDF vocabulary can be use to describe and categorize annotations involving entity mentions (sub-strings of text) that link to knowledgebase identifiers @en
  • A micro-ontology that defines a set of typical document-related services such as provided by libraries, museums and archives. @en