{"id":767,"date":"2006-01-30T10:29:03","date_gmt":"2006-01-30T17:29:03","guid":{"rendered":"http:\/\/www.faganfinder.com\/wp\/2006\/01\/30\/767\/"},"modified":"2007-09-10T05:57:37","modified_gmt":"2007-09-10T12:57:37","slug":"google-toolbar-button-api-follow-up","status":"publish","type":"post","link":"https:\/\/faganm.com\/blog\/2006\/01\/30\/767\/","title":{"rendered":"Google Toolbar Button API Follow-up"},"content":{"rendered":"\n

In my last post was my initital reaction to this new API from Google. It’s not surprising that I’m worried about Google’s plans here, as their record on XML cooperation hasn’t been all that stellar. I haven’t fully looked into it yet, but I had noticed Google’s absence from a new standardization effort; Retailers, Engines Want Standard for Product Description<\/a> (via Gary<\/a>) lists MSN, Yahoo!, and others.<\/p>\n

Anyhow, getting down to the real point, I’ve decided to completely skip over “What Google Should Have Done,” and go right ahead to “What Google Should Now Do.” Save myself the wasted keystrokes.<\/p>\n

Step 1: Fix Feed Refresh Interval<\/h3>\n

Remove the refresh-interval<\/code> attribute from <feed><\/code>. Add it to RSS\/Atom in a namespace. This shouldn’t really change anything. This has nothing to do with OpenSearch by the way, it’s just my general opinion on XML – extend an existing format rather than creating a new one.<\/p>\n

After I started writing this, DeWitt posted his take on it all: Google Toolbar, Custom Buttons, and OpenSearch<\/a>. It includes a lot of what I was going to say, so I will continue my comments as a reply to his post.<\/strong><\/p>\n

A final note, for anyone that’s counting… this makes at least four different Google products that are RSS\/Atom readers (Google Reader, Google Toolbar, Google Personalized Homepage, Google Desktop). I hope they’re all using the API that the Google Reader team has been developing.<\/p>\n","protected":false},"excerpt":{"rendered":"

In my last post was my initital reaction to this new API from Google. It’s not surprising that I’m worried about Google’s plans here, as their record on XML cooperation hasn’t been all that stellar. I haven’t fully looked into … 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":[12,248,171,137,247,204],"class_list":["post-767","post","type-post","status-publish","format-standard","hentry","tag-google","tag-googletoolbar","tag-opensearch","tag-standards","tag-toolbar","tag-xml"],"_links":{"self":[{"href":"https:\/\/faganm.com\/blog\/wp-json\/wp\/v2\/posts\/767","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=767"}],"version-history":[{"count":0,"href":"https:\/\/faganm.com\/blog\/wp-json\/wp\/v2\/posts\/767\/revisions"}],"wp:attachment":[{"href":"https:\/\/faganm.com\/blog\/wp-json\/wp\/v2\/media?parent=767"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/faganm.com\/blog\/wp-json\/wp\/v2\/categories?post=767"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/faganm.com\/blog\/wp-json\/wp\/v2\/tags?post=767"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}