Constructing Non-Persistent Dynamic Rules

Dynamic rules are assembled for execution at runtime rather than being compiled into the knowledge base executable. One way to achieve dynamic rules is to store rules in a rulebase and load them into the knowledge base at run time. Such rules are known as persistent dynamic rules. The Aion mechanisms that support persistent dynamic rules also support their opposite, namely, non‑persistent dynamic rules. Non-persistent dynamic rules are rules created at runtime within the knowledge itself. Instead of programming a rule, the Aion application developer programs logic that literally constructs the definition of a rule as the knowledge base is executing. Rules defined in this manner do not exist beyond the execution of the knowledge base.

Using non-persistent rules could be beneficial if the structure of the rules is highly dependent upon changing, external conditions. For example, non-persistent rules could be used when the conditions and actions that should be considered, and how they should be considered, depends on available data. Another potential use of non-persistent rules is to construct rules that the knowledge base reads from an XML document. In this case, the knowledge base must also have access to an XML translator.

Note: Non-persistent dynamic rules are intended for use by advanced Aion application developers.