{"id":783,"date":"2006-04-20T06:10:36","date_gmt":"2006-04-20T13:10:36","guid":{"rendered":"http:\/\/www.faganfinder.com\/wp\/2006\/04\/20\/783\/"},"modified":"2007-10-10T05:13:50","modified_gmt":"2007-10-10T12:13:50","slug":"google-data-apis-protocol","status":"publish","type":"post","link":"https:\/\/faganm.com\/blog\/2006\/04\/20\/783\/","title":{"rendered":"Google Data APIs Protocol"},"content":{"rendered":"\n

Google Data APIs Protocol<\/a> – interesting move from Google. I (and others<\/a>) have thought for a while that combining OpenSearch<\/a>’s read<\/em> capabilities with the Atom Publishing Protocol’s write<\/em> capabilities would create a very powerful API, and that’s roughly what Google is doing here.<\/p>\n

It’s great to see the OpenSearch support (a bit – they’re using startIndex<\/code>, totalResults<\/code> and itemsPerPage<\/code>), but I’d like to see them using it more. Some of what they’re doing is contrary to how OpenSearch works (that’s not a problem per-say), as they’re using predefined query names such as q<\/code> and max-results<\/code> (and a folder<\/em> for categories) rather that allowing people to use whichever they want and then specify them in an OpenSearch Description<\/a> file.<\/p>\n

In that same vein, it would be nice to see them make use of autodiscovery, as Atom, RSS, OpenSearch, and others do. Upon first inspection I would say these autodiscovered documents could be OpenSearch Descriptions, but I may be wrong about that.<\/p>\n

One interesting thing to note is that they mention how startIndex<\/code> is 1-based (which is true), and then display an example with a value of “0″. Sounds like DeWitt is right<\/a>, it does need to handle 0-based numbers too; even Google is making that mistake.<\/p>\n

DeWitt brings up some other good points as well<\/a>.<\/p>\n

Via Niall<\/a>.<\/p>\n

Update: Joe Gregorio weighs in<\/a><\/ins><\/p>\n

Update 2: Marc Canter (one of my favourite bloggers) finds this linkworthy<\/a> \ud83d\ude09 although I’m always amazed at the spellings my name gets.
\n<\/ins><\/p>\n","protected":false},"excerpt":{"rendered":"

Google Data APIs Protocol – interesting move from Google. I (and others) have thought for a while that combining OpenSearch’s read capabilities with the Atom Publishing Protocol’s write capabilities would create a very powerful API, and that’s roughly what Google … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[142,159,274,12,171,275],"class_list":["post-783","post","type-post","status-publish","format-standard","hentry","tag-api","tag-atom","tag-gdata","tag-google","tag-opensearch","tag-rest"],"_links":{"self":[{"href":"https:\/\/faganm.com\/blog\/wp-json\/wp\/v2\/posts\/783","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/faganm.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/faganm.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/faganm.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/faganm.com\/blog\/wp-json\/wp\/v2\/comments?post=783"}],"version-history":[{"count":0,"href":"https:\/\/faganm.com\/blog\/wp-json\/wp\/v2\/posts\/783\/revisions"}],"wp:attachment":[{"href":"https:\/\/faganm.com\/blog\/wp-json\/wp\/v2\/media?parent=783"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/faganm.com\/blog\/wp-json\/wp\/v2\/categories?post=783"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/faganm.com\/blog\/wp-json\/wp\/v2\/tags?post=783"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}