173
results
  • The Battery Testing Ontology (BTO) is an application-level ontology belonging to EMMO's ecosystem, meant to model battery testing methodologies and techniques, like the partial discharge test. BTO is connected and aligned with a number of EMMO-based ontologies, including CHAMEO, Battery Domain Ontology and Electrochemistry. @en
  • An ontology to capture the staggering diversity of polymeric materials and their applications. @en
  • The MarketPlace Agent and Expert Ontology (MAEO) is an ontology for modeling experts, expertise, and more broadly, knowledge providers and knowledge seekers for the subject areas of Materials Modeling. MAEO is an EMMO-compliant application ontology, and has been loosely aligned with a number of existing ontologies, including Friend-Of-A-Friend (FOAF) and five recently-developed EMMO-based domain ontologies for the classification of materials, models, manufacturing processes, characterization methods and software products related to Materials Modeling. @en
  • The Internet of Construction Ontology (IoC) construction process ontology is intended to represent a comprehensive solution of how processes in the construction industry can be modelled. Due to the iterative nature of creating an ontology, the construction process ontology presented here can at best be considered a working state at the time of publication. Our approach emphasizes the simplest and most comprehensive mapping possible, which is only extended based on insights from practical use when otherwise compelling limitations in usability and applicability arise. Thus, the extension and refinement of the developed construction process ontology strongly depends on the integration of further areas of the construction value chain and the connection of further domain ontologies. @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
  • This RDF vocabulary can be use to describe and categorize annotations involving entity mentions (sub-strings of text) that link to knowledgebase identifiers @en
  • The AGLS Metadata Terms Namespace provides URIs for the AGLS Metadata Terms Vocabulary in the context of AGLS Metadata Standard, a set of metadata properties and associated usage guidelines to improve the visibility, manageability and interoperability of online information and services. Vocabulary terms are declared using RDF Schema language to support RDF applications. It will be updated according to AGLS Working Group decisions. @en
  • Vocabulary to describe fridges and freezers @en
  • The Extension of the Vocabulary of Interlinked Datasets (VoID) RDF Schema that includes the concept of virtual links. This extension enhances interoperability among heterogeneous and distributed RDF data sets by bridging them through explicitly defined virtual links. @en
  • A vocabulary to describe licenses @en
  • 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
  • The Dublin Core Metadata Element Set is a vocabulary of fifteen properties for use in resource description. The name "Dublin" is due to its origin at a 1995 invitational workshop in Dublin, Ohio; "core" because its elements are broad and generic, usable for describing a wide range of resources. @en
  • an up-to-date specification of all metadata terms maintained by the Dublin Core Metadata Initiative, including properties, vocabulary encoding schemes, syntax encoding schemes, and classes. @en
  • Draft for a recommendation for metadata on Representational Units (RU) which appear in ontologies. It is so far harmonized for implementation through owl annotation properties. @en