hResume brainstorming

(Difference between revisions)

Jump to: navigation, search
(Possible Extensions: made structure modification to prep for hListing suggestion)
Current revision (12:36, 9 October 2011) (view source)
(Awards)
 
(7 intermediate revisions not shown.)
Line 1: Line 1:
-
<h1>hResume brainstorming</h1>
+
<entry-title>hResume brainstorming</entry-title>
This page is for brainstorming about various uses and details of [[hresume|hResume]] in particular. See [[resume-brainstorming]] for general brainstorming about a resume microformat.
This page is for brainstorming about various uses and details of [[hresume|hResume]] in particular. See [[resume-brainstorming]] for general brainstorming about a resume microformat.
-
 
-
__TOC__
 
== Possible Extensions ==
== Possible Extensions ==
=== Event Organisation/Participation ===
=== Event Organisation/Participation ===
 +
* [http://barcamp.org/ BarCamp] - as an organizer or participant this is somewhere between an invited presentation (which would be a publication), and "education".  Perhaps there is a need for a new explicit section for such activities and contributions thereto?
 +
** Perhaps abstracting into an activity section that would use hCalendar as per experience?
 +
*** Why not just use 'experience' as is? It seems general enough to be semantically correct. [[User:TobyInk|TobyInk]] 12:28, 19 Jul 2008 (PDT)
 +
<source lang=html4strict>
 +
<div class="hresume">
 +
  <div class="contact vcard" id="me">
 +
    <h1 class="fn">Joe Bloggs</h1>
 +
    ...
 +
  </div>
 +
  <div class="vcalendar" id="work">
 +
    <h2>Previous Work</h2>
 +
    <ul>
 +
      <li class="experience vevent">...</li>
 +
      <li class="experience vevent">...</li>
 +
      <li class="experience vevent">...</li>
 +
    </ul>
 +
  </div>
 +
  <div class="vcalendar" id="conferences">
 +
    <h2>Conferences &amp; Events</h2>
 +
    <ul>
 +
      <li class="experience vevent">...<span class="attendee"><a class="include" href="#me"></a></span></li>
 +
      <li class="experience vevent">...<span class="organizer"><a class="include" href="#me"></a></span></li>
 +
      <li class="experience vevent">...<span class="attendee"><a class="include" href="#me"></a></span></li>
 +
    </ul>
 +
  </div>
 +
</div>
 +
</source>
 +
 +
* Speaking, event organizing etc. (whether professional, or independent like BarCamps) should be listed as a "publication" - this should be an FAQ - no new feature is needed for this IMHO. - [[User:Tantek|Tantek]] 05:55, 20 March 2010 (UTC)
 +
 +
=== Awards ===
 +
* Some awards are for a certain time-frame, others are one-time awards. hCalendar appears appropriate to indicate a list of items with a date or date-range.
 +
** However an award is more an acknowledgment of a certain level of achievement rather than just a specific event. Awards seem closer to publications, though they may deserve their own section. I would be interested in seeing a class name property "award" if there are a good number of real world examples of online resumes with awards documented on [[resume-examples]]. - [[User:Tantek|Tantek]] 05:55, 20 March 2010 (UTC)
 +
** A new hResume field may solve the issue, something like: "award:: with an hCalendar event, optional hCard and an optional "duration" for awards that apply for a fixed length (e.g. health & safety certified for 2 yrs)". Where the vevent would have dtstart and dtend both as the date of the awarding, thus allowing it to appear correctly as a one day event in a parse to hCal, whereas more adaptable parsers would (changing with the spec) take note of the parent "award" class and thus display differently to a normal education or experience event. Looking at the list of hResumes in the wild there are lots of places such a change may be of use, one major example being the "Certifications" section of resumes on LinkedIn.com- [[User:Toby|Toby]] 01:16, 9 October 2011 (UTC)
 +
 +
=== Actively Seeking Employment ===
 +
''If [[hListing]] structure is found within the [[hResume]] document where the lister url is identical to the rel="me" url found in the hResume's hCard, then parsers should indicate this person is actively seeking employment.''
 +
 +
An hResume document lists a person's experience and employment history. It does not- and probably shouldn't- indicate whether the person is actively seeking employment.
 +
 +
While a person could state in the [[hresume#Summary|opening summary]] that they're actively seeking employment, this isn't guaranteed to be machine readable with a 100% success rate (different language and structure of text etc).
 +
 +
The existing microformat '[[hListing]]' is being proposed as a means of [[hlisting-extended-examples#Personal_.2F_Match.com|selling ones' self]]- and when a person is actively seeking employment, their resume is usually used as a means of selling themselves to prospective employers.
 +
 +
I'm proposing one of two things:
 +
 +
#Explict hListing support:
 +
#* If hListing is found, the person is actively seeking employment.
 +
#* If hListing is not found, '''''assume''''' the person is not actively seeking employment.
 +
#Implicit hListing support:
 +
#* If hListing is found, the person is actively seeking employment.
 +
#* If hListing is not found, '''''do not assume''''' the person is not actively seeking employment.
 +
 +
[[User:SignpostMarv|SignpostMarv]] 19:51, 18 Jul 2007 (PDT)
 +
 +
== for hResume 0.2 ==
 +
* incorporate {{must}} implement [[value-class-pattern]].
 +
 +
* consider adopting (for "skill" elements) category+[[rel-tag]] pattern like [[hCard]] and [[hCalendar]], don't require rel-tag.
 +
** same issue for [[hReview]], [[hReview-aggregate]], [[hListing]], [[hProduct]]
 +
** perhaps make category+rel-tag into a pattern for re-use.
-
[http://barcamp.org/ BarCamp] - as an organizer or participant this is somewhere between an invited presentation (which would be a publication), and "education".  Perhaps there is a need for a new explicit section for such activities and contributions thereto?
+
* consider requiring "experience vevent card" in order to provide a reliable hook for the business hCards connected with experience events.
== Related Pages ==
== Related Pages ==
{{hresume-related-pages}}
{{hresume-related-pages}}

Current revision


This page is for brainstorming about various uses and details of hResume in particular. See resume-brainstorming for general brainstorming about a resume microformat.

Contents

Possible Extensions

Event Organisation/Participation

<div class="hresume">
  <div class="contact vcard" id="me">
    <h1 class="fn">Joe Bloggs</h1>
    ...
  </div>
  <div class="vcalendar" id="work">
    <h2>Previous Work</h2>
    <ul>
      <li class="experience vevent">...</li>
      <li class="experience vevent">...</li>
      <li class="experience vevent">...</li>
    </ul>
  </div>
  <div class="vcalendar" id="conferences">
    <h2>Conferences &amp; Events</h2>
    <ul>
      <li class="experience vevent">...<span class="attendee"><a class="include" href="#me"></a></span></li>
      <li class="experience vevent">...<span class="organizer"><a class="include" href="#me"></a></span></li>
      <li class="experience vevent">...<span class="attendee"><a class="include" href="#me"></a></span></li>
    </ul>
  </div>
</div>

Awards

Actively Seeking Employment

If hListing structure is found within the hResume document where the lister url is identical to the rel="me" url found in the hResume's hCard, then parsers should indicate this person is actively seeking employment.

An hResume document lists a person's experience and employment history. It does not- and probably shouldn't- indicate whether the person is actively seeking employment.

While a person could state in the opening summary that they're actively seeking employment, this isn't guaranteed to be machine readable with a 100% success rate (different language and structure of text etc).

The existing microformat 'hListing' is being proposed as a means of selling ones' self- and when a person is actively seeking employment, their resume is usually used as a means of selling themselves to prospective employers.

I'm proposing one of two things:

  1. Explict hListing support:
    • If hListing is found, the person is actively seeking employment.
    • If hListing is not found, assume the person is not actively seeking employment.
  2. Implicit hListing support:
    • If hListing is found, the person is actively seeking employment.
    • If hListing is not found, do not assume the person is not actively seeking employment.

SignpostMarv 19:51, 18 Jul 2007 (PDT)

for hResume 0.2

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 brainstorming was last modified: Sunday, October 9th, 2011

Views