Unfortunately, as Paul K has pointed out, the pairwise matrix is "lossy", as you can never retrieve the actual ballots from it. Whether the voting method itself actually uses this data or not, people who want to see how everyone actually voted, and possibly do various statistical analysis on it, are limited in what they can do because they cannot see all the data.
Since I am now exploring methods that rely directly on ballot data, rather than on the matrix, I especially interested in finding a convenient non-lossy way to compress the ballot data. This compression will not only make it convenient to pass the data around (such as delivering it to a client side _javascript_ application), it can also potentially make it much more efficient to batch process.
So lets say I have the following ballot data:
A>B>C=D
A>C=D>B
D>B
A>B>C=D
D>B
Since there are two pairs of identical ballots, this can obviously be compressed into
2: A>B>C=D
1: A>C=D>B
2: D>B
As the number of ballots becomes large (say, in the thousands or tens of thousands), this becomes quite significant. Given N candidates, there is a fixed number of possible unique ballots, capping the quantity of data. It will still be more data than the pairwise matrix, but far less than having to store each ballot as a separate piece of data.
My question is, what is this number? I'm sure I could work it out but I'm sure someone has already done it....
Thanks,
-rob
---- election-methods mailing list - see http://electorama.com/em for list info
