[rules-users] What is inference and how does it facilitate good rule design and maintenance

[Mark Proctor]

Leonardo Gomes wrote:
> I think I missed something on that post. Just posted a reply.
>
> Cheers,
> Leo.
>   
"In this scenario, aren't we moving logic that would be better expressed 
in a declarative form (drl) to facts that are coded in java?"

That facts are coded in java is incidental there use is still very 
declarative. Imperative is "how" and often procedural in nature. By 
using the inferred fact the de-coupling makes sure it's not procedural, 
the age policy rules do not invoke the card issuing rules. Secondly the 
encapsulation and the abstraction makes sure the card issuing rules do 
not know the "how" someone is an adult, they have just declaratively 
been told that they are.
> On Tue, Nov 10, 2009 at 3:05 AM, Mark Proctor <mproctor at codehaus.org> wrote:
>   
>> Just published this, where I'm trying to explain good rule design in
>> terms more familiar to software developers.
>> http://blog.athico.com/2009/11/what-is-inference-and-how-does-it.html
>>
>> Let me know what you think, and hopefully people have other ideas they
>> can add back in.
>>
>> Mark
>>
>> _______________________________________________
>> rules-users mailing list
>> rules-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/rules-users
>>
>>     
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>
>
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-users/attachments/20091110/e8fa021a/attachment.html