Rule-based system

In computer science, a rule-based system is a computer system in which domain-specific knowledge is represented in the form of rules and general-purpose reasoning is used to solve problems in the domain.

Two different kinds of rule-based systems emerged within the field of artificial intelligence in the 1970s:
* Production systems, which use ''if-then rules'' to derive ''actions'' from ''conditions''.
* Logic programming systems, which use ''conclusion if conditions rules'' to derive ''conclusions'' from ''conditions''.
The differences and relationships between these two kinds of rule-based system has been a major source of misunderstanding and confusion.

Both kinds of rule-based systems use either forward or backward chaining, in contrast with imperative programs, which execute commands listed sequentially. However, logic programming systems have a logical interpretation, whereas production systems do not.

Production system rules

A classic example of a production rule-based system is the domain-specific expert system that uses rules to make deductions or choices. For example, an expert system might help a doctor choose the correct diagnosis based on a cluster of symptoms, or select tactical moves to play a game.

Rule-based systems can be used to perform lexical analysis to compile or interpret computer programs, or in natural language processing.

Rule-based programming attempts to derive execution instructions from a starting set of data and rules. This is a more indirect method than that employed by an imperative programming language, which lists execution steps sequentially.

Construction

A typical rule-based system has four basic components:

* A list of rules or rule base, which is a specific type of knowledge base.
* An inference engine or semantic reasoner, which infers information or takes action based on the interaction of input and the rule base. The interpreter executes a production system program by performing the following match-resolve-act cycle:
:* Match: In this first phase, the condition sides of all productions are matched against the contents of working memory. As a result a set (the ''conflict set'') is obtained, which consists of instantiations of all satisfied productions. An instantiation of a production is an ordered list of working memory elements that satisfies the condition side of the production.
:* Conflict-resolution: In this second phase, one of the production instantiations in the conflict set is chosen for execution. If no productions are satisfied, the interpreter halts.
:* Act: In this third phase, the actions of the production selected in the conflict-resolution phase are executed. These actions may change the contents of working memory. At the end of this phase, execution returns to the first phase.
* Temporary working memory, which is a database of facts.
* A user interface or other connection to the outside world through which input and output signals are received and sent.

Whereas the matching phase of the inference engine has a logical interpretation, the conflict resolution and action phases do not. Instead, "their semantics is usually described as a series of applications of various state-changing operators, which often gets quite involved (depending on the choices made in deciding which ECA rules fire, when, and so forth), and they can hardly be regarded as declarative".

Logic programming rules

The logic programming family of computer systems includes the programming language Prolog, the database language Datalog and the knowledge representation and problem-solving language Answer Set Programming (ASP). In all of these languages, rules are written in the form of ''clauses'':

:A :- B1, ..., Bn.

and are read as declarative sentences in logical form:

:A if B1 and ... and Bn.

In the simplest case of Horn clauses (or "definite" clauses), which are a subset of first-order logic, all of the A, B₁, ..., B_n are atomic formulae.

Although Horn clause logic programs are Turing complete, for many practical applications, it is useful to extend Horn clause programs by allowing negative conditions, implemented by negation as failure. Such extended logic programs have the knowledge representation capabilities of a non-monotonic logic.

Differences and relationships between production rules and logic programming rules

The most obvious difference between the two kinds of systems is that production rules are typically written in the forward direction, ''if A then B'', and logic programming rules are typically written in the backward direction, ''B if A''. In the case of logic programming rules, this difference is superficial and purely syntactic. It does not affect the semantics of the rules. Nor does it affect whether the rules are used to reason backwards, Prolog style, to reduce the goal ''B'' to the subgoals ''A'', or whether they are used, Datalog style, to derive ''B'' from ''A''.

In the case of production rules, the forward direction of the syntax reflects the stimulus-response character of most production rules, with the stimulus ''A'' coming before the response ''B''. Moreover, even in cases when the response is simply to draw a conclusion ''B'' from an assumption ''A'', as in modus ponens, the match-resolve-act cycle is restricted to reasoning forwards from ''A'' to ''B''. Reasoning backwards in a production system would require the use of an entirely different kind of inference engine.

In his Introduction to Cognitive Science,https://www.google.co.uk/books/edition/Mind_second_edition/gjcR1U2HT7kC?hl=en&gbpv=1&pg=PP11&printsec=frontcover Paul Thagard includes logic and rules as alternative approaches to modelling human thinking. He does not consider logic programs in general, but he considers Prolog to be, not a rule-based system, but "a programming language that uses logic representations and deductive techniques" (page 40).

He argues that rules, which have the form ''IF condition THEN action'', are "very similar" to logical conditionals, but they are simpler and have greater psychological plausibility (page 51). Among other differences between logic and rules, he argues that logic uses deduction, but rules use search (page 45) and can be used to reason either forward or backward (page 47). Sentences in logic "have to be interpreted as ''universally true''", but rules can be ''defaults'', which admit exceptions (page 44). He does not observe that all of these features of rules apply to logic programming systems.

See also

* Logic programming
* Expert systems
* Rewriting
* RuleML
* List of rule-based languages
* Learning classifier system
* Rule-based machine learning
* Rule-based modeling

References

{{Semantic Web

Rule engines