I’m a big fan of the Open Government Directive that recently came out of the Obama Administration. I’ve spent the past 10 years of my life trying to help government improve transparency, participation, and collaboration, and this Directive speaks to what I care about and what my company, GovDelivery, has been trying to facilitate. We’re launching a lot of resources in support of the Directive and have made embracing the Directive the theme of our first open Proactive Communication Roundtable of the year on February 9th in Washington, DC.
One of the components of the Directive I appreciate is an “after the slash” requirement for agencies to post their Open Government plans and progress at a specific URL– in this case, “www.agency.gov/open.” It’s a novel idea, but it’s something that has been used well by the administration in other areas– notably with Recovery (see: www.dol.gov/recovery) for an example. Individual agencies use this concept now in other areas, but it’s something that should be rolled out much more broadly.
Here are some ideas:
/data Data feeds that an agency offers
/socialmedia (Check out this example from the Navy)
/widgets (CDC example)
/emailupdates (FEMA example)
/metrics (Another CDC example)
However, the most important link should be /mission. Every website should have the mission or purpose of the website with a link to the metrics being used to track success as well as the mission of the agency. With all the “buzz” around new technologies and initiatives, I’ve been trying to go back to the importance of mission when we look at any agency’s technology needs. I put a longer (more GovDelivery-centric) blog entry about this up on our client blog here.
These high profile initiatives (Recovery and now Open Government) have introduced this easy way of organizing websites to be more consistent across government. Let’s institutionalize this concept across all levels of government and make sure mission is included. I see clear benefits to search engines, consumers of information across many government agencies, anyone looking for best practices, and others. One current example of the benefit is that the Sunlight Foundation has put out an automated check of whether each agency has an “Open” page up and running. These types of useful indexes of online activities and resources at agencies will be commonplace if “after the slash” standardization becomes widespread.
What do you think? What key items would you include after the slash?
This blog entry originally appeared in our Reach the Public blog.
Thanks. That makes a lot of sense.
I don’t know about /contact. I’m just not sure people are going to start typing xxx.gov/contact.
Now, having contact info available is a must, and we’ve had that as a standard on every EPA Web page since 2002.
One thing I didn’t get into in the blog… I think there would be a great benefit of the /metrics /contact /mission /whatever pages in that, eventually, each page can have an XML feed with updates that would be machine readable so any outside service that wants could grab updates from across all fed websites and aggregate them.
So, the fact that you have the contact page is great, but until everyone has the info. in a consistent location, automated aggregation won’t work. Does this benefit make sense and seem real to you?
Yes, that makes more sense.
Although I still think the “sweep it all up” concept is going to be very popular with a very (possibly vanishingly) small audience. Did I just say that out loud?
I do think there is huge value to XML feeds and standardization of critical/repetitive info. Craigslist has held out with XML forever to great advantage for people who set up feeds.
Your blog is tagged ‘web management, so i thought i’d post this reply regarding the Semantic Web and Internet of Things’.
An Orwellian world for Big Brother
The World Government Global Database
Union Now, the U.N. and World Government
You can also follow info/updates on the semantic web
and internet of things
I’ve also started this thread on govloop