Most OWL formatted loads make use of the least complicated procedure to achieve an installation. However, it is a popular format and LexEVS offers some extensive options for customizing a terminology at load time. Therefore step by step instructions are provided for an OWL load.
Step | Action |
---|---|
1 | Obtain an OWL formatted source. |
2 | Load the source without options. ./LoadOWL.sh -in "file:///home/LargeStorage/ontologies/owl/amino-acid.owl" Load in Windows environments: LoadOWL.bat -in "file:///home/LargeStorage/ontologies/owl/amino-acid.owl" Sample output on success: |
3 | Load source with options: ./LoadOWL.sh -in "file:///data/phont/LexEVS/test/resources/testData/camera.owl" -mf "file:///data/phont/LexEVS/test/resources/testData/Camera-manifest.xml" Loading in Windows LoadOWL.bat -in "file:///data/phont/LexEVS/test/resources/testData/camera.owl" -mf "file:///data/phont/LexEVS/test/resources/testData/Camera-manifest.xml" |
Special considerations for OWL2 loads in LexEVS 6.x. OWL2 offers some unique possibilities for authoring and representation. Some terminologies contain a wide range of namespaces that need to be referenced within the code system in order for certain kinds of namespace based searches and hierarchy traversals to take place. Other options for load alterations can be made via a preferences file which can set root nodes and enable loading of Annotation Properties as relationships via a "strict owl" interpretation of the source.
Step | Action |
---|---|
1 | Obtain or write an OWL2 source An example is the OBI Ontology described here: http://obi-ontology.org/page/Main_Page With source currently available here: http://svn.code.sf.net/p/obi/code/releases/2015-09-15/obi.owl |
2 | Create a manifest and preferences file for this source Manifests are XML files formatted to an XML schema. They are easiest to create when using an XML editor that can reference an XML schema. The manifest schema is hosted here: http://LexGrid.org/schema/2010/01/LexOnt/CodingSchemeManifest For OWL2 the user can create one like the example for regular OWL above but add a tag for mappings that will help define namespaces in the OBI load: <supportedCodingScheme isImported="false" localId="OBI" urn="http://purl.obolibrary.org/obo/obi.owl#" xmlns="http://LexGrid.org/schema/2008/01/LexGrid/codingSchemes"/>
|
3 | Load source with options using option files |