Uses of Interface
org.tweetyproject.commons.postulates.Postulate
Packages that use Postulate
Package
Description
- 
Uses of Postulate in org.tweetyproject.arg.dung.principlesClasses in org.tweetyproject.arg.dung.principles that implement PostulateModifier and TypeClassDescriptionclassAdmissibility 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.classCF-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.classConflict-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.classDirectionality 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.classI-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.classIrrelevance 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.classModularization 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.classNaivety 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: TODOclassModels a principle for argumentation semantics i.e.classReduct-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.classReinstatement 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.classSCC 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.classStrong 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.classSemi-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.classPrinciple 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.classWeak 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.postulatesClasses in org.tweetyproject.arg.rankings.postulates that implement PostulateModifier and TypeClassDescriptionclassThe "abstraction" postulate for ranking semantics as proposed in [Amgoud, Ben-Naim.classThe "addition of attack branch" postulate for ranking semantics as formalized in [Bonzon, Delobelle, Konieczny, Maudet.classThe "addition of defense branch" postulate for ranking semantics as formalized in [Bonzon, Delobelle, Konieczny, Maudet.classThe "attack vs full defense" postulate for ranking semantics as proposed in [Bonzon, Delobelle, Konieczny, Maudet.classThe "cardinality precedence" postulate for ranking semantics as proposed in [Amgoud, Ben-Naim.classThe "counter-transitivity" postulate for ranking semantics as proposed in [Amgoud, Ben-Naim.classThe "defense precedence" postulate for ranking semantics as proposed in [Amgoud, Ben-Naim.classThe "distributed-defense precedence" postulate for ranking semantics as proposed in [Amgoud, Ben-Naim.classThe "increase of attack branch" postulate for ranking semantics as formalized in [Bonzon, Delobelle, Konieczny, Maudet.classThe "increase of defense branch" postulate for ranking semantics as formalized in [Bonzon, Delobelle, Konieczny, Maudet.classThe "independence" postulate for ranking semantics as proposed in [Amgoud, Ben-Naim.classAn abstract postulate for ranking-based semantics in abstract argumentation; the ancestor of all concrete postulates.classThe "non-attacked equivalence" postulate for ranking semantics as proposed in [Bonzon, Delobelle, Konieczny, Maudet.classThe "quality precedence" postulate for ranking semantics as proposed in [Amgoud, Ben-Naim.classThe "self-contradiction" postulate for ranking semantics as proposed in [Matt, Toni.classThe "strict addition of defense branch" postulate for ranking semantics as formalized in [Bonzon, Delobelle, Konieczny, Maudet.classThe "strict counter-transitivity" postulate for ranking semantics as proposed by [Amgoud, Ben-Naim.classThe "total" postulate for ranking semantics as proposed in [Bonzon, Delobelle, Konieczny, Maudet.classThe "void precedence" postulate for ranking semantics as proposed by [Amgoud, Ben-Naim.
- 
Uses of Postulate in org.tweetyproject.commons.postulatesMethods in org.tweetyproject.commons.postulates with parameters of type PostulateModifier and TypeMethodDescriptionvoidPostulateEvaluationReport.addNegativeInstance(Postulate<S> postulate, Collection<S> instance) Adds a negative instance for the given postulatevoidPostulateEvaluationReport.addNotApplicableInstance(Postulate<S> postulate, Collection<S> instance) Adds an instance that is not applicable for the given postulatevoidPostulateEvaluationReport.addPositiveInstance(Postulate<S> postulate, Collection<S> instance) Adds a positive instance for the given postulate (that is applicable)voidPostulateEvaluator.addPostulate(Postulate<T> p) Adds the given postulatePostulateEvaluationReport.getNegativeInstances(Postulate<S> postulate) Returns the negative instances for the given postulatebooleanPostulateEvaluator.removePostulate(Postulate<T> p) Removes the given postulateMethod parameters in org.tweetyproject.commons.postulates with type arguments of type PostulateModifier and TypeMethodDescriptionvoidPostulateEvaluator.addAllPostulates(Collection<? extends Postulate<T>> postulates) Adds all postulates in the given collection.voidPostulateEvaluator.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.postulatesClasses in org.tweetyproject.logics.pl.postulates that implement PostulateModifier and TypeClassDescriptionclassThe "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.classThe "attenuation" postulate for inconsistency measures: Minimal inconsistent sets of smaller size should have a larger inconsistency value.classThe "consistency" postulate for inconsistency measures: Consistent knowledge bases receive the minimal inconsistency value (0) and all inconsistent knowledge bases have strictly positive inconsistency values.classThe "contradiction" postulate for inconsistency measures: A knowledge base is maximally inconsistent if all non-empty subsets are inconsistent.classThe "dominance" postulate for inconsistency measures: Substituting a consistent formula by a weaker formula should not increase the inconsistency value.classThe "equal conflict" postulate for inconsistency measures: Minimal inconsistent subsets of the same size should have the same inconsistency value.classThe "exchange" postulate for inconsistency measures: Exchanging consistent parts of a knowledge base with equivalent ones should not change the inconsistency value.classThe "free-formula dilution" postulate for inconsistency measures: Removing a formula not participating in any minimal inconsistent set does not make the inconsistency value larger.classThe "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.classThe "irrelevance of syntax" postulate for inconsistency measures: Knowledge bases with pairwise equivalent formulas should receive the same inconsistency value.classThe "MI-normalization" postulate for inconsistency measures: The inconsistency value of any minimal inconsistent subset is 1.classThe "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.classThe "monotony" postulate for inconsistency measures: Adding information to a belief base cannot decrease the inconsistency value.classThe "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.classThe "penalty" postulate for inconsistency measures: Adding a formula that participates in an inconsistency (i.e.classAn abstract postulate for inconsistency measures in propositional logic; the ancestor of all concrete postulates.classThe "safe-formula independence" postulate for inconsistency measures: Removing a safe formula (i.e.classThe "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.classA weaker variant of the "dominance" postulate using prime implicates, proposed in [Jabbour et al.