Separating and Collapsing Electoral Control Types††thanks: Supported in part by NSF grants CCF-2006496 and DUE-2135431, and CIFellows grant CIF2020-UR-36.
Abstract
Electoral control refers to attacking elections by adding, deleting, or partitioning voters or candidates (?). It was recently discovered, for seven pairs of seemingly distinct standard electoral control types, that and are in practice identical: For each input and each election system , is a “yes” instance of both and under , or of neither (?). Surprisingly, this had previously gone undetected even as the field was score-carding how many standard control types various election systems were resistant to; various “different” cells on such score cards were, unknowingly, duplicate effort on the same issue. This naturally raises the worry that perhaps other pairs of control types are identical, and so work still is being needlessly duplicated.
We completely determine, for all standard control types, which pairs are, for elections whose votes are linear orderings of the candidates, always identical. In particular, we prove that no identical control pairs exist beyond the known seven. We also for three central election systems completely determine which control pairs are identical (“collapse”) with respect to those particular election systems, and we also explore containment and incomparability relationships between control pairs. For approval voting, which has a different “type” for its votes, ?’s (?) seven collapses still hold (since we observe that their argument applies to all election systems). However, we find 14 additional collapses that hold for approval voting but do not hold for some election systems whose votes are linear orderings of the candidates. We find one new collapse for veto elections and none for plurality. We prove that each of the three election systems mentioned have no collapses other than those inherited from ? (?) or added in the present paper. We establish many new containment relationships between separating control pairs, and for each separating pair of standard control types classify its separation in terms of either containment (always, and strict on some inputs) or incomparability.
Our work, for the general case and these three important election systems, clarifies the landscape of the 44 standard control types, for each pair collapsing or separating them, and also providing finer-grained information on the separations.
1 Introduction
Preference aggregation is a central focus of social choice theory, while a central focus of AI is the ways in which agents interact, often in tasks or decision-making settings. It thus is natural that ever since computational social choice theory emerged as a field, it has been prominent at AI venues. The rise of online decision-making and the increasing use of agents in our increasingly online world make computational social choice, and in particular its approach to the study of preference aggregation—including its focus on the study of the complexity of attacks on elections—ever more important. This paper explores, and for some central cases definitively determines, the extent of a type of co-incidence (namely, the equality of seemingly different notions) that affects one of the most important models—control attacks—in the richly studied and important area of the (non)resistance to attacks of preference aggregation by voting. This is important in computational social choice and to AI, since finding collapses of two control types for a given election system means the two cases are effectively identical as sets, and so saves researchers from doing the duplicate work of separately studying the control types as to any set-based property, such as complexity, etc.
Let us start with a brief parallel. Suppose Professor Fou specializes in complexity classification, and for each problem that comes through the door, Professor Fou tries to prove it complete for Fou’s pet list of classes: , , and . So on Monday, a problem from scheduling theory would come in the door and Fou might prove it complete for and would give arguments suggesting -completeness and -completeness are each unlikely. On Tuesday, a problem from computational social choice might come in the door and Fou might prove it complete for and , and would give evidence suggesting -completeness is wildly unlikely. And so on for many years.
Most CS academics would be horrified at the situation and would say: How can Fou not have stepped back and tried to see the big picture—and realized that and are exactly the same class, and thus that Fou was doing duplicate work!
This seems at first a comic situation, yet a more subtle cousin of it has been in play in the computational social choice world for many years.
Let us explain what we mean by that. Control and manipulation are the two families of attack types that were the focus of the seminal papers of Bartholdi, Tovey, and Trick (?, ?, ?) on computational social choice. The various control attacks model different attempts to affect the outcome of elections by changes to their structure, namely, via adding, deleting, or partitioning voters or candidates. The control attack types also vary as to whether the goal is to make the focus candidate a winner (perhaps tied; this is known as the nonunique-winner (NUW) or cowinner setting), or to be a winner who is not tied with anyone else (this is known as the unique-winner (UW) setting), or to not (again regarding one of those two variants regarding ties) win. Over time, there has been something of a race or contest in computational social choice to find election systems for which a very large number of control types have the property that it is -hard to determine on a given input whether that type of control can succeed (see the discussion in our Related Work section).
But what if two (compatible, i.e., having the same input type) control types were in fact the same? That is, what if for every election system (whose votes are linear orders over the candidates) and on every input, despite the control types seeming to model different actions, in fact either for both control types the answer is yes (i.e., for each of the two control types, there is a way to achieve the goal of making the focus candidate win (or lose)), or for both the answer is no (i.e., for each of the two control types, there is no way to achieve the goal of making the focused candidate win (or lose)). We will say that the types “collapse” in this case. Then the two types for all practical purposes are the same. In such a case, all research that separately studied the two types—for example to determine their computational complexity for some election system (over linear orders)—would be doing the same work twice. As our abstract mentioned, surprisingly, it has recently been observed by ? (?) that there are (at least) seven such collapsing pairs of control types. In fact, that paper shows that four control types pairwise collapse—yielding six collapsing pairs—and one other pair also collapses.
The natural question this raises is whether there are other undiscovered collapses—either ones that hold for all election systems or, failing that, ones that hold when our focus is limited to one of the most important election systems. The universe of control types we study is that of the 22 “standard” control types used by ? (?) and other papers (and these are exactly the same 22 control types that appear in the key table summarizing control research as found in the Handbook of Computational Social Choice, see ?), each studied in both the NUW and the UW winner model; so 44 control types in total. For this control-type universe, we completely resolve whether additional collapses exist, both as to whether any additional collapses beyond the seven hold in general—we show that the remaining hundreds of pairs all separate—and as to the major election systems plurality, veto, and approval, for two of which we do discover additional collapses (one additional collapsing pair for veto and 14 additional collapsing pairs for approval) and for all three of which we then separate all remaining pairs.
Why is this important? As pointed out above, collapses reveal that seemingly different control types are for all practical purposes the same ones in disguise, and so general collapses give a clearer picture of the world of control types, and can help us avoid duplicate work, as has indeed already occurred.111Such duplicate work has already occurred extensively. Each time a paper built polynomial-time algorithms for both elements of a collapsing pair of control types, or proved -completeness for both elements, the paper did needless work on one element of the pair, since the sets involved in such a pair are the same set and so perforce they are of identical complexity. As just a few of the many papers that would have been saved a bit or a lot of work by either the seven general collapses of ? (?) or the additional concrete-system collapses established in the present paper, we mention ? (?), ? (?), ? (?), and ? (?). Separations on the other hand assure us that the types differ, and so we are not in the above way doing duplicate work in studying separately the two control types. (Of course, even for differing control types there may be connections of various sorts between the two types, e.g., if both are NP-complete, they will many-one polynomial-time interreduce.)
Since (general-case) collapse is defined as universal over election systems, its negation (separation) is existential over election systems, and as this paper shows, specific systems may have additional collapses. Thus it is important for the field, as to its understanding of control types, to find the collapse/separation behavior for important election systems, and we completely resolve this for the three arguably most important ones: plurality, veto, and approval. We hope that future papers by others will study additional systems or, even better, will (as we do for some cases in Section 3.3) define sufficient conditions that in one fell swoop provide collapses that apply to groups of election systems.
Separations themselves can be refined, for two (compatible) control types, if on each input (except with no focus candidate specified in the input) we consider for each of the two control types the set of all candidates such that if is the focal candidate, the given control action can succeed. It might be the case that for the first control type on all inputs that set is a subset of that set for the second control type; or it could always be a superset; or neither of these cases could hold. Of course, if the first two cases hold simultaneously, that is the same as the two types collapsing. For all our control pairs that separate, we refine our separations into the three cases just described: “always , and on some instance ”; “always , and on some instance ”; and neither of the above (i.e., “incomparable”). We find, for various separating pairs, such containment relationships, and not all are UW and NUW variants of each other (though UW and NUW always have an obvious or relation; which one of those holds depends on whether the type is “constructive” ( holds) or “destructive” ( holds); we will refer back to this fact later as ).
We draw on a wide variety of approaches to establish our separations and collapses. Many of our separations are established by human-constructed example; since the number of pairs we separate is large, when we can we build examples that simultaneously yield many separations. Some of our separation constructions are obtained by computer-aided search. Some of our separation results on the “general-case” tables are obtained by inheritance from a specific-case table. As to our new collapses, some are achieved by direct arguments that exploit some feature of the setting, and most are proven via an axiomatic-sufficient-condition approach. Also, some of the collapse (equality) entries in our tables for specific election systems are inherited from the general-case tables. Some of our collapses draw on multiple approaches. For example, our proof of Theorem 3.14 is a direct proof based on aspects of the setting but also uses an axiomatic property (immunity).
Big picture, this paper completely resolves the extent to which control-type pairs collapse or fail to collapse, both in general (i.e., universally quantified over election systems) and with regard to plurality, veto, and approval elections.
2 Preliminaries
For sets and , denotes , i.e., “” denotes the set difference operator.
For consistency, some of the standard definitions that appear in this section are taken, at times verbatim, from ? (?).
An election comprises a finite set of candidates (each identified uniquely by a name222By allowing names we potentially allow the names to be nefariously exploited by election systems. However, that model as to the use of names in fact makes our collapses and containments stronger than if those results were in a model where (candidate-)neutrality is assumed/required (the same applies to all collapses from ? (?), as those results are in this same with-names model). Although use of names would make our separations weaker, we address that by having ensured that every separation we establish in this paper is achieved via a (candidate-)neutral election system. In contrast, the one separation proven in ? (?) uses a system that is not (candidate-)neutral, see the discussion in our Related Work section. ) and a finite collection of votes over . Except in one section of the paper (Section 3.3, where we will study a system using a different vote type, known as approval vectors), we throughout this paper take the “type” of a vote as being a linear ordering over (note: linear orderings—complete, transitive, antisymmetric binary relations—are inherently tie-free). A simple example of a 3-candidate, 4-voter election thus is and the votes being , , , and .333The treatment of as a multiset—which we use to match ?’s (?) models—in effect limits the election systems the model covers to so-called (voter-)anonymous election systems. In fact, all general-case collapses of ? (?) and all new general-case containments of our paper also hold (in the natural nonanonymous model) for all nonanonymous election systems, as one can easily see from those results’ proofs. Also, we mention that all three concrete election systems that we study in fact are anonymous.
As is standard in computational social choice, an election system maps an election (a pair ) to a (possibly nonstrict) subset of (the set of winners). As is often done in computational social choice papers, we do not forbid the case of having no winners; see ? (?, Footnote 3) for a discussion of why allowing that is natural. The specific election systems plurality, veto, and approval are widely known and studied; we will explicitly define each in the results section devoted to it.
The study of electoral control from a computational perspective was initiated by ? (?). Their notion, known as constructive control, focuses on making a particular candidate a winner by some “control” action. ? (?) define the natural variants of those where instead the goal is to prevent a particular candidate from winning. This is known as destructive control.
The control actions are: partition of voters, partition of candidates, run-off partition of candidates, deleting voters, deleting candidates, adding voters, and adding candidates (both limited and unlimited). For each partition-based control type, we have two subvariants to handle the outcome of the subelections: in the TE (ties eliminate) subvariant, a candidate proceeds to the final round exactly if that candidate is the unique winner of that subelection, and in the TP (ties promote) subvariant, every winner of a subelection (including nonunique winners) proceeds to the final round. ? (?) suggest that it is more natural to study the TE subvariant when dealing with the unique-winner model and the TP subvariant when dealing with the nonunique-winner model. In this paper, since our goal is to uncover all possible collapses and separations (within the standard control types and their variants), we consider both TE and TP subvariants, regardless of the winner model. Since the nonpartition types among the standard control types do not involve two-stage elections, for those we of course will not split them into TE and TP versions, since that would not make sense.
We take the following definition from ? (?) (which itself is taking parts from earlier papers) to help us define the (constructive) control problems (in the nonunique-winner model) succinctly.444Regarding the partition-based control types, in Definition 2.1 and elsewhere in the paper we sometimes will speak of elections whose candidate set is but whose votes, due to candidate partitioning and/or first-round candidate eliminations, are over a set . As is standard in the literature, in such cases we always take this to mean that the votes are each restricted to just the candidates in .
Definition 2.1 (see ?).
Let be an election system.
-
1.
In the constructive control by adding candidates problem for (denoted by ), we are given two disjoint sets of candidates and , a collection of votes over , a candidate , and a nonnegative integer . We ask if there is a set such that (i) and (ii) is a winner of election .
-
2.
In the constructive control by unlimited adding candidates problem for (denoted by ), we are given two disjoint sets of candidates and , a collection of votes over , and a candidate . We ask if there is a set such that is a winner of election .555In Definition 2.1, parts 1 and 3–5 each have among their inputs a parameter that limits the number of additions or deletions. Among those four parts, why does only part 1 have an “unlimited” variant (part 2 of the definition) included in the standard set of control types? The answer comes from the history of control. The seminal paper on control (?) defined addition/deletion of voters and deletion of candidates with a limiting parameter , but in a curious asymmetry—perhaps due to which version the authors had obtained results for—defined and studied adding candidates in the unlimited variant. Later papers (the first of them being ?) ended the omission by studying the version of adding candidates that had a limiting parameter . However, most papers—including the papers this paper is most closely related to—broadly investigating or “score-carding” properties of a “standard” set of control types have, in addition to studying that with-limiting-parameter- version of adding candidates, also retained and studied the unlimited version. They likely did that in part since the unlimited version had been introduced in the seminal paper on control, and in part to support comparisons with other papers that included the unlimited version.
-
3.
In the constructive control by deleting candidates problem for (denoted by ), we are given an election , a candidate , and a nonnegative integer . We ask if there is a set such that (i) , (ii) , and (iii) is a winner of election .
-
4.
In the constructive control by adding voters problem for (denoted by ), we are given a set of candidates , two collections of votes, and , over , a candidate , and a nonnegative integer . We ask if there is a collection such that (i) and (ii) is a winner of election .
-
5.
In the constructive control by deleting voters problem for (denoted by ), we are given an election , a candidate , and a nonnegative integer . We ask if there is a collection such that (i) and (ii) is a winner of election .
-
6.
In the constructive control by partition of voters problem for , in the TP or TE tie-handling rule model (denoted by or , respectively), we are given an election , and a candidate . We ask if there is a partition666A partition of a collection is a pair of collections and such that , where denotes multiset union. A partition of a set is a pair of sets and such that and , where and are standard set union and intersection. of into and such that is a winner of the two-stage election where the winners of subelection that survive the tie-handling rule compete (with respect to vote collection ) along with the winners of subelection that survive the tie-handling rule. Each election (in both stages) is conducted using election system .
-
7.
In the constructive control by run-off partition of candidates problem for , in the TP or TE tie-handling rule model (denoted by or , respectively), we are given an election , and a candidate . We ask if there is a partition of into and such that is a winner of the two-stage election where the winners of subelection that survive the tie-handling rule compete (with respect to vote collection ) against the winners of subelection that survive the tie-handling rule. Each election (in both stages) is conducted using election system .
-
8.
In the constructive control by partition of candidates problem for , in the TP or TE tie-handling rule model (denoted by or , respectively), we are given an election , and a candidate . We ask if there is a partition of into and such that is a winner of the two-stage election where the winners of subelection that survive the tie-handling rule compete (with respect to vote collection ) against all candidates in . Each election (in both stages) is conducted using election system .
There are 11 control “types” listed above (applied regarding generic election system ). For each, we can change “is a winner” to “is an untied (i.e., unique) winner”; for those 11 variants, we change the “-” into “-.” Thus we have 22 control types. Those 22 are all trying to make the focus candidate win. And so they are all spoken of as “constructive” control types (thus the “CC” in their naming strings). Finally, for each of those now 22 control types, we can ask whether one can ensure that the focus candidate is not a winner or not a unique winner; those are known as the “destructive” control variants, and in the names of those, the is replaced by a , e.g., -DC-AC-UW.
We thus have 44 total types of control, which we will view as the “standard” control types. We thus have pairs of control types. Fortunately, 624 of those pairs are incompatible—the two control types have different input fields from each other777So for example --- and --- are compatible, but --- and -- are not, since -- has a nonnegative integer field . Throughout this paper, whenever we speak of pairs of control types, we refer only to compatible pairs (even if that is not explicitly stated, although for emphasis we often do state it). and so comparing them would not even make sense—and so we will exclude them from our study. So we have “only” 322 pairs to focus on in our study. Table LABEL:table:compatibility shows the five compatibility equivalence classes that the 44 types partition into.
When speaking of control types we often will be speaking of the control model itself, and when doing so, we generally do not include the “” prefix. In some sense, we view, for example, as a control type (model)—one among the 44 standard such models—and we view as the set of input strings that are “yes” instances, for election system , under that model of control.
Keeping that in mind, we now define precisely what we mean by two (compatible) control types collapsing or separating, and then introduce a function approach that will allow us to explore in a more refined way the nature of the separations. Let (e.g., Plurality) be an election system and let and be two (compatible) control types from our 44 standard ones (e.g., CC-AC-NUW and CC-AC-UW). Then if we say that the control types and collapse (for election system ), and if we say that the control types and separate (for election system ). We will also use the terms collapse and separate for a more general case, namely, the one of quantifying universally over all election systems whose votes are linear orders. When speaking in that case, we will say that two (compatible) control types from among our 44 collapse if the two control types collapse for every election system whose vote type is linear orders, and otherwise we will say that the control types separate.
As an example, if we fix the election system to be plurality, we note that in the 3-candidate, 4-voter election example given at the beginning of this section is a unique winner. Yet, we could make a unique winner by deleting candidate , hence we have . Also, since a unique winner is a winner in the nonunique-winner model as well, we have . (In this paper we will not focus on encoding details, since they are not important to our study.)
Note that, in this paper, when we prove that two compatible control types separate we are unconditionally proving that they are not the same set. That contrasts with the weaker—namely, conditional—separation one might claim if one of the types was known to be NP-hard and the other was known to be a set (other than the empty set or ) in P, since arguing separation just from those facts would require one to have proven that . Also, one needs to be wary about casually arguing that certain (compatible) control types “inherently,” universally differ. For example, it might be tempting to say just based on intuition that CC-DV-UW and CC-DC-NUW inherently differ for all election systems. However, for the election system where all candidates always lose, these two do collapse, since both are the empty set. Also, the already-known universally collapsing control pairs found by ? (?) were long assumed to be obviously different, but that turned out to not be the case. (However, though in this paper we do not look at showing when pairs of compatible types will differ for every election system, we mention that in some cases one can indeed see that that holds. For example, for each election system , -CC-DV-NUW and -DC-DV-NUW differ since any given legal, syntactically well-formed input with one candidate and zero votes, that input will be in exactly one of the two sets.)
Compatible control types that separate—i.e., are different sets—can do so in different ways, some of which reflect containment relationships. In order to be able to seek such relationships, we define the three different ways that two (compatible) separating control types, and , for can separate. To support this refinement, we introduce a function model. In particular, we will define functions that, for a given control type, map from inputs (that differ from those used so far for that control type only in not having a focus candidate specified) to the set of all candidates such that if is made the focus candidate for that input, successful control is possible. In a bit more detail: Each of our control types has certain inputs, and all include a focus candidate, . Let us for any of our 44 control types, , refer to an input to it, except with the field containing the focus candidate removed, as the reduced form of that input. If we want for a reduced input to add back the name of a particular candidate to be the focus candidate, we will say that is inflating the reduced input by that candidate. For any of our 44 control types, , and any election system , we define the function to be the function that, for a given reduced input , outputs the set of all candidates such that inflated by belongs to the set . For example, given as input , the output of is the set of all candidates that can by deleting less than or equal to three votes be prevented from being a winner.
Clearly, two (compatible) control types collapse exactly if their thus-defined functions are equal. But for two separating (compatible) control types, there are three different ways they can be separated. One way is if, for each reduced input : (a) and (b) for some reduced input , . We will (in a slight abuse of notation) refer to the case where (a) holds as the “” case, and the case where both (a) and (b) hold as the “” case. The “” and “” cases are analogously defined. If the two (compatible) types separate but neither the “” case nor the “” case holds, we will say the two types are incomparable: each will sometimes have successful focus candidates that the other does not. If both directions of noncontainment can be witnessed by the same reduced input, we will say the two types are strongly incomparable, i.e., there is a reduced input such that and . Arguably, strong incomparability is a more satisfying strength of incomparability, since it makes clear that one does not have to cobble the two directions of the incomparability together from different supporting instances. These notions are relative to each specific election system, .
For the general case—where our collapses are universally quantified over all election systems whose vote type is linear orders—we define three increasingly strong types of incomparability. The weakest incomparability notion is simply that for at least one such election system , for some reduced input , holds, and for at least one such election system , for some reduced input , holds. We will call this being weakly incomparable.888We will state no weak incomparability results in this paper, since whenever we obtained a weak incomparability result we in fact were able to even establish incomparability, which we will define in a moment in the main text. Though in this paper we thus never need to prove weak incomparability results, we state the notion so that future research on other control types will have a three-level menu of incomparability strengths to draw on if needed. We will say the pair is incomparable if there is some election system, over linear orders, in which the pair is incomparable in the sense of the previous paragraph. And we will say the pair is strongly incomparable if there is some election system, over linear orders, in which the pair is strongly incomparable in the sense of the previous paragraph. For the general case, we will say “” (resp., “”) holds if for every election system whose vote type is linear orders, the “” (resp., “”) case for , as defined above, holds.
We now cover, and give brief reference labels to (though we at times may use these inheritances tacitly when the use is clear), some collapse, containment, and separation inheritances that hold. We will start these labels with the letter “I” as a mnemonic for that fact that these concepts are about inheritance. General-case collapse, , and results imply, for each election system over linear orders, resp., collapse, , and results (let us shorthand that fact as I1). If a given general case result of this type happens to in addition hold for every election system (not merely those over linear orders), we will refer to that as additionally being an I1+ case. Simply because their particular proofs do not ever draw on the vote types, the seven general-case collapses of ? (?), and also our general containment results of Theorem 3.1, hold even as I1+ cases. As to separation inheritances, if for some election system over linear orders and some reduced input we have that (as, crucially, is always the case if we have that for the relation holds between and ) and we in addition happen to have that in the general case the relation is known to hold between and , then we may conclude that holds in our general case; the analogous claim holds for the case, and we will refer to either of these, when they hold, as an I2 inheritance case. Incomparability in an election system (over linear orders) implies general-case incomparability (we will refer to this as I3), and strong incomparability in an election system (over linear orders) implies general-case strong incomparability (I3∗).
3 Results
In the following three subsections, for the general case and for the cases of plurality, veto, and approval voting, we completely determine which pairs of (compatible) standard control types collapse, and which separate. Beyond that, we refine every separation into one of the three disjoint cases: , , and incomparability.
We discover a number of previously unknown collapses (for two of the three specific systems) and also for many noncollapsing control-type pairs establish new containments in one direction. Regarding the former, for veto we discover a new collapsing pair and for approval we extend a four-type collapse by ? (?) to a six-type collapse, and we find five additional collapsing pairs, for a total of , i.e., , new collapsing control-type pairs for approval.
Overall, we establish that, for the cases we study (i.e., all compatible pairs for each of the four cases), no containments or collapses exist other than those provided by either ? (?) or this paper.
3.1 The General Case and Plurality
We show that the only (compatible) pairs that collapse in general (i.e., that collapse for every election system) are the seven found by ? (?), namely, for every election system , (six pairs) and (one pair). Surprisingly, we will be able to do so using just constructions about plurality elections, combined with uses of inheritance.
In a plurality election, for each vote where a particular candidate is ranked first, that candidate receives a point, and a winner is a candidate with the highest number of points among all the candidates (naturally, there can be multiple winners). The votes in plurality elections are linear orders. Recall that by the “general case,” we mean the general case with respect to elections where the votes are linear orders. Thus to separate two control types in the general case, it certainly suffices to show that they separate under plurality, as such separations inherit back to the general case via the I3 and I2 types of inheritance discussed in our preliminaries.999We note that for some cases we achieve strong incomparability in our general-case results, always via I3∗. In such cases, incomparability still holds, since strong incomparability is simply a specific subcase of incomparability. The reason we know that no separation for the general case is missed is that our results show that plurality has no , , or collapse results not also possessed by the general case; so our I2 cases are valid, and every general-case , , or incomparability (or even strong incomparability) that holds is yielded by our inheritances.
Let us now turn our attention to the two new general-case containments shown in this paper (these containments are in addition to the obvious ones, noted at location of Section 1, about two control types that only differ in their winner model) and also argue that both are strict in the general case (by which, recall, we mean that there is at least one election system under which the containment is not an equality). The following two containments apply to all vote types (not just linear orders; and we argue in Section 3.3 that the collapses by ? also apply to all vote types).
Theorem 3.1.
Let be an election system. For each , .
-
Proof.
Let . We will show . Suppose . Let be a partition that witnesses ’s membership in . It holds that either participates in and loses in a subelection, or participates in and does not win uniquely in the final round. If the former holds, then the partition suffices as will be eliminated in a subelection and thus will not proceed to the final round. If the latter holds, then let denote the set of candidates present during the final round. Clearly . Thus the partition witnesses ’s membership in since either loses in the first subelection or ties in that subelection and is eliminated by the tie-handling rule. ❑
For both containments above (i.e., for each of the two values of stated in the theorem), Table LABEL:table:plurality-results contains a pointer to a separation witness in Table LABEL:table:plurality-tools that shows that the containment is not an equality in the general case (i.e., that for some election system—in fact, plurality—the containment is strict). More generally, Table LABEL:table:plurality-results, for each compatible pair of control types and , gives us an election witnessing if that holds, and gives an election witnessing if that holds (and if both hold Table LABEL:table:plurality-results gives witnesses for each). Of course, we are not claiming that the containments in that theorem are strict under all election systems; for example, Corollary 3.11 and Theorem 3.12 show that all three types mentioned in the above theorem pairwise collapse under approval voting.
Some of the constructions in Table LABEL:table:plurality-tools are quite simple. For example, with and (denoted by “Plur.3”) we clearly get incomparability between all 144 pairs of partition types where one type is constructive and the other is destructive. (This holds since in that election, under every constructive or destructive partition-control action, is the unique winner and is not a winner.) However, showing separations for every pair that can be separated is no trivial matter. Some of our separation examples for plurality are quite large, with up to 18 votes and up to seven candidates. The search for those examples was computer-aided and extensive.
3.2 Veto
In a veto election, for each vote where a particular candidate is not ranked last, that candidate receives a point, and a winner is a candidate with the highest number of points among all the candidates (naturally, there can be multiple winners). For example, if and , then and each receive one point, and receives two points and wins.
We now establish every equality and containment that holds for veto elections but was not established by one of the results of ? (?). For all other veto cases, we have constructed counterexamples. Some of those counterexamples were obtained through computer search.
Theorem 3.2.
.
-
Proof.
The relationship is immediate. The approach that follows resembles closely that of ? (?). Let . If there is a partition such that is not a winner of the two-stage election, then . Otherwise, there is a partition and , , such that and are both winners of the two-stage election. Suppose . Then and are both winners of the election . In this case, consider the partition . Both candidates will tie and be eliminated, in both subelections. Suppose . Then there are two distinct candidates . Let denote the set of votes in which is vetoed and let be the remaining votes. Now, consider the two-stage election with partition . Since is never vetoed in , can at best tie with in the subelection . Finally, is never vetoed in (since all votes there veto ), so cannot be a unique winner of . Thus is eliminated in both first-round elections. ❑
Theorem 3.3.
For each , , .
-
Proof.
Let , . Suppose , and let be a partition that witnesses this membership. Using the same technique as in the proof of Theorem 3.2, we can handle the case where and thus we only need to consider the case where in this proof. Let . First, suppose that is present in the final round. Then, since is not a unique winner of the final round, all candidates in are present in this round. Thus is not a unique winner of the election , and so the partition witnesses ’s membership in . Now, suppose that is absent from the final round. Then is not a winner of or , and so receives strictly more vetoes than in both and . Thus receives more vetoes than in , so again, is not a unique winner of . A separation witness for the strict containment can be found in Table LABEL:table:veto-results. ❑
Theorem 3.4.
For each , , , , .
-
Proof.
Let , , , . Suppose , and let be a partition that witnesses this membership. As per the two preceding proofs (namely, of Theorems 3.2 and 3.3), we need only consider the case where . The case where is present in the final round is handled as in Theorem 3.3, so suppose that is absent from the final round. Without loss of generality, we may assume that . (This is certainly true when is about one of the theorem’s three RPC cases, due to the symmetric nature of that partitioning action. It also holds when is about the theorem’s one PC case, since being in would imply that is in the final round, which contradicts the case we are in.) Then is not a unique winner of , so . Thus is not a unique winner of , and the partition witnesses ’s membership in . A separation witness for the strict containment can be found in Table LABEL:table:veto-results. ❑
3.3 Approval Voting
Approval voting differs from the other election systems discussed so far in this paper as to its vote type. In an approval election , each vote is a bit-vector of length , with each bit being associated with a candidate. If a candidate’s bit is 1, then that candidate is approved by that vote. In approval voting, the winner set is composed of each candidate such that no other candidate is approved by strictly more votes than is. We will sometimes speak of the “score” of a candidate in the rest of this section. In the context of approval voting, the score of a candidate in an election is the number of votes that approve that candidate (and as noted above, the set of winners are those candidates with maximal score).
Although the collapses shown by ? (?) were stated for election systems where votes are linear orders, we note that in their proof they do not use the vote type and thus those collapses hold regardless of what type of votes the election system is over. Thus we have the following corollary.
Corollary 3.5 (see ?).
-
1.
.
-
2.
.
In this section, we prove a number of collapses and inclusions that hold for approval voting. Some of these results draw on previously established immunity101010In the unique-winner model, we say an election system is immune to a particular type of control if the given type of control can never change a candidate from not uniquely winning to uniquely winning (if the control type is constructive) or change a candidate from uniquely winning to not uniquely winning (if the control type is destructive) (?, which clarified a slightly flawed immunity definition of ?). In the nonunique-winner model, we say an election system is immune to a particular type of control if the given type of control can never change a nonwinner to a winner (if the control type is constructive) or change a winner to a nonwinner (if the control type is destructive). arguments that draw on properties satisfied by approval voting, thereby allowing us to generalize our results. Other results are provided by direct arguments. Our direct arguments often rely on the fact that, since the votes are bit-vectors, a candidate’s score in an election is independent of the other candidates present in the election. We will start by discussing the results that draw on the aforementioned immunity arguments.
Let us first consider what is known in the social choice literature as Property (?, see also ?).111111In a number of papers in the computational social choice literature, this property has been spoken of as if it were the Weak Axiom of Revealed Preference. It in fact is not, though they are related; this issue however did not make any of the earlier papers wrong, as they merely were unwisely but internally consistently using a notation in a way that did not match the way it was used elsewhere. This unfortunate terminological confusion came in due to some ambiguous wording in one of the seminal papers on computational social choice theory. In the present paper, we follow the lead of ? (?) and use the (more consistent with the social choice literature) terminology “Property ” and, for Property ’s “unique-winner” analogue, “Property Unique-.” See ? (?) for a more detailed discussion of this issue, including its history and relation to the Weak Axiom of Revealed Preference. Property is defined as the property that winning an election implies that remains a winner of every election for which . (Clearly, some election systems will satisfy this property and some will not.) The “unique” version of this property (which is called Property Unique-) only differs in that it requires to be a unique winner, i.e., it requires that uniquely winning in an election implies that uniquely wins in each election for which (?). ? (?) note that any election system that satisfies Property Unique- is immune to several types of control, namely to (i) destructive control by partition of candidates and run-off partition of candidates (under both and tie-handling rules) in the model, and (ii) destructive control by deleting candidates in the model. From this, we obtain the following results.121212The theorem certainly could also include in the equality. However, including that in the theorem would make little sense, since does not rely on Property Unique-, but in fact holds for all election systems in light of ? (?) and our comment in the paragraph before Corollary 3.5. Also, note that in our sequence of result statements from Theorem 3.6 through Corollary 3.10, each is (intentionally) stated as applying to all election systems satisfying the relevant Property or Unique-, regardless of what vote “type”—such as approval vectors or linear orders—the election system’s votes are over.
Theorem 3.6.
Let be an election system that satisfies Property Unique-. Then .
-
Proof.
Fix any that satisfies Property Unique-. Let and let . Consider the two sets and is a unique winner of election and and is not a unique winner of election . These sets form a partition of and is an election, so of course . Clearly we also have that and that . We will argue that . Since , like all systems satisfying Property Unique-, is immune to both control types in the theorem statement, we have (recall that both of these types are destructive types) that and , and thus it holds that and . Fix . Then the partition witnesses both and , since in both cases the final round will simply be and we know that since , will not be a unique winner of the final round. ❑
Theorem 3.7.
Let be an election system that satisfies Property Unique-. Then the following hold.
-
1.
.
-
2.
.
-
Proof.
Fix any that satisfies Property Unique-.
-
1.
The proof is analogous to that of Theorem 3.6. Since is immune to destructive control by deleting candidates in the unique-winner model (as per the discussion immediately before Theorem 3.6), the inclusion is immediate as is comprised of those inputs where the focus candidate is already not a unique winner.
-
2.
It trivially holds that . Thus the proof follows from the previous part of this theorem. ❑
-
1.
Theorem 3.8.
Let be an election system that satisfies Property . Then .
-
Proof.
Fix any that satisfies Property . The proof is analogous to that of Theorem 3.7. Given an election and , if is a winner of election , by Property it follows that no deletion of candidates (other than ) can prevent from being a winner. Thus is comprised of those inputs where the focus candidate is already not a winner. ❑
The next two results will use the notion of being strongly voiced. An election system is said to be strongly voiced exactly if for every election with , there is at least one winner of under (?). (Most earlier versions of this paper had different hypotheses in what here are Theorem 3.9 and Corollary 3.10 and flawed proofs of those; the current version corrects that.)
Theorem 3.9.
Let be a strongly voiced election system that satisfies Property . Then .
-
Proof.
Fix any that is strongly voiced and satisfies Property . Let and let . Consider the two sets and is a unique winner of election and and is not a unique winner of election . These sets form a partition of and is an election, so of course . Clearly we also have that and that . We will show that . First we show that and .
Consider an element and assume for the sake of contradiction that is not a unique winner of election , i.e., . Since and since is strongly voiced, there is a candidate that is a winner of under . By Property , that candidate is a winner of any subelection they participate in (regardless of how the candidates are partitioned), and since the tie-handling rule never eliminates candidates, will always proceed to the final round and be a winner (again by Property ). This contradicts the fact that , so . Since and since , it follows that . The same argument establishes that . We will now complete this proof by arguing that and .
Fix . Then the partition witnesses that as the final round will simply be and we know that since , will be a unique winner of the final round. Additionally, the partition also witnesses that as no one will proceed from subelection , and only will proceed from subelection (since ), and must be the unique winner of the final round (this follows from both strong voicedness and Property ). ❑
We can build on Theorem 3.9 to show additional containments.
Corollary 3.10.
Let be a strongly voiced election system that satisfies Property and Property Unique-. Then, for each , , , , , , , , it holds that (equivalently, ).
-
Proof.
Fix any that is strongly voiced and that satisfies Property and Property Unique-, fix a , , , , , , , , and fix . By the proof of Theorem 3.9, is comprised of only those inputs where is already a unique winner of the election , so the trivial partition (i.e., if is about partitioning candidates and if is about partitioning votes) is a witness that as will uniquely win at least one subelection in which it participates (if is about partitioning votes, then participates in two subelections) as one of those two subelections is . Moreover, uniquely wins the final round, which it participates in, because satisfies Property Unique-. The “equivalently” follows from Theorem 3.9. ❑
Since approval voting is clearly strongly voiced (?) and satisfies Property Unique- (?), and (clearly) Property , the above theorems and corollaries apply to approval voting. For each case where only the containment (and not the collapse) is shown, the containment can be made strict under approval voting. See Table LABEL:table:approval-results for the separation witnesses.
Corollary 3.11.
-
1.
.
-
2.
.
-
3.
.
-
4.
.
-
5.
.
-
6.
.
-
7.
For each , , , , , , , , it holds that
We can extend the five-type collapse in Part 1 of Corollary 3.11 to a six-type collapse.
Theorem 3.12.
.
-
Proof.
We will show that both sets coincide with the set and is not a unique winner of approval election .
It follows from the fact that approval is immune with respect to and (?) that and are both subsets of . Fix . Then the partition witnesses that as the final stage will be approval election . Similarly, the partition also witnesses that . This follows from the fact that is not a unique winner of the approval election and so there must exist a different candidate who is a winner of election and so whose score is at least as large as ’s score. No one will proceed from subelection and will proceed from subelection (along with those candidates, if any, who tie with ) and be a winner of the final round. Thus even if proceeds to the final round, it will not be a unique winner. ❑
Additionally, we prove the following immunity result about approval voting in the nonunique-winner model; the analogous result for the unique-winner model was obtained by ? (?).
Theorem 3.13.
Approval is immune to constructive control by partition of candidates and run-off partition of candidates under the tie-handling rule in the nonunique-winner model.
-
Proof.
We first show that a winner (possibly tied) of the two-stage approval election induced by partition of candidates under the tie-handling rule must be a winner without any control action (i.e., in the input’s election). Fix an election and let be a candidate such that . Thus it holds that ’s score is at least as high as the score of the other candidates present in the final round. Since no candidate is eliminated by the tie-handling rule, each candidate that is eliminated in the first round has score strictly less than some candidate that is present in the final round. It follows that ’s score is at least as high as the score of every other candidate in . Thus is a winner of the approval election .
Essentially the same argument line can be used to show that for each , it holds that is a winner of approval election . ❑
Theorem 3.14.
.
- Proof.
Consider the following two disjoint sets: and is a winner of approval election and and is not a winner of approval election . It’s clear that and . By Theorem 3.13, it holds that approval is immune to constructive control by partition of candidates and run-off partition of candidates under the tie-handling rule in the nonunique-winner model. Thus and , and it holds that and . Fix . Then the partition witnesses that both and as no candidate will have score higher than ’s score (because is a winner of approval election ), and since the tie-handling rule does not eliminate candidates, will always proceed from the subelection it participates in to the final round. Thus no candidate can defeat in the final round, making a winner of the two-stage election. ❑
Corollary 3.15.
For each , , , it holds that
-
Proof.
Fix , , and fix . By the proof of Theorem 3.14, we know that is comprised of only those inputs where is already a nonunique winner of the approval election . In the first case, where is about partitioning candidates, then the partition is a witness that as will uniquely win the subelection it participates in and proceed to the final round. Regardless of which candidates proceed to the final round from the other subelection, they will not have score greater than ’s (or they would have defeated in the election) and so is a winner of the two-stage election. In the second case, where is about partitioning votes (i.e., ), then the partition suffices as everyone proceeds to the final round (because all the candidates tie in the subelection and the tie-handling rule does not eliminate candidates) and since is already a winner of the approval election , they are a winner of the final round. The corresponding separation witness can be found in Table LABEL:table:approval-results. ❑
Finally, we provide direct arguments that yield additional collapses and containments.
Theorem 3.16.
.
-
Proof.
The relationship is immediate.
: Let . Note that this implies , since in one-candidate approval elections the one candidate always wins. Let be a vote partition that witnesses . As the tie-handling rule is the rule, it must hold (since if uniquely won both subelections it necessarily would uniquely win the second-round election) that either is eliminated in both subelections (either by tieing or by losing) or uniquely wins one subelection, some other candidate uniquely wins the other subelection, and does not uniquely win the final round (thus ’s score must be at least as large as ’s score when using vote set ). In the first case, the partition witnesses since will not proceed to the final round. In the second case, using the partition suffices for the following reasons. In the subelection , since ’s score is at least as large as that of , either uniquely wins the subelection or both and tie and are eliminated by the tie-handling rule. In the subelection every candidate ties and so all candidates are eliminated by the tie-handling rule (since ). Thus is eliminated in both subelections, does not proceed to the final round, and so is not a final-round winner. ❑
Theorem 3.17.
.
- Proof.
We structure this proof so as to yield not just this theorem but also the related result that we state as Corollary 3.18.
: Let and let be a candidate partition that witnesses this membership. Consider the case where uniquely wins the final round. If , then uniquely wins and in the final round defeats all candidates in . If , then in the final round defeats the candidate (if any) that survives the tie-handling rule regarding the subelection as well as all the candidates in . Regardless of which case holds, the partition will witness since will uniquely win its subelection and then will defeat any candidate that moves forward from the other subelection. If does not uniquely win the final round, then there is at least one other candidate that ties with in the final round. If , then must uniquely win in and as no candidate in can have a score greater than ’s (since witnesses ), the partition suffices to witness . If , then under partition could first-round tie with a candidate and be eliminated (under run-off partition of candidates due to the rule). However, let denote the (possibly empty) set of candidates (other than ) that tie with in . Then the partition witnesses , since will uniquely win and will either tie or defeat the winner (if any) of .
: Let and let be a candidate partition that witnesses this membership. Without loss of generality, assume that . Thus it holds that uniquely wins . If uniquely wins the final round, then also defeats the candidate (if any) that moves forward from . Thus the partition will also witness (since has strictly more approvals than any candidate other than itself). If does not uniquely win the final round, then there is another candidate , who is the unique winner of and ties with in the final round. Again the partition suffices to witness since proceeds to the final round and both and win there due to their numbers of approvals. ❑
Corollary (to the Proof) 3.18.
.
-
Proof.
This is an immediate corollary to the above proof of Theorem 3.17, as the proof was intentionally structured to ensure that if the witness of one type made a unique winner of the final round, then the constructed-above (sometimes different) partition for the other type also made a unique winner of the final round under that other type of control. ❑
We can additionally show the following three containments. Theorem 3.20 and Corollary 3.21 are surprising, since they are about partitioning different components of elections.
Theorem 3.19.
.
-
Proof.
The proof is similar in flavor to that of Theorem 3.16. Let and let be a vote partition that witnesses this membership. There are two cases to consider. Either uniquely wins in exactly one subelection (it certainly cannot uniquely win in both, else would be the unique final-round winner), or is not a unique winner in either subelection. In the latter case, the partition witnesses that as never survives the tie-handling rule (because it is not a unique winner in either subelection). In the former case, the partition witnesses that . This is so because, in that case, there must exist a candidate that in the setting under partition proceeds to the final stage and in the second round has a score at least as high as that of . So in the setting’s first round under the partition , in the subelection candidate can at best tie , and thus certainly cannot move forward under the tie-handling rule. Additionally, no one moves forward from subelection (everyone ties and, since in the current case we know there are at least two candidates, everyone is eliminated from that subelection). This shows the containment. The separation witness for the strict containment can be found in Table LABEL:table:approval-results. ❑
Theorem 3.20.
.
-
Proof.
Let and let be a candidate partition that witnesses this membership. Then, with respect to that partition, is eliminated either in its subelection (either by tieing or by losing) or in the final round. In both cases, this must happen because there is another candidate such that ’s score is at most ’s score (using vote set ). By using the partition , we know that every candidate will proceed to the final round (everyone ties in and proceeds to the final round) and in that final round, either will tie or will defeat . In either case, is not a unique winner. This shows the containment. The separation witness for the strict containment can be found in Table LABEL:table:approval-results. ❑
Corollary 3.21.
.
4 Related Work
Electoral control attacks were introduced and studied by Bartholdi, Tovey, and Trick in a tremendously influential 1992 paper (?). They defined a set of attacks based on adding/deleting/partitioning candidates and voters, and those attacks have been studied ever since.
? (?) studied only the goal of making a particular focus candidate be an untied winner of the election (i.e., constructive control in the unique-winner model). ? (?) introduced “destructive control” versions of each constructive control type: The goal is to prevent (via the given control action) the focus candidate from becoming a unique winner. Later papers often additionally, or only, used the nonunique-winner model, in which the goal is to make the focus candidate be (or, for the destructive case, not be) a winner. As far as we know, the first example of this was a study of Llull and Copeland elections by ? (?, ?) that studied both winner models, and ? (?) (see also ?, Footnote 5) argue that the nonunique-winner model is a better model to study than the unique-winner model.
? (?) addressed the ways of handling ties in the first-round elections of the (two-round) “partition” control types of ? (?), and framed the two now-standard approaches called “ties promote” and “ties eliminate”; they did this because although tie-handling had previously been suggested as being unimportant, their paper establishes that, for example, for plurality the choice between those two rules spells the difference between being NP-complete and belonging to P. The “adding candidates” control attack of ? (?) was anomalously defined, and ? (?) kept the original notion but renamed it “unlimited adding of candidates,” and introduced, under the thus-available name “adding candidates,” the version that is analogous to the other ? (?) add/delete types, and the subsequent papers have followed that notational shift.
Altogether, the ? (?) control attack set, under the above clarifications and enrichments, yields a set of eleven constructive control attacks and eleven destructive control attacks. As mentioned earlier, this in some sense forms a “standard” benchmark set of attacks (though some papers use subsets of that collection, and other papers have taken control in additional directions, e.g., resolute control ?, ?). For example, the excellent survey chapter on control and bribery by ? (?) uses precisely those 22 control attacks, as does the recent paper on search versus decision of ? (?). Since the field has not yet resolved whether nonunique-winner or unique-winner is the right standard—indeed, the two just-cited sources make different choices—and because discovering cases when a control type in one of those models turns out to be identical to a control type in the other is itself interesting, in this paper we covered both models, and thus control types.
Of the pairs (322 of them compatible) of those control types, seven were proven to collapse in ? (?). That is the paper that most strongly inspired the present paper. It also separates one pair: --- and ---. However, it does so using an election system that is not (candidate-)neutral. In our present paper, regarding that separation and all separations, we obtain them directly in systems that are (candidate-)neutral or by inheritance from systems that are (candidate-)neutral.
The additional, different control types known as resolute control (?, ?) are quite interesting. Resolute control asks whether there is some action (from a certain range of actions) that keeps every one of a certain collection of candidates from being a winner. This might seem to be the same as our function model for the case of (nonunique-winner) destructive control, but it is not. In our function model for nonunique-winner destructive control, we are speaking of the collection of candidates who can individually be prevented from winning by some control action. But even if two or more candidates belong to our function’s output, they could be put into that output by different control actions, and there might be no single action that blocks both simultaneously. In brief, resolute control is focused on blocking whole groups, and our function model in contrast is a refinement of set separations and focuses on individual candidates to let us identify new containment patterns between control types.
Collapsing or separating control types is not directly about complexity. However, doing so is highly relevant to complexity, as the types were defined as natural benchmarks whose complexity could be studied. In fact, there has been something of a race to find natural systems in which very many control attacks are -hard to carry out.131313Regarding the “race” to find systems that are resistant to a large number of control types, one might ask whether it still is fair to count it as multiple strengths if the elements of collapsing pairs (or larger equivalence classes) are resistant (and so NP-hard), or to count it as multiple weaknesses if the elements of collapsing pairs (or larger equivalence classes) are vulnerable (and thus in P). In some sense, one could argue that this is unfair, as it is putting extra weight on the “same” type. However, one could also argue that having a collapsing control type foursome count as four is fair and natural, since the actual mechanisms of the four are different, and so one either is fighting off attacks through NP-completeness, or is vulnerable to multiple attack lines. In any case, if one focuses solely on number of resistances, one is implicitly saying that all control types are equally important, and we do not think that saying that is correct. Rather, what is most important is that the field knows, for the full palette of control types, which ones are resistant and which ones are vulnerable with respect to a given election system. That will allow the people choosing which election system to use in a given setting to choose an election system that is resistant to as many as possible of the attacks that they expect are the most likely within the setting. And for that, there is no doubt that avoiding duplicate work through exploiting collapses is helpful. Finally, we mention that merging collapsed types on each system’s “score card” would be problematic, since different elections have different collapses, and so different election systems’ score cards would not even have the same number of entries. Among the many systems that have done well or very well in that race are, along with some of the key papers that analyzed the complexity of each, Schulze elections (?, ?, ?), ranked-pair elections (?, ?), SP-AV elections (?), normalized range voting (?), fallback elections (?, ?, see also ?), and Bucklin elections (?, see also ?). ? (?, Table 7.3) provide a lovely table, for the 22 unique-winner control cases, of what is known for twelve voting systems. Regarding the three important systems we spotlight in the present paper, plurality’s control was explored by ? (?) and ? (?), veto has been studied by ? (?) and ? (?) (see also ?, Table 1), and approval has been studied by ? (?) (see also ?).
5 Comments on Checking and Reproducibility
As mentioned earlier, a number of our election examples showing separations were found with the aid of computer searches. Other examples were human generated.
In addition to the verification code within the computer-search programs, we coded—with a different person doing the coding—stand-alone verification routines, as a double-check of the correctness of all separation examples used in this paper. Whether computer-generated or human-generated, every example was checked via those separate verification programs. Also, every computer-generated example was verified by a human.
To support reproducibility, and to aid researchers who might wish to carry our study to other cases, we have made the computer-search programs, and their inputs and outputs, publicly available, in effect as an online appendix of this paper, in an online repository. That repository is available at https://github.com/MikeChav/SCT_Code.
Our search programs use randomization, and the repository captures and documents the randomization used in each run generating our examples. Thus skeptical researchers could, if they wanted, simulate our code, using the same randomization, to assure themselves that our codes indeed produced the examples we claim they did. The repository also includes some information about what systems the programs were run on and how long certain runs took. (In fact, each program was run once, and the run itself randomly tried many examples until a counterexample was found; even the longest-running program ran for at most 21 CPU seconds.)
The repository additionally includes the separate verification programs mentioned above.
6 Conclusions and Open Problems
Table 1 summarizes our results. We established that in the general (universally quantified) case there are no collapsing pairs (by which we always mean among the standard 44 control types) other than the seven collapsing pairs identified by ? (?), and that plurality has no collapsing pairs beyond those seven. For veto and approval voting we discovered additional collapsing pairs beyond those inherited seven, but we also established that veto and approval voting, after our work, have no remaining undiscovered collapsing pairs.
Our work helps clarify the landscape of which control pairs do or do not collapse, both in the general (universally quantified) case, and for plurality, veto, and approval voting.
We also refined all our separations, and in doing so uncovered containment relationships—including many that do not follow from the relationship between the nonunique-winner model and the unique-winner model.
Set Classification | Subclassification of Separations | |||||
Election System | Separations | Collapses | Open | “”/“” | Incomparable | Open |
General Case | 1 + 314 = 315† | 7 | 0 | 38 | 277 | 0 |
Plurality | 315 | 7 | 0 | 38 | 277 | 0 |
Veto | 314 | 7 + 1 = 8 | 0 | 58 | 256 | 0 |
Approval Voting | 301 | 7 + 14 = 21 | 0 | 88 | 213 | 0 |
†Or 0 + 315 for the pure social choice approach to candidate names (see Footnote 2 and the discussion in the Related Work section).
A number of interesting open directions are suggested by our work. One is, for important concrete election systems other than plurality, veto, and approval voting, to completely classify the collapses and separations that hold for those specific systems. Another direction—building on the results of Section 3.3—is to find sufficient conditions (or, better still, necessary-and-sufficient conditions) for many control-pair collapses in terms of axiomatic properties of election systems. Though our goal for separations was to subclassify each separation into exactly one of the three cases “”, “”, or incomparability, in our tables we have also noted those cases where our constructions establish strong incomparability; one could for the cases where we list incomparability try to establish strong incomparability. An additional open direction is to see whether already-studied control types beyond the 44 investigated here collapse with each other or with some of the 44, either in general or for important concrete election systems.
Finally, control types are defined as sets. When a pair of control types collapses, those sets are equal and thus certainly are of the same complexity. However, it would be interesting to see whether for collapsing control types, their complexities as search problems are or are not polynomially related. That issue, inspired by the work of ? (?) and an earlier version of the present paper, has recently been studied by ? (?).
Acknowledgments
Some of these results appeared in the Proceedings of the 22nd International Conference on Autonomous Agents and Multiagent Systems (?). We thank anonymous referees and Ulle Endriss for their valuable comments, suggestions, and guidance.
References
- Bartholdi et al. Bartholdi, III, J., Tovey, C., and Trick, M. (1989a). The computational difficulty of manipulating an election. Social Choice and Welfare, 6(3), 227–241.
- Bartholdi et al. Bartholdi, III, J., Tovey, C., and Trick, M. (1989b). Voting schemes for which it can be difficult to tell who won the election. Social Choice and Welfare, 6(2), 157–165.
- Bartholdi et al. Bartholdi, III, J., Tovey, C., and Trick, M. (1992). How hard is it to control an election?. Mathematical and Computer Modeling, 16(8–9), 27–40.
- Baumeister et al. Baumeister, D., Erdélyi, G., Hemaspaandra, E., Hemaspaandra, L., and Rothe, J. (2010). Computational aspects of approval voting. In Laslier, J., and Sanver, M. (Eds.), Handbook on Approval Voting, pp. 199–251. Springer.
- Carleton et al. Carleton, B., Chavrimootoo, M., Hemaspaandra, L., Narváez, D., Taliancich, C., and Welles, H. (2022). Search versus search for collapsing electoral control types. Tech. rep. arXiv:2207.03049 [cs.GT], Computing Research Repository, arXiv.org/corr/. Revised, May 2023; extended abstract appears in AAMAS-2023 (?).
- Carleton, Chavrimootoo, Hemaspaandra, Narváez, Taliancich, and Welles Carleton, B., Chavrimootoo, M., Hemaspaandra, L., Narváez, D., Taliancich, C., and Welles, H. (2023a). Search versus search for collapsing electoral control types (extended abstract). In Proceedings of the 22nd International Conference on Autonomous Agents and Multiagent Systems, pp. 2682–2684. International Foundation for Autonomous Agents and Multiagent Systems.
- Carleton, Chavrimootoo, Hemaspaandra, Narváez, Taliancich, and Welles Carleton, B., Chavrimootoo, M., Hemaspaandra, L., Narváez, D., Taliancich, C., and Welles, H. (2023b). Separating and collapsing electoral control types. In Proceedings of the 22nd International Conference on Autonomous Agents and Multiagent Systems, pp. 1743–1751. International Foundation for Autonomous Agents and Multiagent Systems.
- Chernoff Chernoff, H. (1954). Rational selection of decision functions. Econometrica, 22(4), 422–443.
- Erdélyi, Fellows, Rothe, and Schend Erdélyi, G., Fellows, M., Rothe, J., and Schend, L. (2015). Control complexity in Bucklin and fallback voting: A theoretical analysis. Journal of Computer and System Sciences, 81(4), 632–660.
- Erdélyi, Nowak, and Rothe Erdélyi, G., Nowak, M., and Rothe, J. (2009). Sincere-strategy preference-based approval voting fully resists constructive control and broadly resists destructive control. Mathematical Logic Quarterly, 55(4), 425–443.
- Erdélyi, Piras, and Rothe Erdélyi, G., Piras, L., and Rothe, J. (2011). The complexity of voter partition in Bucklin and fallback voting: Solving three open problems. In Proceedings of the 10th International Conference on Autonomous Agents and Multiagent Systems, pp. 837–844. International Foundation for Autonomous Agents and Multiagent Systems.
- Erdélyi, Reger, and Yang Erdélyi, G., Reger, C., and Yang, Y. (2019). Towards completing the puzzle: Solving open problems for control in elections. In Proceedings of the 18th International Conference on Autonomous Agents and Multiagent Systems, pp. 846–854. International Foundation for Autonomous Agents and Multiagent Systems.
- Erdélyi and Rothe Erdélyi, G., and Rothe, J. (2010). Control complexity in fallback voting. In Proceedings the 16th Australasian Theory Symposium, pp. 39–48. Australian Computer Society.
- Faliszewski, Hemaspaandra, Hemaspaandra, and Rothe Faliszewski, P., Hemaspaandra, E., Hemaspaandra, L., and Rothe, J. (2007). Llull and Copeland voting broadly resist bribery and control. In Proceedings of the 22nd AAAI Conference on Artificial Intelligence, pp. 724–730. AAAI Press.
- Faliszewski, Hemaspaandra, Hemaspaandra, and Rothe Faliszewski, P., Hemaspaandra, E., Hemaspaandra, L., and Rothe, J. (2009). Llull and Copeland voting computationally resist bribery and constructive control. Journal of Artificial Intelligence Research, 35, 275–341.
- Faliszewski and Rothe Faliszewski, P., and Rothe, J. (2016). Control and bribery in voting. In Brandt, F., Conitzer, V., Endriss, U., Lang, J., and Procaccia, A. (Eds.), Handbook of Computational Social Choice, pp. 146–168. Cambridge University Press.
- Gupta, Roy, Saurabh, and Zehavi Gupta, S., Roy, S., Saurabh, S., and Zehavi, M. (2022). Resolute control: Forbidding candidates from winning an election is hard. Theoretical Computer Science, 915, 74–89.
- Hemaspaandra, Hemaspaandra, and Menton Hemaspaandra, E., Hemaspaandra, L., and Menton, C. (2020). Search versus decision for election manipulation problems. ACM Transactions on Computation Theory, 12(#1, Article 3), 1–42.
- Hemaspaandra, Hemaspaandra, and Rothe Hemaspaandra, E., Hemaspaandra, L., and Rothe, J. (2007). Anyone but him: The complexity of precluding an alternative. Artificial Intelligence, 171(5–6), 255–285.
- Hemaspaandra, Hemaspaandra, and Rothe Hemaspaandra, E., Hemaspaandra, L., and Rothe, J. (2009). Hybrid elections broaden complexity-theoretic resistance to control. Mathematical Logic Quarterly, 55(4), 397–424.
- Hemaspaandra, Lavaee, and Menton Hemaspaandra, L., Lavaee, R., and Menton, C. (2016). Schulze and ranked-pairs voting are fixed-parameter tractable to bribe, manipulate, and control. Annals of Mathematics and Artificial Intelligence, 77(3–4), 191–223.
- Lin Lin, A. (2012). Solving Hard Problems in Election Systems. Ph.D. thesis, Rochester Institute of Technology, Rochester, NY.
- Maushagen and Rothe Maushagen, C., and Rothe, J. (2018). Complexity of control by partitioning veto elections and of control by adding candidates to plurality elections. Annals of Mathematics and Artificial Intelligence, 82(4), 219–244.
- Menton Menton, C. (2013). Normalized range voting broadly resists control. Theory of Computing Systems, 53(4), 507–531.
- Menton and Singh Menton, C., and Singh, P. (2013). Control complexity of Schulze voting. In Proceedings of the 23rd International Joint Conference on Artificial Intelligence, pp. 286–292. AAAI Press.
- Neveling and Rothe Neveling, M., and Rothe, J. (2017). Solving seven open problems of offline and online control in Borda elections. In Proceedings of the 31st AAAI Conference on Artificial Intelligence, pp. 3029–3035. AAAI Press.
- Parkes and Xia Parkes, D., and Xia, L. (2012). A complexity-of-strategic-behavior comparison between Schulze’s rule and ranked pairs. In Proceedings of the 26th AAAI Conference on Artificial Intelligence, pp. 1429–1435. AAAI Press.
- Sen Sen, A. (1971). Choice functions and revealed preference. The Review of Economic Studies, 38(3), 307–317.
- Yang and Wang Yang, Y., and Wang, J. (2017). Anyone but them: The complexity challenge for a resolute election controller. In Proceedings of the 16th International Conference on Autonomous Agents and Multiagent Systems, pp. 1133–1141. International Foundation for Autonomous Agents and Multiagent Systems.
Appendix A Compatible Control Types
Table LABEL:table:compatibility shows how the 44 standard control types partition into five compatibility equivalence classes. Every other (distinct) pair among the 44 is not a compatible pair.
Control Type | Candidates | Votes | Focus Candidate | Spoiler Candidates | Spoiler Votes | Limit (Natural Number) |
---|---|---|---|---|---|---|
CC-PV-TE-UW, CC-PV-TE-NUW, | Yes | Yes | Yes | No | No | No |
CC-PV-TP-UW, CC-PV-TP-NUW, | ||||||
CC-PC-TE-UW, CC-PC-TE-NUW, | ||||||
CC-PC-TP-UW, CC-PC-TP-NUW, | ||||||
CC-RPC-TE-UW, CC-RPC-TE-NUW, | ||||||
CC-RPC-TP-UW, CC-RPC-TP-NUW, | ||||||
DC-PV-TE-UW, DC-PV-TE-NUW, | ||||||
DC-PV-TP-UW, DC-PV-TP-NUW, | ||||||
DC-PC-TE-UW, DC-PC-TE-NUW, | ||||||
DC-PC-TP-UW, DC-PC-TP-NUW, | ||||||
DC-RPC-TE-UW, DC-RPC-TE-NUW, | ||||||
DC-RPC-TP-UW, DC-RPC-TP-NUW | ||||||
CC-AC-UW, CC-AC-NUW, | Yes | Yes | Yes | Yes | No | Yes |
DC-AC-UW, DC-AC-NUW | ||||||
CC-DC-UW, CC-DC-NUW, | Yes | Yes | Yes | No | No | Yes |
CC-DV-UW, CC-DV-NUW, | ||||||
DC-DC-UW, DC-DC-NUW, | ||||||
DC-DV-UW, DC-DV-NUW | ||||||
CC-AV-UW, CC-AV-NUW, | Yes | Yes | Yes | No | Yes | Yes |
DC-AV-UW, DC-AV-NUW | ||||||
CC-UAC-UW, CC-UAC-NUW, | Yes | Yes | Yes | Yes | No | No |
DC-UAC-UW, DC-UAC-NUW |
Appendix B Tables
Tables LABEL:table:plurality-tools, LABEL:table:veto-tools, and LABEL:table:approval-tools list each of the elections (identified by a candidate set and a vote set ) used to show separations and incomparability. Each line of these tables also has some columns that may have no entries (denoted by “-”). These columns are (to denote additional candidates when the control type is about adding candidates), (to denote additional votes when the control type is about adding votes), and (to denote the limit imposed on a particular control, e.g., limited adding of candidates, or deleting candidates/voters).
We assign an ID to each election and use those IDs from Tables LABEL:table:plurality-tools, LABEL:table:veto-tools, and LABEL:table:approval-tools in Tables LABEL:table:plurality-results, LABEL:table:veto-results, and LABEL:table:approval-results to identify which tool is a separation witness. The obvious containments (that are about UW and NUW variants of the same control type, see location in Section 1) are implicit in this table and thus we do not explicitly mark when they are used.
Additionally, we color code Tables LABEL:table:plurality-results, LABEL:table:veto-results, and LABEL:table:approval-results in a specific manner: The entries that have the same (nonwhite) background color form an equivalence class. Each entry that is not colored (i.e., that has a white background) is an equivalence class of size one, and we will not color such entries. Table LABEL:table:equivalence-classes provides a summary of the equivalence classes and their corresponding colors.
Each boldfaced entry indicates the canonical element of its equivalence class. Those are also indicated in Tables LABEL:table:plurality-results, LABEL:table:veto-results, and LABEL:table:approval-results. Having canonical elements helped make the proof process more economical. If we separate from , we implicitly have separated from all members of the equivalence class of . In the proof process we focused on separations regarding only two canonical elements (where we view each singleton type as a stand-alone canonical element of its size-one equivalence class, though we don’t boldface those).
Class | Color |
---|---|
Plurality-DC-RPC-TE-NUW, , , | |
Plurality-DC-RPC-TP-NUW, | |
Veto-DC-RPC-TE-NUW, , , | |
Veto-DC-RPC-TP-NUW, | |
Veto-DC-PV-TE-NUW, | |
Approval-DC-PV-TE-NUW, | |
Approval-DC-RPC-TE-NUW, , , , , | |
Approval-DC-RPC-TP-NUW, | |
Approval-CC-RPC-TP-UW, | |
Approval-CC-RPC-TP-NUW, | |
Approval-CC-RPC-TE-UW, | |
Approval-CC-RPC-TE-NUW, |
ID | |||||
---|---|---|---|---|---|
Plur.1 | - | - | - | ||
Plur.2 | - | - | - | ||
Plur.3 | - | - | - | ||
Plur.4† | - | - | - | ||
Plur.5 | - | - | - | ||
Plur.6 | - | - | - | ||
Plur.7 | - | - | - | ||
Plur.8 | - | - | - | ||
Plur.9 | - | - | - | ||
Plur.10 | - | - | - | ||
Plur.11 | - | - | - | ||
Plur.12 | - | - | - | ||
Plur.13 | - | - | - | ||
Plur.14 | - | - | - | ||
Plur.15 | - | - | - | ||
Plur.16 | - | - | - | ||
Plur.17 | - | - | - | ||
Plur.18 | - | - | - | ||
Plur.19 | - | - | - | ||
Plur.20 | - | - | - | ||
Plur.21 | - | - | - | ||
Plur.22 | - | - | - | ||
Plur.23 | - | - | - | ||
Plur.24 | - | - | - | ||
Plur.25† | - | - | - | ||
Plur.26† | - | - | - | ||
Plur.27 | - | 1 | |||
Plur.28 | - | 1 | |||
Plur.29 | - | 1 | |||
Plur.30 | - | - | 0 | ||
Plur.31 | - | - | 2 | ||
Plur.32 | - | - | 2 | ||
Plur.33 | - | 0 | |||
Plur.34 | - | - | 0 | ||
Plur.35 | - | 0 | |||
Plur.36 | - | - | |||
Plur.37 | - | 0 | |||
Plur.38 | - | - | 0 | ||
Plur.39 | - | 0 | |||
Plur.40 | - | - | |||
Plur.41 | - | - | 1 | ||
Plur.42 | - | - | 1 | ||
Plur.43 | - | - | 1 | ||
Plur.44 | - | - | - | ||
Plur.45 | - | - | - | ||
Plur.46 | - | - | - | ||
Plur.47† | - | - | - | ||
Plur.48† | - | - | - | ||
Plur.49† | - | - | - | ||
Plur.50† | - | - | - |
Classification | Justification(s) | ||
---|---|---|---|
CC-PV-TE-UW | CC-PV-TE-NUW | Plur.2 | |
CC-PV-TE-UW | CC-PV-TP-UW | INCOMP | Plur.1 + Plur.50 |
CC-PV-TE-UW | CC-PV-TP-NUW | INCOMP | Plur.2 + Plur.46 |
CC-PV-TE-UW | CC-RPC-TE-UW | INCOMP | Plur.20 + Plur.23 |
CC-PV-TE-UW | CC-RPC-TE-NUW | INCOMP | Plur.20 + Plur.23 |
CC-PV-TE-UW | CC-RPC-TP-UW | INCOMP | Plur.1 + Plur.24 |
CC-PV-TE-UW | CC-RPC-TP-NUW | INCOMP | Plur.20 + Plur.23 |
CC-PV-TE-UW | CC-PC-TE-UW | INCOMP | Plur.20 + Plur.23 |
CC-PV-TE-UW | CC-PC-TE-NUW | INCOMP | Plur.20 + Plur.23 |
CC-PV-TE-UW | CC-PC-TP-UW | INCOMP | Plur.1 + Plur.24 |
CC-PV-TE-UW | CC-PC-TP-NUW | INCOMP | Plur.20 + Plur.23 |
CC-PV-TE-UW | DC-PV-TE-UW | INCOMP∗ | Plur.3 |
CC-PV-TE-UW | DC-PV-TE-NUW | INCOMP∗ | Plur.3 |
CC-PV-TE-UW | DC-PV-TP-UW | INCOMP∗ | Plur.3 |
CC-PV-TE-UW | DC-PV-TP-NUW | INCOMP∗ | Plur.3 |
CC-PV-TE-UW | DC-RPC-TE-UW | INCOMP∗ | Plur.3 |
CC-PV-TE-UW | DC-RPC-TE-NUW | INCOMP∗ | Plur.3 |
CC-PV-TE-UW | DC-RPC-TP-UW | INCOMP∗ | Plur.3 |
CC-PV-TE-UW | DC-RPC-TP-NUW | INCOMP∗ | Plur.3 |
CC-PV-TE-UW | DC-PC-TE-UW | INCOMP∗ | Plur.3 |
CC-PV-TE-UW | DC-PC-TE-NUW | INCOMP∗ | Plur.3 |
CC-PV-TE-UW | DC-PC-TP-UW | INCOMP∗ | Plur.3 |
CC-PV-TE-UW | DC-PC-TP-NUW | INCOMP∗ | Plur.3 |
CC-PV-TE-NUW | CC-PV-TP-UW | INCOMP | Plur.2 + Plur.50 |
CC-PV-TE-NUW | CC-PV-TP-NUW | INCOMP | Plur.14 + Plur.50 |
CC-PV-TE-NUW | CC-RPC-TE-UW | INCOMP | Plur.20 + Plur.23 |
CC-PV-TE-NUW | CC-RPC-TE-NUW | INCOMP | Plur.20 + Plur.23 |
CC-PV-TE-NUW | CC-RPC-TP-UW | INCOMP | Plur.2 + Plur.24 |
CC-PV-TE-NUW | CC-RPC-TP-NUW | INCOMP | Plur.20 + Plur.23 |
CC-PV-TE-NUW | CC-PC-TE-UW | INCOMP | Plur.20 + Plur.23 |
CC-PV-TE-NUW | CC-PC-TE-NUW | INCOMP | Plur.20 + Plur.23 |
CC-PV-TE-NUW | CC-PC-TP-UW | INCOMP | Plur.2 + Plur.24 |
CC-PV-TE-NUW | CC-PC-TP-NUW | INCOMP | Plur.20 + Plur.23 |
CC-PV-TE-NUW | DC-PV-TE-UW | INCOMP∗ | Plur.3 |
CC-PV-TE-NUW | DC-PV-TE-NUW | INCOMP∗ | Plur.3 |
CC-PV-TE-NUW | DC-PV-TP-UW | INCOMP∗ | Plur.3 |
CC-PV-TE-NUW | DC-PV-TP-NUW | INCOMP∗ | Plur.3 |
CC-PV-TE-NUW | DC-RPC-TE-UW | INCOMP∗ | Plur.3 |
CC-PV-TE-NUW | DC-RPC-TE-NUW | INCOMP∗ | Plur.3 |
CC-PV-TE-NUW | DC-RPC-TP-UW | INCOMP∗ | Plur.3 |
CC-PV-TE-NUW | DC-RPC-TP-NUW | INCOMP∗ | Plur.3 |
CC-PV-TE-NUW | DC-PC-TE-UW | INCOMP∗ | Plur.3 |
CC-PV-TE-NUW | DC-PC-TE-NUW | INCOMP∗ | Plur.3 |
CC-PV-TE-NUW | DC-PC-TP-UW | INCOMP∗ | Plur.3 |
CC-PV-TE-NUW | DC-PC-TP-NUW | INCOMP∗ | Plur.3 |
CC-PV-TP-UW | CC-PV-TP-NUW | Plur.21 | |
CC-PV-TP-UW | CC-RPC-TE-UW | INCOMP | Plur.20 + Plur.23 |
CC-PV-TP-UW | CC-RPC-TE-NUW | INCOMP | Plur.20 + Plur.23 |
CC-PV-TP-UW | CC-RPC-TP-UW | INCOMP | Plur.1 + Plur.23 |
CC-PV-TP-UW | CC-RPC-TP-NUW | INCOMP | Plur.2 + Plur.23 |
CC-PV-TP-UW | CC-PC-TE-UW | INCOMP | Plur.18 + Plur.23 |
CC-PV-TP-UW | CC-PC-TE-NUW | INCOMP | Plur.2 + Plur.23 |
CC-PV-TP-UW | CC-PC-TP-UW | INCOMP | Plur.1 + Plur.23 |
CC-PV-TP-UW | CC-PC-TP-NUW | INCOMP | Plur.2 + Plur.23 |
CC-PV-TP-UW | DC-PV-TE-UW | INCOMP∗ | Plur.3 |
CC-PV-TP-UW | DC-PV-TE-NUW | INCOMP∗ | Plur.3 |
CC-PV-TP-UW | DC-PV-TP-UW | INCOMP∗ | Plur.3 |
CC-PV-TP-UW | DC-PV-TP-NUW | INCOMP∗ | Plur.3 |
CC-PV-TP-UW | DC-RPC-TE-UW | INCOMP∗ | Plur.3 |
CC-PV-TP-UW | DC-RPC-TE-NUW | INCOMP∗ | Plur.3 |
CC-PV-TP-UW | DC-RPC-TP-UW | INCOMP∗ | Plur.3 |
CC-PV-TP-UW | DC-RPC-TP-NUW | INCOMP∗ | Plur.3 |
CC-PV-TP-UW | DC-PC-TE-UW | INCOMP∗ | Plur.3 |
CC-PV-TP-UW | DC-PC-TE-NUW | INCOMP∗ | Plur.3 |
CC-PV-TP-UW | DC-PC-TP-UW | INCOMP∗ | Plur.3 |
CC-PV-TP-UW | DC-PC-TP-NUW | INCOMP∗ | Plur.3 |
CC-PV-TP-NUW | CC-RPC-TE-UW | INCOMP | Plur.2 + Plur.24 |
CC-PV-TP-NUW | CC-RPC-TE-NUW | INCOMP | Plur.18 + Plur.23 |
CC-PV-TP-NUW | CC-RPC-TP-UW | INCOMP | Plur.2 + Plur.24 |
CC-PV-TP-NUW | CC-RPC-TP-NUW | INCOMP | Plur.15 + Plur.24 |
CC-PV-TP-NUW | CC-PC-TE-UW | INCOMP | Plur.2 + Plur.24 |
CC-PV-TP-NUW | CC-PC-TE-NUW | INCOMP | Plur.18 + Plur.23 |
CC-PV-TP-NUW | CC-PC-TP-UW | INCOMP | Plur.2 + Plur.24 |
CC-PV-TP-NUW | CC-PC-TP-NUW | INCOMP | Plur.20 + Plur.23 |
CC-PV-TP-NUW | DC-PV-TE-UW | INCOMP∗ | Plur.3 |
CC-PV-TP-NUW | DC-PV-TE-NUW | INCOMP∗ | Plur.3 |
CC-PV-TP-NUW | DC-PV-TP-UW | INCOMP∗ | Plur.3 |
CC-PV-TP-NUW | DC-PV-TP-NUW | INCOMP∗ | Plur.3 |
CC-PV-TP-NUW | DC-RPC-TE-UW | INCOMP∗ | Plur.3 |
CC-PV-TP-NUW | DC-RPC-TE-NUW | INCOMP∗ | Plur.3 |
CC-PV-TP-NUW | DC-RPC-TP-UW | INCOMP∗ | Plur.3 |
CC-PV-TP-NUW | DC-RPC-TP-NUW | INCOMP∗ | Plur.3 |
CC-PV-TP-NUW | DC-PC-TE-UW | INCOMP∗ | Plur.3 |
CC-PV-TP-NUW | DC-PC-TE-NUW | INCOMP∗ | Plur.3 |
CC-PV-TP-NUW | DC-PC-TP-UW | INCOMP∗ | Plur.3 |
CC-PV-TP-NUW | DC-PC-TP-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TE-UW | CC-RPC-TE-NUW | Plur.2 | |
CC-RPC-TE-UW | CC-RPC-TP-UW | INCOMP∗ | Plur.22 |
CC-RPC-TE-UW | CC-RPC-TP-NUW | INCOMP | Plur.2 + Plur.44 |
CC-RPC-TE-UW | CC-PC-TE-UW | INCOMP | Plur.22 + Plur.49 |
CC-RPC-TE-UW | CC-PC-TE-NUW | INCOMP | Plur.2 + Plur.49 |
CC-RPC-TE-UW | CC-PC-TP-UW | INCOMP | Plur.18 + Plur.47 |
CC-RPC-TE-UW | CC-PC-TP-NUW | INCOMP | Plur.2 + Plur.44 |
CC-RPC-TE-UW | DC-PV-TE-UW | INCOMP∗ | Plur.3 |
CC-RPC-TE-UW | DC-PV-TE-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TE-UW | DC-PV-TP-UW | INCOMP∗ | Plur.3 |
CC-RPC-TE-UW | DC-PV-TP-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TE-UW | DC-RPC-TE-UW | INCOMP∗ | Plur.3 |
CC-RPC-TE-UW | DC-RPC-TE-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TE-UW | DC-RPC-TP-UW | INCOMP∗ | Plur.3 |
CC-RPC-TE-UW | DC-RPC-TP-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TE-UW | DC-PC-TE-UW | INCOMP∗ | Plur.3 |
CC-RPC-TE-UW | DC-PC-TE-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TE-UW | DC-PC-TP-UW | INCOMP∗ | Plur.3 |
CC-RPC-TE-UW | DC-PC-TP-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TE-NUW | CC-RPC-TP-UW | INCOMP | Plur.2 + Plur.4 |
CC-RPC-TE-NUW | CC-RPC-TP-NUW | INCOMP | Plur.18 + Plur.45 |
CC-RPC-TE-NUW | CC-PC-TE-UW | INCOMP | Plur.2 + Plur.47 |
CC-RPC-TE-NUW | CC-PC-TE-NUW | INCOMP | Plur.15 + Plur.49 |
CC-RPC-TE-NUW | CC-PC-TP-UW | INCOMP | Plur.2 + Plur.47 |
CC-RPC-TE-NUW | CC-PC-TP-NUW | INCOMP | Plur.6 + Plur.45 |
CC-RPC-TE-NUW | DC-PV-TE-UW | INCOMP∗ | Plur.3 |
CC-RPC-TE-NUW | DC-PV-TE-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TE-NUW | DC-PV-TP-UW | INCOMP∗ | Plur.3 |
CC-RPC-TE-NUW | DC-PV-TP-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TE-NUW | DC-RPC-TE-UW | INCOMP∗ | Plur.3 |
CC-RPC-TE-NUW | DC-RPC-TE-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TE-NUW | DC-RPC-TP-UW | INCOMP∗ | Plur.3 |
CC-RPC-TE-NUW | DC-RPC-TP-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TE-NUW | DC-PC-TE-UW | INCOMP∗ | Plur.3 |
CC-RPC-TE-NUW | DC-PC-TE-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TE-NUW | DC-PC-TP-UW | INCOMP∗ | Plur.3 |
CC-RPC-TE-NUW | DC-PC-TP-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TP-UW | CC-RPC-TP-NUW | Plur.2 | |
CC-RPC-TP-UW | CC-PC-TE-UW | INCOMP | Plur.18 + Plur.47 |
CC-RPC-TP-UW | CC-PC-TE-NUW | INCOMP | Plur.2 + Plur.49 |
CC-RPC-TP-UW | CC-PC-TP-UW | INCOMP | Plur.7 + Plur.47 |
CC-RPC-TP-UW | CC-PC-TP-NUW | INCOMP | Plur.2 + Plur.49 |
CC-RPC-TP-UW | DC-PV-TE-UW | INCOMP∗ | Plur.3 |
CC-RPC-TP-UW | DC-PV-TE-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TP-UW | DC-PV-TP-UW | INCOMP∗ | Plur.3 |
CC-RPC-TP-UW | DC-PV-TP-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TP-UW | DC-RPC-TE-UW | INCOMP∗ | Plur.3 |
CC-RPC-TP-UW | DC-RPC-TE-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TP-UW | DC-RPC-TP-UW | INCOMP∗ | Plur.3 |
CC-RPC-TP-UW | DC-RPC-TP-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TP-UW | DC-PC-TE-UW | INCOMP∗ | Plur.3 |
CC-RPC-TP-UW | DC-PC-TE-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TP-UW | DC-PC-TP-UW | INCOMP∗ | Plur.3 |
CC-RPC-TP-UW | DC-PC-TP-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TP-NUW | CC-PC-TE-UW | INCOMP | Plur.2 + Plur.9 |
CC-RPC-TP-NUW | CC-PC-TE-NUW | INCOMP | Plur.6 + Plur.49 |
CC-RPC-TP-NUW | CC-PC-TP-UW | INCOMP | Plur.2 + Plur.47 |
CC-RPC-TP-NUW | CC-PC-TP-NUW | INCOMP | Plur.8 + Plur.49 |
CC-RPC-TP-NUW | DC-PV-TE-UW | INCOMP∗ | Plur.3 |
CC-RPC-TP-NUW | DC-PV-TE-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TP-NUW | DC-PV-TP-UW | INCOMP∗ | Plur.3 |
CC-RPC-TP-NUW | DC-PV-TP-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TP-NUW | DC-RPC-TE-UW | INCOMP∗ | Plur.3 |
CC-RPC-TP-NUW | DC-RPC-TE-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TP-NUW | DC-RPC-TP-UW | INCOMP∗ | Plur.3 |
CC-RPC-TP-NUW | DC-RPC-TP-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TP-NUW | DC-PC-TE-UW | INCOMP∗ | Plur.3 |
CC-RPC-TP-NUW | DC-PC-TE-NUW | INCOMP∗ | Plur.3 |
CC-RPC-TP-NUW | DC-PC-TP-UW | INCOMP∗ | Plur.3 |
CC-RPC-TP-NUW | DC-PC-TP-NUW | INCOMP∗ | Plur.3 |
CC-PC-TE-UW | CC-PC-TE-NUW | Plur.2 | |
CC-PC-TE-UW | CC-PC-TP-UW | INCOMP | Plur.17 + Plur.48 |
CC-PC-TE-UW | CC-PC-TP-NUW | INCOMP | Plur.2 + Plur.44 |
CC-PC-TE-UW | DC-PV-TE-UW | INCOMP∗ | Plur.3 |
CC-PC-TE-UW | DC-PV-TE-NUW | INCOMP∗ | Plur.3 |
CC-PC-TE-UW | DC-PV-TP-UW | INCOMP∗ | Plur.3 |
CC-PC-TE-UW | DC-PV-TP-NUW | INCOMP∗ | Plur.3 |
CC-PC-TE-UW | DC-RPC-TE-UW | INCOMP∗ | Plur.3 |
CC-PC-TE-UW | DC-RPC-TE-NUW | INCOMP∗ | Plur.3 |
CC-PC-TE-UW | DC-RPC-TP-UW | INCOMP∗ | Plur.3 |
CC-PC-TE-UW | DC-RPC-TP-NUW | INCOMP∗ | Plur.3 |
CC-PC-TE-UW | DC-PC-TE-UW | INCOMP∗ | Plur.3 |
CC-PC-TE-UW | DC-PC-TE-NUW | INCOMP∗ | Plur.3 |
CC-PC-TE-UW | DC-PC-TP-UW | INCOMP∗ | Plur.3 |
CC-PC-TE-UW | DC-PC-TP-NUW | INCOMP∗ | Plur.3 |
CC-PC-TE-NUW | CC-PC-TP-UW | INCOMP | Plur.2 + Plur.48 |
CC-PC-TE-NUW | CC-PC-TP-NUW | INCOMP | Plur.6 + Plur.48 |
CC-PC-TE-NUW | DC-PV-TE-UW | INCOMP∗ | Plur.3 |
CC-PC-TE-NUW | DC-PV-TE-NUW | INCOMP∗ | Plur.3 |
CC-PC-TE-NUW | DC-PV-TP-UW | INCOMP∗ | Plur.3 |
CC-PC-TE-NUW | DC-PV-TP-NUW | INCOMP∗ | Plur.3 |
CC-PC-TE-NUW | DC-RPC-TE-UW | INCOMP∗ | Plur.3 |
CC-PC-TE-NUW | DC-RPC-TE-NUW | INCOMP∗ | Plur.3 |
CC-PC-TE-NUW | DC-RPC-TP-UW | INCOMP∗ | Plur.3 |
CC-PC-TE-NUW | DC-RPC-TP-NUW | INCOMP∗ | Plur.3 |
CC-PC-TE-NUW | DC-PC-TE-UW | INCOMP∗ | Plur.3 |
CC-PC-TE-NUW | DC-PC-TE-NUW | INCOMP∗ | Plur.3 |
CC-PC-TE-NUW | DC-PC-TP-UW | INCOMP∗ | Plur.3 |
CC-PC-TE-NUW | DC-PC-TP-NUW | INCOMP∗ | Plur.3 |
CC-PC-TP-UW | CC-PC-TP-NUW | Plur.2 | |
CC-PC-TP-UW | DC-PV-TE-UW | INCOMP∗ | Plur.3 |
CC-PC-TP-UW | DC-PV-TE-NUW | INCOMP∗ | Plur.3 |
CC-PC-TP-UW | DC-PV-TP-UW | INCOMP∗ | Plur.3 |
CC-PC-TP-UW | DC-PV-TP-NUW | INCOMP∗ | Plur.3 |
CC-PC-TP-UW | DC-RPC-TE-UW | INCOMP∗ | Plur.3 |
CC-PC-TP-UW | DC-RPC-TE-NUW | INCOMP∗ | Plur.3 |
CC-PC-TP-UW | DC-RPC-TP-UW | INCOMP∗ | Plur.3 |
CC-PC-TP-UW | DC-RPC-TP-NUW | INCOMP∗ | Plur.3 |
CC-PC-TP-UW | DC-PC-TE-UW | INCOMP∗ | Plur.3 |
CC-PC-TP-UW | DC-PC-TE-NUW | INCOMP∗ | Plur.3 |
CC-PC-TP-UW | DC-PC-TP-UW | INCOMP∗ | Plur.3 |
CC-PC-TP-UW | DC-PC-TP-NUW | INCOMP∗ | Plur.3 |
CC-PC-TP-NUW | DC-PV-TE-UW | INCOMP∗ | Plur.3 |
CC-PC-TP-NUW | DC-PV-TE-NUW | INCOMP∗ | Plur.3 |
CC-PC-TP-NUW | DC-PV-TP-UW | INCOMP∗ | Plur.3 |
CC-PC-TP-NUW | DC-PV-TP-NUW | INCOMP∗ | Plur.3 |
CC-PC-TP-NUW | DC-RPC-TE-UW | INCOMP∗ | Plur.3 |
CC-PC-TP-NUW | DC-RPC-TE-NUW | INCOMP∗ | Plur.3 |
CC-PC-TP-NUW | DC-RPC-TP-UW | INCOMP∗ | Plur.3 |
CC-PC-TP-NUW | DC-RPC-TP-NUW | INCOMP∗ | Plur.3 |
CC-PC-TP-NUW | DC-PC-TE-UW | INCOMP∗ | Plur.3 |
CC-PC-TP-NUW | DC-PC-TE-NUW | INCOMP∗ | Plur.3 |
CC-PC-TP-NUW | DC-PC-TP-UW | INCOMP∗ | Plur.3 |
CC-PC-TP-NUW | DC-PC-TP-NUW | INCOMP∗ | Plur.3 |
DC-PV-TE-UW | DC-PV-TE-NUW | Plur.9 | |
DC-PV-TE-UW | DC-PV-TP-UW | INCOMP | Plur.12 + Plur.26 |
DC-PV-TE-UW | DC-PV-TP-NUW | INCOMP | Plur.2 + Plur.26 |
DC-PV-TE-UW | DC-RPC-TE-UW | INCOMP | Plur.10 + Plur.25 |
DC-PV-TE-UW | DC-RPC-TE-NUW | INCOMP | Plur.10 + Plur.25 |
DC-PV-TE-UW | DC-RPC-TP-UW | INCOMP | Plur.16 + Plur.25 |
DC-PV-TE-UW | DC-RPC-TP-NUW | INCOMP | Plur.2 + Plur.25 |
DC-PV-TE-UW | DC-PC-TE-UW | INCOMP | Plur.10 + Plur.25 |
DC-PV-TE-UW | DC-PC-TE-NUW | INCOMP | Plur.10 + Plur.25 |
DC-PV-TE-UW | DC-PC-TP-UW | INCOMP | Plur.13 + Plur.25 |
DC-PV-TE-UW | DC-PC-TP-NUW | INCOMP | Plur.2 + Plur.25 |
DC-PV-TE-NUW | DC-PV-TP-UW | INCOMP | Plur.19 + Plur.10 |
DC-PV-TE-NUW | DC-PV-TP-NUW | INCOMP | Plur.2 + Plur.26 |
DC-PV-TE-NUW | DC-RPC-TE-UW | INCOMP | Plur.19 + Plur.10 |
DC-PV-TE-NUW | DC-RPC-TE-NUW | INCOMP | Plur.19 + Plur.10 |
DC-PV-TE-NUW | DC-RPC-TP-UW | INCOMP | Plur.16 + Plur.25 |
DC-PV-TE-NUW | DC-RPC-TP-NUW | INCOMP | Plur.2 + Plur.25 |
DC-PV-TE-NUW | DC-PC-TE-UW | INCOMP | Plur.19 + Plur.10 |
DC-PV-TE-NUW | DC-PC-TE-NUW | INCOMP | Plur.19 + Plur.10 |
DC-PV-TE-NUW | DC-PC-TP-UW | INCOMP | Plur.19 + Plur.10 |
DC-PV-TE-NUW | DC-PC-TP-NUW | INCOMP | Plur.2 + Plur.25 |
DC-PV-TP-UW | DC-PV-TP-NUW | Plur.2 | |
DC-PV-TP-UW | DC-RPC-TE-UW | INCOMP | Plur.5 + Plur.25 |
DC-PV-TP-UW | DC-RPC-TE-NUW | INCOMP | Plur.5 + Plur.25 |
DC-PV-TP-UW | DC-RPC-TP-UW | INCOMP | Plur.13 + Plur.25 |
DC-PV-TP-UW | DC-RPC-TP-NUW | INCOMP | Plur.2 + Plur.25 |
DC-PV-TP-UW | DC-PC-TE-UW | INCOMP | Plur.5 + Plur.25 |
DC-PV-TP-UW | DC-PC-TE-NUW | INCOMP | Plur.5 + Plur.25 |
DC-PV-TP-UW | DC-PC-TP-UW | INCOMP | Plur.13 + Plur.25 |
DC-PV-TP-UW | DC-PC-TP-NUW | INCOMP | Plur.2 + Plur.25 |
DC-PV-TP-NUW | DC-RPC-TE-UW | INCOMP | Plur.2 + Plur.5 |
DC-PV-TP-NUW | DC-RPC-TE-NUW | INCOMP | Plur.2 + Plur.5 |
DC-PV-TP-NUW | DC-RPC-TP-UW | INCOMP | Plur.2 + Plur.5 |
DC-PV-TP-NUW | DC-RPC-TP-NUW | INCOMP | Plur.1 + Plur.5 |
DC-PV-TP-NUW | DC-PC-TE-UW | INCOMP | Plur.2 + Plur.5 |
DC-PV-TP-NUW | DC-PC-TE-NUW | INCOMP | Plur.2 + Plur.5 |
DC-PV-TP-NUW | DC-PC-TP-UW | INCOMP | Plur.2 + Plur.5 |
DC-PV-TP-NUW | DC-PC-TP-NUW | INCOMP | Plur.1 + Plur.5 |
DC-RPC-TE-UW | DC-RPC-TE-NUW | EQ | ? (?) |
DC-RPC-TE-UW | DC-RPC-TP-UW | Plur.13 + Theorem 3.1 | |
DC-RPC-TE-UW | DC-RPC-TP-NUW | Plur.2 + Theorem 3.1 | |
DC-RPC-TE-UW | DC-PC-TE-UW | EQ | ? (?) |
DC-RPC-TE-UW | DC-PC-TE-NUW | EQ | ? (?) |
DC-RPC-TE-UW | DC-PC-TP-UW | Plur.13 + Theorem 3.1 | |
DC-RPC-TE-UW | DC-PC-TP-NUW | Plur.2 + Theorem 3.1 | |
DC-RPC-TE-NUW | DC-RPC-TP-UW | Plur.13 + Theorem 3.1 | |
DC-RPC-TE-NUW | DC-RPC-TP-NUW | Plur.2 + Theorem 3.1 | |
DC-RPC-TE-NUW | DC-PC-TE-UW | EQ | ? (?) |
DC-RPC-TE-NUW | DC-PC-TE-NUW | EQ | ? (?) |
DC-RPC-TE-NUW | DC-PC-TP-UW | Plur.13 + Theorem 3.1 | |
DC-RPC-TE-NUW | DC-PC-TP-NUW | Plur.2 + Theorem 3.1 | |
DC-RPC-TP-UW | DC-RPC-TP-NUW | Plur.2 + Theorem 3.1 | |
DC-RPC-TP-UW | DC-PC-TE-UW | Plur.13 + Theorem 3.1 + ? (?) | |
DC-RPC-TP-UW | DC-PC-TE-NUW | Plur.13 + Theorem 3.1 + ? (?) | |
DC-RPC-TP-UW | DC-PC-TP-UW | INCOMP | Plur.16 + Plur.11 |
DC-RPC-TP-UW | DC-PC-TP-NUW | Plur.2 + ? (?) | |
DC-RPC-TP-NUW | DC-PC-TE-UW | Plur.2 + Theorem 3.1 + ? (?) | |
DC-RPC-TP-NUW | DC-PC-TE-NUW | Plur.2 + Theorem 3.1 + ? (?) | |
DC-RPC-TP-NUW | DC-PC-TP-UW | Plur.2 + ? (?) | |
DC-RPC-TP-NUW | DC-PC-TP-NUW | EQ | ? (?) |
DC-PC-TE-UW | DC-PC-TE-NUW | EQ | ? (?) |
DC-PC-TE-UW | DC-PC-TP-UW | Plur.13 + Theorem 3.1 + ? (?) | |
DC-PC-TE-UW | DC-PC-TP-NUW | Plur.2 + Theorem 3.1 + ? (?) | |
DC-PC-TE-NUW | DC-PC-TP-UW | Plur.13 + Theorem 3.1 + ? (?) | |
DC-PC-TE-NUW | DC-PC-TP-NUW | Plur.2 + Theorem 3.1 + ? (?) | |
DC-PC-TP-UW | DC-PC-TP-NUW | Plur.2 | |
CC-AC-UW | CC-AC-NUW | Plur.37 | |
CC-AC-UW | DC-AC-UW | INCOMP | Plur.33 + Plur.27 |
CC-AC-UW | DC-AC-NUW | INCOMP | Plur.33 + Plur.27 |
CC-AC-NUW | DC-AC-UW | INCOMP | Plur.33 + Plur.27 |
CC-AC-NUW | DC-AC-NUW | INCOMP | Plur.33 + Plur.27 |
DC-AC-UW | DC-AC-NUW | Plur.37 | |
CC-DC-UW | CC-DC-NUW | Plur.38 | |
CC-DC-UW | CC-DV-UW | INCOMP | Plur.41 + Plur.31 |
CC-DC-UW | CC-DV-NUW | INCOMP | Plur.38 + Plur.41 |
CC-DC-UW | DC-DC-UW | INCOMP | Plur.38 + Plur.30 |
CC-DC-UW | DC-DC-NUW | INCOMP | Plur.34 + Plur.30 |
CC-DC-UW | DC-DV-UW | INCOMP | Plur.38 + Plur.30 |
CC-DC-UW | DC-DV-NUW | INCOMP | Plur.34 + Plur.30 |
CC-DC-NUW | CC-DV-UW | INCOMP | Plur.38 + Plur.31 |
CC-DC-NUW | CC-DV-NUW | INCOMP | Plur.41 + Plur.31 |
CC-DC-NUW | DC-DC-UW | INCOMP | Plur.34 + Plur.30 |
CC-DC-NUW | DC-DC-NUW | INCOMP | Plur.34 + Plur.30 |
CC-DC-NUW | DC-DV-UW | INCOMP | Plur.34 + Plur.30 |
CC-DC-NUW | DC-DV-NUW | INCOMP | Plur.34 + Plur.30 |
CC-DV-UW | CC-DV-NUW | Plur.38 | |
CC-DV-UW | DC-DC-UW | INCOMP | Plur.38 + Plur.30 |
CC-DV-UW | DC-DC-NUW | INCOMP | Plur.34 + Plur.30 |
CC-DV-UW | DC-DV-UW | INCOMP | Plur.38 + Plur.30 |
CC-DV-UW | DC-DV-NUW | INCOMP | Plur.34 + Plur.30 |
CC-DV-NUW | DC-DC-UW | INCOMP | Plur.34 + Plur.30 |
CC-DV-NUW | DC-DC-NUW | INCOMP | Plur.34 + Plur.30 |
CC-DV-NUW | DC-DV-UW | INCOMP | Plur.34 + Plur.30 |
CC-DV-NUW | DC-DV-NUW | INCOMP | Plur.34 + Plur.30 |
DC-DC-UW | DC-DC-NUW | Plur.38 | |
DC-DC-UW | DC-DV-UW | INCOMP | Plur.42 + Plur.32 |
DC-DC-UW | DC-DV-NUW | INCOMP | Plur.38 + Plur.31 |
DC-DC-NUW | DC-DV-UW | INCOMP | Plur.38 + Plur.32 |
DC-DC-NUW | DC-DV-NUW | INCOMP | Plur.43 + Plur.32 |
DC-DV-UW | DC-DV-NUW | Plur.38 | |
CC-AV-UW | CC-AV-NUW | Plur.39 | |
CC-AV-UW | DC-AV-UW | INCOMP | Plur.39 + Plur.28 |
CC-AV-UW | DC-AV-NUW | INCOMP | Plur.35 + Plur.28 |
CC-AV-NUW | DC-AV-UW | INCOMP | Plur.35 + Plur.28 |
CC-AV-NUW | DC-AV-NUW | INCOMP | Plur.35 + Plur.28 |
DC-AV-UW | DC-AV-NUW | Plur.39 | |
CC-UAC-UW | CC-UAC-NUW | Plur.40 | |
CC-UAC-UW | DC-UAC-UW | INCOMP | Plur.40 + Plur.29 |
CC-UAC-UW | DC-UAC-NUW | INCOMP | Plur.36 + Plur.29 |
CC-UAC-NUW | DC-UAC-UW | INCOMP | Plur.36 + Plur.29 |
CC-UAC-NUW | DC-UAC-NUW | INCOMP | Plur.36 + Plur.29 |
DC-UAC-UW | DC-UAC-NUW | Plur.40 |
ID | |||||
---|---|---|---|---|---|
Veto.1 | - | - | - | ||
Veto.2 | - | - | - | ||
Veto.3 | - | - | - | ||
Veto.4 | - | - | - | ||
Veto.5 | - | - | - | ||
Veto.6 | - | - | - | ||
Veto.7 | - | - | - | ||
Veto.8 | - | - | - | ||
Veto.9 | - | - | - | ||
Veto.10 | - | - | - | ||
Veto.11 | - | - | - | ||
Veto.12 | - | - | - | ||
Veto.13 | - | - | - | ||
Veto.14 | - | - | - | ||
Veto.15 | - | - | - | ||
Veto.16† | - | - | - | ||
Veto.17 | - | - | - | ||
Veto.18 | - | - | - | ||
Veto.19 | - | - | - | ||
Veto.20 | - | - | - | ||
Veto.21 | - | 1 | |||
Veto.22 | - | 1 | |||
Veto.23 | - | 1 | |||
Veto.24 | - | 1 | |||
Veto.25 | - | - | 1 | ||
Veto.26 | - | - | 0 | ||
Veto.27 | - | - | 1 | ||
Veto.28 | - | - | 1 | ||
Veto.29 | - | - | 1 | ||
Veto.30 | - | - | 1 | ||
Veto.31 | - | - | 1 | ||
Veto.32 | - | - | 0 | ||
Veto.33 | - | - | 2 | ||
Veto.34 | - | - | 1 | ||
Veto.35 | - | - | 1 | ||
Veto.36 | - | 1 | |||
Veto.37 | - | 1 | |||
Veto.38 | - | 1 | |||
Veto.39 | - | - | |||
Veto.40 | - | - | |||
Veto.41 | - | - | |||
Veto.42 | - | - | - | ||
Veto.43† | - | - | - | ||
Veto.44 | - | 0 | |||
Veto.45 | - | - | 0 | ||
Veto.46 | - | - | 2 |
Classification | Justification(s) | ||
---|---|---|---|
CC-PV-TE-UW | CC-PV-TE-NUW | Veto.1 | |
CC-PV-TE-UW | CC-PV-TP-UW | INCOMP | Veto.2 + Veto.3 |
CC-PV-TE-UW | CC-PV-TP-NUW | INCOMP | Veto.1 + Veto.3 |
CC-PV-TE-UW | CC-RPC-TE-UW | INCOMP | Veto.4 + Veto.8 |
CC-PV-TE-UW | CC-RPC-TE-NUW | INCOMP | Veto.1 + Veto.8 |
CC-PV-TE-UW | CC-RPC-TP-UW | INCOMP | Veto.4 + Veto.8 |
CC-PV-TE-UW | CC-RPC-TP-NUW | INCOMP | Veto.1 + Veto.8 |
CC-PV-TE-UW | CC-PC-TE-UW | INCOMP | Veto.4 + Veto.8 |
CC-PV-TE-UW | CC-PC-TE-NUW | INCOMP | Veto.1 + Veto.8 |
CC-PV-TE-UW | CC-PC-TP-UW | INCOMP | Veto.4 + Veto.8 |
CC-PV-TE-UW | CC-PC-TP-NUW | INCOMP | Veto.1 + Veto.8 |
CC-PV-TE-UW | DC-PV-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-UW | DC-PV-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-UW | DC-PV-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-UW | DC-PV-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-UW | DC-RPC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-UW | DC-RPC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-UW | DC-RPC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-UW | DC-RPC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-UW | DC-PC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-UW | DC-PC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-UW | DC-PC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-UW | DC-PC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-NUW | CC-PV-TP-UW | INCOMP | Veto.1 + Veto.2 |
CC-PV-TE-NUW | CC-PV-TP-NUW | INCOMP | Veto.4 + Veto.7 |
CC-PV-TE-NUW | CC-RPC-TE-UW | INCOMP | Veto.1 + Veto.2 |
CC-PV-TE-NUW | CC-RPC-TE-NUW | INCOMP | Veto.4 + Veto.8 |
CC-PV-TE-NUW | CC-RPC-TP-UW | INCOMP | Veto.1 + Veto.2 |
CC-PV-TE-NUW | CC-RPC-TP-NUW | INCOMP | Veto.4 + Veto.8 |
CC-PV-TE-NUW | CC-PC-TE-UW | INCOMP | Veto.1 + Veto.2 |
CC-PV-TE-NUW | CC-PC-TE-NUW | INCOMP | Veto.4 + Veto.8 |
CC-PV-TE-NUW | CC-PC-TP-UW | INCOMP | Veto.1 + Veto.2 |
CC-PV-TE-NUW | CC-PC-TP-NUW | INCOMP | Veto.4 + Veto.8 |
CC-PV-TE-NUW | DC-PV-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-NUW | DC-PV-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-NUW | DC-PV-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-NUW | DC-PV-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-NUW | DC-RPC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-NUW | DC-RPC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-NUW | DC-RPC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-NUW | DC-RPC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-NUW | DC-PC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-NUW | DC-PC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-NUW | DC-PC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TE-NUW | DC-PC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-UW | CC-PV-TP-NUW | Veto.1 | |
CC-PV-TP-UW | CC-RPC-TE-UW | INCOMP | Veto.4 + Veto.8 |
CC-PV-TP-UW | CC-RPC-TE-NUW | INCOMP | Veto.1 + Veto.8 |
CC-PV-TP-UW | CC-RPC-TP-UW | INCOMP | Veto.4 + Veto.8 |
CC-PV-TP-UW | CC-RPC-TP-NUW | INCOMP | Veto.1 + Veto.8 |
CC-PV-TP-UW | CC-PC-TE-UW | INCOMP | Veto.4 + Veto.8 |
CC-PV-TP-UW | CC-PC-TE-NUW | INCOMP | Veto.1 + Veto.8 |
CC-PV-TP-UW | CC-PC-TP-UW | INCOMP | Veto.4 + Veto.8 |
CC-PV-TP-UW | CC-PC-TP-NUW | INCOMP | Veto.1 + Veto.8 |
CC-PV-TP-UW | DC-PV-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-UW | DC-PV-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-UW | DC-PV-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-UW | DC-PV-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-UW | DC-RPC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-UW | DC-RPC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-UW | DC-RPC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-UW | DC-RPC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-UW | DC-PC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-UW | DC-PC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-UW | DC-PC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-UW | DC-PC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-NUW | CC-RPC-TE-UW | INCOMP | Veto.1 + Veto.9 |
CC-PV-TP-NUW | CC-RPC-TE-NUW | INCOMP | Veto.10 + Veto.8 |
CC-PV-TP-NUW | CC-RPC-TP-UW | INCOMP | Veto.1 + Veto.9 |
CC-PV-TP-NUW | CC-RPC-TP-NUW | INCOMP | Veto.11 + Veto.9 |
CC-PV-TP-NUW | CC-PC-TE-UW | INCOMP | Veto.1 + Veto.9 |
CC-PV-TP-NUW | CC-PC-TE-NUW | INCOMP | Veto.10 + Veto.8 |
CC-PV-TP-NUW | CC-PC-TP-UW | INCOMP | Veto.1 + Veto.9 |
CC-PV-TP-NUW | CC-PC-TP-NUW | INCOMP | Veto.12 + Veto.8 |
CC-PV-TP-NUW | DC-PV-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-NUW | DC-PV-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-NUW | DC-PV-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-NUW | DC-PV-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-NUW | DC-RPC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-NUW | DC-RPC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-NUW | DC-RPC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-NUW | DC-RPC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-NUW | DC-PC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-NUW | DC-PC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-NUW | DC-PC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PV-TP-NUW | DC-PC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-UW | CC-RPC-TE-NUW | Veto.1 | |
CC-RPC-TE-UW | CC-RPC-TP-UW | INCOMP | Veto.10 + Veto.13 |
CC-RPC-TE-UW | CC-RPC-TP-NUW | INCOMP | Veto.1 + Veto.10 |
CC-RPC-TE-UW | CC-PC-TE-UW | INCOMP | Veto.12 + Veto.14 |
CC-RPC-TE-UW | CC-PC-TE-NUW | INCOMP | Veto.1 + Veto.15 |
CC-RPC-TE-UW | CC-PC-TP-UW | INCOMP | Veto.10 + Veto.13 |
CC-RPC-TE-UW | CC-PC-TP-NUW | INCOMP | Veto.1 + Veto.10 |
CC-RPC-TE-UW | DC-PV-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-UW | DC-PV-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-UW | DC-PV-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-UW | DC-PV-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-UW | DC-RPC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-UW | DC-RPC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-UW | DC-RPC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-UW | DC-RPC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-UW | DC-PC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-UW | DC-PC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-UW | DC-PC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-UW | DC-PC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-NUW | CC-RPC-TP-UW | INCOMP | Veto.1 + Veto.13 |
CC-RPC-TE-NUW | CC-RPC-TP-NUW | INCOMP | Veto.10 + Veto.13 |
CC-RPC-TE-NUW | CC-PC-TE-UW | INCOMP | Veto.1 + Veto.14 |
CC-RPC-TE-NUW | CC-PC-TE-NUW | INCOMP | Veto.11 + Veto.15 |
CC-RPC-TE-NUW | CC-PC-TP-UW | INCOMP | Veto.1 + Veto.13 |
CC-RPC-TE-NUW | CC-PC-TP-NUW | INCOMP | Veto.10 + Veto.11 |
CC-RPC-TE-NUW | DC-PV-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-NUW | DC-PV-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-NUW | DC-PV-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-NUW | DC-PV-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-NUW | DC-RPC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-NUW | DC-RPC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-NUW | DC-RPC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-NUW | DC-RPC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-NUW | DC-PC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-NUW | DC-PC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-NUW | DC-PC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TE-NUW | DC-PC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-UW | CC-RPC-TP-NUW | Veto.1 | |
CC-RPC-TP-UW | CC-PC-TE-UW | INCOMP | Veto.10 + Veto.12 |
CC-RPC-TP-UW | CC-PC-TE-NUW | INCOMP | Veto.1 + Veto.15 |
CC-RPC-TP-UW | CC-PC-TP-UW | INCOMP | Veto.12 + Veto.14 |
CC-RPC-TP-UW | CC-PC-TP-NUW | INCOMP | Veto.1 + Veto.15 |
CC-RPC-TP-UW | DC-PV-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-UW | DC-PV-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-UW | DC-PV-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-UW | DC-PV-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-UW | DC-RPC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-UW | DC-RPC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-UW | DC-RPC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-UW | DC-RPC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-UW | DC-PC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-UW | DC-PC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-UW | DC-PC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-UW | DC-PC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-NUW | CC-PC-TE-UW | INCOMP | Veto.1 + Veto.10 |
CC-RPC-TP-NUW | CC-PC-TE-NUW | INCOMP | Veto.10 + Veto.15 |
CC-RPC-TP-NUW | CC-PC-TP-UW | INCOMP | Veto.1 + Veto.14 |
CC-RPC-TP-NUW | CC-PC-TP-NUW | INCOMP | Veto.11 + Veto.15 |
CC-RPC-TP-NUW | DC-PV-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-NUW | DC-PV-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-NUW | DC-PV-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-NUW | DC-PV-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-NUW | DC-RPC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-NUW | DC-RPC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-NUW | DC-RPC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-NUW | DC-RPC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-NUW | DC-PC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-NUW | DC-PC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-NUW | DC-PC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-RPC-TP-NUW | DC-PC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-UW | CC-PC-TE-NUW | Veto.1 | |
CC-PC-TE-UW | CC-PC-TP-UW | INCOMP | Veto.10 + Veto.13 |
CC-PC-TE-UW | CC-PC-TP-NUW | INCOMP | Veto.1 + Veto.10 |
CC-PC-TE-UW | DC-PV-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-UW | DC-PV-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-UW | DC-PV-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-UW | DC-PV-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-UW | DC-RPC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-UW | DC-RPC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-UW | DC-RPC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-UW | DC-RPC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-UW | DC-PC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-UW | DC-PC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-UW | DC-PC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-UW | DC-PC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-NUW | CC-PC-TP-UW | INCOMP | Veto.1 + Veto.16 |
CC-PC-TE-NUW | CC-PC-TP-NUW | INCOMP | Veto.10 + Veto.16 |
CC-PC-TE-NUW | DC-PV-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-NUW | DC-PV-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-NUW | DC-PV-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-NUW | DC-PV-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-NUW | DC-RPC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-NUW | DC-RPC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-NUW | DC-RPC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-NUW | DC-RPC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-NUW | DC-PC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-NUW | DC-PC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-NUW | DC-PC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TE-NUW | DC-PC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-UW | CC-PC-TP-NUW | Veto.1 | |
CC-PC-TP-UW | DC-PV-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-UW | DC-PV-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-UW | DC-PV-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-UW | DC-PV-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-UW | DC-RPC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-UW | DC-RPC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-UW | DC-RPC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-UW | DC-RPC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-UW | DC-PC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-UW | DC-PC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-UW | DC-PC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-UW | DC-PC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-NUW | DC-PV-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-NUW | DC-PV-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-NUW | DC-PV-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-NUW | DC-PV-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-NUW | DC-RPC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-NUW | DC-RPC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-NUW | DC-RPC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-NUW | DC-RPC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-NUW | DC-PC-TE-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-NUW | DC-PC-TE-NUW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-NUW | DC-PC-TP-UW | INCOMP | Veto.5 + Veto.6 |
CC-PC-TP-NUW | DC-PC-TP-NUW | INCOMP | Veto.5 + Veto.6 |
DC-PV-TE-UW | DC-PV-TE-NUW | EQ | Theorem 3.2 |
DC-PV-TE-UW | DC-PV-TP-UW | Veto.42 + Theorem 3.3 | |
DC-PV-TE-UW | DC-PV-TP-NUW | Veto.1 + Theorem 3.3 | |
DC-PV-TE-UW | DC-RPC-TE-UW | Veto.42 + Theorem 3.4 | |
DC-PV-TE-UW | DC-RPC-TE-NUW | Veto.42 + Theorem 3.4 | |
DC-PV-TE-UW | DC-RPC-TP-UW | Veto.42 + Theorem 3.4 | |
DC-PV-TE-UW | DC-RPC-TP-NUW | Veto.1 + Theorem 3.4 | |
DC-PV-TE-UW | DC-PC-TE-UW | Veto.42 + Theorem 3.4 | |
DC-PV-TE-UW | DC-PC-TE-NUW | Veto.42 + Theorem 3.4 | |
DC-PV-TE-UW | DC-PC-TP-UW | Veto.42 + Theorem 3.4 | |
DC-PV-TE-UW | DC-PC-TP-NUW | Veto.1 + Theorem 3.4 + ? (?) | |
DC-PV-TE-NUW | DC-PV-TP-UW | Veto.42 + Theorem 3.3 | |
DC-PV-TE-NUW | DC-PV-TP-NUW | Veto.1 + Theorem 3.3 | |
DC-PV-TE-NUW | DC-RPC-TE-UW | Veto.42 + Theorem 3.4 | |
DC-PV-TE-NUW | DC-RPC-TE-NUW | Veto.42 + Theorem 3.4 | |
DC-PV-TE-NUW | DC-RPC-TP-UW | Veto.42 + Theorem 3.4 | |
DC-PV-TE-NUW | DC-RPC-TP-NUW | Veto.1 + Theorem 3.4 | |
DC-PV-TE-NUW | DC-PC-TE-UW | Veto.42 + Theorem 3.4 | |
DC-PV-TE-NUW | DC-PC-TE-NUW | Veto.42 + Theorem 3.4 | |
DC-PV-TE-NUW | DC-PC-TP-UW | Veto.42 + Theorem 3.4 | |
DC-PV-TE-NUW | DC-PC-TP-NUW | Veto.1 + Theorem 3.4 + ? (?) | |
DC-PV-TP-UW | DC-PV-TP-NUW | Veto.1 | |
DC-PV-TP-UW | DC-RPC-TE-UW | INCOMP | Veto.17 + Veto.18 |
DC-PV-TP-UW | DC-RPC-TE-NUW | INCOMP | Veto.17 + Veto.18 |
DC-PV-TP-UW | DC-RPC-TP-UW | INCOMP | Veto.4 + Veto.20 |
DC-PV-TP-UW | DC-RPC-TP-NUW | INCOMP | Veto.1 + Veto.19 |
DC-PV-TP-UW | DC-PC-TE-UW | INCOMP | Veto.17 + Veto.18 |
DC-PV-TP-UW | DC-PC-TE-NUW | INCOMP | Veto.17 + Veto.18 |
DC-PV-TP-UW | DC-PC-TP-UW | INCOMP | Veto.20 + Veto.18 |
DC-PV-TP-UW | DC-PC-TP-NUW | INCOMP | Veto.1 + Veto.19 |
DC-PV-TP-NUW | DC-RPC-TE-UW | INCOMP | Veto.1 + Veto.18 |
DC-PV-TP-NUW | DC-RPC-TE-NUW | INCOMP | Veto.1 + Veto.18 |
DC-PV-TP-NUW | DC-RPC-TP-UW | INCOMP | Veto.1 + Veto.18 |
DC-PV-TP-NUW | DC-RPC-TP-NUW | INCOMP | Veto.11 + Veto.18 |
DC-PV-TP-NUW | DC-PC-TE-UW | INCOMP | Veto.1 + Veto.18 |
DC-PV-TP-NUW | DC-PC-TE-NUW | INCOMP | Veto.1 + Veto.18 |
DC-PV-TP-NUW | DC-PC-TP-UW | INCOMP | Veto.1 + Veto.18 |
DC-PV-TP-NUW | DC-PC-TP-NUW | INCOMP | Veto.11 + Veto.18 |
DC-RPC-TE-UW | DC-RPC-TE-NUW | EQ | ? (?) |
DC-RPC-TE-UW | DC-RPC-TP-UW | Veto.4 + Theorem 3.1 | |
DC-RPC-TE-UW | DC-RPC-TP-NUW | Veto.1 + Theorem 3.1 | |
DC-RPC-TE-UW | DC-PC-TE-UW | EQ | ? (?) |
DC-RPC-TE-UW | DC-PC-TE-NUW | EQ | ? (?) |
DC-RPC-TE-UW | DC-PC-TP-UW | Veto.17 + Theorem 3.1 | |
DC-RPC-TE-UW | DC-PC-TP-NUW | Veto.1 + Theorem 3.1 | |
DC-RPC-TE-NUW | DC-RPC-TP-UW | Veto.4 + Theorem 3.1 | |
DC-RPC-TE-NUW | DC-RPC-TP-NUW | Veto.1 + Theorem 3.1 | |
DC-RPC-TE-NUW | DC-PC-TE-UW | EQ | ? (?) |
DC-RPC-TE-NUW | DC-PC-TE-NUW | EQ | ? (?) |
DC-RPC-TE-NUW | DC-PC-TP-UW | Veto.17 + Theorem 3.1 | |
DC-RPC-TE-NUW | DC-PC-TP-NUW | Veto.1 + Theorem 3.1 | |
DC-RPC-TP-UW | DC-RPC-TP-NUW | Veto.1 | |
DC-RPC-TP-UW | DC-PC-TE-UW | Veto.4 + Theorem 3.1 + ? (?) | |
DC-RPC-TP-UW | DC-PC-TE-NUW | Veto.4 + Theorem 3.1 + ? (?) | |
DC-RPC-TP-UW | DC-PC-TP-UW | INCOMP | Veto.4 + Veto.43 |
DC-RPC-TP-UW | DC-PC-TP-NUW | Veto.1 + ? (?) | |
DC-RPC-TP-NUW | DC-PC-TE-UW | Veto.1 + Theorem 3.1 + ? (?) | |
DC-RPC-TP-NUW | DC-PC-TE-NUW | Veto.1 + Theorem 3.1 + ? (?) | |
DC-RPC-TP-NUW | DC-PC-TP-UW | Veto.1 + ? (?) | |
DC-RPC-TP-NUW | DC-PC-TP-NUW | EQ | ? (?) |
DC-PC-TE-UW | DC-PC-TE-NUW | EQ | ? (?) |
DC-PC-TE-UW | DC-PC-TP-UW | Veto.17 + Theorem 3.1 + ? (?) | |
DC-PC-TE-UW | DC-PC-TP-NUW | Veto.1 + Theorem 3.1 + ? (?) | |
DC-PC-TE-NUW | DC-PC-TP-UW | Veto.17 + Theorem 3.1 + ? (?) | |
DC-PC-TE-NUW | DC-PC-TP-NUW | Veto.1 + Theorem 3.1 + ? (?) | |
DC-PC-TP-UW | DC-PC-TP-NUW | Veto.1 | |
CC-AC-UW | CC-AC-NUW | Veto.22 | |
CC-AC-UW | DC-AC-UW | INCOMP | Veto.22 + Veto.24 |
CC-AC-UW | DC-AC-NUW | INCOMP | Veto.21 + Veto.23 |
CC-AC-NUW | DC-AC-UW | INCOMP∗ | Veto.26 |
CC-AC-NUW | DC-AC-NUW | INCOMP∗ | Veto.32 |
DC-AC-UW | DC-AC-NUW | Veto.22 | |
CC-DC-UW | CC-DC-NUW | Veto.25 | |
CC-DC-UW | CC-DV-UW | INCOMP | Veto.27 + Veto.30 |
CC-DC-UW | CC-DV-NUW | INCOMP | Veto.25 + Veto.31 |
CC-DC-UW | DC-DC-UW | INCOMP∗ | Veto.26 |
CC-DC-UW | DC-DC-NUW | INCOMP | Veto.25 + Veto.34 |
CC-DC-UW | DC-DV-UW | INCOMP∗ | Veto.45 |
CC-DC-UW | DC-DV-NUW | INCOMP | Veto.25 + Veto.34 |
CC-DC-NUW | CC-DV-UW | INCOMP | Veto.27 + Veto.46 |
CC-DC-NUW | CC-DV-NUW | INCOMP | Veto.35 + Veto.31 |
CC-DC-NUW | DC-DC-UW | INCOMP | Veto.25 + Veto.34 |
CC-DC-NUW | DC-DC-NUW | INCOMP | Veto.25 + Veto.34 |
CC-DC-NUW | DC-DV-UW | INCOMP | Veto.25 + Veto.34 |
CC-DC-NUW | DC-DV-NUW | INCOMP | Veto.25 + Veto.34 |
CC-DV-UW | CC-DV-NUW | Veto.27 | |
CC-DV-UW | DC-DC-UW | INCOMP∗ | Veto.45 |
CC-DV-UW | DC-DC-NUW | INCOMP | Veto.25 + Veto.28 |
CC-DV-UW | DC-DV-UW | INCOMP∗ | Veto.45 |
CC-DV-UW | DC-DV-NUW | INCOMP | Veto.25 + Veto.34 |
CC-DV-NUW | DC-DC-UW | INCOMP∗ | Veto.26 |
CC-DV-NUW | DC-DC-NUW | INCOMP | Veto.25 + Veto.34 |
CC-DV-NUW | DC-DV-UW | INCOMP∗ | Veto.26 |
CC-DV-NUW | DC-DV-NUW | INCOMP | Veto.25 + Veto.34 |
DC-DC-UW | DC-DC-NUW | Veto.27 | |
DC-DC-UW | DC-DV-UW | INCOMP | Veto.29 + Veto.31 |
DC-DC-UW | DC-DV-NUW | INCOMP | Veto.27 + Veto.33 |
DC-DC-NUW | DC-DV-UW | INCOMP | Veto.27 + Veto.31 |
DC-DC-NUW | DC-DV-NUW | INCOMP | Veto.28 + Veto.33 |
DC-DV-UW | DC-DV-NUW | Veto.27 | |
CC-AV-UW | CC-AV-NUW | Veto.44 | |
CC-AV-UW | DC-AV-UW | INCOMP | Veto.37 + Veto.38 |
CC-AV-UW | DC-AV-NUW | INCOMP | Veto.37 + Veto.38 |
CC-AV-NUW | DC-AV-UW | INCOMP | Veto.37 + Veto.38 |
CC-AV-NUW | DC-AV-NUW | INCOMP | Veto.37 + Veto.38 |
DC-AV-UW | DC-AV-NUW | Veto.36 | |
CC-UAC-UW | CC-UAC-NUW | Veto.39 | |
CC-UAC-UW | DC-UAC-UW | INCOMP | Veto.39 + Veto.40 |
CC-UAC-UW | DC-UAC-NUW | INCOMP | Veto.40 + Veto.41 |
CC-UAC-NUW | DC-UAC-UW | INCOMP | Veto.40 + Veto.41 |
CC-UAC-NUW | DC-UAC-NUW | INCOMP | Veto.39 + Veto.41 |
DC-UAC-UW | DC-UAC-NUW | Veto.39 |
ID | |||||
---|---|---|---|---|---|
Appr.1 | - | - | - | ||
Appr.2 | - | - | - | ||
Appr.3 | - | - | - | ||
Appr.4 | - | - | - | ||
Appr.5 | - | - | - | ||
Appr.6 | - | - | - | ||
Appr.7 | - | , , , , , , , , , , , , , , , , | - | - | |
Appr.8 | - | , , , , , , , , , , , | - | - | |
Appr.9 | - | , , , , , , , , , , , , , | - | - | |
Appr.10 | - | - | 0 | ||
Appr.11 | - | 1 | |||
Appr.12 | - | 1 | |||
Appr.13 | - | 1 | |||
Appr.14 | - | - | 1 | ||
Appr.15 | - | - | 1 | ||
Appr.16 | - | - | 1 | ||
Appr.17 | - | - | 1 | ||
Appr.18 | - | - | 1 | ||
Appr.19 | - | - | 1 | ||
Appr.20 | - | - | 1 | ||
Appr.21 | - | - | 2 | ||
Appr.22 | - | - | 2 | ||
Appr.23 | - | - | 1 | ||
Appr.24 | - | 1 | |||
Appr.25 | - | 1 | |||
Appr.26 | - | 1 | |||
Appr.27 | - | 0 | |||
Appr.28 | - | - | |||
Appr.29 | - | - | 0 | ||
Appr.30 | - | - | |||
Appr.31 | - | - | - | ||
Appr.32 | - | - | - |
Classification | Justification(s) | ||
---|---|---|---|
CC-PV-TE-UW | CC-PV-TE-NUW | Appr.2 | |
CC-PV-TE-UW | CC-PV-TP-UW | INCOMP | Appr.5 + Appr.31 |
CC-PV-TE-UW | CC-PV-TP-NUW | INCOMP | Appr.2 + Appr.5 |
CC-PV-TE-UW | CC-RPC-TE-UW | INCOMP | Appr.6 + Appr.9 |
CC-PV-TE-UW | CC-RPC-TE-NUW | INCOMP | Appr.2 + Appr.6 |
CC-PV-TE-UW | CC-RPC-TP-UW | Appr.5 + Corollary 3.10 | |
CC-PV-TE-UW | CC-RPC-TP-NUW | INCOMP | Appr.2 + Appr.5 |
CC-PV-TE-UW | CC-PC-TE-UW | INCOMP | Appr.6 + Appr.9 |
CC-PV-TE-UW | CC-PC-TE-NUW | INCOMP | Appr.2 + Appr.6 |
CC-PV-TE-UW | CC-PC-TP-UW | Appr.5 + Corollary 3.10 | |
CC-PV-TE-UW | CC-PC-TP-NUW | INCOMP | Appr.2 + Appr.5 |
CC-PV-TE-UW | DC-PV-TE-UW | INCOMP∗ | Appr.1 |
CC-PV-TE-UW | DC-PV-TE-NUW | INCOMP∗ | Appr.1 |
CC-PV-TE-UW | DC-PV-TP-UW | INCOMP∗ | Appr.1 |
CC-PV-TE-UW | DC-PV-TP-NUW | INCOMP∗ | Appr.1 |
CC-PV-TE-UW | DC-RPC-TE-UW | INCOMP∗ | Appr.1 |
CC-PV-TE-UW | DC-RPC-TE-NUW | INCOMP∗ | Appr.1 |
CC-PV-TE-UW | DC-RPC-TP-UW | INCOMP∗ | Appr.1 |
CC-PV-TE-UW | DC-RPC-TP-NUW | INCOMP∗ | Appr.1 |
CC-PV-TE-UW | DC-PC-TE-UW | INCOMP∗ | Appr.1 |
CC-PV-TE-UW | DC-PC-TE-NUW | INCOMP∗ | Appr.1 |
CC-PV-TE-UW | DC-PC-TP-UW | INCOMP∗ | Appr.1 |
CC-PV-TE-UW | DC-PC-TP-NUW | INCOMP∗ | Appr.1 |
CC-PV-TE-NUW | CC-PV-TP-UW | INCOMP | Appr.2 + Appr.32 |
CC-PV-TE-NUW | CC-PV-TP-NUW | INCOMP∗ | Appr.5 |
CC-PV-TE-NUW | CC-RPC-TE-UW | INCOMP | Appr.2 + Appr.9 |
CC-PV-TE-NUW | CC-RPC-TE-NUW | INCOMP | Appr.6 + Appr.5 |
CC-PV-TE-NUW | CC-RPC-TP-UW | Appr.2 + Corollary 3.10 | |
CC-PV-TE-NUW | CC-RPC-TP-NUW | INCOMP∗ | Appr.5 |
CC-PV-TE-NUW | CC-PC-TE-UW | INCOMP | Appr.2 + Appr.9 |
CC-PV-TE-NUW | CC-PC-TE-NUW | INCOMP | Appr.6 + Appr.5 |
CC-PV-TE-NUW | CC-PC-TP-UW | Appr.2 + Corollary 3.10 | |
CC-PV-TE-NUW | CC-PC-TP-NUW | INCOMP∗ | Appr.5 |
CC-PV-TE-NUW | DC-PV-TE-UW | INCOMP∗ | Appr.1 |
CC-PV-TE-NUW | DC-PV-TE-NUW | INCOMP∗ | Appr.1 |
CC-PV-TE-NUW | DC-PV-TP-UW | INCOMP∗ | Appr.1 |
CC-PV-TE-NUW | DC-PV-TP-NUW | INCOMP∗ | Appr.1 |
CC-PV-TE-NUW | DC-RPC-TE-UW | INCOMP∗ | Appr.1 |
CC-PV-TE-NUW | DC-RPC-TE-NUW | INCOMP∗ | Appr.1 |
CC-PV-TE-NUW | DC-RPC-TP-UW | INCOMP∗ | Appr.1 |
CC-PV-TE-NUW | DC-RPC-TP-NUW | INCOMP∗ | Appr.1 |
CC-PV-TE-NUW | DC-PC-TE-UW | INCOMP∗ | Appr.1 |
CC-PV-TE-NUW | DC-PC-TE-NUW | INCOMP∗ | Appr.1 |
CC-PV-TE-NUW | DC-PC-TP-UW | INCOMP∗ | Appr.1 |
CC-PV-TE-NUW | DC-PC-TP-NUW | INCOMP∗ | Appr.1 |
CC-PV-TP-UW | CC-PV-TP-NUW | Appr.2 | |
CC-PV-TP-UW | CC-RPC-TE-UW | INCOMP | Appr.5 + Appr.8 |
CC-PV-TP-UW | CC-RPC-TE-NUW | INCOMP | Appr.2 + Appr.8 |
CC-PV-TP-UW | CC-RPC-TP-UW | Appr.7 + Corollary 3.10 | |
CC-PV-TP-UW | CC-RPC-TP-NUW | INCOMP | Appr.2 + Appr.8 |
CC-PV-TP-UW | CC-PC-TE-UW | INCOMP | Appr.5 + Appr.8 |
CC-PV-TP-UW | CC-PC-TE-NUW | INCOMP | Appr.2 + Appr.8 |
CC-PV-TP-UW | CC-PC-TP-UW | Appr.7 + Corollary 3.10 | |
CC-PV-TP-UW | CC-PC-TP-NUW | INCOMP | Appr.2 + Appr.8 |
CC-PV-TP-UW | DC-PV-TE-UW | INCOMP∗ | Appr.1 |
CC-PV-TP-UW | DC-PV-TE-NUW | INCOMP∗ | Appr.1 |
CC-PV-TP-UW | DC-PV-TP-UW | INCOMP∗ | Appr.1 |
CC-PV-TP-UW | DC-PV-TP-NUW | INCOMP∗ | Appr.1 |
CC-PV-TP-UW | DC-RPC-TE-UW | INCOMP∗ | Appr.1 |
CC-PV-TP-UW | DC-RPC-TE-NUW | INCOMP∗ | Appr.1 |
CC-PV-TP-UW | DC-RPC-TP-UW | INCOMP∗ | Appr.1 |
CC-PV-TP-UW | DC-RPC-TP-NUW | INCOMP∗ | Appr.1 |
CC-PV-TP-UW | DC-PC-TE-UW | INCOMP∗ | Appr.1 |
CC-PV-TP-UW | DC-PC-TE-NUW | INCOMP∗ | Appr.1 |
CC-PV-TP-UW | DC-PC-TP-UW | INCOMP∗ | Appr.1 |
CC-PV-TP-UW | DC-PC-TP-NUW | INCOMP∗ | Appr.1 |
CC-PV-TP-NUW | CC-RPC-TE-UW | INCOMP | Appr.2 + Appr.5 |
CC-PV-TP-NUW | CC-RPC-TE-NUW | INCOMP | Appr.5 + Appr.8 |
CC-PV-TP-NUW | CC-RPC-TP-UW | Appr.2 + Corollary 3.10 | |
CC-PV-TP-NUW | CC-RPC-TP-NUW | Appr.7 + Corollary 3.15 | |
CC-PV-TP-NUW | CC-PC-TE-UW | INCOMP | Appr.2 + Appr.5 |
CC-PV-TP-NUW | CC-PC-TE-NUW | INCOMP | Appr.5 + Appr.8 |
CC-PV-TP-NUW | CC-PC-TP-UW | Appr.2 + Corollary 3.10 | |
CC-PV-TP-NUW | CC-PC-TP-NUW | Appr.7 + Corollary 3.15 | |
CC-PV-TP-NUW | DC-PV-TE-UW | INCOMP∗ | Appr.1 |
CC-PV-TP-NUW | DC-PV-TE-NUW | INCOMP∗ | Appr.1 |
CC-PV-TP-NUW | DC-PV-TP-UW | INCOMP∗ | Appr.1 |
CC-PV-TP-NUW | DC-PV-TP-NUW | INCOMP∗ | Appr.1 |
CC-PV-TP-NUW | DC-RPC-TE-UW | INCOMP∗ | Appr.1 |
CC-PV-TP-NUW | DC-RPC-TE-NUW | INCOMP∗ | Appr.1 |
CC-PV-TP-NUW | DC-RPC-TP-UW | INCOMP∗ | Appr.1 |
CC-PV-TP-NUW | DC-RPC-TP-NUW | INCOMP∗ | Appr.1 |
CC-PV-TP-NUW | DC-PC-TE-UW | INCOMP∗ | Appr.1 |
CC-PV-TP-NUW | DC-PC-TE-NUW | INCOMP∗ | Appr.1 |
CC-PV-TP-NUW | DC-PC-TP-UW | INCOMP∗ | Appr.1 |
CC-PV-TP-NUW | DC-PC-TP-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TE-UW | CC-RPC-TE-NUW | Appr.2 | |
CC-RPC-TE-UW | CC-RPC-TP-UW | Appr.5 + Corollary 3.10 | |
CC-RPC-TE-UW | CC-RPC-TP-NUW | INCOMP | Appr.2 + Appr.5 |
CC-RPC-TE-UW | CC-PC-TE-UW | EQ | Corollary 3.18 |
CC-RPC-TE-UW | CC-PC-TE-NUW | Appr.2 | |
CC-RPC-TE-UW | CC-PC-TP-UW | Appr.5 + Corollary 3.10 | |
CC-RPC-TE-UW | CC-PC-TP-NUW | INCOMP | Appr.2 + Appr.5 |
CC-RPC-TE-UW | DC-PV-TE-UW | INCOMP∗ | Appr.1 |
CC-RPC-TE-UW | DC-PV-TE-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TE-UW | DC-PV-TP-UW | INCOMP∗ | Appr.1 |
CC-RPC-TE-UW | DC-PV-TP-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TE-UW | DC-RPC-TE-UW | INCOMP∗ | Appr.1 |
CC-RPC-TE-UW | DC-RPC-TE-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TE-UW | DC-RPC-TP-UW | INCOMP∗ | Appr.1 |
CC-RPC-TE-UW | DC-RPC-TP-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TE-UW | DC-PC-TE-UW | INCOMP∗ | Appr.1 |
CC-RPC-TE-UW | DC-PC-TE-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TE-UW | DC-PC-TP-UW | INCOMP∗ | Appr.1 |
CC-RPC-TE-UW | DC-PC-TP-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TE-NUW | CC-RPC-TP-UW | Appr.2 + Corollary 3.10 | |
CC-RPC-TE-NUW | CC-RPC-TP-NUW | Appr.5 + Corollary 3.15 | |
CC-RPC-TE-NUW | CC-PC-TE-UW | Appr.2 | |
CC-RPC-TE-NUW | CC-PC-TE-NUW | EQ | Theorem 3.17 |
CC-RPC-TE-NUW | CC-PC-TP-UW | Appr.2 + Corollary 3.10 | |
CC-RPC-TE-NUW | CC-PC-TP-NUW | Appr.5 + Corollary 3.15 | |
CC-RPC-TE-NUW | DC-PV-TE-UW | INCOMP∗ | Appr.1 |
CC-RPC-TE-NUW | DC-PV-TE-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TE-NUW | DC-PV-TP-UW | INCOMP∗ | Appr.1 |
CC-RPC-TE-NUW | DC-PV-TP-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TE-NUW | DC-RPC-TE-UW | INCOMP∗ | Appr.1 |
CC-RPC-TE-NUW | DC-RPC-TE-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TE-NUW | DC-RPC-TP-UW | INCOMP∗ | Appr.1 |
CC-RPC-TE-NUW | DC-RPC-TP-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TE-NUW | DC-PC-TE-UW | INCOMP∗ | Appr.1 |
CC-RPC-TE-NUW | DC-PC-TE-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TE-NUW | DC-PC-TP-UW | INCOMP∗ | Appr.1 |
CC-RPC-TE-NUW | DC-PC-TP-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TP-UW | CC-RPC-TP-NUW | Appr.2 | |
CC-RPC-TP-UW | CC-PC-TE-UW | Appr.5 + Corollary 3.10 | |
CC-RPC-TP-UW | CC-PC-TE-NUW | Appr.2 + Corollary 3.10 | |
CC-RPC-TP-UW | CC-PC-TP-UW | EQ | Corollary 3.11 |
CC-RPC-TP-UW | CC-PC-TP-NUW | Appr.2 | |
CC-RPC-TP-UW | DC-PV-TE-UW | INCOMP∗ | Appr.1 |
CC-RPC-TP-UW | DC-PV-TE-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TP-UW | DC-PV-TP-UW | INCOMP∗ | Appr.1 |
CC-RPC-TP-UW | DC-PV-TP-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TP-UW | DC-RPC-TE-UW | INCOMP∗ | Appr.1 |
CC-RPC-TP-UW | DC-RPC-TE-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TP-UW | DC-RPC-TP-UW | INCOMP∗ | Appr.1 |
CC-RPC-TP-UW | DC-RPC-TP-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TP-UW | DC-PC-TE-UW | INCOMP∗ | Appr.1 |
CC-RPC-TP-UW | DC-PC-TE-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TP-UW | DC-PC-TP-UW | INCOMP∗ | Appr.1 |
CC-RPC-TP-UW | DC-PC-TP-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TP-NUW | CC-PC-TE-UW | INCOMP | Appr.2 + Appr.5 |
CC-RPC-TP-NUW | CC-PC-TE-NUW | Appr.5 + Corollary 3.15 | |
CC-RPC-TP-NUW | CC-PC-TP-UW | Appr.2 + Corollary 3.15 | |
CC-RPC-TP-NUW | CC-PC-TP-NUW | EQ | Corollary 3.11 |
CC-RPC-TP-NUW | DC-PV-TE-UW | INCOMP∗ | Appr.1 |
CC-RPC-TP-NUW | DC-PV-TE-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TP-NUW | DC-PV-TP-UW | INCOMP∗ | Appr.1 |
CC-RPC-TP-NUW | DC-PV-TP-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TP-NUW | DC-RPC-TE-UW | INCOMP∗ | Appr.1 |
CC-RPC-TP-NUW | DC-RPC-TE-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TP-NUW | DC-RPC-TP-UW | INCOMP∗ | Appr.1 |
CC-RPC-TP-NUW | DC-RPC-TP-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TP-NUW | DC-PC-TE-UW | INCOMP∗ | Appr.1 |
CC-RPC-TP-NUW | DC-PC-TE-NUW | INCOMP∗ | Appr.1 |
CC-RPC-TP-NUW | DC-PC-TP-UW | INCOMP∗ | Appr.1 |
CC-RPC-TP-NUW | DC-PC-TP-NUW | INCOMP∗ | Appr.1 |
CC-PC-TE-UW | CC-PC-TE-NUW | Appr.2 | |
CC-PC-TE-UW | CC-PC-TP-UW | Appr.5 + Corollary 3.10 | |
CC-PC-TE-UW | CC-PC-TP-NUW | INCOMP | Appr.2 + Appr.5 |
CC-PC-TE-UW | DC-PV-TE-UW | INCOMP∗ | Appr.1 |
CC-PC-TE-UW | DC-PV-TE-NUW | INCOMP∗ | Appr.1 |
CC-PC-TE-UW | DC-PV-TP-UW | INCOMP∗ | Appr.1 |
CC-PC-TE-UW | DC-PV-TP-NUW | INCOMP∗ | Appr.1 |
CC-PC-TE-UW | DC-RPC-TE-UW | INCOMP∗ | Appr.1 |
CC-PC-TE-UW | DC-RPC-TE-NUW | INCOMP∗ | Appr.1 |
CC-PC-TE-UW | DC-RPC-TP-UW | INCOMP∗ | Appr.1 |
CC-PC-TE-UW | DC-RPC-TP-NUW | INCOMP∗ | Appr.1 |
CC-PC-TE-UW | DC-PC-TE-UW | INCOMP∗ | Appr.1 |
CC-PC-TE-UW | DC-PC-TE-NUW | INCOMP∗ | Appr.1 |
CC-PC-TE-UW | DC-PC-TP-UW | INCOMP∗ | Appr.1 |
CC-PC-TE-UW | DC-PC-TP-NUW | INCOMP∗ | Appr.1 |
CC-PC-TE-NUW | CC-PC-TP-UW | Appr.2 + Corollary 3.10 | |
CC-PC-TE-NUW | CC-PC-TP-NUW | Appr.5 + Corollary 3.15 | |
CC-PC-TE-NUW | DC-PV-TE-UW | INCOMP∗ | Appr.1 |
CC-PC-TE-NUW | DC-PV-TE-NUW | INCOMP∗ | Appr.1 |
CC-PC-TE-NUW | DC-PV-TP-UW | INCOMP∗ | Appr.1 |
CC-PC-TE-NUW | DC-PV-TP-NUW | INCOMP∗ | Appr.1 |
CC-PC-TE-NUW | DC-RPC-TE-UW | INCOMP∗ | Appr.1 |
CC-PC-TE-NUW | DC-RPC-TE-NUW | INCOMP∗ | Appr.1 |
CC-PC-TE-NUW | DC-RPC-TP-UW | INCOMP∗ | Appr.1 |
CC-PC-TE-NUW | DC-RPC-TP-NUW | INCOMP∗ | Appr.1 |
CC-PC-TE-NUW | DC-PC-TE-UW | INCOMP∗ | Appr.1 |
CC-PC-TE-NUW | DC-PC-TE-NUW | INCOMP∗ | Appr.1 |
CC-PC-TE-NUW | DC-PC-TP-UW | INCOMP∗ | Appr.1 |
CC-PC-TE-NUW | DC-PC-TP-NUW | INCOMP∗ | Appr.1 |
CC-PC-TP-UW | CC-PC-TP-NUW | Appr.2 | |
CC-PC-TP-UW | DC-PV-TE-UW | INCOMP∗ | Appr.1 |
CC-PC-TP-UW | DC-PV-TE-NUW | INCOMP∗ | Appr.1 |
CC-PC-TP-UW | DC-PV-TP-UW | INCOMP∗ | Appr.1 |
CC-PC-TP-UW | DC-PV-TP-NUW | INCOMP∗ | Appr.1 |
CC-PC-TP-UW | DC-RPC-TE-UW | INCOMP∗ | Appr.1 |
CC-PC-TP-UW | DC-RPC-TE-NUW | INCOMP∗ | Appr.1 |
CC-PC-TP-UW | DC-RPC-TP-UW | INCOMP∗ | Appr.1 |
CC-PC-TP-UW | DC-RPC-TP-NUW | INCOMP∗ | Appr.1 |
CC-PC-TP-UW | DC-PC-TE-UW | INCOMP∗ | Appr.1 |
CC-PC-TP-UW | DC-PC-TE-NUW | INCOMP∗ | Appr.1 |
CC-PC-TP-UW | DC-PC-TP-UW | INCOMP∗ | Appr.1 |
CC-PC-TP-UW | DC-PC-TP-NUW | INCOMP∗ | Appr.1 |
CC-PC-TP-NUW | DC-PV-TE-UW | INCOMP∗ | Appr.1 |
CC-PC-TP-NUW | DC-PV-TE-NUW | INCOMP∗ | Appr.1 |
CC-PC-TP-NUW | DC-PV-TP-UW | INCOMP∗ | Appr.1 |
CC-PC-TP-NUW | DC-PV-TP-NUW | INCOMP∗ | Appr.1 |
CC-PC-TP-NUW | DC-RPC-TE-UW | INCOMP∗ | Appr.1 |
CC-PC-TP-NUW | DC-RPC-TE-NUW | INCOMP∗ | Appr.1 |
CC-PC-TP-NUW | DC-RPC-TP-UW | INCOMP∗ | Appr.1 |
CC-PC-TP-NUW | DC-RPC-TP-NUW | INCOMP∗ | Appr.1 |
CC-PC-TP-NUW | DC-PC-TE-UW | INCOMP∗ | Appr.1 |
CC-PC-TP-NUW | DC-PC-TE-NUW | INCOMP∗ | Appr.1 |
CC-PC-TP-NUW | DC-PC-TP-UW | INCOMP∗ | Appr.1 |
CC-PC-TP-NUW | DC-PC-TP-NUW | INCOMP∗ | Appr.1 |
DC-PV-TE-UW | DC-PV-TE-NUW | EQ | Theorem 3.16 |
DC-PV-TE-UW | DC-PV-TP-UW | Appr.3 + Theorem 3.19 | |
DC-PV-TE-UW | DC-PV-TP-NUW | Appr.2 + Theorem 3.19 | |
DC-PV-TE-UW | DC-RPC-TE-UW | Appr.3 + Corollary 3.11 + Corollary 3.21 | |
DC-PV-TE-UW | DC-RPC-TE-NUW | Appr.3 + Corollary 3.21 | |
DC-PV-TE-UW | DC-RPC-TP-UW | Appr.3 + Theorem 3.12 + Corollaries 3.11 and 3.21 | |
DC-PV-TE-UW | DC-RPC-TP-NUW | Appr.2 + Corollary 3.21 + Corollary 3.11 | |
DC-PV-TE-UW | DC-PC-TE-UW | Appr.3 + Corollary 3.11 + Corollary 3.21 | |
DC-PV-TE-UW | DC-PC-TE-NUW | Appr.3 + Corollary 3.11 + Corollary 3.21 | |
DC-PV-TE-UW | DC-PC-TP-UW | Appr.3 + Corollary 3.11 + Corollary 3.21 | |
DC-PV-TE-UW | DC-PC-TP-NUW | Appr.2 + Corollary 3.21 + Corollary 3.11 | |
DC-PV-TE-NUW | DC-PV-TP-UW | Appr.3 + Theorem 3.19 | |
DC-PV-TE-NUW | DC-PV-TP-NUW | Appr.2 + Theorem 3.19 | |
DC-PV-TE-NUW | DC-RPC-TE-UW | Appr.3 + Corollary 3.21 + Corollary 3.11 | |
DC-PV-TE-NUW | DC-RPC-TE-NUW | Appr.3 + Corollary 3.21 | |
DC-PV-TE-NUW | DC-RPC-TP-UW | Appr.3 + Corollaries 3.11 and 3.21 + Theorem 3.12 | |
DC-PV-TE-NUW | DC-RPC-TP-NUW | Appr.2 + Corollary 3.21 + Corollary 3.11 | |
DC-PV-TE-NUW | DC-PC-TE-UW | Appr.3 + Corollary 3.21 + Corollary 3.11 | |
DC-PV-TE-NUW | DC-PC-TE-NUW | Appr.3 + Corollary 3.21 + Corollary 3.11 | |
DC-PV-TE-NUW | DC-PC-TP-UW | Appr.3 + Corollary 3.21 + Corollary 3.11 | |
DC-PV-TE-NUW | DC-PC-TP-NUW | Appr.2 + Corollary 3.21 + Corollary 3.11 | |
DC-PV-TP-UW | DC-PV-TP-NUW | Appr.2 | |
DC-PV-TP-UW | DC-RPC-TE-UW | Appr.4 + Theorem 3.20 + Corollary 3.11 | |
DC-PV-TP-UW | DC-RPC-TE-NUW | Appr.4 + Theorem 3.20 | |
DC-PV-TP-UW | DC-RPC-TP-UW | Appr.4 + Theorems 3.12 and 3.20 + Corollary 3.11 | |
DC-PV-TP-UW | DC-RPC-TP-NUW | Appr.2 + Corollary 3.15 | |
DC-PV-TP-UW | DC-PC-TE-UW | Appr.4 + Theorem 3.20 + Corollary 3.11 | |
DC-PV-TP-UW | DC-PC-TE-NUW | Appr.4 + Theorem 3.20 + Corollary 3.11 | |
DC-PV-TP-UW | DC-PC-TP-UW | Appr.4 + Theorem 3.20 + Corollary 3.11 | |
DC-PV-TP-UW | DC-PC-TP-NUW | Appr.2 + Corollary 3.15 | |
DC-PV-TP-NUW | DC-RPC-TE-UW | INCOMP | Appr.2 + Appr.8 |
DC-PV-TP-NUW | DC-RPC-TE-NUW | INCOMP | Appr.2 + Appr.8 |
DC-PV-TP-NUW | DC-RPC-TP-UW | INCOMP | Appr.2 + Appr.8 |
DC-PV-TP-NUW | DC-RPC-TP-NUW | Appr.4 + Theorem 3.1 + Theorem 3.20 | |
DC-PV-TP-NUW | DC-PC-TE-UW | INCOMP | Appr.2 + Appr.8 |
DC-PV-TP-NUW | DC-PC-TE-NUW | INCOMP | Appr.2 + Appr.8 |
DC-PV-TP-NUW | DC-PC-TP-UW | INCOMP | Appr.2 + Appr.8 |
DC-PV-TP-NUW | DC-PC-TP-NUW | Appr.4 + Theorem 3.1 + Theorem 3.20 | |
DC-RPC-TE-UW | DC-RPC-TE-NUW | EQ | Corollary 3.11 |
DC-RPC-TE-UW | DC-RPC-TP-UW | EQ | Corollary 3.11 + Corollary 3.11 |
DC-RPC-TE-UW | DC-RPC-TP-NUW | Appr.2 + Theorem 3.1 | |
DC-RPC-TE-UW | DC-PC-TE-UW | EQ | Corollary 3.11 |
DC-RPC-TE-UW | DC-PC-TE-NUW | EQ | Corollary 3.11 |
DC-RPC-TE-UW | DC-PC-TP-UW | EQ | Corollary 3.11 + Corollary 3.11 |
DC-RPC-TE-UW | DC-PC-TP-NUW | Appr.2 + Theorem 3.1 | |
DC-RPC-TE-NUW | DC-RPC-TP-UW | EQ | Corollary 3.11 |
DC-RPC-TE-NUW | DC-RPC-TP-NUW | Appr.2 + Theorem 3.1 | |
DC-RPC-TE-NUW | DC-PC-TE-UW | EQ | Corollary 3.11 |
DC-RPC-TE-NUW | DC-PC-TE-NUW | EQ | Corollary 3.11 |
DC-RPC-TE-NUW | DC-PC-TP-UW | EQ | Corollary 3.11 |
DC-RPC-TE-NUW | DC-PC-TP-NUW | Appr.2 + Theorem 3.1 | |
DC-RPC-TP-UW | DC-RPC-TP-NUW | Appr.2 | |
DC-RPC-TP-UW | DC-PC-TE-UW | EQ | Corollary 3.11 + Theorem 3.12 |
DC-RPC-TP-UW | DC-PC-TE-NUW | EQ | Corollary 3.11 + Theorem 3.12 |
DC-RPC-TP-UW | DC-PC-TP-UW | EQ | Theorem 3.12 |
DC-RPC-TP-UW | DC-PC-TP-NUW | Appr.2 + Theorems 3.1 and 3.12 + Corollary 3.11 | |
DC-RPC-TP-NUW | DC-PC-TE-UW | Appr.2 + Theorem 3.1 + Corollary 3.11 | |
DC-RPC-TP-NUW | DC-PC-TE-NUW | Appr.2 + Theorem 3.1 + Corollary 3.11 | |
DC-RPC-TP-NUW | DC-PC-TP-UW | Appr.2 + Theorem 3.1 + Corollary 3.11 | |
DC-RPC-TP-NUW | DC-PC-TP-NUW | EQ | Corollary 3.11 |
DC-PC-TE-UW | DC-PC-TE-NUW | EQ | Corollary 3.11 |
DC-PC-TE-UW | DC-PC-TP-UW | EQ | Corollary 3.11 + Corollary 3.11 |
DC-PC-TE-UW | DC-PC-TP-NUW | Appr.2 + Theorem 3.1 + Corollary 3.11 | |
DC-PC-TE-NUW | DC-PC-TP-UW | EQ | Corollary 3.11 + Corollary 3.11 |
DC-PC-TE-NUW | DC-PC-TP-NUW | Appr.2 + Theorem 3.1 + Corollary 3.11 | |
DC-PC-TP-UW | DC-PC-TP-NUW | Appr.2 | |
CC-AC-UW | CC-AC-NUW | Appr.11 | |
CC-AC-UW | DC-AC-UW | INCOMP | Appr.13 + Appr.11 |
CC-AC-UW | DC-AC-NUW | INCOMP | Appr.13 + Appr.12 |
CC-AC-NUW | DC-AC-UW | INCOMP | Appr.13 + Appr.12 |
CC-AC-NUW | DC-AC-NUW | INCOMP | Appr.13 + Appr.12 |
DC-AC-UW | DC-AC-NUW | Appr.11 | |
CC-DC-UW | CC-DC-NUW | Appr.14 | |
CC-DC-UW | CC-DV-UW | INCOMP | Appr.15 + Appr.19 |
CC-DC-UW | CC-DV-NUW | INCOMP | Appr.20 + Appr.14 |
CC-DC-UW | DC-DC-UW | INCOMP | Appr.23 + Appr.14 |
CC-DC-UW | DC-DC-NUW | INCOMP∗ | Appr.10 |
CC-DC-UW | DC-DV-UW | INCOMP | Appr.23 + Appr.14 |
CC-DC-UW | DC-DV-NUW | INCOMP∗ | Appr.10 |
CC-DC-NUW | CC-DV-UW | INCOMP | Appr.14 + Appr.21 |
CC-DC-NUW | CC-DV-NUW | INCOMP | Appr.16 + Appr.20 |
CC-DC-NUW | DC-DC-UW | INCOMP | Appr.23 + Appr.16 |
CC-DC-NUW | DC-DC-NUW | INCOMP∗ | Appr.29 |
CC-DC-NUW | DC-DV-UW | INCOMP∗ | Appr.29 |
CC-DC-NUW | DC-DV-NUW | INCOMP∗ | Appr.29 |
CC-DV-UW | CC-DV-NUW | Appr.14 | |
CC-DV-UW | DC-DC-UW | INCOMP | Appr.23 + Appr.14 |
CC-DV-UW | DC-DC-NUW | INCOMP | Appr.23 + Appr.16 |
CC-DV-UW | DC-DV-UW | INCOMP | Appr.23 + Appr.14 |
CC-DV-UW | DC-DV-NUW | INCOMP | Appr.23 + Appr.16 |
CC-DV-NUW | DC-DC-UW | INCOMP | Appr.23 + Appr.17 |
CC-DV-NUW | DC-DC-NUW | INCOMP∗ | Appr.29 |
CC-DV-NUW | DC-DV-UW | INCOMP | Appr.23 + Appr.17 |
CC-DV-NUW | DC-DV-NUW | INCOMP∗ | Appr.29 |
DC-DC-UW | DC-DC-NUW | Appr.14 | |
DC-DC-UW | DC-DV-UW | Theorem 3.7 + Appr.18 | |
DC-DC-UW | DC-DV-NUW | INCOMP | Appr.14 + Appr.22 |
DC-DC-NUW | DC-DV-UW | Theorem 3.7 + Appr.18 | |
DC-DC-NUW | DC-DV-NUW | Theorem 3.8 + Appr.19 | |
DC-DV-UW | DC-DV-NUW | Appr.14 | |
CC-AV-UW | CC-AV-NUW | Appr.24 | |
CC-AV-UW | DC-AV-UW | INCOMP | Appr.25 + Appr.24 |
CC-AV-UW | DC-AV-NUW | INCOMP | Appr.25 + Appr.24 |
CC-AV-NUW | DC-AV-UW | INCOMP | Appr.25 + Appr.26 |
CC-AV-NUW | DC-AV-NUW | INCOMP | Appr.25 + Appr.26 |
DC-AV-UW | DC-AV-NUW | Appr.27 | |
CC-UAC-UW | CC-UAC-NUW | Appr.30 | |
CC-UAC-UW | DC-UAC-UW | INCOMP | Appr.28 + Appr.24 |
CC-UAC-UW | DC-UAC-NUW | INCOMP | Appr.28 + Appr.24 |
CC-UAC-NUW | DC-UAC-UW | INCOMP | Appr.28 + Appr.24 |
CC-UAC-NUW | DC-UAC-NUW | INCOMP | Appr.28 + Appr.24 |
DC-UAC-UW | DC-UAC-NUW | Appr.30 |