hresume-feedback: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
Line 79: Line 79:
*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:
*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.
**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, &lt;address&gt; is a block-level element. And the spec says that is <strong>should</strong> be used, but not that it <strong>must</strong> 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).
**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.
[[User:Ianloic|Ianloic]] 15:58, 10 Dec 2006 (PST)
[[User:Ianloic|Ianloic]] 15:58, 10 Dec 2006 (PST)

Revision as of 19:51, 11 December 2006

hresume-feedback

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

Feedback

General Questions

See the hresume FAQ.

General Comments

    • I used hcalendar'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">
        <tr>
            <td class="level" rowspan="2">
                <abbr title="Advanced">A</abbr> Level
            </td>
            <th class="subject" scope="row">
                Business Studies
            </th>
            <td class="grade">
                B
            </td>
        </tr>
        <tr>
            <th class="subject" scope="row">
                Computing
            </th>
            <td class="grade">
                A
            </td>
        </tr>
    </tbody>

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]
 [position/title]
 [dates]
 [location]
 [Description]

Education

 [school]
 [major]
 [degree]
 [dates]
 [location]

Accreditation

 [type] (PD, CPA, JD and so on)
 [date]
  • 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)