This is a space for brainstorming about a microformat for resumes/CVs.
- 1 Resumé Brainstorming
- 1.1 Contributors
- 1.2 Consequence of
- 1.3 Analysis
- 1.4 Application of current microformats
- 1.5 Photo From Brainstorming Session
- 1.6 See Also
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
- exhibitions - too rare?
- appearances and awards- don't know how to generalize this
- awards - too specific and rare
- interests - too rare
- objective - just use summary
- patents - too rare
- portfolio - too rare?
- projects - too rare?
- status - just use the 'summary'
- presentations - sure probably be part of one of the above, not sure where it fits in yet
The following is the result of some brainstorming between some guys from Technorati and SimplyHired.
According to the SimplyHired guys, who see a lot of resumes, a typical resume consists of these sections:
- Contact Info
- Work Experience
Again, according to SimplyHired, these sections are less common:
- references (could be tied to a specific job)
Some people publish functional resumes, which are a somewhat inverted form of the traditional.
- Work Experience
- experience (job, education, etc)
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 1.0.
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 1.0 for describing events.
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 - The XHTML Friends Network 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