Updating the OWLIM configuration

If you extend the KIM ontology prior to using KIM to annotate a document, we recommend that you add the new RDF files to the initial load list of the embedded OWLIM.

Place all RDF files created above in <KIM_HOME>/context/default/kb or any sub-folder.
Append the files to the initial load list in <KIM_HOME>/config/owlim.ttl, noting the RDF files relative paths to <KIM_HOME/context/default. See the following example configuration:

For details on configuration options, see the OWLIM documentation. When adding ontologies with more than 1 mln. statements, you will need to edit the database configuration in order to have good performance. The OWLIM product page on our website also offers presentations, free white papers and use cases, demonstrating the capabilities of the semantic repository.

NOTES:

imports and defaultNS sections must be delimited by semicolon.
A default namespace must be defined for each imported file. If you do not fill in both imports and defaultNS, OWLIM will report an error and refuse to start.
All statements in the files from the imports section are treated as axioms and cannot be removed.
The serialization format is automatically determined.

Finally, reset KIM to its initial state by stopping the server if started, including Apache Tomcat and removing the whole <KIM_HOME>/context/default/populated directory. This removes all annotated documents.

If you need to extend the ontology of a KIM Server without losing existing documents, don't change the initial load list of the embedded BigOWLIM, but import the new RDF using the RDF Import Tool. Afterwards, stop the KIM Server and Tomcat, delete the whole <KIM_HOME>/context/default/populated/cache directory and start the server again. Naturally, in that case, the ontology changes will not be reflected in the previously annotated documents.