hcard-cheatsheet

hCard cheetsheet

Properties (Class Names)

• vcard {1}
  • 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? confidentiality/access classification of the entire hCard
  • category*
  • email*
    • type?
    • value?
  • fn {1}
  • 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? datetime of the revision of the entire hCard
  • role*
  • sort-string?
  • sound*
  • title*
  • tel* (Note E.123 for formatting info.)
    • type [home|work|pref|fax|cell|pager]?
    • value?
  • tz? timezone of the person
  • uid? applies to the entire hCard
  • url*

Key

Based on Perl's standard quantifiers:

bold {1}	MUST be present exactly once
italic*	OPTIONAL, and MAY occur more than once
+	MUST be present, and MAY occur more than once
?	OPTIONAL, but MUST NOT occur more than once
[square brackets]	list of common values
(parentheses)	data format
#	comment
!	awaiting documentation

pref

preferred

dom

domestic

intl

international

cell

mobile

Notes

• URL in vCard becomes <a url href=...>...</a> inside the element with vcard in hCard.
• Similarly, EMAIL in vCard becomes <a email href=mailto:...>...</a>
• PHOTO in vCard becomes <img photo src=... alt=Photo of ... /> or <object photo data=... type=...>Photo of ...</object>
• UID in vCard simply becomes another semantic applied to a specific URL (or EMAIL) for an hCard.

Geo

• If latitude is present, so MUST be longitude, and vice versa.
• If the secondary classes are omitted, the two values MUST be comma separated and latitude MUST be first:<span class=geo>37.386013,-122.082932</span>
• The same number of decimal places SHOULD be used in each value.

Related pages

• hCard
• hCard cheatsheet - hCard properties
• hCard creator (feedback) - create your own hCard.
• hCard authoring - learn how to add hCard markup to your existing contact info.
• hCard examples - example usage of various classes within hCard.
• hCard examples in the wild - an on-going list of websites which use hCards.
• hcard-supporting-user-profiles - sites with user profiles marked up with hCard - a very common example.
• hCard FAQ - if you have any questions about hCard, check here.
• hCard implementations - websites or tools which either generate or parse hCards.
• hCard parsing - normative details of how to parse hCards.
• hCards and pages - semantic distinctions between different hCards on a page, and how to identify each
• hcard-user-interface - techniques and issues surrounding user-interfaces to author, publish, and display hCards.
• hCard profile - the XMDP profile for hCard
• hCard singular properties - an explanation of the list of singular properties in hCard.
• hCard tests - a wiki page with actual embedded hCards to try parsing.
• hCard advocacy - encourage others to use hCard
• hCard "to do" - jobs to do

The hCard specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.

• hCard brainstorming - brainstorms and other explorations relating to hCard.
  • hcard-parsing-brainstorming - brainstorming specific to parsing of hCard
  • geo brainstorming
• hCard feedback - general feedback (as opposed to specific issues).
• hCard issues - specific issues with the specification.
• vCard errata - corrections to the vCard specification, which underlies hCard.
• vCard suggestions - suggested improvements to the vCard specification.
• Other cheatsheets: hAtom cheatsheet, hCard cheatsheet (also adr cheatsheet + geo cheatsheet), hCalendar cheatsheet, hResume cheatsheet, hReview cheatsheet, PDF cheatsheet