Lots of bills have come up on the Open House Project mail list that we’d label “a good thing”. There are also a few other great ones coming from the GOP. Here’s the roster of bills I’ve jotted down. (If you’re a staffer who’s annoyed I left out your bill, do let me know.)

E-Filing & Disclosure

H.R. 4858: The Public Online Information Act to establish an advisory committee to issue nonbinding governmentwide guidelines on making public information available on the Internet, to require publicly available Government information held by the executive branch to be made available on the Internet, to express the sense of Congress that publicly available information held by the legislative and judicial branches should be available on the Internet, and for other purposes.
By Steve Israel.
(Added to the list 3/25/2010.)

S. 482: Senate Campaign Disclosure Parity Act
A bill to require Senate candidates to file designations, statements, and reports in electronic form, by Feingold with 41 cosponsors.
http://blog.sunlightfoundation.com/2009/02/27/senate-e-filing-bill-reintroduced-pass-s-482/

H.R. 682: Stop Trading on Congressional Knowledge Act
To prohibit securities and commodities trading based on nonpublic information relating to Congress, and to require additional reporting by Members and employees of Congress of securities transaction, and for other purposes, by Rep Baird.
http://blog.sunlightfoundation.com/2009/11/23/lawmaker-investments-and-disclosure/
(added to this list on Nov 23)

CRS Reports

S. Res. 118: A resolution to provide Internet access to certain Congressional Research Service publications
H.R. 3762: Congressional Research Service Electronic Accessibility Act of 2009
To provide members of the public with Internet access to certain Congressional Research Service publications, and for other purposes, by Lieberman with 6 cosponsors and Rep. Frank Kratovil with 2 cosponsors.
http://cdt.org/issue/congressional-research-service

Earmarks

S. Res. 63: A resolution to amend the Standing Rules of the Senate to ensure that all congressionally directed spending items in appropriations and authorization legislation fall under the oversight and transparency provisions of S. 1, the Honest Leadership and Open Government Act of 2007.
By Claire McCaskill with 1 cosponsor.

H. Res. 440: Amending the Rules of the House of Representatives to strengthen the public disclosure of all earmark requests.
By Bill Cassidy with 15 cosponsors.

H.R. 3268: Earmark Transparency and Accountability Reform Act
To amend the Rules of the House of Representatives and the Congressional Budget and Impoundment Control Act of 1974 to increase earmark transparency and accountability, and for other purposes, by Dave Reichert with 1 cosponsor.
(In fairness, this is a big bill and I haven’t studied it closely so I wouldn’t be quick to label it “a good thing” without a review.)

Read The Bill

H. Res. 554: Amending the Rules of the House of Representatives to require that legislation and conference reports be available on the Internet for 72 hours before consideration by the House, and for other purposes.
By Brian Baird with 214 cosponsors.
http://readthebill.org/
http://blog.sunlightfoundation.com/2009/07/09/read-the-bill-the-long-short-story/

H. Res. 835: Amending the rules of the House of Representatives to provide for transparency in the committee amendment process.
By Lynn Jenkins with 110 cosponsors.

Committee Video

H. Res. 869: Directing the Chief Administrative Officer to install cameras in the hearing room of the Committee on Rules.
By Charles Dent with 77 cosponsors.

Google has a philanthropic project underway that might be relevant to us. They are in the process of choosing which projects to pursue, determined by a vote:

http://www.project10tothe100.com/vote.html

Last fall we launched Project 10^100, a call for ideas to change the world by helping as many people as possible. Your response was overwhelming.

…

Make government more transparent

Create a website that enables people from any country or municipality to easily learn about the workings of their government, and rally their fellow citizens to take action to improve it. Numerous user ideas embraced variations on the theme of governmental transparency, with specific proposals ranging from publishing details of proposed laws and politicians’ voting records to making public budgets searchable online and leveraging social networks to let communities make their voices heard by their representatives by voting on pressing issues.

Suggestions that inspired this idea

1. Create a “govwatch” program that allows people to enter in geographic and other info and get back information about bills/laws that affect them

2. Empower individual voters with both online, real-time data on their political representatives’ activity, and tools to analyze, engage and influence outcomes

3. Increase the transparency of laws, eliminate duplicate ones and communicate them better to affected citizens

4. Share information on how municipalities and states use public funds

Recently the GSA has been negotiating on behalf of federal agencies special Terms of Service agreements with various social media services like YouTube to allow agencies to make use of these services — some of those agreements are now publicly available. My understanding is that GSA’s negotiations were necessary before agencies could use these services because of legal issues like liability. I’ve reviewed the TOS’s to see whether they address open-government concerns.

The use of non-governmental services like these as part of a governmental function raises several openness issues, which we rehashed in an earlier thread on the use of YouTube by Congress. To summarize, the issues include:

• whether the service provider meets government web standards including accessibility, privacy, security, nondiscrimination, and archival access to media
• whether the service providers require members of the public to enter into a contractual agreement with them (i.e. more terms of service) in order to access government content, what the public must agree to, and whether these additional terms with the public restrict what the public can do with and how the public can share government media obtained through the service
• whether use of the service constitutes an endorsement of a particular brand or technology, or if it provides a significant business advantage to a profit-seeking entity
• whether the service provides government media in a data format that does not impose technical and legal restrictions on users of the media

I think I need to include a special note about privacy. We can expect that any non-governmental site is going to track their users’ behavior as best they can because of the financial incentives of user-targeted advertising and selling demographic data. I don’t know to what extent any of the services below make use of this, but I expect that this is a major component of the revenue of all of them.

The GSA TOS are amendments to the standard TOS employed by the services. I haven’t read through any of the standard TOS, so of course I might be missing something.

I reviewed the TOS’s with respect to these issues. They had common elements.

No Advertising: The service agrees to not place advertisements on pages with government content (i.e. government “channels” and the like). This addresses part of the concern of endorsement. Of course, services may continue to display their brand name and link users to other parts of the service, so they are still able to promote their business.

No Cookies: The service agrees to not set cookies when a widget is placed *in* a government agency webpage. This means that the service gives up its ability to do the most advanced user tracking in the cases where the user may be unaware that they are even accessing a non-governmental service. The service may still track accesses by IP address which still may provide a more rudimentary means to track users but is more likely to be anonymous.

Closed Captioning: The service will provide the ability for government media to include closed-captioning for videos using industry standard practices, which is of course important for accessibility.

The TOS are linked from here:

https://forum.webcontent.gov/Default.asp?page=TOS_agreements

Here are reviews of each TOS:

AddThis.com

AddThis.com provides a “Social Bookmark & Feed Button Builder”. It’s a widget developers can put on their websites to help users share content on other social sites like Facebook. Because of what AddThis does, there are only a few concerns to be addressed. The TOS addresses both main concerns:

- No Advertising — on government “channels” on the AddThis site
(doesn’t seem to actually apply to AddThis).
- No Cookies — when placed on .gov/.mil websites.

https://forum.webcontent.gov/resource/resmgr/terms_of_service_w_socmed/addthistos_4.30.09_final_uns.pdf

Blip.tv

Blip.tv is a video hosting website, like YouTube. All of the privacy concerns above are relevant. The TOS includes:

- No Cookies — Blip.tv will allow the government to disable parts of its embeddable player that sets cookies.
- Closed Captioning.

Other aspects require some elaboration:

Ads-

The GSA TOS has a confusing section on advertising:

“Blip.tv reserves the right to run advertisements on any page on Blip.tv, but will not run advertisements in-stream or directly adjacent to user videos without the opt-in of the user who uploaded the video.”

It sounds like Blip.tv can place ads on the page, just not directly adjacent to or inside of government media.

Privacy-

The GSA TOS say explicitly that Blip.tv does not collect personally identifiable information about users, but does collect and use demographic data for targeted advertising. Users should expect to be asked demographic data.

https://forum.webcontent.gov/resource/resmgr/Docs/Blip_tv_-_Terms_of_Use_Agree.doc

Blist.com

This is a “social data discovery” tool where users can upload tabular data sets to share. I am actually going to skip a review of this TOS because I expect (or sincerely hope) that tabular data sets are shared with the public directly (as a bulk data download) besides through social tools.

Facebook

Facebook is a social networking site.

The negotiated TOS are not available to the public. Given the likely pervasiveness of the use of all of these tools in the future, it would be a shame if the GSA is facilitating government agencies’ use of third party services that violate the public’s expectations for government web content.

Flickr

Flickr is a photo sharing website. All of the concerns listed above are relevant to Flickr. There are no provisions in the TOS relevant to this review.

https://forum.webcontent.gov/resource/resmgr/Docs/Flickr_TOS_Agreement_Amended.doc

MySpace

MySpace is a social networking site.

The negotiated TOS are not available to the public. Given the likely pervasiveness of the use of all of these tools in the future, it would be a shame if the GSA is facilitating government agencies’ use of third party services that violate the public’s expectations for government web content.

SlideShare

SlideShare is a document (i.e. presentations) sharing tool. The TOS are not posted on the GSA website, but this appears to be a publishing mistake as it notes that the TOS are intended to be publicly available.

Vimeo

Vimeo is a video sharing tool. The TOS has one relevant provision, despite all of the concerns being relevant.

- No Advertising — on government “channels” on the Vimeo site

https://forum.webcontent.gov/resource/resmgr/terms_of_service_w_socmed/vimeo_tos_final_april2009.doc

YouTube

YouTube is a video sharing site.

The negotiated TOS are not available to the public. Given the likely pervasiveness of the use of all of these tools in the future, it would be a shame if the GSA is facilitating government agencies’ use of third party services that violate the public’s expectations for government web content.

Conclusion

While I am encouraged by the GSA’s forward thinking to make use of the latest technologies developed in the private sector, I believe that working with the private sector poses a number of risks to government data, to the public’s privacy and free speech rights, and to good governance. These risks can be minimized and some useful provisions have been included in the negotiated TOS’s along these lines, but far more careful thinking is necessary.

While several of the TOS addressed accessibility and privacy concerns, none of the TOS addressed security, nondiscrimination, archival access to media, the TOS the public are required to enter into to access government content through these services, and web media data formats.

Update: See also this related post.

I frequently see questions like how can I convince my government that open data is important?, and what should I do as a government web manager to make data open?. These and other questions came up at Transparency Camp a few months ago, and at the end of the conference Gunnar Hellekson of Red Hat, and later I, decided to take on the project of bringing together a repository of best-practices guides for technology’s role in an open government. We have a wiki page for the project which lists some of the guides we’d like to see written.

Since the conference I’ve been working on the first guide, Open Data is Civic Capital: Best Practices for “Open Government Data”, which you can read by following the link. The goal was 1) to motivate why open government data isn’t just an ideological issue but actually makes society more powerful, and can really make the world a better place, and 2) to outline some suggested priorities and recommendations for open government data, drawing on the recommendations of a number of past groups (e.g. the 8 Principles of Open Government Data, and others). Thanks for feedback to Gunnar, John Wonderlich, Carl Malamud, Joe Germuska, Kevin Lyons, and David Robinson. (They had a lot of great suggestions many of which I haven’t had the energy to follow through with yet.) The essay begins:

“Creating a well-informed public is a core value of representative government. It is a prerequisite for ensuring the best representatives are elected and a crucial component of government oversight—as well as being important in areas well beyond civics. This document speaks to why public government data (also called ‘public sector information’) is a valuable resource to society if put on the Web and shared freely with the public, and discusses how to go about doing it. We discuss technological considerations and end with sixteen guiding principles for best practices in open government data.”

Kevin Lyons, who works for the Nebraska State Legislature, began work on a best practices guide for the use of the PDF format. When is it appropriate, what to look out for. That’s up on the wiki and I’m sure your suggestions & revisions would be welcome.

JohnWonderlich: woot! Go Senate XML! (votes data now posted, in policy reversal) http://bit.ly/Il7hF

The big news lately is that the Center for Responsive Politics opened up their large database of normalized campaign contribution records under a Creative Commons license. I think this is more significant to the world of government transparency & technology than it might appear. Just around five years ago this world was quite different. Organizations like CRP were very much using technology to bring new insight to civics. That hasn’t changed. But organizations saw themselves as solitary entities whose primary mission was to provide a new direct-to-citizen service to the public. A web application, for instance. There’s no need for me to list off other examples — every advocacy and government transparency website was like that, to the best of my recollection. (Except maybe IMSP who seemed to be ahead of the pack.)

All that has changed, and I wish I could pinpoint exactly how that happened. The combination of “Web 2.0″ as a buzz-word and grassroots digital campaigning in 2004 probably had a lot to do with it. The Howard Dean presidential campaign got a boost (at least in terms of publicity if not poll numbers) from developers coming together to specialize the Drupal open source CMS for political campaigning (“CivicSpace”). That sent a message, even if no one quite recognized it at the time, that developers have a role to play in the world of civics and that cooperation was a viable model for getting things done. Not to say that the CivicSpace project invented this — I was working on GovTrack for a few years by that point and across the pond Tom Steinberg and the MySociety group had been thinking about open source civics for even longer. But I suspect, even in my own thinking, that CivicSpace crystalized some vague earlier notions of civic hacking.

The story isn’t over yet, though, because I don’t think any of this alone would have brought us to where we are today. Unfortunately, from this point forward I run the risk of giving too much credit to the things I know about and not enough credit elsewhere. Still, here’s how I see it. Four more things had to happen, independently. First, entrepreneur Mike Klein had to make a lot a lot a lot of money. Second, Dan Newman and David Moore had to build MAPLight.org and OpenCongress.org, respectively. These are, now, and especially were at the start, leading examples of how you can do really cool new things by mixing data sources (for MAPLight, mixing my GovTrack legislation data with campaign contribution data from CRP) or re-mixing data sources (for OpenCongress giving my legislation data a more social spin). Third, John Wonderlich had to start, quite by accident, the Open House Project — this was a crucial step in bridging the technology world with staffers for congressmen, especially with Speaker Pelosi’s office. The fourth bit was that Ellen Miller and Micah Sifry had to put it all together and form the Sunlight Foundation: funding from Mike going to two great technology projects (IMO these are Sunlight’s most important grantees) and a policy arm with teeth because of its pragmatic approach to connecting with policymakers.

That’s pretty much it, because from there things just make sense. Sunlight recruited great staff and steamrolled through the open government world stamping out the idea that each open government group should be in its own little world — by funding interaction, in a sense.

The expectations for government transparency advocacy changed. Groups had to walk the walk a bit more by sharing and collaborating. So now besides CRP’s data being opened up for anyone to remix we have the Taxpayers earmark data, the Sunlight Labs API, the MAPLight API, and probably several more databases. The New York Times API probably owes some of its inspiration to these changing expectations too. So it’s a whole new world now of not just open governenment, and not even open government data, but open government transparency advocacy data. (Is there a catchier name for that?)

Watch a video of my talk at the Free Culture Conference last year on Civic Hacking. (Text and slides here.) It was my best talk yet. I’ve got another good one (if I do say so myself) coming up at CITP’s Studying Society in a Digital World conference in a few weeks at Princeton.

Announcing: HackingCongress.org
The intersection of civics & technology

http://www.hackingcongress.org/

Our community is growing rapidly these days. And while TransparencyCamp gave us a physical place to come together a few weeks ago, we’re still a little nomadic in the online world.

We’re also a very diverse group. The fact that we all often have to cross-post to the same set of lists indicates that we’ve got great inner communities that focus separately on coding, policy, social media, etc.

HackingCongress.org is meant to be a neutral-ground home for the coder community in the open government world. Really, it’s just a links page. But it’s a links page with a nice Drupal theme you can proudly point to and say “this is my movement”. “Hacking” is, of course, a word with several meanings. In the programming world it is very much a positive term meaning something like “creative programming”.

The site is running Drupal and anyone that creates an account can edit any content on the site. So, it’s basically a new wiki.

Right now you can find:

Community
———

Links to the primary convergence locations for this community, the Sunlight Labs and PoliParsers mail lists, the IRC channel #transparency, the Planet oGosh blog aggregator, the oGosh Facebook group, and the Upcoming Transparency Events page on the OpenCongress wiki.

Links to all of the other mail lists for our community (all of the one’s I’ve mailed here and some others).

Data & APIs
———–

Then beginnings of a list of the databases and APIs that are available for government transparency data. If you’re a data source, add yourself to the list or make sure I got your entry correct, please.

Projects
——–

Links to ongoing projects broken down by type-

– Open-source coding projects like OpenCongress and Sunlight’s
Fifty States.

– Policy projects like Open House/Senate.

– Wiki projects like the new Wired gov data wiki.

It was everything I could come up with quickly. I’ll be adding more as I see them, but feel free to add your own project.

#transparency
————-

Using a Drupal module you can enter the community’s IRC channel #transparency through the website.

Blog Aggregator
—————

Recently I announced Planet oGosh, an aggregator bringing together a whole bunch of blogs in the open government tech community. I’m changing the URL to planet.hackingcongress.org.

Final Notes
———–

Thanks to Kendall Clark for donating the domain name.

There’s a wacky thread on the Open House List of poems for transparency, so I gave it a try. (In fairness, I should say I used an electronic pronunciation dictionary to find some of the rhymes.)

There once was a man named Mike Honda,
A congressman us geeks are quite fond ‘a,
In markup sessions takes on the chairman, a hulk,
so that we the people can get our data in bulk.

His friend maverick Joe likes transparency too,
Senate votes in XML he says long overdue,
At party politics he snorts,
Because the public should see those CRS reports.

And last we hear of the executive’s new plan,
For a CTO and CIO…
…perhaps YesWeScan?