hresume-issues

(Difference between revisions)

Jump to: navigation, search
(Added representative-hcard suggestion to resolve hresume contact info)
(Issues)
Line 18: Line 18:
*#* In Draft, version 0.1 it is required that each "skill" be marked up with rel-tag. While this is a good idea, and easy to do for individuals, it poses some challenges in the real world for large publishers of user generated resume data.  If rel-tag was optional for "skills", it would be easier to implement.  
*#* In Draft, version 0.1 it is required that each "skill" be marked up with rel-tag. While this is a good idea, and easy to do for individuals, it poses some challenges in the real world for large publishers of user generated resume data.  If rel-tag was optional for "skills", it would be easier to implement.  
*#* +1, expecting a resume author to link out to a hypothetical tagspace is an unnecessary barrier to entry.  In reality authors end up linking to places like WikiPedia, which is not a real tagspace as defined in rel-tag. We should look at a more complex skill format for both this and the issue below opened by NTollervey. --[[User:CiaranMc|Ciaran McNulty]]
*#* +1, expecting a resume author to link out to a hypothetical tagspace is an unnecessary barrier to entry.  In reality authors end up linking to places like WikiPedia, which is not a real tagspace as defined in rel-tag. We should look at a more complex skill format for both this and the issue below opened by NTollervey. --[[User:CiaranMc|Ciaran McNulty]]
 +
*#* +1, I have tried very hard to think of ways to make rel-tag work for skills description. In the end I had to drop marking up skills altogether in hResume because I am unwilling to add meaningless hyperlinks.  As Ciaran mentioned we need a more complex structure that actual models to real world use. I have documented some alternative ideas [[hresume-skill-brainstorm|skill brainstorm]] [[User:GlennJones|Glenn Jones]]
* {{OpenIssue}} 2007-01-04 raised by [[User:NTollervey|ntoll]].
* {{OpenIssue}} 2007-01-04 raised by [[User:NTollervey|ntoll]].
-
*# ''With regard to the "skill" attributes in a resume: often skills have an indication of the level of attainment - be it as a descriptive "tag" or a duration denoting the length of experience of the referenced skill. In fact, abstracting out a "skill" microformat might be useful for re-use in the job-listing (Vacancy?) microformat. That way, job requirements can be married to CVs. Although not a job-site, I like Sourceforge.net's skill inventory feature (that captures both a level and length of experience) although I think its implementation is horrendous.''
+
*# ''With regard to the "skill" attributes in a resume:''
 +
*#* Often skills have an indication of the level of attainment - be it as a descriptive "tag" or a duration denoting the length of experience of the referenced skill. In fact, abstracting out a "skill" microformat might be useful for re-use in the job-listing (Vacancy?) microformat. That way, job requirements can be married to CVs. Although not a job-site, I like Sourceforge.net's skill inventory feature (that captures both a level and length of experience) although I think its implementation is horrendous.
 +
*#* +1, There are enough people using either skill ratings or denote duration for us to consider extending the skills. We already have two patterns in other microformats rating and ISO duration that could be used extend the structure [[hresume-skill-brainstorm|skill brainstorm]] [[User:GlennJones|Glenn Jones]]
* {{OpenIssue}} 2006-10-19 raised by [[RyanKing]].
* {{OpenIssue}} 2006-10-19 raised by [[RyanKing]].

Revision as of 09:12, 16 October 2009

hResume issues

These are externally raised issues about hResume with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec. Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — Tantek

See related hcalendar-issues. See related hcard-issues.

Contents


Issues

  • Agreed, when adding my references in hCard to the bottom of my hResume it became apparent there was no way I could mark 'my' hCard as the one belonging to the subject of the hResume. Perhaps @class="hcard subject" as a child of the hResume? Ciaran McNulty


  • open issue! 2009-02-21 raised by mfreeman
  • The 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.
  • For example, a person is employed by ABC Corp. as a Staff Consultant from 1/1/2000 to 12/31/2008. During that time, ABC Corp. placed the person at:
    • XYZ Inc. as a Business Analyst from 1/1/2000 to 12/31/2005
    • DEF LLC as a Technical Writer from 1/1/2006 to 6/1/2006
    • "on the bench" with no assignment from 6/2/2006 to 8/14/2006
    • OMG Inc. as a Database Designer from 8/15/2006 to 12/31/2008
  • The draft may already address this, but it is not obvious.

Related Pages

Research

Previously

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.

hresume-issues was last modified: Wednesday, December 31st, 1969

Views