Data on Arg2p Wiki

argument

Mon, 01 Jan 0001 00:00:00 +0000

argument

Data · Kotlin object ArgumentModule · library prolog.argumentation.data.argument

The term of an argument (module argument), read and built through it rather than by the positions of its parts.

An argument is the list [Rules, TopRule, Conclusion, Body, Info]:

Rules: the identifiers of the rules and premises it is made of;
TopRule: the identifier of its last rule, none for an argument made of a premise alone;
Conclusion: the statement it concludes, [Claim];
Body: the premises of its top rule;
Info: [LastDefeasibleRules, DefeasibleRules, DefeasiblePremises], what the preferences between arguments weigh.

Each accessor is a fact relating an argument to one of its parts, so it works both ways: given an argument it reads the part, given a part it builds the template of the arguments with it, to look them up in the context (argument::claim(A, sup(X, Y)), context_check(argument(A))). Kotlin reads and builds the terms through ArgumentTerm.parts and ArgumentTerm.info, written after the same layout.

attack

Mon, 01 Jan 0001 00:00:00 +0000

attack

Data · Kotlin object AttackModule · library prolog.argumentation.data.attack

The term of an attack (module attack): attack(Type, Attacker, Attacked, On), Attacker attacking Attacked on its sub-argument On (Attacked itself for a direct attack), with an attack of Type (rebut, undermine, undercut, …). Kotlin reads and builds it through AttackTerm.parts and AttackTerm.of.

Called by: graphStore

Predicate	Description
`new/5`	Attack is made of its parts
`type/2`
`attacker/2`
`attacked/2`
`on/2`	On is the sub-argument of the attacked argument the attack is on

new/5

new(?Type, ?Attacker, ?Attacked, ?On, ?Attack)

Attack is made of its parts.

support

Mon, 01 Jan 0001 00:00:00 +0000

support

Data · Kotlin object SupportModule · library prolog.argumentation.data.support

The term of a support (module support): support(Supporter, Supported), Supporter being a sub-argument of Supported. Kotlin reads and builds it through SupportTerm.parts and SupportTerm.of.

Called by: graphStore

Predicate	Description
`new/3`	Support is made of its parts
`supporter/2`
`supported/2`

new/3

new(?Supporter, ?Supported, ?Support)

Support is made of its parts.

label

Mon, 01 Jan 0001 00:00:00 +0000

label

Data · Kotlin object LabelModule · library prolog.argumentation.data.label

The terms of the labels (module label): an argument labelled IN, OUT or UND is in(Argument), out(Argument) or und(Argument), by its identifier inId(Id), outId(Id) or undId(Id) (the native labellings), and a statement statIn(Statement), statOut(Statement) or statUnd(Statement). A label is in, out or und. Kotlin builds them through LabelTerm.argument, LabelTerm.identifier and LabelTerm.statement.

statementTerm

Mon, 01 Jan 0001 00:00:00 +0000

statementTerm

Data · Kotlin object StatementTermModule · library prolog.argumentation.data.statement

The term of a statement (module statementTerm, as statement is the statement labelling of that name): [Claim], the list of the term claimed, as the conclusions of the arguments and the statements labelled are written. Kotlin reads and builds it through StatementTerm.claim and StatementTerm.of.

Predicate	Description
`new/2`	Statement is the statement of Claim

new/2

new(?Claim, ?Statement)

Statement is the statement of Claim.

rule

Mon, 01 Jan 0001 00:00:00 +0000

rule

Data · Kotlin object RuleModule · library prolog.argumentation.data.rule

The terms of the rules and premises of a theory as the parser converts them (module rule): a clause rl(Conclusion) :- [Id, Premises, Conclusion] for a rule, Premises a conjunction, and rl(Conclusion) :- [Id, Conclusion] for a premise, kept in the context by their conclusion. Kotlin builds them through RuleTerm.rule and RuleTerm.premise.