<?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: Costs of Microformats, cont.</title>
	<atom:link href="http://getluky.net/2009/01/13/costs-of-microformats-cont/feed/" rel="self" type="application/rss+xml" />
	<link>http://getluky.net/2009/01/13/costs-of-microformats-cont/</link>
	<description></description>
	<lastBuildDate>Thu, 10 May 2012 02:52:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Neil Kandalgaonkar</title>
		<link>http://getluky.net/2009/01/13/costs-of-microformats-cont/comment-page-1/#comment-310736</link>
		<dc:creator>Neil Kandalgaonkar</dc:creator>
		<pubDate>Wed, 14 Jan 2009 23:43:23 +0000</pubDate>
		<guid isPermaLink="false">http://getluky.net/?p=409#comment-310736</guid>
		<description>&lt;p&gt;I&#039;ve always been skeptical of microformats. &lt;/p&gt;

&lt;p&gt;The argument in favor of microformats is that it&#039;s an easy hack to add to your pages to make them a bit more semantic. But:&lt;/p&gt;

&lt;p&gt;&quot;Easy&quot; doesn&#039;t matter if you continue to pay that cost every time you want to modify a layout. It&#039;s just fundamentally wrong to contort HTML to pretend it can also be a medium for such data. &lt;/p&gt;

&lt;p&gt;&quot;Easy&quot; doesn&#039;t matter if validating it and bugfixing is hard. Proponents may point to the tools now available for validation but now they&#039;re contradicting themselves. If it&#039;s an easy hack, why do I need fancy validation tools? The theory here is that microformats are for authors who don&#039;t normally grok XML, but suddenly they &lt;em&gt;do&lt;/em&gt; need to run parsers and validators?&lt;/p&gt;

&lt;p&gt;We have a simple method available today for related content, or different versions of the same content: the LINK and A (anchor) elements. LINK works just fine for things like RSS. You never have to update your RSS when you want to change the visual layout. LINKed documents can signal what they are about with the REL attribute, and the actual document can use the standard HTTP headers for describing its format. The only flaw with LINK is that it applies to the whole document, rather than various DIVs and so on in the document. But very similar tricks could be done with the A element - it also can use the REL attribute. An empty anchor has no presentation in HTML anyway, so you don&#039;t even have to update your CSS. &lt;/p&gt;

&lt;p&gt;The microformat community could just focus on getting better browser support for that kind of linking and save about 90% of the effort.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;ve always been skeptical of microformats. </p>

<p>The argument in favor of microformats is that it&#8217;s an easy hack to add to your pages to make them a bit more semantic. But:</p>

<p>&#8220;Easy&#8221; doesn&#8217;t matter if you continue to pay that cost every time you want to modify a layout. It&#8217;s just fundamentally wrong to contort HTML to pretend it can also be a medium for such data. </p>

<p>&#8220;Easy&#8221; doesn&#8217;t matter if validating it and bugfixing is hard. Proponents may point to the tools now available for validation but now they&#8217;re contradicting themselves. If it&#8217;s an easy hack, why do I need fancy validation tools? The theory here is that microformats are for authors who don&#8217;t normally grok XML, but suddenly they <em>do</em> need to run parsers and validators?</p>

<p>We have a simple method available today for related content, or different versions of the same content: the LINK and A (anchor) elements. LINK works just fine for things like RSS. You never have to update your RSS when you want to change the visual layout. LINKed documents can signal what they are about with the REL attribute, and the actual document can use the standard HTTP headers for describing its format. The only flaw with LINK is that it applies to the whole document, rather than various DIVs and so on in the document. But very similar tricks could be done with the A element &#8211; it also can use the REL attribute. An empty anchor has no presentation in HTML anyway, so you don&#8217;t even have to update your CSS. </p>

<p>The microformat community could just focus on getting better browser support for that kind of linking and save about 90% of the effort.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

