CINXE.COM

<!DOCTYPE html> <html class="client-nojs" lang="en" dir="ltr"> <head> <meta charset="UTF-8"/> <title>hCard 1.0 - Microformats Wiki</title> <script>document.documentElement.className="client-js";RLCONF={"wgBreakFrames":false,"wgSeparatorTransformTable":["",""],"wgDigitTransformTable":["",""],"wgDefaultDateFormat":"dmy","wgMonthNames":["","January","February","March","April","May","June","July","August","September","October","November","December"],"wgRequestId":"5b11d33282d860d129d6cdb9","wgCSPNonce":false,"wgCanonicalNamespace":"","wgCanonicalSpecialPageName":false,"wgNamespaceNumber":0,"wgPageName":"hcard","wgTitle":"hcard","wgCurRevisionId":70233,"wgRevisionId":70233,"wgArticleId":1002,"wgIsArticle":true,"wgIsRedirect":false,"wgAction":"view","wgUserName":null,"wgUserGroups":["*"],"wgCategories":["Pages using deprecated source tags","Specifications","hCard"],"wgPageContentLanguage":"en","wgPageContentModel":"wikitext","wgRelevantPageName":"hcard","wgRelevantArticleId":1002,"wgIsProbablyEditable":false,"wgRelevantPageIsProbablyEditable":false,"wgRestrictionEdit":["sysop"],"wgRestrictionMove":["sysop"]};RLSTATE={"site.styles": "ready","user.styles":"ready","user":"ready","user.options":"loading","ext.pygments":"ready","skins.vector.styles.legacy":"ready"};RLPAGEMODULES=["site","mediawiki.page.ready","mediawiki.toc","skins.vector.legacy.js"];</script> <script>(RLQ=window.RLQ||[]).push(function(){mw.loader.implement("user.options@1i9g4",function($,jQuery,require,module){mw.user.tokens.set({"patrolToken":"+\\","watchToken":"+\\","csrfToken":"+\\"});});});</script> <link rel="stylesheet" href="/wiki/load.php?lang=en&modules=ext.pygments%7Cskins.vector.styles.legacy&only=styles&skin=vector"/> <script async="" src="/wiki/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector"></script> <meta name="generator" content="MediaWiki 1.38.4"/> <meta name="format-detection" content="telephone=no"/> <link rel="shortcut icon" href="/favicon.ico"/> <link rel="search" type="application/opensearchdescription+xml" href="/wiki/opensearch_desc.php" title="Microformats Wiki (en)"/> <link rel="EditURI" type="application/rsd+xml" href="//microformats.org/wiki/api.php?action=rsd"/> <link rel="alternate" type="application/atom+xml" title="Microformats Wiki Atom feed" href="/wiki/index.php?title=Special:RecentChanges&feed=atom"/> </head> <body class="mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-hcard rootpage-hcard skin-vector action-view skin-vector-legacy"><div id="mw-page-base" class="noprint"></div> <div id="mw-head-base" class="noprint"></div> <div id="content" class="mw-body" role="main"> <a id="top"></a> <div id="siteNotice"></div> <div class="mw-indicators"> </div> <h1 id="firstHeading" class="firstHeading mw-first-heading">hCard 1.0</h1> <div id="bodyContent" class="vector-body"> <div id="siteSub" class="noprint">From Microformats Wiki</div> <div id="contentSub"></div> <div id="contentSub2"></div> <div id="jump-to-nav"></div> <a class="mw-jump-link" href="#mw-head">Jump to navigation</a> <a class="mw-jump-link" href="#searchInput">Jump to search</a> <div id="mw-content-text" class="mw-body-content mw-content-ltr" lang="en" dir="ltr"><div class="mw-parser-output"><div style="text-indent:2em;font-weight:bold;padding:1em;background:yellow">See latest version: <a href="/wiki/h-card" title="h-card">h-card</a></div> <a href="/wiki/User:Tantek" title="User:Tantek">Tantek Çelik</a> (Editor, Author), <a href="/wiki/User:Brian" title="User:Brian">Brian Suda</a> (Author) <hr /> <dfn style="font-style:normal;font-weight:bold">hCard</dfn> is a simple, open format for publishing people, companies, organizations on the web, using a 1:1 representation of vCard (<a href="/wiki/rfc-2426" title="rfc-2426">RFC2426</a>) properties and values in HTML. hCard is one of several open <a href="/wiki/microformats" title="microformats">microformat</a> standards suitable for embedding data in HTML/HTML5, and Atom/RSS/XHTML or other XML. Translations: <a href="/wiki/hcard-fr" title="hcard-fr">Français</a> • <a href="/wiki/hcard-ja" title="hcard-ja">日本語</a> • <a href="/wiki/hcard-ru" title="hcard-ru">Русский</a> • <a href="/wiki/hcard-th" title="hcard-th">ภาษาไทย</a> • <a href="/wiki/hcard-zh" title="hcard-zh">漢語</a> • (<a href="/wiki/how-to-start-new-translation" class="mw-redirect" title="how-to-start-new-translation">Add your language</a>) <a href="/wiki/hcard#Copyright" title="hcard">Copyright</a> and <a href="/wiki/hcard#Patents" title="hcard">patents</a> statements apply. See <a href="/wiki/hcard#Inspiration_and_Acknowledgments" title="hcard">acknowledgments</a>. <h2>Example</h2> hCards are most often used to represent people: <div class="mw-highlight mw-highlight-lang-html mw-content-ltr" dir="ltr"><pre><div class="vcard"> <a class="url fn" href="https://tantek.com/">Tantek Çelik</a> </div> </pre></div> and organizations: <div class="mw-highlight mw-highlight-lang-html mw-content-ltr" dir="ltr"><pre><div class="vcard"> <a class="url fn org" href="https://microformats.org/">microformats.org</a> </div> </pre></div> <div style="float:right;background:rgb(248, 247, 236); border:2px solid rgb(225, 229, 186); margin-left:2em" class="box"> <h3>Get started</h3> <img src="https://microformats.org/wiki/skins/Microformats/images/bullet.gif" alt="bullet.gif" /> Create a <a rel="nofollow" class="external text" href="http://microformats.org/code/hcard/creator">new hCard</a> <img src="https://microformats.org/wiki/skins/Microformats/images/bullet.gif" alt="bullet.gif" /> Learn <a href="/wiki/hcard-authoring" title="hcard-authoring">hCard authoring</a> </div> The class <code>vcard</code> is a <a href="/wiki/hcard#Root_Class_Name" title="hcard">root class name</a> that indicates the presence of an hCard. The classes <code>url</code>, <code>fn</code>, and <code>org</code> define properties of the hCard. <h2>Properties</h2> <div style="white-space:nowrap;float:left">Common hCard properties (inside class <code>vcard</code>) <ul><li><code>fn</code> - name, formatted/full. required</li> <li><code>n</code> - structured name, container for: <ul><li><code>honorific-prefix</code> - e.g. Ms., Mr., Dr.</li> <li><code>given-name</code> - given (often first) name</li> <li><code>additional-name</code> - other/middle name</li> <li><code>family-name</code> - family (often last) name</li> <li><code>honorific-suffix</code> - e.g. Ph.D., Esq.</li></ul></li> <li><code>nickname</code> - nickname/alias, e.g. <a href="/wiki/IRC" class="mw-redirect" title="IRC">IRC</a> <abbr title="nickname">nick</abbr></li> <li><code>org</code> - company/organization</li> <li><code>photo</code> - photo, icon, avatar</li> <li><code>url</code> - home page for this contact</li> <li><code>email</code> - email address</li> <li><code>tel</code> - <a href="/wiki/phone_number" class="mw-redirect" title="phone number">telephone number</a></li> <li><code><a href="/wiki/adr" title="adr">adr</a></code> - structured address, container for: <ul><li><code>street-address</code> - street <abbr title="number">#</abbr>+name, <abbr title="apartment">apt</abbr>/<abbr title="suite">ste</abbr></li> <li><code>locality</code> - city or village</li> <li><code>region</code> - state or province</li> <li><code>postal-code</code> - postal code, e.g. <abbr title="United States">U.S.</abbr> ZIP</li> <li><code>country-name</code> - country name</li></ul></li> <li><code>bday</code> - birthday. <a href="/wiki/date-pattern" class="mw-redirect" title="date-pattern">ISO date</a>.</li> <li><code>category</code> - for tagging contacts</li> <li><code>note</code> - notes about the contact</li></ul> </div> <div style="margin-top:-.4em; float:left;">Example hCard of common properties: <ul style="list-style:none"><li><code><div class="vcard"></code> <ul style="list-style:none; margin-top:-.02em"> <li><code>fn">Sally Ride</code></li> <li><code>(n"></code><ul style="list-style:none"> <li><code>honorific-prefix">Dr.</code></li> <li><code>given-name">Sally</code></li> <li><code><abbr class="additional-name">K.</abbr></code></li> <li><code>family-name">Ride</code></li> <li><code>honorific-suffix">Ph.D.),</code></li></ul></li> <li><code>nickname">sallykride (IRC)</code></li> <li><code><div class="org">Sally Ride Science</div></code></li> <li><code><img class="photo" src="http://example.com/sk.jpg"/> </code></li> <li><code><a class="url" href="http://sally.example.com">w</a>,</code></li> <li><code><a class="email" href="mailto:sally@example.com">e</a> </code></li> <li><code><div class="tel">+1.818.555.1212</div></code></li> <li><code><div class="adr"></code><ul style="list-style:none"> <li><code><div class="street-address">123 Main st.</div></code></li> <li><code>locality">Los Angeles, </code></li> <li><code><abbr class="region" title="California">CA</abbr>, </code></li> <li><code>postal-code">91316</code></li> <li><code><div class="country-name">U.S.A</div></div></code></li></ul></li> <li><code><time class="bday">1951-05-26</time> birthday</code></li> <li><code><div class="category">physicist</div></code></li> <li><code><div class="note">1st American woman in space.</div></code></li></ul></li> <li><code></div></code></li></ul> </div> <div style="clear:both; padding:1em 0 0.5em 0">See the <a href="/wiki/hcard#Property_List" title="hcard">full list of properties</a> for the complete list. </div> <div id="toc" class="toc" role="navigation" aria-labelledby="mw-toc-heading"><input type="checkbox" role="button" id="toctogglecheckbox" class="toctogglecheckbox" style="display:none" /><div class="toctitle" lang="en" dir="ltr"><h2 id="mw-toc-heading">Contents</h2><label class="toctogglelabel" for="toctogglecheckbox"></label></div> <ul> <li class="toclevel-1 tocsection-1"><a href="#Example">1 Example</a> <ul> <li class="toclevel-2 tocsection-2"><a href="#Get_started">1.1 Get started</a></li> </ul> </li> <li class="toclevel-1 tocsection-3"><a href="#Properties">2 Properties</a></li> <li class="toclevel-1 tocsection-4"><a href="#Status">3 Status</a> <ul> <li class="toclevel-2 tocsection-5"><a href="#Errata_and_Updates">3.1 Errata and Updates</a></li> </ul> </li> <li class="toclevel-1 tocsection-6"><a href="#Background">4 Background</a></li> <li class="toclevel-1 tocsection-7"><a href="#Conformance">5 Conformance</a></li> <li class="toclevel-1 tocsection-8"><a href="#Format">6 Format</a> <ul> <li class="toclevel-2 tocsection-9"><a href="#In_General">6.1 In General</a></li> <li class="toclevel-2 tocsection-10"><a href="#Root_Class_Name">6.2 Root Class Name</a></li> <li class="toclevel-2 tocsection-11"><a href="#Properties_and_Sub-properties">6.3 Properties and Sub-properties</a></li> <li class="toclevel-2 tocsection-12"><a href="#Property_List">6.4 Property List</a></li> <li class="toclevel-2 tocsection-13"><a href="#Property_Notes">6.5 Property Notes</a></li> <li class="toclevel-2 tocsection-14"><a href="#Singular_vs._Plural_Properties">6.6 Singular vs. Plural Properties</a></li> <li class="toclevel-2 tocsection-15"><a href="#Human_vs._Machine_readable">6.7 Human vs. Machine readable</a></li> <li class="toclevel-2 tocsection-16"><a href="#Value_excerpting">6.8 Value excerpting</a></li> <li class="toclevel-2 tocsection-17"><a href="#Property_Exceptions">6.9 Property Exceptions</a></li> <li class="toclevel-2 tocsection-18"><a href="#Organization_Contact_Info">6.10 Organization Contact Info</a></li> <li class="toclevel-2 tocsection-19"><a href="#Implied_"N"_Optimization">6.11 Implied "N" Optimization</a></li> <li class="toclevel-2 tocsection-20"><a href="#Implied_"nickname"_Optimization">6.12 Implied "nickname" Optimization</a></li> <li class="toclevel-2 tocsection-21"><a href="#Implied_"organization-name"_Optimization">6.13 Implied "organization-name" Optimization</a></li> <li class="toclevel-2 tocsection-22"><a href="#Tags_as_Categories">6.14 Tags as Categories</a></li> <li class="toclevel-2 tocsection-23"><a href="#type_subproperty_values">6.15 type subproperty values</a> <ul> <li class="toclevel-3 tocsection-24"><a href="#type_with_unspecified_value">6.15.1 type with unspecified value</a></li> <li class="toclevel-3 tocsection-25"><a href="#adr_tel_email_types">6.15.2 adr tel email types</a></li> </ul> </li> <li class="toclevel-2 tocsection-26"><a href="#Profile">6.16 Profile</a></li> <li class="toclevel-2 tocsection-27"><a href="#Parsing_Details">6.17 Parsing Details</a></li> </ul> </li> <li class="toclevel-1 tocsection-28"><a href="#Examples">7 Examples</a> <ul> <li class="toclevel-2 tocsection-29"><a href="#Sample_vCard">7.1 Sample vCard</a></li> <li class="toclevel-2 tocsection-30"><a href="#Live_example">7.2 Live example</a></li> <li class="toclevel-2 tocsection-31"><a href="#More_Examples">7.3 More Examples</a></li> </ul> </li> <li class="toclevel-1 tocsection-32"><a href="#Examples_in_the_wild">8 Examples in the wild</a></li> <li class="toclevel-1 tocsection-33"><a href="#Implementations">9 Implementations</a></li> <li class="toclevel-1 tocsection-34"><a href="#Articles">10 Articles</a></li> <li class="toclevel-1 tocsection-35"><a href="#Buttons">11 Buttons</a></li> <li class="toclevel-1 tocsection-36"><a href="#Copyright">12 Copyright</a></li> <li class="toclevel-1 tocsection-37"><a href="#Patents">13 Patents</a></li> <li class="toclevel-1 tocsection-38"><a href="#References">14 References</a> <ul> <li class="toclevel-2 tocsection-39"><a href="#Normative_References">14.1 Normative References</a></li> <li class="toclevel-2 tocsection-40"><a href="#Informative_References">14.2 Informative References</a> <ul> <li class="toclevel-3 tocsection-41"><a href="#Specifications_That_Use_hCard">14.2.1 Specifications That Use hCard</a></li> <li class="toclevel-3 tocsection-42"><a href="#Similar_Work">14.2.2 Similar Work</a></li> </ul> </li> </ul> </li> <li class="toclevel-1 tocsection-43"><a href="#Inspiration_and_Acknowledgments">15 Inspiration and Acknowledgments</a></li> <li class="toclevel-1 tocsection-44"><a href="#Notes_on_derivation_from_vCard">16 Notes on derivation from vCard</a> <ul> <li class="toclevel-2 tocsection-45"><a href="#More_Semantic_Equivalents">16.1 More Semantic Equivalents</a></li> <li class="toclevel-2 tocsection-46"><a href="#Singular_and_Plural_derivations">16.2 Singular and Plural derivations</a> <ul> <li class="toclevel-3 tocsection-47"><a href="#Plural_Properties_Singularized">16.2.1 Plural Properties Singularized</a></li> </ul> </li> </ul> </li> <li class="toclevel-1 tocsection-48"><a href="#Related_Pages">17 Related Pages</a></li> <li class="toclevel-1 tocsection-49"><a href="#Translations">18 Translations</a></li> </ul> </div> <h2>Status</h2> hCard 1.0 is a microformats.org specification. Public discussion on hCard takes place on <a href="/wiki/hcard-feedback" title="hcard-feedback">hcard-feedback</a>, the #microformats <a href="/wiki/irc" title="irc">irc</a> channel on irc.freenode.net, and <a rel="nofollow" class="external text" href="https://microformats.org/discuss/mail/microformats-discuss/">microformats-discuss mailing list</a>. <h3>Errata and Updates</h3> Known errors and issues in this specification are corrected in <a href="/wiki/hcard-issues-resolved" title="hcard-issues-resolved">resolved</a> and <a href="/wiki/hcard-issues-closed" title="hcard-issues-closed">closed</a> issues. Please check there before reporting <a href="/wiki/hcard-issues" title="hcard-issues">issues</a>. The hCard 1.0.1 update is currently under development and incorporates known errata corrections as well as the <a href="/wiki/value-class-pattern" title="value-class-pattern">value-class-pattern</a>. <h2>Background</h2> The vCard standard (<a href="/wiki/rfc-2426" title="rfc-2426">RFC2426</a>), 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 HTML. 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 <a rel="nofollow" class="external text" href="https://microformats.org/code/hcard/creator">hCard creator</a> and copy the HTML code it generates to your blog or website to publish your contact info. <h2>Conformance</h2> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in <a href="/wiki/rfc-2119" title="rfc-2119">RFC 2119</a>. <h2>Format</h2> <h3>In General</h3> The vCard standard (<a href="/wiki/rfc-2426" title="rfc-2426">RFC2426</a>) 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 HTML elements. <h3>Root Class Name</h3> The root class name for an hCard is "vcard". An element with a class name of "vcard" is itself called an hCard. <h3>Properties and Sub-properties</h3> The properties of an hCard are represented by elements inside the hCard. Elements with class names of the listed properties represent the values of those properties. Some properties have sub-properties, and those are represented by elements inside the elements for properties. <h3>Property List</h3> hCard properties (sub-properties in parentheses like this) Required: <ul><li>fn</li> <li>n<a href="#note1">1</a> <ul><li>family-name</li> <li>given-name</li> <li>additional-name</li> <li>honorific-prefix</li> <li>honorific-suffix</li></ul></li></ul> Optional: <ul><li><a href="/wiki/adr" title="adr">adr</a> <ul><li>post-office-box</li> <li>extended-address</li> <li>street-address</li> <li>locality</li> <li>region</li> <li>postal-code</li> <li>country-name</li> <li>type</li> <li>value</li></ul></li> <li>agent</li> <li>bday</li> <li>category</li> <li>class</li> <li>email (type, value)</li> <li>geo <ul><li>latitude</li> <li>longitude</li></ul></li> <li>key</li> <li>label</li> <li>logo</li> <li>mailer</li> <li>nickname</li> <li>note</li> <li>org (organization-name, organization-unit)</li> <li>photo</li> <li>rev</li> <li>role</li> <li>sort-string</li> <li>sound</li> <li>tel<a href="#note2">2</a> (type, value)</li> <li>title</li> <li>tz<a href="#note3">3</a></li> <li>uid</li> <li>url</li></ul> <h3>Property Notes</h3> <a href="#property-list-n">1. ^</a>: The 'n' property is OPTIONAL if any <a href="/wiki/hcard#Implied_.22n.22_Optimization" title="hcard">implied 'n' optimization rules</a> are in effect. <a href="#property-list-tel">2. ^</a>: tel - Authors MAY follow the <a rel="nofollow" class="external text" href="https://en.wikipedia.org/wiki/E.123">E.123</a> standard for writing values of telephone numbers. Letter values (e.g. +1-555-FORMATS) MUST be converted to numbers. Use an <code>abbr</code> to display letters and provide a numerical value simultaneously, e.g. <code><abbr title="+15553676287">+1-555-FORMATS</abbr></code>. <a href="#property-list-tz">3. ^</a>: tz - timezones are indicated with the timezone offset, e.g. <code>PST (-08:00)</code>. <h3>Singular vs. Plural Properties</h3> Singular properties: 'fn', 'n', 'bday', 'tz', 'geo', 'sort-string', 'uid', 'class', 'rev'. For properties which are singular, the first descendant element with that class SHOULD take effect, any others being ignored. All other properties MAY be plural. Each class instance of such properties creates a new instance of that property. <h3>Human vs. Machine readable</h3> The human visible text contents of an element for a property represents the value of that property, with a few exceptions: If an <code><abbr></code> element is used for a property, then the '<code>title</code>' attribute (if present) of the <code><abbr></code> element is the value of the property, instead of the contents of the element, which instead provide a more 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: <ol><li>For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.</li> <li>For other properties, the element's content is the value of the property.</li></ol> If an <code><img></code> element is used for one or more properties, it MUST be treated as follows: <ol><li>For the 'photo' property and any other property that takes a URL as its value, the <code>src="..."</code> attribute provides the property value.</li> <li>For other properties, the <code><img></code> element's '<code>alt</code>' attribute is the value of the property.</li></ol> If an <code><object></code> element is used for one or more properties, it MUST be treated as follows: <ol><li>For the 'photo' property and any other property that takes a URL as its value, the <code>data="..."</code> attribute provides the property value.</li> <li>For other properties, the element's content is the value of the property.</li></ol> <h3>Value excerpting</h3> Sometimes only part of an element which is the equivalent for a property is 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 used 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: vCard: <pre>TEL;TYPE=HOME:+1.415.555.1212 </pre> hCard: <div class="mw-highlight mw-highlight-lang-html mw-content-ltr" dir="ltr"><pre><span class="tel"> <span class="type">home</span>: <span class="value">+1.415.555.1212</span> </span> </pre></div> This hCard fragment could be displayed as: <div style="border: thin dashed black; width: 95%; padding: .5em 1em;"> home: +1.415.555.1212 </div> You may want to customize/localize the visible punctuation and not want to include it in what machines see. Use multiple class="value" elements which are then concatenated. E.g. <div class="mw-highlight mw-highlight-lang-html mw-content-ltr" dir="ltr"><pre><span class="tel"> <span class="type">home</span>: <span class="value">+1</span>.<span class="value">415</span>.<span class="value">555</span>.<span class="value">1212</span></span> </span> </pre></div> No change in display, but the parsed hCard property value then becomes in vCard: vCard: <pre>TEL;TYPE=HOME:+14155551212 </pre> <h3>Property Exceptions</h3> 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. <ol><li>vCard's NAME, PROFILE, SOURCE, PRODID, VERSION properties are defined in Sections 2.1.2, 2.1.3, 2.1.4, 3.6.3, 3.6.9 of <a href="/wiki/rfc-2426" title="rfc-2426">RFC2426</a>. 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 HTML documents) to construct the NAME property, MAY output a PROFILE value of "<code>VCARD</code>" per <a href="/wiki/rfc-2426" title="rfc-2426">RFC2426</a>, 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 <a href="/wiki/rfc-2426" title="rfc-2426">RFC2426</a> Section 3.6.9.</li></ol> <h3>Organization Contact Info</h3> If the "FN" and "ORG" (organization) 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, organization or place and SHOULD be treated as such. In this case the author also MUST 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. <h3>Implied "N" Optimization</h3> Although vCard requires that the "N" property be present, the authors of the vCard specification (<a href="/wiki/rfc-2426" title="rfc-2426">RFC2426</a>) 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, <a href="/wiki/hcard#Organization_Contact_Info" title="hcard">see above</a> for that. <ol><li>The content of "FN" is broken into two "words" separated by whitespace.</li> <li>The first word of the "FN" is interpreted as the "given-name" for the "N" property.</li> <li>The second/last word of the "FN" is interpreted as the "family-name" for the "N" property.</li> <li>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".</li></ol> This allows simplification in the typical case of people stating: <ul><li>given-name (space) family-name</li> <li>family-name (comma) given-name</li></ul> <h3>Implied "nickname" Optimization</h3> Due to the prevalence of the use of nicknames/handles/usernames in actual content published on the Web (e.g. authors of <a href="/wiki/hReview" class="mw-redirect" title="hReview">reviews</a>), 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: <ol><li>The content of the "FN" MUST be treated as a "nickname" property value.</li> <li>Parsers SHOULD handle the missing "N" property by implying empty values for all the "N" sub-properties.</li></ol> Though parsers MUST follow the implied nickname optimization, publishers SHOULD explicitly indicate the "nickname" even in this case, e.g.: <div class="mw-highlight mw-highlight-lang-html mw-content-ltr" dir="ltr"><pre><span class="vcard"> <span class="fn nickname">daveman692</span> </span> </pre></div> The hCard MAY have additional explicit "nickname" property values in addition to the implied nickname. <h3>Implied "organization-name" Optimization</h3> 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". <h3>Tags as Categories</h3> Categories in hCard MAY be represented by tags with <a href="/wiki/rel-tag" title="rel-tag">rel-tag</a>. When a category property is a rel-tag, the tag (as defined by rel-tag) is used for that category. <h3>type subproperty values</h3> 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>TEL;TYPE=HOME,PREF:+1.415.555.1212 </pre> hCard: <div class="mw-highlight mw-highlight-lang-html mw-content-ltr" dir="ltr"><pre><span class="tel"><span class="type">Home</span> (<span class="type">pref</span>erred): <span class="value">+1.415.555.1212</span> </span> </pre></div> This could be displayed as: <div style="border: thin dashed black; width: 95%; padding: .5em 1em;"> Home (preferred): +1.415.555.1212 </div> <h4>type with unspecified value</h4> 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. <div class="mw-highlight mw-highlight-lang-html mw-content-ltr" dir="ltr"><pre><span class="tel"><span class="type">Home</span> +1.415.555.1212</span> </pre></div> is equivalent to: <div class="mw-highlight mw-highlight-lang-html mw-content-ltr" dir="ltr"><pre><span class="tel"><span class="type">Home</span><span class="value"> +1.415.555.1212</span></span> </pre></div> And thus the type is "home" and the value is "+1.415.555.1212". <h4>adr tel email types</h4> The following lists are informative. See <a href="/wiki/rfc-2426" title="rfc-2426">RFC2426</a> 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. <ul><li>adr type: INTL, POSTAL, PARCEL, WORK, dom, home, pref</li> <li>tel type: VOICE, home, msg, work, pref, fax, cell, video, pager, bbs, modem, <a rel="nofollow" class="external text" href="https://flickr.com/photos/tags/carcellphone/">car</a>, isdn, pcs</li> <li>email type: INTERNET, x400, pref</li></ul> <h3>Profile</h3> The hCard XMDP profile is at <a rel="nofollow" class="external free" href="http://microformats.org/profile/hcard">http://microformats.org/profile/hcard</a> Content that uses hCard SHOULD reference this profile, e.g. <div class="mw-highlight mw-highlight-lang-html mw-content-ltr" dir="ltr"><pre><link rel="profile" href="http://microformats.org/profile/hcard"> </pre></div> or <div class="mw-highlight mw-highlight-lang-html mw-content-ltr" dir="ltr"><pre>This content uses <a rel="profile" href="http://microformats.org/profile/hcard">hCard</a>. </pre></div> or <div class="mw-highlight mw-highlight-lang-html mw-content-ltr" dir="ltr"><pre><head profile="http://microformats.org/profile/hcard"> </pre></div> (profile attribute is deprecated in HTML5) Content may combine the above methods as well. <h3>Parsing Details</h3> See <a href="/wiki/hcard-parsing" title="hcard-parsing">hCard parsing</a>. <h2>Examples</h2> This section is informative. <h3>Sample vCard</h3> Here is a sample vCard: <pre>BEGIN:VCARD VERSION:3.0 N:Çelik;Tantek FN:Tantek Çelik URL:https://tantek.com/ END:VCARD </pre> and an equivalent in hCard with various elements optimized appropriately. See <a href="/wiki/hcard-example1-steps" title="hcard-example1-steps"> hCard Example 1</a> for the derivation. <div class="mw-highlight mw-highlight-lang-html mw-content-ltr" dir="ltr"><pre><div class="vcard"> <a class="url fn" href="https://tantek.com/">Tantek Çelik</a> </div> </pre></div> This hCard might be displayed as: <div style="border: thin dashed black; width: 95%; padding: .5em 1em;"> <a rel="nofollow" class="external text" href="https://tantek.com/">Tantek Çelik</a> </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. <h3>Live example</h3> Here is <a rel="nofollow" class="external text" href="http://www.commerce.net/">Commercenet</a>'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">CommerceNet</div> <div class="url">http://www.commerce.net/</div> <div class="adr">Work: <div class="street-address">169 University Avenue</div> Palo Alto, CA  94301 <div class="country-name">USA</div> </div> <div class="tel">Work +1-650-289-4040</div> <div class="tel">Fax +1-650-289-4041</div> <div>Email info@commerce.net</div> </div> The mark-up, emboldening omitted for clarity, with the following semantic improvements: <ul><li><code>abbr</code> to expand abbreviations</li> <li>hyperlinking the org name with the url</li></ul> <div class="mw-highlight mw-highlight-lang-html mw-content-ltr" dir="ltr"><pre><div class="vcard"> <a class="fn org url" href="http://www.commerce.net/">CommerceNet</a> <div class="adr"> <span class="type">Work</span>: <div class="street-address">169 University Avenue</div> <span class="locality">Palo Alto</span>, <abbr class="region" title="California">CA</abbr>&nbsp;&nbsp; <span class="postal-code">94301</span> <div class="country-name">USA</div> </div> <div class="tel"> <span class="type">Work</span> +1-650-289-4040 </div> <div class="tel"> <span class="type">Fax</span> +1-650-289-4041 </div> <div>Email: <span class="email">info@commerce.net</span> </div> </div> </pre></div> <h3>More Examples</h3> See <a href="/wiki/hcard-examples" title="hcard-examples">hCard examples</a> for more examples, including all examples from vCard <a href="/wiki/rfc-2426" title="rfc-2426">RFC2426</a> converted into hCard. <h2>Examples in the wild</h2> 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 <a href="/wiki/hcard-examples-in-wild" title="hcard-examples-in-wild">separate page</a>. See <a href="/wiki/hcard-examples-in-wild" title="hcard-examples-in-wild">hCard Examples in the wild</a>. <h2>Implementations</h2> 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 <a href="/wiki/hcard-implementations" title="hcard-implementations">separate page</a>. See <a href="/wiki/hcard-implementations" title="hcard-implementations">hCard Implementations</a>. <h2>Articles</h2> This section is informative. For further reading on hCard see <a href="/wiki/hcard-articles" title="hcard-articles">hcard-articles</a>. <h2>Buttons</h2> You can use these buttons on pages with hCards. See <a href="/wiki/buttons#hCard" title="buttons">buttons#hCard</a> for any recent additions. <ul><li><img src="http://www.crowley.nl/images/hcard.png" alt="hcard.png" /> (mirror: <img src="http://www.davidjanes.com/images/mf_hcard.png" alt="mf_hcard.png" />)</li> <li><img src="http://rbach.priv.at/2006/buttons/hcard.png" alt="hcard.png" /></li> <li><img src="http://www.boogdesign.com/images/buttons/microformat_hcard.png" alt="microformat_hcard.png" /></li> <li>CSS-powered button, as evidenced at <a rel="nofollow" class="external text" href="http://re-run.com/about/microformat-badges">microformat badges @ re-run</a></li></ul> <h2>Copyright</h2> Per the public domain release on the authors' user pages (<a href="/wiki/User:Tantek" title="User:Tantek">Tantek Çelik</a>, <a href="/wiki/User:Brian" title="User:Brian">Brian Suda</a>) 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 <a rel="nofollow" class="external text" href="http://microformats.org/wiki/Template:public-domain-release">public domain release template</a> to their user page per the <a rel="nofollow" class="external text" href="http://microformats.org/wiki/Category:public_domain_license">Voluntary Public Domain Declarations instructions</a>. Unreleased contributions may be reverted/removed. <h2>Patents</h2> This specification is subject to a royalty free patent policy, e.g. per the <a rel="nofollow" class="external text" href="http://www.w3.org/Consortium/Patent-Policy-20040205/">W3C Patent Policy</a>, and IETF <a rel="nofollow" class="external text" href="http://www.ietf.org/rfc/rfc3667.txt">RFC3667</a> & <a rel="nofollow" class="external text" href="http://www.ietf.org/rfc/rfc3668.txt">RFC3668</a>. <h2>References</h2> <h3>Normative References</h3> <ul><li><a rel="nofollow" class="external text" href="https://www.w3.org/TR/2002/REC-xhtml1-20020801/">XHTML 1.0 SE</a></li> <li><a rel="nofollow" class="external text" href="https://www.ietf.org/rfc/rfc2426.txt">vCard RFC2426</a></li> <li><a rel="nofollow" class="external text" href="http://www.itu.int/rec/T-REC-E.123-200102-I/en">ITU recommendation E.123</a> format of telephone numbers (chargeable document)</li> <li><a href="/wiki/rfc-2119" title="rfc-2119">RFC 2119</a></li></ul> <h3>Informative References</h3> This section is informative. <ul><li><a href="/wiki/hcard-history" title="hcard-history">hCard history</a> <ul><li><a rel="nofollow" class="external text" href="http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats">FOO Camp 2004 Simple Semantic Formats presentation, 2004-09-10</a></li> <li><a rel="nofollow" class="external text" href="https://tantek.com/log/2004/09.html#hcard">hCard term introduced and defined on the Web, 2004-09-30</a></li> <li>Contributed from <a rel="nofollow" class="external free" href="http://developers.technorati.com/wiki/hCard">http://developers.technorati.com/wiki/hCard</a> 2005-06-20</li></ul></li> <li><a rel="nofollow" class="external text" href="http://www.dante.net/np/ds/osi/9594-6-X.520.A4.ps">X.520 in Postscript</a> (<a rel="nofollow" class="external text" href="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</a>) - vCard refers to ROLE as being "based on the X.520 Business Category explanatory attribute".</li> <li><a rel="nofollow" class="external text" href="https://www.w3.org/2002/12/cal/rfc2426">HTML reformatted version of RFC2426</a></li> <li><a rel="nofollow" class="external text" href="https://www.w3.org/TR/REC-CSS1">CSS1</a></li> <li><a rel="nofollow" class="external text" href="https://www.w3.org/TR/xhtml11">XHTML 1.1</a></li> <li><a rel="nofollow" class="external text" href="https://en.wikipedia.org/wiki/E.123">Wikipedia summary of ITU-T Recommendation E.123</a> - for "TEL" values.</li> <li><a rel="nofollow" class="external text" href="http://www.imc.org/pdi/">Internet Mail Consortium Personal Data Interchange vCard and vCalendar</a></li> <li><a href="/wiki/iso-8601" title="iso-8601">ISO8601</a></li></ul> <h4>Specifications That Use hCard</h4> <ul><li><a href="/wiki/adr" title="adr">adr</a></li> <li><a href="/wiki/geo" title="geo">geo</a></li> <li><a href="/wiki/hcalendar" title="hcalendar">hCalendar</a></li> <li><a href="/wiki/hreview" title="hreview">hReview</a></li></ul> <h4>Similar Work</h4> This section is informative. <ul><li><a rel="nofollow" class="external text" href="http://www.intertwingly.net/wiki/pie/PaceBetterPersonElement">Atom PaceBetterPersonElement</a></li> <li><a rel="nofollow" class="external text" href="http://www.jabber.org/jeps/jep-0054.html">JEP-0054: vcard-temp</a></li></ul> <h2>Inspiration and Acknowledgments</h2> This section is informative. Thanks to: my good friend <a rel="nofollow" class="external text" href="http://vadim.com/">Vadim</a> 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. <h2>Notes on derivation from vCard</h2> This section is informative. <div id="Semantic_XHTML_Design_Principles">See: <a href="/wiki/hcard-design-methodology" title="hcard-design-methodology">hcard-design-methodology</a>.</div> <h3>More Semantic Equivalents</h3> For some properties there are HTML elements which better match and convey their semantics. The following properties SHOULD be encoded with the following HTML: <ul><li><code>URL</code> in vCard becomes <code><a class="url" href="...">...</a></code> inside the element with <code>class="vcard"</code> in hCard.</li> <li>Similarly, <code>EMAIL</code> in vCard becomes <code><a class="email" href="mailto:...">...</a></code></li> <li><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></li> <li><code>UID</code> in vCard simply becomes another semantic applied to a specific URL (or EMAIL) for an hCard.</li></ul> <h3>Singular and Plural derivations</h3> The <a href="/wiki/hcard#Singular_vs._Plural_Properties" title="hcard">lists of singular and plural properties</a> have 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 <a href="/wiki/hcard-singular-properties" title="hcard-singular-properties">hcard-singular-properties</a> for explanations. <h4>Plural Properties Singularized</h4> 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. <h2>Related Pages</h2> <ul><li><a class="mw-selflink selflink">hCard</a></li> <li><a href="/wiki/hcard-cheatsheet" title="hcard-cheatsheet">hCard cheatsheet</a> - hCard properties</li> <li><a rel="nofollow" class="external text" href="http://microformats.org/code/hcard/creator">hCard creator</a> (<a href="/wiki/hcard-creator-feedback" class="mw-redirect" title="hcard-creator-feedback">feedback</a>) - create your own hCard.</li> <li><a href="/wiki/hcard-authoring" title="hcard-authoring">hCard authoring</a> - learn how to add hCard markup to your existing contact info.</li> <li><a href="/wiki/hcard-examples" title="hcard-examples">hCard examples</a> - example usage of various classes within hCard.</li> <li><a href="/wiki/hcard-examples-in-wild" title="hcard-examples-in-wild">hCard examples in the wild</a> - an on-going list of websites which use hCards.</li> <li><a href="/wiki/hcard-supporting-user-profiles" title="hcard-supporting-user-profiles">hcard-supporting-user-profiles</a> - sites with user profiles marked up with hCard - a very common example.</li> <li><a href="/wiki/hcard-faq" title="hcard-faq">hCard FAQ</a> - if you have any questions about hCard, check here.</li> <li><a href="/wiki/hcard-implementations" title="hcard-implementations">hCard implementations</a> - websites or tools which either generate or parse hCards.</li> <li><a href="/wiki/hcard-parsing" title="hcard-parsing">hCard parsing</a> - normative details of how to parse hCards.</li> <li><a href="/wiki/hcards-and-pages" title="hcards-and-pages">hCards and pages</a> - semantic distinctions between different hCards on a page, and how to identify each</li> <li><a href="/wiki/hcard-user-interface" title="hcard-user-interface">hcard-user-interface</a> - techniques and issues surrounding user-interfaces to author, publish, and display hCards.</li> <li><a href="/wiki/hcard-profile" title="hcard-profile">hCard profile</a> - the XMDP profile for hCard</li> <li><a href="/wiki/hcard-singular-properties" title="hcard-singular-properties">hCard singular properties</a> - an explanation of the list of singular properties in hCard.</li> <li><a href="/wiki/hcard-tests" title="hcard-tests">hCard tests</a> - a wiki page with actual embedded hCards to try parsing.</li> <li><a href="/wiki/hcard-advocacy" title="hcard-advocacy">hCard advocacy</a> - encourage others to use hCard</li> <li><a href="/wiki/hCard-to-do" class="mw-redirect" title="hCard-to-do">hCard "to do"</a> - jobs to do</li></ul> 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. <ul><li><a href="/wiki/hcard-brainstorming" title="hcard-brainstorming">hCard brainstorming</a> - brainstorms and other explorations relating to hCard. <ul><li><a href="/wiki/hcard-parsing-brainstorming" title="hcard-parsing-brainstorming">hcard-parsing-brainstorming</a> - brainstorming specific to parsing of hCard</li> <li><a href="/wiki/geo-brainstorming" title="geo-brainstorming">geo brainstorming</a></li></ul></li> <li><a href="/wiki/hcard-feedback" title="hcard-feedback">hCard feedback</a> - general feedback (as opposed to specific issues).</li> <li><a href="/wiki/hcard-issues" title="hcard-issues">hCard issues</a> - specific issues with the specification.</li> <li><a href="/wiki/vcard-errata" title="vcard-errata">vCard errata</a> - corrections to the vCard specification, which underlies hCard.</li> <li><a href="/wiki/vcard-suggestions" title="vcard-suggestions">vCard suggestions</a> - suggested improvements to the vCard specification.</li></ul> <h2>Translations</h2> The English version of this specification is the only normative version. Read the hCard specification in additional languages: <ul><li><a href="/wiki/hcard-fr" title="hcard-fr">Français</a></li> <li><a href="/wiki/hcard-ja" title="hcard-ja">日本語</a></li> <li><a href="/wiki/hcard-ru" title="hcard-ru">Русский</a></li> <li><a href="/wiki/hcard-th" title="hcard-th">ภาษาไทย</a></li> <li><a href="/wiki/hcard-zh" title="hcard-zh">漢語</a></li></ul> Help <a href="/wiki/how-to-start-new-translation" class="mw-redirect" title="how-to-start-new-translation">translate hCard into more languages</a>.    </div> <div class="printfooter">Retrieved from "<a dir="ltr" href="http://microformats.org/wiki/index.php?title=hcard&oldid=70233">http://microformats.org/wiki/index.php?title=hcard&oldid=70233</a>"</div></div> <div id="catlinks" class="catlinks" data-mw="interface"><div id="mw-normal-catlinks" class="mw-normal-catlinks"><a href="/wiki/Special:Categories" title="Special:Categories">Categories</a>: <ul><li><a href="/wiki/index.php?title=Category:Pages_using_deprecated_source_tags&action=edit&redlink=1" class="new" title="Category:Pages using deprecated source tags (page does not exist)">Pages using deprecated source tags</a></li><li><a href="/wiki/Category:Specifications" title="Category:Specifications">Specifications</a></li><li><a href="/wiki/Category:hCard" title="Category:hCard">hCard</a></li></ul></div></div> </div> </div> <div id="mw-navigation"> <h2>Navigation menu</h2> <div id="mw-head"> <nav id="p-personal" class="mw-portlet mw-portlet-personal vector-user-menu-legacy vector-menu" aria-labelledby="p-personal-label" role="navigation" > <label id="p-personal-label" aria-label="" class="vector-menu-heading"> Personal tools </label> <div class="vector-menu-content"> <ul class="vector-menu-content-list"><li id="pt-login" class="mw-list-item"><a href="/wiki/index.php?title=Special:UserLogin&returnto=hcard" title="You are encouraged to log in; however, it is not mandatory [o]" accesskey="o">Log in</a></li></ul> </div> </nav> <div id="left-navigation"> <nav id="p-namespaces" class="mw-portlet mw-portlet-namespaces vector-menu vector-menu-tabs" aria-labelledby="p-namespaces-label" role="navigation" > <label id="p-namespaces-label" aria-label="" class="vector-menu-heading"> Namespaces </label> <div class="vector-menu-content"> <ul class="vector-menu-content-list"><li id="ca-nstab-main" class="selected mw-list-item"><a href="/wiki/hcard" title="View the content page [c]" accesskey="c">Page</a></li><li id="ca-talk" class="new mw-list-item"><a href="/wiki/index.php?title=Talk:hcard&action=edit&redlink=1" rel="discussion" title="Discussion about the content page (page does not exist) [t]" accesskey="t">Discussion</a></li></ul> </div> </nav> <nav id="p-variants" class="mw-portlet mw-portlet-variants emptyPortlet vector-menu-dropdown-noicon vector-menu vector-menu-dropdown" aria-labelledby="p-variants-label" role="navigation" > <input type="checkbox" id="p-variants-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-p-variants" class="vector-menu-checkbox" aria-labelledby="p-variants-label" /> <label id="p-variants-label" aria-label="Change language variant" class="vector-menu-heading"> English expanded collapsed </label> <div class="vector-menu-content"> <ul class="vector-menu-content-list"></ul> </div> </nav> </div> <div id="right-navigation"> <nav id="p-views" class="mw-portlet mw-portlet-views vector-menu vector-menu-tabs" aria-labelledby="p-views-label" role="navigation" > <label id="p-views-label" aria-label="" class="vector-menu-heading"> Views </label> <div class="vector-menu-content"> <ul class="vector-menu-content-list"><li id="ca-view" class="selected mw-list-item"><a href="/wiki/hcard">Read</a></li><li id="ca-viewsource" class="mw-list-item"><a href="/wiki/index.php?title=hcard&action=edit" title="This page is protected.
You can view its source [e]" accesskey="e">View source</a></li><li id="ca-history" class="mw-list-item"><a href="/wiki/index.php?title=hcard&action=history" title="Past revisions of this page [h]" accesskey="h">View history</a></li></ul> </div> </nav> <nav id="p-cactions" class="mw-portlet mw-portlet-cactions emptyPortlet vector-menu-dropdown-noicon vector-menu vector-menu-dropdown" aria-labelledby="p-cactions-label" role="navigation" title="More options" > <input type="checkbox" id="p-cactions-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-p-cactions" class="vector-menu-checkbox" aria-labelledby="p-cactions-label" /> <label id="p-cactions-label" aria-label="" class="vector-menu-heading"> More expanded collapsed </label> <div class="vector-menu-content"> <ul class="vector-menu-content-list"></ul> </div> </nav> <div id="p-search" role="search" class="vector-search-box-vue vector-search-box-show-thumbnail vector-search-box-auto-expand-width vector-search-box"> <div> <h3 > <label for="searchInput">Search</label> </h3> <form action="/wiki/index.php" id="searchform" class="vector-search-box-form"> <div id="simpleSearch" class="vector-search-box-inner" data-search-loc="header-navigation"> <input class="vector-search-box-input" type="search" name="search" placeholder="Search Microformats Wiki" aria-label="Search Microformats Wiki" autocapitalize="none" title="Search Microformats Wiki [f]" accesskey="f" id="searchInput" /> <input type="hidden" name="title" value="Special:Search"/> <input id="mw-searchButton" class="searchButton mw-fallbackSearchButton" type="submit" name="fulltext" title="Search the pages for this text" value="Search" /> <input id="searchButton" class="searchButton" type="submit" name="go" title="Go to a page with this exact name if it exists" value="Go" /> </div> </form> </div> </div> </div> </div> <div id="mw-panel"> <div id="p-logo" role="banner"> <a class="mw-wiki-logo" href="/wiki/Main_Page" title="Visit the main page"></a> </div> <nav id="p-Microformats_Wiki" class="mw-portlet mw-portlet-Microformats_Wiki vector-menu vector-menu-portal portal" aria-labelledby="p-Microformats_Wiki-label" role="navigation" > <label id="p-Microformats_Wiki-label" aria-label="" class="vector-menu-heading"> Microformats Wiki </label> <div class="vector-menu-content"> <ul class="vector-menu-content-list"><li id="n-Front-Page" class="mw-list-item"><a href="/wiki/Main_Page">Front Page</a></li><li id="n-recentchanges" class="mw-list-item"><a href="/wiki/Special:RecentChanges" icon="recentChanges" title="A list of recent changes in the wiki [r]" accesskey="r">Recent changes</a></li></ul> </div> </nav> <nav id="p-Microformats" class="mw-portlet mw-portlet-Microformats vector-menu vector-menu-portal portal" aria-labelledby="p-Microformats-label" role="navigation" > <label id="p-Microformats-label" aria-label="" class="vector-menu-heading"> Microformats </label> <div class="vector-menu-content"> <ul class="vector-menu-content-list"><li id="n-Blog" class="mw-list-item"><a href="http://microformats.org" rel="nofollow">Blog</a></li><li id="n-Events" class="mw-list-item"><a href="/wiki/Microformats_Wiki:Current_events">Events</a></li><li id="n-About" class="mw-list-item"><a href="/wiki/About">About</a></li></ul> </div> </nav> <nav id="p-tb" class="mw-portlet mw-portlet-tb vector-menu vector-menu-portal portal" aria-labelledby="p-tb-label" role="navigation" > <label id="p-tb-label" aria-label="" class="vector-menu-heading"> Tools </label> <div class="vector-menu-content"> <ul class="vector-menu-content-list"><li id="t-whatlinkshere" class="mw-list-item"><a href="/wiki/Special:WhatLinksHere/hcard" title="A list of all wiki pages that link here [j]" accesskey="j">What links here</a></li><li id="t-recentchangeslinked" class="mw-list-item"><a href="/wiki/Special:RecentChangesLinked/hcard" rel="nofollow" title="Recent changes in pages linked from this page [k]" accesskey="k">Related changes</a></li><li id="t-specialpages" class="mw-list-item"><a href="/wiki/Special:SpecialPages" title="A list of all special pages [q]" accesskey="q">Special pages</a></li><li id="t-print" class="mw-list-item"><a href="javascript:print();" rel="alternate" title="Printable version of this page [p]" accesskey="p">Printable version</a></li><li id="t-permalink" class="mw-list-item"><a href="/wiki/index.php?title=hcard&oldid=70233" title="Permanent link to this revision of the page">Permanent link</a></li><li id="t-info" class="mw-list-item"><a href="/wiki/index.php?title=hcard&action=info" title="More information about this page">Page information</a></li></ul> </div> </nav> </div> </div> <footer id="footer" class="mw-footer" role="contentinfo" > <ul id="footer-info"> <li id="footer-info-lastmod"> This page was last edited on 24 August 2020, at 23:36.</li> </ul> <ul id="footer-places"> <li id="footer-places-privacy"><a href="/wiki/Microformats_Wiki:Privacy_policy" title="Microformats Wiki:Privacy policy">Privacy policy</a></li> <li id="footer-places-about"><a href="/wiki/Microformats_Wiki:About" title="Microformats Wiki:About">About Microformats Wiki</a></li> <li id="footer-places-disclaimer"><a href="/wiki/Microformats_Wiki:General_disclaimer" title="Microformats Wiki:General disclaimer">Disclaimers</a></li> </ul> <ul id="footer-icons" class="noprint"> <li id="footer-poweredbyico"><a href="https://www.mediawiki.org/"><img src="/wiki/resources/assets/poweredby_mediawiki_88x31.png" alt="Powered by MediaWiki" srcset="/wiki/resources/assets/poweredby_mediawiki_132x47.png 1.5x, /wiki/resources/assets/poweredby_mediawiki_176x62.png 2x" width="88" height="31" loading="lazy"/></a></li> </ul> </footer> <script src="https://www.googletagmanager.com/gtag/js?id=UA-1889385-1" async=""></script><script> window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'UA-1889385-1'); </script> <script>(RLQ=window.RLQ||[]).push(function(){mw.config.set({"wgPageParseReport":{"limitreport":{"cputime":"0.106","walltime":"2.355","ppvisitednodes":{"value":571,"limit":1000000},"postexpandincludesize":{"value":9585,"limit":2097152},"templateargumentsize":{"value":6,"limit":2097152},"expansiondepth":{"value":3,"limit":100},"expensivefunctioncount":{"value":0,"limit":100},"unstrip-depth":{"value":0,"limit":20},"unstrip-size":{"value":14770,"limit":5000000},"timingprofile":["100.00% 2295.540 1 -total"," 0.54% 12.464 1 Template:rfc-2119-intro"," 0.12% 2.711 1 Template:MicroFormatPublicDomainContributionStatement"," 0.05% 1.260 1 Template:recommended"," 0.05% 1.241 1 Template:latest"," 0.05% 1.198 6 Template:may"," 0.05% 1.191 1 Template:hcard-related-pages"," 0.05% 1.169 10 Template:must"," 0.05% 1.164 3 Template:must-not"," 0.05% 1.153 9 Template:should"]},"cachereport":{"timestamp":"20250218010535","ttl":86400,"transientcontent":false}}});mw.config.set({"wgBackendResponseTime":86});});</script> </body> </html>