Re: Bar code choice

From: David Mertz <voting-project_at_gnosis_dot_cx>
Date: Fri Sep 12 2003 - 17:15:59 CDT

Jan Karrman <> wrote:
|It should be easy to write a Python program that fills in the
|proper text on the ballot. I can give it a shot, but I have to
|learn Python first...

There is an additional requirement (discussed and agreed earlier) that
is not reflected in Jan's otherwise quite excellent samples. In order
to prevent easy visual identification of cast votes via the barcodes, we
will pad the position of actual vote data by a random amount, per ballot.

It looks like Jan's sample encodes about 36 digits of information. We
can probably pad that within the size of the ballot to 60 or 70 digits.
The first two digits will simply indicate the offset to get to the
real data. So, for example, Jan's data is:


Two different voters who vote identically will have on their ballot
distinct encoded strings, such as:




(or rather, the barcode version of these).

Where the 'd's are random decimal digits. I am confident that that is
sufficient to prevent elections workers who see numerous exposed edges
during a day from beginning to recognize vote patterns.

Would one of the Python programmers on the list please volunteer to work
with Jan in producing the ballot page generation software to match his
sample? I guess Jan's plan is to work with postscript, and then the
actual printing will be done with 'gs'--which seems fine to me.

Yours, David...

mertz@  | The specter of free information is haunting the `Net!  All the
gnosis  | powers of IP- and crypto-tyranny have entered into an unholy
.cx     | alliance...ideas have nothing to lose but their chains.  Unite
        | against "intellectual property" and anti-privacy regimes!
= The content of this message, with the exception of any external 
= quotations under fair use, are released to the Public Domain    
Received on Tue Sep 30 23:17:03 2003

This archive was generated by hypermail 2.1.8 : Tue Sep 30 2003 - 23:17:09 CDT