API is a Key Element to Foster Data Based Innovation

-

 

PI First Manifesto

This is a well written manifesto from David Thoumas at OpenDataSoft proclaiming that the ODS strategy will always be API [First]. Below I have slightly edited the content written by David. I want to bring attention to the fine work this company does and why I and my company, BaleFire Global have such high regard for what they do:

At OpenDataSoft, David and team are building and operating a cloud based data management platform. This platform is built 'API first'. This means that any feature that can be accessed from the portal is also available as an API call. The portal is itself the first consumer of the API. Available APIs (source) include:

  • Dataset catalog APIs (keyword and faceted search of datasets within the catalog).
  • Dataset APIs (search within dataset records, geo clustering of geo dataset records, numerical aggregations of dataset records).       David Thoumas from OpenDataSoft
So, not only can one fetch raw data from the portal through API calls but one can also access high level features such as geo clustering and analytics to directly fuel advanced usages on any kind of devices. This makes it extremely easy for an application developer to quickly build a first MVP without having to build any back-end.

API must Support Standards


While APIs are a key feature of Open Data portals, one must not forget a major caveat: potential lack of interoperability. While some advanced features can still be made available through non standardized proprietary APIs, it is key for a data platform to maximize its support of standards. In terms of message formats (JSON, GeoJSON, RSS, RDF...), of protocols (REST, OData...) and security frameworks (OpenId, OAuth, SAML...). Supporting standards is the only way to get the developers community eager to use data portals APIs.

Another good property of "API first" development is that it encourages the development of reusable frameworks based on these APIs. Indeed, an Open Data portal shouldn't exclusively target experienced developers. It should also give to any citizen the possibility to simply reuse Web components, to build their own dashboards and data visualizations.

In Conclusion

  • API [First] development shall be mandatory.
  • Developing and supporting standards will become more and more important.
  • Providing tools and frameworks to ease the reuse of datasets exposed on an Open Data portal is also a key factor of success of an Open Data policy.

Comments

Post a Comment

Popular posts from this blog

Podcast: Open Data Discussions with Anthony Fung

-
Image
A look back at Virginia’s 4 years of data innovation with Anthony Fung, Deputy Secretary of Technology for the Commonwealth of Virginia  Welcome to the OpenDataSoft Leadership Podcast Series, “Open Data Discussions”. Each month, Jason Hare, our Open Data Evangelist, features a different open data program around the country to discuss what has made it successful. These examples will provide insights and strategies that you can implement in your own city. We had the pleasure of welcoming Anthony Fung, Deputy Secretary of Technology for the Commonwealth of Virginia for the fifth podcast in our series. Anthony discussed various subjects, including: What role does open data play in policymaking at the state level in Virginia? Does his department work on ensuring open data quality? What are some of the steps he makes in ensuring sound data governance? How did Virginia come up with this technology and engagement solutions?  How, for example, did yo
Read more

Open Data Licensing

-
Image
Everything you wanted to know but you were afraid to ask. Making data open and available is not just about choosing a format or having an API. A poor choice in your license can prevent people from using them. A traditional open license reassures potential users that their work on the data will be useful in the long run. So, what license should you pick for your data to be broadly used? There are a few things to consider. Choosing a license for your open data can usually be one of the biggest challenges for an open data project. There are plenty of licenses available for your data. Choosing one mostly depends on the usage and reach you want to give to your project. CHOOSE A LICENSE: BASED ON NATIONAL, INTERNATIONAL AND LOCAL STATUTES IN ADDITION TO REUSE It should be noted that different parts of the world use data licensing terms differently. In the US, works in the “public domain” are works are not covered by intellectual property rights, such as copyright. The copyright mig
Read more

AN OPEN DATA POLICY FOR NORTH CAROLINA: COMING SOON?

-
Image
All parts of North Carolina will benefit from open data legislation. FOR THE BETTER PART OF TWO DECADES, I’VE WORKED TO OPEN UP NORTH CAROLINA’S DATA. I’ve been a public servant at Durham Public Schools and the Department of Energy. I have been an onsite consultant for the Cities of Raleigh, Durham as well as the Towns of Cary and Chapel Hill. I’ve been on teams serving state agencies and local governments. I’ve witnessed dozens of open data projects both locally and abroad. All of these projects share crucial steps and goals in common. First, by transforming public documents from disconnected PDFs into machine-readable data, by applying the right open formats, we can liberate public information from the repositories where it used to require manual review. Insights become instant. Second, by publishing machine-readable data compilations online, for everyone to use, we can crowdsource those insights. Citizens and companies and the media can scrutinize. Even better, when a government age
Read more