Page History
...
Below, we define the properties, and axiomitization patterns and prescribed conventions for their use to guide how the eagle-i application layer builds a user interface and captures data in the SWEET curation tool. But first we provide a glossary of concepts and terms that are essential for understanding the interplay between the eagle-I ontologies and applications.
...
Table of Contents
Notation Conventions in this Document
...
Concept 2: Extended vs Core Domain Content (model / files / classes)
...
This is an artificial distinction made based on how MIREOTed content is stored and loaded into memory.
"Extended" content (files / taxonomies / terms) comes from five ontology imports (Uberon, GO, MP, Pato, DOID). Due to their size, these are stored in owl files separate from the ero.owl core file that holds all other domain content. Their content makes these files too large to be loaded into memory as the application runs, and are therefore indexed separately and dynamically called as needed. These files are also handled separately by build scripts and housed in separate files at the end of the build pipeline.
...
Concept 3: Resource Classes (aka Instantiated Classes)
“Resource” classes represent entities considered to be research resources for which instances are created in the eagle-i data. Subtypes of this concept include "primary" resources that are cataloged and shared, "embedded" resources that are directly related (1:1) with a single primary resource instance, and "stubbed" resources that can be related to more than one primary or embedded resource instance (and also not cataloged or shared in eagle-i).
...
Overview
Content Tools