Viewing entries in
Election Data Standards

Comment

Response Letter to POLITICO Article on Critical Election Infrastructure

Below is a letter sent to Tim Starks and Cory Bennett of POLITICO, who cover cyber-security issues.  There seems to be some fundamental misunderstandings of the challenges local election officials (LEOs) face, the process by which the equipment is qualified for deployment (albeit decrepit archaic technology by today's standards), what the vulnerabilities are (and are not), and why a designation of "critical infrastructure" is an important consideration.  We attempt to address some of those points in this response to Tim's otherwise really good coverage....

Comment

Comment

Driving Online Voter Registration Data Standards

We're helping the formation of a new study group regarding online voter registration data and protocol standards.  This week, we're getting started.  You need not be a geek or a member of the standards working groups or any kind of a techie to get involved.  Here's the opportunity to engage...

Comment

Comment

Advancing Election Data Standards: View From the Trenches

Elections data standards are essential to delivering real innovation.  The annual Election Data Standards meeting opened today in Los Angeles, CA.  We thought we'd give you an overview of just what in the hec this is about and why its essential to creating a voting experience that's easy, convenient, and dare we say delightful.  Dry?  Kinda.  But a peek at the real in the trenches work we're doing.  Yep.

Comment

Comment

The “VoteStream Files” A Summary

The TrustTheVote Project Core Team has been hard at work on the Alpha version ofVoteStream, our election results reporting technology. They recently wrapped up a prototype phase funded by the Knight Foundation, and then forged ahead a bit, to incorporate data from additional counties, provided by by participating state or local election officials after the official wrap-up.

Along the way, there have been a series of postings here that together tell a story about the VoteStream prototype project. They start with a basic description of the project in Towards Standardized Election Results Data Reporting and Election Results Reload: the Time is Right. Then there was a series of posts about the project’s assumptions about data, about software (part one and part two), and about standards and converters (part one and part two).

Of course, the information wouldn’t be complete without a description of the open-source software prototype itself, provided Not Just Election Night: VoteStream.

Actually the project was as much about data, standards, and tools, as software. On the data front, there is a general introduction to a major part of the project’s work in “data wrangling” in VoteStream: Data-Wrangling of Election Results DataAfter that were more posts on data wrangling, quite deep in the data-head shed — but still important, because each one is about the work required to take real election data and real election result data from disparate counties across the country, and fit into a common data format and common online user experience. The deep data-heads can find quite a bit of detail in three postings about data wrangling, in Ramsey County MN, in Travis County TX, and in Los Angeles CountyCA.

Today, there is a VoteStream project web site with VoteStream itself and the latest set of multi-county election results, but also with some additional explanatory material, including the election results data for each of these counties.  Of course, you can get that from the VoteStream API or data feed, but there may be some interest in the actual source data.  For more on those developments, stay tuned!

Comment