hCard cheetsheet

Profile

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*

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

FAQ: "why 'adr'?"
URL in vCard becomes <a class="url" href=...>...</a> inside the element with class vcard in hCard.
Similarly, EMAIL in vCard becomes <a class="email" href="mailto:...">...</a>
PHOTO in vCard becomes <img class="photo" src=... alt="Photo of ..." /> or <object class="photo" data=... type=...>Photo of ...</object>
UID in vCard simply becomes another semantic applied to a specific URL (or EMAIL) for an hCard.
If an adr-child (e.g street-address) is present it will ONLY be considered part of the hCard data IF it is inside an adr.