I need to create a huge model of facts using an ontology that is external to salivators. Now I could write a script / program to remove this. My approach would be to create a java bean for each ontology class that contains the appropriate fields, methods, and references to other Java objects based on ontological relationships (possibly on a map). My question is whether there is a better way to approach this problem. I believe the general problem is that the fact model is derived from a resource accessible outside of the saliva, so I wonder if the drool (or guvnor) can have a built-in method for generating a fact model based on some structured input.
I found the discussion in the following thread:
http://drools.46999.n3.nabble.com/rules-users-Using-an-OWL-Ontology-in-drools-advice-td3724566.html
Unfortunately, I could not go very far after this conversation.
Update:
The feature article related to @alikok is very helpful. This, at least, provides the basis on which the ontology can fit. To summarize, one of the big problems when installing an ontology in a model of the java bean class is that java does not perform multiple inheritance. Almost any ontology will require this, and mine is no exception. Traits solve this with proxy classes, but they do it all in the background, allowing you to define new “traits” in drl files.
. ( ), , . , . , . , , - , .