User:Robert Merrill

2006-02-12T16:47:06Z

Robert Merrill:

My name is Robert Merrill. I am a technical recruiter who blogs professionally at, [http://www.utahtechjobs.com www.utahtechjobs.com] and personally at [http://www.utahtechjobs.com/robertmerrill www.utahtechjobs.com/robertmerrill].

I am interested in hResume to simplify resume aquisition, aggregation and (most-importantly) to bring intelligence to the resume-search process.

I first learned about Microformats at a [http://www.devutah.com DevUtah Geek Dinner] where [http://www.windley.com/ Phil Windley] presented on hCard and hCalendar

resume-brainstorming

2006-02-12T15:41:34Z

Robert Merrill: /* Analysis */

=Resumé Brainstorming=

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

__TOC__

== Contributors ==

* [http://tantek.com/ Tantek Çelik]
* [http://theryanking.com Ryan King]
* James Levine

== Consequence of ==
* [[resume-examples]]
* [[resume-formats]]

== 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. --[[User:RyanKing|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)

=== Additional Metadata ===
* It would be helpful to have the following fields associated with skills: [[User:Robert Merrill|Robert Merrill]] 07:41, 12 Feb 2006 (PST)
** Skill-Level: Beginner, Advanced, Expert
** Years of experience with skill (numeric)
** Last used: either value of "currently used" or years since last-used

== 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 [[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 ===
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]]. 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 [[rel-tag|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 [[cite-formats|citation microformat]].

=== 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 ===
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 ===

[http://flickr.com/photos/tantek/87059139/ http://static.flickr.com/41/87059139_88bb16e1b4.jpg]

=== Writeup of Brainstorming Session ===

* "hresume" - root class name
** "contact" [[hcard|hCard]] - should use <code class="element"><address></code>. 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|hCalendar]] vevent - for each job in the jobs section:
*** [[hcard|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|hCalendar]] vevent - for each school attended in the education section:
*** [[hcard|hCard]] for the school with fn==org, address of school, (optionally, url, phone numbers, etc.).
** "skill" [[rel-tag]] - for each skill
** <code class="element"><cite></code> for each publication
** rel="reference" + [http://gmpg.org/xfn/ XFN] + [[hcard|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|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.

<pre><nowiki>

<object data="#j" class="fn n"></object>
SimplyHired
Microformat Brainstormer

</nowiki></pre>

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):

<pre><nowiki>



James


Levine



</nowiki></pre>

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.

'''Status:''' According to Brian Suda: "... it shouldn't be too difficult... you are right it is pretty similar to the AXIS HEADER ID problems."

'''Next Steps:''' Brian will try implementing it in X2V and we'll see how well it works. If it works, then we'll add it to [[hcard|hCard]], [[hcard-parsing]], and [[hreview|hReview]] 0.3 (as well as [[hresume|hResume]] of course).

== 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 in 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. <code class="element"><address></code> + [[hcard|hCard]].
** education. optional. One or more [[hcalendar]] events with the class name '<code class="class-name">education</code>', with an embedded [[hcard|hCard]] indicating the job title, name of company, address of company etc.
** experience. optional One or more [[hcalendar]] events with the class name '<code class="class-name">experience</code>', with an embedded [[hcard|hCard]] indicating the name of school, address of school etc.
** skills. optional. phrases or keywords using the [[rel-tag]] microformat with the class name '<code class="class-name">skill</code>'.
** affiliations. optional. the class name <code class="class-name">affiliation</code> along with an [[hcard]] of the organization
** 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 <code class="element"><address></code> with [[hCard]].
* '''education''':: the class name '<code class="class-name">education</code>' is applied to an [[hcalendar]] event.
* '''experience''':: the class name '<code class="class-name">experience</code>' is applied to an [[hcalendar]] event. Job titles/positions should use an [[hCard]].
* '''skills''':: An hResume may be tagged using the [[rel-tag]] microformat and the '<code class="class-name">skill</code>' class name.
* '''affiliations''':: The class name <code="class-name">affiliation</code> is used along with an [[hcard]] of the organization
* '''publications''':: just use <code class="element"><cite></code>. 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 [http://gmpg.org/xfn/ XFN] values that apply (e.g. "colleague", "co-worker", "friend", "kin" etc.), and use [[hcard|hCard]] to markup the name of the reference.

=== Notes ===
This section is informative.

*...

== Examples ==
=== Summary ===
An example summary:

<pre><nowiki>

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...

</nowiki></pre>

=== Contact ===
<pre><nowiki>
<address class="vcard">
Pedro Sanchez

123 Fake St.
Preston, Idaho 83263

Email: <a class="email" href="mailto:joe@example.com">pedro@vote-for-pedro.com</a>
Homepage: <a class="url" href="http://vote-for-pedro.com/">vote-for-pedro.com</a>
Phone: +01.208.555.4567
</address>
</nowiki></pre>

=== Education ===
<pre><nowiki>
<ol class="vcalendar">
<li class="education vevent">
<a class="url summary" href="http://example.edu/">Preston High School</a>
(<abbr class="dtstart" title="1995-01-24">2001</abbr> - <abbr class="dtend" title="2005-05-25">2005</abbr>)
</li>
...
</nowiki></pre>

=== Experience ===
==== Basic ====
A basic experience event:

<pre><nowiki>
<ol class="vcalendar">
<li class="experience vevent">
President,
Preston High School,
<abbr class="dtstart" title="2004-09-01">May 2005</abbr> - <abbr title="2005-05-25">present</abbr>
</li>
...
</nowiki></pre>

==== Job Titles ====
To express multiple job titles/positions in the same experience event you should use [[hCard]]s. [[hcard]] requires the <code class="class-name">fn</code> ("formatted name") field, but it isn't reasonable to repeat your name for every job title you mark up in [[hResume]]. So, you may use an <code class="element"><object></code> with a reference to the <code class="class-name">fn</code> somewhere else on the page.

For example, this [[hCard]] refers to another [[hCard]]

<pre>

<object data="#j" class="fn n"></object>
Preston High School
Class President

</pre>

Where "<code class="attr-value">j</code>" is the id attribute value of the "<code class="mf-prop">fn n</code>" 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):

<pre><nowiki>
<address class="vcard">

Pedro
Sanchez

</address>
</nowiki></pre>

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.

=== Skills ===
Some sample skills tags:
<pre><nowiki>
I have skills in <a class="skill" rel="tag" href="http://en.wikipedia.org/wiki/Bow_%28weapon%29">bow hunting</a>
and <a class="skill" rel="tag" href="http://en.wikipedia.org/wiki/Nunchucks">nunchucks</a>.
</nowiki></pre>

=== Affiliations ===
<pre><nowiki>
National Honor Society
</nowiki></pre>

=== Publications ===
<pre><nowiki>
<cite>Breeding Ligers for Fun and Magic</cite>, Idaho Press, 2004.
</nowiki></pre>

== Examples in the wild ==
== Implementations ==
== References ==
=== Normative ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[hcalendar|hCalendar]]
* [[rel-tag]]
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]

Microformats Wiki - User contributions [en]

User:Robert Merrill

resume-brainstorming