hcard-cheatsheet
Revision as of 13:20, 28 May 2007 by RobertBachmann (talk | contribs) (Reverted edit of JdnUri, changed back to last version by AndyMabbett)
hCard cheetsheet
Profile
<head profile="http://www.w3.org/2006/03/hcard">
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*
- adr*
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
- FAQ: "why 'adr'?"
URLin vCard becomes<a class="url" href=...>...</a>inside the element with classvcardin hCard.- Similarly,
EMAILin vCard becomes<a class="email" href="mailto:...">...</a> PHOTOin vCard becomes<img class="photo" src=... alt="Photo of ..." />or<object class="photo" data=... type=...>Photo of ...</object>UIDin 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.
Geo
- If latitude is present, so MUST be longitude, and vice versa.
- Coordinates MAY be combined a single <abbr> element; then the latitude and longitude MUST be separated by a semicolon in the title attribute and latitude MUST be first:
<abbr class="geo" title="37.386013;-122.082932">home</abbr>
- The same number of decimal places SHOULD be used in each value.
- Coordinates use the datum of WGS84.
- Sources for latitude/ longitude coordinates
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