Refinement
Matthias van der Hallen
Recap: Knowledge Base Paradigm
- Represent the knowledge in a domain in a Knowledge Base
 - Use multiple inferences to solve different problems concerning that knowledge
 - + Procedural interface
 
Drawbacks of the Knowledge Base Paradigm:
- 
	
Loosely connected components of Domain Knowledge
 - Knowledge exists on different abstraction levels:
	
- Leads to complicated specifications
 - Potentially harder for the solver
 
 
Example: the AREI
(Algemeen Reglement op Elektrische Installaties)
Thesis making an application helping electricians or homeowners to configure law-abiding installations
Example: the AREI
(Algemeen Reglement op Elektrische Installaties)
Knowledge of AREI comes in separate, loosely linked parts:
- Routing of circuit through rooms
 - Circuit breaker mechanisms per circuit
 - Number of allowed devices per type / circuit
 - Cable thickness, length and power usage
 
(Roughly related to the different AREI chapters)
Example: the AREI
(Algemeen Reglement op Elektrische Installaties)
Knowledge of AREI comes in separate, loosely linked parts:
- Routing of circuit through rooms
 - Circuit breaker mechanisms per circuit
 - Number of allowed devices per type / circuit
 - Cable thickness, power usage
 
(Roughly related to the different AREI chapters)
Example: the AREI
(Algemeen Reglement op Elektrische Installaties)
| Passed rooms | Other circuits | Installed devices | |
|---|---|---|---|
| Circuit Routing | yes | yes | no* | 
| Power Analysis | no | no | yes | 
Idea: Refinement
Create a hierarchy of interlinked (smaller) knowledge kernels within a knowledge base
Refinement
By Matthias van der Hallen
Refinement
- 1,139