<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Nicolas Schudel &#187; Microformats</title>
	<atom:link href="http://nicolasschudel.name/tag/microformats/feed/" rel="self" type="application/rss+xml" />
	<link>http://nicolasschudel.name</link>
	<description>Balancing Design and Development in Online Media</description>
	<lastBuildDate>Sun, 09 May 2010 08:42:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Lessons Learned Implementing the hResume Microformat</title>
		<link>http://nicolasschudel.name/lessons-learned-implementing-the-hresume-microformat/</link>
		<comments>http://nicolasschudel.name/lessons-learned-implementing-the-hresume-microformat/#comments</comments>
		<pubDate>Tue, 08 Apr 2008 16:40:20 +0000</pubDate>
		<dc:creator>Nicolas</dc:creator>
				<category><![CDATA[Web Development]]></category>
		<category><![CDATA[Microformats]]></category>

		<guid isPermaLink="false">http://nicolasschudel.name/?p=20</guid>
		<description><![CDATA[<p>A digital resume or <abbr title="Curriculum Vitae">CV</abbr> has a few plusses over its paper predecessor. One of these extras is the ability to give the information more meaning to the reader - human or machine. The hResume microformat introduces some nice additions to the usual HTML markup, but some rocks lay in the path of the implementor.</p>]]></description>
			<content:encoded><![CDATA[<p>
I made two changes of my own while using hResume. I sweetened the (generated) markup and discarded the <code>object</code> tag.
</p>
<h3>Pimping the Markup</h3>
<p>
There are <a href="http://microformats.org/wiki/hresume#Implementations">many tools for creating hResume markup</a>, but the ones I tested ended up creating something similar to the following code:
</p>
<pre class="brush: xml">
&lt;div class=&quot;experience vevent vcard&quot;&gt;
	&lt;div class=&quot;htitle&quot;&gt;
		&lt;object data=&quot;#j&quot; class=&quot;include&quot;&gt;&lt;/object&gt;
		&lt;span class=&quot;title&quot;&gt;Coffee Bringer&lt;/span&gt;&lt;br/&gt;
		&lt;span class=&quot;org&quot;&gt;My Employer&lt;/span&gt;, &lt;span class=&quot;location&quot;&gt;My Location&lt;/span&gt;
	&lt;/div&gt;
	&lt;div class=&quot;date_duration&quot;&gt;
		&lt;abbr class=&quot;dtstart&quot; title=&quot;2008-01-01&quot;&gt;January 2008&lt;/abbr&gt; - &lt;abbr class=&quot;dtend&quot; title=&quot;2008-03-01&quot;&gt;March 2008&lt;/abbr&gt;
	&lt;/div&gt;
	&lt;div style=&quot;clear: both&quot;&gt;&amp;nbsp;&lt;/div&gt;
	&lt;div class=&quot;description&quot;&gt;Bringing coffee to fellow web designers while they work.&lt;/div&gt;
&lt;/div&gt;
</pre>
<p>
The markup kinda misses the point of being human readable (<a href="http://microformats.org/about/">a main objective of Microformats</a>). At first glance, the employer, job title, date, location, and description should be marked up as a definition list. In my opinion, however, describing the data using a table would have an additional advantage: The description could be put into the table footer using the <code>tfoot</code> tag. This way it references to the rest of the data the good-old HTML way.
</p>
<pre class="brush: xml">
&lt;table class=&quot;vcalendar experience vevent vcard&quot; summary=&quot;Experience Overview&quot;&gt;
	&lt;thead&gt;
		&lt;tr&gt;
			&lt;th scope=&quot;col&quot;&gt;Title&lt;/th&gt;
			&lt;th scope=&quot;col&quot;&gt;Duration&lt;/th&gt;
			&lt;th scope=&quot;col&quot;&gt;Employer&lt;/th&gt;
			&lt;th scope=&quot;col&quot;&gt;Location&lt;/th&gt;
		&lt;/tr&gt;
	&lt;/thead&gt;
	&lt;tfoot&gt;
		&lt;tr&gt;
			&lt;td colspan=&quot;4&quot; class=&quot;description&quot;&gt;Bringing coffee to fellow web designers while they work.&lt;/td&gt;
		&lt;/tr&gt;
	&lt;/tfoot&gt;
	&lt;tbody&gt;
		&lt;tr class=&quot;htitle&quot;&gt;
			&lt;td class=&quot;title&quot;&gt;&lt;a class=&quot;include&quot; href=&quot;#j&quot; rel=&quot;#j&quot;&gt;Coffee Bringer 2&lt;/a&gt;&lt;/td&gt;
			&lt;td class=&quot;date_duration&quot;&gt;
				&lt;abbr class=&quot;dtstart&quot; title=&quot;2008-01-01&quot;&gt;January 2008&lt;/abbr&gt; -
				&lt;abbr class=&quot;dtend&quot; title=&quot;2008-03-01&quot;&gt;March 2008&lt;/abbr&gt;
			&lt;/td&gt;
			&lt;td class=&quot;org&quot;&gt;My Employer&lt;/td&gt;
			&lt;td class=&quot;location&quot;&gt;My Location&lt;/td&gt;
		&lt;/tr&gt;
	&lt;/tbody&gt;
&lt;/table&gt;
</pre>
<p>
This has the additional advantage that it displays nicely in the browser even when CSS is turned off. But wait, isn't the object tag missing?
</p>
<h3>Good-Bye Object Tag</h3>
<p>
The <code>object</code> tag inside the Microformat links each <em>vevent</em> element to the <em>vcard</em> later in the hResume. The Safari browser, and presumably any software using WebKit, renders the reference of the <code>object</code> so that it displays the whole page (and vcard) every time. It's the correct thing to do, I guess, but it makes the visualization of the resume overly-complicated.
</p>
<p>
The <a href="http://microformats.org/wiki/hresume">Wiki entry on hResume</a> describes a workaround to this by setting the dimensions to zero.
</p>
<pre class="brush: xml">
&lt;object data=&quot;#j&quot; class=&quot;include&quot; width=&quot;0&quot; height=&quot;0&quot;&gt;&lt;/object&gt;
</pre>
<p>
Safari rendered the data accordingly (by not showing it), but the page's display performance stayed unbearably bad (duh, it rendered the entire page anew inside each <em>vevent</em>). I, therefore, discarded the object tag all-together. I don't think it's a big loss, since the <em>vcard</em> is still there inside the hResume. A better option may be to add the reference along with the title using a link and the <em>rel</em> attribute instead, as seen in my code above.
</p>
<h3>Conclusion</h3>
<p>
There is still some changes to be made to the hResume Microformat before it can be considered "1.0". Turning the <em>vevent</em> markup into a table and rethinking/discarding the <code>object</code> tag may be two useful advances for the format.
</p>]]></content:encoded>
			<wfw:commentRss>http://nicolasschudel.name/lessons-learned-implementing-the-hresume-microformat/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
