Graph

Building the argumentation graph: its arguments and attacks, and where they are kept.

ModulePredicatesDescription
ruleGraph4The whole argumentation graph of the rules of a theory (module ruleGraph, the graphBuilder of the profiles but abstract, see it.unibo.tuprolog.argumentation.core.runtime.settings.Profiles): every argument its rules make (see the module argumentBuilder), those derived from them (conflictArguments), and the attacks between them (attackBuilder), saved in the context (see the module graphStore)
abstractGraph5The argumentation graph of an abstract theory (module abstractGraph, the graphBuilder of the profile abstract): the arguments it states, a. or arg(a), and the attacks between them, a -> b. or att(a, b), and a <-> b. for a mutual attack, facts or derived by Prolog clauses (X -> Y :- beats(X, Y).); an argument attacking or attacked is an argument as well
argumentBuilder1The arguments of a theory (module argumentBuilder): every argument its premises and rules make, built round after round from the conclusions of the previous one, and saved in the context with their supports (see the module graphStore)
attackBuilder1The attacks between the arguments of the graph (module attackBuilder): each argument against those that may attack it (see the module attackCandidates), as the module attackRelation states them, saved in the context (see the module graphStore, which reads them extended to the arguments built on the attacked one)
attackRelation7When an argument attacks another one directly (module attackRelation): rebutting or undermining it through a conflict between their conclusions, rebutting or undermining it through a contrary premise, or undercutting its top rule
attackCandidates6The statements whose arguments may attack an argument, or be attacked by it (module attackCandidates): the graph builders only check the attacks (see the module attackRelation) between an argument and the arguments for these statements, and query mode explores them
graphStore49The argumentation graph kept in the active context, and its labels (module graphStore): the only module reading and writing them in the context; the terms are those of the data modules (argument, support, attack, label, statement)