{"id":71,"date":"2007-01-25T21:31:35","date_gmt":"2007-01-26T04:31:35","guid":{"rendered":"https:\/\/steveganz.org\/blog\/2007\/01\/linkedin-launches-hresume.html"},"modified":"2012-01-09T06:22:34","modified_gmt":"2012-01-09T13:22:34","slug":"linkedin-launches-hresume","status":"publish","type":"post","link":"https:\/\/steveganz.org\/blog\/2007\/01\/linkedin-launches-hresume.html","title":{"rendered":"LinkedIn Launches hResume"},"content":{"rendered":"<p>It is with great pleasure that I announce <a href=\"http:\/\/linkedin.com\/\">LinkedIn<\/a> has republished all <a href=\"http:\/\/linkedin.com\/in\/steveganz\">Public Profiles<\/a> marked up in the <a href=\"http:\/\/microformats.org\/wiki\/hresume\">hResume microformat<\/a>.<\/p>\n<p>LinkedIn has approximately 9 million registered users. By default, a user&#8217;s Public Profile is set to Basic View. The Basic View consists of the following information (the relevant hResume fields are <em>emphasized<\/em>):<\/p>\n<ul>\n<li><em>name<\/em><\/li>\n<li><em>current job title<\/em><\/li>\n<li><em>geographic region<\/em><\/li>\n<li>number of recommendations<\/li>\n<li>number of connections<\/li>\n<li>industry<\/li>\n<\/ul>\n<p>While the user has the ability to turn off Public Profile publishing altogether, only a small percentage have chosen to do so and with just the information listed above, the minimum requirement for hResume is met. In essence, <strong>we just launched ~9 million hResumes<\/strong>.<\/p>\n<p>Admittedly, the information in Basic View amounts to little more than a glorified hCard. It&#8217;s when you choose to activate Full View that hResume really gets a workout. In Full View we are able to implement just about everything available to us in the <a href=\"http:\/\/microformats.org\/wiki\/hresume#Schema\">hResume schema<\/a>:<\/p>\n<ul>\n<li><em>summary<\/em><\/li>\n<li><em>contact info<\/em><\/li>\n<li><em>experience<\/em><\/li>\n<li><em>education<\/em><\/li>\n<li><em>affiliations<\/em><\/li>\n<\/ul>\n<p>If you&#8217;re familiar with the hResume draft schema, you will notice that the missing fields are <em>skills<\/em> and <em>publications<\/em>.<\/p>\n<p>Unfortunately, in this first pass, we were unable to mark up <em>skills<\/em> according to the hResume specification. This is because we&#8217;ve always allowed free-form text for what we call &#8220;specialties&#8221; and while all of our examples show a comma delimited list of of keywords, it&#8217;s not enforced and a lot of users use this area for prose. Also, because hResume <em>skills<\/em> use <a href=\"http:\/\/microformats.org\/wiki\/rel-tag\">rel-tag<\/a>, we may end up needing to create our own tag space which isn&#8217;t trivial and will require significant work on our end. So in lieu of that, I&#8217;ve decided to mark up LinkedIn &#8220;specialties&#8221; with:<\/p>\n<p><code> &lt;p class=\"skills\"&gt;HTML, XHTML, CSS, DOM, JavaScript, W3C, web standards, front-end engineering, user interface development, user-centered design, usability, accessibility, semantic markup, microformats, unobtrusive JavaScript, DOM scripting&lt;\/p&gt;<\/code><\/p>\n<p>As for <em>publications<\/em>, we currently don&#8217;t have a field for that, but that&#8217;s something we could easily add in the future.<\/p>\n<p>Another thing to note is the way we&#8217;re handling an <em>experience<\/em> without an end-date. In other words, how do we communicate &#8220;present&#8221;? In a discussion with <a href=\"http:\/\/suda.co.uk\/\">Brian Suda<\/a>, we thought that using a time\/date stamp might be a novel way to handle the problem. So for a current <em>experience<\/em>, without an end date, we use the class of <code>dtstamp<\/code> and the current date for the value. The markup looks like this:<\/p>\n<p><code> &lt;p class=\"period\"&gt; &lt;abbr class=\"dtstart\" title=\"2006-11-01\"&gt;November 2006&lt;\/abbr&gt; \u00e2\u20ac\u201d &lt;abbr class=\"dtstamp\" title=\"2007-01-26\"&gt;Present&lt;\/abbr&gt; &lt;abbr class=\"duration\" title=\"P3M\"&gt;(3 months)&lt;\/abbr&gt; &lt;\/p&gt;<\/code><\/p>\n<p>Something else worth mentioning is <em>affiliations.<\/em> LinkedIn has two ways of handling this natively. First, we allow free-form text entry for general Groups and Associations on a users profile. Second, we have the formal <a href=\"http:\/\/www.linkedin.com\/static?key=groups_info\">LinkedIn for Groups<\/a> feature. In this first pass it is only the latter that gets marked up as an hResume <em>affiliation<\/em>. I hope to expand this in the future so that both entry methods get marked up as <em>affiliations<\/em>.<\/p>\n<p>So it&#8217;s a pretty big day for hResume! My hope is that this is a significant step towards elevating hResume from a draft into formal specification.<\/p>\n<p>I guess you could say the nucleus of this event was born back on September 21st, 2006 when lead Web Developer and one of LinkedIn&#8217;s founding team members, <a href=\"http:\/\/linkedin.com\/in\/chris\">Chris Saccheri<\/a>, sent me a LinkedIn Introduction asking if I would be interested in exploring an opportunity to join the LinkedIn team. Indeed I was, and one of the driving factors in my decision was the fact that Chris had already embraced <a href=\"http:\/\/microformats.org\/\">microformats<\/a> and was publishing LinkedIn data in hCard, XFN and hReview. I&#8217;d be hard-pressed to find another opportunity that would allow me to work not just on microformats in general, but specifically <a href=\"https:\/\/steveganz.org\/blog\/2006\/01\/hresume.html\">hResume, which I&#8217;ve had a love affair with since its inception<\/a>. It&#8217;s a testament to what a great place it is to work that I&#8217;ve been given the chance to accomplish this in my first couple of months here. I&#8217;m thrilled to be playing a part in the ongoing evolution of helping you build and manage your trusted professional network and promote your career online.<\/p>\n<p>Last, but certainly not least, I want to thank Brian Suda for taking the time to work with me on this over the holidays. He is a pillar of the microformats community and his involvement has been both invaluable and inspirational. Thanks also to <a href=\"http:\/\/factoryjoe.com\/\">Chris Messina<\/a> who has been a cheerleader for the adoption of microformats at LinkedIn over the past several months. And finally, thank you to <a href=\"http:\/\/theryanking.com\/\">Ryan King<\/a>, <a href=\"http:\/\/tantek.com\/\">Tantek \u00c3\u2021elik<\/a>, James Levine of <a href=\"http:\/\/simplyhired.com\/\">SimplyHired <\/a>and <a href=\"http:\/\/epeus.blogspot.com\/\">Kevin Marks<\/a> for <a href=\"http:\/\/microformats.org\/wiki\/resume-brainstorming\">planting the seeds<\/a>.<\/p>\n<p>I&#8217;m sure there are some things I&#8217;m forgetting, so if you have questions, please let me know. Any and all feedback is appreciated!<\/p>\n<p class=\"disclaimer\">P.S. To turn on Full View in your LinkedIn Public Profile, just log in and go to My Profile &gt; Public Profile and select Full View and Save Changes.<\/p>\n<p class=\"disclaimer\">P.P.S. The Public Profile is delivered as XHTML 1.0 transitional. It doesn&#8217;t validate at the present time because of various legacy systems that contribute to the overall output. There are plans to correct this, but it&#8217;s nothing that HTML Tidy can&#8217;t handle in the interim.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>It is with great pleasure that I announce LinkedIn has republished all Public Profiles marked up in the hResume microformat. LinkedIn has approximately 9 million registered users. By default, a user&#8217;s Public Profile is set to Basic View. The Basic View consists of the following information (the relevant hResume fields are emphasized): name current job [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-71","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/steveganz.org\/blog\/wp-json\/wp\/v2\/posts\/71","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/steveganz.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/steveganz.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/steveganz.org\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/steveganz.org\/blog\/wp-json\/wp\/v2\/comments?post=71"}],"version-history":[{"count":6,"href":"https:\/\/steveganz.org\/blog\/wp-json\/wp\/v2\/posts\/71\/revisions"}],"predecessor-version":[{"id":113,"href":"https:\/\/steveganz.org\/blog\/wp-json\/wp\/v2\/posts\/71\/revisions\/113"}],"wp:attachment":[{"href":"https:\/\/steveganz.org\/blog\/wp-json\/wp\/v2\/media?parent=71"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/steveganz.org\/blog\/wp-json\/wp\/v2\/categories?post=71"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/steveganz.org\/blog\/wp-json\/wp\/v2\/tags?post=71"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}