And the hits just keep on comin’.
I’m thrilled to be able to pass along Steve Ganz of LinkedIn‘s Twitter announcement (tweet?) of their support for hResume on LinkedIn (these tweets are becoming trendy!).
Brian Oberkirch is curious about the process they went through in applying microformats post facto — that is, without changing much of the existing codebase and design — and will have a podcast with Steve tomorrow on the topic. Personally I’m curious if they developed any best practices or conventions that might be passed on to other implementors that might improve the appearance and/or import/export of hResumes.
If you’ve been playing along, you’ll note that this is one of the first examples of a successful community-driven effort to create a microformat that wasn’t directly based on some existing RFC (like vcard and ical). Rather, a bunch of folks got together and pushed through the definition, research and iteration cycles and released a spec for the community to digest and expound upon.
Soon after, a WordPress plugin and a handy creator were released, Tails added support and then Emurse got hip: Elegant template has hResume support — long term planning, ya know? It’s your data, and we want to make it as flexible as possible.
.
I wrote about the importance of hResume in August:
Why is this better than going to Monster.com and others? Well, for one thing, you’re always in charge of your data, so instead of having to fill out forms on 40,000 different sites, you maintain your resume on your site and you update it once and then ping others to let them know that you’ve updated your resume. And, when people discover your resume, they come to you in a context that represents you and lets you stand out rather than blending into a sea of homogeneous-looking documents.
Similar threads have come up recently about XFN, hcard and OpenID on the OpenID mailing list and the possible crossover with hResume should not be ignored. When LinkedIn is already support hcard and XFN — it’s just a matter of time before they jump on OpenID and firmly plant themselves in the future of decentralized professional networks.
Oh, and the possibilities to accelerate candidate discovery for all those job boards shouldn’t be understated either.
Factory Joe 
Is that a customized version of Operator? Or are those bookmarklets in your browser?
I wholeheartedly agree about the acceleration of candidate discovery. The question is: Who is gonna be first and implement it the best?
It’s all growing so fast.
This is great! I’m working with a client who would be interested in this.
I can’t believe I read this and didn’t go “holy cow” the first time. This is huge news!
With that much data now available in a machine readable format, I’m curious to see what sort of mashups come of it…
.. I have discovered something about “CV-tagging” here:
http://www.socnetdir.com/profiles/cvtagx .
Sounds simple – could be an alternative to hresume ..
Angelica