Page History

...

Static application ontology files

 These files are located under the src/eagle-i/application directory when an SVN checkout is done. They have “app” in their name, are committed to SVN, and they have OWL imports that import the “non-app” ontology files that are generated in the src/eagle-i/public folder when the generation scripts or build tools are used.

...

To properly edit these files (add annotations, preferred labels, etc.), it is important that they have access to the latest generated ontology files based on the same SVN revision. To help with this, the tools should be used to generate the files based on the current SVN revision that is checked out. The additional benefit for running the build tool before viewing the application files is that Protege catalog files will be generated in the relevant directories to make sure that all imports are resolved locally instead of pulling them from the web.

Generated ontology files 

These files, are generated with the tools based on the definition/configuration in each of their modules. They can be generated as needed with the provided tools.

...

eagle-i ontology import structure

The following image shows the import structure of the eagle-i ontology:

...

In Protege 5, when all the files are loaded locally, looking at the import view should show that all imports are coming from local files:

In Protege 4, opening the “File -> Loaded ontology sources” should provide the same information. This same window in Protege 5 has become unusable.

...