]
Mark Proctor moved JBRULES-3613 to DROOLS-114:
----------------------------------------------
Project: Drools (was: JBRULES)
Key: DROOLS-114 (was: JBRULES-3613)
Workflow: GIT Pull Request workflow (was: jira)
Component/s: (was: drools-core)
(was: drools-compiler)
Support "Defeasible" rules in Drools
------------------------------------
Key: DROOLS-114
URL:
https://issues.jboss.org/browse/DROOLS-114
Project: Drools
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Davide Sottara
Assignee: Davide Sottara
Priority: Critical
Very roughly speaking, "defeasiblity" is about rules being able to prevent
other rules from firing, or canceling the conclusions other rules.
It is used to manage "exceptions" or "(counter)arguments", where
different rules lead to conflicting conclusions and a resolution strategy has to be
applied, depending on some relative ordering (strength, salience, temporal, weight,
etc..).
While an ad-hoc implementation is possible combining salience, appropriate
insertions/retractions and the rule-based agenda, a more declarative approach should be
provided to the user.
This lack of a feature is currently a blocker for the adoption of Drools in several
medical and legal communities, just to cite some.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: