Ballot structure

[Michael Zolotarev <michael.zolotarev@baltimore.com>]

> 
> As for defining "ballot", there seems to be some consistency and some 
> differences among our views. A ballot would look something like ....
> 
> - ballot (begin)
>      - contest 1
>          - option 1A
>          - option 1B
>          - option 1C
>      - contest 2
>          - option 2A
>          - option 2B
>      - contest 3
>          - option 3A
>          - option 3B
>          - option 3C
>          - option 3D
> - ballot (end)
> 
> (+) A "ballot" contains one or more "contests".
> (+) With each "contest", either an "office" or an "issue" is 
> being contested.
> (+) Each "contest" offers a voter one or more "options" 
> (usually two or 
> more, when at least two options are available).
> (+) Each "option" listed where an "office" is being contested 
> would contain 
> a "candidate".
> (+) The "options" listed where an "issue" is being contested would 
> generally be "for" or "against" (or synonyms of these).
> (+) The voter is allowed one or more "selections" (i.e. 
> votes) per "contest".
> 

i'd suggest adding a header which defines, at least, the version, the
"election compain ID", and the "target/audience".


-----------------------------------------------------------------------------------------------------------------
The information contained in this message is confidential and is intended 
for the addressee(s) only.  If you have received this message in error or 
there are any problems please notify the originator immediately.  The 
unauthorized use, disclosure, copying or alteration of this message is 
strictly forbidden. Baltimore Technologies plc will not be liable for direct, 
special, indirect or consequential damages arising from alteration of the 
contents of this message by a third party or as a result of any virus being 
passed on.

In addition, certain Marketing collateral may be added from time to time to 
promote Baltimore Technologies products, services, Global e-Security or 
appearance at trade shows and conferences.
 
This footnote confirms that this email message has been swept by 
Baltimore MIMEsweeper for Content Security threats, including
computer viruses.