In an October 9th article in the New Republic, Lawrence Lessig authored an important critique of the transparency movement. Primarily asking the questions – transparency is all fine and good, but what is the end?
Lessig’s article and a related article by Jill Lepore, which takes a critical look at the history of scientific management, in The New Yorker point out that what seems to be a good idea at one time may not be in the long run, especially if not examined. As the saying goes “the road to hell is paved with good intentions.” Thus, without careful review the rush to transparency may lead to unintended consequence that we do not want and may jeopardizes the good that could have been achieved by opening up government data.
In fact, Lessig points out the non-contextual nature of raw data. Without context, data can saying anything. An example that comes to mind is the Denver Post’s effort to publish the salaries of all Colorado state government workers in the Post’s data center (the information is no longer available). As a pure transparency matter, such publication is not a bad idea. However, this data cannot speak the whole story alone. The data that was release simply stated the name of the employee, the employee’s agency or department, the employee’s state classification, and salary. The data did not say if the employee worked for a full year or not. The data did not say if the employee was promoted or demoted during the year. The data did not say what the employee’s job was. The data was without context. So yes a few department of transportation drivers appear to have huge salaries. Why? They drive snow plows and work lots of over time. Was the information useful? Yes. But without the context it does not tell the whole story.
Neither Lessig’s article nor this post on O’Reilly Radar, which highlights both Lessig and Lepore articles, condemn open government data/transparency, rather they point to the need for goals and to ask the important question of “what is the end?” I support transparency fully and think government does need to open up more information. But we do need to think about what will be the benefits and the costs. And if we are republishing, redisturbing, or mashuping any of the data for use as a policy tool, we must provide context and avoid bias whenever possible.
Finding legislative materials is often have the battle of staying informed on what law makers are doing. Sites like opencongress.org and govtrack.us are aimed at making congressional information more accessible and do a good job at achieving this goal. A new project, legislink.org, recently started with the same aim of making legislative and statutory information more accessible. Legislink goes about this task differently by creating human readable URL that direct the user to the legislative information found on the government’s site.
Legislink is not necessarily a better product. Just a different way of getting to important information. (I should disclose that I have contributed to the legislink project on bring it to the state level in Colorado). What I think legislink does extremely well is get the user to the source of the information, the government. Now republishing the legislative material on a new site like Opencongress or govtrack is fine, but why not go to the source of the information first.
Legislink does this by creating URL that can be cited much more easily than the official URLs provide by legislative sites.
For instance, the official Colorado legislative URL for House Bill 08-1266 (a bill I also worked on) is http://www.leg.state.co.us/clics/clics2008a/csl.nsf/fsbillcont3/A254528A18722054872573D1006E26DA?Open&file=1266_enr.pdf. The legislink URL is http://legislink.org/us-co?HB-08-1266. I think that is easier, but you be the judge. In addition, legislink allows users to go directly to a specific section of the piece of legislation, such as section 8 of HB08-1266, http://legislink.org/us-co?HB-08-1266-8. If a bill of interest is long or if you are looking for a specific section of a bill, this feature is extremely helpful.
As a I state above, legislink is not necessarily the answer. Just as opencongress and govtrack are not the answer. But these sites are a step in the right direction to making government information more accessible.
So in the spirit of Chris Brogan, I must applaud Joe Cramel, a retired IT manager for the US Congress, for getting it right by creating the legislink project. I am also encouraging others to participate in building and expanding legisllink by joining the conversation and contributing to the effort on the project wiki.