For a couple of months I have been looking into options for presenting academics' CVs on the web in semantic xHtml. Of the options out there hResume rises to the surface. There are several reasons for this:
- Popularity of hResume in presenting CV's and Resumes.
- Microformats are about the interoperability of data through semantic markup - Academics generally want people to cite them, and resume publishers usually hope to have resume users and readers.
- Semantic markup of content allows for the semantic styling of content.
The largest challenge in implementing academic CVs in hResueme versus business resumes in hResume format is citations from publications and presentations along with that is the semantic markup of citations with standards like COinS (though COinS might not be true Semantic Markup). However, there are other challenges too. For instance how to categorize the sections of a CV. I work mostly with linguists and with the CV sections that linguists use. Therefore, I may be missing some crucial section of a CV as used by another academic discipline.hCalendar and hCard. So I have also mapped the elements of an hResume back to the building block microformat (per this list on microformat's website). These dependency formats are also presented. In the last column I have presented some remarks specific to that section.
Sections of a Linguist's CV
Sections in hResume
inclusion in hResume
Outstanding issue or question
|Contact info||Contact info||Obligatory||must use hCard; should use <address> + hCard||hCard is a Recommendation||how does the adr and the geo relate to the contact info or hCard?|
|Personal Info||Not designated||What would fit into this section which would not fit into the Contact info section? (married status) But that might be able to be expressed through XFN, unless the spouse is unnamed.|
|Photo||Not designated||Should hmedia be used for this photo?|
|Summary||Summary||Optional||None - No building block indicated.||None|
|Education||Education||Optional||One or more hcalendar events with the class name 'education', with an embedded hCard indicating the name of school, address of school etc.||hCalendar is a Recommendation|
|Education Abroad (Could be considered a sub-category of "Education")||Education||One or more hcalendar events with the class name 'education', with an embedded hCard indicating the name of school, address of school etc.||hCalendar is a Recommendation|
|Research interests||Not designated.||One could argue that this might be related to "skills", or marked with the rel-tag format.|
|Positions Held||Experience||Optional||One or more hcalendar events with the class name 'experience', with an embedded hCard indicating the job title, name of company, address of company etc.||hCalendar and hCard||The [hResume] draft should describe a way to handle a series of assignments at various employers within the context of one job working for a contracting, consulting, or temporary firm/agency. per mfreeman (2009)|
|Field Work||Experience||Optional||One or more hcalendar events with the class name 'experience', with an embedded hCard indicating the job title, name of company, address of company etc.||hCalendar and hCard, (my recommendation is to also consider using hGeo)||Field Work often has a Geo-Location and a language involved so I am not sure if it shouldn't also be marked up with hGeo and some rel-tag to the language.|
|Language Proficiency||Skills||Optional||rel-tag||rel-tag is a Recommendation||Often skills have an indication of the level of attainment - hResume does not have this. per ntoll (2007)|
|Computer Skills||Skills||Optional||rel-tag||rel-tag is a Recommendation|
|Teaching Experience||Experience||Optional||hCalendar and hCard||Embedding hCard for job title leads to ambiguities. per TobyInk (2010)|
|Awards & Honors||Not Designated||Support for Awards and for Service sections are not currently implemented. per jeffmcneill (2007)|
|Grants Received||Not Designated||This might be considered simular to Awards and Honors. But in most CVs I have seen it is given its own section level.|
|Publications||publications||Optional||A lot of work has gone into description or a hCite type of format. But nothing has evolved yet. To this end I have resolved myself to using CoinS. Although the official recomendation is to use the <cite> tag.|
|Edited Volumes (PR)||publications||Optional|
|Not Peer Reviewed||publications||Optional|
|Presentations||Not Designated||Generally these are cited like a publication but put in their own section.|
|Invited Talks||Not Designated||Generally these are cited like a publication but put in their own section.|
|Dissertations and Thesis supervised.||Not designated (but possibly like publications)||Generally these should be treated like publications.|
|Professional Associations||Affiliations||Optional||The class name affiliation along with an hcard of the organization.||hCard is a Recommendation|
|Professional Contacts||Not Designated||hCard and XFN should be used.||hCard is a Recommendation|
XFN is a Recommendation
|I am not clear on how XFN can be used in this context. But it seems that this is the sort of thing that XFN was created for. There is also still the same objection as mentioned by TobyInk (2010) because there is no way to tell who the primary hCard on the page referes to.|
- ↑1 CVs like resumes are unique to each individual so these categories are an abstraction and not all sections will be in every CV.