<?xml version="1.0" encoding="UTF-8"?>
<essay xml:lang="en" version="5.0" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:gal="http://norman.walsh.name/rdf/gallery#" xmlns:foaf="http://xmlns.com/foaf/0.1/">
<info>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
<title>Timing is everything</title><biblioid class="uri">http://norman.walsh.name/2009/05/07/timing</biblioid>
<volumenum>12</volumenum>
<issuenum>15</issuenum>
<pubdate>2009-05-07T10:17:27-04:00</pubdate>
<author>
      <personname>
<firstname>Norman</firstname>
	<surname>Walsh</surname>
</personname>
    </author>
<copyright>
      <year>2009</year>
      <holder>Norman Walsh</holder>
    </copyright>
<abstract>
<para>So, AtomPub is a failure and RSS is dead. Anyone want to guess
what my conference presentation next week is about?</para>
</abstract>
<dc:subject rdf:resource="http://norman.walsh.name/knows/taxonomy#RSS"/>
<dc:subject rdf:resource="http://norman.walsh.name/knows/taxonomy#TheWeb"/>
</info>

<para xml:id="p1">The genesis of my presentation for the
<link xlink:href="http://www.marklogic.com/UserConference2009/">Mark
Logic User Conference</link> next week was the
<wikipedia page="Atom_(standard)">AtomPub</wikipedia> implementation
<link xlink:href="http://norman.walsh.name/2009/01/23/atompub">I described</link>
a few months ago.
</para>

<para xml:id="p2">Imagine my delight when, as I was getting the presentation in
order, <personname>
      <firstname>Joe</firstname>
      <surname>Gregorio</surname>
</personname> declared
<link xlink:href="http://bitworking.org/news/425/atompub-is-a-failure">The
Atom Publishing Protocol is a failure</link> and
<personname>
      <firstname>Steve</firstname>
      <surname>Gillmor</surname>
</personname> wrote
<link xlink:href="http://www.techcrunchit.com/2009/05/05/rest-in-peace-rss/">Rest
in Peace, RSS</link>. Do I have great timing, or what?</para>

<para xml:id="p3">In point of fact, neither of these posts causes me any great
concern. Despite the hyperbole of Joe's title, is actual observation
is that “[AtomPub] hasn't seen the level of adoption [he] had hoped”.
He goes on to describe a number of plausible reasons why this is the case,
mostly having to do with improvements in browser technologies.</para>

<para xml:id="p4">It may not have taken over the world, but support on
the 
<link xlink:href="http://code.google.com/apis/gdata/">Google Data APIs</link>,
<link xlink:href="http://blogs.msdn.com/astoriateam/archive/2008/02/13/atompub-support-in-the-ado-net-data-services-framework.aspx">Microsoft Windows Live</link>,
and some social networking sites,
such as Flickr (though I can't find a link to that, so maybe it's not
yet deployed), seems pretty successful to me. Besides, I'm not primarily
interested in passing data to or from a web browser, although there's an
app^W<link xlink:href="https://addons.mozilla.org/en-US/firefox/addon/3188">extension</link>
for that.</para>

<para xml:id="p5">I want to be able to pass structured data around, data that's
too richly structured for <wikipedia>JSON</wikipedia> to be of any
practical value and data that isn't typically HTML. I could (and have) invented
my own data formats and my own APIs, but rarely as robustly and
completely as Atom and AtomPub.</para>

<para xml:id="p6">Part of my interest in implementing AtomPub stems from a long
range goal to reinvent this weblog on top of
<link xlink:href="http://www.marklogic.com/product/marklogic-server.html">MarkLogic
Server</link>. For that, I'll want to be able to pass DocBook essays in
and out of the server, contacts, appointments, geospatial data, etc.
AtomPub makes that easy.</para>

<para xml:id="p7">As for Gillmor's piece, I'm not sure what to say exactly, except
“Huh?” His opening shot amounts to nothing more than a metaphorical
restatement of <wikipedia page="Sturgeon's_law">Sturgeon's
Law</wikipedia>, which applies equally to
<wikipedia>Twitter</wikipedia>. If the “river of news” has become the
“East River of news”, I'm not sure what the “twitter stream” has become,
exactly, but I wouldn't want to swim in it either.</para>

<para xml:id="p8">If your experience of syndication was that you lived in your
favorite feed aggregator, refreshing it constantly so that you could
get the latest “hot link” or one-liner from your friends the minute
they happened, then sure, I can see how Twitter is a
replacement.</para>

<para xml:id="p9">That's just not how I ever used syndication. I never used by
reader more than a few times a week after the initial technology
excitement wore off. I use it to collect and aggregate longer, more
thoughtful pieces from users or sites that offer a good
signal-to-noise ratio on the topics I'm interested in.</para>

<para xml:id="p10">Which isn't to say that it's all deep and thoughtful stuff. Among
my aggregated feeds, you'll find 
a humor folder that collects things like <wikipedia>xkcd</wikipedia>,
<link xlink:href="http://thisisindexed.com/">Indexed</link>, and
<link xlink:href="http://thedailywtf/">Worse Than Failure</link>,
a Mark Logic folder that collects things likely to be related
to my day job, another folder that's a shameless bit of ego surfing, a photography
folder, and a medium sized folder of individuals about who's projects
and opinions I think I should be aware.
</para>

<para xml:id="p11">Twitter doesn't replace any of that. In fact, several of those folders
contain <emphasis>a feed</emphasis> of <emphasis>Twitter search results</emphasis>.
So, in fact, I actually find it more useful to aggregate some tweets into
a feed than read them any other way.</para>

<para xml:id="p12">Which is not to say that Twitter hasn't cannibalized weblogs to
an extent. It certainly has. Writing a personal weblog, absent any
quest for money or fame, is about scratching an itch. Twitter
scratches that itch, so I'm less motivated to write posts that do
little more than point to something cool or convey my wit.</para>

<para xml:id="p13">I don't know if my weblog is more or less valuable for this
change, but it isn't likely to go away because I have twitter. I care
about lots of things that require more nuanced understanding than you
can squeeze into 140 characters.</para>

<para xml:id="p14">On the subject of RSS, it seems only fair to let
<personname>
      <firstname>Dave</firstname>
      <surname>Winer</surname>
    </personname>
have the last
<link xlink:href="http://www.scripting.com/stories/2009/05/06/rssIsDeadMyAss.html">word</link>.
</para>

</essay>

