Abstract

This paper constitutes the second part of a paper published in the i>Journal of Automated Reasoning 18 (1997), 357–398. The minimal entailment vi>M i n has been characterized elsewhere by i>P vi>M i n p iff i>C n(i>P ∪{p}) ∩ i>G P o s ⊆ i>C n(i>P), where i>C n is the first-order consequence operation, i>P is a set of clauses (disjunctive logic program; in short: a program), p is a clause (a query), and i>G P o s is the set of positive (that is, bodiless) ground clauses. In this part, we address the problem of computational feasibility of certain iterative applications of criterion (1). In the first part of the paper we proposed a query evaluation algorithm that decided i>P vi>M i n p by what we called indefinite modeling. The query evaluation algorithm was capable of deciding the right-hand side of (1) without actually computing all ground positive consequences of i>P or i>P ∪{p}. The objective of the second part of the paper is to extend the proposed approach so that it properly captures phenomena associated with allowing negation in clauses" bodies, however, at a price of substantial complication (in particular, computing all ground positive consequences of i>P ∪{p} that are not consequences of i>P can no longer be avoided). For that purpose, we introduce the concepts of a layered program and its hierarchically minimal semantics, a special case of which covers stratified programs with semantics defined by second-order prioritized circumscription and, in the case of definite programs, perfect models. We characterize the hierarchically minimal entailment vi>H M i n in terms of iterative application of the right-hand side of criterion (1). Finally, we generalize the indefinite modeling and query evaluation algorithms presented in Part I over the layered programs, and indicate their computational advantages relative to other methods (e.g., those based on prefect model semantics). The presented approach does not require assigning different meanings to logically equivalent clauses, so it actually eliminates the need for program clauses with negation in their bodies.

Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call