Page History
...
This contains directories and files needed to generate the eagle-i ontology files. The individual module sub-directories contain the module configuration files that are used by the tooling to generate the corresponding eagle-i ontology files during a local ontology generation. See the tooling documentation for further details.
src/isf/module-scripts
...
This directory can be placed on the “path” to simplify invoking them, but it is also possible to directly invoke them from this directory. The script names are self explanatory. The .bat scripts are the Windows versions and the others are Linux/Bash versions. There appears to be an issue with these scripts on Mac (probably resolved in the current version), most likely due to how the environment is setup for these scripts. Check the “source” folder to see if the Bash scripts do what they are supposed to do on Mac.
Invoking these scripts has to be done from a shell. There are two different ways to open a shell on Windows. The easier way is to use the file browser to find the “module-scripts” directory and then right click while holding down the Shift key. You should see an option saying “Open command window here” as shown in the following image. At this point you will be in the module-scripts directory and you can type the name of a specific script and hit enter to run it.
The other option for Windows is to click the Start button and enter “cmd” in the run field and hit enter. This will open a shell window but you will not be in the SVN directory. You will likely be in your home directory. From there you need to use the “cd” command to change directory to the module-scripts directory and then run a script.
...
If you are not in the module-scripts directory but would like to run a script without first changing to that directory, you have two options. Either type the full/relative path to the script file in the shell (for example, you might need to type “src/isf/module-scripts/ei-...”) or add the “module-scripts” directory to the Windows Path environment variable. Google for how to set Windows environment variables and you can adjust your “user” Path variable to include this directory. See the following image as an example. Google for instructions for doing this.
src/isf/ontology
...
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.
...
Overview
Content Tools