If I understand what you are doing, you probably have some legacy
data from which to work. If that's the case, don't even look at the
legacy data until you have determined the rule logic. Then decide
what data would be necessary to support that logic. If the data
exist (or if most of it
I think Matthew Hutchinson wrote:
>
> Just a conceptual question... since starting with Jess, it always seemed to
> me generally you have the rules established first, then load in facts which
> in turn trigger these rules. No problems there. But is it "proper" to
> consider having the facts alread
I would say that if you reorganized the facts and get a different answer and/or
reorganize your rules and get a different answer, your inference engine is not
valid.
I worked on a pagination app that provided the xy coords for the layout of each
page. Certainly all of the facts were already th
Hi everyone,
Just a conceptual question... since starting with Jess, it always seemed to me generally you have the rules established first, then load in facts which in turn trigger these rules. No problems there. But is it "proper" to consider having the facts already in memory and *then* adding
