ISO

The Descriptive Ontology for Linguistic and Cognitive Engineering (DOLCE) is a top-level ontology (TLO) conforming to ISO/IEC 21838-1. It contains definitions of its terms and relational expressions and formal representations in OWL 2 and in Common Logic (CL). DOLCE is a top-level ontology aimed at making explicit people-s assumptions about the nature and structure of the world, as reflected by natural language, cognition and human common sense. DOLCE is widely used by a diverse array of domain ontologies in areas like enterprise and process modeling, engineering, robotics, geographical information systems, socio-technical systems and digital humanities. The natural language specification of the DOLCE signature supports human maintenance and use of the ontology, including use in development of conformant domain ontologies. The adoption of the Web Ontology Language (OWL) as a W3C standard was motivated by the need to have a decidable ontology representation language as the basis for the Semantic Web. The OWL 2 formalization of DOLCE supports use of the ontology in computing, including enabling DOLCE to be used in tandem with other ontologies expressed in OWL and in related languages, and in allowing ontology quality control through use of OWL reasoners. The CL formalization of DOLCE provides the expressivity needed to provide an axiomatization whose models are the intended models of DOLCE. This axiomatization has a modular structure (see Figure 2 where the arrows represent the relation of extension of theories). This document conforms to ISO/IEC 21838-1.

PSL is being incorporated into the TUpper ontology as Part 4 of ISO 21838 (Top Level Ontologies). In particular, TUpper extends PSL with modules for physical objects, location, and units of measure, thus addressing the shortcomings of using PSL alone. In these notes, we summarize various aspects of PSL and TUpper with respect to the IOF selection criteria for a foundational ontology.

This document describes Basic Formal Ontology (BFO), which is an ontology that is conformant to the requirements specified for top-level ontologies inISO/IEC218381. It describes BFO as a resource designed to support the interchange of information among heterogeneous information systems. The following are within the scope of this document: definitions of BFO-2020 terms and relations; axiomatizations of BFO-2020 in OWL2 and CL; documentation of the conformity of BFO-2020 to the requirements specified for top-level ontologies inISO/IEC218381; specification of the requirements for a domain ontology if it is to serve as a module in a suite of ontologies in which BFO serves as top-level ontology hub by providing a starting point for the introduction of the most general terms in those domain ontologies which are its nearest neighbours within the suite; specification of the role played by the terms in BFO in the formulation of definitions and axioms in ontologies at lower levels that conform to BFO. The following are outside the scope of this document: specification of ontology languages, including the languages RDF, OWL, and CL standardly used in ontology development; specification of methods for reasoning with ontologies; specification of translators between the notations of ontologies developed in different ontology languages.

This document provides the basic concepts for IoT systems semantic interoperability, as described in the facet model of ISO/IEC 21823-1, including: - requirements of the core ontologies for semantic interoperability; - best practices and guidance on how to use ontologies and to develop domain-specific applications, including the need to allow for extensibility and connection to external ontologies; - cross-domain specification and formalization of ontologies to provide harmonized utilization of existing ontologies; - relevant IoT ontologies along with comparative study of the characteristics and approaches in terms of modularity, extensibility, reusability, scalability, interoperability with upper ontologies, and so on, and; - use cases and service scenarios that exhibit necessities and requirements of semantic interoperability.

Industrial automation systems and integration

This document specifies the metamodel that provides a facility to register administrative and evolution information related to ontologies. The metamodel is intended to promote interoperability among application systems, by providing administrative and evolution information related to ontologies, accompanied with standardized ontology repositories that register ontologies themselves in specific languages. This document does not specify the metamodels of ontologies expressed in specific languages and the mappings among them.

ISO/IEC 13250-5:2015 specifies a formal model for subject maps, minimal access functionality and information retrieval from subject maps and a constraint framework governing the interpretation of subject maps. Particular formalisms to constrain subject maps are not covered by this part of ISO/IEC 13250.

ISO/IEC 18384-3:2016 defines a formal ontology for service-oriented architecture (SOA), an architectural style that supports service orientation. The terms defined in this ontology are key terms from the vocabulary in ISO/IEC 18384-1.

This document specifies the metamodel that provides a facility to register administrative and evolution information related to ontologies. The metamodel is intended to promote interoperability among application systems, by providing administrative and evolution information related to ontologies, accompanied with standardized ontology repositories that register ontologies themselves in specific languages. This document does not specify the metamodels of ontologies expressed in specific languages and the mappings among them.

This document complies with the ISO 22166-1 and CD 22166-201 family standards providing requirements and guidelines on specifications on modularity for service robots; in this context the document presents requirements and guidelines for an information model for software modules of service robots, where the information model relates to interoperability, reusability, and composability of software modules. In particular, the document focuses on interfaces, properties, composition, and execution-specific information, which are related to software modules.