<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/stylesheets/rss.css" type="text/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>Spoken: Version Numbers</title>
    <link>http://spoken.phrasewise.com/articles/2006/02/23/version-numbers</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Daniel Berlinger :: helpless :: speechless :: breathless</description>
    <item>
      <title>"Version Numbers" by Daniel</title>
      <description>&lt;p&gt;It seems like tightly spec&amp;#8217;ed profile will do what you need.&lt;/p&gt;

&lt;p&gt;And I should say that I don&amp;#8217;t disagree with what you say. I guess the question behind the question is what does the board have to gain? I really hate sounding like a conspiracy theorist, but when you have an entity whose existance does not seem warranted&amp;#8230; or as Sam put it increases &amp;#8220;social friction&amp;#8221; I want to know what everyone on the board has to gain.&lt;/p&gt;

&lt;p&gt;Anyway, while I&amp;#8217;m not against a better spec, I am against making it seem like RSS is moving if even a little. If folks want to move they should move to Atom or live with RSS as it is for better or for worse.&lt;/p&gt;</description>
      <pubDate>Fri, 24 Feb 2006 00:25:10 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:e6b8a65b-44ce-412e-9cd0-27b71f886d81</guid>
      <link>http://spoken.phrasewise.com/articles/2006/02/23/version-numbers#comment-142</link>
    </item>
    <item>
      <title>"Version Numbers" by Phil Ringnalda</title>
      <description>&lt;p&gt;I&amp;#8217;m not sure what other people&amp;#8217;s points are, but my two points are:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;When I publish an item with a less-than in the title, or (much less likely) with a relative URL or multiple enclosures, or when someone publishes something that my reader doesn&amp;#8217;t properly interpret, I don&amp;#8217;t want a three month long argument with another developer over whether this blog post means that the spec says this, or that mailing list comment says the spec meant to say that. I don&amp;#8217;t mean that hypothetically, I mean that literally: three months of arguing over how a single character in a title should be interpreted, because the spec is vague.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;When someone asks for an opinion about the validity of their RSS, as they do I don&amp;#8217;t know how many thousands of times a day (since even though I didn&amp;#8217;t write most of the validator, being able to commit means I&amp;#8217;m jointly responsible for what it says), I want to say &amp;#8220;this is what the spec says, see, right here?&amp;#8221; not &amp;#8220;based on our best guess about the most reasonable interpretation of the union of these five weblog posts, the spec probably meant to say&amp;#8230;&amp;#8221;&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Atom works fine for me as a producer, when I can say that the cost of being misunderstood is higher than the cost of not being heard by un-updated tools, but as a consumer and a consumer advocate, I can&amp;#8217;t just make RSS go away, so I want to drop that three months down to the five minutes of looking at the spec that should be all anyone needs. For me, that&amp;#8217;s all it&amp;#8217;s about: when something breaks, the spec should tell us whose bug it is.&lt;/p&gt;</description>
      <pubDate>Thu, 23 Feb 2006 19:01:35 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:633b6055-281c-44ab-b1c2-b88f3653bce1</guid>
      <link>http://spoken.phrasewise.com/articles/2006/02/23/version-numbers#comment-141</link>
    </item>
    <item>
      <title>Version Numbers</title>
      <description>&lt;div class="entry" title="Sam Ruby: Version Numbers" link="http://www.intertwingly.net/blog/2006/02/23/Version-Numbers"&gt;
&lt;a href="http://www.intertwingly.net/blog/2006/02/23/Version-Numbers"&gt;Sam Ruby&lt;/a&gt;: Rogers makes the case that all podcasters relying on multiple enclosures will be publishing RSS feeds that don&amp;rsquo;t work for what is potentially their largest audience, and Dave pleads for Rogers to &amp;ldquo;decide whether you&amp;rsquo;re working on a profile or a new format&amp;rdquo;. To this, I say, What Dave Said, though I will voice my preference on the two options that Dave puts on the table. &lt;cite cite="http://www.intertwingly.net/blog/2006/02/23/Version-Numbers" title="Daniel's remark..." class="dRemark"&gt;[And the latest dustup continues, but it seems to be calming down. I fail to understand the dilemma. I think &lt;a href=http://www.ietf.org/rfc/rfc4287.txt/"&gt;Atom&lt;/a&gt; is Roadmap Acceptable. Maybe the RSS board is in the wrong namespace? If they think there are problems with RSS 2.0 (the spec, format, whatever) why don&amp;#8217;t they see if Atom fixes those problems, and if so simply promote Atom? What is the point of minor-modding the spec?]&lt;/cite&gt;
&lt;/div&gt;</description>
      <pubDate>Thu, 23 Feb 2006 18:22:43 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:a9e7ceec-6d04-4957-96a7-e1f37725d281</guid>
      <author>Daniel</author>
      <link>http://spoken.phrasewise.com/articles/2006/02/23/version-numbers</link>
      <category>formats</category>
      <category>rss</category>
      <trackback:ping>http://spoken.phrasewise.com/articles/trackback/140</trackback:ping>
    </item>
  </channel>
</rss>
