Difference between revisions of "hresume-feedback"

From Microformats Wiki
Jump to navigation Jump to search
Line 118: Line 118:
<span class="entry-summary author vcard">
<span class="entry-summary author vcard">
  <span class="published">2010-MM-DD</span>  
  <span class="published">2010-05-18</span>  
  raised by <span class="fn">[[User:Toby|Toby]]</span>
  raised by <span class="fn">[[User:Toby|Toby]]</span>

Revision as of 19:33, 19 May 2010


This document is for keeping track of feedback about hResume, one of several microformats.


Consider using this format (copy and paste this to the end of the list to add your issues; replace ~~~ with an external link if preferred) to report issues or feedback, so that issues can show up in hAtom subscriptions of this issues page. If open issues lack this markup, please add it.

Please post one issue per entry, to make them easier to manage. Avoid combining multiple issues into single reports, as this can confuse or muddle feedback, and puts a burden of separating the discrete issues onto someone else who 1. may not have the time, and 2. may not understand the issue in the same way as the original reporter.

<div class="hentry">
<span class="entry-summary author vcard">
 <span class="published">2011-MM-DD</span> 
 raised by <span class="fn">~~~</span>
<div class="entry-content discussion issues">
* <strong class="entry-title">«Short title of issue»</strong>. «Description of Issue»
** Follow-up comment #1
** Follow-up comment #2


General Questions

See the hResume FAQ.

General Comments

  • There is somewhat of a conflict with the proposed draft. It has a "summary" class to identify summary of qualifications. This conflicts with the "summary" class in the vcalendar micro-format and there are multiple vcalendar tags included as part of the education and experience sections. As such there is a possibility that a summary tag in the resume may mistakenly be interpreted as a summary of qualifications instead of a summary of an event.
  • There should be a way to indicate certifications and licensing in a way that is distinct from education and affiliations. I propose the following certification class within the vcalendar, to include:
    • "fn org" (certifying or licensing organization)
    • "htitle summary" (certification name),
    • "date_duration" (date obtained & expiration date),
    • "org_identification" (certificate or license number)

Here is an example:

     <div class="vcalendar">
         <div class="certification vevent vcard">
             <span class="fn org">Cisco Systems</span>
             <div class="htitle">
                 <span class="summary">Cisco Certified Counter of These Rocks</span>
 	    <div class="date_duration">
                 <abbr class="dtstart" title="2000-01-01">2000</abbr>
                 <abbr class="dtend" title="2010-01-01">2010</abbr>
             <div class="certification_id">#1245</div>

  • Upon implementing hResume at http://davecardwell.co.uk/cv/, I had the following observations:
    • I used hCalendar 1.0's optional "description" element to include a short paragraph of text about each section of education/employment. The examples on the hResume page could be updated to mention this ability.
    • A richer way of marking up qualifications would have been nice. If you view the source of my resume you'll see I marked up each subject as a "skill". This, however, doesn't convey any information about the level or grade achieved. The minimal set for the main educational qualifications in England seems to be qualification(level, subject(s), grade(s)). A section from my resume would then be:
    <tbody class="qualification">
            <td class="level" rowspan="2">
                <abbr title="Advanced">A</abbr> Level
            <th class="subject" scope="row">
                Business Studies
            <td class="grade">
            <th class="subject" scope="row">
            <td class="grade">

Further investigation might show the need for optional information about awarding bodies and such. Not sure if a qualification element would satisfy the 80/20 condition.

Dave Cardwell 06:53, 19 Feb 2006 (GMT)

  • I and others on the #microformats IRC channel have expressed a concern about the way skills are represented. Introducing unnecessary links into a resume is undesirable, especially when you have to link to a page like http://en.wikipedia.org/wiki/Perl to conform to the rel-tag standard while http://www.perl.org might be more intuitive. Non-visual user agents like screen readers will have a great deal of meaningless links to trawl through, and search engines may infer relationships that do not exist.

Dave Cardwell 04:54, 22 Feb 2006 (GMT)

  • Our thoughts:

We would love to be able to mark-up the following data:

Contact Info = hCard

Experience (our issue is with current employment)*

 [company name]




 [type] (PD, CPA, JD and so on)
  • how do you represent current positions that have no end date? Maybe lack of date means present?

Here is our hResume plugin for WordPress (in development): <a href="http://www.flickr.com/photos/alexmuse/144781779/" title="Photo Sharing"><img src="144781779_ddc4d07460_o.jpg"</a>

Alexander Muse 08:54, 11 May 2006 (GMT)

  • Suggestion: Reference information - should there be a field of "References", where hCard information would be held for references? Also, perhaps a distinction between three types (e.g. personal (a friend), professional (e.g. previous boss), educational (e.g. university lecturer)) in a similar method to hCard's telephone type distinctions? If this is already accounted for, what method would you suggest for implementing this?
  • When working on my resume I tried to mark it up as hResume but I hit a couple of show-stoppers for me. If I had the choice of marking it up to look and behave like I wanted or be a valid hResume I'd chose for former and that's what I ended up having to do. My issues were:
    • It's recommended to put the contact hCard in an <address> but address is inline and I wanted to put block elements in there. I could have worked around that with CSS display: but I wanted to be able to render to text with links or w3m which don't support enough CSS for that.
      • Actually, <address> is a block-level element. And the spec says that is should be used, but not that it must be used.
    • hResume builds on rel-tag for describing skills, but I didn't want my skills section filled with links (no matter how they're rendered - I don't want them clickable).
      • Skills are optional, as are linking them.

Ianloic 15:58, 10 Dec 2006 (PST)

Lylo 11:04, 16 Feb 2007 (GMT)

  • Suggestion: I used hResume on a recent website for a client. The resume in question has an Awards section, with a list of industry awards and their corresponding dates. There is currently no specific way of representing this information in the hResume specification. Do the authors have any recommendations for the mark-up to use in this situation? Perhaps an award field could be considered by the authors?
    • Could you provide the URL for the hResume that you mention that is published on the Web? That way we can use it as an example in the wild with a real Awards section with content. If we get enough such examples in the wild of Awards sections, then we can figure out how to best add it to hResume Tantek 09:13, 16 Feb 2007 (PST)

open issue!

raised by Toby

  • Repeat of hcard. It is possible in education and experience (and with a character references section) to reference the same company/school more than once. This can cause confusion when using id's to distinguish between already multiple hcards, especially when using browser add-in parsers, like Michromeformats in chrome, to grab hcards from pages, would use of location in the vevent be a valid alternative.
    • Another suggestion would be to include one full hcard for each company/school in a hidden div or the like and use the include-pattern in the multiple places that each item may be needed?

Related Pages



hResume is the classic microformats predecessor for h-resume. Work on hResume is documented at the following for historical purposes. Much of the general discussion and research likely still applies.

The hResume specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.