<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Nimble Code: Tag atom</title>
    <link>http://www.nimblecode.com/articles/tag?tag=atom</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Jacob Harris' Weblog</description>
    <item>
      <title>The Future of Feeds</title>
      <description>&lt;p&gt;Earlier this year, I made a &lt;a href="http://www.mcsweeneys.net/links/lists/6TeddyWayneandGregWayne.html"&gt;New Year&amp;#8217;s Resolution&lt;/a&gt; to write more postings to the blog, but I have failed abjectly at that so far sadly. January is sadly a busy month for me, and I usually don&amp;#8217;t feel like coming home after a long day to stare at a computer screen some more. But occaisionally inspiration strikes, and I feel like sharing some thoughts I have about the future of Syndication via &lt;span class="caps"&gt;RSS&lt;/span&gt; and Atom feeds in the next few years.&lt;/p&gt;


	&lt;p&gt;I have to agree with my company&amp;#8217;s &lt;span class="caps"&gt;CEO &lt;/span&gt;&lt;a href="http://www.alacrablog.com/"&gt;Steve Goldstein&lt;/a&gt; when he says that &lt;a href="http://www.alacrablog.com/alacrablog/2006/01/trends_in_the_i.html"&gt;increasing &lt;span class="caps"&gt;RSS&lt;/span&gt;/Atom adoption will be one of the big trends in the information industry in 2006&lt;/a&gt;. Speculating wildly, I think that 2006 will be &lt;strong&gt;The Year of &lt;span class="caps"&gt;RSS&lt;/span&gt; and Atom&lt;/strong&gt;. And so, I&amp;#8217;m going to make a few bold predictions of my own about the state of syndication and the software industry. To avoid spending even longer without posting to the blog, I have decided to not bother with &lt;em&gt;research&lt;/em&gt;, so if something I have predicted has actually &lt;em&gt;happened&lt;/em&gt; already, be sure to make a snarky comment about it  to me below. Thanks. And now here are big things I see happening in the next year or so:&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Mainstream Feed Adoption&lt;/strong&gt; &amp;#8211; Currently, most of the sites producing feeds are still blogs and news sites –- those for whom the article paradigm within feeds is a natural fit. However, non-newsy sites like &lt;a href="http://del.icio.us/"&gt;del.icio.us&lt;/a&gt; and &lt;a href="http://www.flickr.com/"&gt;Flickr&lt;/a&gt; have earned a lot of buzz not just for their front-end interfaces but for their innovative and pervasive use of feeds &lt;em&gt;everywhere&lt;/em&gt; and using syndication for non-article content. But this is still under the radar of the typical Internet user for now. I think this will change this year. I expect a major online site to follow suit this year and provide syndication of their data in a similar fashion. For instance, I would not be surprised if &lt;a href="http://www.amazon.com/"&gt;Amazon&lt;/a&gt; began to offer feeds for user wishlists or upcoming recommendations or music alerts. That would rock.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;More People Will Embrace &lt;span class="caps"&gt;RSS&lt;/span&gt;, But Still Not Know It&lt;/strong&gt; &amp;#8211; A survey from last year by Yahoo! revealed that &lt;a href="http://slashdot.org/articles/06/01/01/1424220.shtml?tid=126"&gt;only 4% of Internet users knew what &lt;span class="caps"&gt;RSS&lt;/span&gt; was&lt;/a&gt;, but this will most certainly change. The name is obviously somewhat to blame (there&amp;#8217;s a joke that if it were called SpeedFeed more people would use it), but I think it&amp;#8217;s not the real problem. In truth, most people just don&amp;#8217;t care. For your typical web user, the Web is a toy more than a place to siphon information from; they are therefore not exactly vexed enough by the slowness of visiting sites to want to setup an aggregator. Instead, I think some different killer app beyond mere aggregation will be the only thing to make most people want to use &lt;span class="caps"&gt;RSS&lt;/span&gt;. I have no idea what that app might be, but I&amp;#8217;m sure one of you could think of something awesome.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;RSS Is A Terrible Business Though&lt;/strong&gt; &amp;#8211; For companies that produce or sell content, &lt;span class="caps"&gt;RSS&lt;/span&gt; will be a good fit, providing additional ways for users to access the site and contributing a small boost in sales or page visits. But companies in the &lt;span class="caps"&gt;RSS&lt;/span&gt; software business (particularly online aggregators) will have a terrible time. There are just very few barriers to entry for competitors, and the whole &lt;em&gt;we&amp;#8217;ll make money through advertising&lt;/em&gt; model seems so very pre-boom to me. That said, there are still some promising markets for companies doing &lt;span class="caps"&gt;RSS&lt;/span&gt; software. Software that allows filters or other mechanisms for mitigating information overload from feeds will find a market. Bridges from the pull-based mechanism of &lt;span class="caps"&gt;RSS&lt;/span&gt;/Atom to push-based messaging services like &lt;span class="caps"&gt;SMS&lt;/span&gt;, Email, or IM will probably also do well. And of course, it would be smart for makers of web analytics software to also look at measuring conversions and clickthroughs from feed links.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Syndication Will Drive &lt;span class="caps"&gt;REST &lt;/span&gt;Web Services&lt;/strong&gt; &amp;#8211; One of the common complaints leveled against &lt;a href="http://www.xfront.com/REST-Web-Services.html"&gt;REST-based Web Services&lt;/a&gt; is that the simple model of &lt;a href="http://www.prescod.net/rest/encoding/"&gt;REST does not specify the &lt;span class="caps"&gt;XML&lt;/span&gt; representation for data&lt;/a&gt; (unlike the case of &lt;span class="caps"&gt;XML&lt;/span&gt;-RPC and &lt;span class="caps"&gt;SOAP&lt;/span&gt;). This will never officially change, but I think it will become increasingly more common to see &lt;span class="caps"&gt;REST &lt;/span&gt;Web Services that return &lt;span class="caps"&gt;RSS&lt;/span&gt;-like data for searches. Indeed, throw in Amazon&amp;#8217;s &lt;a href="http://opensearch.a9.com/"&gt;OpenSearch extensions for &lt;span class="caps"&gt;RSS&lt;/span&gt;&lt;/a&gt; and you have support for presenting pagination within &lt;span class="caps"&gt;RSS&lt;/span&gt; documents. The practical upshot of this is that programmers can use the exact same code for &lt;span class="caps"&gt;RSS&lt;/span&gt;, Search Engine Plugins (&lt;em&gt;if any other engines besides A9.com support OpenSearch_&lt;/em&gt;), and &lt;span class="caps"&gt;REST&lt;/span&gt;-based Web Services. More significantly, this makes &lt;span class="caps"&gt;REST&lt;/span&gt; more compelling to these programmers, since supporting &lt;span class="caps"&gt;SOAP&lt;/span&gt;&amp;#8217;s data encoding would require supporting an additional data format for searches and more code to implement. Similarly, the arrival of the &lt;a href="http://www.xml.com/pub/a/2005/12/07/catching-up-with-the-atom-publishing-protocol.html"&gt;Atom Publishing Protocol&lt;/a&gt; will also bring awareness of &lt;span class="caps"&gt;REST &lt;/span&gt;Web Services to a wider market of people who will be using it without even knowing it.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Feed Extensions Will Get Wider Support&lt;/strong&gt; &amp;#8211; As &lt;span class="caps"&gt;RSS&lt;/span&gt;/Atom grows in its usage, it should be possible to find more aggregators and process that also support the more popular extensions to feeds (these are normally specified within the document in a separate namespace). I think a few extensions will become essential in the years ahead (and I don&amp;#8217;t even know if they exist currently!): support for threading of &lt;span class="caps"&gt;RSS&lt;/span&gt; items (for feeds based on email lists); partial encryption of &lt;span class="caps"&gt;RSS&lt;/span&gt; documents to be decrypted in the reader (would allow banks to offer feeds for instance); geographic tagging for marking stories (see the breaking news/photos on a map). In any event, I think good aggregators will show in some fashion all tags embedded in the feed so that users could search or filter based upon them.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Syndication in the Enterprise&lt;/strong&gt; &amp;#8211; Finally, it is obvious that &lt;span class="caps"&gt;RSS&lt;/span&gt;/Atom will become more common within corporate intranets as well. And the &lt;a href="/articles/2005/09/23/rss-comes-to-the-enterprise"&gt;credit for this belongs to Microsoft&lt;/a&gt; of all companies. Mainly, by placing &lt;span class="caps"&gt;RSS&lt;/span&gt; within all aspects of Windows Vista, Microsoft will drag all sorts of big &lt;span class="caps"&gt;IT &lt;/span&gt;Departments into accepting &lt;span class="caps"&gt;RSS&lt;/span&gt; as a solution for messaging and event notification. This will in turn make them more likely to also accept other solutions based on syndication. In fact, I&amp;#8217;m optimistic enough to think that &lt;span class="caps"&gt;B2B &lt;/span&gt;Syndication-based products will do better than &lt;span class="caps"&gt;B2C &lt;/span&gt;(remember that vexing 4% recognition rate from above; CTOs can mandate use in their companies). Smaller companies will be quick to embrace the immediacy of &lt;span class="caps"&gt;RSS&lt;/span&gt; and larger companies will also enjoy it for Windows Vista integration.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Atom vs. &lt;span class="caps"&gt;RSS2&lt;/span&gt;.0 Holy Wars Won&amp;#8217;t Matter&lt;/strong&gt; I know it vexes some readers of this posting that I&amp;#8217;m using &lt;span class="caps"&gt;RSS&lt;/span&gt; sometimes as a shorthand phrase for &lt;span class="caps"&gt;RSS2&lt;/span&gt;.0 or Atom-based syndication. And I agree with them that Atom is technically superior while &lt;span class="caps"&gt;RSS2&lt;/span&gt;.0 has better market share. But my ultimate feeling is that the differences between the two for the consumer will be largely academic (like caring about whether your audio player is playing &lt;span class="caps"&gt;MP3&lt;/span&gt; or &lt;span class="caps"&gt;AAC&lt;/span&gt;), since any good aggregator or processor should just be able to handle both formats effortlessly.&lt;/p&gt;


	&lt;p&gt;I will probably follow up on some of these points in more depth anon, but feel free to comment and quibble in the comments section below. I am no industry expert, but I do so like to make guesses about the business. And I&amp;#8217;m curious what you think as well. Check in next year and we&amp;#8217;ll how well they turned out.&lt;/p&gt;</description>
      <pubDate>Tue, 24 Jan 2006 17:12:00 -0800</pubDate>
      <guid isPermaLink="false">urn:uuid:f0298e47-ec19-4a66-9ee0-1a7113806171</guid>
      <author>harrisj@nimblecode.com (Jacob Harris)</author>
      <link>http://www.nimblecode.com/articles/2006/01/24/the-future-of-feeds</link>
      <category>Web Services</category>
      <category>rss</category>
      <category>atom</category>
      <category>syndication</category>
      <category>prediction</category>
      <trackback:ping>http://www.nimblecode.com/articles/trackback/93</trackback:ping>
    </item>
  </channel>
</rss>
