|
Hi All,
I am looking at a new technique for rules
programming where "mere mortals" can build rule-based systems. Essentially, the
technique uses UML-defined base classes to define a core predicate (that can
also call other methods to define conditional tests) and a core action (that can
also call other methods to accomplish desired actions). This technique relies on
the Rete algorithm for matching of these rule objects and user-defined "data
objects" which are passed to the rule objects for inspection. If the objects
pass the conditional testing by the rule object's predicate, then the RHS is
invoked to call the rule object's action method.
It would seem that this technique could be used by
all the OPS-like rules engines (JESS/JRules/OPSJ/JEOPS) out there and would
enable ordinary Java programmers to write rules in an object-oriented manner for
a Rete-enabled environment. This technique should not inhibit
forward/backward chaining in any way and also allow for control flow logic to be
incorporated into the system.
Anybody have any thoughts ?????
"Life, liberty, and the pursuit of those who threaten it" |
- JESS: A Different Rule Programming Technique Rich Halsey
- Re: JESS: A Different Rule Programming Technique griss
- Re: JESS: A Different Rule Programming Technique Rich Halsey
- Re: JESS: A Different Rule Programming Technique Rich Halsey
- JESS: More Reasons to Use A Different Rule Programming... Rich Halsey
- JESS: Query query... James O'Brien
- Re: JESS: Query query... ejfried
- RE: JESS: A Different Rule Programming Technique Govoni, Darren
- Re: JESS: A Different Rule Programming Technique Rich Halsey
