hcard-profile: Difference between revisions
Jump to navigation
Jump to search
(include 'value-title', add ids for each term, move alternate versions to separate section at end, change head code accordingly) |
m (→Other versions: dup url) |
||
| Line 217: | Line 217: | ||
== Other versions == | == Other versions == | ||
Previous versions of this profile on other sites: | Previous versions of this profile on other sites: | ||
* [ | * [http://www.w3.org/2006/03/hcard W3C 2006 hCard metadata profile] | ||
Other similar profiles: | Other similar profiles: | ||
* [http://www.w3.org/2006/vcard/ns W3C vCard namespace] | * [http://www.w3.org/2006/vcard/ns W3C vCard namespace] | ||
Revision as of 02:11, 6 August 2009
<entry-title>hCard Profile</entry-title>
The following is an XMDP profile for the hCard specification.
URLs
This profile is hosted as a separate XMDP file on microformats.org:
Usage
Profiles are referenced in (X)HTML files in the <HEAD> tag, e.g.:
<head profile='http://microformats.org/profile/hcard'>
Profile
<dl class="profile">
<dt>class</dt>
<dd><p>
<a href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
All values are defined according to the semantics defined in the
<a rel="contents start" href="http://microformats.org/wiki/hcard">
hCard specification</a>
and thus in
<a href="http://www.ietf.org/rfc/rfc2426.txt">RFC 2426</a>.</p>
<dl>
<dt id="vcard">vcard</dt>
<dd>A container for the rest of the class names defined in this XMDP profile.
See section 1. of RFC 2426.
</dd>
<dt id="fn">fn</dt>
<dd>See section 3.1.1 of RFC 2426.</dd>
<dt id="n">n</dt>
<dd>See section 3.1.2 of RFC 2426. May be inferred per
Implied "N" Optimization.</dd>
<dt id="family-name">family-name</dt>
<dd>See "Family Name" in section 3.1.2 of RFC 2426.</dd>
<dt id="given-name">given-name</dt>
<dd>See "Given Name" in section 3.1.2 of RFC 2426.</dd>
<dt id="additional-name">additional-name</dt>
<dd>See "Additional Names" in section 3.1.2 of RFC 2426.</dd>
<dt id="honorific-prefix">honorific-prefix</dt>
<dd>See "Honorific Prefixes" in section 3.1.2 of RFC 2426.</dd>
<dt id="honorific-suffix">honorific-suffix</dt>
<dd>See "Honorific Suffixes" in section 3.1.2 of RFC 2426.</dd>
<dt id="nickname">nickname</dt>
<dd>See section 3.1.3 of RFC 2426.</dd>
<dt id="photo">photo</dt>
<dd>See section 3.1.4 of RFC 2426. Typically used with an <img> tag.
Use the 'src' attribute for URI values. Use the 'data:' URI scheme for
binary values.</dd>
<dt id="bday">bday</dt>
<dd>See section 3.1.5 of RFC 2426. Typically used with an <abbr> tag
with the 'title' attribute for the date value, and a human readable date
inside the element.</dd>
<dt id="adr">adr</dt>
<dd>See section 3.2.1 of RFC 2426.</dd>
<dt id="post-office-box">post-office-box</dt>
<dd>See "post office box" in section 3.2.1 of RFC 2426.</dd>
<dt id="extended-address">extended-address</dt>
<dd>See "extended address" in section 3.2.1 of RFC 2426.</dd>
<dt id="street-address">street-address</dt>
<dd>See "street address" in section 3.2.1 of RFC 2426.</dd>
<dt id="locality">locality</dt>
<dd>See "locality" in section 3.2.1 of RFC 2426.</dd>
<dt id="region">region</dt>
<dd>See "region" in section 3.2.1 of RFC 2426.</dd>
<dt id="postal-code">postal-code</dt>
<dd>See "postal code" in section 3.2.1 of RFC 2426.</dd>
<dt id="country-name">country-name</dt>
<dd>See "country name" in section 3.2.1 of RFC 2426.</dd>
<dt id="type">type</dt>
<dd>See "type" in the various sections of RFC 2426.</dd>
<dt id="label">label</dt>
<dd>See section 3.2.2 of RFC 2426.</dd>
<dt id="tel">tel</dt>
<dd>See section 3.3.1 of RFC 2426.</dd>
<dt id="email">email</dt>
<dd>See section 3.3.2 of RFC 2426.</dd>
<dt id="mailer">mailer</dt>
<dd>See section 3.3.3 of RFC 2426.</dd>
<dt id="tz">tz</dt>
<dd>See section 3.4.1 of RFC 2426. Typically used with an <abbr> tag
with the 'title' attribute for the tz value, and a human readable time zone
inside the element.</dd>
<dt id="geo">geo</dt>
<dd>See section 3.4.2 of RFC 2426.</dd>
<dt id="latitude">latitude</dt>
<dd>See "latitude" in section 3.4.2 of RFC 2426.</dd>
<dt id="longitude">longitude</dt>
<dd>See "longitude" in section 3.4.2 of RFC 2426.</dd>
<dt id="title">title</dt>
<dd>See section 3.5.1 of RFC 2426.</dd>
<dt id="role">role</dt>
<dd>See section 3.5.2 of RFC 2426.</dd>
<dt id="logo">logo</dt>
<dd>See section 3.5.3 of RFC 2426. Typically used with an <img> tag.
Use the 'src' attribute for URI values. Use the 'data:' URI scheme for
binary values.</dd>
<dt id="agent">agent</dt>
<dd>See section 3.5.4 of RFC 2426. If the value is a vCard, then
use a nest hCard. For simplicity in that case, the same element that
has the class name of "agent" should use the class name of "vcard".</dd>
<dt id="org">org</dt>
<dd>See section 3.5.5 of RFC 2426.</dd>
<dt id="organization-name">organization-name</dt>
<dd>See "Organization Name" in section 3.5.5 of RFC 2426.
May be inferred per Implied "organization-name" Optimization.</dd>
<dt id="organization-unit">organization-unit</dt>
<dd>See "Organization Unit" in section 3.5.5 of RFC 2426.</dd>
<dt id="category">category</dt>
<dd>See section 3.6.1 of RFC 2426.</dd>
<dt id="note">note</dt>
<dd>See section 3.6.2 of RFC 2426.</dd>
<dt id="rev">rev</dt>
<dd>See section 3.6.4 of RFC 2426. Typically used with an <abbr> tag
with the 'title' attribute for the date value, and a human readable date
inside the element.</dd>
<dt id="sort-string">sort-string</dt>
<dd>See section 3.6.5 of RFC 2426.</dd>
<dt id="sound">sound</dt>
<dd>See section 3.6.6 of RFC 2426. Typically used with either an <a>
or <object> tag. Use the 'data:' URI scheme for binary values.</dd>
<dt id="uid">uid</dt>
<dd>See section 3.6.7 of RFC 2426.</dd>
<dt id="url">url</dt>
<dd>See section 3.6.8 of RFC 2426. Typically used with an <a> tag.
</dd>
<dt id="class">class</dt>
<dd>See section 3.7.1 of RFC 2426.</dd>
<dt id="key">key</dt>
<dd>See section 3.7.2 of RFC 2426. Typically used with an <abbr> tag
with the 'title' attribute for the key value, and a human readable key
equivalent inside the element.</dd>
<dt id="value">value</dt>
<dd>This class name is used to distinguish the <em>actual</em> value
of a property from any other cruft that may be in
the containing element representing the property.
See the
<a href="http://microformats.org/wiki/value-class-pattern">
value-class-pattern</a> for details.</dd>
<dt id="value-title">value-title</dt>
<dd>This class name is used to distinguish the <em>actual</em> value
of a property, specifically in the 'title' attribute of the element,
from the element contents and the element representing
the containing property.
See the
<a href="http://microformats.org/wiki/value-class-pattern#Parsing_value_from_a_title_attribute">
value-class-pattern value-title description</a> for details.</dd>
</dl>
</dd>
</dl>
Deprecated
2005-09-16:
The following class names have been deprecated in favor of singular names and the use of the "type" sub-property rather than class names for all of its values. hCard publishers MUST NOT use them as a class name.
- plurals:
- additional-names, honorific-prefixes, honorific-suffixes, categories
- type values:
- dom, intl, postal, parcel, home, work, pref, msg, voice, fax, cell, video, pager, bbs, modem, car, isdn, pcs, internet, x400
Other versions
Previous versions of this profile on other sites:
Other similar profiles:
Related Pages
- profile-uris
- Profile URI examples, in the wild
- 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.