Documentation - Profile Structure

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

Example profile

Below is an example of an object/property structure for an individual profile stored in the ident.profiles collection or the ident.combinedProfile property.

 
{
   fn: "Glenn Jones",
   n: {
      "given-name": ["Glenn"],
      "family-name": ["Jones"]
   },
   adr: [{
      locality: "Brighton",
      country-name: "United Kingdom"
   }],
   nickname: ["glennjones"],
   note: ["Glenn Jones is the Creative Director and a founder of Madgex"],
   title: ["Creative Director"],
   url: ["http:\/\/www.glennjones.net\/"],

   name: "Identica",
   domain: "identi.ca",
   sourceUrl: ["http:\/\/identi.ca\/glennjones"]
}

Profile (hCard) structure

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

• vcard
  • adr
    • type [work|home|pref|postal|dom|intl]
    • post-office-box
    • street-address
    • extended-address
    • region
    • locality
    • postal-code
    • country-name
  • agent
  • bday" (ISO Date)
  • class
  • category rel="tag
  • email
    • type
    • value
  • fn
  • geo
    • latitude
    • longitude
  • key
  • label
  • logo
  • mailer
  • n
    • honorific-prefix
    • given-name
    • additional-name
    • family-name
    • honorific-suffix
  • nickname
  • note
  • org
    • organization-name
    • organization-unit
  • photo
  • rev
  • role
  • sort-string
  • sound
  • title
  • tel
    • type [home|work|pref|fax|cell|pager]
    • value
  • tz
  • uid
  • url

Additional non hCard properties

• name
• domain
• sourceUrl