<?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: Visual metadata in feeds</title>
	<atom:link href="http://aaronmentele.com/2007/01/04/visual-metadata-in-feeds/feed/" rel="self" type="application/rss+xml" />
	<link>http://aaronmentele.com/2007/01/04/visual-metadata-in-feeds/</link>
	<description>personal blog of Aaron Mentele, web developer and partner at Electric Pulp</description>
	<lastBuildDate>Sat, 24 Jul 2010 06:48:01 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Aaron Mentele</title>
		<link>http://aaronmentele.com/2007/01/04/visual-metadata-in-feeds/comment-page-1/#comment-7572</link>
		<dc:creator>Aaron Mentele</dc:creator>
		<pubDate>Thu, 04 Jan 2007 20:36:28 +0000</pubDate>
		<guid isPermaLink="false">http://charisma18.com/2007/01/04/visual-metadata-in-feeds/#comment-7572</guid>
		<description>It&#039;s a weird topic - figure out a way to sneak in aesthetic [publisher preference] improvements and we&#039;ll all be talking about how to block them.  I almost think there needs to be a very tight reign.  I used NetNewsWire for a while and seeing the nasty themes that were available scares me to think each publisher would build their own &quot;theme.&quot;  The idea would require an all or nothing approach - an alt version like you mention in the first comment might be an equally good (all) option vs. the controlled baby step option I was suggesting.</description>
		<content:encoded><![CDATA[<p>It&#8217;s a weird topic &#8211; figure out a way to sneak in aesthetic [publisher preference] improvements and we&#8217;ll all be talking about how to block them.  I almost think there needs to be a very tight reign.  I used NetNewsWire for a while and seeing the nasty themes that were available scares me to think each publisher would build their own &#8220;theme.&#8221;  The idea would require an all or nothing approach &#8211; an alt version like you mention in the first comment might be an equally good (all) option vs. the controlled baby step option I was suggesting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jdbartlett</title>
		<link>http://aaronmentele.com/2007/01/04/visual-metadata-in-feeds/comment-page-1/#comment-7561</link>
		<dc:creator>jdbartlett</dc:creator>
		<pubDate>Thu, 04 Jan 2007 19:26:37 +0000</pubDate>
		<guid isPermaLink="false">http://charisma18.com/2007/01/04/visual-metadata-in-feeds/#comment-7561</guid>
		<description>Actually, given a few minutes to think about it, a better method might be to use the &lt;a href=&quot;http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.content&quot; rel=&quot;nofollow&quot;&gt;content&lt;/a&gt; element with the type attribute set to &quot;application/xhtml xml&quot; and the &quot;src&quot; attribute linking to a special feed-reader-friendly styled XHTML document as described above. Current readers should support this.</description>
		<content:encoded><![CDATA[<p>Actually, given a few minutes to think about it, a better method might be to use the <a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.content" rel="nofollow">content</a> element with the type attribute set to &#8220;application/xhtml xml&#8221; and the &#8220;src&#8221; attribute linking to a special feed-reader-friendly styled XHTML document as described above. Current readers should support this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jdbartlett</title>
		<link>http://aaronmentele.com/2007/01/04/visual-metadata-in-feeds/comment-page-1/#comment-7560</link>
		<dc:creator>jdbartlett</dc:creator>
		<pubDate>Thu, 04 Jan 2007 19:13:35 +0000</pubDate>
		<guid isPermaLink="false">http://charisma18.com/2007/01/04/visual-metadata-in-feeds/#comment-7560</guid>
		<description>For me, feeds are all about workflow, and the uniform style of my reader enhances that workflow. Still, I can see where a little personality might enhance some feeds.

A lot of readers offer an option to display the feed&#039;s &lt;a href=&quot;http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.link&quot; rel=&quot;nofollow&quot;&gt;&quot;alternate&quot; article link&lt;/a&gt; through the default web browser instead of the article content. A better solution might be to attach an additional &quot;alternate&quot; link to a special HTML version of the article, styled with feed readers in mind and identified by a uniform title. This could be done without enhancing the Atom spec, but it&#039;s up to feed reader developers to adopt it. Think of it as a microformat for Atom!</description>
		<content:encoded><![CDATA[<p>For me, feeds are all about workflow, and the uniform style of my reader enhances that workflow. Still, I can see where a little personality might enhance some feeds.</p>
<p>A lot of readers offer an option to display the feed&#8217;s <a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.link" rel="nofollow">&#8220;alternate&#8221; article link</a> through the default web browser instead of the article content. A better solution might be to attach an additional &#8220;alternate&#8221; link to a special HTML version of the article, styled with feed readers in mind and identified by a uniform title. This could be done without enhancing the Atom spec, but it&#8217;s up to feed reader developers to adopt it. Think of it as a microformat for Atom!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
