<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="http://www.majordojo.com/projects/FeedManager/atom.xsl" type="text/xsl" media="screen"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://www.majordojo.com/2006/04/google-calendar.php" />
  <link rel="self" type="application/atom+xml" href="http://www.majordojo.com/2006/04/google-calendar.php" />
  <id>tag:www.majordojo.com,2010://3/tag:www.majordojo.com,2006://3.1175-</id>
  <updated></updated>
  <title>Comments for Google Calendar and Atom</title>
  <subtitle>A blog about Movable Type, technology, geek-dom, science-fiction and yes, sometimes my personal life.</subtitle>
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.261</generator>
  <entry>
    <id>tag:www.majordojo.com,2006://3.1175</id>
    <link rel="alternate" type="text/html" href="http://www.majordojo.com/2006/04/google-calendar.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.majordojo.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=3/entry_id=1175" title="Google Calendar and Atom" />
    <published>2006-04-13T17:13:11Z</published>
    <updated>2007-01-15T22:33:42Z</updated>
    <title>Google Calendar and Atom</title>
    <summary>Google today launched Google Calendar. I am sure plenty of people will blog about it, so I won&#8217;t bother with a review of all its Ajaxy-goodness. What I thought was interesting, however, is that Google Calendar does not support RSS....</summary>
    <author>
      <name>Byrne</name>
      <uri>http://www.majordojo.com/</uri>
    </author>
    
    <category term="Atom" />
    
    <category term="Blogging" />
    
    <category term="Technology" />
    
    <category term="Web Services" />
    
    <content type="html" xml:lang="en" xml:base="http://www.majordojo.com/">
      <![CDATA[<p>Google today <a href="http://news.com.com/Google+unveils+Web-based+calendar+app/2100-1032_3-6060741.html">launched</a> <a href="http://www.google.com/calendar">Google Calendar</a>. I am sure plenty of people will <a href="http://www.technorati.com/tags/Google+Calendar">blog about it</a>, so I won&#8217;t bother with a review of all its Ajaxy-goodness. </p>

<p><a href="http://www.majordojo.com/images/screenshots/calendar.png"><img alt="calendar.png" src="http://www.majordojo.com/images/screenshots/calendar-thumb.png" width="300" height="224" border="0" /></a></p>

<p>What I thought was interesting, however, is that Google Calendar does not support <a href="http://en.wikipedia.org/wiki/RSS_(protocol)">RSS</a>. In fact it uses <a href="http://www.atomenabled.org/">Atom</a> exclusively. Only a small minority of people will care about this obscure technology fact, but in the <a href="http://en.wikipedia.org/wiki/Category:Web_syndication_formats">syndication</a> community I think this is tremendously significant. To an engineer, adding RSS support is trivial, so the syndication industry must ask themselves, and the RSS folks especially, why did Google only support Atom?</p>
]]>
      <![CDATA[<p>Google also introduced their own proprietary Atom elements or what I could only call the &#8220;Google Calendar Atom Extension.&#8221; The elements they introduced are:</p>

<ul>
<li>transparency - unsure exactly what this is for</li>
<li>comments - which provides a link to a comment feed</li>
<li>eventStatus - which indicates whether an event is confirmed or not.</li>
<li>where - the location of the event</li>
<li>when - the time and duration of the event</li>
</ul>

<h3>Example Atom Elements</h3>

<pre><code>&lt;gd:transparency value="http://schemas.google.com/g/2005#event.opaque"/&gt;

&lt;gd:comments&gt;
  &lt;gd:feedLink href="http://www.google.com/calendar/feeds/byrne%2Bgoogle%40majordojo.com/public/full"/&gt;
&lt;/gd:comments&gt;

&lt;gd:eventStatus value="http://schemas.google.com/g/2005#event.confirmed"/&gt;

&lt;gd:where&gt;My Living Room&lt;/gc:where&gt;

&lt;gd:when startTime="2006-04-13T20:00:00.000Z" endTime="2006-04-13T21:00:00.000Z"/&gt;
</code></pre>

<h3>Wrap-Up and Final Thoughts</h3>

<p>It is a shame that Google did not use the more standard &#8220;<a href="http://www1.tools.ietf.org/wg/atompub/draft-snell-atompub-feed-thread-07.txt">Threads Extension</a>&#8221; for Atom as opposed to a proprietary <code>&lt;comments&gt;</code> element. But I bet you anything Google will fix that. The threads extension is getting a lot of traction - I know that we (<a href="http://www.sixapart.com">Six Apart</a>) has released support for it on <a href="http://friendsterblogs.friendster.com/">Friendster Blogs</a>, and  I know we intend to release it for <a href="http://www.typepad.com">TypePad</a>. Plus I have my own <a href="http://www.majordojo.com/2006/01/implementing_ja.php">implementation of it for Movable Type</a>.</p>

<p>But regardless, as <a href="http://www.dashes.com/blog/">Anil</a> always says, &#8220;shipping trumps everything else&#8221; so kudos to Google for getting it out there.</p>

<p>But back to one of the questions I posed earlier? Why did Google choose to support Atom <em>exclusively</em>? I personally think that Google foresaw that <a href="http://www.cadenhead.org/workbench/news/2895/rss-id-rather-switch-than-fight">the issues with RSS are finally coming home to roost</a>. Plus, <a href="http://www.majordojo.com/2006/03/why_we_need_a_design_standard.php">standards are just better</a>. </p>
]]>
    </content>
  </entry>

</feed>
