<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="/css/atom.css" type="text/css"?><entry xmlns="http://purl.org/atom/ns#">
<created>2003-07-01T10:08:15Z</created>
<issued>2003-07-01T10:08:15Z</issued>
<title>Bring out da funk, bring in da noise</title>
<modified>2003-07-01T10:08:15Z</modified>
<summary></summary>
<content type="text/html" mode="escaped">&lt;p&gt;Mark Pilgrim &lt;a href="http://diveintomark.org/archives/2003/07/01/leave_rss_alone.html"&gt;has removed all the namespaced elements from his &lt;span class="caps"&gt;RSS&lt;/span&gt; feeds&lt;/a&gt;. Presumably this makes them non-funky, although the funkiness of the now-elided (but valuable) &lt;code&gt;content:encoded&lt;/code&gt; seems debatable&amp;mdash;which, I guess, is the whole problem with the &amp;ldquo;funkiness&amp;rdquo; issue. One man&amp;rsquo;s duplication is another man&amp;rsquo;s way of expressing alternative representations of the same data. (Mark, to his credit, does write up separate excerpts, so they are generally more valuable than your run-of-the-mill &amp;ldquo;chopped off plaintext representation of the &lt;span class="caps"&gt;HTML&lt;/span&gt;&amp;rdquo; excerpt feed, like mine.)&lt;/p&gt;
&lt;p&gt;He explains:&lt;/p&gt;
&lt;blockquote&gt;I want to do all sorts of fancy things that &lt;span class="caps"&gt;RSS&lt;/span&gt; doesn&amp;rsquo;t allow for. Sure, I could shoehorn a bunch of stuff into namespaces and call it &lt;span class="caps"&gt;RSS&lt;/span&gt;, and it would be, technically; I&amp;rsquo;ve been doing that for months now. But that&amp;rsquo;s fundamentally the wrong approach; I see that now. I need a format that is geared for power users like me. It will still have a relatively simple core (probably not as simple as &lt;span class="caps"&gt;RSS&lt;/span&gt;, I mean, how could it be?) but it will have a wide array of well-defined extensions, well-documented, well-maintained, well-organized, and (I hope, someday) well-supported.&lt;/blockquote&gt;
&lt;p&gt;Now, I&amp;rsquo;m not sure where the &amp;ldquo;power user&amp;rdquo; line is at; I&amp;rsquo;m not much of a power user in the grand scheme of things, and even I&amp;rsquo;d like to see straightforward support for things like geographic and hierarchical aggregation, a unified content model (so my syndication feed, posting &lt;span class="caps"&gt;API&lt;/span&gt;, and TrackBack metadata would share the same code), and sensible treatment of multiple content payloads. I&amp;rsquo;m not even sure &lt;span class="caps"&gt;RSS&lt;/span&gt; works well for much of anything beyond the &amp;ldquo;My Netscape&amp;rdquo; design it started out as. But with &lt;span class="caps"&gt;RSS&lt;/span&gt; and &amp;ldquo;Echo&amp;rdquo; soon to be available, people can use the latter when they need to go beyond &lt;span class="caps"&gt;RSS&lt;/span&gt;&amp;rsquo;s capabilities&amp;mdash;without accidentally breaking compatibility with apps that can&amp;rsquo;t grok advanced features like XML namespaces. And that, my friends, is a Good Thing&amp;trade;.&lt;/p&gt;</content>
<link>http://blog.lordsutch.com/archives/546</link>
<id>http://blog.lordsutch.com/atom.cgi/entryid=546</id>
</entry>

