Should careers.stackoverflow.com support hResume?

Question

Jeff recently posted a blog about hosting CVs on careers.stackoverflow.com

I asked in the comments whether there were any plans to support hResume. Jeff said it was a great idea and that I should post it here on meta.stackoverflow.com to see what interest there might be.

So, question is, "Should careers.stackoverflow.com support the hResume microformat?"

Feel free to vote!

Some background:

hResume is a microformat dedicated to the markup of CVs/Resumes to facilitate data exchange. For example:

• The Guardian recently began accepting hResume formatted CVs on their careers website
• LinkedIn exposes using hResume

Answer 1

OK, I implemented hResume for Public CVs. The hResume microformat is layered on existing, older hCard and hCalendar microformats.

I used the Firefox Operator add-in, which was written by this guy, to test and make sure everything was working right.

There's also hCard validators at:
http://ufxtract.com/
http://hcard.geekhood.net/

Implementing this was awkward, because our data is relatively unstructured, and these formats assume you have highly, rigidly structured data. Some of the mappings don't seem quite right to me, but I couldn't figure out any better way. I did browse around some public LinkedIn profiles which are hResume enabled to see how they did it.

Feedback welcome of course!

Answer 2

Yes Yes YES!

Microformats are the future!

Not only should SOCareers support hResume, but I think that Jeff should look into other microformats (although none are as important as hResume) - hCard for profile pages and rel="license" and rel="tag" for the SO content pages!

EDIT: Jeff commented that rel="tag" is indeed used on SO pages. +1 for using some microformats on SO!

Answer 3

I think this is a very sound idea (and fits well with the reverse request to be able to pull in existing resumes (e.g. from LinkedIn) that are marked up as such.

Would also like to see externally linked URLs on career profile pages marked as @rel=me for full semantically linked goodness (I note that the personal URL already has a @rel=nofollow).

Answer 4

It would also be totally awesome if you could point it an existing hResume and have it pre-populate your CV on careers.stackoverflow.

Answer 5

In general the hCard and hCalendar are working well, but the hResume needs some work.

1- The education and experience are currently mark-up as:

<div class="vcard vevent">

You need to add the compound class name like so

<div class="vcard vevent education">
<div class="vcard vevent experience"> 

2- As you are using linkedin.com pattern combining hCard and hCalendar together for education and experience it’s a good idea mark-up all the data items for both schemas.

<div class="statement note">

Should also include the description from hCalendar

<div class="statement note description">

3- You need to mark-up the summary for hResume. Summary is the word use in CV where as the US use the word objectives, means the same thing.

<div class="intro-statement statement">

Should also include the summary from hResume

<div class="intro-statement statement summary">

4- Although it not called for in the specification is very useful to mark-up the hCard that carries the main contact information. Some parsers will not find it otherwise

<div class="intro-wrapper vcard">

Should also include the contact from hResume

<div class="intro-wrapper vcard contact">

5- The biggest issue is the dtStart and the dtEnd, these should be in the ISO datetime format yyyy-mm-dd etc. Unlike adr there is no label property to display a text formatted version of a date it has to be in a machine readable format

<div class="header-time dtstart dtend">April 2006 - May 2008</div>

Should be

<div class="header-time">
    <span class='dtstart'>
        <span class='value-title' title='2006-04'>July 2006</span>
    </span>  -
    <span class='dtend'>
        <span class='value-title' title='2008-05'>May 2008</span>
    </span>  
</div>

The convention is that if there is no dtend property for an hCalendar the event is considered ongoing

<div class="header-time dtstart dtend">April 2006 - Current</div>

Should be

<div class="header-time">
    <span class='dtstart'>
        <span class='value-title' title='2006-04'>July 2006</span>
    </span> - Current 
</div>

If you have date data that already fits the ISO format you can place directly in the text of an element

<div class="header-time dtstart dtend"> 2006 - 2008</div>

Should be

<div class="header-time">
    <span class='dtstart'>2006</span> - 
    <span class='dtend'>2008</span>
</div>

If you need a parser to try this out against try http://ufxtract.com/ I would be more than happy to help out with the mark-up. I have had a lot of experience both creating and parsing all three of the formats you’re using.

Glenn Jones

PS thanks for taking the time and effort for doing this

Answer 6

If they are marked up with microformats, the data will be available for Enhanced Results via SearchMonkey. If SO marks up with uF and starts showing up prevalantly on yahoo results, I'll make an enhanced result for resumes.

For example, videos products, reviews, reference.