Skip Navigation

Federal Communications Commission

English Display Options

Event

.Gov Developer Meet-Up

April 16, 2012, 11:00 AM - 3:00 PM EDT
Room TW-C305, 445 12th Street S.W., Washington, DC

Problem:

The Administrations Open Government Directive has ushered a significant increase in data publication from .Gov’s. What was once just data download, has given way to direct access to many federal agencies data coffers. Federal agency’s are increasingly making data available through application programming interfaces (APIs) and web services. There are more than 25 agencies with developer resources on their sites (aka /developer pages). However, there is no comprehensive forum for the developer community to collectively see the breath of these resources. In order to really see the benefits of open government, APIs need to be consumed by the developer community.

Solution: .gov developer meet-up

The FCC hosted a .gov developer meet-up on April 16, 2012 from 11:00 AM EST- 3:00PM in the Commission meeting room. This event was designed to expose the developer community to most of the .gov /developer resources currently in production, and this event gave .gov producers the opportunity to expose their resources to the open developer community.

Each of the federal agency’s with /developer pages were given less than 10 minutes to present their API resources and assets as ignite type sessions. Developers were invited to be in the audience, ask questions interact with the core producers and see the whole .gov/developer community. This meet-up concluded with a general session where developers interacted with the principles for each of these agencies, wrote code against these APIs, or presented their use cases so government can understand how their assets are being consumed from the outside.

Related Materials

 

close
FCC

You are leaving the FCC website

You are about to leave the FCC website and visit a third-party, non-governmental website that the FCC does not maintain or control. The FCC does not endorse any product or service, and is not responsible for, nor can it guarantee the validity or timeliness of the content on the page you are about to visit. Additionally, the privacy policies of this third-party page may differ from those of the FCC.