github/CommonCoreOntologies
1
1
Fork 0
mirror of https://github.com/CommonCoreOntology/CommonCoreOntologies.git synced 2026-04-27 03:00:27 -04:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #424 from CommonCoreOntology/bugfix/add-content-to-master-readme

Browse Source 
Added references to memo, PAR3195.1; spelling
This commit is contained in:
J. Neil Otte
2024-08-18 22:53:50 -04:00
committed by GitHub
parent 9376002f1a 1bf7d75261
commit e0c094d50a
1 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@@ -6,13 +6,15 @@ The Common Core Ontologies (CCO) is a widely-used suite of eleven ontologies tha
These eleven ontologies constitute a [mid-level ontology](https://arxiv.org/abs/2404.17757) that extends from the [Basic Formal Ontology (BFO)](https://github.com/bfo-ontology/BFO-2020), an [ISO-standard](https://www.iso.org/standard/71954.html) top-level ontology. Whereas BFO represents only the most generic entities and relations, CCO contains classes that users will find common across data sets in many domains. Such classes include, for example, person, facility, date, employment, nickname, and measurement.
Leveraging CCO makes it easier to use the top-level ontology content provided by BFO, and it prevents BFO-compliant domain-specific ontologies from duplicating common concepts. Many organizations within the U.S. Government have found this useful as they seek a coordinated strategy among independent ontology efforts.
Both BFO and CCO have been directed for use as "[baseline standards](https://www.buffalo.edu/news/releases/2024/02/department-of-defense-ontology.html)" for formal ontology development across the United States Department of Defense and Intelligence Community.
CCO itself is not intended to be extended indefinitely into particular domains. Users are encouraged to create their own domain extensions with content particular to those domains and publish these ontologies for re-use by others.
CCO is currently being evaluated as a mid-level ontology standard by the IEEE Standards Association under [PAR3195.1](https://standards.ieee.org/ieee/3195.1/11026/).
CCO itself is not intended to grow indefinitely by including content that is proper to particular domains. Users are encouraged to create their own domain extensions with content particular to those domains and publish these ontologies for re-use by others.
## Contributing
Users may find the current release files for CCO [INSERT RELEASE LINK]()
Users may find the current release files for [CCO here](https://github.com/CommonCoreOntology/CommonCoreOntologies/releases/tag/v1.5-2024-02-14)
Developers may clone this repository and directly import AllCoreOntology.ttl in an ontology editor such as [Protégé](https://protege.stanford.edu/) to generate the merged version of the eleven CCO ontologies. Those who wish to forego managing imports may find a merged version of the files at src/cco-merged/
@@ -62,7 +64,7 @@ For more information about the governance of CCO, please navigate to the [Common
* **cco extensions** - Contains versions of CCO extensions maintained by the governance board, such as the Modal Relations Ontology.
* **.github** - This directory contains files needed to support automated GitHub actions.
* **deployment**
* **sparql** - Contains sparl files used in quality control checks during the development process.
* **sparql** - Contains sparql files used in quality control checks during the development process.
* **ontology-diff-files** - Contains ontology-diff-files, which Mark can tell you more about.
* **mappings** - Contains mappings between content in CCO and other ontologies.
* **templates** - Contains templates used to create issues and discussion topics.