ISO

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.

This document specifies the necessary system hardware components, the characteristics, the component requirements and conditions for the application of robotic ultrasonic test systems.This document specifies the general requirements and acceptance criteria for robotic ultrasonic test systems.This document is applicable to robotic ultrasonic test systems composed of one or more robot(s).This document is applicable to conventional straight beam probes and immersion technique.This document is also applicable for phased array probes but then additional tests can be necessary.

This document describes methods of specifying and evaluating the manipulation performance of service robots, notably:— grasp size. — grasp strength. — grasp slip resistance. — opening a hinged door; and— opening a sliding door.There are other grasping characteristics and use cases for manipulation of service robots. It is expected that these will be included in a future revision.This document deals with the indoor environment only. However, the depicted tests can also be applicable for robots operating in outdoor environments.This document is not applicable for the verification or validation of safety requirements.

his document describes methods of specifying and evaluating the performance of lower-back support robots.This document applies regardless of the purpose and application of lower-back support robots and the driving methods (e.g. electric, hydraulic and pneumatic). This document does not apply to medical robots, although the test methods specified in this document can be utilized for medical robots.This document is not intended for the verification or validation of safety requirements.

IEC TR 60601-4-1:2017(E) is intended to help a manufacturer through the key decisions and steps to be taken to perform a detailed risk management and usability engineering processes for medical electrical equipment or a medical electrical system, hereafter referred to as MEE or MES, employing a degree of autonomy (DOA). This document provides a definition of DOA of MEE or MES and a medical robot, and also provides guidance on: - methodologies to perform the risk management process and usability engineering for an MEE or MES with a DOA; - considerations of basic safety and essential performance for an MEE and MES with a DOA; and - identifying the use of DOA, and similar concepts in existing ISO/IEC standards dealing with MEE or MES with the goal to facilitate alignment of standards by consistent use of the concept of DOA; and - distinguishing between medical robots, and other MEE and MES. Unless specified otherwise, this document considers MEE and MES together. The manufacturer of an MEE or MES with a DOA is expected to design and manufacture an MEE or MES that fulfils its intended use and does not have unacceptable risk throughout its life-cycle. This document provides guidance to help the manufacturer in complying with the requirements of IEC 60601-1:2005 and IEC 60601-1:2005/AMD1:2012 for MEE and MES with DOA. The document is also intended as guidance for future standard writers. There are no prerequisites to this document.