We consider the system map. Alphabet: cons : [a * list] --> list map : [list * a -> a] --> list nil : [] --> list Rules: map(nil, f) => nil map(cons(x, y), f) => cons(f x, map(y, f)) This AFS is converted to an AFSM simply by replacing all free variables by meta-variables (with arity 0). We use the dependency pair framework as described in [Kop12, Ch. 6/7], with static dependency pairs (see [KusIsoSakBla09] and the adaptation for AFSMs and accessible arguments in [Kop13]). We thus obtain the following dependency pair problem (P_0, R_0, static, formative): Dependency Pairs P_0: 0] map#(cons(X, Y), F) =#> map#(Y, F) Rules R_0: map(nil, F) => nil map(cons(X, Y), F) => cons(F X, map(Y, F)) Thus, the original system is terminating if (P_0, R_0, static, formative) is finite. We consider the dependency pair problem (P_0, R_0, static, formative). The formative rules of (P_0, R_0) are R_1 ::= map(cons(X, Y), F) => cons(F X, map(Y, F)) By [Kop12, Thm. 7.17], we may replace the dependency pair problem (P_0, R_0, static, formative) by (P_0, R_1, static, formative). Thus, the original system is terminating if (P_0, R_1, static, formative) is finite. We consider the dependency pair problem (P_0, R_1, static, formative). We will use the reduction pair processor [Kop12, Thm. 7.16]. It suffices to find a standard reduction pair [Kop12, Def. 6.69]. Thus, we must orient: map#(cons(X, Y), F) >? map#(Y, F) map(cons(X, Y), F) >= cons(F X, map(Y, F)) We orient these requirements with a polynomial interpretation in the natural numbers. The following interpretation satisfies the requirements: cons = \y0y1.2 + y0 + y1 map = \y0G1.2y0 + 2y0G1(y0) + 3G1(y0) map# = \y0G1.y0 Using this interpretation, the requirements translate to: [[map#(cons(_x0, _x1), _F2)]] = 2 + x0 + x1 > x1 = [[map#(_x1, _F2)]] [[map(cons(_x0, _x1), _F2)]] = 4 + 2x0 + 2x1 + 2x0F2(2 + x0 + x1) + 2x1F2(2 + x0 + x1) + 7F2(2 + x0 + x1) >= 2 + 2x1 + F2(x0) + 2x1F2(x1) + 3F2(x1) = [[cons(_F2 _x0, map(_x1, _F2))]] By the observations in [Kop12, Sec. 6.6], this reduction pair suffices; we may thus replace a dependency pair problem (P_0, R_1) by ({}, R_1). By the empty set processor [Kop12, Thm. 7.15] this problem may be immediately removed. As all dependency pair problems were succesfully simplified with sound (and complete) processors until nothing remained, we conclude termination. +++ Citations +++ [Kop12] C. Kop. Higher Order Termination. PhD Thesis, 2012. [Kop13] C. Kop. Static Dependency Pairs with Accessibility. Unpublished manuscript, http://cl-informatik.uibk.ac.at/users/kop/static.pdf, 2013. [KusIsoSakBla09] K. Kusakari, Y. Isogai, M. Sakai, and F. Blanqui. Static Dependency Pair Method Based On Strong Computability for Higher-Order Rewrite Systems. In volume 92(10) of IEICE Transactions on Information and Systems. 2007--2015, 2009.