Comments on: Beginning of the end for open web data APIs? http://www.megginson.com/blogs/quoderat/2006/12/18/beginning-of-the-end-for-open-web-data-apis/ XML and the Web. Tue, 07 Oct 2008 18:25:50 +0000 http://wordpress.org/?v=2.5.1 By: john beck http://www.megginson.com/blogs/quoderat/2006/12/18/beginning-of-the-end-for-open-web-data-apis/#comment-24315 john beck Mon, 19 Mar 2007 08:06:38 +0000 http://www.megginson.com/blogs/quoderat/archives/2006/12/18/beginning-of-the-end-for-open-web-data-apis/#comment-24315 Google doesn’t have a REST API to replace it. Instead, something more important is happening, and it could be that REST, WS-*, and the whole of open web data and mash-ups all end up on the losing side. Google doesn’t have a REST API to replace it. Instead, something more important is happening, and it could be that REST, WS-*, and the whole of open web data and mash-ups all end up on the losing side.

]]> By: seo http://www.megginson.com/blogs/quoderat/2006/12/18/beginning-of-the-end-for-open-web-data-apis/#comment-24244 seo Sat, 17 Mar 2007 05:37:39 +0000 http://www.megginson.com/blogs/quoderat/archives/2006/12/18/beginning-of-the-end-for-open-web-data-apis/#comment-24244 I'm really surprised there hasn't been a bigger backlash against this. Where is the outrage? I’m really surprised there hasn’t been a bigger backlash against this. Where is the outrage?

]]> By: The Business of Ajax - Google’s Ajax Search API http://www.megginson.com/blogs/quoderat/2006/12/18/beginning-of-the-end-for-open-web-data-apis/#comment-23484 The Business of Ajax - Google’s Ajax Search API Thu, 01 Mar 2007 14:16:35 +0000 http://www.megginson.com/blogs/quoderat/archives/2006/12/18/beginning-of-the-end-for-open-web-data-apis/#comment-23484 [...] Of course there are many other ways of presenting search results. Many of the more interesting.ways to present the data reorder the results according to other criteria or third-party data (like other search results), or even dispense with a linear order. Now if you want to pull in search data and manipulate it in this way, you’re going to have to use the Yahoo! REST API’s. But will Yahoo! follow suit and get rid of their general API’s in favor of brand-preserving Ajax widgets? Dave Megginson doesn’t think so, but sees some clouds on the horizon. [...] [...] Of course there are many other ways of presenting search results. Many of the more interesting.ways to present the data reorder the results according to other criteria or third-party data (like other search results), or even dispense with a linear order. Now if you want to pull in search data and manipulate it in this way, you’re going to have to use the Yahoo! REST API’s. But will Yahoo! follow suit and get rid of their general API’s in favor of brand-preserving Ajax widgets? Dave Megginson doesn’t think so, but sees some clouds on the horizon. [...]

]]> By: Ajaxian » The Business of Ajax - Google’s Ajax Search API http://www.megginson.com/blogs/quoderat/2006/12/18/beginning-of-the-end-for-open-web-data-apis/#comment-22577 Ajaxian » The Business of Ajax - Google’s Ajax Search API Thu, 15 Feb 2007 16:40:29 +0000 http://www.megginson.com/blogs/quoderat/archives/2006/12/18/beginning-of-the-end-for-open-web-data-apis/#comment-22577 [...] Of course there are many other ways of presenting search results. Many of the more interesting.ways to present the data reorder the results according to other criteria or third-party data (like other search results), or even dispense with a linear order. Now if you want to pull in search data and manipulate it in this way, you’re going to have to use the Yahoo! REST API’s. But will Yahoo! follow suit and get rid of their general API’s in favor of brand-preserving Ajax widgets? Dave Megginson doesn’t think so, but sees some clouds on the horizon. [...] [...] Of course there are many other ways of presenting search results. Many of the more interesting.ways to present the data reorder the results according to other criteria or third-party data (like other search results), or even dispense with a linear order. Now if you want to pull in search data and manipulate it in this way, you’re going to have to use the Yahoo! REST API’s. But will Yahoo! follow suit and get rid of their general API’s in favor of brand-preserving Ajax widgets? Dave Megginson doesn’t think so, but sees some clouds on the horizon. [...]

]]> By: sockdrawer » Blog Archive » Always beta? http://www.megginson.com/blogs/quoderat/2006/12/18/beginning-of-the-end-for-open-web-data-apis/#comment-19827 sockdrawer » Blog Archive » Always beta? Wed, 10 Jan 2007 19:53:26 +0000 http://www.megginson.com/blogs/quoderat/archives/2006/12/18/beginning-of-the-end-for-open-web-data-apis/#comment-19827 [...] Funny, but hardly the point as one of the comments on his post points out, referring to David Megginson who asks, rather more importantly, if this is the Beginning of the end for open web data APIs? Pointing out that, in this case, the alternative to the SOAP API is a set of Ajax widgets, David’s argument is that this could become a common business approach - the data is not directly exposed, and deploying Ajax components is popular to many because it is so easy to do. [...] [...] Funny, but hardly the point as one of the comments on his post points out, referring to David Megginson who asks, rather more importantly, if this is the Beginning of the end for open web data APIs? Pointing out that, in this case, the alternative to the SOAP API is a set of Ajax widgets, David’s argument is that this could become a common business approach - the data is not directly exposed, and deploying Ajax components is popular to many because it is so easy to do. [...]

]]> By: Un peu de lecture 03 at Aurélien Pelletier’s Weblog http://www.megginson.com/blogs/quoderat/2006/12/18/beginning-of-the-end-for-open-web-data-apis/#comment-19209 Un peu de lecture 03 at Aurélien Pelletier’s Weblog Mon, 01 Jan 2007 14:04:11 +0000 http://www.megginson.com/blogs/quoderat/archives/2006/12/18/beginning-of-the-end-for-open-web-data-apis/#comment-19209 [...] Google a “déprécié” son API de recherche SOAP et c’est Dave Megginson qui nous livre la meilleur analyse: Beginning of the end for open web data APIs? Ce n’est pas une victoire de REST sur SOAP/WS-* mais le début de la fin du web as a platform, une composante importante du Web 2.0. [...] [...] Google a “déprécié” son API de recherche SOAP et c’est Dave Megginson qui nous livre la meilleur analyse: Beginning of the end for open web data APIs? Ce n’est pas une victoire de REST sur SOAP/WS-* mais le début de la fin du web as a platform, une composante importante du Web 2.0. [...]

]]> By: Jon http://www.megginson.com/blogs/quoderat/2006/12/18/beginning-of-the-end-for-open-web-data-apis/#comment-19037 Jon Tue, 26 Dec 2006 04:15:18 +0000 http://www.megginson.com/blogs/quoderat/archives/2006/12/18/beginning-of-the-end-for-open-web-data-apis/#comment-19037 Our response to this is the <a href="http://evilapi.com/" rel="nofollow">EvilAPI</a> and <a href="http://evilrss.com/" rel="nofollow">EvilRSS</a> Our response to this is the EvilAPI and EvilRSS

]]> By: Quoderat » Yahoo stands firm behind its search API http://www.megginson.com/blogs/quoderat/2006/12/18/beginning-of-the-end-for-open-web-data-apis/#comment-19005 Quoderat » Yahoo stands firm behind its search API Sat, 23 Dec 2006 15:24:50 +0000 http://www.megginson.com/blogs/quoderat/archives/2006/12/18/beginning-of-the-end-for-open-web-data-apis/#comment-19005 [...] Early in the week, I posted about the end of the Google search API, and speculated that — since everyone else tends to copy Google — it might be the start of a general trend away from open data APIs and in favour of server-side AJAX widgets. In response, Amit Kumar of Yahoo sent me an e-mail message (after failing to get past Spam Karma in the comment system for my blog): [...] [...] Early in the week, I posted about the end of the Google search API, and speculated that — since everyone else tends to copy Google — it might be the start of a general trend away from open data APIs and in favour of server-side AJAX widgets. In response, Amit Kumar of Yahoo sent me an e-mail message (after failing to get past Spam Karma in the comment system for my blog): [...]

]]> By: Venture Beat Contributors » The Google API kerfuffle, and what it means for start-ups http://www.megginson.com/blogs/quoderat/2006/12/18/beginning-of-the-end-for-open-web-data-apis/#comment-18996 Venture Beat Contributors » The Google API kerfuffle, and what it means for start-ups Sat, 23 Dec 2006 01:13:45 +0000 http://www.megginson.com/blogs/quoderat/archives/2006/12/18/beginning-of-the-end-for-open-web-data-apis/#comment-18996 [...] (Editor’s note: Some people, it seems, are steamed about changes Google has made to the way it lets outside developers tap into its search and ad platforms. We asked Rob Drapkin to write about the changes in Google’s ad platform. These changes are different Google’s separate changes to its search platform, where you can see an example of a complaint here.) [...] [...] (Editor’s note: Some people, it seems, are steamed about changes Google has made to the way it lets outside developers tap into its search and ad platforms. We asked Rob Drapkin to write about the changes in Google’s ad platform. These changes are different Google’s separate changes to its search platform, where you can see an example of a complaint here.) [...]

]]> By: Robert Sayre http://www.megginson.com/blogs/quoderat/2006/12/18/beginning-of-the-end-for-open-web-data-apis/#comment-18994 Robert Sayre Fri, 22 Dec 2006 18:59:46 +0000 http://www.megginson.com/blogs/quoderat/archives/2006/12/18/beginning-of-the-end-for-open-web-data-apis/#comment-18994 Well, I think the limitation is basically the same one Google has always had: "no bots". Regarding the API traffic, it looks like a variation on JSON-P. Basically, you do this: --------------------------- /* write a callback function */ function myJSONCallback(aJSON) { alert(aJSON) } /* append a script element to the document */ var myScript = document.createElement("script"); myScript.src = "http://api.example.com/makeArray?elements=3&callback=myJSONCallback"; --------------------------- The browser sends a GET to request the script src, and this can be any host. The body of the request looks like this: myJSONCallback(["","",""]); The contents of the parens are a JSON object literal. Well, I think the limitation is basically the same one Google has always had: “no bots”.

Regarding the API traffic, it looks like a variation on JSON-P. Basically, you do this:

—————————

/* write a callback function */
function myJSONCallback(aJSON) { alert(aJSON) }

/* append a script element to the document */
var myScript = document.createElement(”script”);
myScript.src = “http://api.example.com/makeArray?elements=3&callback=myJSONCallback”;

—————————

The browser sends a GET to request the script src, and this can be any host. The body of the request looks like this:

myJSONCallback(["","",""]);

The contents of the parens are a JSON object literal.

]]>