You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A straightforward dialect for situation writing/designing to be transpiled at runtime into drl rules.
The so-famous Fever situation could be described like:
packagebr.ufes.lprm.scene.examples.feversituationFeverwhen@febrile: Person(temperature > 37)
end
The situation keyword would refer to a special kind of rule with no need for an explicit consequence (RHS) which would always be internal situation life cycle management code.
There would be no need for a static SituationType-descendant Java class. The situation declaration provides enough information for building the situation class dynamically. The @<label> construct would represent that the binding variable maps to a class attribute <label> as a situation role.
short-term downfalls:
situation only file: domain rules and events would be written apart from the situations, although, defined situations could be used by any domain business rule.
The text was updated successfully, but these errors were encountered:
A straightforward dialect for
situation
writing/designing to be transpiled at runtime intodrl
rules.The so-famous
Fever
situation could be described like:situation
keyword would refer to a special kind of rule with no need for an explicit consequence (RHS) which would always be internal situation life cycle management code.SituationType
-descendant Java class. The situation declaration provides enough information for building the situation class dynamically. The@<label>
construct would represent that the binding variable maps to a class attribute<label>
as a situation role.short-term downfalls:
situation only file
: domain rules and events would be written apart from the situations, although, defined situations could be used by any domain business rule.The text was updated successfully, but these errors were encountered: