Documentation - Resume Structure

The Identi Engine resume structure is based on the microformat hResume. There are a number of additional non hResume properties that hold meta information about origin and content type.

Example resume

Below is an example of an object/property structure for an individual resume stored in the ident.resumes collections.

 
{
   summary: Glenn Jones is the Creative Director... ,
   education: [{
      summary: University of Brighton,
      description: BA (Hons) ...,
      fn:University of Brighton,
      org: [University of Brighton]
   },
   {
      summary: Harrogate Art College,
      description: Art Foundation...,
      fn: Harrogate Art College,
      org: [Harrogate Art College]
   }],
   experience: [{
      summary: Madgex,
      dtstamp: 2009-07-28,
      dtstart: 2000-12-01,
      duration: P8Y8M,
      fn: Glenn Jones,
      n: {
         given-name: [Glenn],
         family-name: [Jones]
      },
      org: [Madgex],
   title: [Creative Director]
   }],
   contact: {
      fn: Glenn Jones,
      n: {
         given-name: [Glenn],
         family-name: [Jones]
      },
      adr: [{
         locality: Brighton
      }],
      title: [Creative Director]
   }

   name: Linked in,
   domain: linkedin.com,
   sourceUrl: [http:\/\/linkedin.com\/in\/glennjones]
}

Resume (hResume) structure

Below is an outline of the hResume object/property structure:

Important: It is not uncommon for the experience and education objects to be expanded so that they contain both hCard and hCalendar structures.

• hresume
  • affiliation (hCard)
  • education (hCalendar)
  • experience (hCalendar)
  • publication
  • skill rel="tag
  • summary
  • contact (hCard)

Additional non hResume properties

• name
• domain
• sourceUrl