hResume issues

(Difference between revisions)

Jump to: navigation, search
(Added representative-hcard suggestion to resolve hresume contact info)
Current revision (04:51, 7 April 2013) (view source)
m (Reverted edits by ABIDEEN10 (Talk) to last version by Tantek)
 
(6 intermediate revisions not shown.)
Line 1: Line 1:
-
<h1> hResume issues </h1>
+
<entry-title> hResume issues </entry-title>
-
These are externally raised issues about [[hresume|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. — [http://tantek.com/log/ Tantek]
+
These are externally raised issues about [[hresume|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. — [[User:Tantek|Tantek Çelik]]
See related [[hcalendar-issues]].
See related [[hcalendar-issues]].
Line 9: Line 9:
== Issues ==  
== Issues ==  
 +
=== issues 2012 ===
 +
* {{OpenIssue}} 2012-09-05 raised by [[User:Tantek|Tantek Çelik]]
 +
*# ''the "publications" property should be "publication" per [[naming]]''
 +
*#* the "publications" property in particular seems a bit off - it probably should have been "publication" per the [[naming]] principle, and used, e.g. <code>&lt;cite class="publication"&gt; ... </code>
 +
=== issues 2010 ===
 +
* {{OpenIssue}} 2010-03-17 raised by [[User:TobyInk|TobyInk]]
 +
*# ''Embedding hCard for job title leads to ambiguities.''
 +
*#* It's tempting to assume that any <code>class="vcard"</code> within the <code>class="experience"</code> must be an hCard representing the contact while they were at the organisation (e.g. <code>class="title"</code> represents their job title, <code>class="role"</code> their role, etc). But there's no guarantee of that. e.g. <code>&lt;span class="experience vevent">...&lt;span class="location vcard">&lt;i class="fn">Employer's Name&lt;/i>&lt;/span>...&lt;/span></code>.
 +
*#** Suggested solution: provide a class name for indicating that a particular hCard represents the contact while they were at the organisation. e.g. <code>class="vcard me"</code>.
 +
*#** Suggested solution: based on a couple of recent real world: [[hresume-examples-in-wild]] ([http://jessecravens.com/resume], [http://www.mrgaetan.eu/cv/gaetan-riou-cv.html]) which both use the same pattern, it seems reasonable to use the class name vcard on the same element as experience and vevent. This solution appears to be sufficient to resolve the issue, and does not require any new class names. - [[User:Tantek|Tantek]] 19:58, 18 March 2010 (UTC)
 +
*#*** <code>class="experience vevent vcard"</code> - indicates both the hCard for the job title as well as the event for the experience on the same element.
 +
=== issues 2009 ===
 +
<div class="vevent">
 +
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2009-02-21</span> raised by <span class="fn">[http://microformats.org/wiki/User:mfreeman mfreeman]</span></span>
 +
<div class="description">
 +
*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.
 +
</div>
 +
</div>
 +
 +
=== issues 2007 ===
* {{OpenIssue}} 2007-10-02 raised by [[User:JeffMcNeill|jeffmcneill]].
* {{OpenIssue}} 2007-10-02 raised by [[User:JeffMcNeill|jeffmcneill]].
*# ''Support for Awards and for Service sections are not currently implemented''
*# ''Support for Awards and for Service sections are not currently implemented''
Line 18: Line 44:
*#* 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]]
 +
=== issues 2006 ===
* {{OpenIssue}} 2006-10-19 raised by [[RyanKing]].
* {{OpenIssue}} 2006-10-19 raised by [[RyanKing]].
*# ''There's currently no way to say 'present' in hCalendar''
*# ''There's currently no way to say 'present' in hCalendar''
Line 35: Line 65:
:::* 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? [[User:CiaranMc|Ciaran McNulty]]
:::* 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? [[User:CiaranMc|Ciaran McNulty]]
*#* hCards can be differentiated by their <code>id</code>. [[representative-hcard|Representative hCard]] might be sufficient to point out the contact info of the hResume -- [[User:Csarven|Sarven Capadisli]] 12:22, 9 September 2009 (UTC)
*#* hCards can be differentiated by their <code>id</code>. [[representative-hcard|Representative hCard]] might be sufficient to point out the contact info of the hResume -- [[User:Csarven|Sarven Capadisli]] 12:22, 9 September 2009 (UTC)
-
 
-
 
-
<div class="vevent">
 
-
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2009-02-21</span> raised by <span class="fn">[http://microformats.org/wiki/User:mfreeman mfreeman]</span></span>
 
-
<div class="description">
 
-
*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.
 
-
</div>
 
-
</div>
 
== Related Pages ==
== Related Pages ==
{{hresume-related-pages}}
{{hresume-related-pages}}

Current revision


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 Çelik

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

Contents


Issues

issues 2012

issues 2010

issues 2009

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

issues 2007

issues 2006

  • 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

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: Sunday, April 7th, 2013

Views