Action

A procedural relation that satisfies at least one of the following conditions:

• Returns no value
• Produces output, consumes input, modifies data, or changes state in any other way

For example, the add-value action is phrased as add a value for an entity.

Function

A procedural relation that satisfies both of the following conditions:

• Returns values
• Does not produce output, consume input, modify data, or change state in any other way

For example, the get-profile-attribute function is phrased as a first string is profile attribute of a second string.

knowledge base

NOTE:  There are two uses of this term, with signficantly different definitions. When HaleyAuthority or runtime does not precede knowledge base, assume the first definition.

HaleyAuthority knowledge base:

A database that stores HaleyAuthority schema and data.

Runtime knowledge base:

A representation of the semantic role model and rules that is instantiated in the Application Object Manager at runtime.

Predicate

A function that returns one value, either True or False

rule module

A top-level rule module is a unit of rule definition, deployment, and execution. A rule module may contain sub modules or rule statements (or simply rules). A sub module may contain rule statements.

A rule module is also called agenda at runtime.

semantic role model

In HaleyAuthority, the set of concepts and the relations among them. In order for rules to be written, the objects and relations on which the rules depend must exist as part of the semantic role model.