> > Ok so I've got this AI system which transports water molecules from A to
> > B - a pipe. It uses IF, THEN rules. Can achong know where a specific
> > molecule is at a specific time ? Complex system theory, quantum mechanics,
> > Shroediger's cat - let's not get into religion !
<[EMAIL PROTECTED]> wrote:-
> This is not about religion but about correct software engineering and
> perhaps about "the right tool for the right task" (as Ernest always says.)
What I mean is about 'deterministic': discussions about what is knowable
get messy, philisophical and religious.
> > This mailing list is for jess USERS, not re-designers.
> I'm not sure what you mean by "re-designers", but this list has seen
> discussions about extensions, redesign/refactoring, and user contributions.
Good. Let's dig into Aloysius' problem.
Aloysius wrote:
> ....softwares
> are developed with embedding business rules. Nothing wrong with this
> except which time we need to add, remove, update or delete of business
> rule, we need to open up a piece of code. Change them and redeploy... The
> effort involve in doing that can vary by a great deal.
>
Do you mean that you wish to change the rule set for different
circumstances ?
> The thought is to find a way to keep rules as metadata. Each time an
> application execute, rules will be loaded on the fly and object instance
> will be asserted to match pattern.
I don't understand: "object instance will be asserted to match pattern."
>So instead of having "if" in source code,
> we will have them loaded each time and match.
>
> So for example, a "Person" require logon validation. A person is regard
> as a "Resource" which is to be registrated. Since resource has properties
> and a person has "ID", "Password", "Limit". A pattern can be form, "(test >
> $limit 400)" etc. And a Rule can contain numerous patterns etc
>
> I understand many workflow application could have done something
> similiar..
I'd appreciate knowledgable jess users checking my possibly wrong
mental model of jess, and relating it to Aloysius' requirements.
Pseudo code of jess engine:
Repeat
matching(fixed-ruleset, present-condition-set);
resolve-possible-multi-match-conflict;
update(present-condition-set, chosen-matched-rule)
Until GoalState OR noMatch.
I understand that the original post required to know which
rule had been selected, at each matched cycle. How does this relate to
Aloysius' problem description above?
Chris Glur.
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
