MeetingOneIn.xml

From Scantegrity Wiki

Due to a bug in our wiki, the code does not wrap. Until then, please view this page as "Printable." This can be done by clicking here (or by pressing CTRL p).

<< Back to Audit Specification

Contents 1 Sample file 2 Schema 3 Notes 4 Audit Steps

Sample file

<xml>
	<electionSpec>D:\PunchScan2.0\PunchScan2.0\Elections\SampleScantegrityII\public\ElectionSpec.xml</electionSpec>
	<noBallots>20</noBallots>
	<noDs>2</noDs>
	<constant>UHJpbmNldG9uRWxlY3Rpbw==</constant>
	<partitions>D:\PunchScan2.0\PunchScan2.0\Elections\SampleScantegrityII\public\partitions.xml</partitions>
</xml>

Schema

• element electionSpec

This element defines a path to ElectionSpec.xml.

• element partitions

This element defines a path to partitions.xml

• element noBallots

This element defines the number of ballots in the election. This should be greater than the voting age population to account for print audits and spoiled ballots.

• element noDs

This element refers to the security parameter of the system, which are defined as independent D-tables. In future files, each table will be given an element name of instance.

• element constant

TBD

Notes

Unlike in many E2E voting systems, Scantegrity requires the number of ballots to be fixed prior to the election. This is because the information is mixed prior to the election.

Audit Steps

Assuming this file has just become available, what audits are now possible using this file and previous files?

There are no audits necessary at this stage.