<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Mashup Guide &#187; Google</title>
	<atom:link href="http://blog.mashupguide.net/category/google/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mashupguide.net</link>
	<description>A blog about Raymond Yee&#039;s Book Pro Web 2.0 Mashups: Remixing Data and Web Services</description>
	<lastBuildDate>Wed, 23 Feb 2011 13:35:50 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<image>
  <link>http://blog.mashupguide.net</link>
  <url>http://blog.mashupguide.net/favicon.ico</url>
  <title>Mashup Guide</title>
</image>
		<item>
		<title>Google Mashup Editor will be shut down</title>
		<link>http://blog.mashupguide.net/2009/01/18/google-mashup-editor-will-be-shut-down/</link>
		<comments>http://blog.mashupguide.net/2009/01/18/google-mashup-editor-will-be-shut-down/#comments</comments>
		<pubDate>Sun, 18 Jan 2009 22:31:07 +0000</pubDate>
		<dc:creator>raymond.yee</dc:creator>
				<category><![CDATA[Chapter 11]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Google Mashup Editor]]></category>

		<guid isPermaLink="false">http://blog.mashupguide.net/?p=151</guid>
		<description><![CDATA[	
	<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.title=Google+Mashup+Editor+will+be+shut+down&amp;rft.aulast=Yee&amp;rft.aufirst=Raymond&amp;rft.subject=Chapter+11&amp;rft.subject=Google&amp;rft.source=Mashup+Guide&amp;rft.date=2009-01-18&amp;rft.type=blogPost&amp;rft.format=text&amp;rft.identifier=http://blog.mashupguide.net/2009/01/18/google-mashup-editor-will-be-shut-down/&amp;rft.language=English"></span>
I'm sad about the announcement that Google is shutting down its Mashup Editor -- one reason being that I had spent a fair amount of effort writing about it in Chapter 11 of  my book.  Oh well.  The Google App Engine is touted as a suitable and more powerful alternative to the Mashup Editor -- [...]]]></description>
			<content:encoded><![CDATA[	
	<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.title=Google+Mashup+Editor+will+be+shut+down&amp;rft.aulast=Yee&amp;rft.aufirst=Raymond&amp;rft.subject=Chapter+11&amp;rft.subject=Google&amp;rft.source=Mashup+Guide&amp;rft.date=2009-01-18&amp;rft.type=blogPost&amp;rft.format=text&amp;rft.identifier=http://blog.mashupguide.net/2009/01/18/google-mashup-editor-will-be-shut-down/&amp;rft.language=English"></span>
<p>I'm sad about the announcement that <a href="http://googlemashupeditor.blogspot.com/2009/01/from-mashup-editor-to-app-engine.html">Google is shutting down its Mashup Editor</a> -- one reason being that I had spent a fair amount of effort writing about it in Chapter 11 of  my book.  Oh well.  The <a href="http://code.google.com/appengine/">Google App Engine</a> is touted as a suitable and more powerful alternative to the Mashup Editor -- but I have to agree with that the comment that the<a href="http://googlemashupeditor.blogspot.com/2009/01/from-mashup-editor-to-app-engine.html?showComment=1232005740000#c2317530692676025065"> simplicity of the Mashup Editor was a virtue</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.mashupguide.net/2009/01/18/google-mashup-editor-will-be-shut-down/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Learning about JavaScript libraries using the Google Ajax Libraries API</title>
		<link>http://blog.mashupguide.net/2008/11/25/113/</link>
		<comments>http://blog.mashupguide.net/2008/11/25/113/#comments</comments>
		<pubDate>Tue, 25 Nov 2008 17:22:50 +0000</pubDate>
		<dc:creator>raymond.yee</dc:creator>
				<category><![CDATA[AJAX]]></category>
		<category><![CDATA[Chapter 08]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Google AJAX Libraries API]]></category>

		<guid isPermaLink="false">http://blog.mashupguide.net/?p=113</guid>
		<description><![CDATA[	
	<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.title=Learning+about+JavaScript+libraries+using+the+Google+Ajax+Libraries+API&amp;rft.aulast=Yee&amp;rft.aufirst=Raymond&amp;rft.subject=AJAX&amp;rft.subject=Chapter+08&amp;rft.subject=Google&amp;rft.subject=Google+AJAX+Libraries+API&amp;rft.source=Mashup+Guide&amp;rft.date=2008-11-25&amp;rft.type=blogPost&amp;rft.format=text&amp;rft.identifier=http://blog.mashupguide.net/2008/11/25/113/&amp;rft.language=English"></span>
In Chapter 8 of my mashup book, I wrote Ideally there would be one obvious choice for an excellent JavaScript library, and everyone would use it. The current situation is that there are many JavaScript libraries, and it is not at all obvious how they compare. I was hoping that in the course of writing [...]]]></description>
			<content:encoded><![CDATA[	
	<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.title=Learning+about+JavaScript+libraries+using+the+Google+Ajax+Libraries+API&amp;rft.aulast=Yee&amp;rft.aufirst=Raymond&amp;rft.subject=AJAX&amp;rft.subject=Chapter+08&amp;rft.subject=Google&amp;rft.subject=Google+AJAX+Libraries+API&amp;rft.source=Mashup+Guide&amp;rft.date=2008-11-25&amp;rft.type=blogPost&amp;rft.format=text&amp;rft.identifier=http://blog.mashupguide.net/2008/11/25/113/&amp;rft.language=English"></span>
<p>In Chapter 8 of my mashup book, I wrote</p>
<ul> Ideally there would be one obvious choice for an  excellent JavaScript library, and everyone would use it. The current  situation is that there are many JavaScript libraries, and it is not at  all obvious how they compare.</ul>
<p>I was hoping that in the course of writing my book, I would have had an  opportunity to do my in-depth study of various JavaScript libraries (of  which there are many, judging from the table in the Wikipedia entry <a class="external" href="http://en.wikipedia.org/wiki/Comparison_of_JavaScript_frameworks">Comparison of JavaScript frameworks</a>).  I raised the question of how to choose a JavaScript library during <a class="external" href="http://blog.mashupguide.net/2008/11/13/preparing-for-a-panel-on-openajax/">a panel on OpenAjax</a> as a way of studying the implications of such initiatives as OpenAjax  -- that is, does OpenAjax make it easier to figure out what JavaScript  library to choose -- or does it allow one to pick and choose the best  parts from a whole range of libraries? These are questions I plan to  raise in my spring 2009 <a class="external" href="http://blog.mixingandremixing.info">Mixing and Remixing Information</a> course.</p>
<p>At any rate, I recently had a chance to take a closer look at <a class="external" href="http://code.google.com/apis/ajaxlibs/">AJAX Libraries API - Google Code</a>,  which is "a content distribution network and loading architecture for  the most popular, open source JavaScript libraries", which at present,  include:</p>
<ul>
<li>jQuery</li>
<li>jQuery UI</li>
<li>Prototype</li>
<li>script.aculo.us</li>
<li>MooTools</li>
<li>Dojo</li>
<li>SWFObject</li>
<li>Yahoo! User Interface Library (YUI)</li>
</ul>
<p>From a pedagogical point of view, the Google AJAX Libraries API, by providing a single common library call (<a class="external" href="http://code.google.com/apis/ajaxlibs/documentation/#googleDotLoad">google.load</a>)  simplifies getting set up with each of the libraries, which otherwise,  would require a different setup. Of course, there are reasons that you  might not want to depend on Google to host JavaScript libraries you use  -- but not having to take care of hosting these files yourself helps  beginners jump right in.</p>
<p>I'm pleased to see that <a class="external" href="http://developer.yahoo.com/yui/">The Yahoo! User Interface Library (YUI)</a> recently became part of the Google API.  I use that library in my course and in my book.  The <a class="external" href="http://googleajaxsearchapi.blogspot.com/2008/11/welcome-yui-scriptaculous-gets-fresh.html">post on Google AJAX Search API Blog announcing this inclusion</a> gave a short code example on how to use YUI with the Google AJAX  Libraries API -- it did not actually show any visible in the user  interface. Here I show to elaborate the example slightly to actually  show something visible in the UI.</p>
<p>To do so, you should take look at the <a class="external" href="http://developer.yahoo.com/yui/calendar/">YUI docs for the calendar widget</a> and understand a bit about what the YUILoader (<a class="external" href="http://developer.yahoo.com/yui/yuiloader/">Yahoo! UI Library: YUI Loader Utility</a> does. One thing to note is that <tt>google.load('yui', '2.6.0');</tt> creates an instance of a global YAHOO object. Secondly, YUILoader takes  care of loading the pieces of YUI required to use the widget that you  want to use -- see <a class="external" href="http://developer.yahoo.com/yui/calendar/#start">Getting Started</a> for more details.  You will also want to load in the default CSS to get started (through the line <tt>&lt;body class="yui-skin-sam"&gt;</tt>).  The modified code I came up with is:</p>
<pre>&lt;head&gt;
  &lt;script src="http://www.google.com/jsapi" type="text/javascript" charset="utf-8"&gt;&lt;/script&gt;
  &lt;script type="text/javascript" charset="utf-8"&gt;
  google.load('yui', '2.6.0');
  function init() {
    var loader = new YAHOO.util.YUILoader({
      require: ["button", "calendar"],
      base: "http://ajax.googleapis.com/ajax/libs/yui/2.6.0/build/",
      onSuccess: function() {
        // start playing with buttons and calendars!
        var cal = new YAHOO.widget.Calendar("calContainer");
        cal.render();
      }
    });
    loader.insert();
  }
  google.setOnLoadCallback(init);
  &lt;/script&gt;
&lt;/head&gt;
&lt;body class="yui-skin-sam"&gt;
  &lt;div id="calContainer"&gt;&lt;/div&gt;
&lt;/body&gt;</pre>
<p>which you can run at <a href="http://labs.mashupguide.net/doc/2008/11/google.ajaxlib.yui.eg.html">http://labs.mashupguide.net/doc/2008/11/google.ajaxlib.yui.eg.html</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.mashupguide.net/2008/11/25/113/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>mashups of Google Maps Street View?</title>
		<link>http://blog.mashupguide.net/2007/06/04/mashups-of-google-maps-street-view/</link>
		<comments>http://blog.mashupguide.net/2007/06/04/mashups-of-google-maps-street-view/#comments</comments>
		<pubDate>Mon, 04 Jun 2007 17:18:13 +0000</pubDate>
		<dc:creator>raymond.yee</dc:creator>
				<category><![CDATA[Chapter 13]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Google Maps]]></category>

		<guid isPermaLink="false">http://blog.mashupguide.net/2007/06/04/mashups-of-google-maps-street-view/</guid>
		<description><![CDATA[	
	<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.title=mashups+of+Google+Maps+Street+View%3F&amp;rft.aulast=Yee&amp;rft.aufirst=Raymond&amp;rft.subject=Chapter+13&amp;rft.subject=Google&amp;rft.subject=Google+Maps&amp;rft.source=Mashup+Guide&amp;rft.date=2007-06-04&amp;rft.type=blogPost&amp;rft.format=text&amp;rft.identifier=http://blog.mashupguide.net/2007/06/04/mashups-of-google-maps-street-view/&amp;rft.language=English"></span>
With pointers such as Greg Sadetsky's tidbits on how Google Map's Street View works in the browser (e.g., URLs of specific shots, a pointer to a Flare, an Actionscript decompiler), how long will we have to wait until we get mashups that give us a video tour of Berkeley using photos from Street View?]]></description>
			<content:encoded><![CDATA[	
	<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.title=mashups+of+Google+Maps+Street+View%3F&amp;rft.aulast=Yee&amp;rft.aufirst=Raymond&amp;rft.subject=Chapter+13&amp;rft.subject=Google&amp;rft.subject=Google+Maps&amp;rft.source=Mashup+Guide&amp;rft.date=2007-06-04&amp;rft.type=blogPost&amp;rft.format=text&amp;rft.identifier=http://blog.mashupguide.net/2007/06/04/mashups-of-google-maps-street-view/&amp;rft.language=English"></span>
<p>With pointers such as Greg Sadetsky's <a href="http://gregsadetsky.com/?p=81" class="external">tidbits on how Google Map's Street View works in the browser</a> (e.g., URLs of specific shots, a pointer to a <a href="http://www.nowrap.de/flare.html" class="external">Flare, an Actionscript decompiler</a>), how long will we have to wait until we get mashups that give us a video tour of Berkeley using photos from Street View?</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.mashupguide.net/2007/06/04/mashups-of-google-maps-street-view/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>KML adoption beyond Google Earth</title>
		<link>http://blog.mashupguide.net/2007/06/01/kml-adoption-beyond-google-earth/</link>
		<comments>http://blog.mashupguide.net/2007/06/01/kml-adoption-beyond-google-earth/#comments</comments>
		<pubDate>Fri, 01 Jun 2007 20:08:10 +0000</pubDate>
		<dc:creator>raymond.yee</dc:creator>
				<category><![CDATA[Chapter 13]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Google Earth]]></category>
		<category><![CDATA[Google Maps]]></category>
		<category><![CDATA[KML]]></category>

		<guid isPermaLink="false">http://blog.mashupguide.net/2007/06/01/kml-adoption-beyond-google-earth/</guid>
		<description><![CDATA[	
	<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.title=KML+adoption+beyond+Google+Earth&amp;rft.aulast=Yee&amp;rft.aufirst=Raymond&amp;rft.subject=Chapter+13&amp;rft.subject=Google&amp;rft.subject=Google+Earth&amp;rft.subject=Google+Maps&amp;rft.subject=KML&amp;rft.source=Mashup+Guide&amp;rft.date=2007-06-01&amp;rft.type=blogPost&amp;rft.format=text&amp;rft.identifier=http://blog.mashupguide.net/2007/06/01/kml-adoption-beyond-google-earth/&amp;rft.language=English"></span>
KML has moved beyond its use in Google Earth alone. For instance, you can display KML files and export search results and one of your "my maps" from Google Maps in KML. Other applications are beginning to support KML: For instance, you can get KML coming out of Yahoo! Pipes. There is support for KML [...]]]></description>
			<content:encoded><![CDATA[	
	<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.title=KML+adoption+beyond+Google+Earth&amp;rft.aulast=Yee&amp;rft.aufirst=Raymond&amp;rft.subject=Chapter+13&amp;rft.subject=Google&amp;rft.subject=Google+Earth&amp;rft.subject=Google+Maps&amp;rft.subject=KML&amp;rft.source=Mashup+Guide&amp;rft.date=2007-06-01&amp;rft.type=blogPost&amp;rft.format=text&amp;rft.identifier=http://blog.mashupguide.net/2007/06/01/kml-adoption-beyond-google-earth/&amp;rft.language=English"></span>
<p>KML has moved beyond its use in Google Earth alone. For instance, you  can display KML files and export search results and one of your "my  maps" from Google Maps in KML. Other applications are beginning to  support KML: For instance, you can get <a href="http://blog.pipes.yahoo.com/2007/05/02/pipes-adds-interactive-yahoo-maps-kml-support-and-more/" class="external">KML coming out of Yahoo! Pipes</a>.  There is support for KML in  <a href="http://googleearthuser.blogspot.com/2007/05/feed-validator.html" class="external">Feed Validator</a> KML is being shepherded through a standards process: <a href="http://geotips.blogspot.com/2007/04/kml-ogc.html" class="external">Paul Ramsey: KML @ OGC</a>.  Google is advising people to use KML so that its geo--search can index  KML -- in KML 2.2, there is an attribution element. Google apparently  will also index GeoRSS.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.mashupguide.net/2007/06/01/kml-adoption-beyond-google-earth/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Reader API?</title>
		<link>http://blog.mashupguide.net/2007/05/28/google-reader-api/</link>
		<comments>http://blog.mashupguide.net/2007/05/28/google-reader-api/#comments</comments>
		<pubDate>Mon, 28 May 2007 14:23:37 +0000</pubDate>
		<dc:creator>raymond.yee</dc:creator>
				<category><![CDATA[Chapter 05]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Google Reader]]></category>
		<category><![CDATA[RSS]]></category>
		<category><![CDATA[weblogging]]></category>

		<guid isPermaLink="false">http://blog.mashupguide.net/2007/05/28/google-reader-api/</guid>
		<description><![CDATA[	
	<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.title=Google+Reader+API%3F&amp;rft.aulast=Yee&amp;rft.aufirst=Raymond&amp;rft.subject=Chapter+05&amp;rft.subject=Google&amp;rft.subject=Google+Reader&amp;rft.subject=RSS&amp;rft.subject=weblogging&amp;rft.source=Mashup+Guide&amp;rft.date=2007-05-28&amp;rft.type=blogPost&amp;rft.format=text&amp;rft.identifier=http://blog.mashupguide.net/2007/05/28/google-reader-api/&amp;rft.language=English"></span>
I don't think that there is an official API for Google Reader although Niall Kennedy documened an unofficial Google Reader API a while back.]]></description>
			<content:encoded><![CDATA[	
	<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.title=Google+Reader+API%3F&amp;rft.aulast=Yee&amp;rft.aufirst=Raymond&amp;rft.subject=Chapter+05&amp;rft.subject=Google&amp;rft.subject=Google+Reader&amp;rft.subject=RSS&amp;rft.subject=weblogging&amp;rft.source=Mashup+Guide&amp;rft.date=2007-05-28&amp;rft.type=blogPost&amp;rft.format=text&amp;rft.identifier=http://blog.mashupguide.net/2007/05/28/google-reader-api/&amp;rft.language=English"></span>
<p>I don't think that there is an official API for Google Reader although Niall Kennedy documened an <a href="http://www.niallkennedy.com/blog/archives/2005/12/google_reader_a.html" class="external">unofficial Google Reader API</a> a while back.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.mashupguide.net/2007/05/28/google-reader-api/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ProgrammableWeb points me to yet another Google release!</title>
		<link>http://blog.mashupguide.net/2007/04/19/programmableweb-points-me-to-yet-another-google-release/</link>
		<comments>http://blog.mashupguide.net/2007/04/19/programmableweb-points-me-to-yet-another-google-release/#comments</comments>
		<pubDate>Fri, 20 Apr 2007 05:48:28 +0000</pubDate>
		<dc:creator>raymond.yee</dc:creator>
				<category><![CDATA[Chapter 04]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[ProgrammableWeb]]></category>
		<category><![CDATA[RSS]]></category>

		<guid isPermaLink="false">http://blog.mashupguide.net/2007/04/19/programmableweb-points-me-to-yet-another-google-release/</guid>
		<description><![CDATA[	
	<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.title=ProgrammableWeb+points+me+to+yet+another+Google+release%21&amp;rft.aulast=Yee&amp;rft.aufirst=Raymond&amp;rft.subject=Chapter+04&amp;rft.subject=Google&amp;rft.subject=ProgrammableWeb&amp;rft.subject=RSS&amp;rft.source=Mashup+Guide&amp;rft.date=2007-04-19&amp;rft.type=blogPost&amp;rft.format=text&amp;rft.identifier=http://blog.mashupguide.net/2007/04/19/programmableweb-points-me-to-yet-another-google-release/&amp;rft.language=English"></span>
It's very difficult to keep up with the world of public APIs and mashups -- even for someone like me who is writing a book on the topic and teaching a course on the subject! Now that I have a bit more time to work on the topic, I turn now to being more assiduous [...]]]></description>
			<content:encoded><![CDATA[	
	<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.title=ProgrammableWeb+points+me+to+yet+another+Google+release%21&amp;rft.aulast=Yee&amp;rft.aufirst=Raymond&amp;rft.subject=Chapter+04&amp;rft.subject=Google&amp;rft.subject=ProgrammableWeb&amp;rft.subject=RSS&amp;rft.source=Mashup+Guide&amp;rft.date=2007-04-19&amp;rft.type=blogPost&amp;rft.format=text&amp;rft.identifier=http://blog.mashupguide.net/2007/04/19/programmableweb-points-me-to-yet-another-google-release/&amp;rft.language=English"></span>
<p>  It's very difficult to keep up with the world of public APIs and  mashups -- even for someone like me who is writing a book on the topic  and teaching a course on the subject! Now that I <a href="http://blog.dataunbound.com/2007/04/03/leaving-ist-to-work-on-my-book/" class="external">have a bit more time to work on the topic</a>,  I turn now to being more assiduous in my reading of online news  sources. My first priority is a consistent read of John Musser's <a href="http://programmableweb.com" class="external">ProgrammableWeb</a>.  I already make steady use of its database of <a href="http://www.programmableweb.com/apis" class="external">APIs</a> and often point others to the <a href="http://www.programmableweb.com/mashups" class="external">Mashup Dashboard</a> when people ask me for concrete examples of mashups.  Now I want to keep up with <a href="http://blog.programmableweb.com/" class="external">his blog</a>.  <a href="http://blog.programmableweb.com/2007/04/20/google-ajax-feed-api/" class="external">Today (April 20)'s post</a> concerns <a href="http://code.google.com/apis/ajaxfeeds/" class="external">Google AJAX Feed API</a>, which is described thus by the Google documentation:</p>
<ul> With the AJAX Feed API, you can download any  public Atom or RSS feed using only JavaScript, so you can easily mash  up feeds with your content and other APIs like the Google Maps API.</ul>
<p>Hmmm...I get to a detailed look at Chapter 4 next week on RSS and other  feeds. I've written about Yahoo Pipes for remixing RSS. This Google  AJAX widget demands a close look too! (Thanks, John, for alerting me to  this new development! I also need to subscribe to <a href="http://googleajaxsearchapi.blogspot.com/" class="external">Google AJAX Search API Blog</a> in my news reader.)</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.mashupguide.net/2007/04/19/programmableweb-points-me-to-yet-another-google-release/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Machine tagging in Flickr (and elsewhere?)</title>
		<link>http://blog.mashupguide.net/2007/04/19/machine-tagging-in-flickr-and-elsewhere/</link>
		<comments>http://blog.mashupguide.net/2007/04/19/machine-tagging-in-flickr-and-elsewhere/#comments</comments>
		<pubDate>Fri, 20 Apr 2007 05:32:07 +0000</pubDate>
		<dc:creator>raymond.yee</dc:creator>
				<category><![CDATA[Chapter 03]]></category>
		<category><![CDATA[Flickr]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[tagging]]></category>

		<guid isPermaLink="false">http://blog.mashupguide.net/2007/04/19/machine-tagging-in-flickr-and-elsewhere/</guid>
		<description><![CDATA[	
	<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.title=Machine+tagging+in+Flickr+%28and+elsewhere%3F%29&amp;rft.aulast=Yee&amp;rft.aufirst=Raymond&amp;rft.subject=Chapter+03&amp;rft.subject=Flickr&amp;rft.subject=Google&amp;rft.subject=tagging&amp;rft.source=Mashup+Guide&amp;rft.date=2007-04-19&amp;rft.type=blogPost&amp;rft.format=text&amp;rft.identifier=http://blog.mashupguide.net/2007/04/19/machine-tagging-in-flickr-and-elsewhere/&amp;rft.language=English"></span>
"Machine tags" (see Flickr: Discussing Machine tags in Flickr API) have been introduced into Flickr as generalization of things like geotagging. Machine tags are also known by many as "triple tags". These are tags with a specific syntax aimed primarily for "machine consumption" (that is, by programs) and not directly for display to the typical [...]]]></description>
			<content:encoded><![CDATA[	
	<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.title=Machine+tagging+in+Flickr+%28and+elsewhere%3F%29&amp;rft.aulast=Yee&amp;rft.aufirst=Raymond&amp;rft.subject=Chapter+03&amp;rft.subject=Flickr&amp;rft.subject=Google&amp;rft.subject=tagging&amp;rft.source=Mashup+Guide&amp;rft.date=2007-04-19&amp;rft.type=blogPost&amp;rft.format=text&amp;rft.identifier=http://blog.mashupguide.net/2007/04/19/machine-tagging-in-flickr-and-elsewhere/&amp;rft.language=English"></span>
<p>  "Machine tags" (see <a href="http://www.flickr.com/groups/api/discuss/72157594497877875/" class="external">Flickr: Discussing Machine tags in Flickr API</a>)  have been introduced into Flickr as generalization of things like  geotagging. Machine tags are also known by many as "triple tags". These  are tags with a specific syntax aimed primarily for "machine  consumption" (that is, by programs) and not directly for display to the  typical end-user. You can use machine values to store extra data  elements for a given photo. I think that it's fair to say that most  important example of such data has so far been the latitude and  longitude associated with a photo. So important that Flickr ultimately  introduced specialized functionality to handle this data, to take that  data out of the realm of having people just shoehorning that info into  tags.</p>
<p>I'd really like to know what uptake there has been on machine tags. I  was hoping to be able to do searches for namespaces in use -- but as I  document below, I don't know how to formulate a query to do so.</p>
<p>Some kinks have been fixed in the Flickr machine tags:</p>
<ul>
<li>   If you look at <a href="http://tinyurl.com/2vyrgv">http://tinyurl.com/2vyrgv</a> -- you'll see that <a href="http://tech.groups.yahoo.com/group/yws-flickr/message/2744" class="external">yws-flickr : Message: bug with searching for machine tags?</a> has been fixed.</li>
</ul>
<p>Some outstanding issues remain:</p>
<ul>
<li>   missing negative values and decimals in the machine tag API.  See <a href="http://tech.groups.yahoo.com/group/yws-flickr/message/2861" class="external">yws-flickr : Message: Re: Machine Tag Bug - missing negative values and decimals?</a>.  When I do the a <a href="http://tinyurl.com/2sjxhm" class="external">query</a>  for my pictures that use the geo: machine tag name space and ask for  the machine tags, I get the "-" and "." stripped out. (I confirmed the  problem on March 11 but as of April 19, I've no seen any resolution.)</li>
<li class="gap">   no response to <a href="http://tech.groups.yahoo.com/group/yws-flickr/message/2743" class="external">yws-flickr : Message: Re: Ladies and gentlemen : Machine tags</a>.  I'd love to have a whole set of query functionality, including being  able to look up all domains in use. I know about "geo" but what others  are being used -- and with what frequency? For instance, we can pull up  all the geo: machine tags by searching for "geo:" with the API call.  See <a href="http://tinyurl.com/yt5k2f">http://tinyurl.com/yt5k2f</a>  You will &gt;500,000 photos under that domain. I tried variants on  "geo:" to try to pull up all machine tags ("*:", "*", "*:*") but I  couldn't find any that would get me all the machine tags....</li>
</ul>
<p>What are the equivalent of machine tags in other systems?   What to look at:</p>
<ul>
<li>   <a href="http://www.snee.com/bobdc.blog/2006/01/all_your_google_base_metadata.html" class="external">bobdc.blog: All Your Google Base metadata taxonomy are belong to us</a> and <a href="http://base.google.com/support/bin/answer.py?answer=27882" class="external">Google Base Help Center - What is an "attribute"?</a> in Google Base.</li>
<li class="gap"> I also vaguely remember something about attributes in Amazon S3  that might be related to machine tags. (The connection is probably  vague.)</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://blog.mashupguide.net/2007/04/19/machine-tagging-in-flickr-and-elsewhere/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Some useful references for Chapter 17 on office suites</title>
		<link>http://blog.mashupguide.net/2007/04/18/some-useful-references-for-chapter-17-on-office-suites/</link>
		<comments>http://blog.mashupguide.net/2007/04/18/some-useful-references-for-chapter-17-on-office-suites/#comments</comments>
		<pubDate>Wed, 18 Apr 2007 14:09:25 +0000</pubDate>
		<dc:creator>raymond.yee</dc:creator>
				<category><![CDATA[Chapter 17]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[office suites]]></category>

		<guid isPermaLink="false">http://blog.mashupguide.net/2007/04/18/some-useful-references-for-chapter-17-on-office-suites/</guid>
		<description><![CDATA[	
	<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.title=Some+useful+references+for+Chapter+17+on+office+suites&amp;rft.aulast=Yee&amp;rft.aufirst=Raymond&amp;rft.subject=Chapter+17&amp;rft.subject=Google&amp;rft.subject=Microsoft&amp;rft.subject=office+suites&amp;rft.source=Mashup+Guide&amp;rft.date=2007-04-18&amp;rft.type=blogPost&amp;rft.format=text&amp;rft.identifier=http://blog.mashupguide.net/2007/04/18/some-useful-references-for-chapter-17-on-office-suites/&amp;rft.language=English"></span>
Fodder for Chapter 17 on office suites when I get to writing it in detail: Google office destined to be mashed - CBRonline.com: "We definitely want to build out APIs, especially for the spreadsheets side, as spreadsheets are more data-oriented, but maybe also for he word processor," Google product manager Jonathan Rochelle said. "People will [...]]]></description>
			<content:encoded><![CDATA[	
	<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.title=Some+useful+references+for+Chapter+17+on+office+suites&amp;rft.aulast=Yee&amp;rft.aufirst=Raymond&amp;rft.subject=Chapter+17&amp;rft.subject=Google&amp;rft.subject=Microsoft&amp;rft.subject=office+suites&amp;rft.source=Mashup+Guide&amp;rft.date=2007-04-18&amp;rft.type=blogPost&amp;rft.format=text&amp;rft.identifier=http://blog.mashupguide.net/2007/04/18/some-useful-references-for-chapter-17-on-office-suites/&amp;rft.language=English"></span>
<p>  Fodder for Chapter 17 on office suites when I get to writing it in detail:</p>
<ul>
<li>  <a href="http://www.cbronline.com/article_news.asp?guid=7EF68962-DCB3-4F59-8309-20C18B68D015" class="external">Google office destined to be mashed - CBRonline.com</a>:</li>
</ul>
<ul> "We definitely want to build out APIs, especially  for the spreadsheets side, as spreadsheets are more data-oriented, but  maybe also for he word processor," Google product manager Jonathan  Rochelle said. "People will be able to do mashups with our tools for  other things, and not be stuck behind our dev cycle for everything they  want."</ul>
<ul>
<li><a href="http://office.microsoft.com/en-us/officelive/FX102036321033.aspx" class="external">Web hosting solution For small business, domain registration, and Web design - Microsoft Office Online</a> via <a href="http://blog.jonudell.net/2007/04/06/exploring-office-live/" class="external">Exploring Office Live « Jon Udell</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://blog.mashupguide.net/2007/04/18/some-useful-references-for-chapter-17-on-office-suites/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

