Interoperability Public Working Group

Table of ContentsUseful Links

Interoperability Working Groups and Common Data Format

The Interoperability working groups are for the discussion and development of guidance for voting system interoperability, including common data format (CDF) modeling and schema development. The guidance will inform the development of requirements for the Election Assistance Commission (EAC) Voluntary Voting System Guidelines (VVSG). The main activity underway is the development of CDF specifications for voting device imports and exports. Another activity is assisting with interoperability-related requirements development for the next VVSG.

Many election officials view voting system interoperability as necessary core function for future voting technology. This working group has as its objective the development of guidance and CDFs that will result in voting system interoperability, bringing with it various advantages, including:

  • Increased efficiency in election operations.
  • Cost savings to election operations and to cost of system integration.
  • Greater choice of voting equipment in the marketplace.
  • More automated generation of EAC survey data.
  • Reduced cost of testing and component certification.
  • Greater transparency to election data.

Joining a CDF Interoperability Working Group

Next VVSG Requirements Development

The working group has been assisting in the development of principles and guidelines and general interoperability requirements for the next VVSG.

The latest draft of general interoperability requirements is located here:

The latest drafts of the requirements by voting activity are located here: Many of the requirements are taken from a 2012 update to the 2007 TGDC Recommendations to the EAC. Chapter 7 of that document is included, below:

CDF Overviews

Introduction to the CDF Project

Frequently Asked Questions

What is GitHub

CDF Working Groups

There are currently four CDF specifications under development as well as two additional efforts to 1) rigorously define voting variations such as RCV and (2) create business process models of election processes. Each of these activities has

  • its own subgroup and mailing list, accessible via an individual twiki subgroup page,
  • its own GitHub repository for storing specification materials, and
  • an associated web-based version of the specification documentation that is linked to the GitHub repository.

The following table contains the appropriate links to the above items:

twiki Subgroup Page GitHub Repository Documentation
Cast Vote Records usnistgov/CastVoteRecords
Election Event Logging usnistgov/ElectionEventLogging
Election Modeling usnistgov/ElectionModeling
Election Results Reporting usnistgov/ElectionResultsReporting
Voter Records Interchange usnistgov/VoterRecordsInterchange
Voting Methods Models usnistgov/VotingMethods TBD

Current Status and Meetings

The NIST Voting System Interoperability Working Group meets by telecon generally the 2nd and 4th Thursday of the month at 3pm Eastern/12pm Pacific, whereas the subgroups may meet at other times (consult the specific twiki pages). The interoperability working group meetings generally include overviews of current work and discussion of broader issues such as overall scope of the CDF work. In addition, the meetings also may focus on interoperability-related requirements for the next VVSG.

Recent Meeting Minutes:

January 24, 2018

December 14, 2017

November 16, 2017

November 02, 2017

October 12, 2017

September 29, 2017

September 08, 2017

August 25, 2017 and CDF_Status_Aug_2017.pdf

July 14, 2017


Directions for Adding (or Removing) Yourself to Working Group Mailing Lists and Reading the Archives

The Interoperability Working Group mailing lists are:

  • – main mailing list for the working group
  • – for the cast vote records group
  • – for the voter records interchange/online voter registration group
  • – for the voting methods/models group
  • – for the election process modeling group
  • – for the election results reporting group

    The Interoperability Working Groups use Google Groups for managing the email lists. If you have a Gmail address or Google account, you can join a group and post to the mailing list and access the email archives; non-Google users can still post and access the email archives but to join, you must send an email to the group administrator. A Google account permits you to continue using your non-Gmail address but signs you in to Google; for information on how to obtain a Gmail address or Google account, please see

How to Join a Group or Manage your Membership in a Group

If you do not have a Gmail address or Google account, please send an email to the following address and include your name and preferred email address(es) and which group(s) you wish to join:

If you do have a Gmail address or Google account:

  1. Go to the following URL:
  2. Click on the “Browse all” button to find groups to join, and click on the name of each group you wish to join.
  3. Click on the “Join group to post” button and set up your email account preferences. You’re done!

    Here is a useful article with further information about Google groups:

How to Read a Group’s Email Archives

Google and non-Google users can read a group’s email archives. Do the following:

  1. Go to the following URL:
  2. Click on the “Browse all” button to find the group whose archive you wish to access.
  3. Click on the name of the group.

Working Group Mailing List Policies

  • All information exchanged within the WG will be non-proprietary. WG members should assume that all materials exchanged will be made public.
  • The mailing list is principally for technical discussion related to the Voting System Working Group's activities and not other activities.
  • Include a signature tag on all messages. Include your name, affiliation, location, and e-mail address.
  • State concisely and clearly the specific topic of the comments in the subject line. This allows members to respond more appropriately to your posting and makes it easier for members to search the archives by subject.
  • Only send a message to the entire list when it contains information that everyone can benefit from.
  • Send messages such as "thanks for the information" or "me, too" to individuals—not to the entire list. Do this by using your e-mail application's forwarding option and typing in or cutting and pasting in the e-mail address of the individual to whom you want to respond.
  • Do not send administrative messages, e.g., remove me from the list, to the mailing list. Instead, use the links on this page to change your settings or to remove yourself from a list.

This Topic Is Referenced By


Topic attachments
I Attachment History Action Size Date Who Comment
PDFpdf 2017-04-07_telecon_minutes.pdf r1 manage 199.5 K 2017-04-10 - 12:17 JohnWack  
HTMLhtml CDF-FAQ.html r1 manage 11.0 K 2017-07-17 - 14:09 JohnWack  
PDFpdf CDF_Status_Aug_2017.pdf r1 manage 571.1 K 2017-08-27 - 13:50 JohnWack  
Microsoft Word filedocx Draft_Requirements_by_Voting_Activity_for_Next_VVSG.docx r1 manage 118.4 K 2017-12-19 - 16:14 JohnWack  
PDFpdf Draft_Requirements_by_Voting_Activity_for_Next_VVSG.pdf r1 manage 433.6 K 2017-12-19 - 16:14 JohnWack  
PDFpdf ElectionResultsReporting-v15.pdf r1 manage 3469.8 K 2015-10-01 - 19:09 JohnWack draft NIST SP Common Data Format for Election Results Reporting
Microsoft Word filedocx General_Integratability_and_Data_Export_Requirements_11-02-2017.docx r1 manage 146.5 K 2017-11-06 - 17:59 JohnWack  
PDFpdf General_Integratability_and_Data_Export_Requirements_11-02-2017.pdf r1 manage 56.4 K 2017-11-06 - 17:59 JohnWack  
Microsoft Word filedocx General_Integratability_and_Data_Export_Requirements_11-29-2017.docx r1 manage 22.9 K 2017-11-29 - 18:56 JohnWack  
PDFpdf General_Integratability_and_Data_Export_Requirements_11-29-2017.pdf r1 manage 51.3 K 2017-11-29 - 18:56 JohnWack  
PDFpdf Interop._Working_Group_Call_1.25.2018.pdf r1 manage 233.8 K 2018-01-26 - 19:04 JohnWack  
PDFpdf Interop._Working_Group_Call_11.16.2017.pdf r1 manage 37.7 K 2017-11-28 - 19:05 JohnWack  
PDFpdf Interop._Working_Group_Call_11.2.2017.pdf r1 manage 39.8 K 2017-11-06 - 18:17 JohnWack  
PDFpdf Interop._Working_Group_Call_12.14.2017.pdf r1 manage 260.2 K 2017-12-19 - 16:11 JohnWack  
PDFpdf Interop._Working_Group_Call_7.14.2017.pdf r1 manage 132.5 K 2017-07-17 - 19:52 JohnWack  
PDFpdf Interop._Working_Group_Call_9.29.2017.pdf r1 manage 171.2 K 2017-10-04 - 19:42 JohnWack  
PDFpdf Interop._Working_Group_Call_9.8.2017.pdf r1 manage 146.7 K 2017-09-21 - 13:07 JohnWack  
PowerPointpptx Interoperability-PWG-Intro-2016-01-28.pptx r1 manage 53.2 K 2016-02-02 - 15:18 JohnWack  
PDFpdf Meeting_Minutes_-_October_12.pdf r1 manage 174.0 K 2017-10-13 - 15:28 JohnWack  
PDFpdf Minutes_2017-08-25.pdf r1 manage 59.6 K 2017-08-27 - 13:50 JohnWack  
Microsoft Word filedoc TGDC_Recommendations-2012_-_By_Voting_Activity.doc r1 manage 3189.0 K 2018-01-25 - 17:29 JohnWack  
PDFpdf TGDC_Recommendations-2012_-_By_Voting_Activity.pdf r1 manage 1839.8 K 2018-01-25 - 17:29 JohnWack  
Microsoft Word filedocx VVSG2-Election-Ballot-Definition_01-25-2018.docx r1 manage 33.0 K 2018-01-25 - 17:29 JohnWack  
PDFpdf VVSG2-Election-Ballot-Definition_01-25-2018.pdf r1 manage 400.3 K 2018-01-25 - 17:29 JohnWack  
Microsoft Word filedocx VVSG2-Requirements-by-voting-activity-02-02-2018.docx r1 manage 126.0 K 2018-02-05 - 20:59 JohnWack  
Microsoft Word filedocx VVSG2-Requirements-by-voting-activity-02-07-2018-v2.docx r1 manage 126.8 K 2018-02-07 - 20:40 JohnWack  
PDFpdf VVSG2-Requirements-by-voting-activity-02-07-2018-v2.pdf r1 manage 848.1 K 2018-02-07 - 20:45 JohnWack  
Microsoft Word filedocx VVSG2-Requirements-by-voting-activity-02-07-2018.docx r1 manage 125.4 K 2018-02-07 - 13:14 JohnWack  
PDFpdf VVSG2-Requirements-by-voting-activity-02-07-2018.pdf r1 manage 852.1 K 2018-02-07 - 14:26 JohnWack  
Microsoft Word filedocx VVSG2-Requirements-by-voting-activity-02-08-2018.docx r1 manage 126.6 K 2018-02-08 - 19:30 JohnWack  
PDFpdf VVSG2-Requirements-by-voting-activity-02-08-2018.pdf r1 manage 845.7 K 2018-02-08 - 19:30 JohnWack  
Microsoft Word filedocx VVSG2-Requirements-by-voting-activity-02-09-2018-v2.docx r1 manage 125.4 K 2018-02-09 - 16:40 JohnWack  
PDFpdf VVSG2-Requirements-by-voting-activity-02-09-2018-v2.pdf r1 manage 749.9 K 2018-02-09 - 16:40 JohnWack  
Edit | Attach | Watch | Print version | History: r84 | r63 < r62 < r61 < r60 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r61 - 2018-02-09 - JohnWack
This site is powered by the TWiki collaboration platform Powered by PerlPLEASE NOTE: This wiki is a collaborative website. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. All the material on this website is in the public domain, including any text, diagrams, or images, unless indicated explicitly. Don't share anything on this site that you do not want to be public. Do not pass any proprietary documents or put any on the TWiki with implied public disclosure. If you do, it shall be deemed to have been disclosed on a non-confidential basis, without any restrictions on use by anyone, except that no valid copyright or patent right shall be deemed to have been waived by such disclosure. Certain commercial equipment, instruments, materials, systems, software, and trade names may be identified throughout this site in order to specify or identify technologies adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the systems or products identified are necessarily the best available for the purpose. Any data provided on this site is for illustrative purposes only, and does not imply a validation of results by NIST. By selecting external links, you will be leaving NIST webspace. Links to other websites are provided because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other websites that are more appropriate for your purpose.