[uf-discuss] HResume question
brian.suda at gmail.com
Thu Jun 21 08:16:26 PDT 2007
On 6/21/07, George Malamidis <george at nutrun.com> wrote:
> I've noticed that on many examples of HResume on the web (including
> all the HResumes on linkedin.com) are using class="skills" to
> decorate all the skills in a resume rather than class="skill" for
> each single skill.
--- according to the hResume spec, it should be class="skill", but it
should also be a rel-tag. Linked-in lets you use free text to describe
your skill, for example "top performing clown act in the world". That
doesn't fit into the current design for class="skill", so Linkedin
choose an alternatively semantic value - this is NOT part of hResume,
but instead simply POSH.
> Does anyone have any idea where this inconsistency originates from?
--- the inconsistancy comes from the hResume spec currently expecting
short skill lists, like "C++", "Microformats", "Cooking", whereas
Linked-in allows free-text. So (IMHO) they did the correct thing and
NOT try and make the free-text into a rel-tag.
> It makes parsing HResumes much harder and I was wondering if anyone
> has dealt with it in the past.
--- you shouldn't be parsing the class="skills" at the moment, because
it is NOT part of the spec, so that should make it much easier.
I have been talking with the Linked-in guys and we are working on
getting things either more inline with the current hResume format,
and/or gather examples to help incrementally improve hResume. I can't
seem to find any specific links/wiki pages at the moment, but if you
have any thoughts/concerns or want to know more, we can certainly
discuss it further - please use the new-list for any additional posts.
More information about the microformats-discuss