resume-brainstorming-fr

Brainstorming CV

Ceci est un espace pour le brainstorming à propos d'un microformats pour les resumés/CVs fondé sur les exemples de CV qui ont été recherchés, documentés et analysés avec un oeil vers la réutilisation de portions de vocabulaires provenant de n'importe quels formats de CV.

Contributeurs

• Tantek Çelik
• Ryan King
• James Levine

(Traduction en cours Christophe Ducamp

Conséquence de

• CV-exemples
• formats de CV

Analyse

Analyse d'Exemples

Une première passe sur quelque analyse de l'analyse agrégée sur exemples de CV. Un 80/20 proposé :

affiliations	une liste d'affiliations, chacne avec un nom d'organisation, url et type d'association
contact info	contact info - address, email, url
education	une liste incluant les informations sur l'organisation/école (nom, lieu), degré/expertise d'étude, honneurs/récompenses, date (remise des diplômes seulement ou équivalent), GPA
employment/professional experience	une liste comprenant l'organisation, l'intervalle de temps, le titre de job et le lieu, les réalisations, la description
skills	un plan des compétences/outils éclaté en catégories générales
publications/presentation	une liste des articles, livres incluant chacun les auteur(s), titres, url et années de publication
summary/qualifications	une lsite de qualifications et compétences

laissé de côté à cette heure

Ce sont des choses trouvées dans les exemples de CV, qui semble sortir du schéma de construction 80/20 du CV commun. --RyanKing 14:46, 30 Jan 2006 (PST)

• objectif - utiliser simplement 'summary'
• statut - utiliser simplement 'summary'
• présentations et récompenses - ne sait pas comment généraliser ça
• récompenses - trop spécifiques et rares
• présentations - fera partie sûrement de l'un au-dessus, pas sûr où cela rentre à cette heure.
  • les présentations peuvent être simplement réunies avec d'autres citations ou des publications/travaux
• brevets - trop rares
  • peut-être que citations pourrait être utilisé pour les brevets, parce que ce sont des travaux publiés
• intérêts - trop rares
• portfolio - trop rare ?
• projets - trop rare ?
• exhibitions - trop rare ?

Méta-données supplémentaires

• Ce serait utile d'avoir les champs suivants associés avec 'skills' : Robert Merrill 07:41, 12 Feb 2006 (PST)
  • Skill-Level: Beginner, Advanced, Expert
  • Années d'expérience avec skill (numérique)
  • Last used : soit une valeur de "currently used" ou années depuis 'last-used'
• Malheureusemnet aucun de ceux listés au-dessus avec suffisamment de fréquence (si ce n'est pas du tout) dans les CV trouvés publiés dans la jungle, et en se basant sur le principe de simplicité et 80/20, cela fait du sens de simplement les omettre au moins pour la première version d'un microformat hResume. - Tantek

Autre Brainstorming

Ce qui suit est le résultat de quelques brainstorming entre les types de Technorati et SimplyHired.

Ensemble Minimal

Selon les types de SimplyHired qui voient beaucoup de CVs, un CV typique contient ces sections :

• Contact Info
• Education
• Work Experience
• Skills

Optionnellement

A nouveau, selon SimplyHired, ces sections sont moins communes :

• Objective
• interests
• references (pourraient être reliées à un job spécifique)

Fonctionnel

Quelques personnes publient des CVs fonctionnels, qui sont en quelque sorte sous le format inversé du traditionnel.

• Contact
• Work Experience
  • Company
    • Project
• skill
  • experience (job, education, etc)

Application des microformats actuels

See resume-formats for a description of common résumé elements. It seems that some of these constructs could easily be represented with existing microformats.

Contact

The contact info block of a résumé could be expressed with an hcard.

Education

Educational experience could be expressed as a list of hcalendars. The rationale is that education can be viewed as a long-running event- it would be easy to reuse the vocabulary from hCalendar for describing events.

Expérience Professionnelle

Just like Education, work experience could be expressed as a list of hcalendars.

Additionally, within a particular work experience, the list of job titles could be expressed as hcards. The only issue here is with having to repeat the FN for each of these hcards.

It might also be useful to extend XFN for marking up links to employers and clients.

Skills

Skills could be expressed as tags, using relTag. As with all rel-tag uses, a number of tagspaces would be appropriate.

Publications

Any publications, presentations, or other works could be represented by a citation microformat.

Références

References could be expressed as a list of hcards, though web-based résumés tend to be light on using references.

In our initial brainstorming, we talked about doing references in resumes. However, after doing the resume-examples research it doesn't seem that references are published on the web very often.

endorsements

LinkedIn allows users to endorse others' resumes. This functionality could be capture with vote-links.

Like the previous, this doesn't get used on the open web much, so I (Ryan King) think it should be left out, at least initially.

Brainstorming Session 2005-11-10

Contributeurs

• Tantek Çelik
• Ryan King
• James Levine

Photo de notre Session de Brainstorming

Compte-Rendu de la Session de Brainstorming

• "hresume" - root class name
  • "contact" hCard - should use <address>. Can be the person who the resume is about OR the proxy/contact in the case of recruiting/hiring services
  • "objective" - block of text explaining the objective
  • "job" hCalendar vevent - for each job in the jobs section:
    • hCard for title, org, address of company, (optionally, work phone numbers, etc.). For "fn" use indirection by referencing "contact" hCard above with an object tag as explained below.
  • "education" hCalendar vevent - for each school attended in the education section:
    • hCard for the school with fn==org, address of school, (optionally, url, phone numbers, etc.).
  • "skill" rel-tag - for each skill
  • <cite> for each publication
  • rel="reference" + XFN + hCard for references. rel="reference" makes sense because you are saying this person over here is a reference for the person represented by this resume.

The lists of jobs, education, skills, references should all use XOXO.

référence hCard via object

In typical resumes, each job listed also states the job title that the person had, as well as the name of the company, often the address (or at least city/state) of the company, and other information pertaining to the company.

This is effectively an hCard for the person while they were (are) working at that job, thus it makes sense to markup all that information as an hCard.

The only catch is, rarely do such hCards for each job include the person's name, visibly. Nor do we want to encourage people to replicate their name into those hCards (thus violating DRY) in invisible span elements. Thus the following code is proposed for a field (or several) in an hCard to reference another element in the document (likely the same field(s) in another hCard) and parse that other element as if it was inline in the hCard.

<span class="vcard">
 <object data="#j" class="fn n"></object>
 <span class="org">SimplyHired</span>
 <span class="title">Microformat Brainstormer</span>
</span>

Where "j" is the id attribute value of the "fn n" element of the contact hCard at the top of the page, e.g. (shown here as a verbose hCard for purposes of illustration that the reference may be to a subtree, not just a text node):

<span class="vcard">
 <span class="fn n" id="j">
  <span class="given-name">
   James
  </span>
  <span class="family-name">
   Levine
  </span>
 </span>
</span>

This method of hCard property indirection via an object element could be generalized to apply to any/all string/text properties in hCard.

Note: the object data attribute MUST be a local ID reference. External references (which would require a consuming application to load an external resource) are currently not supported by this method.

Issue: need to check with Brian Suda to see how easy/hard it would be to add this to X2V. Given that it wasn't too difficult to add the table td "headers" attribute content indirection support, this should be just as easy.

Status: According to Brian Suda: "... it shouldn't be too difficult... you are right it is pretty similar to the AXIS HEADER ID problems."

Next Steps: Brian will try implementing it in X2V and we'll see how well it works. If it works, then we'll add it to hCard, parsage hCard, and hReview 0.3 (as well as hResume of course). Note that the proposition hListing also has a similar requirement/concept and is currently using a notion of property inheritance from the context that it may be placed in (typically the page context). This may be an even nicer fallback from an authoring point of view, but may require more implicit parsing than can be relied upon.

Implemented:Brian Suda: i have managed to roll this into X2V pretty easy, it is only in the beta X2V code, if it proves useful and worth while then we can roll it into the production version.

Issue: These object elements end up rendering quite horribly in Safari, and display: none doesn't help. The solution is to style the objects with width: 0; height: 0;.

Plan de Strawman

Here's an outline of a strawman proposal.

proposition

affiliations

Two Suggestions:

1. class~="affiliation" + hcard -- use classname 'affiliation' + an hcard for the organization of which the user is a member
2. a rel or rev value for membership/affiliation (this doesn't capture the name of the organization or any other information, but could be useful outside resumes)

contact info

Simple, an hcard for the person in an <address>.

education

A list of hCalendar events, one for each education experience. We can either define a mapping of the terms, or just let loose and let conventions develop naturally.

employment/professional experience

A list of hCalendar events (one for each work experience). Optionally use hCards for describing job titles, organizational units, etc. We'll likely have a bit of a problem with not wanting to repeat FN for each hCard.

skills

Most resumes analyzed in the resume-examples page had a section for skills and/or qualifications. I think this usage can be best covered by using rel-tag, and not require a specific section for these tags. Perhaps add a 'skill' classname.

publications/presentation

Defer this problem to the citation work.

summary/qualifications

@class~="summary" (like hCalendar, hReview, etc.)

Strawman Draft

Just some space work working the draft schema out...

Format

In General

The hResume format is based on a set of fields common to numerous resumes published today on the web. Where possible field names have been chosen and reused from preexisting microformats.

Schema

The hResume schema consists of the following:

• hResume
  • summary. optional. text.
  • contact info. required. <address> + hCard.
  • education. optional. One or more hCalendar events with the class name 'education', with an embedded hCard indicating the job title, name of company, address of company etc.
  • experience. optional One or more hCalendar events with the class name 'experience', with an embedded hCard indicating the name of school, address of school etc.
  • skills. optional. phrases or keywords using the rel-tag microformat with the class name 'skill'.
  • affiliations. optional. the class name affiliation along with an hCard of the organization
  • publications. optional. One or more citations. Use cite tag.
  • references. optional. One or more references.

Field details

The fields of the hReview schema represent the following:

• summary:: This optional field serves as a overview of qualifications and objectives.
• contact:: Current contact info. The <address> with hcard.
• education:: the class name 'education' is applied to an hCalendar event.
• experience:: the class name 'experience' is applied to an hCalendar event. Job titles/positions should use an hCard.
• skills:: An hResume may be tagged using the rel-tag microformat and the 'skill' class name.
• affiliations:: The class name <code="class-name">affiliation is used along with an hCard of the organization
• publications:: just use <cite>. When there is a citation microformat, then that can be used in combination with the cite element to further markup the components of the citation.
• rel="reference". For references, link to the person with rel="reference" and any other XFN values that apply (e.g. "colleague", "co-worker", "friend", "kin" etc.), and use hCard to markup the name of the reference.

Notes

This section is informative.

• ...

Exemples

Summary

An example summary:

<p class="summary">
  I have 10 years experience with all Web 2.0 technologies– I've been working with Ajax since 1996, 
  designing with pastels while others will still using tiled background images and frames...
</p>

Contact

<address class="vcard">
  <span class="fn">Pedro Sanchez</span>
  <span class="adr">
    <span class="street-address">123 Fake St.</span>
    <span class="locality">Preston</span>, <span class="region">Idaho</span> <span class="postal-code">83263</span>
  </span>
  <span>Email: <a class="email" href="mailto:joe@example.com">pedro@vote-for-pedro.com</a></span>
  <span>Homepage: <a class="url" href="http://vote-for-pedro.com/">vote-for-pedro.com</a></span>
  <span>Phone: <span class="tel">+01.208.555.4567</span></span>
</address>

Education

<ol class="vcalendar">
  <li class="education vevent">
    <a class="url summary" href="http://example.edu/">Preston High School</a>
    (<abbr class="dtstart" title="1995-01-24">2001</abbr> - <abbr class="dtend" title="2005-05-25">2005</abbr>)
  </li>
  ...

Experience

Basique

A basic experience event:

<ol class="vcalendar">
  <li class="experience vevent">
    <span class="summary">President</span>,
    <span class="location">Preston High School</span>,
    <abbr class="dtstart" title="2004-09-01">May 2005</abbr> - <abbr title="2005-05-25">present</abbr>
  </li>
  ...

Titres de Job

To express multiple job titles/positions in the same experience event you should use hCards. hcard requires the fn ("formatted name") field, but it isn't reasonable to repeat your name for every job title you mark up in hResume. So, you may use an <object> with a reference to the fn somewhere else on the page.

For example, this hCard refers to another hCard

<span class="vcard">
  <object data="#j" class="fn n"></object>
  <span class="org">Preston High School</span>
  <span class="title">Class President</span>
</span>

Where "j" is the id attribute value of the "fn n" element of the contact hCard at the top of the page, e.g. (shown here as a verbose hCard for purposes of illustration that the reference may be to a subtree, not just a text node):

<address class="vcard">
  <span class="fn n" id="j">
    <span class="given-name">Pedro</span>
    <span class="family-name">Sanchez</span>
  </span>
</address>

This method of hCard property indirection via an object element could be generalized to apply to any/all string/text properties in hCard. Note: the object data attribute MUST be a local ID reference. External references (which would require a consuming application to load an external resource) are currently not supported by this method.

Skills

Some sample skills tags:

I have skills in <a class="skill" rel="tag" href="http://en.wikipedia.org/wiki/Bow_%28weapon%29">bow hunting</a> 
and <a class="skill" rel="tag" href="http://en.wikipedia.org/wiki/Nunchucks">nunchucks</a>.

Affiliations

<span class="affiliation vcard"><span class="fn org">National Honor Society</span></span>

Publications

<cite>Breeding Ligers for Fun and Magic</cite>, Idaho Press, 2004.

Références

Normatives

• XHTML 1.0 SE
• XMDP
• hCard
• hCalendar
• rel-tag
• RFC2119