<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Archiving and Interchange DTD v2.3 20070202//EN" "archivearticle.dtd">
<article article-type="systematic-review" dtd-version="2.3" xml:lang="EN" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">
<front>
<journal-meta>
<journal-id journal-id-type="publisher-id">Front. Robot. AI</journal-id>
<journal-title>Frontiers in Robotics and AI</journal-title>
<abbrev-journal-title abbrev-type="pubmed">Front. Robot. AI</abbrev-journal-title>
<issn pub-type="epub">2296-9144</issn>
<publisher>
<publisher-name>Frontiers Media S.A.</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="publisher-id">1377897</article-id>
<article-id pub-id-type="doi">10.3389/frobt.2024.1377897</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Robotics and AI</subject>
<subj-group>
<subject>Systematic Review</subject>
</subj-group>
</subj-group>
</article-categories>
<title-group>
<article-title>A survey of ontology-enabled processes for dependable robot autonomy</article-title>
<alt-title alt-title-type="left-running-head">Aguado et al.</alt-title>
<alt-title alt-title-type="right-running-head">
<ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3389/frobt.2024.1377897">10.3389/frobt.2024.1377897</ext-link>
</alt-title>
</title-group>
<contrib-group>
<contrib contrib-type="author" corresp="yes">
<name>
<surname>Aguado</surname>
<given-names>Esther</given-names>
</name>
<xref ref-type="aff" rid="aff1">
<sup>1</sup>
</xref>
<xref ref-type="aff" rid="aff2">
<sup>2</sup>
</xref>
<xref ref-type="corresp" rid="c001">&#x2a;</xref>
<uri xlink:href="https://loop.frontiersin.org/people/1364473/overview"/>
<role content-type="https://credit.niso.org/contributor-roles/conceptualization/"/>
<role content-type="https://credit.niso.org/contributor-roles/methodology/"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-original-draft/"/>
<role content-type="https://credit.niso.org/contributor-roles/Writing - review &#x26; editing/"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Gomez</surname>
<given-names>Virgilio</given-names>
</name>
<xref ref-type="aff" rid="aff1">
<sup>1</sup>
</xref>
<xref ref-type="aff" rid="aff2">
<sup>2</sup>
</xref>
<uri xlink:href="https://loop.frontiersin.org/people/2691691/overview"/>
<role content-type="https://credit.niso.org/contributor-roles/conceptualization/"/>
<role content-type="https://credit.niso.org/contributor-roles/Writing - review &#x26; editing/"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Hernando</surname>
<given-names>Miguel</given-names>
</name>
<xref ref-type="aff" rid="aff2">
<sup>2</sup>
</xref>
<uri xlink:href="https://loop.frontiersin.org/people/2781126/overview"/>
<role content-type="https://credit.niso.org/contributor-roles/methodology/"/>
<role content-type="https://credit.niso.org/contributor-roles/Writing - review &#x26; editing/"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Rossi</surname>
<given-names>Claudio</given-names>
</name>
<xref ref-type="aff" rid="aff2">
<sup>2</sup>
</xref>
<uri xlink:href="https://loop.frontiersin.org/people/91650/overview"/>
<role content-type="https://credit.niso.org/contributor-roles/conceptualization/"/>
<role content-type="https://credit.niso.org/contributor-roles/formal-analysis/"/>
<role content-type="https://credit.niso.org/contributor-roles/Writing - review &#x26; editing/"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Sanz</surname>
<given-names>Ricardo</given-names>
</name>
<xref ref-type="aff" rid="aff1">
<sup>1</sup>
</xref>
<xref ref-type="aff" rid="aff2">
<sup>2</sup>
</xref>
<uri xlink:href="https://loop.frontiersin.org/people/132079/overview"/>
<role content-type="https://credit.niso.org/contributor-roles/conceptualization/"/>
<role content-type="https://credit.niso.org/contributor-roles/formal-analysis/"/>
<role content-type="https://credit.niso.org/contributor-roles/project-administration/"/>
<role content-type="https://credit.niso.org/contributor-roles/Writing - review &#x26; editing/"/>
</contrib>
</contrib-group>
<aff id="aff1">
<sup>1</sup>
<institution>Autonomous Systems Laboratory</institution>, <institution>Universidad Polit&#xe9;cnica de Madrid</institution>, <addr-line>Madrid</addr-line>, <country>Spain</country>
</aff>
<aff id="aff2">
<sup>2</sup>
<institution>Centre for Automation and Robotics</institution>, <institution>Universidad Polit&#xe9;cnica de Madrid-CSIC</institution>, <addr-line>Madrid</addr-line>, <country>Spain</country>
</aff>
<author-notes>
<fn fn-type="edited-by">
<p>
<bold>Edited by:</bold> <ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/353228/overview">Ivano Malavolta</ext-link>, VU Amsterdam, Netherlands</p>
</fn>
<fn fn-type="edited-by">
<p>
<bold>Reviewed by:</bold> <ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/300220/overview">Nico Hochgeschwender</ext-link>, University of Bremen, Germany</p>
<p>
<ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/497843/overview">Giovanni De Gasperis</ext-link>, University of L&#x2019;Aquila, Italy</p>
</fn>
<corresp id="c001">&#x2a;Correspondence: Esther Aguado, <email>e.aguado@upm.es</email>
</corresp>
</author-notes>
<pub-date pub-type="epub">
<day>10</day>
<month>07</month>
<year>2024</year>
</pub-date>
<pub-date pub-type="collection">
<year>2024</year>
</pub-date>
<volume>11</volume>
<elocation-id>1377897</elocation-id>
<history>
<date date-type="received">
<day>28</day>
<month>01</month>
<year>2024</year>
</date>
<date date-type="accepted">
<day>29</day>
<month>05</month>
<year>2024</year>
</date>
</history>
<permissions>
<copyright-statement>Copyright &#xa9; 2024 Aguado, Gomez, Hernando, Rossi and Sanz.</copyright-statement>
<copyright-year>2024</copyright-year>
<copyright-holder>Aguado, Gomez, Hernando, Rossi and Sanz</copyright-holder>
<license xlink:href="http://creativecommons.org/licenses/by/4.0/">
<p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (CC BY). The use, distribution or reproduction in other forums is permitted, provided the original author(s) and the copyright owner(s) are credited and that the original publication in this journal is cited, in accordance with accepted academic practice. No use, distribution or reproduction is permitted which does not comply with these terms.</p>
</license>
</permissions>
<abstract>
<p>Autonomous robots are already present in a variety of domains performing complex tasks. Their deployment in open-ended environments offers endless possibilities. However, there are still risks due to unresolved issues in dependability and trust. Knowledge representation and reasoning provide tools for handling explicit information, endowing systems with a deeper understanding of the situations they face. This article explores the use of declarative knowledge for autonomous robots to represent and reason about their environment, their designs, and the complex missions they accomplish. This information can be exploited at runtime by the robots themselves to adapt their structure or re-plan their actions to finish their mission goals, even in the presence of unexpected events. The primary focus of this article is to provide an overview of popular and recent research that uses knowledge-based approaches to increase robot autonomy. Specifically, the ontologies surveyed are related to the selection and arrangement of actions, representing concepts such as autonomy, planning, or behavior. Additionally, they may be related to overcoming contingencies with concepts such as fault or adapt. A systematic exploration is carried out to analyze the use of ontologies in autonomous robots, with the objective of facilitating the development of complex missions. Special attention is dedicated to examining how ontologies are leveraged in real time to ensure the successful completion of missions while aligning with user and owner expectations. The motivation of this analysis is to examine the potential of knowledge-driven approaches as a means to improve flexibility, explainability, and efficacy in autonomous robotic systems.</p>
</abstract>
<kwd-group>
<kwd>ontology</kwd>
<kwd>robot autonomy</kwd>
<kwd>adaptation</kwd>
<kwd>robustness</kwd>
<kwd>resilience</kwd>
</kwd-group>
<custom-meta-wrap>
<custom-meta>
<meta-name>section-at-acceptance</meta-name>
<meta-value>Computational Intelligence in Robotics</meta-value>
</custom-meta>
</custom-meta-wrap>
</article-meta>
</front>
<body>
<sec id="s1">
<title>1 Introduction</title>
<p>Autonomous robots have endless possibilities; they are applied in a variety of sectors such as transport, logistics, industry, agriculture, healthcare, education, energy, etc. Robotics has shown enormous potential in diverse tasks and environments. However, there are still open issues that compromise autonomous robot dependability. To support their deployment in real-world scenarios, we need to provide robots with tools to act and react properly in unstructured environments with high uncertainty.</p>
<p>Various strategies support the pursuit of a better grasp of intelligence: neuroscience tries to understand how the brain processes information; mathematics seeks computation and rules to draw valid conclusions using formal logic or handling uncertainty with probability and statistics; control theory and cybernetics aim to ensure that the system reaches desired goals, etc. (<xref ref-type="bibr" rid="B64">Russell and Norvig, 2021</xref>). One way that we explore in this survey is the use of symbolic explicit knowledge as a means to enhance system intelligence.</p>
<p>Knowledge representation and reasoning (KR&#x26;R) is a sub-area of artificial intelligence that concerns analyzing, designing, and implementing ways of representing information on computers so that computational agents can use this information to derive information implied by it (<xref ref-type="bibr" rid="B69">Shapiro, 2003</xref>). Reasoning is the process of extracting new information from the implications of existing knowledge. One of the challenges of getting robots to perform tasks in open environments is that programmers cannot fully predict the state of the world in advance. KR&#x26;R provides some background to reason about the runtime situation and act in consequence. In addition to adaptability, these approaches can provide an explanation; knowledge can be queried so humans or other agents can understand why a robot acts in a certain way. Lastly, KR&#x26;R provides reusability. The robot needs information about its capabilities and the environment in which it is involved; this information can be shared among different agents, applications, or tasks because knowledge bases can be stored in broadly applicable modular chunks.</p>
<p>To be useable by robots, knowledge bases must be machine-understandable because the robot shall read, reason about, and update its content. In the context of intelligent robots, <italic>ontologies</italic> allow us to define the conceptualizations that the robot requires to support autonomous decision making. These ontologies are written in specific computer languages. In this article, we present a review of the ontologies used by autonomous robots to perform complex missions. In our analysis, we focus on the critical aspects of robot autonomy, that is, how KR&#x26;R can contribute to increasing the dependability of these types of systems. We aim to draw a landscape on how ontologies can support decision making to build more dependable robots performing elaborated tasks. The main contributions of this work are:<list list-type="simple">
<list-item>
<p>1. A classification of ontologies based on concepts for autonomous robots,</p>
</list-item>
<list-item>
<p>2. An analysis of existing approaches that use ontologies to facilitate action selection, and</p>
</list-item>
<list-item>
<p>3. A discussion of future research directions to increase dependability in autonomous robots.</p>
</list-item>
</list>
</p>
<p>This article is structured as follows. <xref ref-type="sec" rid="s2">Section 2</xref> provides background information on KR&#x26;R with a special focus on ontologies for robot autonomy. <xref ref-type="sec" rid="s3">Section 3</xref> discusses the classification criteria for ontologies that support robust autonomy in robotic applications. In <xref ref-type="sec" rid="s4">Section 4</xref>, we describe the selection process for a systematic review in the field of ontologies for autonomous robots and briefly discuss other surveys in the field. In <xref ref-type="sec" rid="s5">Section 5</xref>, we classify and compare the selected approaches based on their main application domain. <xref ref-type="sec" rid="s6">Section 6</xref> provides a general discussion and describes future research directions. Lastly, <xref ref-type="sec" rid="s7">Section 7</xref> presents the article&#x27;s conclusions.</p>
</sec>
<sec id="s2">
<title>2 Knowledge representation and reasoning for robot autonomy</title>
<p>In this section, we introduce the use of ontologies to increase dependability in autonomous systems and the main languages for knowledge-based agents. Finally, we also discuss the essential and desirable capabilities of fully autonomous robots.</p>
<p>Dependability is the ability to provide the intended services of the system with a certain level of assurance, including factors such as availability, reliability, safety, and security (<xref ref-type="bibr" rid="B68">SEBoK Editorial Board, 2023</xref>). As an introductory exploration into this field, <xref ref-type="bibr" rid="B34">Guiochet et al. (2017)</xref> provide an analysis of techniques used to increase safety in robots and autonomous systems. <xref ref-type="bibr" rid="B6">Avi&#x17e;ienis et al. (2004)</xref> offer definitions and conceptualizations of aspects related to dependability and create a taxonomy of dependable computing and its associated faults as a framework.</p>
<p>Dependability ensures consistent performance that goes beyond reliability, as it also considers factors such as fault tolerance, error recovery, and maintaining service levels. Various models of tackling these challenges include fault trees, failure modes and effect analysis (FMEAs), and safety case modes. There are also model-based approaches in which fault analysis can be used in runtime to evaluate goals and develop and execute alternative plans (<xref ref-type="bibr" rid="B1">Abbott, 1990</xref>). Similarly, this survey focuses on using explicit models to select the most suitable actions for the situation the robot faces to provide the desired outcomes. This survey concentrates on leveraging ontologies as a means to enhance dependability rather than analyzing dependability aspects concerning robotics.</p>
<sec id="s2-1">
<title>2.1 Languages for ontologies</title>
<p>The most extended approach to robot programming is procedural: The intended robot behavior is explicitly encoded in an imperative language. Knowledge-based agents depart from this, using declarative approaches to abstract the control flow. A knowledge base (KB) stores information that allows the robot to deduce how to operate in the environment. This information can be updated with new facts, and repeated queries are used to deduce new facts relevant to the mission. A successful agent often combines <italic>declarative knowledge</italic> with procedural programming to produce more efficient code (<xref ref-type="bibr" rid="B64">Russell and Norvig, 2021</xref>). This declarative knowledge is commonly encoded in logic systems to formally capture conceptualizations.</p>
<p>Prolog (PROgramming in LOGic) is the most widely used declarative programming language. Many knowledge-based systems have been written in this language for legal, medical, financial, and other domains (<xref ref-type="bibr" rid="B64">Russell and Norvig, 2021</xref>). Prolog defines a formalism based on decidable fragments of first-order logic (FOL). In addition to its notation, which is somewhat different from standard FOL, the main difference is the closed-world assumption. The closed-world assumption asserts that only the predicates explicitly defined in the KB are true; there is no way to declare that a sentence is false.</p>
<p>Another widely used language for writing ontologies is Ontology Web Language (OWL). OWL is not a programming language like Prolog but rather a family of languages that can be used to represent knowledge. It is designed for applications that need to process information rather than simply presenting information to humans. Therefore, OWL facilitates greater machine interpretability with a panoply of different formats, such as extensible markup language (XML), resource description framework (RDF), and RDF Schema (RDF-S). The language has been specified by the <xref ref-type="bibr" rid="B79">W3C OWL Working Group (2012)</xref> and is a cornerstone of the semantic web.</p>
<p>The formal basis of OWL is description logic (DL): a family of languages with a compromise between expressiveness and scalability. DL uses decidable fragments of FOL to reason with more expressiveness. The main difference between Prolog and OWL is that the latter uses the open-world assumption. This means that a statement can be true whether it is known or not; that is, only explicitly false predicates are false, in contrast to the closed-world assumption in which only explicitly true predicates are true.</p>
<p>Regarding accessibility, OWL can be encoded by hand or by editors such as Prot&#xe9;g&#xe9; (<xref ref-type="bibr" rid="B55">Musen, 2015</xref>) for a user-friendly environment. OWL can be integrated into robotic software through application program interfaces (APIs) such as Jena Ontology API<xref ref-type="fn" rid="fn1">
<sup>1</sup>
</xref> or OWLAPI<xref ref-type="fn" rid="fn2">
<sup>2</sup>
</xref> implemented in Java or OWLREADY (<xref ref-type="bibr" rid="B44">Lamy, 2017</xref>) implemented in Python. There are also reasoners such as FaCT&#x2b;&#x2b;<xref ref-type="fn" rid="fn3">
<sup>3</sup>
</xref>, Pellet<xref ref-type="fn" rid="fn4">
<sup>4</sup>
</xref>>, or HermiT<xref ref-type="fn" rid="fn5">
<sup>5</sup>
</xref>.</p>
<p>Prolog can also be used to reason about knowledge represented by OWL or to directly encode a Prolog ontology. The main Prolog APIs are GNU-PROLOG<xref ref-type="fn" rid="fn6">
<sup>6</sup>
</xref> and SWI-PROLOG<xref ref-type="fn" rid="fn7">
<sup>7</sup>
</xref>. There is even a package for the robot operating system (ROS) called <italic>rosprolog</italic>
<xref ref-type="fn" rid="fn8">
<sup>8</sup>
</xref> that interfaces between SWI-Prolog and ROS.</p>
</sec>
<sec id="s2-2">
<title>2.2 Fundamental and domain ontologies</title>
<p>Ontological systems can be classified according to several criteria. We distinguish three levels of abstraction based on Guarino&#x2019;s hierarchy (<xref ref-type="bibr" rid="B33">Guarino, 1998</xref>): upper level, domain, and application. <italic>Upper-level</italic> or foundational ontologies conceptualize general terms such as object, property, event, state, and relations such as parthood, constitution, participation, etc. <italic>Domain</italic> ontologies provide a formal representation of a specific field that defines contractual agreements on the meaning of terms within a discipline (<xref ref-type="bibr" rid="B35">Hepp et al., 2006</xref>); these ontologies specify the highly reusable vocabulary of an area and the concepts, objects, activities, and theories that govern it. <italic>Application</italic> ontologies contain the definitions required to model knowledge for a particular application: information about a robot in a specific environment, describing a particular task. Note that the environment or task knowledge could be a subdomain ontology, depending on the reusability it allows. In fact, the progress from upper-level to application ontologies is a continuous spectrum of concept subclassing, with somewhat arbitrary divisions into levels of abstraction reified as ontologies.</p>
<p>Perhaps the most extended upper-level ontology is the Suggested Upper Merged Ontology (SUMO) (<xref ref-type="bibr" rid="B56">Niles and Pease, 2001</xref>; <xref ref-type="bibr" rid="B60">Pease, 2011</xref>)<xref ref-type="fn" rid="fn9">
<sup>9</sup>
</xref>. SUMO is the largest open-source ontology that has expressive formal definitions of its concepts. Domain ontologies for medicine, economics, engineering, and many other topics are part of SUMO. This formalism uses the Standard Upper Ontology Knowledge Interchange Format (SUO-KIF), a logical language to express concepts with higher-order logic (a logic with more expressiveness than first-order logic) (<xref ref-type="bibr" rid="B18">Brown et al., 2023</xref>).</p>
<p>Another relevant foundational ontology for this research is the Descriptive Ontology for Linguistic and Cognitive Engineering (DOLCE), described as an &#x201c;ontology of universals&#x201d; (<xref ref-type="bibr" rid="B30">Gangemi et al., 2002</xref>), which means that it has classes but not relations. It aims to capture the ontological categories that underlie natural language and human common sense (<xref ref-type="bibr" rid="B53">Mascardi et al., 2006</xref>). The taxonomy of the most basic categories of particulars assumed in DOLCE includes, for example, abstract quality, abstract region, agentive physical object, amount of matter, temporal quality, etc. Although the original version of the few dozen terms in DOLCE was defined in FOL, it has since been implemented in OWL; most extensions of DOLCE are also in OWL.</p>
<p>The DOLCE &#x2b; DnS Ultralite ontology<xref ref-type="fn" rid="fn10">
<sup>10</sup>
</xref> (DUL) simplifies some parts of the DOLCE library, such as the names of classes and relations with simpler constructs. The most relevant aspect of DUL is perhaps the design of the ontology architecture based on patterns.</p>
<p>Other important foundational ontologies are the Basic Formal Ontology (BFO) (<xref ref-type="bibr" rid="B5">Arp et al., 2015</xref>), the Bunge&#x2013;Wand&#x2013;Weber Ontology (BWW) (<xref ref-type="bibr" rid="B19">Bunge, 1977</xref>; <xref ref-type="bibr" rid="B81">Wand and Weber, 1993</xref>), and the Cyc Ontology (<xref ref-type="bibr" rid="B48">Lenat, 1995</xref>). BFO focuses on continuant entities involved in a three-dimensional reality and occurring entities, which also include the time dimension. BWW is an ontology based on Bunge&#x2019;s philosophical system that is widely used for conceptual modeling (<xref ref-type="bibr" rid="B51">Lukyanenko et al., 2021</xref>). Cyc is a long-term project in artificial intelligence that aims to use an ontology to understand how the world works by trying to represent implicit knowledge and perform human-like reasoning.</p>
<sec id="s2-2-1">
<title>2.2.1 Robotic domain ontologies</title>
<p>Ontologies have gained popularity in robotics with the growing complexity of actions that systems are expected to perform. A well-defined standard for knowledge representation is recognized as a tool to facilitate human&#x2013;robot collaboration in challenging tasks (<xref ref-type="bibr" rid="B29">Fiorini et al., 2017</xref>). The IEEE Standard Association of Robotics and Automation Society (RAS) created the Ontologies for Robotics and Automation (ORA) working group to address this need.</p>
<p>They first published the Core Ontology for Robotics and Automation (CORA) (<xref ref-type="bibr" rid="B62">Prestes et al., 2013</xref>). This standard specifies the most general concepts, relations, and axioms for the robotics and automation domain. CORA is based on SUMO and defines what a robot is and how it relates to other concepts. For this, it defines four main entities: robot part, robot, complex robot, and robotic system. CORA is an upper-level ontology currently extended in the IEEE Standard 1872-2015 (<xref ref-type="bibr" rid="B41">IEEE SA, 2015</xref>) with other subontologies, such as CORAX, RPARTS, and POS.</p>
<p>CORAX is a subontology created to bridge the gap between SUMO and CORA. It included high-level concepts that the authors claimed to not be explicitly defined in SUMO and particularized in CORA, in particular those associated with design, interaction, and environment. RPARTS provides notions related to specific kinds of robot parts and the roles they can perform, such as grippers, sensors, or actuators. POS presents general concepts associated with spatial knowledge, such as position and orientation, represented as points, regions, and coordinate systems.</p>
<p>However, CORA and its extensions are intended to cover a broad community, so their definitions of ambiguous terms are based solely on necessary conditions and do not specify sufficient conditions (<xref ref-type="bibr" rid="B29">Fiorini et al., 2017</xref>). For this reason, concepts in CORA must be specialized according to the needs of specific subdomains or robotics applications.</p>
<p>CORA, like most of the other application ontologies considered here, is defined in a language of very limited expressiveness, mostly expressible in OWL-Lite, and is therefore limited to simple classification queries. Although it is based on upper-level terms from SUMO, it recreated many terms that could have been used directly from SUMO. Moreover, given its choice of representation language, it did not use the first- and higher-order logic formulas from SUMO, limiting its reuse to only the taxonomy.</p>
<p>The IEEE ORA group created the Robot Task Representation subgroup to produce a <italic>middle-level ontology</italic> with a comprehensive decomposition of tasks, from goal to subgoals, that enables humans or robots to accomplish their expected outcomes at a specific instance in time. It includes a definition of tasks and their properties and terms related to the performance capabilities required to perform them. Moreover, it covers a catalog of tasks demanded by the community, especially in industrial processes (<xref ref-type="bibr" rid="B7">Balakirsky et al., 2017</xref>).</p>
<p>This working group also created three additional subgroups for more specific domain knowledge: Autonomous Robots Ontology, Industrial Ontology, and Medical Robot Ontology. Only the first of these has been active. The Autonomous Robot subgroup (AUR) extends CORA and its associated ontologies for the domain of autonomous robots, including, but not limited to, aerial, ground, surface, underwater, and space robots.</p>
<p>They developed the IEEE Standard for Autonomous Robotics Ontology (<xref ref-type="bibr" rid="B42">IEEE SA, 2022</xref>) with an unambiguous identification of the basic hardware and software components necessary to provide a robot or a group of robots with autonomy. It was conceived to serve different purposes, such as to describe the design patterns of Autonomous Robotics (AuR) systems, to represent AuR system architectures in a unified way, or as a guideline to build autonomous systems consisting of robots operating in various environments.</p>
<p>In addition to the developments of the IEEE ORA working group, there are other relevant domain ontologies, such as OASys and the Socio-physical Model of Activities (SOMA). The Ontology for Autonomous Systems (OASys) (<xref ref-type="bibr" rid="B12">Bermejo-Alonso et al., 2010</xref>) captures and exploits concepts to support the description of any autonomous system with an emphasis on the associated engineering processes. It provides two levels of abstraction systems in general and autonomous systems in particular. This ontology connects concepts such as architecture, components, goals, and functions with the engineering processes required to achieve them.</p>
<p>The SOMA for Autonomous Robotic Agents represents the physical and social context of everyday activities to facilitate accomplishing tasks that are trivial for humans (<xref ref-type="bibr" rid="B14">Be&#xdf;ler et al., 2021</xref>). It is based on DUL, extending their concept to different event types such as action, process, and state, the objects that participated in the activities, and the execution concept. It is worth mentioning that SOMA was intended to be used in the runtime along with the concept of narratively enabled episodic memories (NEEMs), which are comprehensive logs of raw sensor data, actuator control histories, and perception events, all semantically annotated with information about what the robot is doing and why using the terminology provided by SOMA.</p>
<p>The relationship between upper-level ontologies and domain ontologies is a relationship of progressive domain focalization (<xref ref-type="bibr" rid="B65">Sanz et al., 1999</xref>). The frameworks described in the following sections are mostly specializations of these general robotic ontologies and other foundations.</p>
</sec>
</sec>
<sec id="s2-3">
<title>2.3 Capabilities for robot autonomy</title>
<p>Etymologically, autonomy means being governed by the laws of oneself rather than by the rules of others (<xref ref-type="bibr" rid="B78">Vernon, 2014</xref>). <xref ref-type="bibr" rid="B8">Beer et al. (2014)</xref> provide a definition more closely related to robotics: autonomy as the extent to which a robot can <italic>sense</italic> its environment, <italic>plan</italic> based on that environment, and <italic>act</italic> on that environment with the intention of reaching some task-specific <italic>goal</italic> (either given or created by the robot) without external control. A related, systems-oriented perspective pursued in our lab considers autonomy as a relationship between system, task, and context (<xref ref-type="bibr" rid="B67">Sanz et al., 2000</xref>).</p>
<p>Rational agents use sense-decide-act loops to select the best possible action. According to <xref ref-type="bibr" rid="B78">Vernon (2014)</xref>, cognition allows one to increase the repertoire of actions and extend the time horizon of one&#x2019;s ability to anticipate possible outcomes. He also reviews several cognitive architectures to support artificial cognitive systems and discusses the relationship between cognition and autonomy. For him, cognition includes six attributes: perception, learning, anticipation, action, adaptation, and, of course, autonomy.</p>
<p>Following the link between cognition and autonomy, <xref ref-type="bibr" rid="B45">Langley et al. (2009)</xref> also review cognitive architectures and establish the main functional capabilities that autonomous robots must demonstrate. Knowledge is described as an internal property to achieve the following capabilities: (i) recognition and categorization to generate abstractions from perceptions and past actions, (ii) decision making and choice to represent alternatives for selecting the most prosperous action considering the situation, (iii) perception and situation assessment to combine perceptual information from different sources and provide an understanding of the current circumstances, (iv) prediction and monitoring to evaluate the situation and the possible effects of actions, (v) problem solving and planning to specify desired intermediate states and the actions required to reach them, (vi) reasoning and belief maintenance to use and update the KB in dynamic environments, (vii) execution and action to support deliberative and reactive behaviors, (viii) interaction and communication to share knowledge with other agents, and (ix) remembering, reflection, and learning to use meta-reasoning to use past executions as experiences for the future.</p>
<p>
<xref ref-type="bibr" rid="B17">Brachman (2002)</xref> argues about the promising capabilities of reflective agents. For him, real improvements in computational agents come when systems know what they are doing, that is, when the agent can understand the situation: what it is doing, where, and why. Brachman establishes practically the same foundations as <xref ref-type="bibr" rid="B45">Langley et al. (2009)</xref> but explicitly mentions the necessity of coordinated teams and robust software and hardware infrastructure.</p>
<p>In conclusion, most authors recall the importance of the features described above with different levels of granularity. In the next section, we explain and conceptualize those functional capabilities that enable robot operation autonomously. Note that the systems under study use explicit knowledge&#x2014;ontologies&#x2014;as the backbone to achieve autonomy.</p>
</sec>
</sec>
<sec id="s3">
<title>3 Processes for knowledge-enabled autonomous robots</title>
<p>In this section, we introduce the classification on which we will base the review of ontologies for dependable robot autonomy in <xref ref-type="sec" rid="s5">Section 5</xref>. The classification criterion is based on the capabilities introduced in <xref ref-type="sec" rid="s2-3">Section 2.3</xref>. It establishes the fundamental processes that an autonomous robot should perform.</p>
<sec id="s3-1">
<title>3.1 Perception</title>
<p>A percept is the belief produced as a result of a perceptor sensing the environment in an instant. Perception involves five entities: sensor, perceived quality, perceptive environment, perceptor, and the percept itself.</p>
<p>A <italic>sensor</italic> is a device that detects, measures, or captures a property in the environment. Sensors can measure one particular aspect of the physical world, such as thermometers, or capture complex characteristics, such as segmenting cameras.</p>
<p>A <italic>perceived quality</italic> is a feature that allows the perceptor to recognize some part of the environment&#x2014;or the robot itself. Note that this quality is mapped into the percept as an instantiation, a belief produced to translate physical information to the system model. Examples of perceived qualities are the temperature, visual images of the environment, and the rotation of a wheel measured by a rotative encoder placed in a robot.</p>
<p>A <italic>perceptive environment</italic> is the part of the environment that the sensor can detect. The perceptive region can be delimited by the sensor&#x2019;s resolution or to save memory or other resources.</p>
<p>An agent that perceives is a <italic>perceptor</italic>. It constitutes the link between perception and categorization because it takes sensor information and categorizes it. Usually, the perceptor embodies the sensor, as is the case in autonomous robots, but the two could be decoupled if the system processes information from external sensors. Finally, the <italic>percept</italic> is the inner entity&#x2014;a belief&#x2014;that results from the perceptual process.</p>
</sec>
<sec id="s3-2">
<title>3.2 Categorization</title>
<p>Percepts are instantaneous approximate representations of a particular aspect of the physical world. To provide the autonomous robot with an understanding of the situation in which it is deployed, the perceptor must abstract the sensor information and recognize objects, events, and experiences.</p>
<p>Categorization is the process of finding patterns and categories to model the situation in the robot&#x2019;s knowledge. It can be done at different levels of granularity. Examples of categorizations appear everywhere: at sensor fusion processes from different types of sensors, with their corresponding uncertainty propagation; at the classification of an entity as a mobile obstacle when it is an uncontrolled object approaching the robot; or, in a more abstract level, when a mobile miner robot recognizes the type of mine ore depending on its geo-chemical properties.</p>
<p>In general, this step corresponds to a combination of information about objects, events, action responses, physical properties, etc., to create a picture of what is happening in the environment and in the robot itself. For this purpose, the robot shall incorporate other processes, such as reasoning and prediction.</p>
</sec>
<sec id="s3-3">
<title>3.3 Decision making</title>
<p>An autonomous robot must direct its actions towards a goal. When an action cannot be performed, the robot shall implement mechanisms to make decisions and select among the most suitable alternatives for the runtime situation.</p>
<p>Note the difference between decision making and planning. Decision making has a shorter time frame because it focuses on the successful completion of the plan. An example of a decision at this level could be to slightly change the trajectory of a robot to avoid an obstacle and then return to the initial path. Planning, on the other hand, is concerned with achieving a goal; it has a longer time horizon to establish the action sequences to complete a mission. For example, the miner robot presented above must examine the mine, detect the mineral vein, and dig in that direction.</p>
<p>Decision making acts upon the different alternatives that the robot can select, for example, in terms of directions and velocity, but also in terms of what component with functional equivalence can substitute for a defective one. The execution of the action&#x2014;how it is done&#x2014;changes slightly, but the plan&#x2014;the action sequence that achieves the goal&#x2014;remains the same.</p>
</sec>
<sec id="s3-4">
<title>3.4 Prediction and monitoring</title>
<p>Once the robot has an internal model, it can supervise the situation. This model can be given <italic>a priori</italic> or created before stating the task; it could also be learned. The model reflects the understanding of the robot about its own characteristics, its interactions with the environment, and the relationships between its actions and its outcomes. At runtime, the robot can use the model to predict the effect of an action. It can also anticipate future events based on the way the situation is evolving.</p>
<p>This mechanism also allows the robot to monitor processes and compare the result obtained with the expected response. In the event of inconsistencies, it can inform an external operator or use adaptation techniques to solve possible errors. For example, if a robot is stuck, it may change its motion direction to get out, and if this is not possible, it can alert the user.</p>
<p>The prediction process can also benefit from a learning procedure to improve the models from experience and refine them over time. Furthermore, monitoring can be used during learning, as it detects errors that can help improve the model.</p>
</sec>
<sec id="s3-5">
<title>3.5 Reasoning</title>
<p>Reasoning is the process of using existing knowledge to draw logical conclusions and extend the scope of that knowledge. It requires solid definitions and relationships between concepts. It uses instances of such concepts to ground them to the robot&#x2019;s operation and to be used during the mission.</p>
<p>The reasoning process can be used to infer events based on the current percepts, such as the dynamic object approaching the robot, or to infer the best possible action to overcome it based on its background knowledge, such as reducing speed and slightly changing the direction. Lastly, as robots operate in dynamic worlds&#x2014;specifically, they operate by changing their environment&#x2014;the knowledge shall evolve over time.</p>
<p>Reasoning includes two processes: (i) infer and maintain beliefs and (ii) discard beliefs that are no longer valid. Logical systems support assertions and retractions for this purpose; however, they must be handled carefully to maintain ontological consistency. Truth maintenance is a critical capability for cognitive agents situated in dynamic environments.</p>
</sec>
<sec id="s3-6">
<title>3.6 Planning</title>
<p>Planning is the process of finding a sequence of actions to achieve a goal. To reach a solution, the problem must be structured and well defined, especially in terms of the starting state, which the robot shall transform into a desired goal state. The system also needs to know the constraints to execute an action and its expected outcome, that is, preconditions and postconditions. These conditions are also used to establish the order between actions and the effect that they may have on subsequent actions.</p>
<p>The required information is usually stored in three types of models: environment, robot, and goal models. Most authors only mention the environmental model, which includes the most relevant information about the robot world and its actions, tasks, and goals; however, we prefer to isolate the three models to make explicit the importance of proprioceptive information and performance indicators for a more dependable autonomous robot.</p>
<p>Plans can completely guide the behavior of the robot or suggest a succession of abstract actions that can be expanded in different ways. This can result in branches of possible actions, depending on the result of previous states.</p>
<p>Planning is also closely related to monitoring; the supervision output can conclude the effectiveness of the plan or detect some unreachable planned actions. In this case, the plan may need adjustments, such as changing parameters or replacing some actions. Replanning can use part of the plan or draw a completely new structure depending on the progress and status of the plan and the available components.</p>
<p>Lastly, successful plans or sub-plans can be stored for reuse. These stored plans can also benefit from learning, especially with regard to the environmental response to changes and action constraints and outputs.</p>
</sec>
<sec id="s3-7">
<title>3.7 Execution</title>
<p>A key process in robotic deployments is the execution of actions that interact with the environment. The robot model must represent the motor skills that produce such changes. Execution can be purely deliberative or combined with more reactive approaches; for example, a patrolling robot may reduce its speed or stop to ensure safety when close to a human&#x2014;reactiveness&#x2014;but it also needs a defined set of waypoints to fully cover an area&#x2014;deliberation.</p>
<p>Hence, an autonomous robot must facilitate the integration of both reactive and deliberative actions within a goal-oriented hierarchy. A strictly reactive approach would limit the ability to direct the robot&#x2019;s actions toward a defined objective. Meanwhile, an exclusively deliberative approach might be excessively computationally intensive and lead to delayed responses to instantaneous changes.</p>
<p>Another aspect of execution is control. Robots use controllers to overcome small deviations from their state. These controllers can operate in open-loop or closed-loop mode. Open-loop controllers apply predetermined actions based on a set of inputs, assuming that the system will respond predictably. Although they lack the ability to correct runtime deviations, they are often simpler and faster. Closed-loop controllers provide a more accurate and precise action based on inputs and feedback received. Control grounds the decision-making process by specifying the final target value for the robot effectors. It constitutes the final phase of action execution.</p>
</sec>
<sec id="s3-8">
<title>3.8 Communication and coordination</title>
<p>In many applications, robots operate with other agents&#x2014;humans or robots of a different nature. Communication is a key feature to organize actions and coordinate them towards a shared goal. Moreover, in knowledge-based systems, communication provides an effective way to obtain knowledge from other agents&#x2019; perspectives.</p>
<p>Shared information provides a means to validate perceived elements, fuse them with other sources, and provide access to unperceivable regions of the world. However, this requires a way to exchange information between agents in a neutral, shared conceptualization that is understandable and useable for both.</p>
<p>Once communication is established, we shall coordinate the actions of the systems involved. Decision-making and planning processes should take into account the capabilities and availability of agents to direct and sequence their actions toward the most promising solution. For example, in multirobot patrols, agents shall share their pose and planned path to avoid collisions. Another example could be exploring a difficult-to-access mine in which a wheeled robot could be used for most of the inspection activities, and a legged robot could be used to inspect the unreachable areas.</p>
</sec>
<sec id="s3-9">
<title>3.9 Interaction and design</title>
<p>Interaction and design are often omitted when analyzing autonomous capabilities. Although they are part of the design phase, this engineering knowledge holds considerable influence over the robot&#x2019;s performance and dependability.</p>
<p>Interaction between agents can be handled through coordination; however, the embodiment of robots can produce interactions between software and/or hardware components. Robots should be aware of the interaction ports and the possible errors that arise from them. This concern is presented by <xref ref-type="bibr" rid="B17">Brachman (2002)</xref>, as awareness of interaction allows the robot to step back from action execution and understand the sources of failure. This becomes particularly significant during the integration of diverse components and subsystems, where the application of systems engineering techniques proves to be highly beneficial.</p>
<p>
<xref ref-type="bibr" rid="B36">Hern&#xe1;ndez et al. (2018)</xref> argue about the need to exploit functional models to make explicit design decisions and alternatives at runtime. These models can provide background knowledge about requirements, constraints, and assumptions under which a design is valid. With this knowledge, we can endow robots with more tools for adaptability, providing the capability to overcome deviations or contingencies that may occur. For example, a manipulator robot with several tools may have one optimal tool for a task, but if this component is damaged, it can use an alternative tool to solve the problem in a less-than-optimal way.</p>
</sec>
<sec id="s3-10">
<title>3.10 Learning</title>
<p>Most of the processes described above can improve their efficacy through learning: categorization, decision making, prediction and monitoring, planning, execution, coordination, design, etc. Learning can be divided into three steps: remember, reflect, and generalize.<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Remember</italic> is the ability to store information from previous executions.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Reflect</italic> involves analyzing remembered information to detect patterns and establish relationships.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Generalize</italic> is the process of abstract conclusions derived from reflection and subsequently extended to use them in future experiences.</p>
</list-item>
</list>
</p>
<p>The classification of these competencies reveals their incorporation into KBs, identifies potential underrepresented elements, and explores the contributions of knowledge structures to the decision-making process.</p>
</sec>
</sec>
<sec id="s4">
<title>4 Review process</title>
<p>One of our main objectives in this article is to conduct a systematic analysis of recent and relevant projects that use ontologies for autonomous robots. The methodology followed is inspired by relevant surveys discussed in the next section, such as those by <xref ref-type="bibr" rid="B57">Olivares-Alarcos et al. (2019)</xref> and <xref ref-type="bibr" rid="B23">Cornejo-Lupa et al. (2020)</xref>. To avoid personal bias, the entire article selection process has been cross-analyzed by two people, and the framework analysis has been validated by the five authors.</p>
<p>The first step in our review process was to search for relevant keywords in scientific databases. Specifically, we used the most extended literature browsers, <italic>Scopus</italic>
<xref ref-type="fn" rid="fn11">
<sup>11</sup>
</xref> and <italic>Web of Science</italic>
<xref ref-type="fn" rid="fn12">
<sup>12</sup>
</xref>. These databases provide a wide range of peer-reviewed literature, including scientific journals, books, and conference proceedings. Scopus includes more than 7,000 publishers, and WOS includes more than 34,000 journals, including important journals in the field, such as those from IEEE, Springer, and ACM. It also has a user-friendly interface to store, analyze, and display articles. Moreover, related articles cited in the analyzed articles are included in the review process to ensure that relevant articles were not missed. The search was done in terms of title, abstract, or keywords containing the terms robot, ontology, plan, behavior, adapt, autonomy, or fault. In practice, we used the following search string. The search can be replicated using the provided query. However, it is important to note that the survey was conducted in 2022, and there may have been developments or new publications since then. Additionally, a list of the analyzed works and intermediate documents is available upon request.</p>
<p>The required terms are &#x201c;ontology&#x201d; and &#x201c;robot,&#x201d; as they are the foundation of our survey. Using this restriction may seem somewhat limiting because there could be knowledge-based approaches to cognitive robots that are not based on ontologies. However, in this review, we are specifically interested in using explicit ontologies for this purpose, hence the strong requirement regarding &#x201c;ontology.&#x201d; We also target at least one keyword related to (i) selection and arrangement of actions&#x2014;autonomous, planning, behavior&#x2014;or (ii) overcoming contingencies&#x2014;fault, adapt. Note that we use asterisks to be flexible with the notation.</p>
<p>This search returned 695 articles after removing duplicates. To mitigate potential biases, we implemented specific inclusion criteria based on publication dates and citation counts. We only include articles widely cited, with 20 or more citations, before 2010; articles between 2010 and 2015 with five or more citations; and articles between 2015 and 2018 with two or more citations. All articles from 2018 onward were included. With these criteria, we reduced the list to 351 articles. The selection process applied these criteria to identify articles that are not only recent but have also demonstrated impact and influence within their respective publication periods.</p>
<p>Then, we analyzed the content of the articles. We included works in which the main point of the article is the ontology. In particular, the work (i) proposes or extends the ontology and (ii) uses the ontology to select, adapt, or plan actions. We eliminated a number of articles on how to use ontologies to encode simulations, on-line generators of ontologies, or ontologies only used for conversation, perception, or collaboration without impact on robot action. The application of these criteria produced 26 relevant articles.</p>
<p>Finally, we complemented our search with articles from related surveys described in <xref ref-type="sec" rid="s4-1">Section 4.1</xref>. This ensured that we included all relevant and historical articles in the field with a snowball process. In this step, we obtained 22 more articles; some of them were already included in the previous list, and others did not meet our inclusion criteria. After evaluating them, we included six more articles, resulting in a total of 32 articles in deep review. The entire process is depicted in <xref ref-type="fig" rid="F1">Figure 1</xref> with a Preferred Reporting Items for Systematic reviews and Meta-Analyses (PRISMA) flow diagram.</p>
<fig id="F1" position="float">
<label>FIGURE 1</label>
<caption>
<p>PRISMA flow diagram, adapted from <xref ref-type="bibr" rid="B59">Page et al. (2021)</xref>.</p>
</caption>
<graphic xlink:href="frobt-11-1377897-g001.tif"/>
</fig>
<sec id="s4-1">
<title>4.1 Related surveys</title>
<p>This section evaluates a variety of comparative studies and surveys on the application of KR&#x26;R to several robotic domains. These works address robot architecture, as well as specific topics such as path planning, task decomposition, and context comprehension. However, our approach transcends these specific domains, aiming to offer a more comprehensive view of the role of ontologies in enhancing robot understanding and autonomy.</p>
<p>
<xref ref-type="bibr" rid="B31">Gayathri and Uma (2018)</xref> compare languages and planners for robotic path planning from the KR&#x26;R perspective. They discuss ontologies for spatial, semantic, and temporal representations and their corresponding reasoning. In <xref ref-type="bibr" rid="B32">Gayathri and Uma (2019)</xref>, the same authors expand their review by focusing on DL for robot task planning.</p>
<p>Closer to our perspective are articles that compare and analyze different approaches for ontology-based robotic systems, specifically those articles that focus on what to model in an ontology. <xref ref-type="bibr" rid="B23">Cornejo-Lupa et al. (2020)</xref> compare and classify ontologies for simultaneous localization and mapping (SLAM) in autonomous robots. The authors compare domain and application ontologies in terms of (i) robot information such as kinematic, sensor, pose, and trajectory information; (ii) environment mapping such as geographical, landmark, and uncertainty information; (iii) time-related information and mobile objects; and (iv) workspace information such as domain and map dimensions. They focus on one important but specific part of robot operation, autonomous navigation, and, in a particular type of robot, mobile robots.</p>
<p>
<xref ref-type="bibr" rid="B52">Manzoor et al. (2021)</xref> compare projects based on application, ideas, tools, architecture, concepts, and limitations. However, this article does not examine how architecture in the compared frameworks supports autonomy. Their review focuses on objects, environment maps, and task representations from an ontology perspective. It does not compare the different approaches regarding the robot&#x2019;s self-model. It also does not tackle the mechanisms and consequences of using such knowledge to enhance the robot&#x2019;s reliability.</p>
<p>Perhaps the most relevant review from our perspective is the one by <xref ref-type="bibr" rid="B57">Olivares-Alarcos et al. (2019)</xref>. They analyze five of the main projects that use KBs to support robot autonomy. They ground their analysis in (i) ontological terms, (ii) the capabilities that support robot autonomy, and (iii) the application domain. Moreover, they discuss robots and environment modeling. This work is closely related to the development of the recent IEEE Standard 1872.2 (<xref ref-type="bibr" rid="B42">IEEE SA, 2022</xref>).</p>
<p>Our approach differentiates itself from previous reviews because we focus on modeling not only robot actions and their environments but also engineering design knowledge. This type of knowledge is not often considered but provides a deeper understanding of the robot&#x2019;s components and its interaction, design requirements, and possible alternatives to reach a mission. We also base our comparison on explicit knowledge of the mission and how we can ensure that it satisfies the user-expected performance. For this reason, we focus on works that select, adapt, or plan actions. Our search used more flexible inclusion criteria to analyze a variety of articles, even if they address only some of the issues or their ontologies are not publicly available. We have adopted this wide perspective to draw a general picture of different approaches that build the most important capabilities for dependable autonomous robots.</p>
</sec>
<sec id="s4-2">
<title>4.2 Review scope</title>
<p>Our analysis focuses on exploring the role of ontologies in advancing the autonomy of robotic systems. For this purpose, we delve into research articles that address ontologies created or extended to select, adapt, or plan actions autonomously. We excluded studies that solely encode simulations or utilize ontologies for non-action-related tasks, aiming to concentrate on contributions directly impacting robot action. Furthermore, our scope excludes non-ontology-based approaches, even if they are important for dependability or autonomy, such as all the developments in safe-critical systems.</p>
<p>An ontology is a shared conceptualization that structures objects into classes, which can be seen as categories within the domain of discourse. While interaction with the world involves specific objects, referred to as individuals or instances, much reasoning occurs at the class level. Classes can possess properties that characterize the collection of objects they represent or are related to other classes. Additionally, they are organized through inheritance, expressed by the subclass relation. <xref ref-type="fig" rid="F2">Figure 2</xref> represents a simple ontology with partial information about zones in a manufacturing plant.</p>
<fig id="F2" position="float">
<label>FIGURE 2</label>
<caption>
<p>Simple example of manufacturing zones ontology. Classes in light blue, properties in dark blue, and individuals in gray.</p>
</caption>
<graphic xlink:href="frobt-11-1377897-g002.tif"/>
</fig>
<p>Consider the assertion of the class <monospace>ProductionZone</monospace> with the property <monospace>robot_accessible</monospace>. According to this assertion, every instance of <monospace>ProductionZone</monospace>, such as the specific area <monospace>production_01</monospace>, is considered <monospace>robot_accessible</monospace>. In this hierarchy, <monospace>Assembly</monospace> is a subclass of <monospace>ProductionZone</monospace>. Given this hierarchy, we can deduce that every instance of <monospace>AssemblyZone</monospace> inherits the properties of its superclass. Every individual of it, such as <monospace>assembly_01</monospace>, inherits the <monospace>robot_accessible</monospace> property. Zones without the property, such as <monospace>Office</monospace> or <monospace>Control Room,</monospace> are considered restricted.</p>
<p>This kind of reasoning based on classification and consistency can be used to derive new assertions about elements in the robot environment and the robot itself. In this example, the robot can use this information to traverse only the accessible areas when selecting a route to traverse the plant. Therefore, the use of knowledge-driven policies facilitates the fulfillment of safety regulations and compliance standards and can enhance human understanding of the decisions the robot is making.</p>
<p>If the ontology represented components, capabilities, and goals, these conclusions could be used to adapt the system. <xref ref-type="fig" rid="F3">Figure 3</xref> represents a robotic ontology based on components, capabilities, goals, and values to determine which design alternatives are available for the robot. Following the approach of TOMASys <xref ref-type="bibr" rid="B36">Hern&#xe1;ndez et al. (2018)</xref>, we are working on a system that selects the most suitable reconfiguration action for the robot. For example, if a component fails, the ontology can find another component that provides an equivalent capability so the robot can use it to complete the mission. This KB is also useful for determining which interfaces the system requires in that case, which metrics would be affected, and which stakeholders should be advised of the change. More information on the fundamental aspects of this ontology can be found in <xref ref-type="bibr" rid="B2">Aguado et al. (2024)</xref>.</p>
<fig id="F3" position="float">
<label>FIGURE 3</label>
<caption>
<p>Example of an ontology to formalize robotics system models and their runtime deployment to select the most appropriate reconfiguration strategy in response to unexpected circumstances. This ontology represents the robot components, capabilities, and mission goals. The objective of the ontology is to find adaptation solutions that are not predefined or <italic>ad hoc</italic>; rather, they are computed during operation based on explicit engineering knowledge from the design phase.</p>
</caption>
<graphic xlink:href="frobt-11-1377897-g003.tif"/>
</fig>
<p>The analysis developed here does not address different approaches to solving a specific problem; rather, it focuses on examining, for each framework, the capabilities explicitly represented in ontologies or those that leverage the ontology at runtime to enhance the operation of the robot.</p>
<p>The survey is centered on action-related conceptualizations, with the objective of finding the theoretical foundations and relevant applications of ontological frameworks within the field of robotics. For this reason, and especially given that most of the articles do not provide source files for the ontology, we focus on the concepts, and discussions regarding scalability, computational cost, and efficiency are not within the scope of our study.</p>
</sec>
<sec id="s4-3">
<title>4.3 Review audience</title>
<p>This survey is directed towards a specific audience that is not seeking introductory knowledge about ontologies or their basic usage. That content can be found in resources such as <xref ref-type="bibr" rid="B70">Staab and Studer (2009).</xref> For an introduction from the robotics perspective, refer to Chapter 10 in <xref ref-type="bibr" rid="B64">Russell and Norvig (2021)</xref>. Our target audience consists of people interested in understanding the practical application of concepts related to robot autonomy during robot task execution. We aim to cater to researchers, practitioners, and academics who already possess a foundational understanding of ontologies and are now seeking to explore how these concepts intersect with and enhance the execution of tasks in robotic systems.</p>
</sec>
</sec>
<sec id="s5">
<title>5 A survey of applications using ontologies for robot autonomy</title>
<p>The following sections review and compare some projects to find their specific contributions to the field of robotic ontologies. We have organized the analysis of the projects under review based on the application domain&#x2014;manipulation, navigation, social, and industrial&#x2014;in which they have been deployed. However, most of the work has a broader perspective and may be applied to other domains. Each analyzed work includes a brief description and a discussion of the above elements. Finally, each domain provides a comparative table with the most relevant aspects of each capability.</p>
<sec id="s5-1">
<title>5.1 Manipulation domain</title>
<p>In the domain of robotics, manipulation refers to the control and coordination of robotic arms, grippers, and other mechanical systems to interact with objects in the physical world. This includes a wide range of applications, from industrial automation to tasks in unstructured environments, such as household chores or healthcare assistance. In this section, most of the work under analysis focuses on domestic applications for manipulation.</p>
<sec id="s5-1-1">
<title>5.1.1 KnowRob and KnowRob-based approaches</title>
<p>KnowRob<xref ref-type="fn" rid="fn13">
<sup>13</sup>
</xref> is a framework that provides a KB and a processing system to perform complex manipulation tasks (<xref ref-type="bibr" rid="B75">Tenorth and Beetz, 2009</xref>; <xref ref-type="bibr" rid="B76">Tenorth and Beetz, 2013</xref>). KnowRob2<xref ref-type="fn" rid="fn14">
<sup>14</sup>
</xref> (<xref ref-type="bibr" rid="B9">Beetz et al., 2018</xref>) represents the second generation of the framework and serves as a bridge between vague instructions and specific motion commands required for task execution.</p>
<p>KnowRob2&#x2019;s primary objective is to determine the appropriate action parametrization based on the required motion and identify the physical effects that must be achieved or avoided. For example, if the robot is asked to pick up a cup and pour out its contents, the KB retrieves the necessary action of pouring, which includes a sub-task to grasp the source container. Subsequently, the framework queries for pre-grasp and grasp poses, along with grasp force, to establish the required motion parameters.</p>
<p>KnowRob ontology includes a spectrum of concepts related to robots, including information about their body parts, connections, sensing and action capabilities, tasks, actions, and behavior. Objects are represented with their parts, functionalities, and configuration, while context and environment are also taken into account. Additionally, the ontology incorporates temporal predicates based on event logic and time-dependent relations.</p>
<p>While KnowRob&#x2019;s initial ontology was based on Cyc (<xref ref-type="bibr" rid="B48">Lenat, 1995</xref>), which was designed to understand how the world works by representing implicit knowledge and performing human-like reasoning, Cyc has remained proprietary. OpenCyc, a public initiative related to Cyc, is no longer available. The KnowRob framework later transitioned to DUL, which was chosen for its compatibility with concepts for autonomous robots. KnowRob uses Prolog as a query and assert interface, but all perception, navigation, and manipulation actions are encoded in plans rather than Prolog queries or rules.</p>
<p>One of the main expansions of KnowRob is RoboEarth, a worldwide open-source platform that allows any robot with a network connection to generate, share, and reuse data (<xref ref-type="bibr" rid="B80">Waibel et al., 2011</xref>). It uses the principle of linked data connections through web and cloud services to speed up robot learning and adaptation in complex tasks.</p>
<p>RoboEarth uses an ontology to encode concepts and relations in maps and objects and a SLAM map that provides the geometry of the scene and the locations of objects with respect to the robot (<xref ref-type="bibr" rid="B63">Riazuelo et al., 2015</xref>). Each robot has a self-model that describes its kinematic structure and a semantic model to provide meaning to robot parts, such as a set of joints that form a gripper. This model also includes actions, their parameters, and software components, such as object recognition systems (<xref ref-type="bibr" rid="B77">Tenorth et al., 2012</xref>).</p>
<p>Another example of a KnowRob-based application is <xref ref-type="bibr" rid="B24">Crespo et al. (2018)</xref>. In this case, the focus is on using semantic concepts to annotate a SLAM map with additional conceptualizations. This application diverges somewhat from KnowRob&#x2019;s initial emphasis on robot manipulators. The work models the environment utilizing semantic concepts but specifically captures the relationships between rooms, objects, object interactions, and the utility of objects.</p>
<p>The detailed analysis of comparison criteria follows:<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Perception and categorization:</italic> KnowRob and RoboEarth incorporate inference mechanisms to abstract sensing information, particularly in the context of object recognition (<xref ref-type="bibr" rid="B9">Beetz et al., 2018</xref>; <xref ref-type="bibr" rid="B24">Crespo et al., 2018</xref>). As highlighted in <xref ref-type="bibr" rid="B76">Tenorth and Beetz (2013)</xref>, inference processes information perceived from the external environment and abstracts it to the most appropriate level while retaining the connection to the original percepts. These ontologies serve as shared conceptualizations that accommodate various data types and support various forms of reasoning: effectively handling uncertainties arising from sensor noise, limited observability, hallucinated object detection, incomplete knowledge, and unreliable or inaccurate actions (<xref ref-type="bibr" rid="B75">Tenorth and Beetz, 2009</xref>).</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Decision making and planning:</italic> KnowRob places a strong emphasis on determining action parametrizations for successful manipulation, using hybrid reasoning with the goal of <italic>reasoning with eyes and hands</italic> (<xref ref-type="bibr" rid="B9">Beetz et al., 2018</xref>).</p>
</list-item>
</list>
</p>
<p>This approach equips KnowRob with the ability to reason about specific physical effects that can be achieved or avoided through its motion capabilities. Although KnowRob&#x2019;s KB might exhibit redundancy or inconsistency, the reasoning engine computes multiple hypotheses, subjecting them to plausibility and consistency checks and ultimately selecting the most promising parametrization. The planning component of KnowRob2 is tailored for motion planning and solving inverse kinematics problems. Tasks are dynamically assembled on the basis of the robot&#x2019;s situation.<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Prediction and monitoring:</italic> KnowRob uses its ontology to represent the evolution of the state, facilitating the retrieval of semantic information and reasoning (<xref ref-type="bibr" rid="B9">Beetz et al., 2018</xref>). Through these heterogeneous processes, the framework can predict the most appropriate parameters for a given situation. However, the monitoring capabilities within this framework are limited to objects in the environment. Unsuccessful experiences are labeled and stored in the robot&#x2019;s memory, contributing to the selection of action parameters in subsequent scenarios. The framework introduces NEEMs, allowing queries about the robot&#x2019;s actions, their timing, execution details, success outcomes, the robot&#x2019;s observations, and beliefs during each action. This knowledge is used primarily during the learning process.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Reasoning:</italic> KnowRob2 incorporates a hybrid reasoning kernel comprising four KBs with their corresponding reasoning engines (<xref ref-type="bibr" rid="B9">Beetz et al., 2018</xref>):</p>
</list-item>
<list-item>
<p>&#x2022; Inner World KB: Contains CAD and mesh models of objects positioned with accurate 6D poses, enhanced with a physics simulation.</p>
</list-item>
<list-item>
<p>&#x2022; Virtual KB: Computed on demand from the data structures of the control system.</p>
</list-item>
<list-item>
<p>&#x2022; Logic KB: Comprises abstracted symbolic sensor and action data enriched with logical axioms and inference mechanisms. This type of reasoning is the focus of our discussion in this article.</p>
</list-item>
<list-item>
<p>&#x2022; Episodic Memories KB: Stores experiences of the robotic agent.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Execution:</italic> KnowRob execution is driven by competency questions to bridge the gap between undetermined instructions and action. The framework incorporates the Cognitive Robot Abstract Machine (CRAM), where one of its key functionalities is the execution of the plan. The framework provides a plan language to articulate flexible, reliable, and sensor-guided robot behavior. The executor then updates the KB with information about perception and action results, facilitating the inference of new data to make real-time control decisions (<xref ref-type="bibr" rid="B10">Beetz et al., 2010</xref>).</p>
</list-item>
</list>
</p>
<p>RoboEarth and earlier versions of KnowRob rely on action recipes for execution. Before executing an action recipe, the system verifies the availability of the skills necessary for the task and orders each action to satisfy the constraints. In cases where the robot encounters difficulties in executing a recipe, it downloads additional information to enhance its capabilities (<xref ref-type="bibr" rid="B77">Tenorth et al., 2012</xref>). Once the plan is established, the system links robot perceptions with the abstract task description given by the action recipe. RoboEarth ensures the execution of reliable actions by actively monitoring the link between robot perceptions and actions (<xref ref-type="bibr" rid="B80">Waibel et al., 2011</xref>).<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Communication and coordination:</italic> RoboEarth (<xref ref-type="bibr" rid="B77">Tenorth et al., 2012</xref>) uses a communication module to facilitate the exchange of information with the web. This involves making web requests to upload and download data, allowing the construction and updating of the KB.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Learning:</italic> KnowRob includes learning as part of its framework. It focuses on acquiring generalized models that capture how the physical effects of actions vary depending on the motion parametrization (<xref ref-type="bibr" rid="B9">Beetz et al., 2018</xref>). The learning process involves abstracting action models from the data, either by identifying a class structure among a set of entities or by grouping the observed manipulation instances according to a specific property (<xref ref-type="bibr" rid="B75">Tenorth and Beetz, 2009</xref>). KnowRob2 extends its capabilities with the Open-EASE knowledge service (<xref ref-type="bibr" rid="B11">Beetz et al., 2015</xref>), offering a platform to upload, access, and analyze NEEMs of robots involved in manipulation tasks. NEEMs use descriptions of events, objects, time, and low-level control data to establish correlations between various executions, facilitating the learning-from-experience process.</p>
</list-item>
</list>
</p>
</sec>
<sec id="s5-1-2">
<title>5.1.2 Perception and Manipulation Knowledge</title>
<p>The Perception and Manipulation Knowledge (PMK)<xref ref-type="fn" rid="fn15">
<sup>15</sup>
</xref> framework is designed for autonomous robots, with a specific focus on complex manipulation tasks that provide semantic information about objects, types, geometrical constraints, and functionalities. In concrete terms, this framework uses knowledge to support task and motion planning (TAMP) capabilities in the manipulation domain (<xref ref-type="bibr" rid="B26">Diab et al., 2019</xref>).</p>
<p>PMK ontology is grounded in IEEE Standard 1872.2 (<xref ref-type="bibr" rid="B42">IEEE SA, 2022</xref>) for knowledge representation in the robotic domain, extending it to the manipulation domain by incorporating sensor-related knowledge. This extension facilitates the link between low-level perception data and high-level knowledge for comprehensive situation analysis in planning tasks. The ontological structure of PMK comprises a meta-ontology for representing generic information, an ontology schema for domain-specific knowledge, and an ontology instance to store information about objects. These layers are organized into seven classes: <italic>feature</italic>, <italic>workspace</italic>, <italic>object</italic>, <italic>actor</italic>, <italic>sensor</italic>, <italic>context reasoning</italic>, and <italic>actions</italic>. This structure is inspired by OUR-K (<xref ref-type="bibr" rid="B50">Lim et al., 2011</xref>), which is further described in <xref ref-type="sec" rid="s5-3">Section 5.3</xref>).</p>
<p>The detailed analysis of comparison criteria follows:<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Perception and categorization:</italic> The PMK ontology incorporates RFID sensors and 2D cameras to facilitate object localization, explicitly grouping sensors to define equivalent sensing strategies. This design enables the system to dynamically select the most appropriate sensor based on the current situation. PMK establishes relationships between classes such as <italic>feature</italic>, <italic>sensor</italic>, and <italic>action.</italic> For example, it stores poses, colors, and IDs of objects obtained from images.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Decision making and planning:</italic> PMK augments TAMP parameters with data from its KB. The KB contains information on action feasibility considering object features, robot capabilities, and object states. The TAMP module utilizes this information, combining a fast-forward task planner with physics-based motion planning to determine a feasible sequence of actions. This helps determine where the robot should place an object and the associated constraints.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Reasoning:</italic> PMK reasoning targets potential manipulation actions employing description logic&#x2019;s inference for real-time information, such as object positions through spatial reasoning and relationships between entities in different classes. Inference mechanisms assess robot capabilities, action constraints, feasibility, and manipulation behaviors, facilitating the integration of TAMP with the perception module. This process yields information about constraints such as interaction parameters (e.g., friction, slip, maximum force), spatial relationships (e.g., inside, right, left), feasibility of actions (e.g., arm reachability, collisions), and action constraints related to object interactions (e.g., graspable from the handle, pushable from the body).</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Interaction and design:</italic> PMK represents interaction as manipulation constraints, specifying, for example, which part of an object is interactable, such as a handle. It also considers interaction parameters such as friction coefficient, slip, or maximum force.</p>
</list-item>
</list>
</p>
</sec>
<sec id="s5-1-3">
<title>5.1.3 Failure Interpretation and Recovery in Planning and Execution</title>
<p>Failure Interpretation and Recovery in Planning and Execution (FailRecOnt)<xref ref-type="fn" rid="fn16">
<sup>16</sup>
</xref> is an ontology-based framework featuring contingency-based task and motion planning. This innovative system empowers robots to handle uncertainty, recover from failures, and engage in effective human&#x2013;robot interactions. Grounded in the DUL ontology, it addresses failures and recovery strategies, but it also takes some concepts from CORA and SUMO for robotics and ontological foundations, respectively.</p>
<p>The framework identifies failures through the <italic>non-realized situation</italic> concept and proposes corresponding <italic>recovery strategies</italic> for actions. To improve the understanding of failure, the ontology models terms such as <italic>causal mechanism</italic>, <italic>location</italic>, <italic>time</italic>, and <italic>functional considerations</italic>, which facilitates a reasoning-based repair plan (<xref ref-type="bibr" rid="B27">Diab et al., 2020</xref>; <xref ref-type="bibr" rid="B28">Diab et al., 2021</xref>).</p>
<p>Failure ontology requires a system knowledge model in terms of <italic>tasks</italic>, <italic>roles</italic>, and <italic>object concepts</italic>. Lastly, FailRecOnt has some similarities with KnowRob; both target manipulation tasks are at least partially based on DUL and share some of the authors. Moreover, they propose using PMK as a model of the system (<xref ref-type="bibr" rid="B28">Diab et al., 2021</xref>).</p>
<p>The detailed analysis of comparison criteria follows:<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Perception and categorization:</italic> Perception in FailRecOnt is limited to action detection to detect abnormal events. For geometric information and environment categorization, the framework leverages PMK to abstract perceptual information related to the environment.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Decision making and planning:</italic> FailRecOnt is structured into three layers: planning and execution, knowledge, and an assistant low-level layer. The planning and execution layer provides task planning and a task manager module. The assistant layer manages perception and action execution for the specific robot, determining how to sense an action and checking whether a configuration is collision-free. The framework has been evaluated for a task that involves storing an object in a given tray according to its color; it can handle situations such as facing a closed or flipped box and continuing the plan (<xref ref-type="bibr" rid="B28">Diab et al., 2021</xref>).</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Prediction and monitoring:</italic> Monitoring is a crucial aspect of the FailRecOnt framework. It continuously monitors executed actions and signals a failure to the recovery module if an error occurs. The reasoning component interprets potential failures and, if possible, triggers a recovery action to repair the plan.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Reasoning:</italic> FailRecOnt ontology describes how the perception of actions should be formalized. Reasoning selects an appropriate recovery strategy depending on the kind of failure, why it happened, and if other activities are affected, etc.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Execution:</italic> FailRecOnt relies on planning for execution. The task planner generates a sequence of symbolic-level actions without geometric considerations. Geometric reasoning comes into play to establish a feasible path. During action execution, the framework monitors each manipulation action for possible failures by sensing. Reasoning is then applied to interpret potential failures, identify causes, and determine recovery strategies.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Communication and coordination:</italic> FailRecOnt incorporates the reasoning for communication failure from <xref ref-type="bibr" rid="B27">Diab et al. (2020)</xref> to address failures in scenarios where multiple agents exchange information.</p>
</list-item>
</list>
</p>
</sec>
<sec id="s5-1-4">
<title>5.1.4 Probabilistic Logic Module</title>
<p>Probabilistic Logic Module (PLM) offers a framework that integrates semantic and geometric reasoning for robotic grasping (<xref ref-type="bibr" rid="B4">Antanas et al., 2019</xref>). Specific details about the KB, such as the source files, are not publicly available, so the information provided here is derived from articles about the framework.</p>
<p>The primary focus of this work is on an ontology that generalizes similar object parts to semantically reason about the most probable part of an object to grasp, considering object properties and task constraints. This information is used to reduce the search space for possible final gripper poses. This acquired knowledge can also be transferred to objects within the same category.</p>
<p>The object ontology comprises specific objects such as <italic>cup</italic> or <italic>hammer</italic>, along with supercategories based on functionality, such as <italic>kitchen container</italic> or <italic>tool</italic>. The task ontology encodes grasping tasks with objects, such as <italic>pick and place right</italic> or <italic>pour in</italic>. Additionally, a third ontology conceptualizes object-task affordances, considering the manipulation capabilities of a two-finger gripper and the associated probability of success.</p>
<p>In using the ontology, high-level knowledge is combined with low-level learning based on visual shape features to enhance object categorization. Subsequently, high-level knowledge utilizes probabilistic logic to translate low-level visual perception into a more promising grasp planning strategy.</p>
<p>The detailed analysis of comparison criteria follows:<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Perception and categorization:</italic> This approach is based on visual perception, employing vision to identify the most suitable part of an object for grasping. The framework utilizes a low-level perception module to label visual data with semantic object parts, such as detecting the top, middle, and bottom areas of a cup and its handle. The probabilistic logic module combines this information with the affordances model.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Decision making and planning:</italic> PLM uses ontologies to support grasp planning. It integrates ontological knowledge with probabilistic logic to translate low-level visual perception into an effective grasp planning strategy. Once an object is categorized and its affordances are inferred, the task ontology determines the most likely object part to be grasped, thereby reducing the search space for possible final gripper poses. Subsequently, a low-level shape-based planner generates a trajectory for the end effector.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Prediction and monitoring:</italic> Although this framework does not specifically predict or monitor robot actions, it uses task prediction to select among alternative tasks based on their probability of success but does not actively monitor them.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Reasoning:</italic> PLM uses semantic reasoning to grasp. It selects the best grasping task based on object affordances, addressing the uncertainty of visual perception through a probabilistic approach.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Learning:</italic> Learning techniques are used to identify the visual characteristics of the shape, which are then categorized. The robot utilizes the acquired knowledge for grasp planning.</p>
</list-item>
</list>
</p>
<p>
<xref ref-type="table" rid="T1">Table 1</xref> provides a concise comparison of the four frameworks analyzed. Although all of them address perception and categorization, decision making and planning, and reasoning, the specific aspects involved depend on the perspective. Only half of the frameworks explicitly utilize their KB for execution, prediction and monitoring, communication and coordination, and learning. In particular, integration and design are addressed exclusively by the PMK framework.</p>
<table-wrap id="T1" position="float">
<label>TABLE 1</label>
<caption>
<p>Use of ontologies in the manipulation domain for perception and categorization (P/C), decision making and planning (DM/P), prediction and monitoring (P/M), reasoning (R), execution (E), communication and coordination (C/C), interaction and design (I/D) and learning (L).</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center"/>
<th align="center">KnowRob (<xref ref-type="bibr" rid="B75">Tenorth and Beetz, 2009</xref>; <xref ref-type="bibr" rid="B9">Beetz et al., 2018</xref>; <xref ref-type="bibr" rid="B76">Tenorth and Beetz, 2013</xref>; <xref ref-type="bibr" rid="B80">Waibel et al., 2011</xref>; <xref ref-type="bibr" rid="B77">Tenorth et al., 2012</xref>; <xref ref-type="bibr" rid="B24">Crespo et al., 2018</xref>; <xref ref-type="bibr" rid="B63">Riazuelo et al., 2015</xref>)</th>
<th align="center">PMK (<xref ref-type="bibr" rid="B26">Diab et al., 2019</xref>)</th>
<th align="center">FailRecOnt (<xref ref-type="bibr" rid="B28">Diab et al., 2021</xref>; <xref ref-type="bibr" rid="B27">Diab et al., 2020</xref>)</th>
<th align="center">PLM (<xref ref-type="bibr" rid="B4">Antanas et al., 2019</xref>)</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="left">P/C</td>
<td align="center">Integrate data types and object recognition</td>
<td align="center">Dynamically select the most appropriate sensor</td>
<td align="center">Action sensing to detect abnormal events</td>
<td align="center">Identify the most suitable part of an object for grasping</td>
</tr>
<tr>
<td align="left">DM/P</td>
<td align="center">Action parametrization for successful manipulation</td>
<td align="center">Task and motion planning feasibility</td>
<td align="center">How to sense an action and check if a configuration is collision-free</td>
<td align="center">Translate low-level visual perception into effective grasp planning</td>
</tr>
<tr>
<td align="left">P/M</td>
<td align="center">Predict the most appropriate parameters. Monitoring objects in the environment</td>
<td align="center">-</td>
<td align="center">Failure detection and identification of failed recovery attempts</td>
<td align="center">Task prediction to select among alternatives</td>
</tr>
<tr>
<td align="left">R</td>
<td align="center">Hybrid, symbolic reasoning for sensor and action data</td>
<td align="center">Integration of task and motion planning with the perception module</td>
<td align="center">How the perception of actions should be formalized</td>
<td align="center">Select the best grasping task based on object affordances</td>
</tr>
<tr>
<td align="left">E</td>
<td align="center">Match undetermined instructions and actions</td>
<td align="center">-</td>
<td align="center">Symbolic-level actions without geometric considerations</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">C/C</td>
<td align="center">Web exchange of information</td>
<td align="center">-</td>
<td align="center">Communication failures between multiple agents</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">I/D</td>
<td align="center">-</td>
<td align="center">Information about which part of an object is interactable, constraints</td>
<td align="center">-</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">L</td>
<td align="center">Use previous descriptions of events, objects, time, and low-level control data</td>
<td align="center">-</td>
<td align="center">-</td>
<td align="center">Categorize visual shape features</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
</sec>
<sec id="s5-2">
<title>5.2 Navigation domain</title>
<p>The navigation domain describes the challenges and techniques involved in enabling robots to autonomously move around their environment. This involves the processes of guidance, navigation, and control (GNC), incorporating elements such as computer vision and sensor fusion for perception and localization, as well as control systems and artificial intelligence for mapping, path planning, or obstacle avoidance.</p>
<sec id="s5-2-1">
<title>5.2.1 Teleological and Ontological Model for Autonomous Systems</title>
<p>Teleological and Ontological Model for Autonomous Systems (TOMASys)<xref ref-type="fn" rid="fn17">
<sup>17</sup>
</xref> is a metamodel designed to consider the functional knowledge of autonomous systems, incorporating both teleological and ontological dimensions. The teleological aspect includes engineering knowledge, which represents the intentions and purposes of system designers. The ontological dimension categorizes the structure and behavior of the system.</p>
<p>TOMASys serves as a metamodel to ensure robust operation, focusing on mission-level resilience (<xref ref-type="bibr" rid="B36">Hern&#xe1;ndez et al., 2018</xref>). This metamodel relies on a functional ontology derived from the Ontology for Autonomous Systems (OASys) (<xref ref-type="bibr" rid="B12">Bermejo-Alonso et al., 2010</xref>), establishing connections between the robot&#x2019;s architecture and its mission. The core concepts in TOMASys include functions, objectives, components, and configurations. However, it operates as a metamodel and intentionally avoids representing specific features of the operational environment, such as objects, maps, etc.</p>
<p>At the core of the TOMASys framework is the metacontroller. While a conventional controller closes a loop to maintain a system component&#x2019;s output close to a set point, the metacontroller closes a control loop on top of a system&#x2019;s functionality. This metacontroller triggers reconfiguration when the system deviates from the functional reference, allowing the robot to adapt and maintain desired behavior in the presence of failures. Explicit knowledge of mission requirements is leveraged for reconfiguration using the system&#x2019;s functional specifications captured in the ontology.</p>
<p>In practice, TOMASys has been applied to various robots and environments, particularly for navigation tasks. Examples include its application to an underwater mine explorer robot (<xref ref-type="bibr" rid="B3">Aguado et al., 2021</xref>) and a mobile robot patrolling a university campus (<xref ref-type="bibr" rid="B16">Bozhinoski et al., 2022</xref>).</p>
<p>The detailed analysis of comparison criteria follows:<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Decision making and planning:</italic> In TOMASys, the metacontrol system manages decision making by adjusting parameters and configurations to address contingencies and mission deviations. It assumes the presence of a nominal controller responsible for standard decisions. In the case of failure detection or unmet mission requirements, the metacontroller selects an appropriate configuration. The planning process is integrated into the metacontrol subsystem, where reconfiguration decisions can impact the overall system plan, potentially altering parameters, components, functionalities, or even relaxing mission objectives to ensure task accomplishment.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Prediction and monitoring:</italic> Monitoring is a critical aspect of TOMASys, providing failure models to detect contingencies or faulty components. Reconfiguration is triggered not only in the event of failure but also when mission objectives are not satisfactorily achieved. Observer modules are used to monitor reconfigurable components of the system.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Reasoning:</italic> TOMASys uses a DL reasoner for real-time system diagnosis. It propagates component failures to the system level, identifying affected functionalities and available alternatives. This reasoning process helps to select the most promising alternative to fulfill mission objectives.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Execution:</italic> The execution in TOMASys follows the monitor-analyze-plan-execute (MAPE-K) loop (<xref ref-type="bibr" rid="B40">IBM Corporation, 2005</xref>). It evaluates the mission and system state through monitoring observers, uses ontological reasoners for assessing mission objectives and propagating component failures, decides reconfigurations based on engineering and runtime knowledge, and executes the selected adaptations.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Communication and coordination:</italic> TOMASys uses its hierarchical structure to coordinate components working toward a common goal. Components utilize roles that specify parameters for specific functions, and bindings facilitate communication by connecting component roles with function specifications during execution. Bindings are crucial for detecting component failures or errors. In cases where the metacontroller cannot handle errors, a function design log informs the user.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Interaction and design:</italic> TOMASys provides a metamodel that leverages engineering models from design time to runtime. This approach aims to bridge the gap between design and operation, relying on functional and component modeling to map mission requirements to the engineering structure. The explicit dependencies between components, roles, and functions, along with specifications of required component types based on functionality, support the system&#x2019;s adaptability at runtime.</p>
</list-item>
</list>
</p>
</sec>
<sec id="s5-2-2">
<title>5.2.2 Ontology-based multi-layered robot knowledge framework</title>
<p>The Ontology-based Multi-layered Robot Knowledge Framework (OMRKF) aims to integrate high-level knowledge with perception data to enhance the intelligence of a robot in its environment (<xref ref-type="bibr" rid="B72">Suh et al., 2007</xref>). Specific details about the KB, such as the source files, are not publicly available, so the information provided here is derived from articles about the framework.</p>
<p>The framework is organized into knowledge boards, each representing four knowledge classes: perception, activity, model, and context. These classes are divided into three knowledge levels (high, middle, and low). Perception knowledge involves visual concepts, visual features, and numerical descriptions. Similarly, activity knowledge is classified into service, task, and behavior, while model knowledge includes space, objects, and their features. The context class is organized into high-level context, temporal context, and spatial context.</p>
<p>At each knowledge level, OMRKF employs three ontology layers: (a) a meta-ontology for generic knowledge, (b) an ontology schema for domain-specific knowledge, and (c) an ontology instance to ground concepts with application-specific data. The framework uses rules to define relationships between ontology layers, knowledge levels, and knowledge classes.</p>
<p>OMRKF facilitates the execution of sequenced behaviors by allowing the specification of high-level services and guiding the robot in recognizing objects even with incomplete knowledge. This capability enables robust object recognition, successful navigation, and inference of localization-related knowledge. Additionally, the framework provides a querying-asking interface through Prolog, enhancing the robot&#x2019;s interaction capabilities.</p>
<p>The detailed analysis of comparison criteria follows:<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Perception and categorization:</italic> OMRKF includes perception as one of its knowledge classes, specifically addressing the numerical descriptor class in the lower-level layer. Examples of these numerical descriptors are generated by robot sensors and image processing algorithms such as Gabor filter or scale-invariant feature transform (SIFT) (<xref ref-type="bibr" rid="B72">Suh et al., 2007</xref>).</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Decision making and planning:</italic> OMRKF uses an event calculus planner to define the sequence to execute a requested service. The framework relies on query-based reasoning to determine how to achieve a goal. In cases of insufficient knowledge, the goal is recursively subdivided into subgoals, breaking down the task into atomic functions such as <italic>go to</italic>, <italic>turn</italic>, and <italic>extract feature.</italic> Once the calculus planner generates an output, the robot follows a sequence to complete a task, such as the steps involved in a delivery mission.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Reasoning:</italic> OMRKF employs axioms, such as the inverse relation of <italic>left</italic> and <italic>right</italic> or <italic>on</italic> and <italic>under</italic>, to infer useful facts using the ontology. The framework uses Horn rules to identify concepts and relations, enhancing its reasoning capabilities.</p>
</list-item>
</list>
</p>
</sec>
<sec id="s5-2-3">
<title>5.2.3 Smart and Networked Underwater Robots in Cooperation Meshes ontology</title>
<p>The Smart and Networked Underwater Robots in Cooperation Meshes (SWARMs) ontology addresses information heterogeneity and facilitates a shared understanding among robots in the context of maritime or underwater missions (<xref ref-type="bibr" rid="B49">Li et al., 2017</xref>). Specific details about the KB, such as the source files, are not publicly available, so the information provided here is derived from articles about the ontology.</p>
<p>SWARMs leverages the probabilistic ontology PR-OWL<xref ref-type="fn" rid="fn18">
<sup>18</sup>
</xref> to annotate the uncertainty of the context based on the multi-entity Bayesian network (MEBN) theory (<xref ref-type="bibr" rid="B46">Laskey, 2008</xref>). This allows SWARMs to perform hybrid reasoning on (i) the information exchanged between robots and (ii) environmental uncertainty.</p>
<p>SWARMs establishes a core ontology to interrelate several domain-specific ontologies. The core ontology manages entities, objects, and infrastructures. These ontologies include:<list list-type="simple">
<list-item>
<p>&#x2013; <italic>Mission and Planning Ontology</italic>: Provides a general representation of the entire mission and the associated planning procedures.</p>
</list-item>
<list-item>
<p>&#x2013; <italic>Robotic Vehicle Ontology</italic>: Captures information on underwater or surface vehicles and robots.</p>
</list-item>
<list-item>
<p>&#x2013; <italic>Environment Ontology</italic>: Characterizes the environment through recognition and sensing.</p>
</list-item>
<list-item>
<p>&#x2013; <italic>Communication and Networking Ontology</italic>: Describes the communication links available in SWARMs to interconnect different agents involved in the mission, enabling communication between the underwater segment and the surface.</p>
</list-item>
<list-item>
<p>&#x2013; <italic>Application Ontology</italic>: Provides information on scenarios and their requirements. PR-OWL is included in this layer to handle uncertainty.</p>
</list-item>
</list>
</p>
<p>
<xref ref-type="bibr" rid="B49">Li et al. (2017)</xref> present an example using SWARMa to monitor chemical pollution based on a probability distribution. SWARMs incorporates this model into the ontology and uses MEBN to deduce the emergency level of the polluted sea region.</p>
<p>The detailed analysis of comparison criteria follows:<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Perception and categorization:</italic> The SWARMs ontology provides a shared framework to represent the underwater environment. For this reason, it contains classes on sensors and the main concepts of the environment to understand it through its properties, such as water salinity, conductivity, temperature, and currents. Uncertainty reasoning is critical for the categorization of sensor information, especially in harsh maritime and underwater environments.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Decision making and planning:</italic> SWARMs uses two levels of abstraction. High-level planning allows the user to describe different tasks related to operations without specifying the exact actions that each robotic vehicle must perform. Low-level planning is performed on each robot to generate waypoints, actions, and other similar low-level tasks.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Reasoning:</italic> SWARMs uses a hybrid context reasoner that combines ontological rule-based reasoning with MEBN for probabilistic annotations.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Communication and coordination:</italic> A main concern in SWARMs is cooperation; robots share tasks, operations, and actions. The ontology provides transparent information sharing to support the heterogeneity of the data. It also provides an abstraction for communication and networking, describing the communication links available from command control stations to vehicles and from vehicles to command control stations.</p>
</list-item>
</list>
</p>
</sec>
<sec id="s5-2-4">
<title>5.2.4 Robot Task Planning Ontology</title>
<p>The Robot Task Planning Ontology (RTPO) <xref ref-type="bibr" rid="B74">Sun et al. (2019b)</xref> is an effective knowledge representation framework for robot task planning. Specific details about the KB, such as the source files, are not publicly available, so the information provided here is derived from articles about the ontology.</p>
<p>Designed to accommodate temporal, spatial, continuous, and discrete information, RTPO prioritizes scalability and responsiveness to ensure practicality in task planning. The ontology comprises three main components: robot, environment, and task.<list list-type="simple">
<list-item>
<p>&#x2013; <italic>Robot Ontology</italic>: Comprises hardware and software details, location information, dynamic data, and more. Sensors are explicitly modeled as a subclass of hardware, specifying the measurable aspects of the environment. In an experimental context, the robot&#x2019;s perception is limited to obstacles.</p>
</list-item>
<list-item>
<p>&#x2013; <italic>Environment Ontology</italic>: Focuses on location and recognition of humans and objects, the environment map, and information collected from other robots.</p>
</list-item>
<list-item>
<p>&#x2013; <italic>Task Ontology</italic>: Aims to understand how to decompose high-level tasks into atomic actions and adapt plans when the environment changes.</p>
</list-item>
</list>This multi-ontology approach allows RTPO to capture the details of robot task planning by representing both the robot&#x2019;s internal state and its interactions with the environment.</p>
<p>The detailed analysis of comparison criteria follows:<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Perception and categorization:</italic> The robot ontology in RTPO considers sensors as a subclass of hardware, specifying measurable aspects of the environment. In the experiment discussed, the robot&#x2019;s perception is limited to detecting obstacles.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Decision making and planning:</italic> Task planning is performed using a domain and a problem file, as in the Planning Domain Definition Language (PDDL). The algorithm described by <xref ref-type="bibr" rid="B74">Sun et al. (2019b)</xref> generates and uses these files.</p>
</list-item>
</list>
</p>
<p>The task planning process is realized by matching the execution preconditions of atomic actions and their effects on the environment from the initial state to the goal state. With this approach, the task planning module can also be executed by changing the input tasks while considering the present action resources. The plans generated by the task planning algorithm are added to the ontology to improve the efficiency of task planning if the same task needs to be planned again.<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Reasoning:</italic> The reasoning process in RTPO involves updating and storing the knowledge within the ontology. The scalability of robot knowledge aims to enhance the efficiency of reasoning. Experimental scenarios involving the addition of elements to the indoor environment and corresponding KB instances demonstrate changes in consumed time, particularly affecting knowledge query speed. The authors show real-time performance in an application that involves 52,000 individuals, although the impact on the planning process is not explicitly detailed.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Communication and coordination:</italic> This process is not explicitly explained by (<xref ref-type="bibr" rid="B74">Sun et al. 2019b</xref>). However, a scenario with three robots and two humans is described. Communication among the three robots is highlighted, emphasizing knowledge sharing. The relationships between these entities can be defined by users or developers based on their requirements. In situations with various robots mapping different rooms and using various sensors, the ontology facilitates linking and adding knowledge to constraints to maintain coherence.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Learning:</italic> RTPO incorporates learning by updating and adding the plans generated by the task planning algorithm into the ontology. This iterative process aims to improve the efficiency of future task planning, especially when the same task is encountered again.</p>
</list-item>
</list>
</p>
</sec>
<sec id="s5-2-5">
<title>5.2.5 Guidance, navigation, and control for planetary rovers</title>
<p>
<xref ref-type="bibr" rid="B20">Burroughes and Gao (2016)</xref> present an architectural solution to address limitations in autonomous software and GNC structures designed for extraterrestrial planetary exploration rovers. Specific details about the KB, such as the source files, are not publicly available, so the information provided here is derived from articles about the framework.</p>
<p>This framework uses an ontology to facilitate the autonomous reconfiguration of mission goals, software architecture, software components, and the control of hardware components during runtime. To manage complexity, the self-reconfiguration ontology is organized into modules. The base ontology serves as an upper ontology, including modules that delineate logic, numeric aspects, temporality, fuzziness, confidences, processes, and block diagrams. Additional modules describe the functions of software, hardware, and the environment.</p>
<p>The primary focus of this framework is reconfiguration. Once the ontology manager detects an undesired state change through the monitoring process, it activates a safety mode. In this safety mode, the system can execute either a reactive plan or create a new plan based on inferences drawn from the new situation.</p>
<p>Following the replanning process, new mission goals are established, allowing the robot to exit safety mode and resume normal operation. The framework specifically aims to minimize odometry errors and ensure safety during travel. To achieve this objective, the connective architecture and processes, such as navigation, localization, control, mapping, as well as sensors and the locomotion system, can be fine-tuned and optimized according to the environment and faulty hardware conditions. For example, certain methods may prioritize tolerance to sensor noise over absolute accuracy in localization.</p>
<p>The detailed analysis of comparison criteria follows:<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Decision making and planning:</italic> <xref ref-type="bibr" rid="B20">Burroughes and Gao (2016)</xref> integrate a reactive approach with a deliberative layer for quick responses. Precalculated responses are prepared for likely changes, but in the absence of options, the rational agent resorts to deliberative techniques. Ontologies and the PDDL are used for knowledge representation and planning, respectively. Actions correspond to specific configurations of services, with plans defined using the initial state of the world, the goal state, the resources of the system, the safety criteria, and the rules. The approach employs a pruning algorithm to reduce possible actions and planning space.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Prediction and monitoring:</italic> The focus is on replanning, requiring monitoring to trigger the process. Generic inspectors perform network, resource, and state checks, and specific inspectors manage tasks like checking camera performance, monitoring, and updating the ontology on the current state of the world. The system can decide the depth of monitoring for each subsystem, balancing computational resources and self-protection.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Reasoning:</italic> Reasoning is used to configure the software elements of the rover, update the state of the world, and decide whether the system should re-plan to adapt to changes or use pre-established reactive responses. The ontology checks for knowledge incoherence when adding new information.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Execution:</italic> The MAPE-K loop is used for self-reconfiguration. When the monitor detects a change, the ontology provides the knowledge to select how the system should evolve. The configuration of the components is established through planning or reactivity. Navigation and operation components are organized into modular services with self-contained functionality to allow reconfiguration.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Communication and coordination:</italic> Communication requirements, such as publication rate, conditions, and effects, are used to establish appropriate communication links between modules, treating communication as a reconfigurable service within the framework.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Interaction and design:</italic> While not explicitly detailing the design or requirements, the system reasons in terms of service capacities, considering measures such as accuracy or suitability for sensor noise in sensor processing algorithms. It also incorporates safety criteria to select system changes, providing design and engineering knowledge to select alternative designs based on runtime situations.</p>
</list-item>
</list>
</p>
</sec>
<sec id="s5-2-6">
<title>5.2.6 Collaborative context awareness in search and rescue missions</title>
<p>
<xref ref-type="bibr" rid="B21">Chandra and Rocha (2016)</xref> present a framework for collaborative context awareness using an ontology that comprises high-level aspects of urban search and rescue (USAR) missions. Specific details about the KB, such as the source files, are not publicly available, so the information provided here is derived from articles about the framework.</p>
<p>The framework serves as an efficient knowledge-sharing platform to represent and correlate various mission concepts, including those related to agents and their capabilities, scenarios, and teams. The ontology facilitates the sharing of homogeneous knowledge among all robots and supports human&#x2013;robot collaboration by reasoning based on rules provided by humans.</p>
<p>The detailed analysis of comparison criteria follows:<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Perception and categorization:</italic> The system employs perceived and pre-processed information gathered from its own sensors, as well as from other agents, such as humans and robots, to continually update its KB. Specifically, it focuses on entities within context classes and their relationships, including information about smoke levels, visibility, location, and temperature.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Decision making and planning:</italic> The framework offers an efficient knowledge-sharing strategy that improves decision-making processes. For example, it facilitates the management of a global map with shared events and real-time tracking of agent locations.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Reasoning:</italic> In this framework, reasoning plays a crucial role in storing and disseminating information between agents. The KB retains essential details such as location, temperature, visibility, battery status, tasks, and detection of victims or fires. Furthermore, reasoning contributes to resilience against communication failures by storing information for future sharing. This process supports coordination, including the incorporation of new team members or the temporary removal and subsequent reintegration of teammates.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Communication and coordination:</italic> Building on a foundation of multirobot cooperation, <xref ref-type="bibr" rid="B21">Chandra and Rocha (2016)</xref> structure the framework to represent the team and mission within an ontology. This enables the creation of a global map and the selection of suitable candidates for various tasks. Examples of coordination include telepresence and compensating for a teammate&#x2019;s immobility. Furthermore, the framework ensures resilience in the face of communication failures. For example, all events detected by a robot are logged in the local KB and shared across the team to synchronize knowledge. In situations of communication loss or isolation from teammates, a list of unattended events is maintained and shared after communication is restored.</p>
</list-item>
</list>
</p>
</sec>
<sec id="s5-2-7">
<title>5.2.7 Autonomous vehicle situation assessment and decision making</title>
<p>
<xref ref-type="bibr" rid="B38">Huang et al. (2019)</xref> use ontologies for situation assessment and decision making in the context of autonomous vehicles navigating urban environments. Specific details about the KB, such as the source files, are not publicly available, so the information provided here is derived from articles about the ontologies.</p>
<p>The KB integrates vehicle information, storing details of the permissible <italic>directions</italic> a vehicle can take. Furthermore, the KB includes representations of both static and dynamic obstacles, as well as relevant information on the characteristics of roads, distinguishing between <italic>highways</italic> and <italic>urban roads</italic>. The ontology incorporates specific scenarios that the autonomous vehicle could encounter on the road, such as proximity to an <italic>intersection</italic>, traversing a <italic>bridge</italic>, or executing a <italic>U-turn</italic>. The autonomous driving system leverages this KB to assess the current driving scenario, facilitating well-informed decisions on whether to maintain its current trajectory or initiate a lane change.</p>
<p>The detailed analysis of comparison criteria follows:<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Decision making and planning:</italic> The decision-making process is tied to situation assessment, employing a methodology that evaluates the safety of the surroundings of the vehicle. This involves characterizing the regions around the car and assigning a binary safety value based on the presence of obstacles.</p>
</list-item>
</list>
</p>
<p>If a region is considered safe, the vehicle continues in its current lane; otherwise, a lane change is initiated. This decision-making step incorporates statistical indicators that account for velocity. Moreover, the model considers legitimacy by adhering to traffic rules during lane changes and reasonableness by querying the global planning path to identify the next road segment or lane, particularly when approaching intersections. This strategic approach prevents the system from optimizing locally at the expense of compromising the overarching global plan.<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Reasoning:</italic> The reasoner is used to generate behavioral decisions. It employs rules derived from traffic regulations and driving experiences, taking into account various factors that influence the road, such as speed limits, traffic lights, and the presence of surrounding obstacles.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Interaction and design:</italic> Although the framework does not explicitly include concepts as design decisions, it addresses requirements such as legality by incorporating traffic rules and reasonableness. This ensures that the behavior of the lane change aligns with the main goal of global planning, avoiding changes to local optimization that may compromise the broader strategic plan.</p>
</list-item>
</list>
</p>
</sec>
<sec id="s5-2-8">
<title>5.2.8 Search and rescue scenario</title>
<p>
<xref ref-type="bibr" rid="B73">Sun et al. (2019a)</xref> introduce an ontology tailored for search and rescue (SAR), enhancing the decision-making capabilities of robots in complex and unpredictable scenarios. Specific details about the KB, such as the source files, are not publicly available, so the information provided here is derived from articles about the ontology. The SAR ontology comprises three interlinked subontologies: an <italic>entity</italic> ontology, an <italic>environment</italic> ontology, and a <italic>task</italic> ontology.<list list-type="simple">
<list-item>
<p>&#x2013; The <italic>entity</italic> ontology includes various types of robots, including ground, underwater, and air robots. It delineates their constituent parts and specifications in terms of hardware and software aspects.</p>
</list-item>
<list-item>
<p>&#x2013; The <italic>environment</italic> ontology extends the scope to store most of the elements present in SAR scenarios, including the environment map and objects that shall be recognized. Updated knowledge from the environment can be shared among other robots, although the specific mechanisms are not detailed in the presented use case.</p>
</list-item>
<list-item>
<p>&#x2013; The <italic>task</italic> ontology encapsulates the task-related knowledge that is necessary for informed decision making. This involves task decomposition and allocation facilitated by a hierarchical structure. The ontology defines four typical tasks: <italic>charge</italic>, <italic>search</italic>, <italic>rescue</italic>, and <italic>recognize.</italic> Additionally, atomic actions are articulated by their effects on the state of the environment. The framework proposes a task planning algorithm that aligns the preconditions of execution with the effects on the environment, utilizing the SAR ontology as a foundational framework.</p>
</list-item>
</list>
</p>
<p>The detailed analysis of comparison criteria follows:<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Perception and categorization:</italic> The SAR framework focuses on SLAM and autonomous navigation. The authors use a semantic map, which facilitates the recognition and localization of objects. The acquired information dynamically updates the environment ontology, establishing connections between the SLAM map and the semantic details. Bayesian reasoning enhances the precision of victim positioning, while QR code scanning streamlines the acquisition of semantic information, such as vital signs (e.g., heart rate and blood pressure), in disaster rescue scenarios.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Decision making and planning:</italic> decision making in this framework is based on structured queries. It begins by defining tasks and identifying the requisite actions, followed by a comprehensive examination of the action properties, including time constraints, preconditions, and postconditions, to achieve the desired state. The planner then specifies a sequenced set of atomic actions. The program can adopt specific search algorithms for planning or reusing previously established plans.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Reasoning:</italic> Before planning, the robot conducts a preliminary assessment to determine the suitability of the task for the current state. If considered appropriate, the planning phase starts, identifying the tasks the robot should execute under the given circumstances.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Execution:</italic> The robot systematically executes the sequence of atomic actions. When faced with a previously planned task, the robot can query the task definition, retrieving the corresponding atomic action sequence.</p>
</list-item>
</list>
</p>
<p>
<xref ref-type="table" rid="T2">Tables 2</xref> and <xref ref-type="table" rid="T3">3</xref> summarize studies in the navigation domain. All frameworks address decision making, planning, and reasoning, mainly to organize tasks. Most of the works focus on perceiving and categorizing measurable aspects of the environment, along with communication and coordination among different elements and systems. TOMASys, the planetary rover scenario, and the SAR scenario explicitly handle prediction, monitoring, and execution. The use of engineering knowledge&#x2014;interaction and design&#x2014;is explicitly addressed in TOMASys, the planetary rover scenario, and the autonomous vehicle scenario. Learning is applied only in RTPO to improve the plan generation process.</p>
<table-wrap id="T2" position="float">
<label>TABLE 2</label>
<caption>
<p>Part 1: Use of ontologies in the navigation domain for perception and categorization (P/C), decision making and planning (DM/P), prediction and monitoring (P/M), reasoning (R), execution (E), communication and coordination (C/C), interaction and design (I/D) and learning (L).</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center"/>
<th align="center">TOMASys (<xref ref-type="bibr" rid="B36">Hern&#xe1;ndez et al., 2018;</xref>
<xref ref-type="bibr" rid="B16">Bozhinoski et al., 2022</xref>; <xref ref-type="bibr" rid="B3">Aguado et al., 2021</xref>)</th>
<th align="center">OMRKF (<xref ref-type="bibr" rid="B72">Suh et al., 2007</xref>)</th>
<th align="center">SWARMs (<xref ref-type="bibr" rid="B49">Li et al., 2017</xref>)</th>
<th align="center">RTPO (<xref ref-type="bibr" rid="B74">Sun et al., 2019b</xref>)</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="left">P/C</td>
<td align="center">-</td>
<td align="center">Lower-lever perception features such as numerical descriptors</td>
<td align="center">Represent underwater environment properties and sensors</td>
<td align="center">Specification of measurable aspects of the environment</td>
</tr>
<tr>
<td align="left">DM/P</td>
<td align="center">Adjust parameters and configurations to address mission contingencies</td>
<td align="center">Calculus planner to accomplish goals and subgoals</td>
<td align="center">Task-level planning and low-level planning to generate waypoints, actions, etc.</td>
<td align="center">Generate and use domains and problem files to generate plans</td>
</tr>
<tr>
<td align="left">P/M</td>
<td align="center">Failure models to detect faulty components and goals not achieved</td>
<td align="center">-</td>
<td align="center">-</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">R</td>
<td align="center">Propagate failures to system level, identify affected functionalities and available alternatives</td>
<td align="center">Geometrical relationships between objects</td>
<td align="center">Hybrid context reasoner: rule-based reasoning and probabilistic annotations</td>
<td align="center">Evaluation of real-time performance in reasoning with 52,000 elements of indoor environments</td>
</tr>
<tr>
<td align="left">E</td>
<td align="center">MAPE-K loop to evaluate mission status</td>
<td align="center">-</td>
<td align="center">-</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">C/C</td>
<td align="center">Component coordination</td>
<td align="center">-</td>
<td align="center">Robots share tasks, operations, and actions</td>
<td align="center">Knowledge sharing between three robots and two humans</td>
</tr>
<tr>
<td align="left">I/D</td>
<td align="center">Use of metamodels to bridge the gap between design and operation</td>
<td align="center">-</td>
<td align="center">-</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">L</td>
<td align="center">-</td>
<td align="center">-</td>
<td align="center">-</td>
<td align="center">Update and add plans generated by the task planning algorithm back into the ontology</td>
</tr>
</tbody>
</table>
</table-wrap>
<table-wrap id="T3" position="float">
<label>TABLE 3</label>
<caption>
<p>Part 2: Use of ontologies in the navigation domain for perception and categorization (P/C), decision making and planning (DM/P), prediction and monitoring (P/M), reasoning (R), execution (E), communication and coordination (C/C), interaction and design (I/D) and learning (L).</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center"/>
<th align="center">Planetary rover scenario (<xref ref-type="bibr" rid="B20">Burroughes and Gao, 2016</xref>)</th>
<th align="center">USAR scenario (<xref ref-type="bibr" rid="B21">Chandra and Rocha, 2016</xref>)</th>
<th align="center">Autonomous vehicle scenario (<xref ref-type="bibr" rid="B38">Huang et al., 2019</xref>)</th>
<th align="center">SAR scenario (<xref ref-type="bibr" rid="B73">Sun et al., 2019a</xref>)</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="left">P/C</td>
<td align="center">-</td>
<td align="center">Pre-processed information from sensors and other intelligent agents</td>
<td align="center">-</td>
<td align="center">Semantic map for recognizing and localizing objects</td>
</tr>
<tr>
<td align="left">DM/P</td>
<td align="center">Precalculated solutions for likely changes, combined with deliberative techniques</td>
<td align="center">Management of a global map with shared events and real-time tracking of agent locations</td>
<td align="center">Evaluate the safety of the vehicle&#x2019;s surroundings with statistical indicators</td>
<td align="center">Definition of tasks and identification of requisite actions and their properties</td>
</tr>
<tr>
<td align="left">P/M</td>
<td align="center">Monitor resources and state checks to trigger replanning</td>
<td align="center">-</td>
<td align="center">-</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">R</td>
<td align="center">Configure SW elements, update world state, and decide on replanning</td>
<td align="center">Store and distribute information among agents</td>
<td align="center">Apply rules derived from traffic regulations and driving experiences</td>
<td align="center">Evaluate the suitability of the task for the current state</td>
</tr>
<tr>
<td align="left">E</td>
<td align="center">MAPE-K loop for reconfiguration</td>
<td align="center">-</td>
<td align="center">-</td>
<td align="center">Query task definition to retrieve the corresponding atomic action sequence</td>
</tr>
<tr>
<td align="left">C/C</td>
<td align="center">Communication requirements between modules</td>
<td align="center">Multirobot cooperation, global map, and selection of suitable candidates for each task</td>
<td align="center">-</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">I/D</td>
<td align="center">Explicit service capacities</td>
<td align="center">-</td>
<td align="center">Addresses requirements such as legality by incorporating traffic rules and reasonableness</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">L</td>
<td align="center">-</td>
<td align="center">-</td>
<td align="center">-</td>
<td align="center">-</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
</sec>
<sec id="s5-3">
<title>5.3 Social domain</title>
<p>Social robots usually refer to the interaction between robots and humans in a variety of contexts, such as homes, healthcare, education, entertainment, and public spaces. The goal is to create robots that are not only technically capable but also socially aware and able to interact with humans in a manner that is natural, intuitive, and socially acceptable.</p>
<sec id="s5-3-1">
<title>5.3.1 Ontology-based unified robot knowledge</title>
<p>The Ontology-based Unified Robot Knowledge (OUR-K) framework for service robots (<xref ref-type="bibr" rid="B50">Lim et al., 2011</xref>) consists of five knowledge classes: features, objects, spaces, contexts, and actions. It takes OMRKF, the concept of layer division, from its predecessor. Although OMRKF was originally evaluated in navigation domains, OUR-K extends its application to social robots operating within domestic environments. Specific details about the KB, such as the source files, are not publicly available, so the information provided here is derived from articles about the framework.</p>
<p>A notable feature of OUR-K is its ability to perform tasks even when provided with incomplete information. The framework incorporates a knowledge description of both the robot and its environment, employing algorithms for knowledge association. This involves logic, Bayesian inference, and heuristics; however, logical inference in OUR-K is specifically limited to performing associations between classes and ontological levels, with no indication of alternative inference mechanisms in the literature.</p>
<p>OUR-K includes mechanisms for object recognition, context modeling, task planning, space representation, and navigation. Regarding action representation, its descriptions are simpler and do not contemplate processes as did its predecessor, OMRKF.</p>
<p>
<xref ref-type="bibr" rid="B25">Diab et al. (2018)</xref> extend OUR-K with a physics-based manipulation ontology to address the challenges that a motion planner might encounter. An actor class is introduced within the knowledge classes to describe the working constraints of the robot, enhancing the planner&#x2019;s capability to handle interaction dynamics. In addition, the authors propose a prediction mechanism for the entire OUR-K framework. Instead of relying on inferences, a semantic map is generated for categorizing and assigning manipulation constraints, using reasoning based on logical axioms. This approach is evaluated in the context of a specific manipulation task, where a robot serves a liquid drink contained in a can.</p>
<p>The detailed analysis of comparison criteria follows:<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Perception and categorization:</italic> OUR-K follows the same approach as OMRKF. Perception is abstracted and stored in the feature, space, and object classes. The feature class defines the same knowledge level as the OMRKF. The space class defines a topological map in the middle level and a semantic map in the higher one. The object class middle level includes the object name and function, whereas the top layer defines generic information and relationships among objects; for example, a cup is a type of container.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Decision making and planning:</italic> The OMRKF successor, OUR-K (<xref ref-type="bibr" rid="B50">Lim et al., 2011</xref>), uses the same structure based on the abductive event calculus planner to reach a hierarchical abstraction of space elements and behaviors. High-level tasks, such as <italic>delivery</italic>, are decomposed into mid-level sub-tasks, such as <italic>go to goal space</italic>, <italic>find object</italic>, or <italic>generate context.</italic> These sub-tasks are further planned as sequences of primitive behaviors, such as <italic>go to</italic> or <italic>recognize object.</italic> The approach used in <xref ref-type="bibr" rid="B25">Diab et al. (2018)</xref> based on OUR-K also integrates the three levels of the action class for planning. The planner consults the topological map to determine which object (or robot) occupies which space, and then the semantic map is used to extract object and robot constraints concerning the action. This results in a sequence of actions that may consider contextual information, particularly at the temporal level.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Prediction and monitoring:</italic> OUR-K includes rules for navigation monitoring and missing object recognition tasks. However, monitoring is not treated as a distinct process in this framework; instead, it is represented as rules that use several knowledge classes.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Reasoning:</italic> Like OMRKF, OUR-K relies on logical inference to associate classes and ontological levels. The bidirectional links between low-level data and high-level knowledge enable both frameworks to fill in missing information, contributing to mission accomplishment.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Execution:</italic> OUR-K execution is plan based, where the robot follows the plan and executes a sequence of actions. However, action knowledge is coupled with all other concepts to represent world environments using features such as sensory-motor coordination, object action complex, and affordances. This approach allows robots to perform actions without explicit planning, potentially enabling reactive behavior when necessary (<xref ref-type="bibr" rid="B50">Lim et al., 2011</xref>).</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Interaction and design:</italic> The OUR-K extension presented by <xref ref-type="bibr" rid="B25">Diab et al. (2018)</xref> introduces dynamic interaction, focusing on how robotic controllers should adapt to runtime situations. This extension provides information on how a motion planner should handle dynamic forces when manipulating objects, enhancing the framework&#x2019;s capability to deal with real-time interactions.</p>
</list-item>
</list>
</p>
</sec>
<sec id="s5-3-2">
<title>5.3.2 OpenRobots Common Sense Ontology</title>
<p>The OpenRobots Common Sense Ontology (ORO) (<xref ref-type="bibr" rid="B47">Lemaignan et al., 2010</xref>) establishes a knowledge processing framework and a common sense ontology tailored for facilitating semantic-rich human&#x2013;robot interaction environments<xref ref-type="fn" rid="fn19">
<sup>19</sup>
</xref>. This approach focuses on conceptualization but offers flexibility for implementing other cognitive functions simultaneously, such as object recognition, task planning, or reasoning. Cooperation is a crucial aspect in ORO, as it targets human&#x2013;robot interactions.</p>
<p>ORO ontology is based on OpenCyc. The authors specify in the project Wiki<xref ref-type="fn" rid="fn20">
<sup>20</sup>
</xref> that it shares most of its concepts with the first version of the KnowRob ontology. It includes categories, such as <italic>spatial thing</italic> or <italic>action,</italic> and more concrete concepts, such as <italic>event</italic> or <italic>book</italic>. The authors evaluated their approach by showing robot objects and asking humans about their properties.</p>
<p>The detailed analysis of comparison criteria follows:<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Perception and categorization:</italic> The authors use several algorithms, such as common ancestors or calculating the best discriminant to categorize perceptions. Discrimination is an important element in human&#x2013;robot collaboration. For example, if a user asks the robot to bring the bottle and two bottles are available, it can use its ability to discriminate to select the best option.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Reasoning:</italic> ORO provides ontological reasoning, as well as external modules that trigger when an event occurs. External modules are used to provide reactive responses. For example, when a human asks the robot to bring an object, the robot creates an instance of this desire. Statements are stored in different memory profiles, such as long-term and short-term memory. Each profile is characterized by a lifetime that is assigned to the stored facts; when a lifetime ends, the ontology removes the fact.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Execution:</italic> The framework integrates CRAM (<xref ref-type="bibr" rid="B10">Beetz et al., 2010</xref>) to automatically update the ORO server when an object enters or exits the field of view. Execution is query-based, involving combinations of patterns like <italic>is the bottle on the table?</italic> or filters such as <italic>weight &#x3c; 150.</italic>
</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Communication and coordination:</italic> ORO is designed as an intelligent blackboard that allows various modules to push or pull knowledge to and from a central repository. This facilitates knowledge sharing among agents. Examples of heterogeneity with shared information include event registration, categorization capabilities, and the existence of different memory profiles.</p>
</list-item>
</list>
</p>
<p>Each agent has an alternative cognitive model for the other agents with whom it has interacted. When ORO identifies a new agent, it automatically creates a new separate model that can be shared with others. This feature enables the storage and reasoning of different and potentially globally inconsistent models of the world.</p>
</sec>
<sec id="s5-3-3">
<title>5.3.3 Ontology for Collaborative Robotics and Adaptation</title>
<p>Ontology for Collaborative Robotics and Adaptation (OCRA)<xref ref-type="fn" rid="fn21">
<sup>21</sup>
</xref>, as described by <xref ref-type="bibr" rid="B58">Olivares-Alarcos et al. (2022)</xref>, is a specialized ontology designed to represent relevant knowledge in collaborative scenarios, facilitating plan adaptation. Based on KnowRob (<xref ref-type="bibr" rid="B75">Tenorth and Beetz, 2009</xref>; <xref ref-type="bibr" rid="B9">Beetz et al., 2018</xref>) and its upper ontology, DUL, OCRA shares the support of its predecessor for the temporal history of the KB through episodic memories.</p>
<p>This work primarily employs FOL definitions to establish a foundation for reliable, collaborative robots, with the aim of enhancing the interoperability and reusability of terminology within this domain. The ontology serves as a tool for the robot to address competency questions, such as identifying ongoing collaborations, understanding current plans and goals, determining the agents involved, and assessing plans before and after adaptation.</p>
<p>This ontology has been qualitatively validated for human&#x2013;robot cooperation, sharing the task of filling the compartments of a tray. The main asset of OCRA, from our perspective, is its explicit representation of collaboration requirements, including safety considerations and a measure of risks, with the objective of effective plan adaptation.</p>
<p>The detailed analysis of comparison criteria follows:<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Decision making and planning:</italic> OCRA uses ontological knowledge for dynamic plan adaptation during runtime. For example, if the robot had a plan to fill a certain compartment and it is not empty, it adapts to fill another empty compartment. The ontology also stores the adaptation triggers.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Reasoning:</italic> As stated above, this work focuses on answering competency questions related to agents involved in collaboration, their plans, goals, and the adaptation of plans when required.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Communication and coordination:</italic> OCRA focuses on collaboration with humans, providing a mechanism to explain its plan adaptation through the ontology. This collaboration is enabled through coordination in terms of the plan to solve the task. Specifically, the robot changes its plan according to variations in the environment, such as an already-filled compartment.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Learning:</italic> While not explicitly implemented in the current work, OCRA mentions future plans to incorporate episodic memories for learning tasks. Examples include modeling the preferences of different users or learning the structure of tasks to generalize to new ones.</p>
</list-item>
</list>
</p>
</sec>
<sec id="s5-3-4">
<title>5.3.4 Intelligent Service Robot Ontology</title>
<p>Intelligent Service Robot Ontology (ISRO) (<xref ref-type="bibr" rid="B22">Chang et al., 2020</xref>) introduces an ontology-based model tailored for human&#x2013;robot interaction. The practical application of this approach is demonstrated through the implementation of a social robot that functions as a medical receptionist in a hospital setting. Specific details about the KB, such as the source files, are not publicly available, so the information provided here is derived from articles about the ontology.</p>
<p>ISRO serves as an abstract knowledge management system designed to comprehend information about agents, encompassing both users and robots, as well as their environment. The ontology establishes connections between user knowledge and the robot&#x2019;s actions and behaviors, incorporating considerations for the spatial and temporal environment. This integration is facilitated through the Artificial Robot Brain Intelligence (ARBI) framework, which includes a task planner, a context reasoner, and a knowledge manager.</p>
<p>ISRO is not limited to a specific domain because it provides a high-level scheme for dynamic generation and management of information. The ontology is divided into four sub-models:<list list-type="simple">
<list-item>
<p>&#x2013; <italic>User</italic> ontology to store profile information.</p>
</list-item>
<list-item>
<p>&#x2013; <italic>Robot</italic> ontology to define the robot type, components, and capabilities.</p>
</list-item>
<list-item>
<p>&#x2013; <italic>Perception</italic> and <italic>environment</italic> to define objects and their attributes, maps, places, temporal events, and relations such as before, after, etc.</p>
</list-item>
<list-item>
<p>&#x2013; <italic>Action</italic> ontology to define the actions required to perform a task and the expected events in such situations.</p>
</list-item>
</list>
</p>
<p>The detailed analysis of comparison criteria follows:<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Perception and categorization:</italic> The framework uses sensor information to recognize the user involved, their face, gender, and age, and recognize their state, that is, the user&#x2019;s expression, in its application. It also senses the robot&#x2019;s pose to guide the user to the medical department. Additionally, the framework is also prepared to handle information related to spaces and objects that was not defined in the experiment.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Decision making and planning:</italic> The ARBI framework uses path planning to move the robot, specifically, to guide patients to the correct medical department. It is based on JAM architecture (<xref ref-type="bibr" rid="B39">Huber, 1999</xref>), which defines goals and plans using the belief, desire, and intention (BDI) agent (<xref ref-type="bibr" rid="B22">Chang et al., 2020</xref>). The path is produced using semantic spatial knowledge, defining the spaces the robot shall traverse and relationships between spaces such as <italic>connected to.</italic> The semantic path is translated into topological waypoints using knowledge about objects and a map. This path is stored in the KB and shared between robots.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Reasoning:</italic> The knowledge manager infers spatial and temporal information, such as the relationships of currently recognized objects and the time intervals between events. It also characterizes users. It uses Prolog to recognize dynamically generated information. However, only information considered important or critical is stored in the KB as static information.</p>
</list-item>
</list>
</p>
</sec>
<sec id="s5-3-5">
<title>5.3.5 Service robot scenario</title>
<p>
<xref ref-type="bibr" rid="B43">Ji et al. (2012)</xref> provide a flexible framework for service robots using the automatic planner Stanford Research Institute Problem Solver (STRIPS). Specific details about the KB, such as the source files, are not publicly available, so the information provided here is derived from articles about the framework.</p>
<p>The ontology represents two main types of information, environmental description and primitive robot actions, which handle spatial uncertainties of particular objects and the primitive actions that the robot can perform. Actions include four main attributes to comply with STRIPS: precondition, postcondition, input, and result. The planning process is optimized using a recursive back-trace search method and knowledge information to limit the search space. The framework is applied to the Care-O-Bot agent in a scenario in which it shall get a milk box.</p>
<p>The detailed analysis of comparison criteria follows:<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Perception and categorization:</italic> Symbol grounding is crucial for <xref ref-type="bibr" rid="B43">Ji et al. (2012)</xref>, as it bridges the gap between abstract planning and actual robot sensing and actuation. For example, a task of moving a table involves moving the robot near the table. The symbol grounding specifies exactly where <italic>&#x201c;near the table&#x201d;</italic> is.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Decision making and planning:</italic> This framework uses recursive backtracing search for action planning in dynamic environments. The use of semantic maps can improve the search for an object by limiting the search space using semantic inference.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Reasoning:</italic> <xref ref-type="bibr" rid="B43">Ji et al. (2012)</xref> use reasoning to retrieve information about spatial objects, such as the location of the table where milk is stored. Specific actions, such as <italic>workspace of</italic>, are defined to support reasoning and enable the retrieval of spatial information about an object. For example, a milk box could provide a result of <italic>above the table</italic> or <italic>in the refrigerator</italic>, as it is a perishable product. This framework also provides a likelihood estimation of possible locations of objects.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Execution:</italic> Execution uses a central controller to propagate the action to the task planner, the user interface, and the low-level robot modules. Each action is represented as a state machine that is executed in real time. After the action is finished, it updates the models based on the result and the action postcondition.</p>
</list-item>
</list>
</p>
<p>
<xref ref-type="table" rid="T4">Table 4</xref> depicts the main aspects of each capability in the social applications reviewed. All capabilities incorporate reasoning using knowledge from the ontology, with the majority also utilizing it for perception and categorization, decision making and planning, and execution. Communication and coordination are only present in two of the five analyzed works. Prediction and monitoring, interaction and design, and learning are the least addressed capabilities across these applications.</p>
<table-wrap id="T4" position="float">
<label>TABLE 4</label>
<caption>
<p>Use of ontologies in the social domain for perception and categorization (P/C), decision making and planning (DM/P), prediction and monitoring (P/M), reasoning (R), execution (E), communication and coordination (C/C), interaction and design (I/D) and learning (L).</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center"/>
<th align="center">OUR-K (<xref ref-type="bibr" rid="B50">Lim et al., 2011</xref>, <xref ref-type="bibr" rid="B25">Diab et al., 2018</xref>)</th>
<th align="center">ORO (<xref ref-type="bibr" rid="B47">Lemaignan et al., 2010</xref>)</th>
<th align="center">OCRA (<xref ref-type="bibr" rid="B58">Olivares-Alarcos et al., 2022</xref>)</th>
<th align="center">ISRO (<xref ref-type="bibr" rid="B22">Chang et al., 2020</xref>)</th>
<th align="center">Service robot scenario (<xref ref-type="bibr" rid="B43">Ji et al., 2012</xref>)</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="left">P/C</td>
<td align="center">Same approach as OMRKF</td>
<td align="center">Use common ancestors or the best discriminant to categorize</td>
<td align="center">-</td>
<td align="center">Sensor information to recognize the user involved</td>
<td align="center">Abstract planning information</td>
</tr>
<tr>
<td align="left">DM/P</td>
<td align="center">Abductive event calculus planner for hierarchical abstraction</td>
<td align="center">-</td>
<td align="center">Dynamic plan adaptation during runtime</td>
<td align="center">Path planning, semantic maps</td>
<td align="center">Recursive back-trace searching</td>
</tr>
<tr>
<td align="left">P/M</td>
<td align="center">Navigation monitoring and missing object recognition tasks</td>
<td align="center">-</td>
<td align="center">-</td>
<td align="center">-</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">R</td>
<td align="center">Bidirectional links between low and high levels to fill in missing information</td>
<td align="center">Ontological reasoning combined with external modules triggered when an event occurs</td>
<td align="center">Answering competency questions for collaboration, plans, goals, and adaptations</td>
<td align="center">Infer spatial and temporal information and user characterization</td>
<td align="center">Information about spatial objects</td>
</tr>
<tr>
<td align="left">E</td>
<td align="center">Action knowledge is coupled with all other concepts of the knowledge of models and features</td>
<td align="center">Query-based integrated CRAM to automatically update the ontology</td>
<td align="center">-</td>
<td align="center">-</td>
<td align="center">Central controller to propagate the action to planner, user interface, and lower levels</td>
</tr>
<tr>
<td align="left">C/C</td>
<td align="center">-</td>
<td align="center">Intelligent blackboard for knowledge sharing among agents</td>
<td align="center">Collaboration with humans, explainability</td>
<td align="center">-</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">I/D</td>
<td align="center">Dynamic interaction, runtime controller adaptation</td>
<td align="center">-</td>
<td align="center">-</td>
<td align="center">-</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">L</td>
<td align="center">-</td>
<td align="center">-</td>
<td align="center">Envisioned as future work</td>
<td align="center">-</td>
<td align="center">-</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
</sec>
<sec id="s5-4">
<title>5.4 Industrial domain</title>
<p>Robots in industrial domains aim to increase efficiency and precision in a variety of tasks. These are often related to manufacturing, production, and other industrial processes. Ontologies in this domain aim to increase flexibility, reduce maintenance, or enhance control and inspection processes.</p>
<sec id="s5-4-1">
<title>5.4.1 Robot control for Skilled Execution of Tasks</title>
<p>Robot control for Skilled Execution of Tasks (ROSETTA) constitutes an ontology for robots performing manufacturing tasks<xref ref-type="fn" rid="fn22">
<sup>22</sup>
</xref>. Its origins can be traced to the European projects SIARAS, RoSta, and ROSETTA (<xref ref-type="bibr" rid="B71">Stenmark and Malec, 2015</xref>). The core of the ontology is mostly focused on robot devices and their skills. It relies on a component called the knowledge integration framework (KIF) to provide services for robotic ontologies and data repositories (<xref ref-type="bibr" rid="B71">Stenmark and Malec, 2015</xref>). Note that this should not be confused with the knowledge interchange format, which is a syntax for FOL. KIF acts as an interface to users. They can specify the task by partially ordering the subgoals in an assembly tree; the framework then establishes the action planning and its schedule with limited resources. KIF also provides an execution structure that generates state machines from skill descriptions and their constraints.</p>
<p>
<xref ref-type="bibr" rid="B37">Hoebert et al. (2021)</xref> use ROSETTA ontology to control the assembly process of a variety of electronic devices. This work focuses on a world model that represents robotic devices and the skills of ROSETTA. It also relies on the boundary representation (BREP) ontology (<xref ref-type="bibr" rid="B61">Perzylo et al., 2015</xref>) to semantically encode geometric entities. This work uses the ontology to conceptualize objects and their properties in the environment. It defines a product as a hierarchy of sub-assemblies and parts. Requirements are also included to determine the correct automated manufacturing.</p>
<p>
<xref ref-type="bibr" rid="B54">Merdan et al. (2019)</xref> also employ the ROSETTA ontology to control an industrial assembly process, in particular, a pallet transport system and the control of an industrial robot. In this case, it uses the ROSETTA and BREP ontologies to conceptualize the robotic system (e.g., skills, properties, constraints, etc.), the product model (e.g., parts, geometries, assembly orientation, etc.), and the manufacturing infrastructure (e.g., product, storage, sensors, etc.). Rosetta has been defined in OWL.</p>
<p>The detailed analysis of comparison criteria follows:</p>
<p>
<italic>Perception and categorization:</italic> The ROSETTA application by <xref ref-type="bibr" rid="B37">Hoebert et al. (2021)</xref> provides an object recognition module that links perception data with geometric features represented in the KB.</p>
<p>
<italic>Decision making and planning:</italic> The KIF executor of the ROSETTA ontology serves as the planning mechanism. It transforms an assembly graph into a sequence of operations with preconditions and postconditions, subsequently translated into a task state machine. Both <xref ref-type="bibr" rid="B54">Merdan et al. (2019)</xref> and <xref ref-type="bibr" rid="B37">Hoebert et al. (2021)</xref> approach decision making as a plan generator, utilizing PDDL. <xref ref-type="bibr" rid="B37">Hoebert et al. (2021)</xref> provide a generator that extracts information from the ontology to produce the required PDDL files for planning. <xref ref-type="bibr" rid="B54">Merdan et al. (2019)</xref> also translate the semantic model, that is, states and actions, into domain and problem files through templates.</p>
<p>
<italic>Reasoning:</italic> ROSETTA reasoning is enabled by the KIF server (<xref ref-type="bibr" rid="B71">Stenmark and Malec, 2015</xref>). It allows the user to download and upload libraries with object descriptions, task specifications, and skills. The KIF reasoner assists robot programming by retrieving information about tools, sensors, objects, object properties, etc. <xref ref-type="bibr" rid="B37">Hoebert et al. (2021)</xref> take advantage of the ROSETTA ontology to select the individual actions and the equipment required to manufacture a product part.</p>
<p>
<italic>Execution:</italic> KIF uses state machines to execute the skills defined in the ROSETTA ontology (<xref ref-type="bibr" rid="B71">Stenmark and Malec, 2015</xref>). However, <xref ref-type="bibr" rid="B37">Hoebert et al. (2021)</xref> and <xref ref-type="bibr" rid="B54">Merdan et al. (2019)</xref> use the execution of atomic actions through PDDL commands. With this approach, as discussed by <xref ref-type="bibr" rid="B37">Hoebert et al. (2021),</xref> the missing standardization of the meta-level concepts can cause difficulties when integrating existing ontologies and reduce the scalability of the approach. A comparison of the performance using several PDDL planners is discussed in this article. In terms of scalability, <xref ref-type="bibr" rid="B54">Merdan et al. (2019)</xref> use a central database server to support a high-performance integration of multiple homogeneous data sources to integrate the ontology with other knowledge sources.</p>
<p>
<italic>Communication and coordination:</italic> The ROSETTA-based framework by <xref ref-type="bibr" rid="B54">Merdan et al. (2019)</xref> aims to communicate between robots and entities in the external production environment. Additionally, being a component-based approach, it provides infrastructure for intercomponent communication.</p>
<p>
<italic>Interaction and design:</italic> ROSETTA provides an engineering specification of workspace objects, skills, and tasks from libraries (<xref ref-type="bibr" rid="B71">Stenmark and Malec, 2015</xref>). It acts as a database for all the information present in the object and in the environment. <xref ref-type="bibr" rid="B37">Hoebert et al. (2021)</xref> use these design models to establish and verify the manufacturing process, tailoring the requirements to parameters such as assembly operation type, manufacturing constraints, material used, and piece dimensions.</p>
</sec>
<sec id="s5-4-2">
<title>5.4.2 Industrial robotic scenario</title>
<p>
<xref ref-type="bibr" rid="B13">Bernardo et al. (2018)</xref> define an ontology-based approach for an industrial robotic application focused on inserting up to 56 small pins (sealants) into a harness box terminal specifically tailored for the automotive industry. Specific details about the KB, such as the source files, are not publicly available, so the information provided here is derived from articles about the approach.</p>
<p>The KB is built upon CORA (<xref ref-type="bibr" rid="B62">Prestes et al., 2013</xref>) and provides specifications for the robot, the machine vision system, and the tasks required for seamless operation. Task sequences are used to execute the plan, but the machine vision system also uses them to inspect whether the sealants were correctly inserted into the connecting boxes. If not, the system prioritizes applying the sealant in the faulty position(s) in the connecting box.</p>
<p>The detailed analysis of comparison criteria follows:<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Perception and categorization:</italic> This approach uses vision to inspect robot operations, specifically to verify the correct insertion of sealants in connecting boxes. Image processing is applied for this inspection, although the information is not categorized in the ontology. The framework also utilizes proximity, position, and fiber optic sensors to facilitate robot operation.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Decision making and planning:</italic> The framework incorporates visual inspection to validate the precision of the insertion of sealants into the connecting boxes. Additionally, it features a re-planning process that modifies production orders when an error calculus task detects errors. Ontological knowledge is used to establish a sequence of tasks, and in the event of an error, a priority task is immediately added to determine the position of the sealant that requires attention. Once this high-priority task is completed successfully, the robotic system resumes the original production order. The authors define adding this priority task as a re-plan, but we think it corresponds to a planned repair as it returns to the original plan afterward.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Reasoning:</italic> This framework uses DL reasoning to acquire valuable data for production and maintenance at the factory level. This reasoning includes information about sensors and actuators and their purposes in various tasks. The knowledge obtained is then utilized to plan and respond to queries, improving the overall decision-making process.</p>
</list-item>
</list>
</p>
</sec>
<sec id="s5-4-3">
<title>5.4.3 Adaptive agents for manufacturing domains</title>
<p>
<xref ref-type="bibr" rid="B15">Borgo et al. (2019)</xref> extend the DOLCE ontology from a broad perspective. They validated their approach using a real pilot plant, a reconfigurable manufacturing system designed for recycling printed circuit boards (PCBs). Specific details about the KB, such as the source files, are not publicly available, so the information provided here is derived from articles about the ontology. The ontological framework aims to store knowledge about fundamental assumptions and identify the current scenario, including the presence and location of objects, executed actions, responsible agents, changes occurring, etc.</p>
<p>The KB created by this approach seeks to integrate various perspectives within the enterprise, covering intelligent agents, engineering activities, and management activities. The framework is structured in a deliberative layer to synthesize the actions needed to achieve a goal, an executive and monitoring layer to verify the actions, and a mechatronic system that determines the capabilities of the agent.<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Decision making and planning:</italic> The updated KB uses an abstraction of the device to be controlled, the environment parameters, and the execution constraints to generate a timeline-based planning model. This model provides the atomic operations that a transportation module can perform, depending on its components and the available collaborators. The timeline incorporates temporal flexibility, allowing for relaxed start and end times. The resulting plan represents the potential evolution of the relevant feature. The framework also supports replanning in case of plan execution failure, generating a new plan based on the current state of the mechatronic system.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Prediction and monitoring:</italic> Execution is monitored by comparing action outcomes with respect to the expected state of the system and the environment. The monitor process receives signals about the (either positive or negative) outcome of the execution, for example, from the transportation module, and checks whether the actual status of the mechatronic system complies with the plan.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Reasoning:</italic> Two types of reasoning are used in this approach. Low-level reasoning infers information about the internal and local contexts of transport modules, identifying system components and available collaborating agents. High-level reasoning utilizes low-level inferences to extract knowledge about the transportation machine&#x2019;s functional capabilities, deducing specific internal and local contexts. This knowledge is then used to generate the plan and its control model.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Execution:</italic> The execution is based on a knowledge-based control loop (KBCL) presented in <xref ref-type="bibr" rid="B15">Borgo et al. (2019</xref>). This loop facilitates monitoring by dynamically representing the robot&#x2019;s capabilities, internal status, and environmental situation to infer the available functionalities. A reconfiguration phase is activated in case of failure or when new capabilities are added, updating the KB and initiating a new iteration of the overall loop. The executor receives sensor signals and feedback from the transportation module, issuing action commands based on the plan.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Communication and coordination:</italic> The framework includes the exchange of information through ontologies, employing commands for sending and receiving interactions with other entities. The concept of <italic>collaborators</italic> represents relationships between the agent (transport module) and any connected entities, such as other transport modules or machines.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Interaction and design:</italic> The ontology also models engineering and management activities. The authors use engineering approaches to identify high-level functions to be executed to reach a given goal, explore the difference between the actual state and the desired state, and isolate the changes to be made. They include information on operand integrity, operand qualities, quality relationships, etc. These concepts make explicit engineering facts that are usually not included in robotic approaches that complement knowledge about robot capacities and contexts.</p>
</list-item>
</list>
</p>
<p>
<xref ref-type="table" rid="T5">Table 5</xref> provides a summary of three frameworks applied to industrial scenarios. ROSETTA encompasses all capabilities except prediction, monitoring, and learning. Similarly, the adaptive agent for manufacturing domains includes all capabilities except perception, categorization, and learning. Lastly, the remaining industrial scenario only covers decision making, planning, and reasoning, which were required to be included in the review, and perception and categorization.</p>
<table-wrap id="T5" position="float">
<label>TABLE 5</label>
<caption>
<p>Use of ontologies in the industrial domain for perception and categorization (P/C), decision making and planning (DM/P), prediction and monitoring (P/M), reasoning (R), execution (E), communication and coordination (C/C), interaction and design (I/D) and learning (L).</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center"/>
<th align="center">ROSETTA (<xref ref-type="bibr" rid="B71">Stenmark and Malec, 2015;</xref> <xref ref-type="bibr" rid="B37">Hoebert et al., 2021;</xref> <xref ref-type="bibr" rid="B54">Merdan et al., 2019</xref>)</th>
<th align="center">Industrial robotic scenario (<xref ref-type="bibr" rid="B13">Bernardo et al., 2018</xref>)</th>
<th align="center">Adaptive agent for manufacturing domains (<xref ref-type="bibr" rid="B15">Borgo et al., 2019</xref>)</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="left">P/C</td>
<td align="center">Object recognition linking perception data with geometric features</td>
<td align="center">Vision to inspect robot operations and proximity, position, and fiber optic sensors</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">DM/P</td>
<td align="center">Transform an assembly graph into a sequence of operations with preconditions and postconditions to create a task-state machine</td>
<td align="center">Replanning process that modifies production orders when an error calculus task detects them</td>
<td align="center">Generate a timeline-based planning model with atomic operations</td>
</tr>
<tr>
<td align="left">P/M</td>
<td align="center">-</td>
<td align="center">-</td>
<td align="center">Compare action outcomes with respect to the expected status of the system and the environment</td>
</tr>
<tr>
<td align="left">R</td>
<td align="center">Retrieve information about tools, sensors, objects, object properties, etc.</td>
<td align="center">Reasoning to acquire valuable data for production and maintenance at the factory level</td>
<td align="center">Low-level reasoning for local context and high-level reasoning for the transportation machine&#x2019;s functional capabilities</td>
</tr>
<tr>
<td align="left">E</td>
<td align="center">State machines to execute skills</td>
<td align="center">-</td>
<td align="center">Reconfiguration phase is activated in case of failure or when new capabilities are added</td>
</tr>
<tr>
<td align="left">C/C</td>
<td align="center">Communication between robot and external production environment entities and infrastructure for intercomponent communication</td>
<td align="center">-</td>
<td align="center">Commands for sending and receiving interactions with other entities</td>
</tr>
<tr>
<td align="left">I/D</td>
<td align="center">Design models to establish and verify the manufacturing process, tailoring requirements to parameters</td>
<td align="center">-</td>
<td align="center">Model engineering and management activities</td>
</tr>
<tr>
<td align="left">L</td>
<td align="center">-</td>
<td align="center">-</td>
<td align="center">-</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
</sec>
<sec id="s5-5">
<title>5.5 Discussion</title>
<p>In this section, we summarize the most relevant results on the reviewed projects as a whole, independent of the discipline in which they were evaluated, as most aim to be generally applicable to any domain. We also discuss other relevant information on the work reviewed, such as the use of temporal information, the encoding language, or the main application and domain.</p>
<p>As far as <italic>perception and categorization</italic> are concerned, most of the projects focus on situation assessment, providing information about the environment to handle the situation and make decisions accordingly. This part is directly related to reasoning because frameworks such as KnowRob (<xref ref-type="bibr" rid="B75">Tenorth and Beetz, 2009</xref>; <xref ref-type="bibr" rid="B9">Beetz et al., 2018</xref>), SWARMs (<xref ref-type="bibr" rid="B49">Li et al., 2017</xref>), or PLM (<xref ref-type="bibr" rid="B4">Antanas et al., 2019</xref>) use probability reasoning to generate knowledge about the environment and its affordances.</p>
<p>All works except ORO (<xref ref-type="bibr" rid="B47">Lemaignan et al., 2010</xref>) and OCRA (<xref ref-type="bibr" rid="B58">Olivares-Alarcos et al., 2022</xref>) use explicit knowledge for <italic>decision making and planning</italic>. These two focus on answering competency questions related to actions or planning for actions in future developments. Geometric and grasp planning are widely used along with task planners to establish a sequence of atomic actions. PDDL is the most widely used task planner. Replanning is also important for some of these articles: TOMASys (<xref ref-type="bibr" rid="B36">Hern&#xe1;ndez et al., 2018</xref>), RTPO (<xref ref-type="bibr" rid="B74">Sun et al., 2019b</xref>), FailRecOnt (<xref ref-type="bibr" rid="B28">Diab et al., 2021</xref>), industrial application (<xref ref-type="bibr" rid="B13">Bernardo et al., 2018</xref>), adaptive manufacturing application (<xref ref-type="bibr" rid="B15">Borgo et al., 2019</xref>), and the planetary rover case (<xref ref-type="bibr" rid="B20">Burroughes and Gao, 2016</xref>). In these projects, the objective is to maintain the operation in the presence of faults. Lastly, some works also use ontologies to plan in combination with reactive behaviors, such as OUR-K (<xref ref-type="bibr" rid="B50">Lim et al., 2011</xref>), ORO (<xref ref-type="bibr" rid="B47">Lemaignan et al., 2010</xref>), and the planetary rover application (<xref ref-type="bibr" rid="B20">Burroughes and Gao, 2016</xref>).</p>
<p>
<italic>Prediction and monitoring</italic> are less present in the reviewed articles. This activity requires a fully operational KB used during runtime and a deeper understanding of the situation and the autonomous robot. Most of the works monitor only the environment, such as KnowRob (<xref ref-type="bibr" rid="B75">Tenorth and Beetz, 2009</xref>; <xref ref-type="bibr" rid="B9">Beetz et al., 2018</xref>) and OUR-K (<xref ref-type="bibr" rid="B50">Lim et al., 2011</xref>). Others only assess the robot state, such as FailRecOnt (<xref ref-type="bibr" rid="B28">Diab et al., 2021</xref>), the manipulation application (<xref ref-type="bibr" rid="B15">Borgo et al., 2019</xref>), and the planetary rover application (<xref ref-type="bibr" rid="B20">Burroughes and Gao, 2016</xref>). Lastly, TOMASys (<xref ref-type="bibr" rid="B36">Hern&#xe1;ndez et al., 2018</xref>) assesses the robot&#x27;s state and mission status.</p>
<p>
<italic>Reasoning</italic> is addressed in all the works. All use ontologies to at least answer queries and verify ontological consistency, as this was an inclusion requirement for the review. Ontological information is used at runtime to recover from failure in some frameworks such as FailRecOnt (<xref ref-type="bibr" rid="B28">Diab et al., 2021</xref>), TOMASys (<xref ref-type="bibr" rid="B36">Hern&#xe1;ndez et al., 2018</xref>), and the planetary rover application (<xref ref-type="bibr" rid="B20">Burroughes and Gao, 2016</xref>). Reasoners can download additional required information, such as RoboEarth (<xref ref-type="bibr" rid="B77">Tenorth et al., 2012</xref>), which uses web and cloud services, or ROSETTA (<xref ref-type="bibr" rid="B71">Stenmark and Malec, 2015</xref>), which uses the KIF server to download and upload libraries.</p>
<p>SWARMs (<xref ref-type="bibr" rid="B49">Li et al., 2017</xref>) uses a hybrid context reasoner, combining ontological rule-based reasoning with MEBN theory (<xref ref-type="bibr" rid="B46">Laskey, 2008</xref>) for probabilistic annotations. PLM (<xref ref-type="bibr" rid="B4">Antanas et al., 2019</xref>) uses a probabilistic logic module for grasping, which combines semantic reasoning with object affordances. KnowRob2 (<xref ref-type="bibr" rid="B9">Beetz et al., 2018</xref>) takes a further step and provides a hybrid reasoning kernel that enables physics-based reasoning, flexible data structure reasoning, and a detailed robotic agent experience. However, this use comes at a higher cost, as its computation may yield inconsistencies or inefficient reasoning. For this reason, RTPO (<xref ref-type="bibr" rid="B74">Sun et al., 2019b</xref>) targets knowledge scalability and efficient reasoning by conducting a study on the performance of real-time reasoning with 52,000 individuals. However, the authors do not describe how this approach affects the planning process.</p>
<p>Not all frameworks use explicit knowledge during <italic>execution;</italic> some of them only perform the action sequence defined in the plan. Others drive its execution to answer competency questions, such as OCRA (<xref ref-type="bibr" rid="B58">Olivares-Alarcos et al., 2022</xref>) and KnowRob (<xref ref-type="bibr" rid="B75">Tenorth and Beetz, 2009</xref>; <xref ref-type="bibr" rid="B9">Beetz et al., 2018</xref>). KnowRob also uses the CRAM (<xref ref-type="bibr" rid="B10">Beetz et al., 2010</xref>) executor to update the KB with information about perception and action results, inferring new data to make control decisions at runtime. ORO (<xref ref-type="bibr" rid="B47">Lemaignan et al., 2010</xref>) also uses CRAM to update the server when new objects are detected.</p>
<p>Other approaches use state machines, such as ROSETTA (<xref ref-type="bibr" rid="B71">Stenmark and Malec, 2015</xref>), or the MAPE-K loop (<xref ref-type="bibr" rid="B40">IBM Corporation, 2005</xref>), such as TOMASys (<xref ref-type="bibr" rid="B36">Hern&#xe1;ndez et al., 2018</xref>) and the planetary rover application (<xref ref-type="bibr" rid="B20">Burroughes and Gao, 2016</xref>). Similarly, the manufacturing application of <xref ref-type="bibr" rid="B15">Borgo et al. (2019)</xref> presents a knowledge-based control loop to combine execution with monitoring.</p>
<p>Other important processes for autonomous systems are <italic>communication and coordination</italic>. All ontological systems can be used easily to answer queries from a human operator. However, this is not sufficient for reliable autonomy; the ontology can provide transparent information to complete the knowledge. SWARMs (<xref ref-type="bibr" rid="B49">Li et al., 2017</xref>) enables an abstraction for communication, networking, and information sharing of heterogeneous data. For this, ORO (<xref ref-type="bibr" rid="B47">Lemaignan et al., 2010</xref>) uses an intelligent blackboard that allows other modules to push or pull knowledge to a central repository. RoboEarth (<xref ref-type="bibr" rid="B63">Riazuelo et al., 2015</xref>) and ROSETTA (<xref ref-type="bibr" rid="B71">Stenmark and Malec, 2015</xref>) obtain knowledge from other sources. RoboEarth defines a communication module for uploading and downloading information from the web, and ROSETTA uses the KIF server to download and upload libraries.</p>
<p>Coordination between agents and components of the agent is critical for autonomous operation. ROSETTA provides an infrastructure for intercomponent communication. Component coordination is explicitly addressed in TOMASys (<xref ref-type="bibr" rid="B36">Hern&#xe1;ndez et al., 2018</xref>), the planetary rover from <xref ref-type="bibr" rid="B20">Burroughes and Gao (2016),</xref> and the adaptive manufacturing from <xref ref-type="bibr" rid="B15">Borgo et al. (2019)</xref>. The USAR application from <xref ref-type="bibr" rid="B21">Chandra and Rocha (2016)</xref> targets multirobot cooperation for both information sharing and task coordination with other agents. OCRA (<xref ref-type="bibr" rid="B58">Olivares-Alarcos et al., 2022</xref>) also handles task coordination and plan adaptation but only concerns human&#x2013;robot collaboration.</p>
<p>
<italic>Interaction and design</italic> are often not explicitly handled during robot operation. However, awareness of interaction allows the robot to step back from action execution and understand the sources of failure. TOMASys (<xref ref-type="bibr" rid="B36">Hern&#xe1;ndez et al., 2018</xref>) provides a metamodel that benefits from the engineering models used during design time. ROSETTA also uses the engineering specification of workspace objects, skills, and tasks as part of the KB. The planetary rover (<xref ref-type="bibr" rid="B20">Burroughes and Gao, 2016</xref>) does not explicitly include any information on design or requirements; however, it reasons in terms of the capacity of the services onboard, using some sort of operational requirement to select among alternatives. Similarly, the autonomous vehicle framework (<xref ref-type="bibr" rid="B38">Huang et al., 2019</xref>) handles requirements such as legality using traffic rules or reasonableness to support decision making. The adaptive manufacturing application from <xref ref-type="bibr" rid="B15">Borgo et al. (2019)</xref> takes a further step in modeling engineering and management activities. Lastly, with regard to dynamical interactions, the OUR-K extension from <xref ref-type="bibr" rid="B25">Diab et al. (2018)</xref> includes this knowledge to support the adaptation of robotic controllers. PMK (<xref ref-type="bibr" rid="B26">Diab et al., 2019</xref>) represents the interaction as manipulation constraints.</p>
<p>Given the availability of general learning methods, all the processes described above can improve their effectiveness through <italic>learning</italic>. However, this process is less present in the review. Most articles use a form of case-based learning when storing previous successful plans or using episodic memories to recall past situations, such as CORA (<xref ref-type="bibr" rid="B58">Olivares-Alarcos et al., 2022</xref>). Other frameworks, such as PMK (<xref ref-type="bibr" rid="B26">Diab et al., 2019</xref>) and PLM (<xref ref-type="bibr" rid="B4">Antanas et al., 2019</xref>), use learning as part of a situational assessment to categorize perceptual information.</p>
<p>KnowRob provides the most complete learning mechanics. It learns class structures of entities and identifies manipulation places; in addition, it generates generalized models of the physical effects of actions. KnowRob2 (<xref ref-type="bibr" rid="B9">Beetz et al., 2018</xref>) makes the learned information available through the Open-EASE knowledge service (<xref ref-type="bibr" rid="B11">Beetz et al., 2015</xref>). This service enables any user to upload, access, and analyze episodic memories of robots performing manipulation tasks.</p>
<sec id="s5-5-1">
<title>5.5.1 Other aspects</title>
<p>
<xref ref-type="table" rid="T6">Table 6</xref> depicts other aspects of the frameworks studied, such as the languages used, the use of temporal conceptualizations, and the foundational ontologies.</p>
<table-wrap id="T6" position="float">
<label>TABLE 6</label>
<caption>
<p>Summary of other aspects of the framework: concrete encoding languages used, incorporation of temporal conceptualizations, and whether the framework is built upon other works or utilizes an upper-level ontology.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="left">Framework</th>
<th align="center">Encoding Lang</th>
<th align="center">Temporal</th>
<th align="center">Upper-level Ont</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="left">KnowRob (<xref ref-type="bibr" rid="B75">Tenorth and Beetz, 2009</xref>; <xref ref-type="bibr" rid="B9">Beetz et al., 2018</xref>; <xref ref-type="bibr" rid="B76">Tenorth and Beetz, 2013</xref>; <xref ref-type="bibr" rid="B80">Waibel et al., 2011</xref>; <xref ref-type="bibr" rid="B77">Tenorth et al., 2012</xref>; <xref ref-type="bibr" rid="B24">Crespo et al., 2018</xref>; <xref ref-type="bibr" rid="B63">Riazuelo et al., 2015</xref>)</td>
<td align="center">OWL, Prolog</td>
<td align="center">Intervals</td>
<td align="center">DUL</td>
</tr>
<tr>
<td align="left">PMK (<xref ref-type="bibr" rid="B26">Diab et al., 2019</xref>)</td>
<td align="center">OWL, Prolog</td>
<td align="center">-</td>
<td align="center">IEEE-1872.2 Std</td>
</tr>
<tr>
<td align="left">FailRecOnt (<xref ref-type="bibr" rid="B28">Diab et al., 2021;</xref> <xref ref-type="bibr" rid="B27">Diab et al., 2020</xref>)</td>
<td align="center">OWL</td>
<td align="center">-</td>
<td align="center">DUL</td>
</tr>
<tr>
<td align="left">PLM (<xref ref-type="bibr" rid="B4">Antanas et al., 2019</xref>)</td>
<td align="center">OWL</td>
<td align="center">-</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">TOMASys (<xref ref-type="bibr" rid="B36">Hern&#xe1;ndez et al., 2018;</xref> <xref ref-type="bibr" rid="B16">Bozhinoski et al., 2022</xref>; <xref ref-type="bibr" rid="B3">Aguado et al., 2021</xref>)</td>
<td align="center">OWL</td>
<td align="center">-</td>
<td align="center">OASys</td>
</tr>
<tr>
<td align="left">OMRKF (<xref ref-type="bibr" rid="B72">Suh et al., 2007</xref>)</td>
<td align="center">Prolog</td>
<td align="center">Context</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">SWARMs (<xref ref-type="bibr" rid="B49">Li et al., 2017</xref>)</td>
<td align="center">OWL</td>
<td align="center">-</td>
<td align="center">PR-OWL</td>
</tr>
<tr>
<td align="left">RTPO (<xref ref-type="bibr" rid="B74">Sun et al., 2019b</xref>)</td>
<td align="center">OWL, Prolog</td>
<td align="center">-</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">Planetary Rovers Scenario (<xref ref-type="bibr" rid="B20">Burroughes and Gao, 2016</xref>)</td>
<td align="center">PDDL, OWL</td>
<td align="center">Time Concept</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">USAR Scenario (<xref ref-type="bibr" rid="B21">Chandra and Rocha, 2016</xref>)</td>
<td align="center">OWL</td>
<td align="center">-</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">Autonomous Vehicles Scenario (<xref ref-type="bibr" rid="B38">Huang et al., 2019</xref>)</td>
<td align="center">Prolog</td>
<td align="center">-</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">SAR Scenario (<xref ref-type="bibr" rid="B73">Sun et al., 2019a</xref>)</td>
<td align="center">OWL</td>
<td align="center">-</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">OUR-K (<xref ref-type="bibr" rid="B50">Lim et al., 2011</xref>; <xref ref-type="bibr" rid="B25">Diab et al., 2018</xref>)</td>
<td align="center">OWL</td>
<td align="center">Context</td>
<td align="center">OMRKF</td>
</tr>
<tr>
<td align="left">ORO (<xref ref-type="bibr" rid="B47">Lemaignan et al., 2010</xref>)</td>
<td align="center">OWL</td>
<td align="center">-</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">OCRA (<xref ref-type="bibr" rid="B58">Olivares-Alarcos et al., 2022</xref>)</td>
<td align="center">OWL</td>
<td align="center">Intervals</td>
<td align="center">DUL, KnowRob</td>
</tr>
<tr>
<td align="left">ISRO (<xref ref-type="bibr" rid="B22">Chang et al., 2020</xref>)</td>
<td align="center">OWL, Prolog</td>
<td align="center">Time Concept</td>
<td align="center">OpenCyc</td>
</tr>
<tr>
<td align="left">Service Robot Scenario (<xref ref-type="bibr" rid="B43">Ji et al., 2012</xref>)</td>
<td align="center">OWL, STRIPS</td>
<td align="center">-</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">ROSETTA (<xref ref-type="bibr" rid="B71">Stenmark and Malec, 2015;</xref> <xref ref-type="bibr" rid="B37">Hoebert et al., 2021;</xref> <xref ref-type="bibr" rid="B54">Merdan et al., 2019</xref>)</td>
<td align="center">PDDL, OWL</td>
<td align="center">-</td>
<td align="center">-</td>
</tr>
<tr>
<td align="left">Industrial Robotic Scenario (<xref ref-type="bibr" rid="B13">Bernardo et al., 2018</xref>)</td>
<td align="center">OWL</td>
<td align="center">-</td>
<td align="center">CORA</td>
</tr>
<tr>
<td align="left">Adaptive Agents (<xref ref-type="bibr" rid="B15">Borgo et al., 2019</xref>)</td>
<td align="center">OWL</td>
<td align="center">Intervals</td>
<td align="center">DOLCE</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>Almost all works use OWL or a combination of OWL and Prolog as the KB language. For planning, most of them use geometric planners, such as PLM (<xref ref-type="bibr" rid="B4">Antanas et al., 2019</xref>), along with task planners. In some works, task planners are custom made, such as the service robot from <xref ref-type="bibr" rid="B43">Ji et al. (2012)</xref>. However, in general, task planners are based on ontological queries, such as the SAR scenario (<xref ref-type="bibr" rid="B73">Sun et al., 2019a</xref>), the industrial application (<xref ref-type="bibr" rid="B13">Bernardo et al., 2018</xref>), and the adaptive manufacturing of <xref ref-type="bibr" rid="B15">Borgo et al. (2019</xref>). The planetary rover (<xref ref-type="bibr" rid="B20">Burroughes and Gao, 2016</xref>) and ROSETTA (<xref ref-type="bibr" rid="B71">Stenmark and Malec, 2015</xref>) use PDDL directly, while RTPO (<xref ref-type="bibr" rid="B74">Sun et al., 2019b</xref>) and SWARMs (<xref ref-type="bibr" rid="B49">Li et al., 2017</xref>) use a custom approach similar to PDDL.</p>
<p>Some studies use temporal conceptualizations to address planning dynamics. Most of them rely on an ordered sequence of actions. However, KnowRob (<xref ref-type="bibr" rid="B75">Tenorth and Beetz, 2009</xref>; <xref ref-type="bibr" rid="B9">Beetz et al., 2018</xref>), OCRA (<xref ref-type="bibr" rid="B58">Olivares-Alarcos et al., 2022</xref>), and the adaptive manufacturing approach use time intervals to recall a time frame in which the action is executed. OMRKF (<xref ref-type="bibr" rid="B72">Suh et al., 2007</xref>) and OUR-K (<xref ref-type="bibr" rid="B50">Lim et al., 2011</xref>) include time as part of the context ontology, and the planetary rover (<xref ref-type="bibr" rid="B20">Burroughes and Gao, 2016</xref>) and ISRO (<xref ref-type="bibr" rid="B22">Chang et al., 2020</xref>) conceptualize time in their KBs.</p>
</sec>
</sec>
</sec>
<sec id="s6">
<title>6 Research directions and conclusion</title>
<p>Considering the projects surveyed, we believe that ontologies are a valuable asset that supports robot autonomy. The frameworks discussed provide an advance towards mission-level dependability, increasing robot reliability and availability. However, there are both unsolved issues and valuable possibilities for further research in this domain.</p>
<p>An unsolved issue is the limited dissemination and convergence of the different ontological approaches. There is still insufficient reuse of existing ontologies and interchangeability or interoperability of the different realization frameworks. In this direction, KnowRob (<xref ref-type="bibr" rid="B75">Tenorth and Beetz, 2009</xref>; <xref ref-type="bibr" rid="B9">Beetz et al., 2018</xref>) is the most documented and impactful project, as it proves its influence on other projects such as ORO (<xref ref-type="bibr" rid="B47">Lemaignan et al., 2010</xref>), FailRecOnt (<xref ref-type="bibr" rid="B28">Diab et al., 2021</xref>), and OCRA (<xref ref-type="bibr" rid="B58">Olivares-Alarcos et al., 2022</xref>). Ontology convergence is always a challenge that is exacerbated by the variety of ontologies, both vertical&#x2014;the levels of abstraction&#x2014;and horizontal&#x2014;the domains of application. However, efforts must be made to ensure this harmonization, given the fact that robots are not isolated entities but are always part of systems-of-systems that share specific forms of knowledge (<xref ref-type="bibr" rid="B66">Sanz et al., 2021</xref>).</p>
<p>We believe that future engineering-grade, knowledge-driven autonomous robot software platforms should also be capable of providing three characteristics: explainability, reusability, and scalability. In the articles under review:<list list-type="simple">
<list-item>
<p>&#x2022; <italic>Explainability</italic> is enabled in most cases&#x2014;at least in a shallow form&#x2014;as most frameworks include query/answer interfaces to provide information on robot operation. However, this explainability is tightly bound to the capability of the human user, who is often a robot operator, to fully grasp the explanation. More broad-spectrum, human-aligned ontologies are needed to support a wider spectrum of users.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Reusability</italic> is intrinsically present, given the explicitness of declarative knowledge and the sharing of common backgrounds, some of which are built on previous works or upper-layer ontologies. Efforts should made to harmonize and integrate conceptualizations to effectively reuse ontologies&#x2014;especially in heterogeneous systems.</p>
</list-item>
<list-item>
<p>&#x2022; <italic>Scalability</italic> and information handling are also partially addressed in some of the realizations, such as reasoning in RTPO (<xref ref-type="bibr" rid="B74">Sun et al., 2019b</xref>) and KnowRob (<xref ref-type="bibr" rid="B75">Tenorth and Beetz, 2009</xref>; <xref ref-type="bibr" rid="B9">Beetz et al., 2018</xref>). However, the problems of scalability remain, such as when dealing with complex systems-of-systems, when addressing geographical or temporal extensive missions, or when knowledge-based collaboration is required, as is the case of cognitive multirobot systems or human&#x2013;robot teams.</p>
</list-item>
</list>
</p>
<p>Therefore, we propose a shared concern in future works in this field to improve the capabilities of robots and contribute to the community in these three aspects. There are already some initiatives, such as CRAM from KnowRob authors, a software toolbox for the design, implementation, and deployment of manipulation activities (<xref ref-type="bibr" rid="B10">Beetz et al., 2010</xref>). This toolbox supports planning, beliefs, and KnowRob reasoners and has been used in other frameworks such as ORO (<xref ref-type="bibr" rid="B47">Lemaignan et al., 2010</xref>). The same authors provide the package <italic>rosprolog</italic>, a bidirectional interface between SWI-Prolog and ROS, to make this logic language accessible to the main robotics middleware. However, these tools are tailored for KnowRob-based environments and are sometimes not well documented or maintained.</p>
<p>The conclusions we extract from this survey are that most of the work is focused on categorization, decision making, and planning. However, <italic>monitoring and coordination</italic> are critical processes with respect to robot control, especially for robust and reliable operation. These kinds of processes are difficult to assess using reusable implementations because of the enormous variability between applications, context, and intervening agents. We propose the use of <italic>explicit engineering models</italic> to facilitate these processes. They are already partially included in TOMASys (<xref ref-type="bibr" rid="B36">Hern&#xe1;ndez et al., 2018</xref>), ROSETTA (<xref ref-type="bibr" rid="B71">Stenmark and Malec, 2015</xref>), the planetary rover scenario (<xref ref-type="bibr" rid="B20">Burroughes and Gao, 2016</xref>), and the adaptive manufacturing application from <xref ref-type="bibr" rid="B15">Borgo et al. (2019)</xref>. We believe that the combination of runtime information with design knowledge can be used during decision making and to drive adaptation to bridge the differences between the expected results of robotic users and the actual robot performance.</p>
</sec>
<sec sec-type="conclusion" id="s7">
<title>7 Conclusion</title>
<p>In this article, we have presented an overview of projects that use ontologies to enable robot autonomy. We have systematically searched for works that propose or extend an ontology and use that knowledge to select, adapt, or plan robot actions. We have compared approaches in terms of how the processes that support autonomous operation use and update the supporting ontology. We also briefly discussed applications, languages, and time representation in those works.</p>
<p>Conceptualization provides robots with a path to understanding, which is a powerful tool for achieving robustness and resiliency. We have found that most frameworks do not include explicit engineering knowledge about the robot system itself. Information about robot components and their interaction, design requirements, and alternatives enables both explainability and self-adaptation. Robots are far from meeting user and owner expectations, especially in terms of dependability, efficiency, and efficacy. We have found that task and goal specifications usually lack explicit knowledge of the user-expected performance. This is necessary information to create robots that a user can trust because trust depends on the reliable provision of some user-expected result. For example, this information could include user phenomenological aspects, required safety levels, or energy thresholds that make a task unprofitable.</p>
<p>In conclusion, we believe that explicit knowledge can support autonomous robot operations in unstructured environments. There are still open issues with respect to reliability, safety, and explainability to meet the expectations of researchers and the industry. However, the steps taken by these projects in a variety of domains to enhance autonomy using ontologies have proven how promising this approach is. A strong effort in convergence and harmonization is needed, but this is maximally difficult because the necessary concepts are situated in the realm of the always elusive cognitive robot mind.</p>
</sec>
</body>
<back>
<sec sec-type="data-availability" id="s8">
<title>Data availability statement</title>
<p>The raw data supporting the conclusion of this article will be made available by the authors, without undue reservation.</p>
</sec>
<sec id="s9">
<title>Author contributions</title>
<p>EA: conceptualization, methodology, writing&#x2013;original draft, writing&#x2013;review and editing. VG: conceptualization, writing&#x2013;review and editing. MH: methodology, writing&#x2013;review and editing. CR: conceptualization, formal analysis, writing&#x2013;review and editing. RS: conceptualization, formal analysis, project administration, writing&#x2013;review and editing.</p>
</sec>
<sec sec-type="funding-information" id="s10">
<title>Funding</title>
<p>The author(s) declare that financial support was received for the research, authorship, and/or publication of this article. This work was partially supported by the ROBOMINERS project with funding from the European Union&#x2019;s Horizon 2020 research and innovation programme (Grant Agreement No. 820971), by the CORESENSE project with funding from the European Union&#x2019;s Horizon Europe research and innovation programme (Grant Agreement No. 101070254), and by a grant from the <italic>Programa Propio</italic> supported by the Universidad Polit&#xe9;cnica de Madrid.</p>
</sec>
<sec sec-type="COI-statement" id="s11">
<title>Conflict of interest</title>
<p>The authors declare that the research was conducted in the absence of any commercial or financial relationships that could be construed as a potential conflict of interest.</p>
</sec>
<sec sec-type="disclaimer" id="s12">
<title>Publisher&#x2019;s note</title>
<p>All claims expressed in this article are solely those of the authors and do not necessarily represent those of their affiliated organizations, or those of the publisher, the editors and the reviewers. Any product that may be evaluated in this article, or claim that may be made by its manufacturer, is not guaranteed or endorsed by the publisher.</p>
</sec>
<fn-group>
<fn id="fn1">
<label>1</label>
<p>
<ext-link ext-link-type="uri" xlink:href="https://jena.apache.org/documentation/ontology">https://jena.apache.org/documentation/ontology</ext-link>
</p>
</fn>
<fn id="fn2">
<label>2</label>
<p>
<ext-link ext-link-type="uri" xlink:href="https://github.com/owlcs/owlapi/wiki">https://github.com/owlcs/owlapi/wiki</ext-link>
</p>
</fn>
<fn id="fn3">
<label>3</label>
<p>
<ext-link ext-link-type="uri" xlink:href="http://owl.cs.manchester.ac.uk/tools/fact">http://owl.cs.manchester.ac.uk/tools/fact</ext-link>
</p>
</fn>
<fn id="fn4">
<label>4</label>
<p>
<ext-link ext-link-type="uri" xlink:href="https://github.com/stardog-union/pellet">https://github.com/stardog-union/pellet</ext-link>
</p>
</fn>
<fn id="fn5">
<label>5</label>
<p>
<ext-link ext-link-type="uri" xlink:href="http://www.hermit-reasoner.com/">http://www.hermit-reasoner.com/</ext-link>
</p>
</fn>
<fn id="fn6">
<label>6</label>
<p>
<ext-link ext-link-type="uri" xlink:href="http://www.gprolog.org/">http://www.gprolog.org/</ext-link>
</p>
</fn>
<fn id="fn7">
<label>7</label>
<p>
<ext-link ext-link-type="uri" xlink:href="https://www.swi-prolog.org/">https://www.swi-prolog.org/</ext-link>
</p>
</fn>
<fn id="fn8">
<label>8</label>
<p>
<ext-link ext-link-type="uri" xlink:href="https://github.com/KnowRob/rosprolog">https://github.com/KnowRob/rosprolog</ext-link>
</p>
</fn>
<fn id="fn9">
<label>9</label>
<p>
<ext-link ext-link-type="uri" xlink:href="https://www.ontologyportal.org">https://www.ontologyportal.org</ext-link>, <ext-link ext-link-type="uri" xlink:href="https://github.com/ontologyportal">https://github.com/ontologyportal</ext-link>
</p>
</fn>
<fn id="fn10">
<label>10</label>
<p>
<ext-link ext-link-type="uri" xlink:href="http://ontologydesignpatterns.org/wiki/Ontology:DOLCE&#x2b;DnS_Ultralite">http://ontologydesignpatterns.org/wiki/Ontology:DOLCE&#x2b;DnS_Ultralite</ext-link>
</p>
</fn>
<fn id="fn11">
<label>11</label>
<p>
<ext-link ext-link-type="uri" xlink:href="https://www.scopus.com">https://www.scopus.com</ext-link>
</p>
</fn>
<fn id="fn12">
<label>12</label>
<p>
<ext-link ext-link-type="uri" xlink:href="https://www.webofscience.com/wos/alldb/basic-search">https://www.webofscience.com/wos/alldb/basic-search</ext-link>
</p>
</fn>
<fn id="fn13">
<label>13</label>
<p>
<ext-link ext-link-type="uri" xlink:href="http://KnowRob.org">http://KnowRob.org</ext-link>
</p>
</fn>
<fn id="fn14">
<label>14</label>
<p>
<ext-link ext-link-type="uri" xlink:href="https://github.com/KnowRob/KnowRob">https://github.com/KnowRob/KnowRob</ext-link>
</p>
</fn>
<fn id="fn15">
<label>15</label>
<p>
<ext-link ext-link-type="uri" xlink:href="https://github.com/MohammedDiab1/PMK">https://github.com/MohammedDiab1/PMK</ext-link>
</p>
</fn>
<fn id="fn16">
<label>16</label>
<p>
<ext-link ext-link-type="uri" xlink:href="https://github.com/ease-crc/failrecont">https://github.com/ease-crc/failrecont</ext-link>
</p>
</fn>
<fn id="fn17">
<label>17</label>
<p>
<ext-link ext-link-type="uri" xlink:href="https://github.com/meta-control/mc_mdl_tomasys">https://github.com/meta-control/mc_mdl_tomasys</ext-link>
</p>
</fn>
<fn id="fn18">
<label>18</label>
<p>
<ext-link ext-link-type="uri" xlink:href="https://www.pr-owl.org">https://www.pr-owl.org</ext-link>
</p>
</fn>
<fn id="fn19">
<label>19</label>
<p>
<ext-link ext-link-type="uri" xlink:href="http://kb.openrobots.org/">http://kb.openrobots.org/</ext-link>
</p>
</fn>
<fn id="fn20">
<label>20</label>
<p>
<ext-link ext-link-type="uri" xlink:href="https://www.openrobots.org/wiki/oro-ontology">https://www.openrobots.org/wiki/oro-ontology</ext-link>
</p>
</fn>
<fn id="fn21">
<label>21</label>
<p>
<ext-link ext-link-type="uri" xlink:href="https://github.com/albertoOA/know_cra">https://github.com/albertoOA/know_cra</ext-link>
</p>
</fn>
<fn id="fn22">
<label>22</label>
<p>
<ext-link ext-link-type="uri" xlink:href="https://github.com/jacekmalec/Rosetta_ontology">https://github.com/jacekmalec/Rosetta_ontology</ext-link>
</p>
</fn>
</fn-group>
<ref-list>
<title>References</title>
<ref id="B1">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Abbott</surname>
<given-names>R. J.</given-names>
</name>
</person-group> (<year>1990</year>). <article-title>Resourceful systems for fault tolerance, reliability, and safety</article-title>. <source>ACM Comput. Surv.</source> <volume>22</volume>, <fpage>35</fpage>&#x2013;<lpage>68</lpage>. <pub-id pub-id-type="doi">10.1145/78949.78951</pub-id>
</citation>
</ref>
<ref id="B2">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Aguado</surname>
<given-names>E.</given-names>
</name>
<name>
<surname>G&#xf3;mez</surname>
<given-names>V.</given-names>
</name>
<name>
<surname>Hernando</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Rossi</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Sanz</surname>
<given-names>R.</given-names>
</name>
</person-group> (<year>2024</year>). &#x201c;<article-title>Category theory for autonomous robots: the marathon 2 use case</article-title>,&#x201d; in <source>Robot 2023: sixth iberian robotics conference</source>. Editors <person-group person-group-type="editor">
<name>
<surname>Marques</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Santos</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Lima</surname>
<given-names>J. L.</given-names>
</name>
<name>
<surname>Tardioli</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Ferre</surname>
<given-names>M.</given-names>
</name>
</person-group> (<publisher-loc>Cham</publisher-loc>: <publisher-name>Springer Nature Switzerland</publisher-name>), <fpage>39</fpage>&#x2013;<lpage>52</lpage>.</citation>
</ref>
<ref id="B3">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Aguado</surname>
<given-names>E.</given-names>
</name>
<name>
<surname>Milosevic</surname>
<given-names>Z.</given-names>
</name>
<name>
<surname>Hern&#xe1;ndez</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Sanz</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Garzon</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Bozhinoski</surname>
<given-names>D.</given-names>
</name>
<etal/>
</person-group> (<year>2021</year>). <article-title>Functional self-awareness and metacontrol for underwater robot autonomy</article-title>. <source>Sensors</source> <volume>21</volume>, <fpage>1210</fpage>&#x2013;<lpage>1228</lpage>. <pub-id pub-id-type="doi">10.3390/s21041210</pub-id>
</citation>
</ref>
<ref id="B4">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Antanas</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Moreno</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Neumann</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>de Figueiredo</surname>
<given-names>R. P.</given-names>
</name>
<name>
<surname>Kersting</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Santos-Victor</surname>
<given-names>J.</given-names>
</name>
<etal/>
</person-group> (<year>2019</year>). <article-title>Semantic and geometric reasoning for robotic grasping: a probabilistic logic approach</article-title>. <source>Aut. Robots</source> <volume>43</volume>, <fpage>1393</fpage>&#x2013;<lpage>1418</lpage>. <pub-id pub-id-type="doi">10.1007/s10514-018-9784-8</pub-id>
</citation>
</ref>
<ref id="B5">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Arp</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Smith</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Spear</surname>
<given-names>A. D.</given-names>
</name>
</person-group> (<year>2015</year>) <source>Building ontologies with basic formal ontology</source>. <publisher-name>The MIT Press</publisher-name>. <pub-id pub-id-type="doi">10.7551/mitpress/9780262527811.001.0001</pub-id>
</citation>
</ref>
<ref id="B6">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Avi&#x17e;ienis</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Laprie</surname>
<given-names>J.-C.</given-names>
</name>
<name>
<surname>Randell</surname>
<given-names>B.</given-names>
</name>
</person-group> (<year>2004</year>). &#x201c;<article-title>Dependability and its threats: a taxonomy</article-title>,&#x201d; in <source>Building the information society</source>. Editor <person-group person-group-type="editor">
<name>
<surname>Jacquart</surname>
<given-names>R.</given-names>
</name>
</person-group> (<publisher-loc>Boston, MA</publisher-loc>: <publisher-name>Springer US</publisher-name>), <fpage>91</fpage>&#x2013;<lpage>120</lpage>.</citation>
</ref>
<ref id="B7">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Balakirsky</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Schlenoff</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Fiorini</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Redfield</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Barreto</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Nakawala</surname>
<given-names>H.</given-names>
</name>
<etal/>
</person-group> (<year>2017</year>). &#x201c;<article-title>Towards a robot task ontology standard</article-title>,&#x201d; in <source>Proceedings of the manufacturing science and engineering conference (MSEC)</source> (<publisher-loc>Los Angeles, CA</publisher-loc>: <publisher-name>US</publisher-name>).</citation>
</ref>
<ref id="B8">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Beer</surname>
<given-names>J. M.</given-names>
</name>
<name>
<surname>Fisk</surname>
<given-names>A. D.</given-names>
</name>
<name>
<surname>Rogers</surname>
<given-names>W. A.</given-names>
</name>
</person-group> (<year>2014</year>). <article-title>Toward a framework for levels of robot autonomy in human-robot interaction</article-title>. <source>J. Hum.-Robot Interact.</source> <volume>3</volume>, <fpage>74</fpage>&#x2013;<lpage>99</lpage>. <pub-id pub-id-type="doi">10.5898/JHRI.3.2.Beer</pub-id>
</citation>
</ref>
<ref id="B9">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Beetz</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Be&#xdf;ler</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Haidu</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Pomarlan</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Bozcuo&#x1e7;lu</surname>
<given-names>A. K.</given-names>
</name>
<name>
<surname>Bartels</surname>
<given-names>G.</given-names>
</name>
</person-group> (<year>2018</year>). &#x201c;<article-title>Know rob 2.0 &#x2014; a 2nd generation knowledge processing framework for cognition-enabled robotic agents</article-title>,&#x201d; in <source>2018 IEEE international conference on robotics and automation (ICRA)</source>, <fpage>512</fpage>&#x2013;<lpage>519</lpage>. <pub-id pub-id-type="doi">10.1109/ICRA.2018.8460964</pub-id>
</citation>
</ref>
<ref id="B10">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Beetz</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>M&#xf6;senlechner</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Tenorth</surname>
<given-names>M.</given-names>
</name>
</person-group> (<year>2010</year>). &#x201c;<article-title>CRAM &#x2014; a Cognitive Robot Abstract Machine for everyday manipulation in human environments</article-title>,&#x201d; in <source>2010 IEEE/RSJ international conference on intelligent robots and systems</source>, <fpage>1012</fpage>&#x2013;<lpage>1017</lpage>. <pub-id pub-id-type="doi">10.1109/IROS.2010.5650146</pub-id>
</citation>
</ref>
<ref id="B11">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Beetz</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Tenorth</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Winkler</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2015</year>). &#x201c;<article-title>Open-EASE &#x2013; a knowledge processing service for robots and robotics/ai researchers</article-title>,&#x201d; in <source>IEEE international conference on robotics and automation (ICRA) (seattle, Washington, USA). Finalist for the best cognitive robotics paper award</source>.</citation>
</ref>
<ref id="B12">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Bermejo-Alonso</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Sanz</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Rodr&#xed;guez</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Hern&#xe1;ndez</surname>
<given-names>C.</given-names>
</name>
</person-group> (<year>2010</year>). &#x201c;<article-title>An ontology&#x2013;based approach for autonomous systems&#x2019; description and engineering</article-title>,&#x201d; in <source>Knowledge-based and intelligent information and engineering systems</source>. Editors <person-group person-group-type="editor">
<name>
<surname>Setchi</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Jordanov</surname>
<given-names>I.</given-names>
</name>
<name>
<surname>Howlett</surname>
<given-names>R. J.</given-names>
</name>
<name>
<surname>Jain</surname>
<given-names>L. C.</given-names>
</name>
</person-group> (<publisher-loc>Berlin, Heidelberg</publisher-loc>: <publisher-name>Springer Berlin Heidelberg</publisher-name>), <fpage>522</fpage>&#x2013;<lpage>531</lpage>.</citation>
</ref>
<ref id="B13">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Bernardo</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Farinha</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Gon&#xe7;alves</surname>
<given-names>P. J. S.</given-names>
</name>
</person-group> (<year>2018</year>). &#x201c;<article-title>Knowledge and tasks representation for an industrial robotic application</article-title>,&#x201d; in <source>Robot 2017: third iberian robotics conference</source>. Editors <person-group person-group-type="editor">
<name>
<surname>Ollero</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Sanfeliu</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Montano</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Lau</surname>
<given-names>N.</given-names>
</name>
<name>
<surname>Cardeira</surname>
<given-names>C.</given-names>
</name>
</person-group> (<publisher-loc>Cham</publisher-loc>: <publisher-name>Springer International Publishing</publisher-name>), <fpage>441</fpage>&#x2013;<lpage>451</lpage>.</citation>
</ref>
<ref id="B14">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Be&#xdf;ler</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Porzel</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Pomarlan</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Vyas</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>H&#xf6;ffner</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Beetz</surname>
<given-names>M.</given-names>
</name>
<etal/>
</person-group> (<year>2021</year>). &#x201c;Foundations of the socio-physical model of activities (SOMA) for autonomous robotic agents,&#x201d; in <source>Formal ontology in information systems</source> <comment>(IOS Press)</comment>, <fpage>159</fpage>&#x2013;<lpage>174</lpage>.</citation>
</ref>
<ref id="B15">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Borgo</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Cesta</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Orlandini</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Umbrico</surname>
<given-names>A.</given-names>
</name>
</person-group> (<year>2019</year>). <article-title>Knowledge-based adaptive agents for manufacturing domains</article-title>. <source>Eng. Comput.</source> <volume>35</volume>, <fpage>755</fpage>&#x2013;<lpage>779</lpage>. <pub-id pub-id-type="doi">10.1007/s00366-018-0630-6</pub-id>
</citation>
</ref>
<ref id="B16">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Bozhinoski</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Oviedo</surname>
<given-names>M. G.</given-names>
</name>
<name>
<surname>Garcia</surname>
<given-names>N. H.</given-names>
</name>
<name>
<surname>Deshpande</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>van der Hoorn</surname>
<given-names>G.</given-names>
</name>
<name>
<surname>Tjerngren</surname>
<given-names>J.</given-names>
</name>
<etal/>
</person-group> (<year>2022</year>). <article-title>MROS: runtime adaptation for robot control architectures</article-title>. <source>Adv. Robot.</source> <volume>36</volume>, <fpage>502</fpage>&#x2013;<lpage>518</lpage>. <pub-id pub-id-type="doi">10.1080/01691864.2022.2039761</pub-id>
</citation>
</ref>
<ref id="B17">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Brachman</surname>
<given-names>R.</given-names>
</name>
</person-group> (<year>2002</year>). <article-title>Systems that know what they&#x2019;re doing</article-title>. <source>IEEE Intell. Syst.</source> <volume>17</volume>, <fpage>67</fpage>&#x2013;<lpage>71</lpage>. <pub-id pub-id-type="doi">10.1109/MIS.2002.1134363</pub-id>
</citation>
</ref>
<ref id="B18">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Brown</surname>
<given-names>C. E.</given-names>
</name>
<name>
<surname>Pease</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Urban</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2023</year>). &#x201c;<article-title>Translating SUMO-K to higher-order set theory</article-title>,&#x201d; in <source>Frontiers of combining systems (FroCoS), to appear</source>.</citation>
</ref>
<ref id="B19">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Bunge</surname>
<given-names>M.</given-names>
</name>
</person-group> (<year>1977</year>) <source>Treatise on basic philosophy: volume 3: ontology I: the furniture of the world</source>. <publisher-loc>Boston, MA</publisher-loc>: <publisher-name>Reidel</publisher-name>.</citation>
</ref>
<ref id="B20">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Burroughes</surname>
<given-names>G.</given-names>
</name>
<name>
<surname>Gao</surname>
<given-names>Y.</given-names>
</name>
</person-group> (<year>2016</year>). <article-title>Ontology-based self-reconfiguring guidance, navigation, and control for planetary rovers</article-title>. <source>J. Aerosp. Inf. Syst.</source> <volume>13</volume>, <fpage>316</fpage>&#x2013;<lpage>328</lpage>. <pub-id pub-id-type="doi">10.2514/1.I010378</pub-id>
</citation>
</ref>
<ref id="B21">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Chandra</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Rocha</surname>
<given-names>R. P.</given-names>
</name>
</person-group> (<year>2016</year>). &#x201c;<article-title>Knowledge-based framework for human-robots collaborative context awareness in usar missions</article-title>,&#x201d; in <source>2016 international conference on autonomous robot systems and competitions (ICARSC)</source>, <fpage>335</fpage>&#x2013;<lpage>340</lpage>. <pub-id pub-id-type="doi">10.1109/ICARSC.2016.50</pub-id>
</citation>
</ref>
<ref id="B22">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Chang</surname>
<given-names>D. S.</given-names>
</name>
<name>
<surname>Cho</surname>
<given-names>G. H.</given-names>
</name>
<name>
<surname>Choi</surname>
<given-names>Y. S.</given-names>
</name>
</person-group> (<year>2020</year>). &#x201c;<article-title>Ontology-based knowledge model for human-robot interactive services</article-title>,&#x201d; in <source>Proceedings of the 35th annual ACM symposium on applied computing</source> (<publisher-loc>New York, NY, USA</publisher-loc>: <publisher-name>Association for Computing Machinery</publisher-name>), <fpage>2029</fpage>&#x2013;<lpage>2038</lpage>. <pub-id pub-id-type="doi">10.1145/3341105.3373977</pub-id>
</citation>
</ref>
<ref id="B23">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Cornejo-Lupa</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Ticona-Herrera</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Cardinale</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>Barrios-Aranibar</surname>
<given-names>D.</given-names>
</name>
</person-group> (<year>2020</year>). <article-title>A survey of ontologies for simultaneous localization and mapping in mobile robots</article-title>. <source>ACM Comput. Surv.</source> <volume>53</volume>, <fpage>1</fpage>&#x2013;<lpage>26</lpage>. <pub-id pub-id-type="doi">10.1145/3408316</pub-id>
</citation>
</ref>
<ref id="B24">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Crespo</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Barber</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Mozos</surname>
<given-names>O. M.</given-names>
</name>
<name>
<surname>BeBler</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Beetz</surname>
<given-names>M.</given-names>
</name>
</person-group> (<year>2018</year>). &#x201c;<article-title>Reasoning systems for semantic navigation in mobile robots</article-title>,&#x201d; in <source>2018 IEEE/RSJ international conference on intelligent robots and systems</source>, <fpage>5654</fpage>&#x2013;<lpage>5659</lpage>. <pub-id pub-id-type="doi">10.1109/IROS.2018.8594271</pub-id>
</citation>
</ref>
<ref id="B25">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Diab</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Akbari</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Rosell</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2018</year>). &#x201c;<article-title>An ontology framework for physics-based manipulation planning</article-title>,&#x201d; in <source>Robot 2017: third iberian robotics conference</source>. Editors <person-group person-group-type="editor">
<name>
<surname>Ollero</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Sanfeliu</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Montano</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Lau</surname>
<given-names>N.</given-names>
</name>
<name>
<surname>Cardeira</surname>
<given-names>C.</given-names>
</name>
</person-group> (<publisher-loc>Cham</publisher-loc>: <publisher-name>Springer International Publishing</publisher-name>), <fpage>452</fpage>&#x2013;<lpage>464</lpage>.</citation>
</ref>
<ref id="B26">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Diab</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Akbari</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Ud Din</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Rosell</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2019</year>). <article-title>PMK&#x2014;a knowledge processing framework for autonomous robotics perception and manipulation</article-title>. <source>Sensors</source> <volume>19</volume>, <fpage>1166</fpage>. <pub-id pub-id-type="doi">10.3390/s19051166</pub-id>
</citation>
</ref>
<ref id="B27">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Diab</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Pomarlan</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Be&#xdf;ler</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Akbari</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Rosell</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Bateman</surname>
<given-names>J.</given-names>
</name>
<etal/>
</person-group> (<year>2020</year>). &#x201c;<article-title>An ontology for failure interpretation in automated planning and execution</article-title>,&#x201d; in <source>Robot 2019: fourth iberian robotics conference</source>. Editors <person-group person-group-type="editor">
<name>
<surname>Silva</surname>
<given-names>M. F.</given-names>
</name>
<name>
<surname>Lu&#xed;s Lima</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Reis</surname>
<given-names>L. P.</given-names>
</name>
<name>
<surname>Sanfeliu</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Tardioli</surname>
<given-names>D.</given-names>
</name>
</person-group> (<publisher-loc>Cham</publisher-loc>: <publisher-name>Springer International Publishing</publisher-name>), <fpage>381</fpage>&#x2013;<lpage>390</lpage>.</citation>
</ref>
<ref id="B28">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Diab</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Pomarlan</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Borgo</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Be&#xdf;ler</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Rosell</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Bateman</surname>
<given-names>J.</given-names>
</name>
<etal/>
</person-group> (<year>2021</year>). &#x201c;FailRecOnt &#x2013; An Ontology-Based Framework for Failure Interpretation and Recovery in Planning and Execution,&#x201d; in <source>Proceedings of the Joint Ontology Workshops co-located with the Bolzano Summer of Knowledge (BOSK 2021)</source>, <conf-loc>Virtual &#x26; Bozen-Bolzano, Italy</conf-loc>, <conf-date>September 13&#x2013;17, 2021</conf-date>, <comment>CEUR-WS.org, 2021</comment>.</citation>
</ref>
<ref id="B29">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Fiorini</surname>
<given-names>S. R.</given-names>
</name>
<name>
<surname>Bermejo-Alonso</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Gon&#xe7;alves</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Pignaton de Freitas</surname>
<given-names>E.</given-names>
</name>
<name>
<surname>Olivares Alarcos</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Olszewska</surname>
<given-names>J. I.</given-names>
</name>
<etal/>
</person-group> (<year>2017</year>). <article-title>A suite of ontologies for robotics and automation [industrial activities]</article-title>. <source>IEEE Robotics Automation Mag.</source> <volume>24</volume>, <fpage>8</fpage>&#x2013;<lpage>11</lpage>. <pub-id pub-id-type="doi">10.1109/MRA.2016.2645444</pub-id>
</citation>
</ref>
<ref id="B30">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Gangemi</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Guarino</surname>
<given-names>N.</given-names>
</name>
<name>
<surname>Masolo</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Oltramari</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Oltramari</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Schneider</surname>
<given-names>L.</given-names>
</name>
</person-group> (<year>2002</year>). <article-title>Sweetening ontologies with DOLCE</article-title>. In <source>Proceedings of the 13th European conference on knowledge engineering and knowledge management (EKAW)</source>, <fpage>166</fpage>&#x2013;<lpage>181</lpage>.</citation>
</ref>
<ref id="B31">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Gayathri</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Uma</surname>
<given-names>V.</given-names>
</name>
</person-group> (<year>2018</year>). <article-title>Ontology based knowledge representation technique, domain modeling languages and planners for robotic path planning: a survey</article-title>. <source>ICT Express</source> <volume>4</volume>, <fpage>69</fpage>&#x2013;<lpage>74</lpage>. <pub-id pub-id-type="doi">10.1016/j.icte.2018.04.008</pub-id>
</citation>
</ref>
<ref id="B32">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Gayathri</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Uma</surname>
<given-names>V.</given-names>
</name>
</person-group> (<year>2019</year>). <article-title>A review of description logic-based techniques for robot task planning</article-title>. <source>Stud. Comput. Intell.</source> <volume>771</volume>, <fpage>101</fpage>&#x2013;<lpage>107</lpage>. <pub-id pub-id-type="doi">10.1007/978-981-10-8797-4_11</pub-id>
</citation>
</ref>
<ref id="B33">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Guarino</surname>
<given-names>N.</given-names>
</name>
</person-group> (<year>1998</year>) <source>Formal ontology in information systems: proceedings of the 1st international conference june 6-8, 1998, trento, Italy</source>. <publisher-loc>Netherlands</publisher-loc>: <publisher-name>IOS Press</publisher-name>.</citation>
</ref>
<ref id="B34">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Guiochet</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Machin</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Waeselynck</surname>
<given-names>H.</given-names>
</name>
</person-group> (<year>2017</year>). <article-title>Safety-critical advanced robots: a survey</article-title>. <source>Robotics Aut. Syst.</source> <volume>94</volume>, <fpage>43</fpage>&#x2013;<lpage>52</lpage>. <pub-id pub-id-type="doi">10.1016/j.robot.2017.04.004</pub-id>
</citation>
</ref>
<ref id="B35">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Hepp</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Bachlechner</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Siorpaes</surname>
<given-names>K.</given-names>
</name>
</person-group> (<year>2006</year>). &#x201c;<article-title>Ontowiki: community-driven ontology engineering and ontology usage based on wikis</article-title>,&#x201d; in <source>Proceedings of the 2006 international symposium on wikis</source> (<publisher-loc>New York, NY, USA</publisher-loc>: <publisher-name>Association for Computing Machinery</publisher-name>), <fpage>143</fpage>&#x2013;<lpage>144</lpage>. <pub-id pub-id-type="doi">10.1145/1149453.1149487</pub-id>
</citation>
</ref>
<ref id="B36">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Hern&#xe1;ndez</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Bermejo-Alonso</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Sanz</surname>
<given-names>R.</given-names>
</name>
</person-group> (<year>2018</year>). <article-title>A self-adaptation framework based on functional knowledge for augmented autonomy in robots</article-title>. <source>Integr. Computer-Aided Eng.</source> <volume>25</volume>, <fpage>157</fpage>&#x2013;<lpage>172</lpage>. <pub-id pub-id-type="doi">10.3233/ICA-180565</pub-id>
</citation>
</ref>
<ref id="B37">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Hoebert</surname>
<given-names>T.</given-names>
</name>
<name>
<surname>Lepuschitz</surname>
<given-names>W.</given-names>
</name>
<name>
<surname>Vincze</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Merdan</surname>
<given-names>M.</given-names>
</name>
</person-group> (<year>2021</year>). <article-title>Knowledge-driven framework for industrial robotic systems</article-title>. <source>J. Intelligent Manuf.</source> <pub-id pub-id-type="doi">10.1007/s10845-021-01826-8</pub-id>
</citation>
</ref>
<ref id="B38">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Huang</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Liang</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Yu</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Li</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Zhu</surname>
<given-names>H.</given-names>
</name>
</person-group> (<year>2019</year>). &#x201c;<article-title>Ontology-based driving scene modeling, situation assessment and decision making for autonomous vehicles</article-title>,&#x201d; in <source>2019 4th asia-pacific conference on intelligent robot systems (ACIRS)</source>, <fpage>57</fpage>&#x2013;<lpage>62</lpage>. <pub-id pub-id-type="doi">10.1109/ACIRS.2019.8935984</pub-id>
</citation>
</ref>
<ref id="B39">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Huber</surname>
<given-names>M. J.</given-names>
</name>
</person-group> (<year>1999</year>). &#x201c;<article-title>Jam: a bdi-theoretic mobile agent architecture</article-title>,&#x201d; in <source>Proceedings of the third annual conference on autonomous agents</source> (<publisher-loc>New York, NY, USA</publisher-loc>: <publisher-name>Association for Computing Machinery</publisher-name>), <fpage>236</fpage>&#x2013;<lpage>243</lpage>. <pub-id pub-id-type="doi">10.1145/301136.301202</pub-id>
</citation>
</ref>
<ref id="B40">
<citation citation-type="journal">
<collab>IBM Corporation</collab> (<year>2005</year>). <article-title>An architectural blueprint for autonomic computing</article-title>. <source>Tech. Rep.</source> <comment>White Paper</comment>. <pub-id pub-id-type="doi">10.1109/ICAC.2004.1301340</pub-id>
</citation>
</ref>
<ref id="B41">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Ieee</surname>
<given-names>S. A.</given-names>
</name>
</person-group> (<year>2015</year>). <article-title>IEEE standard ontologies for robotics and automation</article-title>. <source>IEEE Std</source> <volume>1872-2015</volume>, <fpage>1</fpage>&#x2013;<lpage>60doi</lpage>. <pub-id pub-id-type="doi">10.1109/IEEESTD.2015.7084073</pub-id>
</citation>
</ref>
<ref id="B42">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Ieee</surname>
<given-names>S. A.</given-names>
</name>
</person-group> (<year>2022</year>). &#x201c;<article-title>IEEE standard for autonomous robotics (AuR) ontology</article-title>,&#x201d; in <source>Standard IEEE std 1872</source> (<publisher-name>IEEE</publisher-name>), <fpage>2</fpage>&#x2013;<lpage>2021</lpage>. <pub-id pub-id-type="doi">10.1109/IEEESTD.2022.9774339</pub-id>
</citation>
</ref>
<ref id="B43">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Ji</surname>
<given-names>Z.</given-names>
</name>
<name>
<surname>Qiu</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Noyvirt</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Soroka</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Packianather</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Setchi</surname>
<given-names>R.</given-names>
</name>
<etal/>
</person-group> (<year>2012</year>). &#x201c;<article-title>Towards automated task planning for service robots using semantic knowledge representation</article-title>,&#x201d; in <source>IEEE 10th international conference on industrial informatics</source>, <fpage>1194</fpage>&#x2013;<lpage>1201</lpage>. <pub-id pub-id-type="doi">10.1109/INDIN.2012.6301131</pub-id>
</citation>
</ref>
<ref id="B44">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Lamy</surname>
<given-names>J.-B.</given-names>
</name>
</person-group> (<year>2017</year>). <article-title>Owlready: ontology-oriented programming in python with automatic classification and high level constructs for biomedical ontologies</article-title>. <source>Artif. Intell. Med.</source> <volume>80</volume>, <fpage>11</fpage>&#x2013;<lpage>28</lpage>. <pub-id pub-id-type="doi">10.1016/j.artmed.2017.07.002</pub-id>
</citation>
</ref>
<ref id="B45">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Langley</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Laird</surname>
<given-names>J. E.</given-names>
</name>
<name>
<surname>Rogers</surname>
<given-names>S.</given-names>
</name>
</person-group> (<year>2009</year>). <article-title>Cognitive architectures: research issues and challenges</article-title>. <source>Cognitive Syst. Res.</source> <volume>10</volume>, <fpage>141</fpage>&#x2013;<lpage>160</lpage>. <pub-id pub-id-type="doi">10.1016/j.cogsys.2006.07.004</pub-id>
</citation>
</ref>
<ref id="B46">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Laskey</surname>
<given-names>K. B.</given-names>
</name>
</person-group> (<year>2008</year>). <article-title>MEBN: a language for first-order Bayesian knowledge bases</article-title>. <source>Artif. Intell.</source> <volume>172</volume>, <fpage>140</fpage>&#x2013;<lpage>178</lpage>. <pub-id pub-id-type="doi">10.1016/j.artint.2007.09.006</pub-id>
</citation>
</ref>
<ref id="B47">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Lemaignan</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Ros</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>M&#xf6;senlechner</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Alami</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Beetz</surname>
<given-names>M.</given-names>
</name>
</person-group> (<year>2010</year>). &#x201c;<article-title>Oro, a knowledge management platform for cognitive architectures in robotics</article-title>,&#x201d; in <source>2010 IEEE/RSJ international conference on intelligent robots and systems</source>, <fpage>3548</fpage>&#x2013;<lpage>3553</lpage>. <pub-id pub-id-type="doi">10.1109/IROS.2010.5649547</pub-id>
</citation>
</ref>
<ref id="B48">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Lenat</surname>
<given-names>D. B.</given-names>
</name>
</person-group> (<year>1995</year>). <article-title>Cyc: a large-scale investment in knowledge infrastructure</article-title>. <source>Commun. ACM</source> <volume>38</volume>, <fpage>33</fpage>&#x2013;<lpage>38</lpage>. <pub-id pub-id-type="doi">10.1145/219717.219745</pub-id>
</citation>
</ref>
<ref id="B49">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Li</surname>
<given-names>X.</given-names>
</name>
<name>
<surname>Bilbao</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Mart&#xed;n-Wanton</surname>
<given-names>T.</given-names>
</name>
<name>
<surname>Bastos</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Rodriguez</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2017</year>). <article-title>SWARMs ontology: a common information model for the cooperation of underwater robots</article-title>. <source>Sensors</source> <volume>17</volume>, <fpage>569</fpage>. <pub-id pub-id-type="doi">10.3390/s17030569</pub-id>
</citation>
</ref>
<ref id="B50">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Lim</surname>
<given-names>G. H.</given-names>
</name>
<name>
<surname>Suh</surname>
<given-names>I. H.</given-names>
</name>
<name>
<surname>Suh</surname>
<given-names>H.</given-names>
</name>
</person-group> (<year>2011</year>). <article-title>Ontology-based unified robot knowledge for service robots in indoor environments</article-title>. <source>IEEE Trans. Syst. Man, Cybern. - Part A Syst. Humans</source> <volume>41</volume>, <fpage>492</fpage>&#x2013;<lpage>509</lpage>. <pub-id pub-id-type="doi">10.1109/TSMCA.2010.2076404</pub-id>
</citation>
</ref>
<ref id="B51">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Lukyanenko</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Storey</surname>
<given-names>V. C.</given-names>
</name>
<name>
<surname>Pastor</surname>
<given-names>O.</given-names>
</name>
</person-group> (<year>2021</year>). <article-title>Foundations of information technology based on bunge&#x2019;s systemist philosophy of reality</article-title>. <source>Softw. Syst. Model.</source> <volume>20</volume>, <fpage>921</fpage>&#x2013;<lpage>938</lpage>. <pub-id pub-id-type="doi">10.1007/s10270-021-00862-5</pub-id>
</citation>
</ref>
<ref id="B52">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Manzoor</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Rocha</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>Joo</surname>
<given-names>S.-H.</given-names>
</name>
<name>
<surname>Bae</surname>
<given-names>S.-H.</given-names>
</name>
<name>
<surname>Kim</surname>
<given-names>E.-J.</given-names>
</name>
<name>
<surname>Joo</surname>
<given-names>K.-J.</given-names>
</name>
<etal/>
</person-group> (<year>2021</year>). <article-title>Ontology-based knowledge representation in robotic systems: a survey oriented toward applications</article-title>. <source>Appl. Sci. Switz.</source> <volume>11</volume>, <fpage>4324</fpage>. <pub-id pub-id-type="doi">10.3390/app11104324</pub-id>
</citation>
</ref>
<ref id="B53">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Mascardi</surname>
<given-names>V.</given-names>
</name>
<name>
<surname>Cord&#xec;</surname>
<given-names>V.</given-names>
</name>
<name>
<surname>Rosso</surname>
<given-names>P.</given-names>
</name>
</person-group> (<year>2006</year>) <source>A comparison of upper ontologies (technical report DISI-TR-06-21)</source>. <publisher-name>Tech. rep., Dipartimento di Informatica e Scienze dell&#x2019;Informazione (DISI) and Universidad Polit&#xe9;cnica de Valencia</publisher-name>.</citation>
</ref>
<ref id="B54">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Merdan</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Hoebert</surname>
<given-names>T.</given-names>
</name>
<name>
<surname>List</surname>
<given-names>E.</given-names>
</name>
<name>
<surname>Lepuschitz</surname>
<given-names>W.</given-names>
</name>
</person-group> (<year>2019</year>). <article-title>Knowledge-based cyber-physical systems for assembly automation</article-title>. <source>Prod. Manuf. Res.</source> <volume>7</volume>, <fpage>223</fpage>&#x2013;<lpage>254</lpage>. <pub-id pub-id-type="doi">10.1080/21693277.2019.1618746</pub-id>
</citation>
</ref>
<ref id="B55">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Musen</surname>
<given-names>M. A.</given-names>
</name>
</person-group> (<year>2015</year>). <article-title>The prot&#xe9;g&#xe9; project: a look back and a look forward</article-title>. <source>AI Matters</source> <volume>1</volume>, <fpage>4</fpage>&#x2013;<lpage>12</lpage>. <pub-id pub-id-type="doi">10.1145/2757001.2757003</pub-id>
</citation>
</ref>
<ref id="B56">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Niles</surname>
<given-names>I.</given-names>
</name>
<name>
<surname>Pease</surname>
<given-names>A.</given-names>
</name>
</person-group> (<year>2001</year>). &#x201c;<article-title>Toward a standard upper ontology</article-title>,&#x201d; in <source>Proceedings of the 2nd international conference on formal ontology in information systems (FOIS-2001)</source>. Editors <person-group person-group-type="editor">
<name>
<surname>Welty</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Smith</surname>
<given-names>B.</given-names>
</name>
</person-group>, <fpage>2</fpage>&#x2013;<lpage>9</lpage>.</citation>
</ref>
<ref id="B57">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Olivares-Alarcos</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Be&#xdf;ler</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Khamis</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Goncalves</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Habib</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Bermejo-Alonso</surname>
<given-names>J.</given-names>
</name>
<etal/>
</person-group> (<year>2019</year>). <article-title>A review and comparison of ontology-based approaches to robot autonomy</article-title>. <source>Knowl. Eng. Rev.</source> <volume>34</volume>, <fpage>e29</fpage>. <pub-id pub-id-type="doi">10.1017/S0269888919000237</pub-id>
</citation>
</ref>
<ref id="B58">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Olivares-Alarcos</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Foix</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Borgo</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Aleny&#xe0;</surname>
<given-names>G.</given-names>
</name>
</person-group> (<year>2022</year>). <article-title>OCRA &#x2013; an ontology for collaborative robotics and adaptation</article-title>. <source>Comput. Industry</source> <volume>138</volume>, <fpage>103627</fpage>. <pub-id pub-id-type="doi">10.1016/j.compind.2022.103627</pub-id>
</citation>
</ref>
<ref id="B59">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Page</surname>
<given-names>M. J.</given-names>
</name>
<name>
<surname>McKenzie</surname>
<given-names>J. E.</given-names>
</name>
<name>
<surname>Bossuyt</surname>
<given-names>P. M.</given-names>
</name>
<name>
<surname>Boutron</surname>
<given-names>I.</given-names>
</name>
<name>
<surname>Hoffmann</surname>
<given-names>T. C.</given-names>
</name>
<name>
<surname>Mulrow</surname>
<given-names>C. D.</given-names>
</name>
<etal/>
</person-group> (<year>2021</year>). <article-title>The PRISMA 2020 statement: an updated guideline for reporting systematic reviews</article-title>. <source>BMJ</source> <volume>372</volume>, <fpage>n71</fpage>. <pub-id pub-id-type="doi">10.1136/bmj.n71</pub-id>
</citation>
</ref>
<ref id="B60">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Pease</surname>
<given-names>A.</given-names>
</name>
</person-group> (<year>2011</year>) <source>Ontology: a practical guide</source>. <publisher-loc>Angwin, CA</publisher-loc>: <publisher-name>Articulate Software Press</publisher-name>.</citation>
</ref>
<ref id="B61">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Perzylo</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Somani</surname>
<given-names>N.</given-names>
</name>
<name>
<surname>Rickert</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Knoll</surname>
<given-names>A.</given-names>
</name>
</person-group> (<year>2015</year>). &#x201c;<article-title>An ontology for cad data and geometric constraints as a link between product models and semantic robot task descriptions</article-title>,&#x201d; in <source>2015 IEEE/RSJ international conference on intelligent robots and systems (IROS)</source>, <fpage>4197</fpage>&#x2013;<lpage>4203</lpage>. <pub-id pub-id-type="doi">10.1109/IROS.2015.7353971</pub-id>
</citation>
</ref>
<ref id="B62">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Prestes</surname>
<given-names>E.</given-names>
</name>
<name>
<surname>Carbonera</surname>
<given-names>J. L.</given-names>
</name>
<name>
<surname>Rama FioriniJorge</surname>
<given-names>S. M. V. A.</given-names>
</name>
<name>
<surname>Abel</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Madhavan</surname>
<given-names>R.</given-names>
</name>
<etal/>
</person-group> (<year>2013</year>). <article-title>Towards a core ontology for robotics and automation</article-title>. <source>Robotics Aut. Syst.</source> <volume>61</volume>, <fpage>1193</fpage>&#x2013;<lpage>1204</lpage>. <pub-id pub-id-type="doi">10.1016/j.robot.2013.04.005</pub-id>
</citation>
</ref>
<ref id="B63">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Riazuelo</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Tenorth</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Di Marco</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Salas</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>G&#xe1;lvez-L&#xf3;pez</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>M&#xf6;senlechner</surname>
<given-names>L.</given-names>
</name>
<etal/>
</person-group> (<year>2015</year>). <article-title>Roboearth semantic mapping: a cloud enabled knowledge-based approach</article-title>. <source>IEEE Trans. Automation Sci. Eng.</source> <volume>12</volume>, <fpage>432</fpage>&#x2013;<lpage>443</lpage>. <pub-id pub-id-type="doi">10.1109/TASE.2014.2377791</pub-id>
</citation>
</ref>
<ref id="B64">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Russell</surname>
<given-names>S. J.</given-names>
</name>
<name>
<surname>Norvig</surname>
<given-names>P.</given-names>
</name>
</person-group> (<year>2021</year>) <source>Artificial Intelligence: a modern approach</source>. <edition>4 edn</edition>. <publisher-loc>England</publisher-loc>: <publisher-name>Pearson</publisher-name>.</citation>
</ref>
<ref id="B65">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Sanz</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Alarcon</surname>
<given-names>I.</given-names>
</name>
<name>
<surname>Segarra</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Clavijo</surname>
<given-names>J. A.</given-names>
</name>
<name>
<surname>de Antonio</surname>
<given-names>A.</given-names>
</name>
</person-group> (<year>1999</year>). <article-title>Progressive domain focalization in intelligent control systems</article-title>. <source>Control Eng. Pract.</source> <volume>7</volume>, <fpage>665</fpage>&#x2013;<lpage>671</lpage>. <pub-id pub-id-type="doi">10.1016/S0967-0661(99)00012-X</pub-id>
</citation>
</ref>
<ref id="B66">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Sanz</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Bermejo</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Rodr&#xed;guez</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Aguado</surname>
<given-names>E.</given-names>
</name>
</person-group> (<year>2021</year>). <article-title>The role of knowledge in cyber-physical systems of systems</article-title>. <source>TASK Q.</source> <volume>25</volume>, <fpage>355</fpage>&#x2013;<lpage>373</lpage>.</citation>
</ref>
<ref id="B67">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Sanz</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Matia</surname>
<given-names>F.</given-names>
</name>
<name>
<surname>Galan</surname>
<given-names>S.</given-names>
</name>
</person-group> (<year>2000</year>). &#x201c;<article-title>Fridges, elephants, and the meaning of autonomy and intelligence</article-title>,&#x201d; in <source>IEEE international symposium on intelligent control - proceedings (patras, Greece)</source>, <fpage>217</fpage>&#x2013;<lpage>222</lpage>. <pub-id pub-id-type="doi">10.1109/isic.2000.882926</pub-id>
</citation>
</ref>
<ref id="B68">
<citation citation-type="journal">
<collab>SEBoK Editorial Board</collab> (<year>2023</year>). <article-title>The guide to the systems engineering body of knowledge</article-title> (<source>SEBoK</source>), <comment>Available at: <ext-link ext-link-type="uri" xlink:href="www.sebokwiki.org">www.sebokwiki.org</ext-link>. (Accessed August 2023).</comment>
</citation>
</ref>
<ref id="B69">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Shapiro</surname>
<given-names>S. C.</given-names>
</name>
</person-group> (<year>2003</year>) <source>Encyclopedia of cognitive science</source>. <publisher-name>Macmillan Publishers Ltd</publisher-name>, <fpage>671</fpage>&#x2013;<lpage>680</lpage>. <comment>Knowledge Representation</comment>.</citation>
</ref>
<ref id="B70">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Staab</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Studer</surname>
<given-names>R.</given-names>
</name>
</person-group> (<year>2009</year>) <source>Handbook on ontologies</source>. <edition>2nd edn</edition>. <publisher-loc>Incorporated</publisher-loc>: <publisher-name>Springer Publishing Company</publisher-name>.</citation>
</ref>
<ref id="B71">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Stenmark</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Malec</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2015</year>). <article-title>Knowledge-based instruction of manipulation tasks for industrial robotics</article-title>. <source>Robotics Computer-Integrated Manuf. Special Issue Knowl. Driven Robotics Manuf.</source> <volume>33</volume>, <fpage>56</fpage>&#x2013;<lpage>67</lpage>. <pub-id pub-id-type="doi">10.1016/j.rcim.2014.07.004</pub-id>
</citation>
</ref>
<ref id="B72">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Suh</surname>
<given-names>I. H.</given-names>
</name>
<name>
<surname>Lim</surname>
<given-names>G. H.</given-names>
</name>
<name>
<surname>Hwang</surname>
<given-names>W.</given-names>
</name>
<name>
<surname>Suh</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Choi</surname>
<given-names>J.-H.</given-names>
</name>
<name>
<surname>Park</surname>
<given-names>Y.-T.</given-names>
</name>
</person-group> (<year>2007</year>). &#x201c;<article-title>Ontology-based multi-layered robot knowledge framework (omrkf) for robot intelligence</article-title>,&#x201d; in <source>2007 IEEE/RSJ international conference on intelligent robots and systems</source>, <fpage>429</fpage>&#x2013;<lpage>436</lpage>. <pub-id pub-id-type="doi">10.1109/IROS.2007.4399082</pub-id>
</citation>
</ref>
<ref id="B73">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Sun</surname>
<given-names>X.</given-names>
</name>
<name>
<surname>Zhang</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>Chen</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2019a</year>). <article-title>High-level smart decision making of a robot based on ontology in a search and rescue scenario</article-title>. <source>Future Internet</source> <volume>11</volume>, <fpage>230</fpage>. <pub-id pub-id-type="doi">10.3390/fi11110230</pub-id>
</citation>
</ref>
<ref id="B74">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Sun</surname>
<given-names>X.</given-names>
</name>
<name>
<surname>Zhang</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>Chen</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2019b</year>). <article-title>RTPO: a domain knowledge base for robot task planning</article-title>. <source>Electronics</source> <volume>8</volume>, <fpage>1105</fpage>. <pub-id pub-id-type="doi">10.3390/electronics8101105</pub-id>
</citation>
</ref>
<ref id="B75">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Tenorth</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Beetz</surname>
<given-names>M.</given-names>
</name>
</person-group> (<year>2009</year>). <article-title>Knowrob &#x2014; knowledge processing for autonomous personal robots</article-title>. in <source>2009 IEEE/RSJ international conference on intelligent robots and systems</source>, <fpage>4261</fpage>&#x2013;<lpage>4266</lpage>. <pub-id pub-id-type="doi">10.1109/IROS.2009.5354602</pub-id>
</citation>
</ref>
<ref id="B76">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Tenorth</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Beetz</surname>
<given-names>M.</given-names>
</name>
</person-group> (<year>2013</year>). <article-title>Knowrob: a knowledge processing infrastructure for cognition-enabled robots</article-title>. <source>Int. J. Robotics Res.</source> <volume>32</volume>, <fpage>566</fpage>&#x2013;<lpage>590</lpage>. <pub-id pub-id-type="doi">10.1177/0278364913481635</pub-id>
</citation>
</ref>
<ref id="B77">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Tenorth</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Clifford Perzylo</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Lafrenz</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Beetz</surname>
<given-names>M.</given-names>
</name>
</person-group> (<year>2012</year>). &#x201c;<article-title>The roboearth language: representing and exchanging knowledge about actions, objects, and environments</article-title>,&#x201d; in <source>2012 IEEE international conference on robotics and automation</source>, <fpage>1284</fpage>&#x2013;<lpage>1289</lpage>. <pub-id pub-id-type="doi">10.1109/ICRA.2012.6224812</pub-id>
</citation>
</ref>
<ref id="B78">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Vernon</surname>
<given-names>D.</given-names>
</name>
</person-group> (<year>2014</year>) <source>Artificial cognitive systems: a primer</source>. <publisher-name>The MIT Press</publisher-name>.</citation>
</ref>
<ref id="B79">
<citation citation-type="book">
<collab>W3C OWL Working Group</collab> (<year>2012</year>) <source>OWL 2 web ontology language document overview</source>. <publisher-name>World Wide Web Consortium</publisher-name>. <comment>Tech. rep</comment>.</citation>
</ref>
<ref id="B80">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Waibel</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Beetz</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Civera</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>D&#x2019;Andrea</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Elfring</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>G&#xe1;lvez-L&#xf3;pez</surname>
<given-names>D.</given-names>
</name>
<etal/>
</person-group> (<year>2011</year>). <article-title>Roboearth</article-title>. <source>IEEE Robotics Automation Mag.</source> <volume>18</volume>, <fpage>69</fpage>&#x2013;<lpage>82</lpage>. <pub-id pub-id-type="doi">10.1109/MRA.2011.941632</pub-id>
</citation>
</ref>
<ref id="B81">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Wand</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>Weber</surname>
<given-names>R.</given-names>
</name>
</person-group> (<year>1993</year>). <article-title>On the ontological expressiveness of information systems analysis and design grammars</article-title>. <source>Inf. Syst. J.</source> <volume>3</volume>, <fpage>217</fpage>&#x2013;<lpage>237</lpage>. <pub-id pub-id-type="doi">10.1111/j.1365-2575.1993.tb00127.x</pub-id>
</citation>
</ref>
</ref-list>
</back>
</article>