election-services message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [election-services] RE: Enhancing Referendum items handling
- From: "David RR Webber \(XML\)" <david@drrw.info>
- To: Paul Spencer <paul.spencer@boynings.co.uk>
- Date: Thu, 24 May 2007 09:17:52 -0700
Paul,
Followup note here - I've put together an XML example to illustrate the concepts in action here!
Fragment below for an EML 510 shows how the new structure works for recording count totals for regular candidate and then referendum items - so you can see how this fits into the existing paradigm.
Thanks, DW
"The way to be is to do" - Confucius (551-472 B.C.)
Existing structure:
<Selection>
<CandidateIdentifier Id="133" DisplayOrder="573" />
</Candidate>
<ValidVotes>17</ValidVotes>
</Selection>
<CandidateIdentifier Id="143" DisplayOrder="574" />
</Candidate>
<ValidVotes>12</ValidVotes>
</Selection>
</ReportingUnitVotes>
</Contest>
New referendum ProposalItem capable approach:
<ContestIdentifier Id="19000000001A" />
<ProposalItem ReferendumOptionIdentifier="19000000001A-YES" />
</Candidate>
<ValidVotes>6400587</ValidVotes>
</Selection>
<ProposalItem ReferendumOptionIdentifier="19000000001A-NO" />
</Candidate>
<ValidVotes>1916925</ValidVotes>
</Selection>
</TotalVotes>
</Contest>
<ContestIdentifier Id="19000000001B" />
<ProposalItem ReferendumOptionIdentifier="19000000001B-YES" />
</Candidate>
<ValidVotes>5112142</ValidVotes>
</Selection>
<ProposalItem ReferendumOptionIdentifier="19000000001B-NO" />
</Candidate>
<ValidVotes>3218657</ValidVotes>
</Selection>
</TotalVotes>
</Contest>
</Contests>
</Election>
</Count>
</EML>
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]