Revision as of 23:46, 30 January 2006 by RyanKing (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)

Jump to: navigation, search

Resumé Brainstorming

This is a space for brainstorming about a microformat for resumes/CVs.



Consequence of


Examples Analysis

A first pass at some analysis of the Aggregate analysis on resume-examples. A proposed 80/20:

affiliations a list of affiliations, each with organization name, url and association type
contact info contact info - address, email, url
education a list including organization/school info (name, location), degree/area of study, honors/awards, date (graduation only or range), GPA
employment/professional experience a list including the organization, timeframe, job title and location, accomplishments, description
skills an outline of skills/tools broken down by general categories
publications/presentation a list of writings, each including author(s), title, url and published year
summary/qualifications a list of qualifications and competencies

left off for now =

These are things found in resume-examples, which seem to be outside of the 80/20 of common resume constructs. --RyanKing 14:46, 30 Jan 2006 (PST)

Other Brainstorming

The following is the result of some brainstorming between some guys from Technorati and SimplyHired.

Minimal Set

According to the SimplyHired guys, who see a lot of resumes, a typical resume consists of these sections:


Again, according to SimplyHired, these sections are less common:


Some people publish functional resumes, which are a somewhat inverted form of the traditional.

Application of current microformats

See resume-formats for a description of common résumé elements. It seems that some of these constructs could easily be represented with existing microformats.


The contact info block of a résumé could be expressed with an hcard.


Educational experience could be expressed as a list of hcalendars. The rationale is that education can be viewed as a long-running event- it would be easy to reuse the vocabulary from hcalendar for describing events.

Work Experience

Just like Education, work experience could be expressed as a list of hcalendars.

Additionally, within a particular work experience, the list of job titles could be expressed as hcards. The only issue here is with having to repeat the FN for each of these hcards.

It might also be useful to extend xfn for marking up links to employers and clients.


Skills could be expressed as tags, using relTag. As with all rel-tag uses, a number of tagspaces would be appropriate.


Any publications, presentations, or other works could be represented by a citation microformat.


References could be expressed as a list of hcards, though web-based résumés tend to be light on using references.

In our initial brainstorming, we talked about doing references in resumes. However, after doing the resume-examples research it doesn't seem that references are published on the web very often.


LinkedIn allows users to endorse others' resumes. This functionality could be capture with vote-links.

Like the previous, this doesn't get used on the open web much, so I (Ryan King) think it should be left out, at least initially.

Photo From Brainstorming Session


Strawman Outline

Here's an outline of a strawman proposal.



Two Suggestions:

  1. class~="affiliation" + hcard -- use classname 'affiliation' + an hcard for the organization of which the user is a member
  2. a rel or rev value for membership/affiliation

contact info

Simple, an hcard for the person. Preferably inside an <address>


A list of hCalendar events, one for each education experience. We can either define a mapping of the terms, or just let loose and let conventions develop naturally.

employment/professional experience

A list of hCalendar events (one for each work experience). Optionally use hCards for describing job titles, organizational units, etc. We'll likely have a bit of a problem with not wanting to repeat FN for each hCard.


Most resumes analyzed in the resume-examples page had a section for skills and/or qualifications. I think this usage can be best covered by using rel-tag, and not require a specific section for these tags. Perhaps add a 'skill' classname.


Defer this problem to the citation work.


@class~="summary" (like hCalendar, hReview, etc.)

resume-brainstorming was last modified: Wednesday, December 31st, 1969