Posted on 12-20-2011
The FCC just launched a new platform that allows anyone to create, save and manage a customized page, built from widgets that pull content from FCC APIs, called MyFCC.
At first glance MyFCC might look like just another dashboard or start page, but it goes much further, as an API curation platform.
To understand, you have to go back to the beginning and see the scope of the problem being solved. To deliver on its promise for a more open government, the FCC didn't just want a new website, they needed a platform. To do this the FCC embraced an API-driven methodology while building their web site, meant to standardize the way they deliver information between internal groups, government agencies and with the public.
At the time, the managing FCC director Steve Van Roekel, partnered with Seabourne to architect a platform that could deliver on this vision.
The new FCC web site would start with Drupal, providing a content management system (CMS) that would allow the FCC to focus on getting a handle on its content, centralizing it, preparing it to be shared with other departments, agencies and the public. The federal government is drowning in content, so the entry, storage and management of this content was the first problem to solve, and an open-source platform like Drupal, was an ideal solution.
The new Drupal web site provided public access to the content, but the FCC needed to allow sharing of content with other departments, agencies and allow the public to get at the raw data for re-use.
"Everyone is talking about opening up data with APIs, to me it makes more sense to focus on opening up content using APIs.", says Mike Reich, owner of Seabourne.
So Seabourne developed the Content API module for Drupal, providing a plug-and-play API, not just for the FCC website, but for any Drupal driven website.
Then in April, the FCC launched their API driven content platform, stating that “Everything should be an API”. In doing so the FCC did two very significant things:
- Got control over their content using an open-source content management tool
- Made their content accessible inter-department, inter-agency and with the public using APIs
Now with MyFCC the FCC is providing a dashboard that allows anyone to curate content that is made available via the FCC’s API. Centralized content, opened up with APIs, bundled with curation tools opens up lot of potential for data journalists, analysts, scientists and other average users to derive deeper meaning from FCC operations.
All of this potential is made possible through a healthy dose of open source Drupal CMS, open source Drupal modules, open data, and open APIs. That is a lot of open, and shows the commitment of the FCC.
I sat down with Mike, while in DC in October, when he first introduced me to Cumula , the framework that drives MyFCC. During their work with the FCC, they have been committing the Cumula framework to Github, planting the seeds for a much larger vision of what the framework could do.
Cumula has the potential to act as curation platform for any single or group of APIs. The MyFCC implementation is very tailored to serving up the FCC content, but the platform can act as a visual builder and dashboard for any topical area. For example, the platform could be setup with widgets that pull medical content from various health, science and medical APIs, allowing users to create custom dashboards around the medical information most important and relevant to them.
Cumula is to API curation as Apigee console is to API exploration, Google API Discovery Service is to API discovery, and Swagger is to interactive API documentation. It has the potential to be the platform that the world uses to discover, pull, curate and make sense of the flood of content and data we are only just beginning to drown in, with this new API driven economy.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- My Discussion Today With 6 Hypermedia Leaders At API-Craft in Detroit
- Getting To Know Jørn Wildt For The API Craft 2014 Detroit Hypermedia Panel
- Hypermedia Feels Like We Are Still Learning To Communicate With APIs
- Getting To Know Markus Lanthaler For The API Craft 2014 Detroit Hypermedia Panel
- Getting To Know Kevin Swiber For The API Craft 2014 Detroit Hypermedia Panel
- Getting To Know Steve Klabnik For The API Craft 2014 Detroit Hypermedia Panel
- New Indix API KickStart Program Reduces Costs For Developers
- Getting To Know Mike Kelly For The API Craft 2014 Detroit Hypermedia Panel
- A Shared, Distributed Experience(Metrics) Layer For The API Driven Application Stack
- Showcasing Your API Integrations With Other Platforms
- Increasing The Focus On APIs In Higher Education Is Important
- Getting To Know Mike Amundsen For The API Craft 2014 Detroit Hypermedia Panel
- The New StrongLoop API Server Provides A Look At Future Of API Deployment
- Models For API Driven Startups Built Around Public Data
- Will You Add Me To API Evangelist And How To Spot The Cool Kids
- When I Remix APIs Using Swagger How Do I Deal With Authentication Across Multiple APIs
- It Takes A Team Of Evangelists To Raise An API
- Support For Only Two Creative Commons Licenses In The API Commons
- Machine Readable Terms of Service Didn't Read Applied To APIs Via APIs.json
- API Deployment For Non-Developers Using Zapier, Google Docs, and APISpark
- State of Hypermedia Today @ API Craft In Detroit
- Need A Formal API Standard For Your Government Agency? Fork 18Fs, And Make It Your Own!
- CORS Makes Your API Portable And Remix-able
- Chief Data Officer Needs To Make The Department Of Commerce Developer Portal The Center Of API Economy
- An API Definition As The Truth In The API Contract