Uses of Interface
org.tweetyproject.commons.postulates.Postulate
Packages that use Postulate
Package
Description
-
Uses of Postulate in org.tweetyproject.arg.dung.principles
Classes in org.tweetyproject.arg.dung.principles that implement PostulateModifier and TypeClassDescriptionclass
Admissibility Principle A semantics satisfies admissibility if for all extensions E it holds that: every argument in E is defended by E see Baroni, P., and Giacomin, M.class
CF-Reinstatement Principle A semantics satisfies cf-reinstatement if for all extensions E it holds that: for all arguments a, if E u {a} is conflict-free and E defends a, then a is in E see: Baroni, P., and Giacomin, M.class
Conflict-free Principle A semantics satisfies conflict-freeness if for all extensions E it holds that: E is conflict-free trivial property satisfied by practically all semantics see: Baroni, P., and Giacomin, M.class
Directionality Principle A semantics satisfies directionality if for every unattacked set U in a dung theory F it holds that: The extensions of F restricted to U are equal to the extensions of F intersected with U see: Baroni, P., and Giacomin, M.class
I-Maximality Principle A semantics satisfies I-Maximality iff for all pairs of extensions E1, E2 it holds that: if E1 is a subset of E2, then E1 = E2 see: Baroni, P., and Giacomin, M.class
Irrelevance of Necessarily Rejected Arguments (INRA) Principle A semantics s satisfies INRA if for every AF F it holds that: for every argument a in F, if every s-extension attacks a, then s(F) = s(F\{a}) i.e if an argument is attacked by every extension, then it does not influence the computation of extensions and can be ignored see: Cramer, M., and van der Torre, L.class
Modularization Principle A semantics s satisfies modularization iff for every AF F we have: if E1 is a s-extension of F and E2 is a s-extension of the E1-reduct of F, then (E1 u E2) is a s-extension of F see: Baumann et.class
Naivety Principle A semantics satisfies naivety if for all extensions E it holds that: E is conflict-free and maximal w.r.t set inclusion see: TODOclass
Models a principle for argumentation semantics i.e.class
Reduct-Admissibility Principle A semantics satisfies reduct admissibility iff for every AF F and every extension E we have: For all arguments a in E: if an argument b attacks a, then b is in no extension of the E-reduct of F see: Dauphin, Jeremie, Tjitze Rienstra, and Leendert Van Der Torre.class
Reinstatement Principle A semantics satisfies reinstatement if for all extensions E it holds that: for all arguments a, if E defends a, then a is in E i.e E is a complete extension see: Baroni, P., and Giacomin, M.class
SCC Decomposability Principle also: SCC-Recursiveness A semantics satisfies SCC decomposability iff for all AFs we have: The extensions of F are the same as computing the extensions of each SCC individually and combining the result see: Pietro Baroni et al.class
Strong Complete Completeness Outside Odd Cycles Principle (SCOOC) A semantics satisfied SCOOC if for every extension E it holds that: for every argument a, if neither a nor its attackers are in an odd cycle and E does not attack a, then a is in E.class
Semi-Qualified Admissibility Principle A semantics s satisfies semi-qualified admissibility iff for every AF F and every s-extension E we have: For all arguments a in E: if an argument b attacks a and b is in any s-extension, then E attacks b see: Dauphin, Jeremie, Tjitze Rienstra, and Leendert Van Der Torre.class
Principle of Strong Admissibility A semantics satisfies strong admissibility iff for every extensions E in every AF it holds that: all arguments in E are strongly defended by E, i.e.class
Weak Reinstatement Principle A semantics satisfies weak reinstatement if for all extensions E it holds that: if E strongly defends an argument a, then a is in E An argument a is strongly defended by E iff some argument in E \ {a} defends a see: Baroni, P., and Giacomin, M. -
Uses of Postulate in org.tweetyproject.arg.rankings.postulates
Classes in org.tweetyproject.arg.rankings.postulates that implement PostulateModifier and TypeClassDescriptionclass
The "abstraction" postulate for ranking semantics as proposed in [Amgoud, Ben-Naim.class
The "addition of attack branch" postulate for ranking semantics as formalized in [Bonzon, Delobelle, Konieczny, Maudet.class
The "addition of defense branch" postulate for ranking semantics as formalized in [Bonzon, Delobelle, Konieczny, Maudet.class
The "attack vs full defense" postulate for ranking semantics as proposed in [Bonzon, Delobelle, Konieczny, Maudet.class
The "cardinality precedence" postulate for ranking semantics as proposed in [Amgoud, Ben-Naim.class
The "counter-transitivity" postulate for ranking semantics as proposed in [Amgoud, Ben-Naim.class
The "defense precedence" postulate for ranking semantics as proposed in [Amgoud, Ben-Naim.class
The "distributed-defense precedence" postulate for ranking semantics as proposed in [Amgoud, Ben-Naim.class
The "increase of attack branch" postulate for ranking semantics as formalized in [Bonzon, Delobelle, Konieczny, Maudet.class
The "increase of defense branch" postulate for ranking semantics as formalized in [Bonzon, Delobelle, Konieczny, Maudet.class
The "independence" postulate for ranking semantics as proposed in [Amgoud, Ben-Naim.class
An abstract postulate for ranking-based semantics in abstract argumentation; the ancestor of all concrete postulates.class
The "non-attacked equivalence" postulate for ranking semantics as proposed in [Bonzon, Delobelle, Konieczny, Maudet.class
The "quality precedence" postulate for ranking semantics as proposed in [Amgoud, Ben-Naim.class
The "self-contradiction" postulate for ranking semantics as proposed in [Matt, Toni.class
The "strict addition of defense branch" postulate for ranking semantics as formalized in [Bonzon, Delobelle, Konieczny, Maudet.class
The "strict counter-transitivity" postulate for ranking semantics as proposed by [Amgoud, Ben-Naim.class
The "total" postulate for ranking semantics as proposed in [Bonzon, Delobelle, Konieczny, Maudet.class
The "void precedence" postulate for ranking semantics as proposed by [Amgoud, Ben-Naim. -
Uses of Postulate in org.tweetyproject.commons.postulates
Methods in org.tweetyproject.commons.postulates with parameters of type PostulateModifier and TypeMethodDescriptionvoid
PostulateEvaluationReport.addNegativeInstance
(Postulate<S> postulate, Collection<S> instance) Adds a negative instance for the given postulatevoid
PostulateEvaluationReport.addNotApplicableInstance
(Postulate<S> postulate, Collection<S> instance) Adds an instance that is not applicable for the given postulatevoid
PostulateEvaluationReport.addPositiveInstance
(Postulate<S> postulate, Collection<S> instance) Adds a positive instance for the given postulate (that is applicable)void
PostulateEvaluator.addPostulate
(Postulate<T> p) Adds the given postulatePostulateEvaluationReport.getNegativeInstances
(Postulate<S> postulate) Returns the negative instances for the given postulateboolean
PostulateEvaluator.removePostulate
(Postulate<T> p) Removes the given postulateMethod parameters in org.tweetyproject.commons.postulates with type arguments of type PostulateModifier and TypeMethodDescriptionvoid
PostulateEvaluator.addAllPostulates
(Collection<? extends Postulate<T>> postulates) Adds all postulates in the given collection.void
PostulateEvaluator.removeAllPostulates
(Collection<? extends Postulate<T>> postulates) Removes all postulates in the given collection.Constructor parameters in org.tweetyproject.commons.postulates with type arguments of type PostulateModifierConstructorDescriptionPostulateEvaluationReport
(PostulateEvaluatable<S> ev, List<Postulate<S>> postulates) Creates a new evaluation report for the given approach and set of postulatesPostulateEvaluator
(BeliefSetIterator<T, U> iterator, PostulateEvaluatable<T> ev, Collection<Postulate<T>> postulates) Creates a new evaluator for the given evaluatable and belief base generator. -
Uses of Postulate in org.tweetyproject.logics.pl.postulates
Classes in org.tweetyproject.logics.pl.postulates that implement PostulateModifier and TypeClassDescriptionclass
The "adjunction invariance" postulate for inconsistency measures: The set notation of knowledge bases should be equivalent to the conjunction of its formulas in terms of inconsistency values.class
The "attenuation" postulate for inconsistency measures: Minimal inconsistent sets of smaller size should have a larger inconsistency value.class
The "consistency" postulate for inconsistency measures: Consistent knowledge bases receive the minimal inconsistency value (0) and all inconsistent knowledge bases have strictly positive inconsistency values.class
The "contradiction" postulate for inconsistency measures: A knowledge base is maximally inconsistent if all non-empty subsets are inconsistent.class
The "dominance" postulate for inconsistency measures: Substituting a consistent formula by a weaker formula should not increase the inconsistency value.class
The "equal conflict" postulate for inconsistency measures: Minimal inconsistent subsets of the same size should have the same inconsistency value.class
The "exchange" postulate for inconsistency measures: Exchanging consistent parts of a knowledge base with equivalent ones should not change the inconsistency value.class
The "free-formula dilution" postulate for inconsistency measures: Removing a formula not participating in any minimal inconsistent set does not make the inconsistency value larger.class
The "free-formula independence" postulate for inconsistency measures: Removing a formula not participating in any minimal inconsistent set (= a free formula) does not change the inconsistency value.class
The "irrelevance of syntax" postulate for inconsistency measures: Knowledge bases with pairwise equivalent formulas should receive the same inconsistency value.class
The "MI-normalization" postulate for inconsistency measures: The inconsistency value of any minimal inconsistent subset is 1.class
The "MI-separability" postulate for inconsistency measures: The sum of inconsistency values of two knowledge bases with non-interfering sets of minimal inconsistent subsets should be the same as the inconsistency value of their union.class
The "monotony" postulate for inconsistency measures: Adding information to a belief base cannot decrease the inconsistency value.class
The "normalization" postulate for inconsistency measures: The inconsistency value is always in the unit interval [0,1], making it possible to compare inconsistency values for knowledge bases of different sizes.class
The "penalty" postulate for inconsistency measures: Adding a formula that participates in an inconsistency (i.e.class
An abstract postulate for inconsistency measures in propositional logic; the ancestor of all concrete postulates.class
The "safe-formula independence" postulate for inconsistency measures: Removing a safe formula (i.e.class
The "super-additivity" postulate for inconsistency measures: The sum of the inconsistency values of two disjoint knowledge bases is not larger than the inconsistency value of the joint knowledge base.class
A weaker variant of the "dominance" postulate using prime implicates, proposed in [Jabbour et al.