I’m here this morning to warn that, whatever gloss might be put on it, the so-called “compromise” on immunity for phone companies that broke the law is anything but a compromise, and that Congress appears poised to needlessly toss the rule of law out the window and deprive these millions of ordinary Americans of their day in court. My one simple message is that no matter how they spin it, this is still immunity, period.
Indeed, there’s an easy litmus test that everyone can use when evaluating this proposal or any other: does it allow the court to rule on the legality of the surveillance? That is, does it allow the plaintiffs to obtain a public decision on whether the companies broke the law, and if they did, to get an injunction to stop them from breaking the law again? If the answer is “no”, then it’s still immunity, plain and simple.
The EFF's Kevin Bankston in a prepared statement. (emphasis mine)
(Press Release: EFF Speaks Out Against Telecom Immunity Deal)
";}s:7:"summary";s:1106:"> I?m here this morning to warn that, whatever gloss might be put on it, the so-called ?compromise? on immunity for phone companies that broke the law is anything but a compromise, and that Congress appears poised to needlessly toss the rule of law out the window and deprive these millions of ordinary Americans of their day in court. My one simple message is that no matter how they spin it, this is still immunity, period. > > **Indeed, there?s an easy litmus test that everyone can use when evaluating this proposal or any other: does it allow the court to rule on the legality of the surveillance?** That is, does it allow the plaintiffs to obtain a public decision on whether the companies broke the law, and if they did, to get an injunction to stop them from breaking the law again? If the answer is ?no?, then it?s still immunity, plain and simple. The EFF's Kevin Bankston in a [prepared statement][1]. (emphasis mine) [1]: http://www.eff.org/files/filenode//EFF_bankston.pdf (Press Release: [EFF Speaks Out Against Telecom Immunity Deal][2]) [2]: http://www.eff.org/press/archives/2008/06/18";s:12:"atom_content";s:1226:"I’m here this morning to warn that, whatever gloss might be put on it, the so-called “compromise” on immunity for phone companies that broke the law is anything but a compromise, and that Congress appears poised to needlessly toss the rule of law out the window and deprive these millions of ordinary Americans of their day in court. My one simple message is that no matter how they spin it, this is still immunity, period.
Indeed, there’s an easy litmus test that everyone can use when evaluating this proposal or any other: does it allow the court to rule on the legality of the surveillance? That is, does it allow the plaintiffs to obtain a public decision on whether the companies broke the law, and if they did, to get an injunction to stop them from breaking the law again? If the answer is “no”, then it’s still immunity, plain and simple.
The EFF's Kevin Bankston in a prepared statement. (emphasis mine)
(Press Release: EFF Speaks Out Against Telecom Immunity Deal)
";}i:1;a:8:{s:5:"about";s:62:"http://www.josephhall.org/nqb2/index.php/2008/06/10/njgusbrief";s:5:"title";s:43:"Voting Machine Gag Orders and Trade Secrets";s:4:"link";s:62:"http://www.josephhall.org/nqb2/index.php/2008/06/10/njgusbrief";s:2:"dc";a:3:{s:4:"date";s:20:"2008-06-10T17:43:46Z";s:7:"creator";s:3:"joe";s:7:"subject";s:9:"elections";}s:11:"description";s:2887:"ACLU of New Jersey [has submitted an amicus brief](http://www.aclu-nj.org/news/aclunjdemandsendtovotingma.htm) ([1.5MB PDF](http://www.aclu-nj.org/downloads/061008Gusciora.pdf)) in the *Gusciora* case, being litigated by Penny Venetis and her team at Rutgers' Constitutional Law Clinic. The brief challenges a gag order issued by the Judge based on the implications of the Judge's order with respect to 1) the first amendment rights of the experts in the case and the public; and 2) the lack of showing of good cause in restricting dissemination of results from the experts' testing. I haven't seen the full protective order, but the two paragraphs at issue here are troubling. I can't imagine any expert that could agree to those terms that also hopes to be available for such work during the next few years (while the case makes its way through the courts). For academics that work in this field, the order is even worse in the sense that one couldn't discuss any aspect of their findings and could even be chilled in discussing findings from other studies. One thing that gets me is the continual use (in all areas of voting technology) of the terms "proprietary information" and "confidential information". Let's be clear here: the only types of information that could be compromised by disclosure are trade secrets and confidential personal information. Any other term is just not acceptable: the other forms of intellectual property---copyright, trademark and patent rights---would not be implicated by disclosure of the information; that is, the vendor would still be able to enforce those rights. And any confidential information that is not personal information is a trade secret. Vendors in voting systems have been getting a "pass" on the issue of trade secrecy for too long. In other contexts, trade secrets are things that one can point to and identify (e.g., the recipe for Coca-Cola). Vendors of voting technology have been able to point vaguely at their hardware, software and documentation and say, "There's trade secrets there." Undoubtedly there are. However, we need a mechanism by which vendors can positively identify trade secrets... or reviewers should be able to ask, "Is there a trade secret in this sentence from your documentation?" Narrowing what is a possible trade secret would allow reviewers (or anyone) to produce public and private reports more easily where the private reports contained trade secrets. Usually, we "know it when we see it" with trade secrets but in the realm of voting technology, we currently do not. That's going to need to change. NB: Obviously, there is a third type of information that could be problematic if disclosed: actionable security exploits. That is, details about security vulnerabilities sufficient to allow compromise of a voting system in a manner such that elections are placed in danger of exploit.";s:7:"content";a:1:{s:7:"encoded";s:2959:"ACLU of New Jersey has submitted an amicus brief (1.5MB PDF) in the Gusciora case, being litigated by Penny Venetis and her team at Rutgers' Constitutional Law Clinic. The brief challenges a gag order issued by the Judge based on the implications of the Judge's order with respect to 1) the first amendment rights of the experts in the case and the public; and 2) the lack of showing of good cause in restricting dissemination of results from the experts' testing.
I haven't seen the full protective order, but the two paragraphs at issue here are troubling. I can't imagine any expert that could agree to those terms that also hopes to be available for such work during the next few years (while the case makes its way through the courts). For academics that work in this field, the order is even worse in the sense that one couldn't discuss any aspect of their findings and could even be chilled in discussing findings from other studies.
One thing that gets me is the continual use (in all areas of voting technology) of the terms "proprietary information" and "confidential information". Let's be clear here: the only types of information that could be compromised by disclosure are trade secrets and confidential personal information. Any other term is just not acceptable: the other forms of intellectual property---copyright, trademark and patent rights---would not be implicated by disclosure of the information; that is, the vendor would still be able to enforce those rights. And any confidential information that is not personal information is a trade secret.
Vendors in voting systems have been getting a "pass" on the issue of trade secrecy for too long. In other contexts, trade secrets are things that one can point to and identify (e.g., the recipe for Coca-Cola). Vendors of voting technology have been able to point vaguely at their hardware, software and documentation and say, "There's trade secrets there." Undoubtedly there are. However, we need a mechanism by which vendors can positively identify trade secrets... or reviewers should be able to ask, "Is there a trade secret in this sentence from your documentation?" Narrowing what is a possible trade secret would allow reviewers (or anyone) to produce public and private reports more easily where the private reports contained trade secrets.
Usually, we "know it when we see it" with trade secrets but in the realm of voting technology, we currently do not. That's going to need to change.
NB: Obviously, there is a third type of information that could be problematic if disclosed: actionable security exploits. That is, details about security vulnerabilities sufficient to allow compromise of a voting system in a manner such that elections are placed in danger of exploit.
";}s:7:"summary";s:2887:"ACLU of New Jersey [has submitted an amicus brief](http://www.aclu-nj.org/news/aclunjdemandsendtovotingma.htm) ([1.5MB PDF](http://www.aclu-nj.org/downloads/061008Gusciora.pdf)) in the *Gusciora* case, being litigated by Penny Venetis and her team at Rutgers' Constitutional Law Clinic. The brief challenges a gag order issued by the Judge based on the implications of the Judge's order with respect to 1) the first amendment rights of the experts in the case and the public; and 2) the lack of showing of good cause in restricting dissemination of results from the experts' testing. I haven't seen the full protective order, but the two paragraphs at issue here are troubling. I can't imagine any expert that could agree to those terms that also hopes to be available for such work during the next few years (while the case makes its way through the courts). For academics that work in this field, the order is even worse in the sense that one couldn't discuss any aspect of their findings and could even be chilled in discussing findings from other studies. One thing that gets me is the continual use (in all areas of voting technology) of the terms "proprietary information" and "confidential information". Let's be clear here: the only types of information that could be compromised by disclosure are trade secrets and confidential personal information. Any other term is just not acceptable: the other forms of intellectual property---copyright, trademark and patent rights---would not be implicated by disclosure of the information; that is, the vendor would still be able to enforce those rights. And any confidential information that is not personal information is a trade secret. Vendors in voting systems have been getting a "pass" on the issue of trade secrecy for too long. In other contexts, trade secrets are things that one can point to and identify (e.g., the recipe for Coca-Cola). Vendors of voting technology have been able to point vaguely at their hardware, software and documentation and say, "There's trade secrets there." Undoubtedly there are. However, we need a mechanism by which vendors can positively identify trade secrets... or reviewers should be able to ask, "Is there a trade secret in this sentence from your documentation?" Narrowing what is a possible trade secret would allow reviewers (or anyone) to produce public and private reports more easily where the private reports contained trade secrets. Usually, we "know it when we see it" with trade secrets but in the realm of voting technology, we currently do not. That's going to need to change. NB: Obviously, there is a third type of information that could be problematic if disclosed: actionable security exploits. That is, details about security vulnerabilities sufficient to allow compromise of a voting system in a manner such that elections are placed in danger of exploit.";s:12:"atom_content";s:2959:"ACLU of New Jersey has submitted an amicus brief (1.5MB PDF) in the Gusciora case, being litigated by Penny Venetis and her team at Rutgers' Constitutional Law Clinic. The brief challenges a gag order issued by the Judge based on the implications of the Judge's order with respect to 1) the first amendment rights of the experts in the case and the public; and 2) the lack of showing of good cause in restricting dissemination of results from the experts' testing.
I haven't seen the full protective order, but the two paragraphs at issue here are troubling. I can't imagine any expert that could agree to those terms that also hopes to be available for such work during the next few years (while the case makes its way through the courts). For academics that work in this field, the order is even worse in the sense that one couldn't discuss any aspect of their findings and could even be chilled in discussing findings from other studies.
One thing that gets me is the continual use (in all areas of voting technology) of the terms "proprietary information" and "confidential information". Let's be clear here: the only types of information that could be compromised by disclosure are trade secrets and confidential personal information. Any other term is just not acceptable: the other forms of intellectual property---copyright, trademark and patent rights---would not be implicated by disclosure of the information; that is, the vendor would still be able to enforce those rights. And any confidential information that is not personal information is a trade secret.
Vendors in voting systems have been getting a "pass" on the issue of trade secrecy for too long. In other contexts, trade secrets are things that one can point to and identify (e.g., the recipe for Coca-Cola). Vendors of voting technology have been able to point vaguely at their hardware, software and documentation and say, "There's trade secrets there." Undoubtedly there are. However, we need a mechanism by which vendors can positively identify trade secrets... or reviewers should be able to ask, "Is there a trade secret in this sentence from your documentation?" Narrowing what is a possible trade secret would allow reviewers (or anyone) to produce public and private reports more easily where the private reports contained trade secrets.
Usually, we "know it when we see it" with trade secrets but in the realm of voting technology, we currently do not. That's going to need to change.
NB: Obviously, there is a third type of information that could be problematic if disclosed: actionable security exploits. That is, details about security vulnerabilities sufficient to allow compromise of a voting system in a manner such that elections are placed in danger of exploit.
";}i:2;a:8:{s:5:"about";s:59:"http://www.josephhall.org/nqb2/index.php/2008/06/04/getbent";s:5:"title";s:7:"Psst...";s:4:"link";s:59:"http://www.josephhall.org/nqb2/index.php/2008/06/04/getbent";s:2:"dc";a:3:{s:4:"date";s:20:"2008-06-04T19:52:33Z";s:7:"creator";s:3:"joe";s:7:"subject";s:4:"wtf?";}s:11:"description";s:81:"...many of us don't want to read your blog posts on Obama and Clinton. Get bent.";s:7:"content";a:1:{s:7:"encoded";s:89:"...many of us don't want to read your blog posts on Obama and Clinton. Get bent.
";}s:7:"summary";s:81:"...many of us don't want to read your blog posts on Obama and Clinton. Get bent.";s:12:"atom_content";s:89:"...many of us don't want to read your blog posts on Obama and Clinton. Get bent.
";}i:3;a:8:{s:5:"about";s:57:"http://www.josephhall.org/nqb2/index.php/2008/06/03/evt08";s:5:"title";s:15:"EVT 2008 is on!";s:4:"link";s:57:"http://www.josephhall.org/nqb2/index.php/2008/06/03/evt08";s:2:"dc";a:3:{s:4:"date";s:20:"2008-06-03T21:47:10Z";s:7:"creator";s:3:"joe";s:7:"subject";s:9:"elections";}s:11:"description";s:466:"The 2008 USENIX/ACCURATE Workshop on Electronic Voting Technology is open for registration with the full technical program posted here: It's been quite popular to the extent that the organizers and PC chairs this year, David Dill and Tadayoshi Kohno, worked to expand it to two days! I'll be moderating a panel and presenting the last chapter of my thesis, so be sure to come early if you plan on attending USENIX Security or if you're a die-hard elections geek!";s:7:"content";a:1:{s:7:"encoded";s:583:"The 2008 USENIX/ACCURATE Workshop on Electronic Voting Technology is open for registration with the full technical program posted here:
http://www.usenix.org/events/evt08/tech/
It's been quite popular to the extent that the organizers and PC chairs this year, David Dill and Tadayoshi Kohno, worked to expand it to two days! I'll be moderating a panel and presenting the last chapter of my thesis, so be sure to come early if you plan on attending USENIX Security or if you're a die-hard elections geek!
";}s:7:"summary";s:466:"The 2008 USENIX/ACCURATE Workshop on Electronic Voting Technology is open for registration with the full technical program posted here: It's been quite popular to the extent that the organizers and PC chairs this year, David Dill and Tadayoshi Kohno, worked to expand it to two days! I'll be moderating a panel and presenting the last chapter of my thesis, so be sure to come early if you plan on attending USENIX Security or if you're a die-hard elections geek!";s:12:"atom_content";s:583:"The 2008 USENIX/ACCURATE Workshop on Electronic Voting Technology is open for registration with the full technical program posted here:
http://www.usenix.org/events/evt08/tech/
It's been quite popular to the extent that the organizers and PC chairs this year, David Dill and Tadayoshi Kohno, worked to expand it to two days! I'll be moderating a panel and presenting the last chapter of my thesis, so be sure to come early if you plan on attending USENIX Security or if you're a die-hard elections geek!
";}i:4;a:8:{s:5:"about";s:57:"http://www.josephhall.org/nqb2/index.php/2008/05/28/vipqs";s:5:"title";s:46:"Questions about the Voting Information Project";s:4:"link";s:57:"http://www.josephhall.org/nqb2/index.php/2008/05/28/vipqs";s:2:"dc";a:3:{s:4:"date";s:20:"2008-05-28T17:42:39Z";s:7:"creator";s:3:"joe";s:7:"subject";s:9:"standards";}s:11:"description";s:10243:"Doug Chapin and [Chris Backert] pointed me to the new [Voting Information Project] (Chris entitled his post, [*?Just About The Coolest Thing?*][1]). My initial reaction was much like the title of Chris? post: it did seem very cool. Not only that, but it?s funded/coordinated by [Google, Inc.], [Pew?s Center on the States] and the [JEHT Foundation]. This will be a wonderful resource when finished and will start to regularize structured data publication by local election jurisdictions. Many thanks and my gratitude to those behind VIP for their efforts and investment. However, after looking a bit more deeply into the current content of the VIP site, I?m left with some serious questions. I hope we can work through some of these comments to best position VIP to fulfill its goals. [Pew?s Center on the States]: http://www.pewcenteronthestates.org/ [JEHT Foundation]: http://www.jehtfoundation.org/ [Google, Inc.]: http://www.google.com/ ### What?s the vision? It?s hard to find a coherent vision for the project. They have a [FAQ] and [a longer description] of the project, but no mission, vision or roadmap and no indication of who (as in people, individuals) are participating (other than the developers listed on [their Google Code page]). Right now the VIP appears to be a data standard (a markup language specification), a funding program for states to collect data in this format and a method of uploading such data to the VIP site. (In the longer description of the project, they say they?ll soon provide data feeds.) It would be nice to know what else they have planned. One concern during an election year is a data collection overload; the VIP shouldn?t develop in a vacuum, which it appears to have over the past eight months. That is, much of this information is regularly made available by NGOs. Ballot information can be had at the state and local level via LWV?s [smartvoter], for example. The [Verified Voting Foundation] has invested quite a bit of time and effort in producing a mapping of the types of voting technologies used at the local level (check out their [Verifier] tool). I can understand how this is a ?push? effort rather than a ?pull? effort---that is, the idea is for government entities to start providing this data instead of NGOs to have to collect it---but a more likely outcome for this project is that a few states provide feeds in 2008 and then stop maintaining this information when the attention dissipates. (NB: The specification doesn?t have a name other than the ?Voting Information Project?s open format? (or, in various places, ?EVP XML? or ?EIP XML?). I?ll call it the ?VIP XML format?.) ### Where?s the EML? The VIP XML format specification document (via [this very ugly URL][standard]), doesn?t mention the OASIS? [Election Markup Language][EML] (EML). EML is an international standard markup language for election data that is currently in the process of becoming an ISO standard. It would be good if the VIP folks could say why they decided to make their own standard instead of reusing pieces of the EML standard. I suspect this is because the EML standard is general to more than just US elections and that it might not include elements that they need for their goals. However, it would make sense to see how EML could be changed to accommodate these needs rather than eschewing it altogether. This is an important point: There is no mention on the VIP site that they?re working with voting system vendors. Vendors are planning on supporting data interchange in EML format and a number of us have made the case that the new US VVSG standard should *require* vendors to produce data in EML (see the [text of ACCURATE?s VVSG comments][accurate-vvsg]). The VIP project would be much more useful if they also invested time in XSL transforms that would allow EML interoperability with the VIP XML format. ### Where are the data entry tools, etc.? Related to this last point, if the idea is to provide regularly-updated ?feeds? of elections-related information, there needs to be mechanisms for getting this information out of the tools that jurisdictions currently use, or providing data-entry ?wizards? that will walk local election officials---where most of this information will reside---through the process of creating a data feed. Obviously, data ?feeds? are best and most useful when automatically created rather than manually updated. There isn?t any attention on the VIP site to the integration needed with existing elections information management tools and election management systems to best support data publication and dissemination such that the end-to-end connection is made from tools that contain this information to publication of the information via the VIP feeds mechanism. ### What will encourage jurisdictions to enter/provide data? In all seriousness, why would a jurisdiction want to provide this information? Unless election officials see a clear benefit from providing the data and that the process for doing so is easy (and hard to provide incorrect, incomplete, etc. data), I can?t imagine many jurisdictions will take the time to do this. The VIP project seems to think that this is a problem of initial costs. To remedy this, they?re [offering $20,000 per state][funding] to help with these fixed costs. I?m not convinced that?s adequate. It might make more sense if there was some sort of incentive offered for providing data, similar to a non-profit equivalent to [Dan Tokaji and Thad Hall?s proposal] for providing federal funding contingent upon completing a detailed election data survey instrument. I don?t think financial incentives are absolutely necessary to get comprehensive, high-quality data. Instead, election officials need to see there is some sort of network effect that compels them to provide data. For example, if there was a social network-component or if, through using it, they got access to some tools that made their jobs easier (such as voter-oriented elections information portals). ### What?s with the draconian terms? Being not-quite-a-lawyer, I was really interested to see the VIP project?s [Terms of Service]. There are a few interesting, and possibly troubling, features of this ToS: * **CC licensed specification:** The specification document is licensed under a Creative Commons Attribution-ShareAlike 2.5 license. It appears that the text of recent Google and Microsoft specifications are so licensed but, I?d feel more comfortable with a license that recognizes that a specification is more than just text (see Creative Common?s Mike Linksvayer?s post [*?What good is a CC licensed specification??*][ccspec]). * **Changes could be arbitrary:** For a site that aims to provide data feeds, it?s a bit troubling that the ToS says anything can happen at any time without any notice. Some notion of a commitment to provide data that people are relying on would be a good thing. * **It?s a contract:** Unlike most ToSs, it explicitly says that the ToS is a ?contract? that we, as visitors, enter into by using the website. In the world of terms of use, terms of service, etc., it?s rare to see the word ?contract? used; usually ToS writers prefer less-specific language. I?m not sure if this is necessarily a problem and would be interested if any legal minds out there have an opinion on such adhesion contracts on the internet. (I just might not be aware of recent developments that advise using the more specific ?contract? language.) My point here is that these terms seem somewhat draconian and reflect the desire of the backers to avoid legal messes and liability. But will these terms serve their goals of creating a interactive data community? I?m doubtful. The question of what terms should apply to ?open services? will have to wait for a future article. ### What kind of standard is their spec? Finally, the big kicker for me: This doesn?t appear to be an open standard. I would call it a disclosed standard or a limited open standard (after [my paper on source code disclosure in voting systems]... that I?m currently updating for my thesis publication): Only a few possible constituencies are able to provide input into the VIP XML standard and it can change arbitrarily at any point in time. If one of the goals is to support data publication in an end-to-end manner, it would be best to include users of the data as well as election management system developers (vendors) in development of the standard. As it stands now, it appears to be an effort entirely contained within Google and a set of unidentified state-level election officials. [my paper on source code disclosure in voting systems]: http://josephhall.org/papers/jhall_evt06.pdf [Chris Backert]: http://blog.electiontechnology.com/ [Voting Information Project]: http://www.votinginfoproject.org/ [1]: http://blog.electiontechnology.com/?p=123 [smartvoter]: http://www.smartvoter.org/ [Verified Voting Foundation]: http://verifiedvoting.org/ [Verifier]: http://www.verifiedvoting.org/verifier/ [FAQ]: http://www.votinginfoproject.org/index.cfm?objectid=95FDF9E5-1D09-317F-BBADD2A46EC576BA [a longer description]: http://www.votinginfoproject.org/index.cfm?objectid=960198E5-1D09-317F-BB3EAC4473134BE6 [their Google Code page]: http://code.google.com/p/election-info-standard/downloads/list [standard]: http://www.votinginfoproject.org/index.cfm?objectid=EE2171E7-1D09-317F-BBDC338FB97201CE [EML]: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=election [funding]: http://www.votinginfoproject.org/index.cfm?objectid=EE7D0E83-1D09-317F-BB78158ADFC5626E [Dan Tokaji and Thad Hall?s proposal]: http://moritzlaw.osu.edu/blogs/tokaji/2007/06/money-for-data-funding-oldest-unfunded.html [ccspec]: http://creativecommons.org/weblog/entry/8165 [Terms of Service]: http://www.votinginfoproject.org/index.cfm?objectid=9600D288-1D09-317F-BB2F3B368CABDA44 [accurate-vvsg]: http://accurate-voting.org/2008/05/05/accurate-vvsg2-comments/ I don?t want to sound too harsh; I think this is exactly the kind of endeavor we need more of. However, the overall feeling I get from the VIP is not as promising as it could be. **UPDATE [2008-05-28T12:26:47PDT]:** Added some sugar to my criticism.";s:7:"content";a:1:{s:7:"encoded";s:10693:"Doug Chapin and Chris Backert pointed me to the new Voting Information Project (Chris entitled his post, “Just About The Coolest Thing”). My initial reaction was much like the title of Chris’ post: it did seem very cool. Not only that, but it’s funded/coordinated by Google, Inc., Pew’s Center on the States and the JEHT Foundation. This will be a wonderful resource when finished and will start to regularize structured data publication by local election jurisdictions. Many thanks and my gratitude to those behind VIP for their efforts and investment.
However, after looking a bit more deeply into the current content of the VIP site, I’m left with some serious questions. I hope we can work through some of these comments to best position VIP to fulfill its goals.
It’s hard to find a coherent vision for the project. They have a FAQ and a longer description of the project, but no mission, vision or roadmap and no indication of who (as in people, individuals) are participating (other than the developers listed on their Google Code page).
Right now the VIP appears to be a data standard (a markup language specification), a funding program for states to collect data in this format and a method of uploading such data to the VIP site. (In the longer description of the project, they say they’ll soon provide data feeds.)
It would be nice to know what else they have planned. One concern during an election year is a data collection overload; the VIP shouldn’t develop in a vacuum, which it appears to have over the past eight months. That is, much of this information is regularly made available by NGOs. Ballot information can be had at the state and local level via LWV’s smartvoter, for example. The Verified Voting Foundation has invested quite a bit of time and effort in producing a mapping of the types of voting technologies used at the local level (check out their Verifier tool). I can understand how this is a “push” effort rather than a “pull” effort---that is, the idea is for government entities to start providing this data instead of NGOs to have to collect it---but a more likely outcome for this project is that a few states provide feeds in 2008 and then stop maintaining this information when the attention dissipates.
(NB: The specification doesn’t have a name other than the “Voting Information Project’s open format” (or, in various places, “EVP XML” or “EIP XML”). I’ll call it the “VIP XML format”.)
The VIP XML format specification document (via this very ugly URL), doesn’t mention the OASIS’ Election Markup Language (EML). EML is an international standard markup language for election data that is currently in the process of becoming an ISO standard. It would be good if the VIP folks could say why they decided to make their own standard instead of reusing pieces of the EML standard. I suspect this is because the EML standard is general to more than just US elections and that it might not include elements that they need for their goals. However, it would make sense to see how EML could be changed to accommodate these needs rather than eschewing it altogether.
This is an important point: There is no mention on the VIP site that they’re working with voting system vendors. Vendors are planning on supporting data interchange in EML format and a number of us have made the case that the new US VVSG standard should require vendors to produce data in EML (see the text of ACCURATE’s VVSG comments). The VIP project would be much more useful if they also invested time in XSL transforms that would allow EML interoperability with the VIP XML format.
Related to this last point, if the idea is to provide regularly-updated “feeds” of elections-related information, there needs to be mechanisms for getting this information out of the tools that jurisdictions currently use, or providing data-entry “wizards” that will walk local election officials---where most of this information will reside---through the process of creating a data feed.
Obviously, data “feeds” are best and most useful when automatically created rather than manually updated. There isn’t any attention on the VIP site to the integration needed with existing elections information management tools and election management systems to best support data publication and dissemination such that the end-to-end connection is made from tools that contain this information to publication of the information via the VIP feeds mechanism.
In all seriousness, why would a jurisdiction want to provide this information? Unless election officials see a clear benefit from providing the data and that the process for doing so is easy (and hard to provide incorrect, incomplete, etc. data), I can’t imagine many jurisdictions will take the time to do this.
The VIP project seems to think that this is a problem of initial costs. To remedy this, they’re offering $20,000 per state to help with these fixed costs. I’m not convinced that’s adequate. It might make more sense if there was some sort of incentive offered for providing data, similar to a non-profit equivalent to Dan Tokaji and Thad Hall’s proposal for providing federal funding contingent upon completing a detailed election data survey instrument.
I don’t think financial incentives are absolutely necessary to get comprehensive, high-quality data. Instead, election officials need to see there is some sort of network effect that compels them to provide data. For example, if there was a social network-component or if, through using it, they got access to some tools that made their jobs easier (such as voter-oriented elections information portals).
Being not-quite-a-lawyer, I was really interested to see the VIP project’s Terms of Service. There are a few interesting, and possibly troubling, features of this ToS:
My point here is that these terms seem somewhat draconian and reflect the desire of the backers to avoid legal messes and liability. But will these terms serve their goals of creating a interactive data community? I’m doubtful. The question of what terms should apply to “open services” will have to wait for a future article.
Finally, the big kicker for me: This doesn’t appear to be an open standard. I would call it a disclosed standard or a limited open standard (after my paper on source code disclosure in voting systems... that I’m currently updating for my thesis publication): Only a few possible constituencies are able to provide input into the VIP XML standard and it can change arbitrarily at any point in time. If one of the goals is to support data publication in an end-to-end manner, it would be best to include users of the data as well as election management system developers (vendors) in development of the standard. As it stands now, it appears to be an effort entirely contained within Google and a set of unidentified state-level election officials.
I don’t want to sound too harsh; I think this is exactly the kind of endeavor we need more of. However, the overall feeling I get from the VIP is not as promising as it could be.
UPDATE [2008-05-28T12:26:47PDT]: Added some sugar to my criticism.
";}s:7:"summary";s:10243:"Doug Chapin and [Chris Backert] pointed me to the new [Voting Information Project] (Chris entitled his post, [*?Just About The Coolest Thing?*][1]). My initial reaction was much like the title of Chris? post: it did seem very cool. Not only that, but it?s funded/coordinated by [Google, Inc.], [Pew?s Center on the States] and the [JEHT Foundation]. This will be a wonderful resource when finished and will start to regularize structured data publication by local election jurisdictions. Many thanks and my gratitude to those behind VIP for their efforts and investment. However, after looking a bit more deeply into the current content of the VIP site, I?m left with some serious questions. I hope we can work through some of these comments to best position VIP to fulfill its goals. [Pew?s Center on the States]: http://www.pewcenteronthestates.org/ [JEHT Foundation]: http://www.jehtfoundation.org/ [Google, Inc.]: http://www.google.com/ ### What?s the vision? It?s hard to find a coherent vision for the project. They have a [FAQ] and [a longer description] of the project, but no mission, vision or roadmap and no indication of who (as in people, individuals) are participating (other than the developers listed on [their Google Code page]). Right now the VIP appears to be a data standard (a markup language specification), a funding program for states to collect data in this format and a method of uploading such data to the VIP site. (In the longer description of the project, they say they?ll soon provide data feeds.) It would be nice to know what else they have planned. One concern during an election year is a data collection overload; the VIP shouldn?t develop in a vacuum, which it appears to have over the past eight months. That is, much of this information is regularly made available by NGOs. Ballot information can be had at the state and local level via LWV?s [smartvoter], for example. The [Verified Voting Foundation] has invested quite a bit of time and effort in producing a mapping of the types of voting technologies used at the local level (check out their [Verifier] tool). I can understand how this is a ?push? effort rather than a ?pull? effort---that is, the idea is for government entities to start providing this data instead of NGOs to have to collect it---but a more likely outcome for this project is that a few states provide feeds in 2008 and then stop maintaining this information when the attention dissipates. (NB: The specification doesn?t have a name other than the ?Voting Information Project?s open format? (or, in various places, ?EVP XML? or ?EIP XML?). I?ll call it the ?VIP XML format?.) ### Where?s the EML? The VIP XML format specification document (via [this very ugly URL][standard]), doesn?t mention the OASIS? [Election Markup Language][EML] (EML). EML is an international standard markup language for election data that is currently in the process of becoming an ISO standard. It would be good if the VIP folks could say why they decided to make their own standard instead of reusing pieces of the EML standard. I suspect this is because the EML standard is general to more than just US elections and that it might not include elements that they need for their goals. However, it would make sense to see how EML could be changed to accommodate these needs rather than eschewing it altogether. This is an important point: There is no mention on the VIP site that they?re working with voting system vendors. Vendors are planning on supporting data interchange in EML format and a number of us have made the case that the new US VVSG standard should *require* vendors to produce data in EML (see the [text of ACCURATE?s VVSG comments][accurate-vvsg]). The VIP project would be much more useful if they also invested time in XSL transforms that would allow EML interoperability with the VIP XML format. ### Where are the data entry tools, etc.? Related to this last point, if the idea is to provide regularly-updated ?feeds? of elections-related information, there needs to be mechanisms for getting this information out of the tools that jurisdictions currently use, or providing data-entry ?wizards? that will walk local election officials---where most of this information will reside---through the process of creating a data feed. Obviously, data ?feeds? are best and most useful when automatically created rather than manually updated. There isn?t any attention on the VIP site to the integration needed with existing elections information management tools and election management systems to best support data publication and dissemination such that the end-to-end connection is made from tools that contain this information to publication of the information via the VIP feeds mechanism. ### What will encourage jurisdictions to enter/provide data? In all seriousness, why would a jurisdiction want to provide this information? Unless election officials see a clear benefit from providing the data and that the process for doing so is easy (and hard to provide incorrect, incomplete, etc. data), I can?t imagine many jurisdictions will take the time to do this. The VIP project seems to think that this is a problem of initial costs. To remedy this, they?re [offering $20,000 per state][funding] to help with these fixed costs. I?m not convinced that?s adequate. It might make more sense if there was some sort of incentive offered for providing data, similar to a non-profit equivalent to [Dan Tokaji and Thad Hall?s proposal] for providing federal funding contingent upon completing a detailed election data survey instrument. I don?t think financial incentives are absolutely necessary to get comprehensive, high-quality data. Instead, election officials need to see there is some sort of network effect that compels them to provide data. For example, if there was a social network-component or if, through using it, they got access to some tools that made their jobs easier (such as voter-oriented elections information portals). ### What?s with the draconian terms? Being not-quite-a-lawyer, I was really interested to see the VIP project?s [Terms of Service]. There are a few interesting, and possibly troubling, features of this ToS: * **CC licensed specification:** The specification document is licensed under a Creative Commons Attribution-ShareAlike 2.5 license. It appears that the text of recent Google and Microsoft specifications are so licensed but, I?d feel more comfortable with a license that recognizes that a specification is more than just text (see Creative Common?s Mike Linksvayer?s post [*?What good is a CC licensed specification??*][ccspec]). * **Changes could be arbitrary:** For a site that aims to provide data feeds, it?s a bit troubling that the ToS says anything can happen at any time without any notice. Some notion of a commitment to provide data that people are relying on would be a good thing. * **It?s a contract:** Unlike most ToSs, it explicitly says that the ToS is a ?contract? that we, as visitors, enter into by using the website. In the world of terms of use, terms of service, etc., it?s rare to see the word ?contract? used; usually ToS writers prefer less-specific language. I?m not sure if this is necessarily a problem and would be interested if any legal minds out there have an opinion on such adhesion contracts on the internet. (I just might not be aware of recent developments that advise using the more specific ?contract? language.) My point here is that these terms seem somewhat draconian and reflect the desire of the backers to avoid legal messes and liability. But will these terms serve their goals of creating a interactive data community? I?m doubtful. The question of what terms should apply to ?open services? will have to wait for a future article. ### What kind of standard is their spec? Finally, the big kicker for me: This doesn?t appear to be an open standard. I would call it a disclosed standard or a limited open standard (after [my paper on source code disclosure in voting systems]... that I?m currently updating for my thesis publication): Only a few possible constituencies are able to provide input into the VIP XML standard and it can change arbitrarily at any point in time. If one of the goals is to support data publication in an end-to-end manner, it would be best to include users of the data as well as election management system developers (vendors) in development of the standard. As it stands now, it appears to be an effort entirely contained within Google and a set of unidentified state-level election officials. [my paper on source code disclosure in voting systems]: http://josephhall.org/papers/jhall_evt06.pdf [Chris Backert]: http://blog.electiontechnology.com/ [Voting Information Project]: http://www.votinginfoproject.org/ [1]: http://blog.electiontechnology.com/?p=123 [smartvoter]: http://www.smartvoter.org/ [Verified Voting Foundation]: http://verifiedvoting.org/ [Verifier]: http://www.verifiedvoting.org/verifier/ [FAQ]: http://www.votinginfoproject.org/index.cfm?objectid=95FDF9E5-1D09-317F-BBADD2A46EC576BA [a longer description]: http://www.votinginfoproject.org/index.cfm?objectid=960198E5-1D09-317F-BB3EAC4473134BE6 [their Google Code page]: http://code.google.com/p/election-info-standard/downloads/list [standard]: http://www.votinginfoproject.org/index.cfm?objectid=EE2171E7-1D09-317F-BBDC338FB97201CE [EML]: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=election [funding]: http://www.votinginfoproject.org/index.cfm?objectid=EE7D0E83-1D09-317F-BB78158ADFC5626E [Dan Tokaji and Thad Hall?s proposal]: http://moritzlaw.osu.edu/blogs/tokaji/2007/06/money-for-data-funding-oldest-unfunded.html [ccspec]: http://creativecommons.org/weblog/entry/8165 [Terms of Service]: http://www.votinginfoproject.org/index.cfm?objectid=9600D288-1D09-317F-BB2F3B368CABDA44 [accurate-vvsg]: http://accurate-voting.org/2008/05/05/accurate-vvsg2-comments/ I don?t want to sound too harsh; I think this is exactly the kind of endeavor we need more of. However, the overall feeling I get from the VIP is not as promising as it could be. **UPDATE [2008-05-28T12:26:47PDT]:** Added some sugar to my criticism.";s:12:"atom_content";s:10693:"Doug Chapin and Chris Backert pointed me to the new Voting Information Project (Chris entitled his post, “Just About The Coolest Thing”). My initial reaction was much like the title of Chris’ post: it did seem very cool. Not only that, but it’s funded/coordinated by Google, Inc., Pew’s Center on the States and the JEHT Foundation. This will be a wonderful resource when finished and will start to regularize structured data publication by local election jurisdictions. Many thanks and my gratitude to those behind VIP for their efforts and investment.
However, after looking a bit more deeply into the current content of the VIP site, I’m left with some serious questions. I hope we can work through some of these comments to best position VIP to fulfill its goals.
It’s hard to find a coherent vision for the project. They have a FAQ and a longer description of the project, but no mission, vision or roadmap and no indication of who (as in people, individuals) are participating (other than the developers listed on their Google Code page).
Right now the VIP appears to be a data standard (a markup language specification), a funding program for states to collect data in this format and a method of uploading such data to the VIP site. (In the longer description of the project, they say they’ll soon provide data feeds.)
It would be nice to know what else they have planned. One concern during an election year is a data collection overload; the VIP shouldn’t develop in a vacuum, which it appears to have over the past eight months. That is, much of this information is regularly made available by NGOs. Ballot information can be had at the state and local level via LWV’s smartvoter, for example. The Verified Voting Foundation has invested quite a bit of time and effort in producing a mapping of the types of voting technologies used at the local level (check out their Verifier tool). I can understand how this is a “push” effort rather than a “pull” effort---that is, the idea is for government entities to start providing this data instead of NGOs to have to collect it---but a more likely outcome for this project is that a few states provide feeds in 2008 and then stop maintaining this information when the attention dissipates.
(NB: The specification doesn’t have a name other than the “Voting Information Project’s open format” (or, in various places, “EVP XML” or “EIP XML”). I’ll call it the “VIP XML format”.)
The VIP XML format specification document (via this very ugly URL), doesn’t mention the OASIS’ Election Markup Language (EML). EML is an international standard markup language for election data that is currently in the process of becoming an ISO standard. It would be good if the VIP folks could say why they decided to make their own standard instead of reusing pieces of the EML standard. I suspect this is because the EML standard is general to more than just US elections and that it might not include elements that they need for their goals. However, it would make sense to see how EML could be changed to accommodate these needs rather than eschewing it altogether.
This is an important point: There is no mention on the VIP site that they’re working with voting system vendors. Vendors are planning on supporting data interchange in EML format and a number of us have made the case that the new US VVSG standard should require vendors to produce data in EML (see the text of ACCURATE’s VVSG comments). The VIP project would be much more useful if they also invested time in XSL transforms that would allow EML interoperability with the VIP XML format.
Related to this last point, if the idea is to provide regularly-updated “feeds” of elections-related information, there needs to be mechanisms for getting this information out of the tools that jurisdictions currently use, or providing data-entry “wizards” that will walk local election officials---where most of this information will reside---through the process of creating a data feed.
Obviously, data “feeds” are best and most useful when automatically created rather than manually updated. There isn’t any attention on the VIP site to the integration needed with existing elections information management tools and election management systems to best support data publication and dissemination such that the end-to-end connection is made from tools that contain this information to publication of the information via the VIP feeds mechanism.
In all seriousness, why would a jurisdiction want to provide this information? Unless election officials see a clear benefit from providing the data and that the process for doing so is easy (and hard to provide incorrect, incomplete, etc. data), I can’t imagine many jurisdictions will take the time to do this.
The VIP project seems to think that this is a problem of initial costs. To remedy this, they’re offering $20,000 per state to help with these fixed costs. I’m not convinced that’s adequate. It might make more sense if there was some sort of incentive offered for providing data, similar to a non-profit equivalent to Dan Tokaji and Thad Hall’s proposal for providing federal funding contingent upon completing a detailed election data survey instrument.
I don’t think financial incentives are absolutely necessary to get comprehensive, high-quality data. Instead, election officials need to see there is some sort of network effect that compels them to provide data. For example, if there was a social network-component or if, through using it, they got access to some tools that made their jobs easier (such as voter-oriented elections information portals).
Being not-quite-a-lawyer, I was really interested to see the VIP project’s Terms of Service. There are a few interesting, and possibly troubling, features of this ToS:
My point here is that these terms seem somewhat draconian and reflect the desire of the backers to avoid legal messes and liability. But will these terms serve their goals of creating a interactive data community? I’m doubtful. The question of what terms should apply to “open services” will have to wait for a future article.
Finally, the big kicker for me: This doesn’t appear to be an open standard. I would call it a disclosed standard or a limited open standard (after my paper on source code disclosure in voting systems... that I’m currently updating for my thesis publication): Only a few possible constituencies are able to provide input into the VIP XML standard and it can change arbitrarily at any point in time. If one of the goals is to support data publication in an end-to-end manner, it would be best to include users of the data as well as election management system developers (vendors) in development of the standard. As it stands now, it appears to be an effort entirely contained within Google and a set of unidentified state-level election officials.
I don’t want to sound too harsh; I think this is exactly the kind of endeavor we need more of. However, the overall feeling I get from the VIP is not as promising as it could be.
UPDATE [2008-05-28T12:26:47PDT]: Added some sugar to my criticism.
";}i:5;a:8:{s:5:"about";s:64:"http://www.josephhall.org/nqb2/index.php/2008/05/19/comm2008pics";s:5:"title";s:23:"Some graduation pics...";s:4:"link";s:64:"http://www.josephhall.org/nqb2/index.php/2008/05/19/comm2008pics";s:2:"dc";a:3:{s:4:"date";s:20:"2008-05-19T17:29:26Z";s:7:"creator";s:3:"joe";s:7:"subject";s:7:"iSchool";}s:11:"description";s:308:"Here are some pics taken at our commencement... a superb pic taken by Andrew Fiore (catch his album on Facebook): A picture taken by Jens of me messin' around (link is to my flickr set): A picture taken by me with Yuri's camera... this is Yuri, Fredrik, danah and Jens (the other four PhD graduates): ";s:7:"content";a:1:{s:7:"encoded";s:1270:"Here are some pics taken at our commencement... a superb pic taken by Andrew Fiore (catch his album on Facebook):
A picture taken by Jens of me messin' around (link is to my flickr set):
A picture taken by me with Yuri's camera... this is Yuri, Fredrik, danah and Jens (the other four PhD graduates):
Here are some pics taken at our commencement... a superb pic taken by Andrew Fiore (catch his album on Facebook):
A picture taken by Jens of me messin' around (link is to my flickr set):
A picture taken by me with Yuri's camera... this is Yuri, Fredrik, danah and Jens (the other four PhD graduates):
I gave my dissertation talk today. It went surprisingly well. I felt my delivery was smooth---with nary an “um”---and people seemed interested! I’ve learned that I have to practice talks 3-4 times before I’m ready to give them. (and the “presenter tools” feature in powerpoint is killer, I must say.)
The dissertation talk is a curious beast on the academic landscape. It involves summing up 5 years of work (at least!) in about 50 minutes. I found it very challenging to both adequately explain the work I’ve done and then make that explanation accessible to a multidisciplinary audience. Apparently, I didn't do such a bad job; I can’t explain how gratifying that is for someone who enjoys teaching.
I’ll post my slides one slideshare in a bit and update this post, but they do need a bit of massaging---I used animation to make images appear and disappear over the text, which doesn’t seem to work with slideshare.
Anyway, I’s tie tie now.
(image by the Schultz-enator)
";}s:7:"summary";s:1109:" I gave my dissertation talk today. It went surprisingly well. I felt my delivery was smooth---with nary an ?um?---and people seemed interested! I?ve learned that I have to practice talks 3-4 times before I?m ready to give them. (and the ?presenter tools? feature in powerpoint is killer, I must say.) The dissertation talk is a curious beast on the academic landscape. It involves summing up 5 years of work (at least!) in about 50 minutes. I found it very challenging to both adequately explain the work I?ve done and then make that explanation accessible to a multidisciplinary audience. Apparently, I didn't do such a bad job; I can?t explain how gratifying that is for someone who enjoys teaching. I?ll post my slides one slideshare in a bit and update this post, but they do need a bit of massaging---I used animation to make images appear and disappear over the text, which doesn?t seem to work with slideshare. Anyway, [I?s tie tie now](http://icanhascheezburger.com/2007/10/23/id-eat-yooz-but-i-is-to-tired/). (image by the [Schultz-enator](http://www.flickr.com/photos/jdawg/2492841848/))";s:12:"atom_content";s:1469:" I gave my dissertation talk today. It went surprisingly well. I felt my delivery was smooth---with nary an “um”---and people seemed interested! I’ve learned that I have to practice talks 3-4 times before I’m ready to give them. (and the “presenter tools” feature in powerpoint is killer, I must say.)
The dissertation talk is a curious beast on the academic landscape. It involves summing up 5 years of work (at least!) in about 50 minutes. I found it very challenging to both adequately explain the work I’ve done and then make that explanation accessible to a multidisciplinary audience. Apparently, I didn't do such a bad job; I can’t explain how gratifying that is for someone who enjoys teaching.
I’ll post my slides one slideshare in a bit and update this post, but they do need a bit of massaging---I used animation to make images appear and disappear over the text, which doesn’t seem to work with slideshare.
Anyway, I’s tie tie now.
(image by the Schultz-enator)
";}i:8;a:8:{s:5:"about";s:59:"http://www.josephhall.org/nqb2/index.php/2008/05/09/uberrun";s:5:"title";s:13:"Cool Runnings";s:4:"link";s:59:"http://www.josephhall.org/nqb2/index.php/2008/05/09/uberrun";s:2:"dc";a:3:{s:4:"date";s:20:"2008-05-09T20:01:39Z";s:7:"creator";s:3:"joe";s:7:"subject";s:8:"exercise";}s:11:"description";s:353:"What do you do when you get tired of your old running routes and want a new one? Maybe even a bit longer? Well, you can combine two old ones into a new one! It's like recycling. The run above combines my Oakland Ave. -> Piedmont run and my Lake Merritt run into one uber-run. It's pretty and about 8 miles (although it really feels like about 9).";s:7:"content";a:1:{s:7:"encoded";s:764:"What do you do when you get tired of your old running routes and want a new one? Maybe even a bit longer? Well, you can combine two old ones into a new one! It's like recycling.
The run above combines my Oakland Ave. -> Piedmont run and my Lake Merritt run into one uber-run. It's pretty and about 8 miles (although it really feels like about 9).
";}s:7:"summary";s:353:"What do you do when you get tired of your old running routes and want a new one? Maybe even a bit longer? Well, you can combine two old ones into a new one! It's like recycling. The run above combines my Oakland Ave. -> Piedmont run and my Lake Merritt run into one uber-run. It's pretty and about 8 miles (although it really feels like about 9).";s:12:"atom_content";s:764:"What do you do when you get tired of your old running routes and want a new one? Maybe even a bit longer? Well, you can combine two old ones into a new one! It's like recycling.
The run above combines my Oakland Ave. -> Piedmont run and my Lake Merritt run into one uber-run. It's pretty and about 8 miles (although it really feels like about 9).
";}i:9;a:8:{s:5:"about";s:63:"http://www.josephhall.org/nqb2/index.php/2008/05/07/brewsterlol";s:5:"title";s:36:"FBI withdraws NSL letter to Brewster";s:4:"link";s:63:"http://www.josephhall.org/nqb2/index.php/2008/05/07/brewsterlol";s:2:"dc";a:3:{s:4:"date";s:20:"2008-05-08T00:14:50Z";s:7:"creator";s:3:"joe";s:7:"subject";s:6:"photos";}s:11:"description";s:191:" (full res. [here][1], EFF press release [here][2]) [1]: http://www.josephhall.org/nqb2/media/users/joebeone/brewster_kahle_lolcat-630x.jpg [2]: http://www.eff.org/press/archives/2008/05/06";s:7:"content";a:1:{s:7:"encoded";s:527:"
(full res. here, EFF press release here)
";}s:7:"summary";s:191:" (full res. [here][1], EFF press release [here][2]) [1]: http://www.josephhall.org/nqb2/media/users/joebeone/brewster_kahle_lolcat-630x.jpg [2]: http://www.eff.org/press/archives/2008/05/06";s:12:"atom_content";s:527:"