The debate over RSS never seems to end. 2011 kicked off with a widely read post predicting the decreasing influence of RSS in 2010. There have been responses from Fred Wilson and GigaOM that argue it is still relevant today. We believe that it continues to be a solid mechanism for web sites to aggregate data from multiple sources, as displayed by the 121 RSS APIs in our directory. In this post, we’ll look at RSS beyond blog syndication.
JSON has been winning over developers and API providers over the last year due to its lightness and simplicity. There’s no denying that XML has fallen out of favor. It might be safe to assume that RSS (which is basically XML) might have even less takers. One major upside to RSS is that it has standard fields that are generic enough to work for many uses. What’s especially interesting is that the APIs in our directory that output RSS span across several categories. This goes to show that the uses of RSS are much beyond simply blog aggregation.
RSS, and more specifically its location extension GeoRSS, is popular amongst mapping APIs. It is also used by San Francisco Bay Area transit company in the BART API, citizen engagement platform SeeClickFix’s API and RSS is an option for output from real-time push Kwwika API.
Despite the wide number of uses outside of blog aggregation, there’s tremendous momentum behind JSON. With this trend in mind, do you see API vendors continuing to support RSS as a data format in the long run?
Icon by Equipe Teia MG