The intention of SAREF4AGRI is to connect SAREF with existing ontologies and important standardization initiatives and ontologies in the Smart Agriculture and Food Chain domain, including ICAR for livestock data, AEF for agricultural equipment, Plant Ontology Consortium for plants, or AgGateway for IT support for arable farming.
The SAREF extension for the wearables domain (SAREF4WEAR) is based on a limited set of use cases and from available existing data models.
The SAREF4EHAW extension has been specified and formalised by investigating EHAW domain related resources such as: potential stakeholders, standardization initiatives, alliances/associations, European projects, EC directives, existing ontologies, and data repositories.
SAREF4ENVI has two main aims: on the one hand, to be the basis for enabling the use of SAREF in the environment domain and, on the other hand, to exemplify how to enable interoperability between environmental devices in cooperation.
The SAREF extension for the water domain (SAREF4WATR) is based on a limited set of use cases and from available existing data models.
The intention of SAREF4AUTO is to connect SAREF with existing ontologies (such as W3C SSN, W3C SOSA, GeoSPARQL, etc.) and important standardization initiatives and ontologies in the Automotive domain.
SAREF4ENER is an extension of SAREF that was created in collaboration with Energy@Home and EEBus to enable the interconnection of their (different) data models.
SAREF4LIFT is an ontology that extends SAREF for the Smart Lifts domain. This SAREF extension is based on a limited set of use cases and existing data models identified within available initiatives.
SAREF4BLDG is an extension of the SAREF ontology that was created based on the Industry Foundation Classes (IFC) standard for building information. It should be noted that not the whole standard has been transformed since it exceeds the scope of this extension, which is limited to devices and appliances within the building domain.
The objective of the paper is to show how the OAM can be used to realize seamless integration of product information, with an emphasis on assembly, throughout all phases of a product design
the main categories of cutting tool data and the relationships between them. It provides a general information model of data representation and information exchange for these categories, as well as an overview of the principles of product data exchange used in ISO 13399 as a whole, a description of the other parts of ISO 13399 and a method for transferring cutting tool data
The IOF-s mission is to create a suite of ontologies intended to support digital manufacturing by facilitating cross-system integration both within the factory and across an enterprise, in commerce between suppliers, manufacturers, customers and other trading partners, and throughout the various stages of the product life cycle. The IOF Core Ontology resides at the top of this suite from an architectural perspective and contains terms found in a number of operational areas of manufacturing. These common terms appear, or are anticipated to appear, in two or more of the ontologies of the suite. Additionally, as the architectural approach chosen by the IOF is to base all of its ontologies on a single foundational or top-level ontology - for which the IOF chose the Basic Formal Ontology or BFO - the Core Ontology contains a number of intermediate-level terms that derive from BFO and from which common industry terms are in turn derived. Such intermediate-level terms are most often domain independent - meaning they are found in other industries and domains, such as in the banking, insurance, and healthcare industries, or in the sciences, as in the physics, chemistry and biology domains. The IOF Core Ontology is developed and formalized as an ontology using both first-order logic and version 2 of the Web Ontology Language (OWL). The use of logic ensures that each term is defined in a way that is unambiguous to humans and can be processed by computers. All terms appearing in the ontology are reviewed and curated by a working group and consensus is reached by validating usage in the context of manufacturing domain use cases.