...

\[picture\]

The runtime memory model that represents the ontology to the applications is built by loading the domain and application ontologies and applying the filters described in the application ontology.and interpreting the annotations in different ways. The memory model is organized as a core model fully stored in memory and a collection of referenced taxonomy models stored in Solr indexes for rapid access.

File Structure

• eagle-i-app-def.owl contains axioms that define the basic annotation vocabulary (classes and properties). 
• eagle-i-core-app.owl serves as a root for the software loading mechanism. It provides the chain of imports - if an owl file is reachable directly or indirectly from this file via an owl:import statement, it will be loaded as part of the core model. It is a configurable parameter in the software.
• Files named *-app.owl contain the axioms that annotate the domain ontologies. There is typically one app file per domain owl file (e.g. mesh-app.owl -> mesh.owl).
  • Note that eagle-i-core-app.owl serves this purpose for the ero.owl file. Should eventually be renamed to ero-app.owl for consistency
  • (describe mechanism for loading referenced taxonomy files into solr)

Requirements

Every app file must declare an ontology IRI (details and examples to come)

Every app file must declare an ontology version (details and examples to come)

Every app file must import its corresponding domain owl file

Summary of app ontology (eagle-i-app-def.owl)

...