Rules For Knowledge Representation
Rules For Knowledge Representation
One way to represent knowledge is by using rules that express what must happen or what
does happen when certain conditions are met.
Rules are usually expressed in the form of IF . . . THEN . . . statements, such as: IF A THEN
B This can be considered to have a similar logical meaning as the following: A→B
In expressing rules, the consequent usually takes the form of an action or a conclusion.
In other words, the purpose of a rule is usually to tell a system (such as an expert system)
what to do in certain circumstances, or what conclusions to draw from a set of inputs about
the current situation.
In general, a rule can have more than one antecedent, usually combined either by AND or by
OR (logically the same as the operators ∧ and ∨).
In general, the antecedent of a rule compares an object with a possible value, using an
operator.
For example, suitable antecedents in a rule might be
IF x > 3
IF name is “Bob”
IF weather is cold
Here, the objects being considered are x, name, and weather; the operators are “>” and “is”,
and the values are 3, “Bob,” and cold.
Note that an object is not necessarily an object in the real-world sense—the weather is not a
real world object, but rather a state or condition of the world.
An object in this sense is simply a variable that represents some physical object or state in the
real world.
An example of a rule might be
IF name is “Bob”
This is an example of a recommendation rule, which takes a set of inputsand gives advice as a
result.
The conclusion of the rule is actually an action, and the action takes the form of a
recommendation to Bob that he should wear a coat.
In some cases, the rules provide more definite actions such as “move left” or “close door,” in
which case the rules are being used to represent directives.
Rules can also be used to represent relations such as:
IF temperature is below 0
o User Interface
o Inference Engine
o Knowledge Base
1. User Interface
With the help of a user interface, the expert system
interacts with the user, takes queries as an input in
a readable format, and passes it to the inference
engine. After getting the response from the
inference engine, it displays the output to the user.
In other words, it is an interface that helps a
non-expert user to communicate with the
expert system to find a solution.
3. Knowledge Base
o The knowledgebase is a type of storage that
stores knowledge acquired from the different
experts of the particular domain. It is
considered as big storage of knowledge. The
more the knowledge base, the more precise
will be the Expert System.
o It is similar to a database that contains
information and rules of a particular domain or
subject.
o One can also view the knowledge base as
collections of objects and their attributes. Such
as a Lion is an object and its attributes are it is
a mammal, it is not a domestic animal, etc.
Knowledge engineering
KNOWLEDGE ACQUISITION
The role of knowledge engineer is also very important with respect to develop
the refinements of knowledge. Knowledge engineers may be the professionals
who elicit knowledge from experts. They integrate knowledge from various
sources like creates and edits code, operates the various interactive tools, build
the knowledge base etc.
Figure Knowledge Engineer’s Roles in Interactive Knowledge Acquisition
c) Hierarchy-Generation Techniques
f) Sorting Techniques
In diagram based techniques the generation and use of concept maps, event
diagrams and process maps. This technique captures the features like “why, whe
n, who, how and where”. The matrix based techniques involve the construction
of grids indicating such things as problems encountered against possible
solutions. Hierarchical techniques are used to build hierarchical structures like
trees. Protocol analysis technique is used to identify the type of knowledge like
goals, decisions, relationships etc. The protocol generation techniques include
various types of interviews like structured, semi-structured and unstructured.
The most common knowledge acquisition technique is face-to-face interview.
Interview is a very important technique which must be planned carefully. The
results of an interview must be verified and validated. Some common variations
of an unstructured interview are talk through, teach through and read through.
The knowledge engineer slowly learns about the problem. Then can build a
representation of the knowledge. In unstructured interviews, seldom provides
complete or well-organized descriptions of cognitive processes because the
domains are generally complex. The experts usually find it very difficult to
express some more important knowledge. Data acquired are often unrelated,
exists at varying levels of complexity, and are difficult for the knowledge
engineer to review, interpret and integrate. But on the other hand structured
interviews are systematic goal oriented process. It forces an organized
communication between the knowledge engineer and the expert. In structured
interview, inter personal communication and analytical skills are important.