Microformats Wiki - User contributions [en]

hcalendar-profile

2007-04-24T08:49:32Z

Vadania: Second pass at an XMDP profile: XMLized existing description, added "attendee", "contact", and "organizer" commensurate with "Semantic Equivalents" section of the hcalendar page.

''Here's a second pass at a
[http://dannyayers.com/microformats/hcalendar-profile XMDP Profile for hCalendar]''

<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" 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 href="http://microformats.org/wiki/hcalendar">
hCalendar specification</a>
and thus in
<a href="http://www.ietf.org/rfc/rfc2445.txt">RFC 2445</a>.
</p>
<dl>
<dt>vcalendar</dt>
<dd>A container for one or more events (vevent).
This property is optional; if there is only one event then omit it.
See section 1. of RFC 2445.
</dd>

<dt>vevent</dt>
<dd>A container for one event.
See section 4.6.1 of RFC 2445.
</dd>

<dt>dtstart</dt>
<dd>Date/time of the start of the event.
See section 4.8.2.4 of RFC 2445.
</dd>

<dt>dtend</dt>
<dd>Date/time of the end of the event.
See section 4.8.2.2 of RFC 2445.
</dd>

<dt>duration</dt>
<dd>Length of the event.
See section 4.8.2.5 of RFC 2445.
</dd>

<dt>summary</dt>
<dd>Short synopsis, title, or name of the event.
See section 4.8.1.12 of RFC 2445.
</dd>

<dt>uid</dt>
<dd>A globally unique identifier for the event; typically a URL is used.
See section 4.8.4.7 of RFC 2445.
</dd>

<dt>dtstamp</dt>
<dd>Date/time of when the document containing information about the event
was created.
See section 4.8.7.2 of RFC 2445.
</dd>

<dt>method</dt>
<dd>Function of the event object.
Values for this property are: PUBLISH, REQUEST, REPLY, ADD, CANCEL, REFRESH,
COUNTER, or DECLINECOUNTER. For example, a value of REQUEST indicates that a
request is being made for the event to occur.
See section 4.7.2 of RFC 2445.
</dd>

<dt>category</dt>
<dd>Category of the event object.
Note: this property may be repeated (an event may belong in several categories).
Common values are: MEETING, APPOINTMENT, CONFERENCE, EXPO.
See section 4.8.1.2 of RFC 2445.
</dd>

<dt>location</dt>
<dd>Tells where the event is to be held. May be represented by nested
<a href="http://microformats.org/wiki/hcard">hCard record</a>,
<a href="http://microformats.org/wiki/adr">adr record</a>,
<a href="http://microformats.org/wiki/geo">geo record</a>, or combination thereof.
See sections 4.8.1.7 and 4.8.1.6 of RFC 2445.
</dd>

<dt>url</dt>
<dd>A URL to a page that contains the definitive/preferred information about an event;
UID and URL are typically the same.
See section 4.8.4.6 of RFC 2445.
</dd>

<dt>description</dt>
<dd>A more detailed synopsis of the event than that provided by summary.
See section 4.8.1.5 of RFC 2445.
</dd>

<dt>last-modified</dt>
<dd>Date/time the information about the event was updated.
See section 4.8.7.3 of RFC 2445.
</dd>

<dt>status</dt>
<dd>Status of the calendar event. Values are: TENTATIVE, CONFIRMED, CANCELLED.
See section 4.8.1.11 of RFC 2445.
</dd>

<dt>class</dt>
<dd>Access classification of the event information;
Values are: PUBLIC, PRIVATE, CONFIDENTIAL.
See section 4.8.1.3 of RFC 2445.
</dd>

<dt>attendee</dt>
<dd>An individual invited to attend the event;
An event container may contain more than one attendee record;
May be represented by nested <a href="http://microformats.org/wiki/hcard">hCard record</a>.
See section 4.8.4.1 of RFC 2445.
</dd>

<dt>contact</dt>
<dd>Contact information associated with the event;
May be represented by nested <a href="http://microformats.org/wiki/hcard">hCard record</a>.
See section 4.8.4.2 of RFC 2445.
</dd>

<dt>organizer</dt>
<dd>The organizer associated with the event;
May be represented by nested <a href="http://microformats.org/wiki/hcard">hCard record</a>.
See section 4.8.4.3 of RFC 2445.
</dd>

</dl>
</dd>
</dl>

</pre>

== Related Pages ==
{{hcalendar-related-pages}}

irc-people

2007-04-24T08:18:21Z

Vadania: Added self

A list of [[irc|IRC]] regulars sorted by nick and their normal timezones (winter/summer).

* [[User:WebOrganics|weborganics]] (+0100)
* [[User:Adam Craven|AdamCraven]] (+0000)
* [[User:Alexander Graf|AlexanderGraf]] (+0100)
* [[User:AmanuelTewolde|Amanuel]] (-0500/-0400)
* [[User:Amette|amette]] (+1000)
* [[User:Amir Guindehi|AmirGuindehi]] (+1000)
* [[User:Ashley|Ashley]] (+1000)
* [[User:B.K._DeLong|bkdelong]] (-0500/-0400)
* [[User:Tyler Roehmholdt|Baristo]] (-0800/-0700)
* [[User:Ben Ward|BenWard]] (+0000)
* [[User:BenjaminCarlyle|BenjaminCarlyle]] (+1000)
* [[User:HenriBergius|bergie]] (+0200/+0300)
* [[User:BenWest|bewest]] (-0800/-0700)
* [[User:BluesMoon|bluesmoon]] (+0530)
* [[User:BobChao|BobChao]] (+0800)
* [[User:Bob Jonkman|BobJonkman]] (-0500/-0400)
* [[User:Boneill|boneill]] (+0000)
* [[User:Brian|briansuda]] (+0000)
* [[User:BryanRieger|Bryan Rieger]] (+0000)
* [[User:Bug-E|Bug-E]] (+0200)
* [[User:Cgriego|cgriego]] (-0600/-0500)
* [[User:CharlesRoper|charles_r]] (0000/+0100)
* [[User:Charlvn|Charl]] (+0200/+0200)
* [[User:ChristopherStJohn|cks]] (-0600/-0500)
* [[User:Cloud|Cloud]] (+0000)
* [[User:Colin_Barrett|cbarrett]] (-1000)
* [[User:ColinDDevroe|cdevroe]] (-0500/-0600)
* [[User:Csarven|csarven]] (-0500/-0400)
* [[User:DavidMead|DavidMead]] (-0400)
* [[User:DerrickPallas|DerrickPallas]] (-0800/-0700)
* [[User:Dan Kubb|dkubb]] (-0800/-0700)
* [[User:DanC|DanC]] (-0600/-0500)
* [[User:DannyAyers|danja]] (+0100/+0200)
* [[User:Dave Cardwell|davecardwell]] (+0000)
* [[User:DenisDefreyne|ddfreyne]] (+0100/+0200)
* [[User:DeanEro|deanero]] (-0800/-0700)
* [[User:DiegoBudny|DiegoBudny]]
* [[User:DimitriGlazkov|dglazkov]] (-0600/-0500)
* [[User:DrewMcLellan|drewinthehead]] (+0000/+0100)
* [[User:DrewBell|droob]] (-0600/-0500)
* [[User:DimitriosZachariadis|dzach]] (+0200/+0300)
* [[User:Ed Summers|edsu]] (-0500/-0400)
* [[User:Enric|enric]] (-0800/-0700)
* [[User:Enric|Enric]] (-0800/-0700)
* [[User:Evan|evanpro]] (-0500)
* [[User:ChrisMessina|factoryjoe]] (-0800/-0700)
* [[User:Fil|Fil]] (+0200)
* [[User:MarkNormanFrancis|Mark Norman Francis]] (+0000/+0100)
* [[User:MarkoMrdjenovic|friedcell]] (+0100/+0200)
* [[User:Griffin|Griffin]] (-0600/-0500)
* [[User:Grantbow|Grantbow]] (-0800/-0700)
* [[User:Aubergine10|Guy Fraser]] (+0100/+0000)
* [[User:HenrichPoehls|HenrichP]] (+0100)
* [[User:Hlb|hlb]] (+0800-0700)
* [[User:IanHickson|Hixie]] (-0800/-0700)
* [[User:EdwardOConnor|hober]] (-0800/-0700)
* [[User:Ichigo|ichigo]] (+1000)
* [[User:IwaiMasaharu|iwaim]] (+0900)
* [[User:Izo|IZO]]
* [[User:JamieKnight|JamieKnight]] (+1000/0000)
* [[User:WizardIsHungry|jcw9]] (-0500/-0400)
* [[User:Adactio|Jeremy Keith]] (+0000)
* [[User:JasonK|jkridner]] (-0600/-0500)
* [[User:JoeGregorio|jcgregorio]]
* [[User:Jonathan_Arkell|jonnay]] (-0700/0600)
* [[User:JulianStahnke|Julian Stahnke]] (+0000)
* [[User:Kapowaz|kapowaz]] (+0000/+0100)
* [[User:Keri Henare|kerihenare]] (+1200)
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)
* [[User:RyanKing|kingryan]] (-0800/-0700)
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC
* [[User:Lachlan Hunt|Lachy]] (+1000/+1100)
* [[User:Mark Mansour|Mark Mansour]] (+1100)
* [[User:CiaranMc|McNulty]] (+0000/+0100)
* [[mfbot]] - a bot which logs all edits to this wiki. It appends a number with a '+' or '-' sign, to indicate the number of characters added or removed as a result of the edit.
* [[User:Mike|Michael McCracken(mmc)]] (-0800/-0700)
* [[User:MikeKaply|mkaply]] (-0600/-0500)
* [[User:SteveIvy|monkinetic/redmonk]] (-0700)
* [[User:neuro|neuro`]]
* [[User:NTollervey|ntoll]] (+0000/+0100)
* [[User:Phae|Phae]] (+0000/+0100)
* [[User:PriitLaes|plaes]] (+0200/+0300)
* [[User:ChrisCasciano|pnhChris]] (-0500/-0400)
* [[User:PetarPopov|popov]] (-0800/-0700)
* [[User:DavidOsolkowski|qid]] (-0500)
* [[User:RCanine|RCanine]] (-0500/-0400)
* [[User:Remi|Remi]] (-0500/-0400)
* [[User:RobertBachmann|RobertBachmann]] (+0100/+0200)
** Office hours: <del>Wednesday, 18:00-20:00 UTC</del> (Currently no office hours)
* [[User:Ronnos|Ron Kok]] (+0000)
* [[User:Dana Benson|Snowden]] (-0800/-0700)
* [[User:Smackman|Steve Farrell]] (-0800/-0700)
* [[User:Steve Ganz|SteveGanz]] (-0800/-0700)
* [[User:SuperPhly|SuperPhly]] (-600/-500)
* [[User:Tantek|Tantek]] (-0800/-0700)
* [[User:Trovster|trovster]] (-0800/-0700)
* [[User:Vadania|vadania]] (-0600/-0700)
* [[User:Vant|vant]] (+0900)
* [[User:KrissWatt|VoodooChild]] (+0000/+0100)
* [[User:JacksonWilkinson|whafro]] (-0500/-0400)
* [[User:Richard Conyard|WhiskeyM]] (+0000)
* [[User:Veeliam|William Lawrence]] (-0800/-0700)
* [[User:Ianloic|yakk]] (-0800/-0700)
* [[User:StevenWoods|woodss]] (+0000 GMT)

hcard

2007-04-22T02:29:02Z

Vadania: Fixing a typo (missing '=') at line 7, char 33 which caused an XML / SGML parse error.

<h1>hCard</h1>

hCard is a simple, open, distributed format for representing people, companies, organizations, and places, using a 1:1 representation of the properties and values of the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in [[semantic-xhtml|semantic XHTML]]. hCard is one of several open [[microformats|microformat]] standards suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML.

Want to get started with writing an [[hcard|hCard]]? Use the [http://microformats.org/code/hcard/creator hCard creator] to write up some contact information and publish it, or follow the [[hcard-authoring|hCard authoring tips]] to add hCard markup to your current contact page.

__TOC__

== Specification ==

=== Editor ===
[http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]

=== Authors ===
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]
* [http://suda.co.uk/ Brian Suda]

=== Copyright ===
{{MicroFormatCopyrightStatement2004}}

=== Patents ===
{{MicroFormatPatentStatement}}

=== Inspiration and Acknowledgments ===
Thanks to: my good friend [http://vadim.com/ Vadim] who introduced me to vCard ''many'' years ago, and if I'd only paid more attention then, perhaps I could have helped a lot of people avoid wasting a lot of time reinventing various standards wheels.

== Introduction ==
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), has been broadly interoperably implemented (e.g. Apple's "Address Book" application built into MacOSX).

In addition, many bloggers identify themselves by name and discuss their friends and family. With just a tad bit of structure, bloggers can discuss people in their blog(s) in such a way that spiders and other aggregators can retrieve this information, automatically convert them to vCards, and use them in any vCard application or service.

This specification introduces the '''hCard''' format, which uses a 1:1 representation of the properties and values of the aforementioned vCard standard, in semantic XHTML. Bloggers can both embed hCards directly in their web pages, and style them with CSS to make them appear as desired. In addition, hCard enables applications to retrieve information directly from web pages without having to reference a separate file.

Use the [http://microformats.org/code/hcard/creator hCard creator] and copy the HTML code it generates to your blog or website to publish your contact info.

== Semantic XHTML Design Principles ==
{{semantic-xhtml-design-principles}}

== Format ==
=== In General ===
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) forms the basis of hCard.

The basic format of hCard is to use vCard object/property names in lower-case for class names, and to map the nesting of vCard objects directly into nested XHTML elements.

=== More Semantic Equivalents ===
For some properties there are HTML elements which better match and convey their semantics. The following properties SHOULD be encoded with the following (X)HTML:
* <code>URL</code> in vCard becomes <code><a class="url" href="...">...</a></code> inside the element with <code>class="vcard"</code> in hCard.
* Similarly, <code>EMAIL</code> in vCard becomes <code><nowiki><a class="email" href="mailto:...">...</a></nowiki></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.

=== Singular vs. Plural Properties ===
For properties which are singular (e.g. "N" and "FN"), the first descendant element with that class should take effect, any others being ignored.

For properties which can be plural (e.g. "TEL"), each class instance should create a instance of that property.

==== Singular properties ====

Singular properties: "FN", "N", "BDAY", "TZ", "GEO", "SORT-STRING", "UID", "CLASS".

All other properties are plural. This list has been derived by analyzing the semantics of the individual properties in vCard RFC2426 and determining logically that they MUST be singular per their semantics. See [[hcard-singular-properties]] for explanations.

==== Plural Properties Singularized ====

Since plural property names become their singular equivalents, even if the original plural property permitted only a single value with multiple components, those multiple components are represented each with their own singularly named property and the the property is effectively multivalued and subject to the above treatment of multivalued properties.

=== Human vs. Machine readable ===

If an <code><abbr></code> element is used for a property, then the '<code>title</code>' attribute of the <code><abbr></code> element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value.

If an <code><a></code> element is used for one or more properties, it must be treated as follows:
# For the "PHOTO" property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for one or more properties, it must be treated as follows:
# For the "PHOTO" property and any other property that takes a URL as its value, the <code>src="..."</code> attribute provides the property value.
# For other properties, the <code><img></code> element's '<code>alt</code>' attribute is the value of the property.

If an <code><object></code> element is used for one or more properties, it must be treated as follows:
# For the "PHOTO" property and any other property that takes a URL as its value, the <code>data="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

=== Value excerpting ===

Sometimes only part of an element which is the equivalent for a property should be used for the value of the property. This typically occurs when a property has a subtype, like TEL. For this purpose, the special class name "<code>value</code>" is introduced to excerpt out the subset of the element that is the value of the property. E.g. here is an hCard fragment for marking up a home phone number:<br />

vCard:
<pre><nowiki>
TEL;TYPE=HOME:+1.415.555.1212
</nowiki></pre>

hCard:
<pre><nowiki>
<span class="tel">
<span class="type">home</span>:
<span class="value">+1.415.555.1212</span>
</span>
</nowiki></pre>

This hCard fragment could be displayed as:

<div style="border: thin dashed black; width: 95%; padding: .5em 1em;">
<span class="tel">
<span class="type">home</span>:
<span class="value">+1.415.555.1212</span>
</span>
</div>

=== Property Exceptions ===

vCard has several properties which either do not make sense on, or are already implied within the context of a web page. This section explains what to (not) do with them.

# '''NAME''', '''PROFILE''', '''SOURCE''', '''PRODID''', '''VERSION''' properties as defined in Sections 2.1.2, 2.1.3, 2.1.4, 3.6.3, 3.6.9 of RFC 2426. Content publishers MUST NOT use these properties in their hCards, and as such, hCard consumers/parsers MUST IGNORE these properties if they are found within an hCard. Instead. hCard to vCard converters SHOULD use the title of the page where the hCard is found (e.g. the <code><title></code> element in (X)HTML documents) to construct the NAME property, MAY output a PROFILE value of "<code>VCARD</code>" per RFC 2426, SHOULD use the URL of the page where the hCard is found to construct the SOURCE property (e.g. perhaps as a parameter to a URL/service that converts hCards to vCards), for an output vCard stream (e.g. a .vcf file). Only services/applications that output actual vCards should write the PRODID property, with the product identifier for said service/application. Similarly only such services/applications should write the VERSION property, with the value "3.0" (without quotes) per RFC2426 Section 3.6.9.

=== Organization Contact Info ===

If the "FN" and "ORG" properties have the exact same value (typically because they are set on the same element, e.g. class="fn org"), then the hCard represents contact information for a company or organization and should be treated as such. In this case the author MUST also NOT set the "N" property, or set it (and any sub-properties) explicitly to the empty string "". Thus parsers should handle the missing "N" property in this case by implying empty values for all the "N" sub-properties.

=== Implied "n" Optimization ===

Although vCard requires that the "N" property be present, the authors of the vCard specification (RFC 2426) themselves do not include "N" properties in their vCards near the end of the spec (p.38). This apparent contradiction can be resolved by simply allowing the "FN" property to imply "N" property values in typical cases provided in the spec. We do so explicitly in hCard.

If "FN" and "ORG" are not the same (see previous section), and the value of the "FN" property is exactly two words (separated by whitespace), and there is no explicit "N" property, then the "N" property is inferred from the "FN" property. For "FN"s with either one word see below, and for three or more, the author MUST explicitly markup the "N", except for the organization contact info case, [http://microformats.org/wiki/hcard#Organization_Contact_Info see above] for that.

# The content of "FN" is broken into two "words" separated by whitespace.
# The ''first'' word of the "FN" is interpreted as the "given-name" for the "N" property.
# The ''second/last'' word of the "FN" is interpreted as the "family-name" for the "N" property.
# Exception: If the first word ends in a "," comma OR if the second word is a single character (optionally followed by a period "."), then the first word (minus the comma at the end if any) 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
* family-name (comma) given-name-first-initial
* family-name (space) given-name-first-initial (optional period)

=== Implied "nickname" Optimization ===

Due to the prevalence of the use of nicknames/handles/usernames on the Web in actual content published on the Web (e.g. authors of [[hReview|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:

# The content of the "FN" is treated as a "nickname" property value.
# Parsers should handle the missing "N" property by implying empty values for all the "N" sub-properties.

Note: 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 can optionally 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.

=== Root Class Name ===
The root class name for an hCard is "vcard".

=== Property List ===
This is the list of properties (and subproperties, in parentheses, like this) in hCard, taken from vCard:

* fn, n (family-name, given-name, additional-name, honorific-prefix, honorific-suffix), nickname, sort-string
* url, email (type, value), tel (type, value)
* adr (post-office-box, extended-address, street-address, locality, region, postal-code, country-name, type, value), label
* geo (latitude, longitude), tz
* photo, logo, sound, bday
* title, role, org (organization-name, organization-unit)
* category, note
* class, key, mailer, uid, rev

=== Property Notes ===
* tel - Authors MAY want to follow the E.123 standard for writing values of telephone numbers.

==== 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:

vCard:
<pre><nowiki>
TEL;TYPE=HOME,PREF:+1.415.555.1212
</nowiki></pre>

hCard:
<pre><nowiki>
<span class="tel"><span class="type">Home</span> (<span class="type">pref</span>erred):
<span class="value">+1.415.555.1212</span>
</span>
</nowiki></pre>

This could be displayed as:

<div style="border: thin dashed black; width: 95%; padding: .5em 1em; ">
<span class="tel"><span class="type">Home</span> (<span class="type">pref</span>erred):
<span class="value">+1.415.555.1212</span>
</span>
</div>

The following lists are ''informative''. See RFC 2426 sections 3.2.1 ADR, 3.3.1 TEL, and 3.3.2 EMAIL respectively for normative type values. They are repeated here for convenience. Default type subproperty value(s) is(are) first in each list and indicated in ALL CAPS. types may be multivalued.

* adr type: INTL, POSTAL, PARCEL, WORK, dom, home, pref
* tel type: VOICE, home, msg, work, pref, fax, cell, video, pager, bbs, modem, [http://flickr.com/photos/tags/carcellphone/ car], isdn, pcs
* email type: INTERNET, x400, pref, "other IANA registered address types"

=== XMDP Profile ===

See [[hcard-profile]] for the [http://gmpg.org/xmdp XMDP] profile of hCard which contains the above complete list of properties, with references to their RFC 2426 definitions.

=== Parsing Details ===

See [[hcard-parsing|hCard parsing]].

== Examples ==

This section is informative.

=== Sample vCard ===

Here is a sample vCard:

<pre><nowiki>
BEGIN:VCARD
VERSION:3.0
N:Çelik;Tantek
FN:Tantek Çelik
URL:http://tantek.com/
ORG:Technorati
END:VCARD
</nowiki></pre>

and an equivalent in hCard with various elements optimized appropriately. See [[hcard-example1-steps| hCard Example 1]] for the derivation.

<pre><nowiki>
<div class="vcard">
<a class="url fn" href="http://tantek.com/">Tantek Çelik</a>
<div class="org">Technorati</div>
</div>
</nowiki></pre>

This hCard might be displayed as:
<div style="border: thin dashed black; width: 95%; padding: .5em 1em;">
[http://tantek.com/ Tantek Çelik]<br />
Technorati
</div>

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 <head> element.

===Live example===

Here are the WikiMedia Foundation's contact details, as a live hCard which will be detected, on this page, by microformat parsing tools:

<div class="vcard">
<div class="fn org">'''Wikimedia Foundation Inc.'''</div>
<div class="adr">
<div class="street-address">'''200 2nd Ave. South #358'''</div>
<div> <span class="locality">'''St. Petersburg'''</span>, <span class="region">'''FL'''</span> <span class="postal-code">'''33701-4313'''</span></div>
<div class="country-name">'''USA'''</div>
</div>
<div>'''Phone:''' <span class="tel">'''+1-727-231-0101'''</span></div>
<div>'''Email:''' <span class="email">'''info@wikimedia.org'''</span></div>
<div><span class="tel"><span class="type">'''Fax'''</span>''':''' <span class="value">'''+1-727-258-0207'''</span></span></div>
</div>

The mark-up (wrapped, and emboldening omitted, for clarity) used is:

<pre><nowiki>
<div class="vcard">
<div class="fn org">Wikimedia Foundation Inc.</div>
<div class="adr">
<div class="street-address">200 2nd Ave. South #358</div>
<div>
<span class="locality">St. Petersburg</span>,
<abbr class="region" title="Florida">FL</abbr> <span class="postal-code">33701-4313</span>
</div>
<div class="country-name">USA</div>
</div>
<div>Phone: <span class="tel">+1-727-231-0101</span></div>
<div>Email: <span class="email">info@wikimedia.org</span></div>
<div>
<span class="tel"><span class="type">Fax</span>:
<span class="value">+1-727-258-0207</span></span>
</div>
</div>
</nowiki></pre>

=== More Examples ===
See [[hcard-examples|hCard examples]] for more examples, including all examples from vCard RFC 2426 converted into hCard.

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

* http://www.crowley.nl/images/hcard.png (mirror: http://www.davidjanes.com/images/mf_hcard.png)
* http://rbach.priv.at/2006/buttons/hcard.png
* http://www.boogdesign.com/images/buttons/microformat_hcard.png
* CSS-powered button, as evidenced at [http://re-run.com/about/microformat-badges microformat badges @ re-run]

== Examples in the wild ==
This section is '''informative'''. The number of hCard examples in the wild has expanded far beyond the capacity of being kept inline in this specification. They have been moved to a [[hcard-examples-in-wild|separate page]].

See [[hcard-examples-in-wild|hCard Examples in the wild]].

== 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 [[hcard-implementations|separate page]].

See [[hcard-implementations|hCard Implementations]].

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426]
* [http://www.itu.int/rec/T-REC-E.123-200102-I/en ITU recommendation E.123] format of telephone numbers (chargeable document)

=== Informative References ===
* Contributed from http://developers.technorati.com/wiki/hCard.
* [http://www.dante.net/np/ds/osi/9594-6-X.520.A4.ps X.520 in Postscript] ([http://72.14.253.104/search?q=cache:FjqzsFu4h20J:www.dante.net/np/ds/osi/9594-6-X.520.A4.ps HTMLization courtesy of Google Cache]) - vCard refers to ROLE as being "based on the X.520 Business Category explanatory attribute".
* [http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426]
* [http://w3.org/TR/REC-CSS1 CSS1]
* [http://tantek.com/log/2004/09.html#hcard hCard term introduced and defined on the Web, 20040930]
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]
* [http://en.wikipedia.org/wiki/E.123 Wikipedia summary of ITU-T Recommendation E.123] - for "TEL" values.
* [http://www.imc.org/pdi/ Internet Mail Consortium Personal Data Interchange vCard and vCalendar]

==== Specifications That Use hCard ====
* [[adr]]
* [[geo]]
* [[hcalendar|hCalendar]]
* [[hreview|hReview]]

==== Similar Work ====
* [http://www.intertwingly.net/wiki/pie/PaceBetterPersonElement Atom PaceBetterPersonElement]
* [http://www.jabber.org/jeps/jep-0054.html JEP-0054: vcard-temp]

== Further Reading ==
* [http://www.digital-web.com/articles/microformats_primer/ Digital Web Magazine: Microformats Primer] by Garrett Dimon has a good intro to hCard
* [http://24ways.org/advent/practical-microformats-with-hcard Practical Microformats with hCard] by Drew McLellan
* [http://www.naturalsearchblog.com/archives/2006/09/28/tips-for-local-search-engine-optimization-for-your-site/ Local Search Engine Optimization using Microformats] by Chris Silver Smith
* [http://thedredge.org/ Andrew D. Hume] has written a blog post on [http://usabletype.com/articles/2005/usable-microformats/ usable microformats] which discusses hCard
* [http://www.thefutureoftheweb.com/blog/2006/1/hcard Jesse Skinner's introduction to hCard]
* [http://blog.usweb.com/ Shaun Shull's] great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], including his [[hcard|hCard]] as an example.
* [http://24ways.org/2006/styling-hcards-with-css 24 Ways: Styling hCards with CSS] A 24 Ways article - John Allsopp on styling hCard using CSS
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page] and the [http://technorati.com/tags/hcard hCard tag]
* [http://www.rfc-editor.org/rfc/rfc4770.txt RFC 4770 - Extensions for Instant Messaging]

== Related Pages ==
{{hcard-related-pages}}