Sorry, couldn't let this one go by without a comment. (And then I really, really have to get back to work... :-) Alan, I cut out all but one paragraph of your response. I was in complete agreement with the rest of it. A well-designed, goal-oriented approach actually uses (not salience - hate that one) recency as a control strategy. Just to name-drop a little bit, but I got hooked on this approach back in 1999 working with Dr. Charles Forgy on a project at Ericsson. I also worked with him later on a JRules project where he took the time to re-write the JRules version Monkeys-and-Bananas (which used priorities to the extreme) to a goal-oriented approach. That may not be what you meant in the paragraph below, but I just thought I'd have one final comment and then go get my third cup of coffee for the day. It's 3:20 and I deserve it.
Alan Moore wrote: > Try not to let your rules don't rely too much on implicit control structures, > like salience for example. Take the time to design some explicit > system/computation state components, or use modules or other strategies that > can be employed to partition your rules and to control their activation, etc. > This advice may be controversial among some rule purists but it has helped me > immeasurably. > -- SDG jco --------------------------------- James C. Owen Senior KE Knowledgebased Systems Corporation 6314 Kelly Circle Garland, TX 75044 972.530.2895 -------------------------------------------------------------------- To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' in the BODY of a message to [EMAIL PROTECTED], NOT to the list (use your own address!) List problems? Notify [EMAIL PROTECTED] --------------------------------------------------------------------
