Mark J. Headd is an experienced voice, mobile and web application developer who has been certified as a VoiceXML Application Developer by the VoiceXML Forum. He currently works as a Senior Application developer for Tele-Works, Inc., which develops IVR solutions and software for local government across the country. He holds a Master’s degree in Public Administration from the Maxwell School of Citizenship and Public Affairs at Syracuse University, and is a former adjunct instructor at the University of Delaware teaching a course in electronic government. He served for three years as the chief policy and budget advisor for the State of Delaware’s Department of Technology and Information. He has also served as Director of the Delaware Government Information Center and as Technology Adviser to former Delaware Governor Thomas Carper. Mark has built open source solutions using open government data and APIs for the District of Columbia, the Sunlight Foundation, the New York State Senate, and the cities of New York and Toronto. Follow me on Twitter. Friend me on Facebook. Join my LinkedIn Network.

The case for open transit data

This is an awesome short film from StreetFilms.org that convincingly lays out the case for open transit data. Later this year, the State of Delaware will – for the first time ever – release all of its transit data in open formats. This is the result of a bill introduced this past legislative session by State Senator Bethany Hall-Long.

The opposite of open government

There has been some pretty good discussion lately going around the Interwebs about what Gov 2.0 and open government looks like. I can’t say that I agree with everything that has been thrown out there with a Gov 2.0 label on it, but I can say without equivocation that this is the opposite of OpenGov and Gov 2.0.

A ‘glass half full’ view of government app contests

An increasing number of people are starting to suggest that the concept of the “app contest” (where governments challenge developers to build civic applications) is getting a bit long in the tooth.

There have been lots of musings lately about the payoff for governments that hold such contests and the long term viability of individual entries developed for these contests. Even Washington DC – the birthplace of the current government app contest craze – seems the be moving beyond the framework it has employed not once, but twice to engage local developers.

Building an Open311 application

Earlier this year, I had an idea to build a Twitter application that would allow a citizen to start a 311 service request with their city.

At the time, there was no way to build such an application as no municipality had yet adopted a 311 API that would support it (although the District of Columbia did have a 311 API in place, it did not – at the time – support the type of application I envisioned).

That changed recently, when San Francisco announced the deployment of their Open311 API. I quickly requested an API key and began trying to turn my idea into reality.

What’s old is new: How citizens communicate with government

Social media enthusiasts (myself included) let out a big huzzah recently at the results of a study conducted by the Pew Internet and American Life Project entitled Government Online.

The report, like a similar one several years ago, looks at how citizens communicate and interact with their government. This study focused specifically on online contact with government, the use of social media to interact with government and citizen use of open government data.

Gov 2.0 guide to 311 and Open311

311 is an abbreviated dialing designation set up for use by municipal governments in both the U.S. and Canada. Dialing 311 in communities where it is implemented will typically direct a caller to a call center where an operator will provide information in response to a question, or open a service ticket in response to report of an issue. The difference between 311 and other abbreviated dialing designations (like 911) can be summed up by a promotional slogan for the service used in the City of Los Angeles: “Burning building? Call 911. Burning question? Call 311.”

OpenGov APIs: Interfacing with Open Government

There has been lots of good talk (and a good deal of action) lately around open government APIs (Application Programming Interface) at events like Transparency Camp, Where 2.0 and on the Twitters.

So, as a prelude to a talk I’ll be giving at eComm next month, I wanted to write a post surveying the landscape of recent government API developments, and also to describe evolving efforts to construct standards for government APIs.

Email RSS Twitter Facebook YouTube Google Buzz

Email updates

Photos

Partners

Sustainable Websites Gov 2.0 Radio OpenGovWest GovTwit Gov 101 Radio