Errata and Updates

Known errors and issues in this specification are corrected in resolved and closed issues. Please check there before reporting issues .

The hCard 1.0.1 update is currently under development and incorporates known errata corrections as well as the value-class-pattern .

Background

Format

In General

1. The content of "FN" is broken into two "words" separated by whitespace.
2. The first word of the "FN" is interpreted as the "given-name" for the "N" property.
3. The second/last word of the "FN" is interpreted as the "family-name" for the "N" property.
4. Exception: If the first word ends in a "," comma, then the first word (minus the comma at the end) is interpreted as the "family-name" and the second word is interpreted as the "given-name".

This allows simplification in the typical case of people stating:

• given-name (space) family-name
• family-name (comma) given-name

Implied "nickname" Optimization

Due to the prevalence of the use of nicknames/handles/usernames in actual content published on the Web (e.g. authors of reviews), hCard also has an implied "nickname" optimization to handle this.

Similar to the implied "n" optimization, if "FN" and "ORG" are not the same, and the value of the "FN" property is exactly one word, and there is no explicit "N" property, then:

1. The content of the "FN" MUST be treated as a "nickname" property value.
2. Parsers SHOULD handle the missing "N" property by implying empty values for all the "N" sub-properties.

Though parsers MUST follow the implied nickname optimization, publishers SHOULD explicitly indicate the "nickname" even in this case, e.g.:

daveman692

The hCard MAY have additional explicit "nickname" property values in addition to the implied nickname.

Implied "organization-name" Optimization

The "ORG" property has two subproperties, organization-name and organization-unit. Very often authors only publish the organization-name. Thus if an "ORG" property has no "organization-name" inside it, then its entire contents MUST be treated as the "organization-name".

Tags as Categories

Categories in hCard MAY be represented by tags with rel-tag . When a category property is a rel-tag, the tag (as defined by rel-tag) is used for that category.

type subproperty values

The "type" subproperty in particular takes different values depending on which property it is a subproperty of. These "type" subproperty values are case-INSENSITIVE, meaning "Home" is the same as "home", as well as multivalued, e.g. a tel can be home and preferred:

TEL;TYPE=HOME,PREF:+1.415.555.1212

Home ( pref erred): +1.415.555.1212

This could be displayed as:

Home (pref erred): +1.415.555.1212

type with unspecified value

When the type of a property is specified, and there is no explicit value specified, then everything in the property except for the type is considered the value of the property. E.g.

Home +1.415.555.1212

is equivalent to:

Home +1.415.555.1212

And thus the type is "home" and the value is "+1.415.555.1212".

adr tel email types

Content that uses hCard SHOULD reference this profile, e.g.

"http://сайт/profile/hcard" >

This content uses "http://сайт/profile/hcard" > hCard .

"http://сайт/profile/hcard" >

(profile attribute is deprecated in HTML5) Content may combine the above methods as well.

Parsing Details

Examples

This section is informative.

Sample vCard

Here is a sample vCard:

BEGIN:VCARD VERSION:3.0 N:Çelik;Tantek FN:Tantek Çelik URL:http://tantek.com/ END:VCARD

and an equivalent in hCard with various elements optimized appropriately. See hCard Example 1 for the derivation.

This hCard might be displayed as:

Note: The version information is unnecessary in hCard markup directly since the version will be defined by the profile of hCard that is used/referred to in the "profile" attribute of the element.

Live example

Implementations

This section is informative . The number of hCard implementations has also expanded beyond the capacity of keeping them inline. They have been moved to a separate page .

Articles

This section is informative . For further reading on hCard see hcard-articles .

Buttons

You can use these buttons on pages with hCards. See buttons#hCard for any recent additions.

Copyright

Per the public domain release on the authors" user pages (Tantek Çelik , Brian Suda) this specification is released into the public domain.

Public Domain Contribution Requirement . Since the author(s) released this work into the public domain, in order to maintain this work"s public domain status, all contributors to this page agree to release their contributions to this page to the public domain as well. Contributors may indicate their agreement by adding the to their user page per the

Примеры

Данный раздел является информативным