Great!. You can write rules in a Graphic Rule Editor named Oryx (GPL) and execute them into mandarax (the rule engine). Mandarax supports RuleML (a standard specification for rules) then you can port rules to other compatible rule engine (in theory, Jess?).
I used Mandarax in a project (I was the project leader) and I advertise you: use it only if you are a expert in prolog and you know how WAM (Warren Abstract Machine) solves problems.
The integration of knowledge with Mandarax is great and beautiful, you can use Mandarax to integrate multiple data stores in multiple technologies: you can integrate html, webservices, data buses (like tibco), relational databaes (oracle,..), text files, xml files, and so on in a virtual memory database and merge data in memory for resolving querys. You will need write some java-mandarax adapters (ClauseSet) between those systems and mandarax, then you can launch SQL!! querys in Mandarax and resolve complex relations (on-line) over remote systems.
The performance may be the worst aspect of Mandarax if you write nested rules in many levels, like it occurs in prolog.
Finally, mandarax justifies the responses, in other words you can view what rules,the order and data which resolves your problem.
Great!. You can write rules in a Graphic Rule Editor named Oryx (GPL) and execute them into mandarax (the rule engine). Mandarax supports RuleML (a standard specification for rules) then you can port rules to other compatible rule engine (in theory, Jess?).
I used Mandarax in a project (I was the project leader) and I advertise you: use it only if you are a expert in prolog and you know how WAM (Warren Abstract Machine) solves problems.
The integration of knowledge with Mandarax is great and beautiful, you can use Mandarax to integrate multiple data stores in multiple technologies: you can integrate html, webservices, data buses (like tibco), relational databaes (oracle,..), text files, xml files, and so on in a virtual memory database and merge data in memory for resolving querys. You will need write some java-mandarax adapters (ClauseSet) between those systems and mandarax, then you can launch SQL!! querys in Mandarax and resolve complex relations (on-line) over remote systems.
The performance may be the worst aspect of Mandarax if you write nested rules in many levels, like it occurs in prolog.
Finally, mandarax justifies the responses, in other words you can view what rules,the order and data which resolves your problem.
Regards, pbeltranl@gmail.com