Hi,
[Sorry for stripping all the names]
> > jess is a free expert system in java derived from CLIPS.
> JESS http://herzberg.ca.sandia.gov/jess/
> isn't free for commercial use, not a good pair for JBoss IMHO.
Exactly - Jess is great, but is not free. However
it is most mature Java RETE implementations in my opinion, with some
nice ideas about JavaBeans with RuleEngine integration (simply put,
JavaBEans can be treated as facts in the RETE tree) - not useful as a
codebase due to licensing but important to know for future
reference/implementation/ideas/user-base/etc.
[...]
> Zeus Agent Toolkit http://sourceforge.net/projects/zeusagent/
> "Zeus provides an easy to use graphical development environment to
> build distributed agent systems. A RETE based rule engine and a
> backward chaining planner are bundled along with an interface to Java.
> Development Status: 5 - Production/Stable"
> The project is "BCS IT Award Winner 1997".
> They use proprietary licence
>
>http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi/~checkout~/source_code/zeus/licence.html?rev=1.1.1.1&content-type=text/html&cvsroot=zeusagent
> which seems to be Python-like.
> The most attractive variant for me.
I have talked couple of weeks ago with Zeus main developers and their RETE
implementator, about making Zeus more modular and...
*) Their RETE implementation and rule editor are pretty much not modular,
and the code is deeply "linked" with the rest of the agent platform and
gui.
*) The code does not support Java and JavaBeans as much as Jess does.
*) No "standard" API to this part of the project
*) Zeus codebase itself is huge
*) They do not like their current rule editing and RETE and would be happy
to improve it
We have discuss different options of making Zeus more modular, and one
scenario was to develop a "standard" java API to RETE-based rule based
algorithms, talk to Jess author and other Open Sourced Java RETE
implementations suggesting adaptation of the new uniform API, and
from Zeus use different RETE engines via this API. Maybe something
like that would be a way to go for J2EE platform as well? I reckon,
once standard or semistandard API is out there, different RETE projects
would adopt it, and there would be no much point picking one RETE
implementation, but enable RETE integration with J2EE in more general
sense. What others think? It would be also valueable for related
projects, like rule editors, rule convertors, bigger exert systems
environments, agent platforms etc.
I may dedicate some of my time into this myself, as we need something
similar for our own Agent Platform. (btw. I also have no idea how rule
based engines work in real life, all my experience comes from research
viewpoint, and all the need are for research purposes only at that stage).
best regards
Mariusz
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
