The resources in the KIM default IE pipeline depend on the KIM default ontology - the PROTON ontology.
When you want to add a completely different conceptual model, you have to go through all the stages of mapping an ontology to PROTON.
For mapping an ontology to PROTON you can use either equivalence, or subsumption mechanisms.
Generally subsumption is preferred, because equivalence sometimes has awkward side effects.
Subclass the three major classes from the new ontology to the corresponding three major classes in PROTON.
This means, for example, that when you make a query to the knowledge base about People from PROTON, the result will be both people from the new ontology and PROTON. On the other hand, if you search for people from the new ontology, the result will be only from the new ontology.
- Create a file called newOntology_proton.nt in which you will store all the RDF data that aligns the ontology to PROTON.
- Put this file in a dedicated folder.
- Include it in the import section of the Owlim config file.
KIM has a mechanism to control the visibility of different taxonomy parts in the WEB UI. It is done through a property.
Make your new classes from the new ontology visible in the Web UI.
- Add statements such as:
- Append those statements to <KIM_HOME>/context/default/kb/visibility.nt.
There is not much sense to make visible the classes that can be subclassed to PROTON. Such as Philosopher is a Person. They can be queried by their parents. Other classes that can not be directly mapped, and are subclassed to protons:Entity, should be displayed, to be able to chose them, when making queries.