Achieving space domain awareness requires the identification, characterization, and tracking of space objects. Storing and leveraging associated space object data for purposes such as hostile threat assessment, object identification, and collision prediction and avoidance present further challenges. Space objects are characterized according to a variety of parameters including their identifiers, design specifications, components, subsystems, capabilities, vulnerabilities, origins, missions, orbital elements, patterns of life, processes, operational statuses, and associated persons, organizations, or nations. The Space Object Ontology provides a consensus-based realist framework (...) for formulating such characterizations in a computable fashion. Space object data are aligned with classes and relations in the Space Object Ontology and stored in a dynamically updated Resource Description Framework triple store, which can be queried to support space domain awareness and the needs of spacecraft operators. This paper presents the core of the Space Object Ontology, discusses its advantages over other approaches to space object classification, and demonstrates its ability to combine diverse sets of data from multiple sources within an expandable framework. Finally, we show how the ontology provides benefits for enhancing and maintaining longterm space domain awareness. (shrink)

The Ontology for Biomedical Investigations (OBI) is an ontology that provides terms with precisely defined meanings to describe all aspects of how investigations in the biological and medical domains are conducted. OBI re-uses ontologies that provide a representation of biomedical knowledge from the Open Biological and Biomedical Ontologies (OBO) project and adds the ability to describe how this knowledge was derived. We here describe the state of OBI and several applications that are using it, such as adding semantic expressivity to (...) existing databases, building data entry forms, and enabling interoperability between knowledge resources. OBI covers all phases of the investigation process, such as planning, execution and reporting. It represents information and material entities that participate in these processes, as well as roles and functions. Prior to OBI, it was not possible to use a single internally consistent resource that could be applied to multiple types of experiments for these applications. OBI has made this possible by creating terms for entities involved in biological and medical investigations and by importing parts of other biomedical ontologies such as GO, Chemical Entities of Biological Interest (ChEBI) and Phenotype Attribute and Trait Ontology (PATO) without altering their meaning. OBI is being used in a wide range of projects covering genomics, multi-omics, immunology, and catalogs of services. OBI has also spawned other ontologies (Information Artifact Ontology) and methods for importing parts of ontologies (Minimum information to reference an external ontology term (MIREOT)). The OBI project is an open cross-disciplinary collaborative effort, encompassing multiple research communities from around the globe. To date, OBI has created 2366 classes and 40 relations along with textual and formal definitions. The OBI Consortium maintains a web resource providing details on the people, policies, and issues being addressed in association with OBI. (shrink)

The notion of function is indispensable to our understanding of distinctions such as that between being broken and being in working order (for artifacts) and between being diseased and being healthy (for organisms). A clear account of the ontology of functions and functioning is thus an important desideratum for any top-level ontology intended for application to domains such as engineering or medicine. The benefit of using top-level ontologies in applied ontology can only be realized when each of the categories identified (...) and defined by a top-level ontology is integrated with the others in a coherent fashion. Basic Formal Ontology (BFO) has from the beginning included function as one of its categories, exploiting a version of the etiological account of function that is framed at a level of generality sufficient to accommodate both biological and artifactual functions. This account has been subjected to a series of criticisms and refinements. We here articulate BFO’s account of function, provide some reasons for favoring it over competing views, and defend it against objections. (shrink)

As engineering applications require management of ever larger volumes of data, ontologies offer the potential to capture, manage, and augment data with the capability for automated reasoning and semantic querying. Unfortunately, considerable barriers hinder wider deployment of ontologies in engineering. Key among these is lack of a shared top-level ontology to unify and organise disparate aspects of the field and coordinate co-development of orthogonal ontologies. As a result, many engineering ontologies are limited to their scope, and functionally difficult to extend (...) or interoperate with other engineering ontologies. This paper demonstrates how the use of a top-level ontology, specifically the Basic Formal Ontology (BFO), greatly facilitates interoperability of multiple engineering-related ontologies. We constructed a system of formal linked ontologies by re-engineering legacy ontologies to be conformant with BFO and developing new BFO-conformant ontologies to capture knowledge in the engineering design, enterprise, human factors, manufacturing, and application domain of additive manufacturing. The resulting Integrated Framework for Additively Manufactured Products (IFAMP), including the body knowledge instantiated on its basis, serve as the basis for a proposed Design with Additive Manufacturing Method (DWAM), which we believe can support the design of innovative products with semantically enhanced ideation tools and enhanced access to application domain knowledge. The method and its facilitation through the ontological framework are demonstrated using a case study in medicine. (shrink)

When the U.S. conducts warfare, elements of a force are drawn from different services and work together as a single team to accomplish an assigned mission. To achieve such unified action, it is necessary that the doctrines governing the actions of members of specific services be both consistent with and subservient to joint Doctrine. Because warfighting today increasingly involves not only live forces but also automated systems, unified action requires that information technology that is used in joint warfare must be (...) aligned with joint doctrine. It requires also that the separate information systems used by the different elements of a joint force must be interoperable, in the sense that data and information that is generated by each element must be usable (understandable, processable) by all the other elements that need them. Currently, such interoperability is impeded by multiple inconsistencies among the different data and software standards used by warfighters. We describe here the on-going project of creating a Joint Doctrine Ontology (JDO), which uses joint doctrine to provide shared computer-accessible content valid for any field of military endeavor, organization, and information system. JDO addresses the two previously mentioned requirements of unified action by providing a widely applicable benchmark for use by developers of information systems that will both guarantee alignment with joint doctrine and support interoperability. (shrink)