Siksha Sarovar

Siksha Sarovar (sikshasarovar.com) is a free educational web application that helps students in India learn programming and prepare for academic and competitive exams. The platform offers structured coding courses (C, C++, Python, Java, HTML, CSS, PHP, Power BI, AI, Machine Learning, Data Science), complete university curriculum notes for BCA/MCA students with previous year question papers, Class 10 and Class 12 CBSE/HBSE school notes, and dedicated preparation material for SSC, UPSC, Banking, Railway and other government exams. Browsing the site is completely free and requires no account. Users may optionally sign in with Google solely to save their learning progress, quiz scores and personal preferences across devices.

Privacy Policy | Terms of Service | Contact Siksha Sarovar | About Siksha Sarovar

v4.0.9 · PWA
Siksha Sarovar logo
Siksha Sarovar
Your Learning Universe

Siksha Sarovar is a free e-learning platform for coding courses, BCA university notes and competitive exam preparation. Optional Google sign-in saves your learning progress across devices.

Initializing knowledge base…
Compiling modules 0%

Unit 2 — Issues in Knowledge Representation

Lesson 17 of 34 in the free Artificial Intelligence notes on Siksha Sarovar, written by Rohit Jangra.

Issues in Knowledge Representation

Choosing how to represent knowledge raises several recurring design questions, regardless of which approach (semantic net, frame, logic, etc.) is used.

The Key Issues

IssueQuestion
1. Important attributesAre there attributes so fundamental they apply to almost every object (e.g., IS-A, INSTANCE-OF), and should they be handled specially?
2. Relationships between attributesShould relationships among slots/attributes themselves (inverses, existence dependency, value constraints) be represented explicitly?
3. Granularity of representationAt what level of detail should knowledge be captured — too coarse loses needed distinctions, too fine explodes complexity?
4. Choosing the right representational unitShould knowledge be represented as individual objects, sets, or both?
5. Finding the right structures as neededHow does the system pick, from a large knowledge base, the specific structures relevant to the current situation?
6. Representing sets of objectsTwo reasons: (a) to derive properties of an object from its set membership (inheritance), and (b) to assert facts about the set as a whole (e.g., "all birds have feathers" vs "this bird has feathers")

Inheritable Knowledge and Its Trade-offs

Representing knowledge by class hierarchy (IS-A) allows automatic inheritance — a huge saving in storage and consistency — but raises problems:

ProblemExample
Exceptions"Birds fly" — but penguins and ostriches don't; the representation must support overriding defaults
Multiple inheritance conflictsIf an object inherits from two parents with contradictory attribute values, which wins?
Non-monotonicityNew information can retract a previously valid inference (unlike formal logic, where truths never become false)

Attribute vs Relation Choice

Some facts can be represented either as an attribute of one object or as a relation between two objects — the choice affects how easily the fact can be reasoned about and generalised.

RepresentationExample
AttributeCar.colour = "Red"
RelationHas-Colour(Car1, Red)

The relation form generalises better (it can be reasoned over: "find all red things"), while the attribute form is often simpler to store and access directly.

Practical Impact

These issues explain why no single KR approach dominates — a system may combine several (e.g., frames with attached production rules, or semantic networks layered on predicate logic) depending on which issues matter most for the domain at hand.

Exam tip: "Discuss the issues in knowledge representation" typically expects the six-point list above, with at least one concrete example per point.