{scrollbar:icons=false}

Page info
title title

OWL One Terminology Loads

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. The National Center for Bio Ontology (NCBO Multiexcerpt include nopanel true MultiExcerptName ExitDisclaimer PageWithExcerpt wikicontent:Exit Disclaimer to Include ) hosts OWL formatted and other sources and downloads of some sources are available. Save the source to a local folder.
2	Load the source without options. Load in Linux/Unix environments: Code Block ./LoadOWL.sh -in "file:///home/LargeStorage/ontologies/owl/amino-acid.owl" Load in Windows environments: Code Block LoadOWL.bat -in "file:///home/LargeStorage/ontologies/owl/amino-acid.owl" Sample output on success:
3	Load source with options: Some sources may not offer much in the way of information about the terminology. Since this information is often found in resources outside the terminology itself, LexEVS offers an option to load it in an accompanying manifest file. This is an example of an OWL file with minimal metadata about the terminology: and this manifest file allows the user to add appropriate metadata: Manifest file construction is detailed in the administrative guide. Loading in LInux/Unix Code Block ./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 Code Block LoadOWL.bat -in "file:///data/phont/LexEVS/test/resources/testData/camera.owl" -mf "file:///data/phont/LexEVS/test/resources/testData/Camera-manifest.xml"

...

OWL2 Terminology Loads

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. 

...