69
results
  • The EUropean Research Information Ontology (EURIO) conceptualises, formally encodes and makes available in an open, structured and machine-readable format data about resarch projects funded by the EU's framework programmes for research and innovation. @en
  • Open 311 Ontology This ontology generalizes the concepts that appear in 311 open data files published by several cities (Toronto, New York, Chicago, Vancouver) across North America. It provides a generis representation of 311 data that other cities can map their data onto and be used as a means of achieving interoperability. @en
  • The Plan module of CEON (Circular Economy Ontology Network). @en
  • A core ODP of the CEON ontology network, defining aspects of the process concept. @en
  • 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
  • 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
  • This ontology, called VIR, is an extension of CIDOC-CRM created to sustain propositions on the nature of visual elements and permit these descriptions to be published on the Web. With the term visual element, we refer to those signs identified in the visual space as distinct and documentable units, and subject to an analytical interpretation. The scope of this ontology is to s to provide a framework to support the identification, annotation and interconnections between diverse visual elements and presents and assist their documentation and retrieval. Specifically, the model aims to clarify the identity and the relation of these visual signs, providing the necessary classes to characterise their constituent elements, reference, symbolic content and source of interpretation. VIR expands on key entities and properties from CIDOC-CRM, introducing new classes and relationships responding to the visual and art historical community, specifically building up on the iconographical tradition. The result is a model which differentiates between interpretation and element identified, providing a clear distinction between denotation and signification of an element. As a consequence of such distinction, the ontology allows for the definition of diverse denotative criteria for the same representation, which could change based on traditions and perspective. Visual objects can be, in fact, polysemic and ambiguous, and it is not so easy to pin down a denotative or connotative meaning because they are very much context-dependent. @en
  • This ontology aims at providing a simple vocabulary for describing programmes. It covers brands, series (seasons), episodes, broadcast events, broadcast services, etc. @en
  • The Stories ontology was developed in collaboration with the BBC, with an aim to creating an ontology for narrative representation that could be applied across a diverse set of cases. These included accounts of events in Northern Ireland, the storylines of Doctor Who episodes, and key events of the Battle of Britain. @en
  • This Vocabulary provides the means to create a document which describes a large event or other connected series of events. The primary purpose is to help humans comprehend the programme, not describe absolute truth. A single event (or even series) may have multiple programmes. @en
  • SCoRO, the Scholarly Contributions and Roles Ontology, is an ontology for use by authors and publishers for describing the contributions that may be made and the roles that may be held by a person with respect to a journal article or other publication, and by research administrators and others for describing contributions and roles with respect to other aspects of scholarly research. @en
  • An ontology for organising theatrical data. @en
  • The Media Value Chain Ontology (MVCO) is an ontology for formalizing the representation of the Media Value Chain. It couples naturally with the MPEG-21 multimedia framework, and its standardization as Part 19 of this ISO/IEC standard is underway (at the editing time of this document). @en