We propose capability as a universal or type intermediate between function and disposition. A capability is, broadly speaking, a disposition that is of a type whose instances can be evaluated on the basis of how well they are realized. A function, on the view we are proposing, is a capability the possession of which is the rationale for the existence of its bearer. To say for example that a water pump has the function to pump water is to say that (...) the pump exists because something was needed that would pump water. A water pump may have many capabilities, including: to be weatherproof, to run without lubricant, to be transportable, and so forth. But its function is to pump water. We focus here on capabilities possessed by humans – such as piano playing or language using – and we explore the relation between capabilities of these sorts and structures in the brain. (shrink)

Volume 20, Issue 8, August 2020, Page 96-98.

Pavarini et al. argue for the potential benefits of using games and other technologies to collect empirical data to enhance bioethics research. They propose a methodology called “design bioe...

We propose a domain-level ontology of plays for the facilitation of play-based collaborative autonomy among unmanned and manned-unmanned aircraft teams in the Army’s Unmanned Aircraft System (UAS) mission domain. We define a play as a type of plan that prescribes some pattern of intentional acts that are intended to reliably result in some goal in some competitive context, and which specifies one or more roles that are realized by those prescribed intentional acts. The ontology is well suited to be extended (...) to other types of military and nonmilitary unmanned vehicle operations. (shrink)

Applied ontologies have been used more and more frequently to enhance systems engineering. In this paper, we argue that adopting principles of ontological realism can increase the benefits that ontologies have already been shown to provide to the systems engineering process. Moreover, adopting Basic Formal Ontology (BFO), an ISO standard for top-level ontologies from which more domain specific ontologies are constructed, can lead to benefits in four distinct areas of systems engineering: (1) interoperability, (2) standardization, (3) testing, and (4) data (...) exploitation. Reaping these benefits in a model-based systems engineering (MBSE) context requires utilizing an ontology’s vocabulary when modeling systems and entities within those systems. If the chosen ontology abides by the principles of ontological realism, a semantic standard capable of uniting distinct domains, using BFO as a hub, can be leveraged to promote greater interoperability among systems. As interoperability and standardization increase, so does the ability to collect data during the testing and implementation of systems. These data can then be reasoned over by computational reasoners using the logical axioms within the ontology. This, in turn, generates new data that would have been impossible or too inefficient to generate without the aid of computational reasoners. (shrink)

A disposition, in Basic Formal Ontology (BFO), is defined as an intrinsic property of an entity that is realized by processes of a specific type in which that entity participates. We define capability as a disposition in whose realization one or more organisms have an interest. A function in BFO is (simplifying somewhat) a disposition whose realization is the rationale for the existence of its bearer. To say, for example, that a water pump has the function to pump water is (...) to say that the pump exists because something was needed that would pump water. Capabilities are like functions in that they are marked by the fact that they can be evaluated on the basis of how well they are realized. They differ from functions in that they are not the rationale for the existence of their bearers. Thus, a water pump may have many capabilities – such as: to be weatherproof, to run without lubricant – in addition to its primary capability, which is its function. We argue that all functions are capabilities, but not all capabilities are functions, and develop a series of axioms to formally distinguish capabilities from both functions and dispositions. (shrink)

In “Toward an Ontology of Commercial Exchange” [11], we proposed human readable definitions for terms that are central to an ontology of commercial exchange. This paper furthers that project in two ways. First, the definitions have been modified to be compatible with the Common Core Ontologies (CCO). CCO is used in a wide variety of domains including the industrial and military domains. Having a commerce ontology compatible with CCO allows data about the exchange of goods relevant to those domains to (...) be tagged with compatible ontologies. Second, we propose preliminary formalizations of these definitions, with the aim of informing the creation of an ontology which can be used to assist in reasoning over businessrelated data. (shrink)

In this paper we propose an Ontology of Commercial Exchange (OCE) based on Basic Formal Ontology. OCE is designed for re-use in the Industrial Ontologies Foundry (IOF) and in other ontologies addressing different aspects of human social behavior involving purchasing, selling, marketing, and so forth. We first evaluate some of the design patterns used in the Financial Industry Business Ontology (FIBO) and Product Types Ontology (PTO). We then propose terms and definitions that we believe will improve the representation of contractual (...) obligations, sales processes, and their associated documents. A commercial exchange, for instance, involves mutual agreement to reciprocate actions, such as transferring money, performing a service, or transferring goods. (shrink)