Changing the visibility of resources

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:

{noformat}
<http//dbpedia.org/ontology/Actor> <http://www.ontotext.com/kim/2006/05/kimso#visibilityLevel1> "" .
<http//dbpedia.org/ontology/Artist> <http://www.ontotext.com/kim/2006/05/kimso#visibilityLevel1> "" .
........
{noformat}

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:

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.