resume-brainstorming: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
=Resumé Brainstorming= | =Resumé Brainstorming= | ||
This is a space for brainstorming about a microformat for resumes/CVs. | |||
__TOC__ | |||
== Contributors == | == Contributors == | ||
* [http://tantek.com/ Tantek Çelik] | * [http://tantek.com/ Tantek Çelik] | ||
* | * [http://theryanking.com Ryan King] | ||
* James Levine | * James Levine | ||
| Line 33: | Line 37: | ||
|} | |} | ||
left off for now: | ==== left off for now ===== | ||
These are things found in [[resume-examples]], which seem to be outside of the 80/20 of common resume constructs. --[[User:RyanKing|RyanKing]] 14:46, 30 Jan 2006 (PST) | |||
* exhibitions - too rare? | * exhibitions - too rare? | ||
| Line 46: | Line 51: | ||
* presentations - sure probably be part of one of the above, not sure where it fits in yet | * presentations - sure probably be part of one of the above, not sure where it fits in yet | ||
=== | === Other Brainstorming === | ||
====Minimal Set==== | |||
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 | * Contact Info | ||
* Education | * Education | ||
| Line 53: | Line 64: | ||
* Skills | * Skills | ||
====Optionally==== | ==== Optionally ==== | ||
Again, according to SimplyHired, these sections are less common: | |||
* Objective | * Objective | ||
* interests | * interests | ||
* references (could be tied to a specific job) | * references (could be tied to a specific job) | ||
===Functional=== | === Functional === | ||
Some people publish functional resumes, which are a somewhat inverted form of the traditional. | Some people publish functional resumes, which are a somewhat inverted form of the traditional. | ||
| Line 68: | Line 82: | ||
** experience (job, education, etc) | ** experience (job, education, etc) | ||
It | == 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 === | |||
===Contact=== | |||
The contact info block of a résumé could be expressed with an [[hcard]]. | The contact info block of a résumé could be expressed with an [[hcard]]. | ||
===Education=== | === Education === | ||
Educational experience could be expressed as a list of [[hcalendar|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. | Educational experience could be expressed as a list of [[hcalendar|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=== | === Work Experience === | ||
Just like Education, work experience could be expressed as a list of [[hcalendar|hcalendars]]. | Just like Education, work experience could be expressed as a list of [[hcalendar|hcalendars]]. | ||
Additionally, within a particular work experience, the list of job titles could be expressed as [[hcard|hcards]]. | Additionally, within a particular work experience, the list of job titles could be expressed as [[hcard|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. | It might also be useful to extend [[xfn]] for marking up links to employers and clients. | ||
===Skills=== | === Skills === | ||
Skills could be expressed as tags, using [[rel-tag|relTag]]. | Skills could be expressed as tags, using [[rel-tag|relTag]]. As with all rel-tag uses, a number of tagspaces would be appropriate. | ||
=== Publications === | === Publications === | ||
Any publications, presentations, or other works could be represented by a [[cite-formats|citation microformat]] | Any publications, presentations, or other works could be represented by a [[cite-formats|citation microformat]]. | ||
===References=== | === References === | ||
References could be expressed as a list of [[hcard|hcards]], though web-based résumés tend to be light on using references. | References could be expressed as a list of [[hcard|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 === | === endorsements === | ||
LinkedIn allows users to endorse others' resumes. This functionality could be capture with [[vote-links]]. | 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 == | == Photo From Brainstorming Session == | ||
Revision as of 22:46, 30 January 2006
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
- Company
- 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.
Photo From Brainstorming Session
