Hi Folks
Thanks for the input, I admit I lack OO and AI knowledge. But let me
share my thought so that everyone can input. The ideal is pretty simply,
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.
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. 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, anyone who has done something similiar, please advise. All input
and thoughts are welcome. Thanks!
Regards
Aloysius
----- Original Message -----
From: "Hart, Lewis" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 03, 2001 11:50 PM
Subject: RE: JESS: Triggering of Rules
> I have to disagree, the triggering of rules in JESS is completely
> deterministic. Given the same initial conditions and the same input facts
> asserted in the same order, -- the same rules in the same order will
always
> be fired. This even includes random number generators if you can control
> their initial "seed" values. Knowledge/rule-based systems are not
> procedural, and often the order of rule firing is not obvious beforehand,
> but this is different issue.
>
> - Lewis
> ___________________________________________
> Lewis L Hart
> GRC International [EMAIL PROTECTED]
> 1900 Gallows Rd. Voice (703)506-5938
> Vienna, Va 22182 Fax (703)556-4261
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 03, 2001 7:29 AM
> To: [EMAIL PROTECTED]
> Subject: RE: JESS: Triggering of Rules
>
> ...deleted...
>
> * AI systems are often non-deterministic, like sorting potatos sizes
> through 3 sieves - you can't be sure which hole a particular potato
> will pass, to get the correct selection.
>
> ...deleted...
>
> 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]
> ---------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> 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]
> ---------------------------------------------------------------------
>
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
