In order to be able to see and use the new classes and properties in the web interface, KIM uses a visibility mechanism. The new resources have to be defined as visible in
KIM/context/default/kb/visibility.nt . Here is an excerpt:
Clear the cache of KIM (remove KIM/context/default/populated) and start it again, you should be able to see the additional classes in the ontology view:
Unable to render embedded object: File (worddavf8b746a72d622da031182400598f2b83.png) not found.
Figure 7. The new ontology in the KIM Web UI
We have shown how to utilize only the Person class from the new ontology. The process is identical for the other classes.
Described here is only a single approach for adopting a new ontology into KIM. Every ontology is unique and may require a different setup. For example, you can use only a single gazetteer to create Lookup annotations for all the instances, and then jape rules to determine their real annotation type. This will require only changing the default gazetteer query in KIM/config/query.txt and writing some jape rules.