2023-10-29 22:44:05 -04:00
2023-10-29 20:24:06 -04:00
2023-04-07 12:54:18 -04:00
2023-09-18 23:31:31 -04:00
2023-04-07 12:54:18 -04:00
2023-04-07 12:54:18 -04:00
2023-09-20 13:00:50 -04:00
2023-04-07 12:21:03 -04:00
2023-04-07 13:02:19 -04:00
2023-04-07 12:54:18 -04:00
2023-10-29 22:44:05 -04:00

Aligning CCO to BFO2020 Core

Summary of Changes

  1. The subset of RO is no longer imported. Five properties from CCO are deprecated. Four RO properties have no replacement.
  2. The following mapping is provided:
  1. All role constraints are removed, a scope note is added to track what was deleted for users that may want to use.
    • The role constraints on subs of is_about / is_subject_of may stay, depending on consensus on a unified model for information in the CCO.
  2. Removed the restriction on cco:GeospatialRegionBooundingBox hat uses cco:non_tangential_part. This is inconsistent with BFO2020, which adds disjointness between site, spatial region, and boundaries.
  3. Added BFO_0000144 [process profile] (Confirm metadata, new definition, no use of has_process_profile)
  4. Removed dubious parthood restrictions from cco:WiredCommunicationRelayArtifactFunction
  5. has_process_part / is_part_of_process now subs of BFO_0000117 / BFO_0000132 [occurrent part] (confirm transitivity of parent not a problem)
  6. is_site_of/occurs_at now subs of BFO_0000183 / BFO_0000066 [environs/occurs in], domain/range fixed to match definitions, now only bfo:site
  7. Changed the range and inverse for is_temporal_region_of. Range now matches definition (process or process boundary). Inverse is now BFO_0000199 (why doesnt bfo have an inverse of for 199?)

The Common Core Ontologies (CCO) comprise twelve ontologies that are designed to represent and integrate taxonomies of generic classes and relations across all domains of interest.

CCO is a mid-level extension of Basic Formal Ontology (BFO), an upper-level ontology framework widely used to structure and integrate ontologies in the biomedical domain (Arp, et al., 2015). BFO aims to represent the most generic categories of entity and the most generic types of relations that hold between them, by defining a small number of classes and relations. CCO then extends from BFO in the sense that every class in CCO is asserted to be a subclass of some class in BFO, and that CCO adopts the generic relations defined in BFO (e.g., has_part) (Smith and Grenon, 2004). Accordingly, CCO classes and relations are heavily constrained by the BFO framework, from which it inherits much of its basic semantic relationships.

The CCO provide semantics for concepts and relations that are used in most domains of interest. The utility of the CCO comes from preventing BFO-compliant domain-specific ontologies from needlessly duplicating common concepts or from forcing such ontologies to include concepts outside of their domain (e.g. organization in the Ontology of Biomedical Investigations).

This utility has been realized by a number of U.S. Government sponsored projects in which either existing BFO compliant ontologies were aligned to the CCO or domain ontologies were created by using the CCO as a starting point and adding classes and properties as needed.

The names of a sample of these domain ontologies are provided in the list below.

The U.S. Government holds Government Purpose Rights on all of these domain ontologies. To obtain one or more of these domain ontologies for a government purpose it will be necessary for a government representative to contact the government sponsor of the development of the ontology. CUBRC can facilitate these connections so if interested please use the contact link at the bottom of https://www.cubrc.org/index.php/data-science-and-information-fusion/ontology .

Sample of Common Core Domain Ontology Extensions

Aircraft Ontology

Airforce Aircraft Maintenance Ontology

Army Universal Task List Ontology

Atmospheric Feature Ontology

Cyber Ontology

Hydrographic Feature Ontology

Legal and Criminal Act Ontology

Marine Corps Task List Ontology

Military Operations Ontology

Mission Planning Ontology

Occupation Ontology

Outerspace Ontology

Physiographic Feature Ontology

Sensor Ontology

Spacecraft Mission Ontology

Spacecraft Ontology

Space Event Ontology

Space Object Ontology

Transportation Infrastructure Ontology

Undersea Warfare Ontology

Watercraft Ontology

Description
No description provided
Readme BSD-3-Clause 23 MiB
Languages
Python 41.7%
Makefile 38%
Shell 19.7%
HTML 0.6%