Checking termination of bottom-up evaluation of logic programs with function symbols*. Issue 6 (November 2015)

• Record Type: Journal Article
• Authors: CALAUTTI, MARCO; GRECO, SERGIO; SPEZZANO, FRANCESCA; TRUBITSYNA, IRINA
• Is Part Of: Theory and practice of logic programming. Volume 15:Issue 6(2015)
• Page Start: 854
• Page End: 889
• Publication Date: 2015-11
• Subjects: Logic programming -- Periodicals; Artificial intelligence -- Computer programs -- Periodicals; Constraint programming (Computer science) -- Periodicals; 005.115
• DOI: 10.1017/S1471068414000623
• Languages: English
• ISSNs: 1471-0684

Abstract

<abstract abstract-type="normal"> <title>Abstract</title> <p>Recently, there has been an increasing interest in the bottom-up evaluation of the semantics of logic programs with complex terms. The presence of function symbols in the program may render the ground instantiation infinite, and finiteness of models and termination of the evaluation procedure, in the general case, are not guaranteed anymore. Since the program termination problem is undecidable in the general case, several decidable criteria (called program termination criteria) have been recently proposed. However, current conditions are not able to identify even simple programs, whose bottom-up execution always terminates. The paper introduces new decidable criteria for checking termination of logic programs with function symbols under bottom-up evaluation, by deeply analyzing the program structure. First, we analyze the propagation of complex terms among arguments by means of the extended version of the argument graph called <italic>propagation graph</italic>. The resulting criterion, called <italic>acyclicity</italic>, generalizes most of the decidable criteria proposed so far. Next, we study how rules may activate each other and define a more powerful criterion, called <italic>safety</italic>. This criterion uses the so-called <italic>safety function</italic> able to analyze how rules may activate each other and how the presence of some arguments in a rule limits its activation. We also study the application of the proposed criteria to bound queries and show that the safety criterion is well-suited to identify relevant classes of programs and bound queries. Finally, we propose a hierarchy of classes of terminating programs, called <italic>k-safety</italic>, where the <italic>k</italic>-safe class strictly includes the (<italic>k</italic>-1)-safe class.</p> </abstract>