hcard-cheatsheet: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
AndyMabbett (talk | contribs) m ({{hcard-related-pages}}) |
||
Line 62: | Line 62: | ||
* <code>PHOTO</code> in vCard becomes <code><img class="photo" src="..." alt="Photo of ..." /></code> or <code><object class="photo" data="..." type="...">Photo of ...</object></code> | * <code>PHOTO</code> in vCard becomes <code><img class="photo" src="..." alt="Photo of ..." /></code> or <code><object class="photo" data="..." type="...">Photo of ...</object></code> | ||
* <code>UID</code> in vCard simply becomes another semantic applied to a specific URL (or EMAIL) for an hCard. | * <code>UID</code> in vCard simply becomes another semantic applied to a specific URL (or EMAIL) for an hCard. | ||
{{hcard-related-pages}} |
Revision as of 22:15, 26 November 2006
- class="vcard"
- class="adr"
- class="type" [work|home|pref|postal|dom|intl]
- class="post-office-box"
- class="street-address"
- class="extended-address"
- class="region"
- class="locality"
- class="postal-code"
- class="country-name"
- class="agent"
- class="bday" (ISO date)
- class="class" – confidentiality/access classification of the entire hCard
- class="category"
- class="email"
- class="type"
- class="value"
- class="fn"
- class="geo"
- class="latitude"
- class="longitude"
- class="key"
- class="label"
- class="logo"
- class="mailer"
- class="n"
- class="honorific-prefix"
- class="given-name"
- class="additional-name"
- class="family-name"
- class="honorific-suffix"
- class="nickname"
- class="note"
- class="org"
- class="organization-name"
- class="organization-unit"
- class="photo"
- class="rev" – datetime of the revision of the entire hCard
- class="role"
- class="sort-string"
- class="sound"
- class="title"
- class="tel"
- class="type" [home|work|pref|fax|cell|pager]
- class="value"
- class="tz" – timezone of the person
- class="uid" – applies to the entire hCard
- class="url"
- class="adr"
- Key
- Single occurrence required
- One or more, required
- single occurrence optional
- zero or more occurrence
- [common list of values]
- (data format)
URL
in vCard becomes<a class="url" href="...">...</a>
inside the element withclass="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.
- 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.