Resumé Brainstorming

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

Contributors

Tantek Çelik
Ryan King
James Levine

Consequence of

Analysis

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)

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

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:

Contact Info
Education
Work Experience
Skills

Optionally

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

Objective
interests
references (could be tied to a specific job)

Functional

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

Contact
Work Experience
- Company
  - Project
skill
- 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.

Contact

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

Education

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

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

Publications

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

References

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.

endorsements

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.

Brainstorming Session 2005-11-10

Contributors

Tantek Çelik
Ryan King
James Levine

Photo From Brainstorming Session

Writeup of Brainstorming Session

"hresume" - root class name
- "contact" hCard - should use <address>. Can be the person who the resume is about OR the proxy/contact in the case of recruiting/hiring services
- "objective" - block of text explaining the objective
- "job" hCalendar vevent - for each job in the jobs section:
  - hCard for title, org, address of company, (optionally, work phone numbers, etc.). For "fn" use indirection by referencing "contact" hCard above with an object tag as explained below.
- "education" hCalendar vevent - for each school attended in the education section:
  - hCard for the school with fn==org, address of school, (optionally, url, phone numbers, etc.).
- "skill" rel-tag - for each skill
- <cite> for each publication
- rel="reference" + XFN + hCard for references. rel="reference" makes sense because you are saying this person over here is a reference for the person represented by this resume.

The lists of jobs, education, skills, references should all use XOXO.

hCard reference via object

In typical resumes, each job listed also states the job title that the person had, as well as the name of the company, often the address (or at least city/state) of the company, and other information pertaining to the company.

This is effectively an hCard for the person while they were (are) working at that job, thus it makes sense to markup all that information as an hCard.

The only catch is, rarely do such hCards for each job include the person's name, visibly. Nor do we want to encourage people to replicate their name into those hCards (thus violating DRY) in invisible span elements. Thus the following code is proposed for a field (or several) in an hCard to reference another element in the document (likely the same field(s) in another hCard) and parse that other element as if it was inline in the hCard.

<span class="vcard">
 <object data="#j" class="fn n"></object>
 <span class="org">SimplyHired</span>
 <span class="title">Microformat Brainstormer</span>
</span>

Where "j" is the id attribute value of the "fn n" element of the contact hCard at the top of the page, e.g. (shown here as a verbose hCard for purposes of illustration that the reference may be to a subtree, not just a text node):

<span class="vcard">
 <span class="fn n" id="j">
  <span class="given-name">
   James
  </span>
  <span class="family-name">
   Levine
  </span>
 </span>
</span>

This method of hCard property indirection via an object element could be generalized to apply to any/all string/text properties in hCard.

Note: the object data attribute MUST be a local ID reference. External references (which would require a consuming application to load an external resource) are currently not supported by this method.

Issue: need to check with Brian Suda to see how easy/hard it would be to add this to X2V. Given that it wasn't too difficult to add the table td "headers" attribute content indirection support, this should be just as easy.

Strawman Outline

Here's an outline of a strawman proposal.

proposal

affiliations

Two Suggestions:

class~="affiliation" + hcard -- use classname 'affiliation' + an hcard for the organization of which the user is a member
a rel or rev value for membership/affiliation (this doesn't capture the name of the organization or any other information, but could be useful outside resumes)

contact info

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

education

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.

skills

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.

publications/presentation

Defer this problem to the citation work.

summary/qualifications

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

Strawman Draft

Just some space work working the draft schema out...

Format

In General

The hResume format is based on a set of fields common to numerous resumes published today on the web. Where possible field names have been chosen and reused from preexisting microformats.

Schema

The hResume schema consists of the following:

hResume
- summary. optional. text.
- contact info. required. <address> + hCard.
- education. optional. One or more hcalendar events with the class name 'education', with an embedded hCard indicating the job title, name of company, address of company etc.
- experience. optional One or more hcalendar events with the class name 'experience', with an embedded hCard indicating the name of school, address of school etc.
- skills. optional. phrases or keywords using the rel-tag microformat with the class name 'skill'.
- affiliations. optional. @TODO
- publications. optional. One or more citations. Use cite tag.
- references. optional. One or more references.

Field details

The fields of the hReview schema represent the following:

summary:: This optional field serves as a overview of qualifications and objectives.
contact:: Current contact info. The <address> element SHOULD be used, with an hCard to markup the individual contact information properties.
education:: the class name 'education' is applied to an hcalendar event.
experience:: the class name 'experience' is applied to an hcalendar event.
skill:: An hResume may be tagged using the rel-tag microformat with relevant keywords and phrases.
affiliations:: @TODO
publications:: just use <cite>. When there is a citation microformat, then that can be used in combination with the cite element to further markup the components of the citation.
rel="reference". For references, link to the person with rel="reference" and any other XFN values that apply (e.g. "colleague", "co-worker", "friend", "kin" etc.), and use hCard to markup the name of the reference.

Notes

This section is informative.

...

Examples

Summary

An example summary:

  <p class="summary">
    I have 10 years experience with all Web 2.0 technologies– I've been working with Ajax since 1996, 
    designing with pastels while others will still using tiled background images and frames...
  </p>

Contact

Minimal

  <address>Joe Smith</address>

hCard

  <address class="vcard">
    <span class="fn">Joe Smith</span>
    <span class="adr">
      <span class="street-address">123 Fake St.</span>
      <span class="locality">Anywhere</span>, <span class="region">CA</span> <span class="postal-code">123456</span>
    </span>
    <span>Email: <a class="email" href="mailto:joe@example.com">joe@example.com</a></span>
    <span>Homepage: <a class="url" href="http://example.com/~joe/">example.com/~joe/</a></span>
    <span>Phone: <span class="tel">+01.555.123.4567</span></span>
  </address>

resume-brainstorming

Resumé Brainstorming

Contributors

Consequence of

Analysis

Examples Analysis

left off for now

Other Brainstorming

Minimal Set

Optionally

Functional

Application of current microformats

Contact

Education

Work Experience

Skills

Publications

References

endorsements

Brainstorming Session 2005-11-10

Contributors

Photo From Brainstorming Session

Writeup of Brainstorming Session

hCard reference via object

Strawman Outline

proposal

affiliations

contact info

education

employment/professional experience

skills

publications/presentation

summary/qualifications

Strawman Draft

Format

In General

Schema

Field details

Notes

Examples

Summary

Contact

Minimal

hCard

Examples in the wild

Implementations

References

Normative

Navigation menu

Search