<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Educating Kent: The Single RSS Enclosure Thing</title>
	<atom:link href="http://www.newsome.org/2007/07/educating-kent-single-rss-enclosure/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.newsome.org/2007/07/educating-kent-single-rss-enclosure/</link>
	<description>Kent Newsome on technology, music and life</description>
	<lastBuildDate>Sun, 05 Feb 2012 23:43:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Kent</title>
		<link>http://www.newsome.org/2007/07/educating-kent-single-rss-enclosure/comment-page-1/#comment-3539</link>
		<dc:creator>Kent</dc:creator>
		<pubDate>Wed, 11 Jul 2007 05:44:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/newsome/?p=3462#comment-3539</guid>
		<description>Yeah, I&#039;m a little confused by the profile.I get why a podcast ought to have a single enclosure, so it can be correctly named and categorized, etc.But it seems to me that multiple audio files in a single post ought to somehow be treated equally- the effect of what I mean by that is that they would all be playable like the first one from within a feed.  Granted, there may be no way to distinguish a podcast from an audio file within a post.But in this day where everything is about pushing media, it seems inevitable to me, as a publisher and end user, that multiple audio files will need to be addressed.</description>
		<content:encoded><![CDATA[<p>Yeah, I&#8217;m a little confused by the profile.I get why a podcast ought to have a single enclosure, so it can be correctly named and categorized, etc.But it seems to me that multiple audio files in a single post ought to somehow be treated equally- the effect of what I mean by that is that they would all be playable like the first one from within a feed.  Granted, there may be no way to distinguish a podcast from an audio file within a post.But in this day where everything is about pushing media, it seems inevitable to me, as a publisher and end user, that multiple audio files will need to be addressed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jackson Miller</title>
		<link>http://www.newsome.org/2007/07/educating-kent-single-rss-enclosure/comment-page-1/#comment-3540</link>
		<dc:creator>Jackson Miller</dc:creator>
		<pubDate>Wed, 11 Jul 2007 01:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/newsome/?p=3462#comment-3540</guid>
		<description>An RSS &quot;feed&quot; can have multiple enclosures.  An RSS feed is made up of &quot;items&quot;, it makes sense for an &quot;item&quot; to have a single enclosure.  Multiple enclosures would be multiple items.The issue might be that people are thinking about enclosures as attachments like in an email.  However, when thinking about enclosures with something like a podcast feed, each audio file is a separate item, and thus a separate item in the feed.</description>
		<content:encoded><![CDATA[<p>An RSS &#8220;feed&#8221; can have multiple enclosures.  An RSS feed is made up of &#8220;items&#8221;, it makes sense for an &#8220;item&#8221; to have a single enclosure.  Multiple enclosures would be multiple items.The issue might be that people are thinking about enclosures as attachments like in an email.  However, when thinking about enclosures with something like a podcast feed, each audio file is a separate item, and thus a separate item in the feed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rogers</title>
		<link>http://www.newsome.org/2007/07/educating-kent-single-rss-enclosure/comment-page-1/#comment-3541</link>
		<dc:creator>Rogers</dc:creator>
		<pubDate>Tue, 10 Jul 2007 16:01:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/newsome/?p=3462#comment-3541</guid>
		<description>The long answer is &lt;a HREF=&quot;http://www.rssboard.org/rss-profile#element-channel-item-enclosure&quot; rel=&quot;nofollow&quot;&gt;in the profile&lt;/A&gt;, but the short version is that the intent in RSS 2.0 was for a one-to-one relationship between RSS items and enclosures, so the item title and description could be assumed to describe the enclosure.</description>
		<content:encoded><![CDATA[<p>The long answer is <a HREF="http://www.rssboard.org/rss-profile#element-channel-item-enclosure" rel="nofollow">in the profile</a>, but the short version is that the intent in RSS 2.0 was for a one-to-one relationship between RSS items and enclosures, so the item title and description could be assumed to describe the enclosure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randy Charles Morin</title>
		<link>http://www.newsome.org/2007/07/educating-kent-single-rss-enclosure/comment-page-1/#comment-3542</link>
		<dc:creator>Randy Charles Morin</dc:creator>
		<pubDate>Tue, 10 Jul 2007 15:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/newsome/?p=3462#comment-3542</guid>
		<description>Basically it&#039;s how the spec was written. enclosures were said to be optional.</description>
		<content:encoded><![CDATA[<p>Basically it&#8217;s how the spec was written. enclosures were said to be optional.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kent</title>
		<link>http://www.newsome.org/2007/07/educating-kent-single-rss-enclosure/comment-page-1/#comment-3543</link>
		<dc:creator>Kent</dc:creator>
		<pubDate>Tue, 10 Jul 2007 13:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/newsome/?p=3462#comment-3543</guid>
		<description>Maybe it&#039;s not RSS, but something in a feed takes the first audio file it finds and adds a play button at the bottom of the feed to play it.  It&#039;s always the first audio file in the post.What I&#039;m wondering about is why that can&#039;t be done with all the audio files.There was discussion in the Feedburner forums that indicated it was a RSS standards thing.</description>
		<content:encoded><![CDATA[<p>Maybe it&#8217;s not RSS, but something in a feed takes the first audio file it finds and adds a play button at the bottom of the feed to play it.  It&#8217;s always the first audio file in the post.What I&#8217;m wondering about is why that can&#8217;t be done with all the audio files.There was discussion in the Feedburner forums that indicated it was a RSS standards thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.newsome.org/2007/07/educating-kent-single-rss-enclosure/comment-page-1/#comment-3544</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Tue, 10 Jul 2007 12:09:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/newsome/?p=3462#comment-3544</guid>
		<description>I&#039;m not sure it is really an rss thing.  If you look at the html on the original post, it is just an &quot;a&quot; tag linking directly to an mp3 file.  Then there is some magic javascript from del.icio.us that adds the autoplay ability.  I don&#039;t think Javascript code carries over to the rss feed code.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure it is really an rss thing.  If you look at the html on the original post, it is just an &#8220;a&#8221; tag linking directly to an mp3 file.  Then there is some magic javascript from del.icio.us that adds the autoplay ability.  I don&#8217;t think Javascript code carries over to the rss feed code.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

