Verification and correctness issues for nonmonotonic knowledge bases
β Scribed by Grigoris Antoniou
- Publisher
- John Wiley and Sons
- Year
- 1997
- Tongue
- English
- Weight
- 147 KB
- Volume
- 12
- Category
- Article
- ISSN
- 0884-8173
No coin nor oath required. For personal study only.
β¦ Synopsis
Anomalies such as redundant, contradictory, or deficient knowledge in a knowledge base indicate possible errors. Various methods for detecting such anomalies have been introduced, analyzed, and applied in the past years, but they usually deal with rule-based systems. So far, little attention has been paid to the verification and validation of more complex representations, such as nonmonotonic knowledge bases, although there are good reasons to expect that these technologies will be increasingly used in practical applications. This article does a step towards the verification of knowledge bases which include defaults by providing a theoretical foundation of correctness concepts and a classification of possible anomalies. It also points out how existing verification methods may be applied to detect some anomalies in nonmonotonic knowledge bases, and discusses methods of avoiding potential inconsistencies (in the context of default reasoning inconsistency means nonexistence of extensions).
π SIMILAR VOLUMES
Validation has emerged as a significant problem in the development of knowledgebased systems (KBS). Verification of KBS correctness and completeness has been cited as one of the most difficult aspects of validation. A number of software tools have been developed to perform such verification, but non
In recent Web development trends, the discovery of data is in charge of automated agents, sophisticated search engines, and interoperability services. The era of Web Semantic allows machines the sharing and exploitation of knowledge, in a scalable and extensible way, where information is given a wel
A key obstacle hampering the fielding of AI planning applications is the considerable expense of developing, verifying, updating and maintaining the planning knowledge base (KB). Planning systems must be able to compare favorably in terms of software lifecycle costs to other means of automation such