<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://microformats.org/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Trovster</id>
	<title>Microformats Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://microformats.org/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Trovster"/>
	<link rel="alternate" type="text/html" href="https://microformats.org/wiki/Special:Contributions/Trovster"/>
	<updated>2026-04-06T02:55:10Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.38.4</generator>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hatom&amp;diff=17923</id>
		<title>hatom</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hatom&amp;diff=17923"/>
		<updated>2007-06-15T11:58:49Z</updated>

		<summary type="html">&lt;p&gt;Trovster: /* Examples in the wild */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt; hAtom 0.1 &amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
hAtom is a microformat for content that can be syndicated, primarily but not exclusively weblog postings. hAtom is based on a subset of the [http://www.atomenabled.org/ Atom] syndication format. hAtom is one of several [[microformats]] open standards.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
== Draft Specification ==&lt;br /&gt;
&lt;br /&gt;
=== Editor/Author ===&lt;br /&gt;
* [http://blogmatrix.blogmatrix.com/ David Janes], [http://www.blogmatrix.com BlogMatrix, Inc.]&lt;br /&gt;
&lt;br /&gt;
=== Contributors ===&lt;br /&gt;
* [http://members.optusnet.com.au/benjamincarlyle/benjamin/blog/ Benjamin Carlyle]&lt;br /&gt;
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]&lt;br /&gt;
&lt;br /&gt;
=== Copyright ===&lt;br /&gt;
{{MicroFormatCopyrightStatement2005}}&lt;br /&gt;
&lt;br /&gt;
=== Patents ===&lt;br /&gt;
{{MicroFormatPatentStatement}}&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
hAtom is a [[microformat]] for identifying semantic information in weblog posts and practically any other place [http://www.atomenabled.org/ Atom] may be used, such as news articles. hAtom content is easily added to most blogs by simple modifications to the blog's template definitions.&lt;br /&gt;
&lt;br /&gt;
== Semantic XHTML Design Principles ==&lt;br /&gt;
{{semantic-xhtml-design-principles}}&lt;br /&gt;
&lt;br /&gt;
== Format ==&lt;br /&gt;
=== In General ===&lt;br /&gt;
The [http://atomenabled.org/developers/syndication/#person Atom Syndication Format] provides the conceptual basis for this microformat, with the following caveats:&lt;br /&gt;
&lt;br /&gt;
* Atom provides a lot more functionality than we need for a &amp;quot;blog post&amp;quot; microformat, so we've taken the minimal number of elements needed.&lt;br /&gt;
* the &amp;quot;logical&amp;quot; model of hAtom is that of Atom. If there is a conflict, Atom should be taken as correct.&lt;br /&gt;
* the &amp;quot;physical&amp;quot; model of hAtom -- the actual writing of elements -- is a lot more varied than Atom provides for, due to the variety of ways weblogs are actually produced in the wild. The hAtom microformat provides a number of rules for &amp;quot;bridging the gap&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Schema ===&lt;br /&gt;
Schema elements are based on the Atom nomenclature and follow the microformat pattern of prefixing a unique identifier (in this case, '&amp;lt;code&amp;gt;h&amp;lt;/code&amp;gt;') on the outermost container elements -- the Feed or Entry. The parts of this microformat are based on analysis of many weblog, bulletin board and media posts and can be read [[blog-post-brainstorming#Discovered_Elements]].&lt;br /&gt;
&lt;br /&gt;
The hAtom schema consists of the following:&lt;br /&gt;
&lt;br /&gt;
* hfeed ('''&amp;lt;code&amp;gt;hfeed&amp;lt;/code&amp;gt;'''). optional.&lt;br /&gt;
* hentry ('''&amp;lt;code&amp;gt;hentry&amp;lt;/code&amp;gt;'''). &lt;br /&gt;
** '''&amp;lt;code&amp;gt;entry-title&amp;lt;/code&amp;gt;'''. required. text.&lt;br /&gt;
** '''&amp;lt;code&amp;gt;entry-content&amp;lt;/code&amp;gt;'''. optional (see field description). text.&lt;br /&gt;
** '''&amp;lt;code&amp;gt;entry-summary&amp;lt;/code&amp;gt;'''. optional. text.&lt;br /&gt;
** '''&amp;lt;code&amp;gt;updated&amp;lt;/code&amp;gt;'''. required using [[datetime-design-pattern]].&lt;br /&gt;
** '''&amp;lt;code&amp;gt;published&amp;lt;/code&amp;gt;'''. optional using [[datetime-design-pattern]].&lt;br /&gt;
** '''&amp;lt;code&amp;gt;author&amp;lt;/code&amp;gt;'''. required using '''[[hcard|hCard]]'''.&lt;br /&gt;
** '''&amp;lt;code&amp;gt;bookmark&amp;lt;/code&amp;gt;''' (permalink). optional, using '''[[rel-bookmark]]'''.&lt;br /&gt;
** tags. optional. keywords or phrases, using '''[[rel-tag]]'''.&lt;br /&gt;
&lt;br /&gt;
Some required elements have defaults if missing, see below.&lt;br /&gt;
&lt;br /&gt;
=== Field and Element Details ===&lt;br /&gt;
&lt;br /&gt;
===== Feed =====&lt;br /&gt;
* a Feed element is identified by the class name &amp;lt;code&amp;gt;hfeed&amp;lt;/code&amp;gt;&lt;br /&gt;
* a Feed element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.1.1 Atom feed]&lt;br /&gt;
* the Feed element is optional and, if missing, is assumed to be the page&lt;br /&gt;
* hAtom documents MAY have multiple Feed elements&lt;br /&gt;
&lt;br /&gt;
===== Feed Category =====&lt;br /&gt;
* a Feed Category element is identified by [[rel-tag]]&lt;br /&gt;
* a Feed MAY have a Feed Category&lt;br /&gt;
* a Feed Category element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.2 Atom category] inside a [http://www.atomenabled.org/developers/syndication/#optionalFeedElements feed]&lt;br /&gt;
* Feed Category elements MUST appear inside a Feed element but not inside an Entry element&lt;br /&gt;
* the [[rel-tag]] &amp;lt;code&amp;gt;href&amp;lt;/code&amp;gt; encodes the atom &amp;lt;code&amp;gt;category:term&amp;lt;/code&amp;gt;; the link text defines the atom &amp;lt;code&amp;gt;category:label&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Entry =====&lt;br /&gt;
* an Entry element is identified by class name &amp;lt;code&amp;gt;hentry&amp;lt;/code&amp;gt;&lt;br /&gt;
* an Entry element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.1.2 Atom entry]&lt;br /&gt;
* any microformat content inside a &amp;lt;code&amp;gt;&amp;amp;lt;blockquote&amp;gt;&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;&amp;amp;lt;q&amp;gt;&amp;lt;/code&amp;gt; element within the Entry should not be considered part of the Entry.&lt;br /&gt;
: ''This allows quoting other microformated data without worry of corrupting the model''&lt;br /&gt;
&lt;br /&gt;
===== Entry Category =====&lt;br /&gt;
* an Entry Category element is identified by [[rel-tag]]&lt;br /&gt;
* an Entry MAY have an Entry Category&lt;br /&gt;
* an Entry Category element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.2 Atom category] inside an [http://www.atomenabled.org/developers/syndication/#optionalEntryElements entry]&lt;br /&gt;
* the [[rel-tag]] &amp;lt;code&amp;gt;href&amp;lt;/code&amp;gt; encodes the atom &amp;lt;code&amp;gt;category:term&amp;lt;/code&amp;gt;; the link text defines the atom &amp;lt;code&amp;gt;category:label&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Entry Title =====&lt;br /&gt;
* an Entry Title element is identified by the class name &amp;lt;code&amp;gt;entry-title&amp;lt;/code&amp;gt;&lt;br /&gt;
* an Entry SHOULD have an Entry Title&lt;br /&gt;
* an Entry Title element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.14 Atom entry title]&lt;br /&gt;
* if the Entry Title is missing, use&lt;br /&gt;
** the first &amp;lt;code&amp;gt;&amp;amp;lt;h#&amp;gt;&amp;lt;/code&amp;gt; element in the Entry, or&lt;br /&gt;
** the &amp;lt;code&amp;gt;&amp;amp;lt;title&amp;gt;&amp;lt;/code&amp;gt; of the page, if there is no enclosing Feed element, or&lt;br /&gt;
** assume it is the empty string&lt;br /&gt;
&lt;br /&gt;
===== Entry Content =====&lt;br /&gt;
* an Entry Content element is identified by class name &amp;lt;code&amp;gt;entry-content&amp;lt;/code&amp;gt;&lt;br /&gt;
* an Entry SHOULD have Entry Content&lt;br /&gt;
* an Entry Content element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#atomContent Atom content]&lt;br /&gt;
* an Entry MAY have 0 or more Entry Content elements. The &amp;quot;logical Entry Content&amp;quot; of an Entry is the concatenation, in order of appearance, of all the Entry Contents within the Entry&lt;br /&gt;
: ''Many weblogs split content into multiple sections with a &amp;quot;Read More&amp;quot; link and javascript tricks. This is also needed in cases where Entry Titles are coded inline and are considered part of the content.''&lt;br /&gt;
* if the Entry Content is missing, assume it is the empty string&lt;br /&gt;
&lt;br /&gt;
===== Entry Summary =====&lt;br /&gt;
* an Entry Summary element is identified by class name &amp;lt;code&amp;gt;entry-summary&amp;lt;/code&amp;gt;&lt;br /&gt;
* an Entry Summary element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.13 Atom summary]&lt;br /&gt;
* an Entry MAY have 0 or more Entry Summary elements. The &amp;quot;logical Entry Summary&amp;quot; of an Entry is the concatenation, in order of appearance, of all the Entry Summarys within the Entry&lt;br /&gt;
&lt;br /&gt;
===== Entry Permalink =====&lt;br /&gt;
* an Entry Permalink element is identified by [[rel-bookmark]]&lt;br /&gt;
* an Entry SHOULD have an Entry Permalink&lt;br /&gt;
* an Entry Permalink element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.7 Atom link in an entry]&lt;br /&gt;
* if the Entry Permalink is missing, use the URI of the page; if the Entry has an &amp;quot;id&amp;quot; attribute, add that as a fragment to the page URI to distinguish individual entries&lt;br /&gt;
&lt;br /&gt;
===== Entry Updated =====&lt;br /&gt;
* an Entry Updated element is identified by class name &amp;lt;code&amp;gt;updated&amp;lt;/code&amp;gt;&lt;br /&gt;
* an Entry Updated element represents the concept of [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.15 Atom updated]&lt;br /&gt;
* an Entry SHOULD have an Entry Updated element&lt;br /&gt;
* use the [[datetime-design-pattern]] to encode the updated datetime&lt;br /&gt;
* if there is no Entry Updated element,&lt;br /&gt;
** use the Entry Published element, if present&lt;br /&gt;
** otherwise the page is invalid hAtom&lt;br /&gt;
&lt;br /&gt;
===== Entry Published =====&lt;br /&gt;
* an Entry Published element is identified by the class name &amp;lt;code&amp;gt;published&amp;lt;/code&amp;gt;&lt;br /&gt;
* an Entry Published element represents the concept of [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.9 Atom published]&lt;br /&gt;
* use the [[datetime-design-pattern]] to encode the published datetime&lt;br /&gt;
&lt;br /&gt;
===== Entry Author =====&lt;br /&gt;
* an Entry Author element is represented by class name &amp;lt;code&amp;gt;author&amp;lt;/code&amp;gt;&lt;br /&gt;
* an Entry Author element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.1 Atom author]&lt;br /&gt;
* an Entry Author element MUST be encoded in an [[hcard|hCard]]&lt;br /&gt;
* an Entry Author element SHOULD be encoded in an &amp;lt;code&amp;gt;&amp;amp;lt;address&amp;gt;&amp;lt;/code&amp;gt; element&lt;br /&gt;
* an Entry SHOULD have at least one Entry Author element&lt;br /&gt;
* an Entry MAY have more than one Entry Author elements&lt;br /&gt;
* if the Entry Author is missing&lt;br /&gt;
** find the [[algorithm-nearest-in-parent|Nearest In Parent]] &amp;lt;code&amp;gt;&amp;amp;lt;address&amp;gt;&amp;lt;/code&amp;gt; element(s) with class name &amp;lt;code&amp;gt;author&amp;lt;/code&amp;gt; and that is/are a valid [[hcard|hCard]]&lt;br /&gt;
** otherwise the entry is invalid hAtom&lt;br /&gt;
&lt;br /&gt;
=== XMDP Profile ===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;dl class=&amp;quot;profile&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;dt&amp;gt;class&amp;lt;/dt&amp;gt;&lt;br /&gt;
 &amp;lt;dd&amp;gt;&amp;lt;p&amp;gt;&lt;br /&gt;
  &amp;lt;a rel=&amp;quot;help&amp;quot; href=&amp;quot;http://www.w3.org/TR/html401/struct/global.html#adef-class&amp;quot;&amp;gt;&lt;br /&gt;
   HTML4 definition of the 'class' attribute.&amp;lt;/a&amp;gt;&lt;br /&gt;
  This meta data profile defines some 'class' attribute values (class names) &lt;br /&gt;
  and their meanings as suggested by a &lt;br /&gt;
  &amp;lt;a href=&amp;quot;http://www.w3.org/TR/WD-htmllink-970328#profile&amp;quot;&amp;gt;&lt;br /&gt;
   draft of &amp;quot;Hypertext Links in HTML&amp;quot;&amp;lt;/a&amp;gt;.&lt;br /&gt;
  &amp;lt;dl&amp;gt;&lt;br /&gt;
   &amp;lt;dt&amp;gt;hfeed&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;&lt;br /&gt;
    The concept of atom:feed from &lt;br /&gt;
    &amp;lt;a href=&amp;quot;http://www.atomenabled.org/developers/syndication/atom-format-spec.php&amp;quot;&amp;gt;The Atom Syndication Format&amp;lt;/a&amp;gt;, &lt;br /&gt;
    constrained and modified as per the &amp;lt;a href=&amp;quot;http://microformats.org/wiki/hatom&amp;quot;&amp;gt;hAtom microformat spec&amp;lt;/a&amp;gt;.&lt;br /&gt;
   &amp;lt;/dd&amp;gt;&lt;br /&gt;
   &amp;lt;dt&amp;gt;hentry&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;&lt;br /&gt;
    The concept of atom:entry from &lt;br /&gt;
    &amp;lt;a href=&amp;quot;http://www.atomenabled.org/developers/syndication/atom-format-spec.php&amp;quot;&amp;gt;The Atom Syndication Format&amp;lt;/a&amp;gt;, &lt;br /&gt;
    constrained and modified as per the &amp;lt;a href=&amp;quot;http://microformats.org/wiki/hatom&amp;quot;&amp;gt;hAtom microformat spec&amp;lt;/a&amp;gt;.&lt;br /&gt;
   &amp;lt;/dd&amp;gt;&lt;br /&gt;
   &amp;lt;dt&amp;gt;entry-title&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;&lt;br /&gt;
    The concept of atom:title inside of an atom:entry from &lt;br /&gt;
    &amp;lt;a href=&amp;quot;http://www.atomenabled.org/developers/syndication/atom-format-spec.php&amp;quot;&amp;gt;The Atom Syndication Format&amp;lt;/a&amp;gt;, &lt;br /&gt;
    constrained and modified as per the &amp;lt;a href=&amp;quot;http://microformats.org/wiki/hatom&amp;quot;&amp;gt;hAtom microformat spec&amp;lt;/a&amp;gt;.&lt;br /&gt;
   &amp;lt;/dd&amp;gt;&lt;br /&gt;
   &amp;lt;dt&amp;gt;entry-content&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;&lt;br /&gt;
    The concept of atom:content from &lt;br /&gt;
    &amp;lt;a href=&amp;quot;http://www.atomenabled.org/developers/syndication/atom-format-spec.php&amp;quot;&amp;gt;The Atom Syndication Format&amp;lt;/a&amp;gt;, &lt;br /&gt;
    constrained and modified as per the &amp;lt;a href=&amp;quot;http://microformats.org/wiki/hatom&amp;quot;&amp;gt;hAtom microformat spec&amp;lt;/a&amp;gt;.&lt;br /&gt;
   &amp;lt;/dd&amp;gt;&lt;br /&gt;
   &amp;lt;dt&amp;gt;entry-summary&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;&lt;br /&gt;
    The concept of atom:summary from &lt;br /&gt;
    &amp;lt;a href=&amp;quot;http://www.atomenabled.org/developers/syndication/atom-format-spec.php&amp;quot;&amp;gt;The Atom Syndication Format&amp;lt;/a&amp;gt;, &lt;br /&gt;
    constrained and modified as per the &amp;lt;a href=&amp;quot;http://microformats.org/wiki/hatom&amp;quot;&amp;gt;hAtom microformat spec&amp;lt;/a&amp;gt;.&lt;br /&gt;
   &amp;lt;/dd&amp;gt;&lt;br /&gt;
   &amp;lt;dt&amp;gt;bookmark&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;&lt;br /&gt;
    The concept of atom:link (without any &amp;quot;rel&amp;quot;) with an atom:entry from &lt;br /&gt;
    &amp;lt;a href=&amp;quot;http://www.atomenabled.org/developers/syndication/atom-format-spec.php&amp;quot;&amp;gt;The Atom Syndication Format&amp;lt;/a&amp;gt;, &lt;br /&gt;
    constrained and modified as per the &amp;lt;a href=&amp;quot;http://microformats.org/wiki/hatom&amp;quot;&amp;gt;hAtom microformat spec&amp;lt;/a&amp;gt;.&lt;br /&gt;
   &amp;lt;/dd&amp;gt;&lt;br /&gt;
   &amp;lt;dt&amp;gt;published&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;&lt;br /&gt;
    The concept of atom:published from &lt;br /&gt;
    &amp;lt;a href=&amp;quot;http://www.atomenabled.org/developers/syndication/atom-format-spec.php&amp;quot;&amp;gt;The Atom Syndication Format&amp;lt;/a&amp;gt;, &lt;br /&gt;
    constrained and modified as per the &amp;lt;a href=&amp;quot;http://microformats.org/wiki/hatom&amp;quot;&amp;gt;hAtom microformat spec&amp;lt;/a&amp;gt;.&lt;br /&gt;
   &amp;lt;/dd&amp;gt;&lt;br /&gt;
   &amp;lt;dt&amp;gt;updated&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;&lt;br /&gt;
    The concept of atom:updated from &lt;br /&gt;
    &amp;lt;a href=&amp;quot;http://www.atomenabled.org/developers/syndication/atom-format-spec.php&amp;quot;&amp;gt;The Atom Syndication Format&amp;lt;/a&amp;gt;, &lt;br /&gt;
    constrained and modified as per the &amp;lt;a href=&amp;quot;http://microformats.org/wiki/hatom&amp;quot;&amp;gt;hAtom microformat spec&amp;lt;/a&amp;gt;.&lt;br /&gt;
   &amp;lt;/dd&amp;gt;&lt;br /&gt;
   &amp;lt;dt&amp;gt;author&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;&lt;br /&gt;
    The concept of atom:author from &lt;br /&gt;
    &amp;lt;a href=&amp;quot;http://www.atomenabled.org/developers/syndication/atom-format-spec.php&amp;quot;&amp;gt;The Atom Syndication Format&amp;lt;/a&amp;gt;, &lt;br /&gt;
    constrained and modified as per the &amp;lt;a href=&amp;quot;http://microformats.org/wiki/hatom&amp;quot;&amp;gt;hAtom microformat spec&amp;lt;/a&amp;gt;.&lt;br /&gt;
   &amp;lt;/dd&amp;gt;&lt;br /&gt;
  &amp;lt;/dl&amp;gt;&lt;br /&gt;
 &amp;lt;/dd&amp;gt;&lt;br /&gt;
&amp;lt;/dl&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
&lt;br /&gt;
See [[hatom-examples]].&lt;br /&gt;
&lt;br /&gt;
== Examples in the wild ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
The following sites have implemented hAtom , and thus are a great place to start for anyone looking for examples &amp;quot;in the wild&amp;quot; to try parsing, indexing, organizing etc. If your site marked up with hAtom, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.&lt;br /&gt;
&lt;br /&gt;
=== 0.1 hAtom examples===&lt;br /&gt;
* [http://www.creation.uk.com Creation design &amp;amp; marketing] uses hAtom for a lot of the content as well as [http://www.creation.uk.com/news/2007/06/06/easy-money/ comments on articles].&lt;br /&gt;
* [http://www.sndbx.org/ The Sandbox Designs Competition] uses hAtom for all content, hCard for participant (the competition designers) and sponsor information, hCalendar for the competition schedule, XFN for links, and rel-license for licensing information. It's all GNU GPL.&lt;br /&gt;
* [http://guyleech.net guyleech.net] uses hAtom for blog posts, and uses hCard for contact information. There is also an [http://guyleech.net/2007/7 article] on how to minimise hAtom, to save time and code.&lt;br /&gt;
* [http://kpumuk.info/ Dmytro Shteflyuk] uses hAtom for all blog posts.&lt;br /&gt;
* [http://blog.no-panic.at Florian Beer] uses hAtom to mark up all the blog posts. There is also a [http://blog.no-panic.at/2006/11/16/hatom-and-wordpress/ tutorial] on how to convert Wordpress themes to include hAtom.&lt;br /&gt;
* [http://ficlets.com/ Ficlets] uses hAtom on the [http://ficlets.com/stories main stories page] and on [http://ficlets.com/stories/12 individual story pages].&lt;br /&gt;
* [http://www.international.unt.edu UNT International] uses hAtom combined with hCard on news/announcement pages (e.g., [http://www.international.unt.edu/quick/news the main news page]) in addition to providing traditional Atom feeds&lt;br /&gt;
* [http://www.absalom.net.au Absalom Media] uses hAtom combined with hCard for articles.&lt;br /&gt;
* [http://www.joomlamug.com Joomla! Melbourne User Group] uses hAtom combined with hCard for articles.&lt;br /&gt;
* [http://www.volume.co.uk Volume] - Main news page is marked up as hAtom 0.1 &lt;br /&gt;
* [http://yedda.com Yedda] - Yedda support hAtom on exploration of questions where there is also support for Atom and RSS feeds. ([http://yedda.com/questions/recent/ example])&lt;br /&gt;
* The [http://www.westmidlandbirdclub.com/ West Midland Bird Club's] frequently-updated [http://www.westmidlandbirdclub.com/new.htm What's New] page,  [http://www.westmidlandbirdclub.com/ladywalk/latest.htm news from its Ladywalk Reserve] and [http://www.westmidlandbirdclub.com/worcs/grimley/latest.htm news from Grimley Pits] &amp;amp;mdash;  comments welcome on my talk page [[User:AndyMabbett|Andy Mabbett]]&lt;br /&gt;
* [http://pixelsebi.com pixelsebi's repository] uses hAtom 0.1 for blog posts (and hCard, hCalendar, XFN, xFolk and many more) based on manual WordPress template modifications&lt;br /&gt;
* [http://www.geekinthepark.co.uk Geek in the Park] uses hAtom for the comments. -- by [[User:Trovster|trovster]]&lt;br /&gt;
* [http://www.csarven.ca Sarven Capadisli] uses hAtom for the articles and comments -- by [[User:Csarven|csarven]]&lt;br /&gt;
* [http://www.fberriman.com fberriman.com] uses hAtom 0.1 for blog posts (WordPress loop) and hCard throughout -- by [[User:Phae|Frances Berriman]] (Also - [http://www.fberriman.com/?p=86 Implementing hAtom: The Entries Code])&lt;br /&gt;
* [http://www.capital.edu Capital University] uses hAtom 0.1 to mark up the feed of latest posts by student bloggers on its home page.&lt;br /&gt;
* [http://blog.davidjanes.com Ranting and Roaring] (David Janes)&lt;br /&gt;
* [http://ChunkySoup.net/ ChunkySoup.net] has redesigned using hAtom 0.1 and hCards on the entire site -- by [[User:ChrisCasciano|Chris Casciano]]&lt;br /&gt;
* [http://sedna.spip.org/sedna/ Sedna RSS] (a feed aggregator based on SPIP, by Fil, IZO and others; GPLd sources are available at [http://zone.spip.org/trac/spip-zone/browser/_squelettes_/sedna SPIP-Zone])&lt;br /&gt;
* [http://members.optusnet.com.au/benjamincarlyle/benjamin/blog/ Sound Advice] (Benjamin Carlyle)&lt;br /&gt;
* [http://quotedprintable.com/pages/scribbish Scribbish] is a Typo theme which uses hAtom.&lt;br /&gt;
* [http://rbach.priv.at/hAtom2Atom/Changelog/ hAtom2Atom.xsl's Changelog] is published as hAtom and Atom.&lt;br /&gt;
* [http://federali.st/ federali.st]'s webbed Federalist Papers are each marked up in hAtom.&lt;br /&gt;
* [http://www.plaintxt.org/themes/sandbox/ Sandbox] is a theme for [http://wordpress.org/ WordPress] that uses hAtom. &lt;br /&gt;
** The theme is also available to accounts on the [http://wordpress.com/ &amp;lt;username&amp;gt;.wordpress.com] hosting service. The [http://blog.coworking.info Coworking] and [http://barcamp.wordpress.com BarCamp] blogs are examples of custom Sandbox themes.&lt;br /&gt;
* [http://www.whump.com/dropbox/Strangelove.zip Strangelove] is a modification of the default WordPress theme (Kubrick) with hAtom support. &lt;br /&gt;
** It points to the hAtom2Atom proxy service as the link for syndication feeds.&lt;br /&gt;
* All [http://www.plaintxt.org/themes/ plaintxt.org themes] for [http://wordpress.org/ WordPress] now use hAtom. The themes are also coded for hCard compliance. The themes, by name, are:&lt;br /&gt;
** [http://www.plaintxt.org/themes/barthelme/ Barthelme] (two-column, fluid), [http://www.plaintxt.org/themes/blogtxt/ blog.txt] (two- or three-column, elastic), [http://www.plaintxt.org/themes/plaintxtblog/ plaintxtBlog] (three-column, fluid), [http://www.plaintxt.org/themes/simplr/ Simplr] (one column, elastic), [http://www.plaintxt.org/themes/veryplaintxt/ veryplaintxt] (two column, fluid)&lt;br /&gt;
* [http://archgfx.net/blog/index.php/themes/disconnected/ Disconnected], a theme for WordPress, also incorporated hAtom with version 1.2&lt;br /&gt;
* [http://www.pats.ua.ac.be/courses PATS Courses], the PATS Research Group uses hAtom to mark up the latest course documents for some of their courses&lt;br /&gt;
* [http://mix.excite.co.uk Excite MIX], the Ajax Start Page from Excite Europe, uses hAtom 0.1 and hCard in the Feed Viewer to mark up feed entries and authors.&lt;br /&gt;
* [http://last.fm Last.FM], a social music sharing platform, uses hAtom markup for [http://blog.last.fm/2007/05/30/rss-your-shoutbox-and-you shoutbox], and recommends using [http://tools.microformatic.com microformatic]'s transcode tool&lt;br /&gt;
&lt;br /&gt;
===Examples with some problems===&lt;br /&gt;
&lt;br /&gt;
Entries may be moved here if there's a problem with the way hAtom is used on the page concerned. If the page is yours, and you want to improve it, see the [[hatom-faq|hAtom FAQ]], or raise any queries on [[hatom-issues|hAtom Issues]] or [[mailing-lists#microformats-discuss|the mailing list]], where people will be happy to help you. &lt;br /&gt;
&lt;br /&gt;
==== Pre 0.1 hAtom examples====&lt;br /&gt;
These pages conform to an older draft standard and need to be updated.&lt;br /&gt;
&lt;br /&gt;
* [http://www.myelin.co.nz/post/ Second p0st] (Phil Pearson)&lt;br /&gt;
&lt;br /&gt;
== Implementations ==&lt;br /&gt;
&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
The following implementations have been developed which either generate or parse hAtom links. If you have an hAtom implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.&lt;br /&gt;
&lt;br /&gt;
* [http://dichotomize.com/uf/hatom/creator.html hAtom Creator] modified from the other creators by BenWest.&lt;br /&gt;
* the [http://tools.blogmatrix.com/extract/ Almost Universal Microformat Parser] can extract hAtom content from webpages ([http://tools.blogmatrix.com/extract/?uri=http%3A%2F%2Fblog.davidjanes.com&amp;amp;microformat=hatom&amp;amp;submit=Submit example])&lt;br /&gt;
* the [http://www.trinityanne.com/tools/greasemonkey/microformat-action.user.js microformat-action] [[greasemonkey|Greasemonkey]] script detects hAtom content on webpages and will call the [http://tools.blogmatrix.com/extract/ Almost Universal Microformat Parser]&lt;br /&gt;
* [http://rbach.priv.at/hAtom2Atom/ hAtom2Atom.xsl] transforms hAtom to Atom (as the name suggests.)&lt;br /&gt;
* There is now an [http://www.lukearno.com/projects/hatom2atom/ hatom2atom proxy] that uses hAtom2Atom.xsl.&lt;br /&gt;
* [http://placenamehere.com/article/185/SubscribingTohAtomFeedsWithNetNewsWire Subscribe To hAtom] is a script that provides [http://ranchero.com/netnewswire/ NetNewsWire 2.x] users with the ability to subscribe to hAtom documents as they would any other feed. by [[User:ChrisCasciano|Chris Casciano]].&lt;br /&gt;
* [http://boxtheweb.mihopa.net/code/apis/#outlineclasses Outline Classes] - has GPL'ed PHP code for reading hAtom&lt;br /&gt;
* [http://boxtheweb.4x2.net/ BoxtheWeb] - supports subscribing to hAtom as a feed format&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
=== Normative References ===&lt;br /&gt;
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]&lt;br /&gt;
* [http://www.ietf.org/rfc/rfc4287 RFC4287: The Atom Syndication Format]&lt;br /&gt;
* [[hcard-parsing]]&lt;br /&gt;
&lt;br /&gt;
=== Informative References ===&lt;br /&gt;
* [http://www.atomenabled.org/ atomenabled.org]&lt;br /&gt;
&lt;br /&gt;
== Work in progress ==&lt;br /&gt;
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. There is a separate document where we are keeping our brainstorms and other explorations relating to hAtom:&lt;br /&gt;
&lt;br /&gt;
* [[blog-post-brainstorming|blog-post Brainstorming]]&lt;br /&gt;
&lt;br /&gt;
=== Version 0.1 ===&lt;br /&gt;
&lt;br /&gt;
Version 0.1 was released 28 February 2006.&lt;br /&gt;
&lt;br /&gt;
== Discussions ==&lt;br /&gt;
&lt;br /&gt;
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].&lt;br /&gt;
&lt;br /&gt;
=== Q&amp;amp;A ===&lt;br /&gt;
* If you have any questions about hAtom, check the [[hatom-faq|hAtom FAQ]], and if you don't find answers, add your questions!&lt;br /&gt;
&lt;br /&gt;
=== Issues ===&lt;br /&gt;
* Please add any issues with the specification to the separate [[hatom-issues|hAtom issues]] document.&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
{{hatom-related-pages}}&lt;br /&gt;
* [[rel-enclosure]] - how to semantically reference enclosures (e.g. podcasts) in hAtom&lt;br /&gt;
* [[blog-post-brainstorming]]&lt;br /&gt;
* [[blog-post-formats]]&lt;br /&gt;
* [[blog-post-examples]]&lt;br /&gt;
* [[blog-description-format]] - how to describe a blog (as opposed to the individual entries, which is what we're doing here)&lt;/div&gt;</summary>
		<author><name>Trovster</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=geo&amp;diff=17875</id>
		<title>geo</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=geo&amp;diff=17875"/>
		<updated>2007-06-15T11:56:44Z</updated>

		<summary type="html">&lt;p&gt;Trovster: /* Examples in the wild */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt; geo &amp;lt;/h1&amp;gt;&lt;br /&gt;
*http://rbach.priv.at/2006/buttons/geo.png&lt;br /&gt;
'''geo''' (pronounced &amp;quot;gee-oh&amp;quot;) is a simple format for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates (latitude; longitude), suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. '''geo''' is a 1:1 representation of the &amp;quot;geo&amp;quot; property in the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in XHTML, one of several open [[microformats|microformat]] standards.&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Draft Specification ==&lt;br /&gt;
&lt;br /&gt;
=== Editor/Author ===&lt;br /&gt;
[http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]&lt;br /&gt;
&lt;br /&gt;
=== Copyright ===&lt;br /&gt;
{{MicroFormatCopyrightStatement2005}}&lt;br /&gt;
&lt;br /&gt;
=== Patents ===&lt;br /&gt;
{{MicroFormatPatentStatement}}&lt;br /&gt;
&lt;br /&gt;
=== Inspiration and Acknowledgments ===&lt;br /&gt;
Thanks to everyone who participated in the [[geo-bof-2005-06-30|Geo Microformat BOF at O'Reilly's Where 2.0 conference]], and in particular to [http://radar.oreilly.com/nat/ Nat Torkington] and Vee McMillen of [http://oreilly.com O'Reilly] for [http://conferences.oreillynet.com/cs/where2005/view/e_sess/7476 arranging and hosting the BOF].  Thanks to Chris Hibbbert for providing the [http://www.geocaching.com/seek/cache_details.aspx?guid=dc4754bf-64d5-4f28-8715-45ad2505c86f real world geo-caching example].&lt;br /&gt;
&lt;br /&gt;
== Introduction and Background ==&lt;br /&gt;
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), has been broadly and interoperably implemented (e.g. Apple's Address Book application). The [[hcard|hCard]] microformat has similarly received significant adoption, from numerous sites publishing the format, to hCard to vCard proxies, to clientside javascript parsers.&lt;br /&gt;
&lt;br /&gt;
At the [http://conferences.oreillynet.com/where/ Where 2.0 conference] in June 2005, there was widespread recognition that the community needed a way to simply and easily publish visible, extractable, geographic location information on the Web, given how often bloggers, and numerous other sites publish such information.  The [[geo-bof-2005-06-30|geo microformat BOF]] discussed this very topic, and concluded with a consensus decision to just try using ''geo'' from vCard/hCard.&lt;br /&gt;
&lt;br /&gt;
This specification introduces the '''geo''' microformat, which is a 1:1 representation of the aforementioned ''geo'' property from the vCard standard, by simply reusing the ''geo'' property and sub-properties as-is from the [[hcard|hCard]] microformat.&lt;br /&gt;
&lt;br /&gt;
Publishers can both embed '''geo''' addresses directly in their web pages and feeds, as well as markup existing latitude/longitude coordinates in the context of the rest of the information in their web pages and feeds.&lt;br /&gt;
&lt;br /&gt;
If the publisher knows and is publishing the ''name'' of the location in addition to its geo lat/long, then the publisher MUST use [[hcard|hCard]] instead of just '''geo''' to publish the name and geo lat/long of the location.&lt;br /&gt;
&lt;br /&gt;
If the publisher knows and is publishing the address of the location, OR if the address of the location was what was actually entered by a human, and the publisher simply turned that into lat/long using some sort of a service, then the publisher SHOULD use [[adr]] to publish the actual human entered address information since that communicates far more semantic information than a simple geo lat/long coordinate.&lt;br /&gt;
&lt;br /&gt;
== Semantic XHTML Design Principles ==&lt;br /&gt;
{{semantic-xhtml-design-principles}}&lt;br /&gt;
&lt;br /&gt;
== Format ==&lt;br /&gt;
=== Singular Properties ===&lt;br /&gt;
&lt;br /&gt;
Note that all the properties in '''geo''' are singular properties, and thus the first descendant element with that class should take effect, any others being ignored.&lt;br /&gt;
&lt;br /&gt;
=== Human vs. Machine readable ===&lt;br /&gt;
&lt;br /&gt;
If an &amp;lt;code&amp;gt;&amp;amp;lt;abbr&amp;amp;gt;&amp;lt;/code&amp;gt; element is used for a property, then the &amp;lt;code&amp;gt;title&amp;lt;/code&amp;gt; attribute of the &amp;lt;code&amp;gt;&amp;amp;lt;abbr&amp;amp;gt;&amp;lt;/code&amp;gt; element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value.&lt;br /&gt;
&lt;br /&gt;
=== Value excerpting ===&lt;br /&gt;
&lt;br /&gt;
Sometimes only part of an element which is the equivalent for a property should be used for the value of the property. For this purpose, the special class name &amp;lt;code&amp;gt;value&amp;lt;/code&amp;gt; is used to excerpt out the subset of the element that is  the value of the property.  See [[hcard|hCard]] for details on this.&lt;br /&gt;
&lt;br /&gt;
=== Root Class Name ===&lt;br /&gt;
&lt;br /&gt;
The root class name for an geo location is &amp;lt;code&amp;gt;geo&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=== Property List ===&lt;br /&gt;
&lt;br /&gt;
This is the list of properties in geo, taken from [[hcard|hCard]]:&lt;br /&gt;
&lt;br /&gt;
* latitude&lt;br /&gt;
* longitude&lt;br /&gt;
&lt;br /&gt;
=== XMDP Profile ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Parsing Details ===&lt;br /&gt;
&lt;br /&gt;
See [[hcard-parsing|hCard parsing]], with the only difference being that &amp;quot;geo&amp;quot; is the root class name, rather than &amp;quot;vcard&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
&lt;br /&gt;
This section is informative.&lt;br /&gt;
&lt;br /&gt;
=== Example from RFC2426 ===&lt;br /&gt;
&lt;br /&gt;
Section 3.4.2 of RFC2426 has a simple geo example:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
GEO:37.386013;-122.082932&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
this vCard fragment as a geo, as [http://microformats.org/wiki/hcard-examples#3.4.2_GEO_Type_Definition first documented on the hCard examples page]:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;geo&amp;quot;&amp;gt;GEO: &lt;br /&gt;
 &amp;lt;span class=&amp;quot;latitude&amp;quot;&amp;gt;37.386013&amp;lt;/span&amp;gt;, &lt;br /&gt;
 &amp;lt;span class=&amp;quot;longitude&amp;quot;&amp;gt;-122.082932&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
this geo could be displayed as: &amp;lt;!-- this section includes a live Geo microforamt - please edit with care --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;geo&amp;quot;&amp;gt;GEO: &amp;lt;span class=&amp;quot;latitude&amp;quot;&amp;gt;37.386013&amp;lt;/span&amp;gt;, &amp;lt;span class=&amp;quot;longitude&amp;quot;&amp;gt;-122.082932&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note that this is a '''live''' geo microformat, which will be found on this page by parsers.&lt;br /&gt;
&lt;br /&gt;
=== Real world geo example ===&lt;br /&gt;
&lt;br /&gt;
Here is a sample of published lat/long info (from [http://www.geocaching.com/seek/cache_details.aspx?guid=dc4754bf-64d5-4f28-8715-45ad2505c86f geocaching: Noble Steed]):&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
N 37° 24.491 W 122° 08.313&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With geo markup:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;geo&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;abbr class=&amp;quot;latitude&amp;quot; title=&amp;quot;37.408183&amp;quot;&amp;gt;N 37° 24.491&amp;lt;/abbr&amp;gt; &lt;br /&gt;
 &amp;lt;abbr class=&amp;quot;longitude&amp;quot; title=&amp;quot;-122.13855&amp;quot;&amp;gt;W 122° 08.313&amp;lt;/abbr&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This geo might be displayed as: &amp;lt;!-- this section includes a live Geo microforamt - please edit with care --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;geo&amp;quot;&amp;gt;&amp;lt;abbr class=&amp;quot;latitude&amp;quot; title=&amp;quot;37.408183&amp;quot;&amp;gt;N 37° 24.491&amp;lt;/abbr&amp;gt; &amp;lt;abbr class=&amp;quot;longitude&amp;quot; title=&amp;quot;-122.13855&amp;quot;&amp;gt;W 122° 08.313&amp;lt;/abbr&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Again, this is a '''live''' example.&lt;br /&gt;
&lt;br /&gt;
Note that since the real world example used a more human readable presentation of the geo coordinates, we use the [[abbr-design-pattern]] to keep that more human readable presentation, and in addition provide the respective absolute numerical values for the geo.&lt;br /&gt;
&lt;br /&gt;
== Examples in the wild ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
The following sites have published geos, outside their normal context of hCards, and thus are a great place to start for anyone looking for examples &amp;quot;in the wild&amp;quot; to try parsing, indexing, organizing etc., in addition to those in many [[hcard-examples-in-wild|hCard examples in the wild]]. If you find geos outside of hCards anywhere else, feel free to add them to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page.&lt;br /&gt;
&lt;br /&gt;
Pages with live Geo can use this button (see [[buttons#Geo]] for any recent additions): http://rbach.priv.at/2006/buttons/geo.png&lt;br /&gt;
&lt;br /&gt;
* [http://www.creation.uk.com Creation design &amp;amp; marketing] has Geo microformat on the [http://www.creation.uk.com/contact/ contact information].&lt;br /&gt;
* Wikipedia now has a template, [http://en.wikipedia.org/wiki/Template:Hcard-geo hcard-geo], for in-line hCards with coordinates, using Geo, such as that on [http://en.wikipedia.org/wiki/Engine_Arm Engine Arm]&lt;br /&gt;
*[http://www.davidosbornephotography.co.uk/gallery2/main.php www.davidosbornephotography.co.uk] has implemented Geo on all location photography pages; eg. [http://www.davidosbornephotography.co.uk/gallery2/main.php?g2_itemId=1747 Callanish Stones]&lt;br /&gt;
*[http://en.wikipedia.org/wiki/Category:Templates_generating_Geo Wikipedia-EN templates_generating_Geo]&lt;br /&gt;
*Wikipedia-IT now has Geo on all  [http://it.wikipedia.org/wiki/Speciale:PuntanoQui/Template:Coord pages using the ''coord'' template], e.g. [http://it.wikipedia.org/wiki/Messina Messina]. [[User:AndyMabbett|Andy Mabbett]] 07:05, 26 May 2007 (PDT)&lt;br /&gt;
*'Area' pages on Wholemap, summarizing the photos, videos, etc... for a specific area, now have Geo codes - [http://wholemap.com/map/area.php?area=NiagaraFalls Niagara Falls, for example] May 10, 2007&lt;br /&gt;
*The Italian Wikipedia, for example [http://it.wikipedia.org/wiki/Genova Genova (Genoa)]&lt;br /&gt;
*I've just added geo support to all of [http://socialight.com Socialight]'s Sticky Notes - here's an example - http://socialight.com/note/2007/4/14/11Aqk_a-great-way-to-spend-a-few-hours &lt;br /&gt;
*The [http://www.bayofislands.net/ Bay of Islands] site has geo on its main page, and all photo pages. Example: [http://www.bayofislands.net/photos/8/ photo of Edgewater Apartments]&lt;br /&gt;
*I've added geo to [http://commons.wikimedia.org/wiki/Special:Whatlinkshere/Template:Location_dec_US all images tagged in Wikimedia Commons] using decimal values. Example: [http://commons.wikimedia.org/wiki/Image:Montreal_City_Hall_Jan_2006.jpg Montreal City Hall, Jan 2006]  [[User:AndyMabbett|Andy Mabbett]] 08:54, 12 Apr 2007 (PDT)&lt;br /&gt;
**Now on pages tagged in D-M-S also.&lt;br /&gt;
*Spotstor.com - e.g. [http://spotstor.com] uses Geo for all coordinates displayed on the site.&lt;br /&gt;
*Panoramio - e.g. [http://www.panoramio.com/photo/564690]&lt;br /&gt;
* Wikipedia-NL now has Geo on all its map-links pages, e.g. [http://www.nsesoftware.nl/wiki/maps.asp?params=52_28_47_N_1_53_51_W_type:city_region:GB&amp;amp;src=Birmingham_%28Engeland%29 maps for Wikipedia-NL article on Birmingham]&lt;br /&gt;
**Called from '''87,724''' article pages as of 2006-04-09; reportedly the sixth most popular website in the Netherlands [http://www.multiscope.nl/organisatie/nieuws/sberichten/nederlandse-wikipedia-groeit-als-kool.html].&lt;br /&gt;
* I recently added Geo to Wikipedia-DE's map link pages  e.g. [http://tools.wikimedia.de/~magnus/geo/geohack.php?language=de&amp;amp;params=52_28_47_N_1_53_51_W_type:city_region:GB maps for Wikipedia-DE article on Birmingham]. [[User:AndyMabbett|Andy Mabbett]] 14:27, 9 Apr 2007 (PDT)&lt;br /&gt;
* I've just added &amp;quot;geo&amp;quot; to OpenStreetMap documentation pages - see [http://wiki.openstreetmap.org/index.php/Birmingham Birmingham page on OpenStreetMap] for example. [[User:AndyMabbett|Andy Mabbett]] 02:39, 6 Apr 2007 (PDT)&lt;br /&gt;
* I've [http://en.wikipedia.org/w/index.php?title=Template%3AGeoTemplate&amp;amp;diff=119003866&amp;amp;oldid=118216477 just added] Geo to Wikipedia's [http://en.wikipedia.org/wiki/Template:GeoTemplate GeoTemplate] which is called by '''many thousands''' of other Wikipedia pages. Example: the coordinates (top right) in [http://en.wikipedia.org/wiki/Great_Barr] link to [http://tools.wikimedia.de/~magnus/geo/geohack.php?params=52.54833_N_1.93212_W_region:GB_source:enwiki-osgb36(SP047945)]; the latter now has a Geo microformat. [[User:AndyMabbett|Andy Mabbett]] 03:38, 30 Mar 2007 (PDT)&lt;br /&gt;
** [http://tools.wikimedia.de/~kolossos/wp-world/imageworld-art.php Map showing global distribution of geo-tagged Wikipedia articles].&lt;br /&gt;
* [http://www.jillesvangurp.com/places jillesvangurp.com] provides an xsl stylesheet to transform Google Earth place-marks (kmz files) into html with nested lists of geo formatted places. Several examples are provided.&lt;br /&gt;
*[http://www.geograph.org.uk Geograph British Isles] has experimental support for geos on '''350,000+''' photo pages, for example http://www.geograph.org.uk/photo/1234&lt;br /&gt;
*[http://www.poi66.com/ POI66] has '''over 58,500''' waypoints geo-formatted, many describing [[geo-waypoint-examples|trails]] e.g [http://www.poi66.com/maps/show_album.php?album=santiago Mijn pelgrimstocht naar Santiago]&lt;br /&gt;
* [http://3amproductions.net 3AM Productions] has published coordinates of cities both in and outside the context of hCards under [http://3amproductions.net/jason.php Jason's] and [http://3amproductions.net/gilbert.php Gil's] pages.&lt;br /&gt;
* [http://www.w3.org/People/Connolly/events/ Dan Connoly's Index of Events] has a few geos&lt;br /&gt;
** Notes that two of the geos are considered invalid because they use commas instead of semicolons&lt;br /&gt;
*Wikitravel now has the facility to add co-ordinates for the subject of the article, and publishes them as a 'geo' microformat - e.g. [http://wikitravel.org/en/Birmingham_%28England%29 Wikitravel - Birmingham]; see [http://wikitravel.org/shared/Tech:Add_SpecialMap_using_Mapstraction_link_for_geo-tagged_pages_and_for_single_listings The announcement].&lt;br /&gt;
* [http://flickr.com/ Flickr] now [http://blog.flickr.com/flickrblog/2006/08/great_shot_wher.html supports the geo microformat] on all [http://flickr.com/map/ geotagged photos].  Within 11 days of launch there are now over '''3,000,000+''' photos (as of 2006-09-07) marked up with the &amp;quot;geo&amp;quot; microformat. &lt;br /&gt;
* [http://ocono.com/ ocono.com] has marked each of it's &amp;quot;Upcoming Events&amp;quot; items with lat/long values.&lt;br /&gt;
* [http://harry.hchen1.com/mylife.htm Harry Chen has marked up his geo location]&lt;br /&gt;
* [http://www.multimap.com Multimap.com] uses the geo microformat to mark up latitude and longitude values on map pages.&lt;br /&gt;
* [http://rasterweb.net/raster/ Pete Prodoehl] geotags posts on his blog.&lt;br /&gt;
* [http://07.pagesd.info/ 07.pagesd.info] uses the geo microformat to mark up latitude and longitude values for each commune of the Ardèche département in France.&lt;br /&gt;
* [http://www.openguides.org/ OpenGuides] has support for the geo microformat in svn, and for now you can see it in action on the [http://cotswolds.openguides.org/ Cotswolds OpenGuide]&lt;br /&gt;
&lt;br /&gt;
== Implementations ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
The following implementations have been developed which either generate or parse geos outside the context of hCards. If you have an geo implementation, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page.&lt;br /&gt;
&lt;br /&gt;
*GIS-Wiki's &amp;quot;[http://www.giswiki.org/hjl_get_CoorE.htm hjl_getCoor]&amp;quot; now outputs Geo markup, from a Google Maps API.&lt;br /&gt;
*[http://www.addressfix.com/ AddressFix] takes any valid address in the listed countries (as at 2003-07) or map point (using GoogleMaps API) and outputs geo markup.&lt;br /&gt;
**Countries: Andorra, Australia, Austria, Belgium, Canada, France, Germany, Gibraltar, Italy, Japan (but only in Japanese), Liechtenstein, Luxembourg, Monaco, Netherlands, New Zealand, San Marino, Spain, Sweden, Switzerland, United States of America and the Vatican City. &lt;br /&gt;
**For countries other than the UK, the British Isles and China it provides geocoding for country names and city names (e.g. &amp;quot;Nairobi, Kenya&amp;quot;).&lt;br /&gt;
**For UK, the British Isles and China, Google returns an error.&lt;br /&gt;
* [http://code.highearthorbit.com/greaseroute/index.php GreaseRoute] is a GreaseMonkey user script (also available as a simple Firefox Extension) which will add icons for displaying the MapQuest map of a [[geo]]. Written by [http://highearthorbit.com Andrew Turner] &lt;br /&gt;
* [http://www.podster.de/page/geotest podster.de] finds geo markups in podcast RSS Feeds and maps soundseeing episodes on a map (German only)&lt;br /&gt;
* [http://blog.codeeg.com/ Calvin Yu] has written a  [http://blog.codeeg.com/2006/01/28/using-microformats-to-plot-my-favorite-places/ web service that will allow you plot and describe places on a Yahoo Map easily] using [[hreview|hReview]] and [[geo]].&lt;br /&gt;
* [http://bluesmoon.blogspot.com/ Philip Tellis] has written a [http://bluesmoon.blogspot.com/2006/01/of-microformats-and-geocoding.html javascript to add maps to geo markup on pages]&lt;br /&gt;
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding geos and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].&lt;br /&gt;
* [http://bluesmoon.blogspot.com/ Philip Tellis] has written some javascript to [http://bluesmoon.blogspot.com/2006/01/of-microformats-and-geocoding.html convert the geo microformat to a google map] using [[geo]].&lt;br /&gt;
* Brian Suda has written some [http://suda.co.uk/projects/microformats/geo/ geo extracting] code to convert geo microformats to KML for use with Google Maps and Google Earth. There is also a bookmarklet to extract the data and pass it to google maps automatically. He is working on a GeoRSS version for Yahoo! Maps as well.&lt;br /&gt;
* Fil explains [http://www.jquery.info/spip.php?article7 how to use the geo microformat with the javascript library jQuery] [http://jquery.com].&lt;br /&gt;
* [http://georss.org/geopress GeoPress] is a WordPress (http://wordpress.org) plugin that supports embedding adrs, geo, maps (dynamically switchable between Google-Yahoo-Microsoft Maps), and GeoRSS (http://georss.org) feeds. Written by [http://highearthorbit.com Andrew Turner]&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
=== Normative References ===&lt;br /&gt;
* [[hcard|hCard]]&lt;br /&gt;
&lt;br /&gt;
=== Informative References ===&lt;br /&gt;
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426] ([http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426])&lt;br /&gt;
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]&lt;br /&gt;
* [http://www.census.gov/geo/www/tiger/tigermap.html TIGER Map Service]&lt;br /&gt;
* [http://en.wikipedia.org/wiki/Geotagging Wikipedia article on GeoTagging]&lt;br /&gt;
&lt;br /&gt;
== Work in progress ==&lt;br /&gt;
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.&lt;br /&gt;
&lt;br /&gt;
* Proposals for changes, additions and other thoughts about [[geo]] may be found in the [[hcard-brainstorming#geo_improvements|hCard brainstorming - geo improvements]] section.&lt;br /&gt;
&lt;br /&gt;
== Related Work ==&lt;br /&gt;
* [[luna]] (proposal for geo-style microformat for co-ordinates on The Moon)&lt;br /&gt;
* [[mars]] (proposal for geo-style microformat for co-ordinates on the planet Mars)&lt;br /&gt;
* [[geo-extension-strawman]] - extends [[geo]] to include the above, and for representing coordinates on other planets, moons etc.&lt;br /&gt;
* [[thoughts-on-extending-the-geo-microformat|thoughts on addind time and reference system]] to the geo microformat, that could also be used for places on other celestial bodies&lt;br /&gt;
&lt;br /&gt;
== Similar Work ==&lt;br /&gt;
* [[adr]]&lt;br /&gt;
* [[hcalendar|hCalendar]]&lt;br /&gt;
* [[XOXO]]&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
* [http://en.wikipedia.org/wiki/Geo_%28microformat%29 Geo on Wikipedia]&lt;br /&gt;
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page]&lt;br /&gt;
* [http://wikitravel.org/en/Wikitravel:Geocoding#Sources_for_lat.2Flongs Sources for latitude/ longitude coordinates]&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
{{geo-related-pages}}&lt;/div&gt;</summary>
		<author><name>Trovster</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hcard-examples-in-wild&amp;diff=17617</id>
		<title>hcard-examples-in-wild</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hcard-examples-in-wild&amp;diff=17617"/>
		<updated>2007-06-15T11:42:39Z</updated>

		<summary type="html">&lt;p&gt;Trovster: /* New Examples */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=hCard Examples in the wild=&lt;br /&gt;
&lt;br /&gt;
This page is an '''informative''' section of the [[hcard|hCard specification]].&lt;br /&gt;
&lt;br /&gt;
The following sites have published [[hcard|hCards]], and thus are a great place to start for anyone looking for examples &amp;quot;in the wild&amp;quot; to try parsing, indexing, organizing etc.  &lt;br /&gt;
&lt;br /&gt;
If people or organizations on your site are marked up with hCard (even just your own contact information), feel free to add it to the top of this list.  Please be sure to include at least one URL to a page on your site that includes actual [[hcard|hCard]] markup.  Examples added without a URL to a page with hCard markup may be removed.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Buttons==&lt;br /&gt;
You can use these buttons on pages with hCards. See [[buttons#hCard]] for any recent additions.&lt;br /&gt;
&lt;br /&gt;
* http://www.crowley.nl/images/hcard.png (mirror: http://www.davidjanes.com/images/mf_hcard.png)&lt;br /&gt;
* http://rbach.priv.at/2006/buttons/hcard.png&lt;br /&gt;
* http://www.boogdesign.com/images/buttons/microformat_hcard.png&lt;br /&gt;
* CSS-powered button, as evidenced at [http://re-run.com/about/microformat-badges microformat badges @ re-run]&lt;br /&gt;
&lt;br /&gt;
== Examples To Act On ==&lt;br /&gt;
&lt;br /&gt;
===New Examples===&lt;br /&gt;
&lt;br /&gt;
Please add new examples to the '''top''' of this section so they can be reviewed!&lt;br /&gt;
* Creation design &amp;amp; marketing has hCards throughout the site, including the [http://www.creation.uk.com/contact/ contact page], the [http://www.creation.uk.com/company/leigh-scott/ company profile pages] and on the [http://www.creation.uk.com/news/2007/06/06/easy-money/#comments-view comments on articles]&lt;br /&gt;
* Wikipedia now has a template, [http://en.wikipedia.org/wiki/Template:Hcard-geo hcard-geo], for in-line hCards with coordinates, such as that on [http://en.wikipedia.org/wiki/Engine_Arm Engine Arm]&lt;br /&gt;
* [http://www.thomsonlocal.com/ ThomsonLocal.com], major UK business directory publisher, use hcard on the search results and company information pages.&lt;br /&gt;
* [http://www.corissia.com Corissia Group Hotels in Crete Greece] have included contact information as a hCard on the footer of every page of the website. There is a multilingual implementation as well.&lt;br /&gt;
* [http://zucchetti.co.uk/2007/03/06/simple-address-formatting-solution/ Laura Zucchetti] illustrates a simple address formatting solution as a hCard and marked up in a definition list. &lt;br /&gt;
* [http://www.feike.de/Kontakt.html Feike Contact] has a hCard on to top of the page.&lt;br /&gt;
* [http://www.londondrum.com/ London Drum] uses a whole host of microformats - there are hcards and geo's on the hotel pages, events are written up in hcalendar format on the homepage, and you can also find some hreviews as well (like on the [http://www.londondrum.com/accommodation/athenaeum.php Athenaeum Hotel page]) &lt;br /&gt;
* [http://www.regels-stadskanaal.nl/ Regelingenbank Stadskanaal] has a hCard on each page, containing Geo-information too. &lt;br /&gt;
* [http://www.tomstone.se Tom Stone - Trollkarl] has a hCard in the footer of each page of the site.&lt;br /&gt;
* [http://www.rolandinsh.lv/ Rolands Umbrovskis]'s home page has hCard in [http://www.rolandinsh.lv/?ro=contacts contact page] and all other pages with contact information.&lt;br /&gt;
* [http://www.epiphanysolutions.co.uk/ Epiphany Solutions Ltd] use a hCard on their contact us page. We intend to use the hCard on everypage if successfully implemented, along with a link to the Technorati vCard generator.&lt;br /&gt;
* [http://twitter.com Twitter] uses hCard for user information (along with [http://ihack.us/2007/05/14/twitter-gets-microformatted/ several other microformats])&lt;br /&gt;
* [http://www.bendodson.com/developer/ Ben Dodson] uses an hCard for his contact details on every page of his site as well as using hCards for any XFN relationships in his blogrolls.&lt;br /&gt;
*[http://www.pats.ua.ac.be/group PATS Group Members] uses hCard to mark up member contact information.&lt;br /&gt;
*[http://couchsurfing.com CouchSurfing] has limited information in hCard available on members' profiles (such as [http://www.couchsurfing.com/people/guaka Guaka's]).&lt;br /&gt;
*Wikipedia-UK (Ukranian)&lt;br /&gt;
**Starting to roll out on biographies e.g. [http://uk.wikipedia.org/wiki/%D0%93%D0%B5%D1%82%D1%8C%D0%BC%D0%B0%D0%BD_%D0%92%D0%B0%D0%B4%D0%B8%D0%BC_%D0%9F%D0%B5%D1%82%D1%80%D0%BE%D0%B2%D0%B8%D1%87 Vadym Hetman]&lt;br /&gt;
* [http://christophertcressman.com Christopher T. Cressman] uses an hCard on the home page of his blog, [http://christophertcressman.com christopher t cressman].&lt;br /&gt;
* [http://kpumuk.info Dmytro Shteflyuk] uses an hCard on his [http://kpumuk.info/contact/ contact] and [http://kpumuk.info/curriculum-vitae/ curriculum vitae] pages.&lt;br /&gt;
*Wikipedia-EN&lt;br /&gt;
**starting to roll-out on articles about people, for example [http://en.wikipedia.org/wiki/Albert_einstein Albert Einstein]. The nature of Wikipedia means that there are a large number of templates to update (Albert's is &amp;quot;infobox scientist; there's also &amp;quot;infobox military people&amp;quot;, &amp;quot;infobox musician&amp;quot; and so on, almost ad infinitum). DoB is only included if it's entered using a birth-date template, not as raw text. &lt;br /&gt;
**starting to roll-out on articles about places, for example on UK Railway station template, e.g. [http://en.wikipedia.org/wiki/Birmingham_New_Street Birmingham New Street station] (includes Geo); and  cities, for example [http://en.wikipedia.org/wiki/New_York_City New York]. See above for note on Wikipedia templates.&lt;br /&gt;
**Any Wikipedia editors willing to assist with updating templates should see [http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Microformats Wikipedia's microformat project]; [http://en.wikipedia.org/wiki/Category:Templates_generating_hCards Wikipedia templates generating hCards] &amp;amp; [http://en.wikipedia.org/wiki/Category:Templates_generating_Geo Wikipedia templates generating Geo]&lt;br /&gt;
* The [http://www.bayofislands.net/ Bay of Islands] site has implemented hCard on all listing pages, eg: [http://www.bayofislands.net/accommodation/backpackers/saltwater-lodge/ Saltwater Lodge]&lt;br /&gt;
* [http://people.cs.uchicago.edu/~mpschaef/index.html Merrick Schaefer] is psyched to use hCard on his homepage for his contact info.&lt;br /&gt;
* [http://www.hess-cr.com Christian Hess] has an hCard in his [http://www.hess-cr.com/utilidades/correo.shtml#postal contact] and [http://www.hess-cr.com/secciones/curriculum/datos.shtml personal curriculum] pages (in Spanish)&lt;br /&gt;
* [http://www.JamPlanet.com Jam Planet] uses hCard in Contact Us page; application can generate hCard for a contact.&lt;br /&gt;
* [http://www.anisfield-wolf.org/ The Anisfield-Wolf Book Awards], designated specifically to recognize works addressing issues of racism and diversity, uses hCard for the author bios of [http://www.anisfield-wolf.org/Winners/PastWinners/ past winners].&lt;br /&gt;
* [http://www.buy-our-honeymoon.com/ Buy Our Honeymoon], a wedding gift list service, uses hCard in their [http://www.buy-our-honeymoon.com/contact Contact Us] page.&lt;br /&gt;
* '''W3C webmaster''' [http://www.w3.org/People/Jean-Gui/ Jean-Guilhem Rouel] now has an hCard.&lt;br /&gt;
* [http://source.ibegin.com/ iBegin Source] - All 10.8+ million business listings have their information marked up in hCard. Example: [http://source.ibegin.com/california/adelanto/aeronautical-supplies/general-atomics-9779-yucca-rd-1.html General Atomics]&lt;br /&gt;
* [http://david.weekly.org/ David Weekly] has added an hCard to his home page for himself.&lt;br /&gt;
* [http://ficlets.com/stories/12 Ficlets] story page uses hCard for author bio.&lt;br /&gt;
* [http://redmonk.com/contact/ RedMonk Contact page] uses hCard for RedMonk firm as well as each analysts.&lt;br /&gt;
* [http://source.ibegin.com/ iBegin Source] uses hCard to identify business information for all 10.5+ million businesses listed.&lt;br /&gt;
* [http://www.lounews.com/ The Louisville News Company] uses hCard for site-wide contact information for the company and for the site developer.&lt;br /&gt;
* [http://cloudislands.com/contact.php Cloud Islands] uses hCard for our Contact Info.&lt;br /&gt;
* [http://www.international.unt.edu UNT International] uses hCard to mark up contact information sitewide (see esp. [http://www.international.unt.edu/offices/ieli/people/instructors/profiles the IELI instructor profile listing])&lt;br /&gt;
* [http://www.giraffo.de giraffo.de] has different hCards on every page (+ geo in &amp;quot;kontakt&amp;quot;)&lt;br /&gt;
* [http://www.enap.com ENAP, Inc.] lists the HR Contact in hCard format on the [http://www.enap.com/career.aspx Career Opportunities] page.&lt;br /&gt;
* [http://sxsw07.conferenceer.com/people Conferenceer] lists panelists and participants to the 2007 South by Southwest interactive conference in hCard format&lt;br /&gt;
* [http://news.stanford.edu Stanford News] (Redesign)  hCard in the footer on every page as well as markup for every staff member on the Staff page.&lt;br /&gt;
* [http://www.wikiservice.at/fractal/wikidev.cgi?FR/EveMoreau Valérie-Eve Moreau] has an hCard on her wiki-homepage.&lt;br /&gt;
* [http://en.wikipedia.org/wiki/St_George%27s_Minster%2C_Doncaster St George's Minster, Doncaster, on Wikipedia]&lt;br /&gt;
* AOL Journals publishes hCards for authors. [http://journals.aol.com/carowill/whats-happening Example]&lt;br /&gt;
* Ian McKellar's [http://ian.mckellar.org/ home page] is an hCard that's styled to look like a business card.&lt;br /&gt;
* [[Christophe Ducamp]]'s hCard based on    [http://www.wikiservice.at/fractal/wikidev.cgi?FR/MicroFormats/ChristopheDucamp wiki personal page] of a wiki-branch which could be dedicated to seed a french group to support microformats. Thanks to Laurent Lunati for the CSS. You can [http://www.wikiservice.at/fractal/wikidev.cgi?action=edit&amp;amp;id=FR/MicroFormats/ChristopheDucamp edit it]. Any suggestions welcome.&lt;br /&gt;
* [http://www.matthewwest.co.uk Matthew West] has an hCard on his [http://www.matthewwest.co.uk/email contact] page.&lt;br /&gt;
*[http://www.webmaster.waw.pl Paweł Wrzosek] Freelance webdeveloper`s portfolio&lt;br /&gt;
*[http://thibeaultstudios.com Thibeault Studios] has an organization hCard in the footer on every page as while as individual hCards on the [http://thibeaultstudios.com/contact_us.php Contact] page.&lt;br /&gt;
*[http://www.stanford.edu/ Stanford.edu] hCard markup is included in the footer of the homepage and all subsequent pages within the /home directory.&lt;br /&gt;
*[http://openid.ne.jp OpenID.ne.jp] First OpenID provider service in Japan(日本語). Each personal  OpenID page (ex:[http://eouia.openid.ne.jp http://eouia.openid.ne.jp]) is marked up as his hCard. And there is a company hCard on every page, too.&lt;br /&gt;
* [http://www.qwertycars.co.uk/garages/mechanics-near-tadworth-kt20.aspx UK Car Garages] Address of car mechanics in the UK, in hCard format.&lt;br /&gt;
* [http://www.columbiaautomation.com/sub/contact.php Columbia Automation]'s About Us page every employee marked up as an hCard, as well as having a company hCard with geo information.&lt;br /&gt;
* [http://www.pointermix.com Pointermix Design] uses the hCard format.&lt;br /&gt;
* [http://eight6.com/contact/ eight6]'s contact page uses the hCard format.&lt;br /&gt;
* [http://www.raveaboutit.com.au Rave About It]'s business listings use the hCard format.&lt;br /&gt;
* [http://optics.org/cws/Contact/OurTeam.do optics.org]'s team page.&lt;br /&gt;
* [http://www.robcottingham.ca/contact Rob Cottingham]'s first foray into microformats is an hCard on the contact page of his personal blog. (He was inspired by Tantek Çelik's presentation at Web Directions North 2007.)&lt;br /&gt;
* [http://redmonk.net/about-this-site Steve Ivy] - hcard about page, includes the usual suspects + XFN on 'url's, photo, amd geo.&lt;br /&gt;
* [http://seattleu.edu Seattle University] uses hCard on it's front page and most pages that share an official template. &lt;br /&gt;
* [http://www.josemarti.waw.pl Jose Marti XXII Secondary School in Warsaw] includes hCard on Contact and About Author sections&lt;br /&gt;
* [http://www.jaama.co.uk Jaama] have their company details as a vCard download on their [http://www.jaama.co.uk/Contact.aspx contact] and [http://www.jaama.co.uk/Fleet_Management_Software.aspx fleet management software] page.&lt;br /&gt;
* [http://3amproductions.net 3AM Productions] has company details marked up as hCard all across the site and particularly for [http://3amproductions.net/jason.php Jason] and [http://3amproductions.net/gilbert.php Gilbert]&lt;br /&gt;
* [http://jc-development.co.uk/ JC's Development] has company contact details as hCard.&lt;br /&gt;
* [http://berlin.barwick.de/index.html Berlin Guide] is converting their address markup to hcard, e.g. [http://berlin.barwick.de/shopping/kadewe-kaufhaus-des-westens.html KaDeWe] &lt;br /&gt;
* [http://www.xlntads.com XLNTads] has their contact information marked up in hCard, as well as their development schedule/timeline in hCalendar&lt;br /&gt;
* [http://derrick.pallas.us Derrick Pallas] tells people to look for him here.&lt;br /&gt;
* [http://bluemonkcreative.com/contact/ Bill Turner] adds an hCard to the contact page of his freelance business' website.&lt;br /&gt;
* [http://www.oppenheim.com.au/ James Oppenheim's blog] includes an inline author hCard in the footer of each page and also on the contact page.&lt;br /&gt;
* [http://steinhardt.nyu.edu/ NYU Steinhardt] has [http://steinhardt.nyu.edu/faculty_bios/list/Faculty 240+ faculty bios marked up], e.g. [http://steinhardt.nyu.edu/faculty_bios/view/Susan_Murray].&lt;br /&gt;
* [http://www.boogdesign.com/aboutus.html boogdesign.com] has added hCard markup on the contact page.&lt;br /&gt;
* [http://www.gptg.org/ Great Places To Golf], hCards for golf clubs around the world, e.g. [http://www.gptg.org/club/12/]&lt;br /&gt;
*[http://www.travellerspoint.com/ The Travellerspoint Travel Community] has added hCards to all of their member profiles (e.g. [http://www.travellerspoint.com/member_profile.cfm?user=jax_07]). Details include name, photo, location, notes and url. &lt;br /&gt;
* The [http://www.westmidlandbirdclub.com/ West Midland Bird Club] in the English Midlands uses hCard on its [http://www.westmidlandbirdclub.com/ home page], [http://www.westmidlandbirdclub.com/diary/ events diary], [http://www.westmidlandbirdclub.com/club/contact.htm contact pages], [http://www.westmidlandbirdclub.com/site/links.htm links page], [http://www.westmidlandbirdclub.com/club/older.htm list of the world's oldest bird clubs] and in a page footer which is gradually being rolled out across the whole site. {{UpdateMarker}} Page-footer's hCard now has logo, using [[include-pattern]].&lt;br /&gt;
*[http://wizardishungry.com/blog/ wizardishungry/blog] has the author's hCard in the footer of every page with a link to X2V.&lt;br /&gt;
* [http://www.walkerfineart.com Walker Fine Art Gallery] Most pages contain an hCard in the footer.&lt;br /&gt;
* [http://www.brdatasystems.com.au/contact-us.html B&amp;amp;R Data Systems] is an organisation hCard. We have also used the technorati tool to download as a vCard, which I think is useful for a business.&lt;br /&gt;
* [http://chewbittel.com/contact.php Chew Bittel Assoc., Inc.] is an organization hCard. It's got abbr's in there, and a duplicate telephone field, and some hidden things. I'm really pushing things to the limit here. This should be a great test for your parser.&lt;br /&gt;
* [[User:Steve Ivy|Steve Ivy]]'s [http://redmonk.net/about-this-site/ about page] has his hcard, including a link to Technorati's contacts feed to let visitors download his contact information.&lt;br /&gt;
* Scott Allan Wallick's hCard is [[User:ScottWallick|his user page]] and on his blog, [http://www.plaintxt.org/about/2/ plaintxt.org]&lt;br /&gt;
* [[User:Bob_Jonkman|Bob Jonkman's hCard]] '''on this 'wiki'''' &lt;br /&gt;
* [http://www.last.fm Last FM] has hCards hidden on their profile pages e.g. [http://www.last.fm/user/Crok/?scrobbling=t1].&lt;br /&gt;
* [http://thetenwordreview.com The Ten Word Review] simply contains ten word long reviews. All reviews are marked up as [[hreview|hReviews]], and user information is marked up as hCards.&lt;br /&gt;
*OffshoreAgile.com, a subsite of Starsoft Development Labs, uses hCard in the [http://www.offshoreagile.com/company/contact/ Starsoft Contacts] and Media Inquiries sections&lt;br /&gt;
*T-Mobile uses hCard for the [http://t-mobilepressoffice.co.uk/press/contact-details/ T-Mobile UK Press Contact Details page], as well as for some of the latest press releases&lt;br /&gt;
* Psychology Press and Routledge's Behavioral Sciences' publishing division have implemented hCard on their contact pages on 17 of their websites (example on the contact page on their [http://www.clinicalpsychologyarena.com/contact/ Clinical Psychology Arena])&lt;br /&gt;
*[http://72ppi.us 72ppi], uses hCard in the footer.&lt;br /&gt;
*[http://www.csarven.ca Sarven Capadisli] uses hCard throughout the site (including user comments in articles).&lt;br /&gt;
* [https://www.urbanbody.com/information/contact-us Urban Body Men's Clothing] uses hCard for business locations and hCalendar for business hours.&lt;br /&gt;
* [http://www.iqair.us/ IQAir North America], uses hCard for contact information.&lt;br /&gt;
* [http://www.infoiasi.ro/ The website of the Faculty of Computer Science], &amp;quot;A. I. Cuza&amp;quot; University Ia&amp;amp;#351;i, Romania uses hCard for each staff member.&lt;br /&gt;
* [http://www.finds.org.uk/ The Portable Antiquities Scheme at the British Museum] hCards added to footer of every page and to contacts section. Working on adding more and getting it right.&lt;br /&gt;
* In [http://www.ideasfornet.com/ IdeasForNet.com - the ideas repository] hCards were implemented partially in the footer of each page, and more comprehensively in the contact and about pages.&lt;br /&gt;
* The [http://www.cst.ed.ac.uk/ Centre of Canadian Studies] at the University of Edinburgh use hCards for contact information in the footer of their site.&lt;br /&gt;
* [http://www.theatrestudies.llc.ed.ac.uk/ Theatre Studies: European Theatre] at the University of Edinburgh use hCards for contact information on their home page&lt;br /&gt;
* [http://www.carolinemockett.com/design/about.aspx Caroline Mockett] has an hCard on her About Me page&lt;br /&gt;
* [http://wait-till-i.com Christian Heilmann] has a footer address using hCard&lt;br /&gt;
*[http://www.audience-response-rentals.com/ Audience Response System Rentals] uses hcard as a popup in the site accessibility area (lower right) for easy copy and paste of address by customers.&lt;br /&gt;
* [http://www.fischsolutions.com/ Fisch Internet Solutions] uses an embedded hCard and a vCard download to provide customers an easy way to contact them on their [http://fischsolutions.com/contactus.html Contact Us] section of the website.&lt;br /&gt;
* [http://www.micatholicconference.org/ Michigan Catholic Conference] uses hCard for contact information in the sidebar.&lt;br /&gt;
* [http://www.adambunn.co.uk/ Adam Bunn] provides contact details in the sidebar using hCard.&lt;br /&gt;
* [http://www.belkin.com/pressroom/releases/uploads/10_10_06NotebookExpansionDock.html Belkin Press Releases] are using hCards for PR contacts and corporate offices.&lt;br /&gt;
* [http://mybank.com myBank.com] uses hCard for its listings of every branch of every FDIC-insured bank in the United States.&lt;br /&gt;
* [http://leftlogic.com Left Logic] uses hCard for embedded contact information.&lt;br /&gt;
* [http://inga-art.co.uk/artist Inga Scholes] uses hCard for contact information in the sidebar.&lt;br /&gt;
* [http://www.lussumo.com/ Lussumo] uses hCards on user profile pages in its open-source [http://www.getvanilla.com/ Vanilla] Discussions Forum software.&lt;br /&gt;
* [http://www.creative-ways.nl/ Ron Kok] uses hCards to mark-up the names and URLs of commentors on his blog. He also uses hCards in combination with XFN in his blogposts to refer to friends, and has an hCard for himself on every page on his blog.&lt;br /&gt;
* [http://tagg.no Tagg Media] uses hCard for [http://heine.tagg.no/contact.php contact information] and provide link to vCard download in the contact section.&lt;br /&gt;
* The article about the fictitious Matrix character [http://en.wikipedia.org/wiki/Neo_%28The_Matrix%29 Thomas A Anderson in Wikipedia] is now marked up with hCard.&lt;br /&gt;
* [http://dconstruct06.madgex.com/ d.Construct 2006 Backnetwork] uses hCards for conference delegates (and provides the markup so that delegates can copy and paste cards into their own sites).&lt;br /&gt;
* [http://www.brown.edu Brown University] now uses hCard on the front page&lt;br /&gt;
* [http://www.wideblueyonderweb.co.uk Dunks at Wide Blue Yonder Web Design] has added hCard markup on his [http://www.wideblueyonderweb.co.uk/wbyw/pages/contact.htm contact page] and is looking to implement it on all past &amp;amp; future contact pages for clients.&lt;br /&gt;
* [http://southamptonrubberstamp.com Southampton Rubber Stamp Company] now has hCard markup with a vCard download link on every page.&lt;br /&gt;
* [http://barefoot-ceramics.com Barefoot Ceramics paint your own pottery studio] (in Newport, South Wales) has added hCard markup to its [http://barefoot-ceramics.com/find#address &amp;quot;Find&amp;quot;] page and other address instances. They hopes to implement hCalendar event lists as soon as an ics to hCalendar PHP class can be found or written.&lt;br /&gt;
* [http://dsingleton.co.uk/ David Singleton] has added a hCard to his blog.&lt;br /&gt;
* [http://krisswatt.co.uk/ Kriss Watt] has hidden an hCard his blog footer.&lt;br /&gt;
* [http://www.thestreet.org.au The Street Theatre (Canberra, Australia)] has added hCard markup to its [http://www.thestreet.org.au/contact.htm Contact Us] page. hCalendar markup will soon be added for all of our performances.&lt;br /&gt;
* [http://www.informatik.uni-hamburg.de/SVS/personnel/henrich/index.php Henrich C. P&amp;amp;ouml;hls] has marked up his about page using hcard, including his PGP-Key that is stored in an abbr title, using class=key.&lt;br /&gt;
* [http://www.yalf.de Yalf Webentwicklung] has [http://www.yalf.de/kontakt contact information] available as hCard (and vCard).&lt;br /&gt;
* [http://www.zeldman.com/about/ Jeffrey Zeldman]. Jeffrey Zeldman has marked up his about page using hcard.&lt;br /&gt;
* [http://WhereAreYouCamping.com Where Are You Camping]. hCards for all members and camps, employing the include pattern as well. AFAIK this is the first Burning Man related microformats implementation, not to mention addresses in Black Rock City.&lt;br /&gt;
* [http://www.clacksweb.org.uk Clackmannanshire Council ]. hCard is implemented for all contact details across the site, and for specific individuals such as elected members (Councillors).&lt;br /&gt;
* [http://www.webdirections.org Web Directions]. hCard is used as contact information for the conference, while speakers are marked up with hCard.&lt;br /&gt;
* [http://www.markthisdate.com/contactform.html MarkThisDate.com]. An hCard is implemented on our contact form. For our calendars hCalendars will follow as soon as possible.&lt;br /&gt;
* [http://www.msiinet.com/contact/ MSI Systems Integrators] has its &amp;amp;quot;Contact MSI&amp;amp;quot; page encoded with hCards.&lt;br /&gt;
* [http://www.coolblue.nl/ Corporate website of Coolblue BV]. hCards were implemented in both the footer of each page, and in the &amp;quot;News&amp;quot; section for press contact information.&lt;br /&gt;
* [http://www.besancon.fr/index.php?p=32 Official site of Besançon (France)] uses hCard for each page concerning the small towns surrounding Besançon.&lt;br /&gt;
* [http://2006.dconstruct.org/speakers/ d.Construct 2006 conference speakers list] is implemented using hCards.&lt;br /&gt;
* [http://local.yahoo.com Yahoo Local] now supports hCards for business and places in the search results&lt;br /&gt;
* [http://learningtheworld.eu/imprint/ Learning the World] has hcard information on the imprint, alas we didn't succeed to mark-up the work phone and fax numbers properly.&lt;br /&gt;
* The [http://www.fuckparade.org F’parade] website uses hcard, though I didn't find a type to distinguish mobile and landline phone numbers.&lt;br /&gt;
**Use &amp;lt;code&amp;gt;cell&amp;lt;/code&amp;gt; for mobiles.&lt;br /&gt;
* [http://www.miranet.nl/contact.htm Miranet Webdesign] have added a hcard to their [http://www.miranet.nl/contact.htm 'contact' page]&lt;br /&gt;
* [http://weblog.200ok.com.au/ Ben Buchanan] has added a vCard to the [http://weblog.200ok.com.au/about/ 'About' page on The 200ok Weblog]&lt;br /&gt;
* [http://www.radiantcore.com Radiant Core] has their contact information [http://www.radiantcore.com/contact/ available in hCard].&lt;br /&gt;
* [http://www.mikerumble.co.uk/ Mike Rumble] has [http://www.mikerumble.co.uk/contact.html uploaded his hCard].&lt;br /&gt;
* [http://www.saumag.edu/ Southern Arkansas University] has its contact footer encoded as hCard&lt;br /&gt;
* [http://main.uab.edu/ University of Alabama at Birmingham] has its contact footer encoded as hCard&lt;br /&gt;
* [http://www.capital.edu Capital University] has contact footer and bloggers' names encoded as hCard. Also, all page-specific contact information is encoded as hCards (see [http://www.capital.edu/Internet/Default.aspx?pid=67 Admissions] page for an example)&lt;br /&gt;
* [http://main.uab.edu/shrp/ UAB School of Health Professions] uses hCard in its contact footer&lt;br /&gt;
* [http://green.carisenda.com/ Stephen Stewart] has his hCard on the front page of his weblog ('You are here' section)&lt;br /&gt;
* [http://www.fberriman.com/ Frances Berriman] has a hidden vCard in the footers of her website.&lt;br /&gt;
* [http://www.candlescience.com/ CandleScience Candle Supply] added a hidden hcard sitewide.&lt;br /&gt;
* [http://www.direction.es/ Direction] uses hCard for contact information.&lt;br /&gt;
* [http://audiobank.tryphon.org AudioBank] uses hCard to display member informations.&lt;br /&gt;
* [http://www.vivabit.com/atmedia2006/speakers/ @media speakers] are marked up with hCard (photos depend on BASE tag support which makes this a good test case)&lt;br /&gt;
* [http://www.dougransom.com Doug Ransom] uses hCard for his financial advisory practice. &lt;br /&gt;
* [http://rubyandrails.org/usergroups/newcastle/members.html ncl.rb] uses hCard for contact information.&lt;br /&gt;
* [http://www.snowinteractive.com/ Snow Interactive] uses hCard for contact information.&lt;br /&gt;
* [http://flickr.com Flickr] now supports [[hcard|hCard]] and [http://gmpg.org/xfn XFN] on profile pages.  See [http://flickr.com/photos/factoryjoe/113866484/ screenshot of Flickr UI in Flock browser using Flocktails extension - March 17th 2006].&lt;br /&gt;
* [http://www.ndiyo.org/contact Contact information for the Ndiyo project]&lt;br /&gt;
* [http://www.pixelenvy.co.uk/ Pixel Envy] uses hCard for contact information on every page&lt;br /&gt;
* [http://stilbuero.de/contact/ Klaus Hartl] uses hCard in the sidebar for contact information (maybe easier to parse through delivering xhtml as xml).&lt;br /&gt;
* [http://charlvn.virafrikaans.com/contact Charl van Niekerk's hCard]&lt;br /&gt;
* [http://billy-girlardo.com/WP/ BillyBLOGirlardo] uses hCard for contact information.&lt;br /&gt;
* [http://www.hicksdesign.co.uk/ Hicksdesign] uses hCard for contact information.&lt;br /&gt;
* http://www.gr0w.com/articles/press/growsearch_launched_press_release/ - hCard in a press release for the press contact info&lt;br /&gt;
* http://www.redmonk.com/cote/archives/2006/03/testing_out_mic.html - hCard with explanation&lt;br /&gt;
* [http://andy.ciordia.info/ it's my island], personal blog, hcard on the ''[http://andy.ciordia.info/pages/about_me About the Writer]'' page. [[User:Ciordia9|Andy Ciordia]]&lt;br /&gt;
* [http://www.windowonwoking.org.uk/ Window on Woking], a local community site in the UK, uses hCard in the homepage of each member organisation and local Councillor.&lt;br /&gt;
* [http://ChunkySoup.net/ ChunkySoup.net] has redesigned using hAtom 0.1 and hCards on the entire site -- by [[User:ChrisCasciano|Chris Casciano]]&lt;br /&gt;
* [http://www.30boxes.com/ 30 Boxes],a social calendar application and digital lifestyle aggregator, automatically creates an hcard for you with your account.  It is found under Settings &amp;gt; Syndication.&lt;br /&gt;
* [http://www.nearwhere.com/ Nearwhere.com] allow you to put an hcard on an interactive map.&lt;br /&gt;
* [http://www.brentozar.com/ Brent Ozar] added a [http://www.brentozar.com/contact.php contact] page hCard.&lt;br /&gt;
* [http://www.kerihenare.com/ Keri Henare] has rewritten his [http://www.kerihenare.com/contact/ contact] page hCard. Now using &amp;lt;code&amp;gt;&amp;lt;object&amp;gt;&amp;lt;/code&amp;gt; instead of &amp;lt;code&amp;gt;&amp;lt;img&amp;gt;&amp;lt;/code&amp;gt; for photo. (Thanks Brian Suda for updating the vCard converter)&lt;br /&gt;
* [http://michaelraichelson.com/contact/ Michael Raichelson] had an hCard on his contact page before SXSW, but never thought to add it here until Tantek requested it.&lt;br /&gt;
* [http://www.commoner.com/~lsimon/lindsey_simon_hcard.html Lindsey Simon] has added an hCard to his website as per Tantek's SXSW request for folks to try it &lt;br /&gt;
* [http://www.davidgagne.net/ David Gagne] has an hCard in his sidebar.&lt;br /&gt;
* [http://www.churchzip.com/map/ Churchzip.com/map] and [http://www.skiwhere.com/map/ Skiwhere.com/map], provide churches, hotels, and ski resorts on the same maps.  Locations are formatted as hCards.&lt;br /&gt;
* All [http://www.iqdir.com/ IQ Directory Solutions] Yellow Pages web portals use [[hcard|hCard]] markup on listings. For example [http://www.yellowpages-cambodia.com/ Cambodia Yellow Pages] and [http://www.superpages.com.my/ Malaysia Super Pages]&lt;br /&gt;
* Ning's cloneable Group app uses fuzzy matching to map custom fields to [[hcard|hCard]] markup on its [http://group.ning.com/index.php?controller=person&amp;amp;action=view&amp;amp;content=JonathanAquino profile] pages.&lt;br /&gt;
* [http://claimid.com/factoryjoe Chris Messina' ClaimID hCard]&lt;br /&gt;
* [http://factoryjoe.com/blog/hcard Chris Messina' hCard]&lt;br /&gt;
* [http://flock.com/about Flock About]&lt;br /&gt;
* [http://tantek.com/microformats/2006/03-01-TechPlenAgenda.html Agenda: W3C Technical Plenary Day, March 1 2006] has [[hcard|hCard]] and [[hcalendar|hCalendar]] markup. ([http://www.w3.org/2006/03/01-TechPlenAgenda.html original here]).&lt;br /&gt;
* [http://www.gr0w.com/articles/press/growsearch_launched_press_release/ GrowSearch Launched (Press Release)] uses an hCard to provide Press Contact Point.&lt;br /&gt;
* The [http://www.arborday.org/ National Arbor Day Foundation] has started using hCards for their [http://arborday.org/programs/conferences/communityforestry/index.cfm upcoming] [http://arborday.org/programs/conferences/hazardtrees-treeplanting/ conferences].&lt;br /&gt;
* [http://www.multipack.co.uk The Multipack] has numerous hCards, especially on the [http://www.multipack.co.uk/members/ members page], as well as the next meeting information.&lt;br /&gt;
* [http://deadringrancor.livejournal.com/ Justin McDowell] used an hCard when [http://deadringrancor.livejournal.com/221332.html referring to a person in his blog post]&lt;br /&gt;
* [http://davecardwell.co.uk/cv/ Dave Cardwell] has included his hCard in his Curriculum Vitae.&lt;br /&gt;
* [http://blog.usweb.com/ Shaun Shull] has written a great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], and has included his [[hcard|hCard]] as one of the examples.&lt;br /&gt;
* [http://www.thefutureoftheweb.com/ Jesse Skinner] has written a simple [http://www.thefutureoftheweb.com/blog/2006/1/hcard tutorial with examples]&lt;br /&gt;
* [http://www.w3.org/2005/12/allgroupoverview.html 2006 W3C Technical Plenary Week] has marked up the venue, contacts, and program committee members all with hCard.&lt;br /&gt;
* [http://www.avf-nexus.co.uk AVF-Nexus] have a hCard on their [http://www.avf-nexus.co.uk/contact/ contact page] - (by [http://creation.uk.com Creation&amp;quot;])&lt;br /&gt;
* [http://www.thefantasticos.com/andrew/ Andrew White] posted [http://www.thefantasticos.com/andrew/index.php/my-hcard/ his hCard] and [http://www.thefantasticos.com/andrew/index.php/62/microformats-the-should-have-been-obvious-web-dev-tool/ blogged about it].&lt;br /&gt;
* [http://www.2sheds.ru Oleg &amp;quot;2sheds&amp;quot; Kourapov] in his [http://www.2sheds.ru/blog/ blog] ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog X2V]) has turned personal profile into hCard ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/hcard.html X2V]) and his blogroll - into combination XFN/hCards ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/friends.html X2V])&lt;br /&gt;
* [http://www.approveddesign.co.uk Approved Design Consultancy] have a hCard on their [http://www.approveddesign.co.uk/about/contact/ contact page] as well as on their [http://www.approveddesign.co.uk/about/people/ people section] - (by [http://creation.uk.com Creation&amp;quot;])&lt;br /&gt;
* [http://weblog.200ok.com.au/ Ben Buchanan] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&amp;amp;format=search Colin Morris] have [http://weblog.200ok.com.au/2006/01/griffith-phonebook-adds-hcard-and.html implemented hCards and vCards] for the [http://www.griffith.edu.au Griffith University] [http://www.griffith.edu.au/find/content_phonebook.html online phone book]. Eg. [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=ben+buchanan&amp;amp;format=search Ben's vCard] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&amp;amp;format=search Colin's vCard]&lt;br /&gt;
* WWF-Australia [http://wwf.org.au/about/contactdetails/ contact details page]&lt;br /&gt;
* [http://rasterweb.net/raster/ Pete Prodoehl] used the hCard format on his [http://rasterweb.net/raster/contact.html Contact page] and his [http://rasterweb.net/portfolio/ Portfolio]&lt;br /&gt;
* [http://alexander-mette.de amette] uses the hCard format in a module of his TikiWiki powered blog&lt;br /&gt;
* [http://staff.washington.edu/oren/weblog2/ Oren Sreebny] has an hcard on his blog main index template &lt;br /&gt;
* [http://www.cs.brandeis.edu/~zippy/ Patrick Tufts] has an hCard on his homepage.&lt;br /&gt;
* [http://ascii20.blogspot.com/ Mathias Kolehmainen and Jamie Taylor] have hCards on their weblog.&lt;br /&gt;
* [http://www.hoppsan.org/jamesb/blogger/ Barnaby James] has a hCard on his weblog.&lt;br /&gt;
* [http://esa-education.com/schools/map ESA Education] Uses hCards for their 100+ schools and each of the individual school sites.&lt;br /&gt;
* [http://www.thereisnocat.com/#vcard Ralph Brandi] has added an hCard to the sidebar of his weblog as a result of Tantek Çelik's portion of the Microformats presentation at SXSW 2006.&lt;br /&gt;
* [http://www.pierce.ctc.edu/ephone/ Pierce College] -- community college directory uses hCard on all individual directory entries.&lt;br /&gt;
* [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/ the Institutional Web Management Workshop 2006] have marked up all their [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/committee/ speakers with hCard].&lt;br /&gt;
* http://wikitravel.org/en/Singapore/Sentosa. Wikitravel is experimenting with hcard on its travel guides. This guide uses hcard for all its business listings. More info on http://wikitravel.org/en/Wikitravel_talk:Listings.&lt;br /&gt;
* [http://www.musik-erber.de/ Musik-Erber] uses to present contact information at the sidebar&lt;br /&gt;
* [http://cdevroe.com/about/#contact Colin D. Devroe] uses hCard to display his contact information on his about page&lt;br /&gt;
* The ECS (Scool of Electronics and Computer Science  at the University of Southampton) [http://www.ecs.soton.ac.uk/people People Pages] use vCard. Contact cjg@ecs.soton.ac.uk if there's any bugs.&lt;br /&gt;
* [http://www.southwestern.edu/~ramseyp Pat Ramsey] has his contact information on his blog marked up with hCard. Contact [mailto:ramsey.pat@gmail.com ramsey.pat@gmail.com] if there are any bugs there.&lt;br /&gt;
* [http://www.meryl.net/ Meryl K. Evans] has a hidden hCard on her homepage.&lt;br /&gt;
* [http://www.vyre.com/company/contact-us/ VYRE] is a CMS development company with a &amp;quot;contact us&amp;quot; hCard&lt;br /&gt;
* [http://www.lefdal.cc/info.php Alf Kåre Lefdal] uses hCard in the markup of his contact information&lt;br /&gt;
* [http://www.pignwhistle.com.au/ Pig N Whistle, a chain of pubs in Brisbane, Australia] is using hcard to mark up all the contact pages for its outlets and head office&lt;br /&gt;
* [http://kollitsch.de/ Patrick Kollitsch] has built his personal Profil as hCard&lt;br /&gt;
* [http://www.hbs.edu/faculty/dspar/ Harvard Business School] has hCards on their faculty pages&lt;br /&gt;
* [http://openmikes.org/ openmikes.org] uses hCards for open mike venue addresses in its listing detail pages.&lt;br /&gt;
* [http://www.intertecnollc.com/ InterTecno, LCC] publishes an hCard on the home page and contact page.&lt;br /&gt;
* [http://canaltcm.com/ver/sobre-tcm Turner Classic Movies TCM Spanish website] has published contact details as a hCard&lt;br /&gt;
* [http://rejuvenation.com/ Rejuvenation] is now using hCard for contact information.&lt;br /&gt;
* [http://www.mattash.com/contact/ Matthew Ash] uses the hCard in his contacts section.&lt;br /&gt;
* [http://yarmouthguide.com/business.php Yarmouth Guide] uses hCard for each business details page.&lt;br /&gt;
* [http://www.merchantcircle.com MerchantCircle] has embedded an hCard in every one of their 15+ million US business listings.&lt;br /&gt;
&lt;br /&gt;
===Examples with some problems===&lt;br /&gt;
&lt;br /&gt;
Entries may be moved here if there's a problem with the way hCards are used on the page concerned. If the page is yours, and you want to improve it, see the [[hcard-faq|hCard FAQ]], or raise any queries on [[hcard-issues|hCard Issues]] or [[mailing-lists#microformats-discuss|the mailing list]], where people will be happy to help you. &lt;br /&gt;
&lt;br /&gt;
* IBM is embracing microformats. The [http://www.ibm.com/contact/employees/ IBM Employee Directory] now returns hCards in its query results. Also see the [http://www.ibm.com/shortcuts/ Shortcuts Podcast].&lt;br /&gt;
**Invalid - no &amp;lt;code&amp;gt;fn&amp;lt;/code&amp;gt;; &amp;lt;code&amp;gt;adr&amp;lt;/code&amp;gt; has no children.&lt;br /&gt;
* Spotstor.com eg - [http://spotstor.com/] uses hCard on profile pages (where user has elected to show contact information).&lt;br /&gt;
* [http://soap.stanford.edu/ Stanford Online Accessibility Program] has implemented hCard on every page&lt;br /&gt;
**positioned off screen via CSS [[User:AndyMabbett|Andy Mabbett]] 15:09, 9 Apr 2007 (PDT)&lt;br /&gt;
* [http://www.belkin.com/pressroom/releases/uploads/10_09_06SportCommand.html Belkin Press Release] - All Belkin  press releases since October 2006 use hCard and vCard for company contact info.&lt;br /&gt;
**One of the three hCards in invalid (no &amp;quot;fn&amp;quot;) [[User:AndyMabbett|Andy Mabbett]] 16:50, 2 Apr 2007 (PDT)&lt;br /&gt;
* [http://www.rayberndtson.com/en/worldwide-offices/ Ray &amp;amp; Berndtson], a global recruitment firm, are listing all of their offices worldwide as hCards, e.g [http://www.rayberndtson.com/en/worldwide-offices/western-europe/united-kingdom/ UK offices].&lt;br /&gt;
** All invalid: no &amp;quot;fn&amp;quot;. [[User:AndyMabbett|Andy Mabbett]] 07:05, 31 Mar 2007 (PDT)&lt;br /&gt;
* The imprint of [http://www.hsg-kl.de/impressum/index.php Hohenstaufen Gymnasium Kaiserslautern]&lt;br /&gt;
** No &amp;lt;code&amp;gt;adr&amp;lt;/code&amp;gt;. [[User:AndyMabbett|Andy Mabbett]] 12:10, 3 Mar 2007 (PST)&lt;br /&gt;
* [http://www.alexa.com Alexa Internet] marked up its [http://www.alexa.com/site/company/managers managers' page] with hCard.&lt;br /&gt;
**Person's job title within &amp;quot;fn&amp;quot;. [[User:AndyMabbett|Andy Mabbett]]&lt;br /&gt;
* [http://www.naturalengland.org.uk/press/default.htm Natural England] (new UK government agency, formed 2006-10-01). &lt;br /&gt;
** No &amp;quot;fn&amp;quot; - which makes it invalid.&lt;br /&gt;
*[http://drop-off.co.uk G3:2] uses hCard with geo tags in the copyright and on the about me page&lt;br /&gt;
** Address data is hidden using CSS. &lt;br /&gt;
* [http://zdnet.co.uk/misc/contact/ ZDnet Contact Us Page] supports [[hcard|hCard]].&lt;br /&gt;
** by [http://www.subtleasafish.com/ James Myers] and [http://www.fromthefrontend.co.uk/2006/11/23/zdnet-uses-microformats/ David Long]&lt;br /&gt;
**Images and e-mail addresses are hidden; telephone numbers do not comply with [http://en.wikipedia.org/wiki/E.123 E.123]&lt;br /&gt;
* [http://gbraad.nl/ Gerard Braad] has published an example on his [http://gbraad.nl/site/?p=profile profile] page that is almost consistent with his original [http://gbraad.nl/files/gbraad.vcf vCard] file. Also progress is made for transforming his [http://files.gbraad.nl/foaf.rdf FoaF] file to a hCard encoded representation (also done for my spouse:[http://spouse.gbraad.nl/site/?p=profile Yong Yuan])&lt;br /&gt;
** (2005-09-27) PASSED, PASSED&lt;br /&gt;
** WARNINGS&lt;br /&gt;
*** uses 'n given-name' and 'n family-name' instead of nesting the given- and family- names inside the 'n'&lt;br /&gt;
*** has one 'tel' value with a bunch of values stuffed in&lt;br /&gt;
*** probably more problems --[[User:RyanKing|RyanKing]] 17:19, 5 Jan 2006 (PST)&lt;br /&gt;
* [http://kinrowan.net/ Cori Schlegel] [http://kinrowan.net/blog/wp/archives/2005/07/08/a-problem-with-the-structured-blogging-plug-in-for-wordpress/ discusses how he has updated] [http://kinrowan.net/blog/contact his contact page with hCard]&lt;br /&gt;
** INVALID - using 'prefix' instead of 'honorific-prefix' and type's in classnames (in both adr and tel) and has two photo's (the second could be 'logo') --[[User:RyanKing|RyanKing]] 15:15, 5 Jan 2006 (PST)&lt;br /&gt;
* The good ship [http://styrheim.com/test/leonid.html Leonid Miloslavskiy] spotted in the North Atlantic&lt;br /&gt;
** INVALID  --[[User:RyanKing|RyanKing]] 00:50, 27 Oct 2005 (PDT)&lt;br /&gt;
*** class=&amp;quot;family&amp;quot; should probably be family-name&lt;br /&gt;
*** the &amp;quot;n&amp;quot; property is missing and the &amp;quot;n&amp;quot; optimization can't be applied&lt;br /&gt;
*** the first geo propery is empty, the second one is invalid (i.e., it doesn't contain lat/long)&lt;br /&gt;
* [http://landsbank.fo/#hCard Landsbanki Føroya]&lt;br /&gt;
** INVALID - using embedded RDF/XML invalidly&lt;br /&gt;
* [http://chrischerry.name/ Chris Cherry's contact page with his hCard]&lt;br /&gt;
** &amp;lt;strike&amp;gt;WARNING - uses class=&amp;quot;cell&amp;quot; instead of &amp;amp;lt;span class=&amp;quot;type&amp;quot;&amp;amp;gt;cell&amp;amp;lt;/span&amp;amp;gt;&amp;lt;/strike&amp;gt; Fixed -- [[User:Seriph|Chris Cherry]] 19:54, 15 Sep 2006 (PST)&lt;br /&gt;
* [http://www.bath.ac.uk/contact/ University of Bath] Person Finder results are encoded with hCards so you can easily create a vCard from any result. &lt;br /&gt;
** ERROR - attempt to use Implied-N optimization where that's not possible. --[[User:RyanKing|RyanKing]] 14:29, 5 Jan 2006 (PST)&lt;br /&gt;
** Error appears for external users only. Won't be fixed any time soon. -- [[User:PhilWilson|PhilWilson]] 00:03, 28 Jan 2006 (GMT)&lt;br /&gt;
* [http://richi.co.uk/blog/2005/12/structured-blogging.html Richi Jennings] has put up his attempt&lt;br /&gt;
** INVALID, missing &amp;quot;fn&amp;quot;--[[User:RyanKing|RyanKing]] 12:47, 5 Jan 2006 (PST)&lt;br /&gt;
* [http://www.yellowpencil.com/contact/ Yellow Pencil] Using microformats to present company contact information&lt;br /&gt;
** First hcard has empty &amp;quot;fn&amp;quot; and no &amp;quot;n&amp;quot;. &amp;quot;fn&amp;quot; should be with &amp;quot;org&amp;quot; -- [[User: ScottReynen |ScottReynen]] 21:29, 19 Jun 2006 (CST)&lt;br /&gt;
&lt;br /&gt;
=== Reviewed Examples ===&lt;br /&gt;
Reviewed New Examples which are fine can be moved here to indicate that they've been reviewed. Or take the next step and note which type of example in the wild each of these are, and then please move them to the &amp;quot;Grouped Examples&amp;quot; sectionl&lt;br /&gt;
&lt;br /&gt;
* [http://vcardplus.info/show.asp?uid=Z9959-06323 Greg Bays], the author of vCardPlus! has made his sites vCard display page hCard complaint. &lt;br /&gt;
* [http://www.nfwebsolutions.com/ New Frontier Web Solutions] uses hCard on their front page along with a link pointing to Brian Suda's [http://suda.co.uk/projects/X2V/get-vcard?uri=http://www.nfwebsolutions.com/ X2V].&lt;br /&gt;
* [http://shiftingpixel.com/about/the-artist shifting pixel photoblog] has published an hCard.&lt;br /&gt;
* [http://thoughtport.blogspot.com/ Aiden Kenny] hasn't published his hCard yet, but he has [http://thoughtport.blogspot.com/2005/07/elemental-particles-of-web.html published his hCard icon]: http://photos1.blogger.com/blogger/4224/444/320/AK-Hcard-icon.gif&lt;br /&gt;
* [http://thedredge.org Andy Hume] uses hCards to mark-up the names and URLs of commentors on his blog, e.g. his [http://thedredge.org/2005/06/using-hcards-in-your-blog/ blog post on &amp;quot;Using hCards in your blog&amp;quot;]. &lt;br /&gt;
* [http://www.bidclix.com/ BidClix]'s [http://www.bidclix.com/AboutContact.html Contact BidClix] page has it's ''contact info'' marked up with an hCard.&lt;br /&gt;
* [http://suda.co.uk/ Brian Suda] has managed to embed a photo in [http://suda.co.uk/contact/ his hCard] through the [http://www.ietf.org/rfc/rfc2397.txt data URI scheme] by converting the image to BASE64 code. View the Source to see how this is accomplished. [http://suda.co.uk/projects/X2V/get-vcard.php?uri=http%3A//suda.co.uk/contact/ The X2V link] will extract the image and encode it for a vCard which will be displayed in some address book applications.&lt;br /&gt;
** Inspired by this I thought to try the same for SVG at [http://barefoot-ceramics.com/find Barefoot] ...&lt;br /&gt;
** &amp;amp;lt;img class=&amp;quot;photo&amp;quot; style=&amp;quot;display:none;&amp;quot; src=&amp;quot;data:image/svg+xml;text,&amp;amp;lt;?xml version='1.0' encoding='UTF-8' standalone='no'?&amp;amp;gt;&amp;amp;lt;svg xmlns:svg='http://www.w3.org/2000/svg' xmlns='http://www.w3.org/2000/svg' version='1.0' width='50' height='80' id='svg3957'&amp;amp;gt;&amp;amp;lt;defs id='defs3959' /&amp;gt;&amp;amp;lt;path d='M 28.91433,...32.192802 z' style='fill:#cc4d00;fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:0.625;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1' id='path9551' /&amp;amp;gt;&amp;amp;lt;/svg&amp;amp;gt;&amp;quot; alt=&amp;quot;Barefoot&amp;quot;&amp;amp;gt;&lt;br /&gt;
** Does it work?? Well it parses OK. Some automated tools replace the &amp;amp;lt; with %3C (etc., e.g. Brian Suda's vCard form). Unfortunately Kontact (KDE contacts tool) doesn't handle SVG as a vCard photo or logo format - I don't know if this is a standard. It seems it could work and maybe even does somewhere. Maybe the text field needs to be Base64 encoded? ... see [http://slashdot.org/~pbhj/journal/142382 pbhj's slashdot journal] for a bit more on this.&lt;br /&gt;
* [http://cinematreasures.org Cinema Treasures] uses hCard to markup venue information for 10,000+ movie theaters.&lt;br /&gt;
* [http://www.w3.org/People/Connolly/events/ Dan Connolly's index of events and talks] has hCards for many of the people he has met at those events. In Mar 2006, he moved a bunch of hotel contact info from his PDA to this page; it's now up to 32 hCards.&lt;br /&gt;
* [http://doncrowley.blogspot.com/ Don Crowley] has published [http://www.crowley.nl/hcard.html his hCard] as well as a nifty hCard button: http://www.crowley.nl/images/hcard.png&lt;br /&gt;
* [http://loadaveragezero.com/hnav/contact.php Douglas W. Clifton] added all types of contact information&lt;br /&gt;
* [http://eventful.com Eventful] publishes all of its venue information pages with embedded hCards.&lt;br /&gt;
* [http://www.iowamilitaryveteransband.com/members/ Iowa Military Veterans Band Contacts] - 95 hCards [http://weblog.randomchaos.com/archive/2005/10/24/Microformats/ marked up by Scott Reynen]&lt;br /&gt;
* [http://JackWolfgang.blogspot.com Jack L. Wolfgang II] has [http://jack.randomata.com/resume/ converted the addresses in his resume to hCards].&lt;br /&gt;
* [http://www.efas.fupl.asso.fr/efas/_Mathieu-Drouet_.html Mathieu Drouet] and [http://www.efas.fupl.asso.fr/efas/_Annie-Leger_.html Annie Leger] both have hCards&lt;br /&gt;
* [http://www.oliverbrown.me.uk/ Oliver Brown] has published his hCard.&lt;br /&gt;
* [http://www.paradigmproductions.org/contact/ Paradigm Productions] published a vCard as a &amp;lt;code&amp;gt;ul&amp;lt;/code&amp;gt; (marked up by [http://www.linkingarts.com/ Peter Jacobson])&lt;br /&gt;
* [http://www.splintered.co.uk/ Patrick H. Lauke] has marked up [http://www.splintered.co.uk/about/ his contact info with hCard].&lt;br /&gt;
* [http://blah Paul Schreiber has published his hCard on [http://paulschreiber.com/about/?contact his about page].&lt;br /&gt;
* [http://paulschreiber.com/blog/ Paul Schreiber]'s [http://concerts.shrub.ca/ Sunnyvale House Concerts] site publishes hCards for upcoming artists, as well as an hCard for the page itself.  In addition the [http://concerts.shrub.ca/shows Past Shows] page contains hCards for all past artists.&lt;br /&gt;
* [http://www.paulmichaelsmith.com/blog/hcard.htm Paul Smith] has created an hCard page which is Human Readable, and a link to X2V passing the same hCard page to generate a vCard.&lt;br /&gt;
* [http://www.windley.com/archives/2005/07/hcards_trying_o.shtml Phil Windley has published] [http://phil.windley.org/hcard.html his hCard].&lt;br /&gt;
* [http://www.go-curiosity.com/about.htm Piercarlo Slavazza] has published an hCard.&lt;br /&gt;
* [http://zooibaai.nl/ Rob Mientjes] has published his hCard on [http://zooibaai.nl/about/ his about page].&lt;br /&gt;
* [http://rbach.priv.at/Contact Robert Bachmann] has published his hCard and [http://rbach.priv.at/Images/hcard a button].&lt;br /&gt;
* [http://blah Scott Reynen has published his hCard on [http://www.randomchaos.com/document.php?source=scott_reynen his profile page].&lt;br /&gt;
* [http://www.stackframe.com/ StackFrame, LLC] has published [http://www.stackframe.com/people/ employee] and [http://www.stackframe.com/contact/ general] contact information as hCards.&lt;br /&gt;
* [http://www.wolfsreign.com Steven Ametjan] has published his hCard on [http://www.wolfsreign.com/about/ his about page].&lt;br /&gt;
* [http://tantek.com/microformats/2005/syndicate/speakers-list.html Syndicate - Speaker List] as a set of hCards&lt;br /&gt;
* [http://tagcamp.org/index.cgi?ContactList TagCamp contact list]&lt;br /&gt;
* [http://www.deadringerart.com/ The Brothers McDowell] have hCards at their Contact page.&lt;br /&gt;
* [http://twinsparc.com/ Twinsparc] put an hCard in the header and footer of all their pages.&lt;br /&gt;
* [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 Conference speakers page marked up with hCard]&lt;br /&gt;
* [http://we05.com/ Web Essentials 05] marked up all their [http://we05.com/presenters.cfm presenters with hCard].&lt;br /&gt;
* [http://www.uoguelph.ca/directory/ The University of Guelph] includes hCard info in its directory.&lt;br /&gt;
* [http://www.echildcare.com.au/ The Australian Child Care Index] has over 3000 entries listing child care services across Australia - and every single one is marked up with an hCard!&lt;br /&gt;
* [http://www.cadforless.com/partners/ CADforless, Inc.] we listed our partners using hCard&lt;br /&gt;
* [http://avon.com/ Avon] - publishes all 40,000+ Avon representatives' contact info with hCard.&lt;br /&gt;
* [http://flock.com/about Flock About] page supports hCard microformat.&lt;br /&gt;
** by [[implementations#Flock|Flock]]&lt;br /&gt;
* [http://www.iowamilitaryveteransband.com/members/ Iowa Military Veterans Band]&lt;br /&gt;
* [http://www.nature.com/ Nature homepage], uses [[XOXO]].&lt;br /&gt;
** by [[implementations#Nature Publishing Group|Nature Publishing Group]]&lt;br /&gt;
* [http://concerts.shrub.ca/shows Sunnyvale House Concerts] supports hCard and [[hcalendar|hCalendar]].&lt;br /&gt;
* [http://www.bath.ac.uk/ University of Bath] [http://www.bath.ac.uk/contact/ Person Finder] supports hCard, e.g. see [http://www.bath.ac.uk/person/760874 Mrs A Smith] page.&lt;br /&gt;
* [http://www.monster-prague.cz/ Monster Prague Openings] supports hCard, e.g. home page, contact list to come.&lt;br /&gt;
&lt;br /&gt;
== Grouped Examples ==&lt;br /&gt;
This section organizes examples into several rough categories as follows. If an example fits in more than one cateogry, use the *last* matching category in this list that matches the specific hCard example(s) in the wild that you are trying to categorize.&lt;br /&gt;
# '''Individuals''' - one card per person, perhaps sort alphabetically by &amp;quot;family-name&amp;quot;.  People with their own hCards (typically) on their own site.&lt;br /&gt;
# '''Organizations''' - one card per organization, alphabetical by &amp;quot;fn&amp;quot;.  Organizations with their own hCard(s) (typically) on their own site.&lt;br /&gt;
# '''Institutions''' - which list more than one person, with a count estimating the # of hCards, e.g. 40k for Avon. Also indicate complexity of information supplied, eg. just name+number vs. complete details.  Alphabetically sorted by &amp;quot;org&amp;quot; with perhaps a few individuals listed in a single sub-bullet, comma delimited, sorted by &amp;quot;family-name&amp;quot;.&lt;br /&gt;
# '''Online Profiles''' - which host profiles for more than one person, with a count estimating the # of hCards, e.g. 10m+ for Flickr.com.  Alphabetically sorted by &amp;quot;fn&amp;quot; with perhaps a few individuals listed in a single sub-bullet, comma delimited, sorted by &amp;quot;family-name&amp;quot;.&lt;br /&gt;
# '''Online Venues''' - which provide listings for businesses or organizations, with a count estimating the # of venues, e.g. ~10k for Upcoming.org. Alphabetically sorted by service/site name, with perhaps a few specific venues listed in a single sub-bullet, comma delimited, sorted by &amp;quot;fn&amp;quot;.&lt;br /&gt;
# '''Speakers Listings''' - event sites' speakers pages where the speakers are marked up with hCard.  Sort by date, sub-grouped by year.  Most recent first.  Perhaps a few individuals listed in a single sub-bullet each event, comma delimited, sorted by &amp;quot;family-name&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
In addition there is a separate &amp;quot;UTF8 Examples&amp;quot; section that can be used to put another link to any hCard examples in the wild which exercise various non-ASCII7 / non-english characters for various property values.&lt;br /&gt;
&lt;br /&gt;
As each section itself become quite large (we might be there already, once we sort through the above &amp;quot;Reviewed Examples&amp;quot;), it will probably be moved to a separate page, leaving its heading here in place, and replacing its contents here with a link to the separate page and perhaps a stats summary.&lt;br /&gt;
&lt;br /&gt;
=== Individuals ===&lt;br /&gt;
* [http://dbaron.org/ David Baron]'s home page is marked up with hCard.&lt;br /&gt;
* [http://tantek.com/ Tantek Çelik]'s home page includes an inline author hCard at the bottom of the page.&lt;br /&gt;
* [http://blogs.msdn.com/cwilso/ Chris Wilson] has an hCard for himself on [http://blogs.msdn.com/cwilso/about.aspx his about page].&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
=== Organizations ===&lt;br /&gt;
* [http://technorati.com Technorati] (3)&lt;br /&gt;
** [http://technorati.com/about/ about], [http://technorati.com/press/ press], and [http://technorati.com/about/contact.html contact] pages are marked up with hCard and have &amp;quot;Add to Address Book&amp;quot; links that use the [http://feed.technorati.com/contacts/ Technorati Contacts Feed service].&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
=== Institutions ===&lt;br /&gt;
* [http://technorati.com/about/staff.html Technorati's Staff page] has hCards for its employees (~31)&lt;br /&gt;
** E.g. [http://technorati.com/about/staff.html?s=adam_hertz#adam_hertz Adam Hertz], [http://technorati.com/about/staff.html?s=matthew_levine#matthew_levine Matthew Levine], [http://technorati.com/about/staff.html?s=ryan_king#ryan_king Ryan King], [http://technorati.com/about/staff.html?s=david_sifry#david_sifry David Sifry], etc.&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
=== Online Profiles ===&lt;br /&gt;
* See [[hcard-supporting-profiles]].&lt;br /&gt;
&lt;br /&gt;
=== Online Venues ===&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
=== Speakers Listings ===&lt;br /&gt;
==== 2007 ====&lt;br /&gt;
* ...&lt;br /&gt;
==== 2006 ====&lt;br /&gt;
* ...&lt;br /&gt;
==== 2005 ====&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
===UTF8 Examples===&lt;br /&gt;
These examples all contain one or more characters in UTF8 that are outside the ASCII7 range and make for excellent test cases to make sure you are handling UTF8 properly throughout your hCard parsing and transforming. And especially if you are generating vCards, these test cases will help you make sure you are generating UTF8 vCards in such a way that can be recognized by UTF8 supporting vCard applications.&lt;br /&gt;
&amp;lt;!-- &lt;br /&gt;
&lt;br /&gt;
    Newest at top, please &lt;br /&gt;
&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
* Various Wikipedia-EN articles, e.g. the &amp;quot;nickname&amp;quot; in: [http://en.wikipedia.org/wiki/Noyabrsk Noyabrsk] (Russian), [http://en.wikipedia.org/wiki/Thessaloniki Thessaloniki] (Greek), [http://en.wikipedia.org/wiki/Kyoto Kyoto] (Japanese) and [http://en.wikipedia.org/wiki/Beijing Beijing] (Chinese)&lt;br /&gt;
* [http://sphinx.net.ru/author/ Dmitry Dzhus] embedded his UTF8 encoded hCard with russian characters in «Author» page of his website.&lt;br /&gt;
* [http://tantek.com/ Tantek's Thoughts] encodes Çelik as inline UTF8.&lt;br /&gt;
* [http://uk.wikipedia.org/wiki/%D0%93%D0%B5%D1%82%D1%8C%D0%BC%D0%B0%D0%BD_%D0%92%D0%B0%D0%B4%D0%B8%D0%BC_%D0%9F%D0%B5%D1%82%D1%80%D0%BE%D0%B2%D0%B8%D1%87 Vadym Hetman] (Wikipedia-UK (Ukranian))&lt;br /&gt;
&lt;br /&gt;
===Non-HTML examples===&lt;br /&gt;
* [http://dannyayers.com/misc/microformats/hcard-svg Danny Ayers' SVG hCard demo]&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
{{hcard-related-pages}}&lt;/div&gt;</summary>
		<author><name>Trovster</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=events/2006-09-08-brighton-microformats-picnic&amp;diff=8418</id>
		<title>events/2006-09-08-brighton-microformats-picnic</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=events/2006-09-08-brighton-microformats-picnic&amp;diff=8418"/>
		<updated>2006-09-06T13:08:15Z</updated>

		<summary type="html">&lt;p&gt;Trovster: /* Attending */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Brighton Microformats Picnic =&lt;br /&gt;
&lt;br /&gt;
Because it looks like the weather is going to be good for d.Construct, let's get together in the sunshine and chat about microformats while munching on sandwiches.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Details ==&lt;br /&gt;
&lt;br /&gt;
;Date: Friday, September 8th&lt;br /&gt;
;Time: 12:45 - 14:00&lt;br /&gt;
;Location: Pavilion Gardens, Brighton.&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
The picnic will take place in the Pavilion Gardens, Brighton on September 8th from 12:45 to 2pm.&lt;br /&gt;
&lt;br /&gt;
There's no set agenda. Depending on who shows up, we might be talking about the basics of microformats, or the nitty-gritty of implementations, or both. Everyone is welcome to attend. The picnic is being organised by [http://adactio.com/ Jeremy Keith] who will be more than happy to lead the discussion.&lt;br /&gt;
&lt;br /&gt;
== Attending ==&lt;br /&gt;
&lt;br /&gt;
Please add your name here if you think you'll be able to come along. If there's enough interest, maybe we can organise a delivery of sandwiches.&lt;br /&gt;
&lt;br /&gt;
* [http://adactio.com/ Jeremy Keith] - I'll be speaking at d.Construct right before the lunch break so I'll announce the picnic on stage.&lt;br /&gt;
* [http://fberriman.com Frances Berriman]&lt;br /&gt;
* [http://www.trovster.com Trevor Morris]&lt;br /&gt;
* William Lawrence - [[User:Veeliam|veeliam]] 23:25, 17 Aug 2006 (PDT)&lt;br /&gt;
&lt;br /&gt;
== Blog Posts ==&lt;br /&gt;
&lt;br /&gt;
== Photos ==&lt;br /&gt;
&lt;br /&gt;
If you come to the picnic and take photos, add links to them here.&lt;/div&gt;</summary>
		<author><name>Trovster</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hcalendar&amp;diff=7791</id>
		<title>hcalendar</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hcalendar&amp;diff=7791"/>
		<updated>2006-07-25T11:29:35Z</updated>

		<summary type="html">&lt;p&gt;Trovster: /* Examples in the wild */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt; hCalendar &amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
hCalendar is a simple, open, distributed calendaring and events format, based on the  iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]), suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. hCalendar is one of several open [[microformats|microformat]] standards.&lt;br /&gt;
&lt;br /&gt;
Want to get started with writing an [[hcalendar|hCalendar]] event?  Use the [http://microformats.org/code/hcalendar/creator hCalendar creator] to write up an event and publish it.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Specification ==&lt;br /&gt;
&lt;br /&gt;
; Editor : [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc])&lt;br /&gt;
; Authors : [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]&lt;br /&gt;
: [http://suda.co.uk/ Brian Suda]&lt;br /&gt;
&lt;br /&gt;
=== Copyright ===&lt;br /&gt;
{{MicroFormatCopyrightStatement2004}}&lt;br /&gt;
&lt;br /&gt;
=== Patents ===&lt;br /&gt;
{{MicroFormatPatentStatement}}&lt;br /&gt;
&lt;br /&gt;
=== Inspiration and Acknowledgments ===&lt;br /&gt;
Thanks to:&lt;br /&gt;
* Adam Bosworth for leading the [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation] which brought together a critical mass of interested parties.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
The iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]), has been broadly interoperably implemented (e.g. Apple's &amp;quot;iCal&amp;quot; application built into MacOSX).&lt;br /&gt;
&lt;br /&gt;
In addition, bloggers often discuss events on their blogs -- upcoming events, writeups of past events, etc.  With just a tad bit of structure, bloggers can discuss events in their blog(s) in such a way that spiders and other aggregators can retrieve such events, automatically convert them to iCalendar, and use them in any iCalendar application or service.&lt;br /&gt;
&lt;br /&gt;
This specification introduces the '''hCalendar''' format, which is a 1:1 representation of the aforementioned iCalendar standard, in semantic XHTML.  Bloggers can both embed hCalendar events directly in their web pages, and style them with CSS to make them appear as desired.  In addition, hCalendar enables applications to retrieve information about such events directly from web pages without having to reference a separate file.&lt;br /&gt;
&lt;br /&gt;
== Semantic XHTML Design Principles ==&lt;br /&gt;
&lt;br /&gt;
{{semantic-xhtml-design-principles}}&lt;br /&gt;
&lt;br /&gt;
== Format ==&lt;br /&gt;
&lt;br /&gt;
=== In General ===&lt;br /&gt;
&lt;br /&gt;
The iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]) forms the basis of hCalendar.&lt;br /&gt;
&lt;br /&gt;
Note: the editor and authors of this specification are tracking the [http://lists.osafoundation.org/pipermail/ietf-calsify/ &amp;quot;iCal-Basic&amp;quot; effort] and intend to base the core hCalendar profile on iCal-Basic. See references for a link to the current draft.&lt;br /&gt;
&lt;br /&gt;
The basic format of hCalendar is to use iCalendar object/property names in lower-case for class names, and to map the nesting of iCalendar objects directly into nested XHTML.&lt;br /&gt;
&lt;br /&gt;
=== More Semantic Equivalents ===&lt;br /&gt;
&lt;br /&gt;
However, for some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:&lt;br /&gt;
* &amp;lt;code&amp;gt;URL&amp;lt;/code&amp;gt; in iCalendar becomes  &amp;lt;code&amp;gt;&amp;lt;a class=&amp;quot;url&amp;quot; href=&amp;quot;...&amp;quot;&amp;gt;...&amp;lt;/a&amp;gt;&amp;lt;/code&amp;gt; inside the element with &amp;lt;code&amp;gt;class=&amp;quot;vevent&amp;quot;&amp;lt;/code&amp;gt; in hCalendar.&lt;br /&gt;
* &amp;lt;code&amp;gt;ATTENDEE&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;CONTACT&amp;lt;/code&amp;gt;, and &amp;lt;code&amp;gt;ORGANIZER&amp;lt;/code&amp;gt; in iCalendar may be represented by an [[hcard|hCard]] in hCalendar .&lt;br /&gt;
* A named &amp;lt;code&amp;gt;LOCATION&amp;lt;/code&amp;gt; (potentially with an address and/or geo) in iCalendar may be represented by a nested [[hcard|hCard]] in hCalendar.  Similarly, an address &amp;lt;code&amp;gt;LOCATION&amp;lt;/code&amp;gt; may be represented by an [[adr]], and a geo (latitude and longitude) &amp;lt;code&amp;gt;LOCATION&amp;lt;/code&amp;gt; may be represented by a [[geo]].&lt;br /&gt;
* &amp;lt;code&amp;gt;UID&amp;lt;/code&amp;gt; in iCalendar simply becomes another semantic applied to a specific URL for an hCalendar event.&lt;br /&gt;
&lt;br /&gt;
=== Singular vs. Plural Properties ===&lt;br /&gt;
&lt;br /&gt;
For properties which are singular (e.g. &amp;quot;N&amp;quot; and &amp;quot;FN&amp;quot; from vCard), the first descendant element with that class should take effect, any others being ignored.&lt;br /&gt;
&lt;br /&gt;
For properties which can be plural (e.g. &amp;quot;TEL&amp;quot; from vCard), each class instance should create a instance of that property.  Plural properties with subtypes (e.g. TEL with WORK, HOME, CELL from vCard) can be optimized to share a common element for the property itself, with each instance of subtype being an appropriately classed descendant of the property element.&lt;br /&gt;
&lt;br /&gt;
==== Plural Properties Singularized ====&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Human vs. Machine readable ===&lt;br /&gt;
If an &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; element is used for a property, then the '&amp;lt;code&amp;gt;title&amp;lt;/code&amp;gt;' attribute of the &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; element is the value of the property, instead of the contents of the element,  which instead provide a human presentable version of the value.  This specification recommends that such &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; elements be used for the following iCalendar properties:&lt;br /&gt;
* DTSTART, DTEND, DURATION, RDATE, RRULE&lt;br /&gt;
&lt;br /&gt;
== Example ==&lt;br /&gt;
&lt;br /&gt;
Here is a sample event in an iCalendar:&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
BEGIN:VCALENDAR&lt;br /&gt;
PRODID:-//XYZproduct//EN&lt;br /&gt;
VERSION:2.0&lt;br /&gt;
BEGIN:VEVENT&lt;br /&gt;
URL:http://www.web2con.com/&lt;br /&gt;
DTSTART:20051005&lt;br /&gt;
DTEND:20051008&lt;br /&gt;
SUMMARY:Web 2.0 Conference&lt;br /&gt;
LOCATION:Argent Hotel\, San Francisco\, CA&lt;br /&gt;
END:VEVENT&lt;br /&gt;
END:VCALENDAR&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
and an equivalent event in hCalendar format with various elements optimized appropriately.  See [[hcalendar-example1-steps]] for the derivation.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;a class=&amp;quot;url&amp;quot; href=&amp;quot;http://www.web2con.com/&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;summary&amp;quot;&amp;gt;Web 2.0 Conference&amp;lt;/span&amp;gt;: &lt;br /&gt;
  &amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;2005-10-05&amp;quot;&amp;gt;October 5&amp;lt;/abbr&amp;gt;-&lt;br /&gt;
  &amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;2005-10-08&amp;quot;&amp;gt;7&amp;lt;/abbr&amp;gt;,&lt;br /&gt;
 at the &amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt;Argent Hotel, San Francisco, CA&amp;lt;/span&amp;gt;&lt;br /&gt;
 &amp;lt;/a&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
which could be displayed as:&lt;br /&gt;
&lt;br /&gt;
[http://www.web2con.com/ Web 2.0 Conference: October 5-7, at the Argent Hotel, San Francisco, CA]&lt;br /&gt;
&lt;br /&gt;
Note 1: The product information is not necessary since hCalendar is an interchange format.  When transforming hCalendar back into iCalendar, the transforming engine should add its own product ID.&lt;br /&gt;
&lt;br /&gt;
Note 2: A surrounding &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;span class=&amp;quot;vcalendar&amp;quot;&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; element is optional, and is left out as such.  It is optional since the context of a vcalendar is implied when a vevent is encountered.  The implied context/scope is that of the document.  Authors may explicitly use elements with class=&amp;quot;vcalendar&amp;quot; to wrap sets of vevents that all belong to the same calendar, e.g. when publishing multiple calendars on the same page.&lt;br /&gt;
&lt;br /&gt;
Note 3: The version information is unnecessary in hCalendar markup directly since the version will be defined by the profile of hCalendar that is used/referred to in the 'profile' attribute of the &amp;lt;head&amp;gt; element.&lt;br /&gt;
&lt;br /&gt;
Note 4: ISO8601 dates (required by iCalendar) are not very human friendly.  In addition, the year is often understood implicitly by humans from the context.  Thus &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; elements are used to simultaneously provide a human friendly date and/or time in the visible contents of the element, while placing the respective machine parsable comprehensive ISO8601 datetime in the 'title' attribute.&lt;br /&gt;
The notation YYYY-MM-DD should be used for better readability.&lt;br /&gt;
&lt;br /&gt;
Note 5: The difference between the DTEND ISO8601 date (2005-10-08) and the human readable date (7) is NOT a mistake.  [http://lists.osafoundation.org/pipermail/ietf-calsify/2005-September/000769.html DTEND is exclusive], meaning, that the event ends just before the DTEND. Thus for events which start on one day and end on another day, the DTEND date must be specified as the day after the day that a human would say is the last day of the event.&lt;br /&gt;
&lt;br /&gt;
Note 6: The location in this example contains implicit structure (venue name, city, state) which could be marked up explicitly as an [[hcard|hCard]].  See [http://microformats.org/wiki/hcalendar-brainstorming#hCard_locations hCalendar brainstorming: hCard locations] for a informative explanation of how to do this.&lt;br /&gt;
&lt;br /&gt;
See [[hcalendar-examples]] for more hCalendar examples&lt;br /&gt;
&lt;br /&gt;
== Examples in the wild ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
The following sites have implemented hCalendar, and thus are a great place to start for anyone looking for examples &amp;quot;in the wild&amp;quot; to try parsing, indexing, organizing etc.  If events on your pages are marked up with hCalendar, feel free to add it to the top of this list.  Once the list grows too big, we'll make a separate wiki page.&lt;br /&gt;
&lt;br /&gt;
=== New Examples ===&lt;br /&gt;
Please add new examples to this section.&lt;br /&gt;
* [http://www.geekinthepark.co.uk Geek in the Park] uses hCalendar for the event information. -- by [[User:Trovster|trovster]]&lt;br /&gt;
* [http://www.besancon.fr/ official site of Besançon (France)] for its events&lt;br /&gt;
* [http://2006.dconstruct.org/schedule/ Conference schedule for d.Construct 2006] is published using hCalendar.&lt;br /&gt;
* [http://local.yahoo.com Yahoo Local] now supports hCalendar&lt;br /&gt;
* We used hcalendar for the [http://www.fuckparade.org/flyer/2006/ F’parade flyer 2006], a counter demonstration to the Love Parade in Berlin, alas two issues arose: the '''Firefox tails extension''' doesn't get a summary when it's an alt-text in an image. Also the '''default charset''' when creating an iCal file through the [http://feeds.technorati.com/events/http://www.fuckparade.org/flyer/2006/ Technorati feed] is UTF-8, but our website is ISO-8859-15. Is there a way to define a different charset, or why doesn’t the API respect the charset given by the website in the first place (in our case it’s in the HTPP header, in the XML declaration, ''and'' the meta tag)?&lt;br /&gt;
* [http://www.harper-adams.ac.uk/press/events.cfm Harper Adams University College] uses hCalendar to mark up all University events on the Homepage and Events Calendar page.&lt;br /&gt;
* [http://www.capital.edu/ Capital University] uses hCalendar on multiple pages to provide feeds of events, relevant to page content&lt;br /&gt;
* [http://www.thesession.org/events/ The Session events] uses hCalendar to mark up concerts, festivals and workshops related to Irish traditional music.&lt;br /&gt;
* [http://rubyandrails.org/usergroups/newcastle ncl.rb] uses hCalendar to mark up new meetings.&lt;br /&gt;
* [http://www.worldcupkickoff.com/ World Cup KickOff] where you can download and keep all the fixtures you are interested in so you will never miss a single game of the 2006 football World Cup!&lt;br /&gt;
** This link was on the [http://www.lifehacker.com/software/sports/world-cup-start-times-for-ical-etc-175393.php Lifehackers site] and made its way to the yahoo news site:&lt;br /&gt;
&lt;br /&gt;
Mon May 22, 4:00 PM ET&lt;br /&gt;
The World Cup, one of the world's most watched sporting events, is almost upon us. If you've ever tried to follow your favorite team through the Cup you know that it can sometimes be difficult to know when they're on. World Cup Kickoff can help.&lt;br /&gt;
&lt;br /&gt;
World Cup KickOff is all you will ever need for knowing all the match details for the upcoming World Cup 2006. Whether you use your mobile phone, MS Outlook, Apple iCal or Mozilla Calendar, you can download and keep all the fixtures you are interested in so you will never miss a single game!&lt;br /&gt;
ADVERTISEMENT&lt;br /&gt;
&lt;br /&gt;
Next tip? We'll show you how to get up at 2 AM to watch your matches. ;0) Thanks to Tom for the tip!&lt;br /&gt;
&lt;br /&gt;
* [http://gross.org.za/calendar GROSSUG Calendar] - Uses hCalendar to mark up meetings and other events.&lt;br /&gt;
* [http://www.webanalyticsassociation.org/en/calendarevents/search.asp  Web Analytics Association] - hCalendar microformat is in place on all Tendenci sites on the calendar events search page and consolidated list page.&lt;br /&gt;
* [http://www.tendenci.com/en/calendarevents/search.asp Tendenci Calendar Events] with hCalendar&lt;br /&gt;
* [http://www.argolon.com/2006/04/17/web20-conference-in-dublin/ Web2.0 Conference in Dublin] hCalendar event&lt;br /&gt;
* [http://www.meetup.com/ Meetup.com] has marked up [http://www.meetup.com/cities/us/ny/new_york city event calendars], [http://photo.meetup.com/100/events/ group event lists], and [http://www.meetup.com/ signed-in homepages] with hCalendar.&lt;br /&gt;
* [http://ukwindsurfing.com/ ukwindsurfing.com] has marked upcoming events with hCalendar, and the [http://ukwindsurfing.com/events/ events page] in a table.&lt;br /&gt;
* [http://ocono.com/ ocono.com] has marked up it's &amp;quot;Upcoming Events&amp;quot; list with hCalendar.&lt;br /&gt;
* [http://www.austinbloggers.org/ Austin Bloggers] has marked up their &amp;quot;Upcoming Events&amp;quot; box with hCalendar ([http://www.austinbloggers.org/blog/a/001123.html announcement]).&lt;br /&gt;
* Ning's cloneable Group app has [[hcalendar|hCalendar]] markup on its [http://group.ning.com/index.php?controller=event&amp;amp;action=list event calendar] and [http://group.ning.com/index.php?controller=event&amp;amp;action=view&amp;amp;id=727220 event detail] pages.&lt;br /&gt;
* [http://tantek.com/microformats/2006/03-01-TechPlenAgenda.html Agenda: W3C Technical Plenary Day, March 1 2006] has [[hcard|hCard]] and [[hcalendar|hCalendar]] markup. ([http://www.w3.org/2006/03/01-TechPlenAgenda.html original here]).&lt;br /&gt;
* The National Arbor Day Foundation has started using hCalendars for their [http://arborday.org/programs/conferences/communityforestry/index.cfm upcoming] [http://arborday.org/programs/conferences/hazardtrees-treeplanting/ conferences].&lt;br /&gt;
* [http://www.stateofflux.com/ State of Flux street art site] has started adding events in hCalendar format&lt;br /&gt;
* The [http://barcamp.org/#BarCamps BarCamp home page lists upcoming BarCamps marked up with hCalendar] and even has a &amp;quot;Subscribe...&amp;quot; link.&lt;br /&gt;
* [http://www.w3.org/2005/12/allgroupoverview.html 2006 W3C Technical Plenary Week] has marked up the schedule and events for the week with hCalendar.&lt;br /&gt;
* [http://www.code4lib.org/2006/schedule code4lib Conference 2006 Schedule] is marked up with hCalendar as [http://www.code4lib.org/node/65 announced on their blog].&lt;br /&gt;
* [http://grouper.ieee.org/groups/754 IEEE 754 Working Group] - trying hCalendar for upcoming meetings.&lt;br /&gt;
* [http://www.pehuen.org/node/494  Elecciones 2005 Chile] - the first spanish language hCalendar event found in the wild.&lt;br /&gt;
* [http://www.codewitch.org/it/2005/11/17/no-creative-commons-no-party/ Giocolando » No Creative Commons? No Party!] is marked up with hCalendar&lt;br /&gt;
* [http://www.cmprofessionals.org/events/calendar.html CM Pros Events Calendar] by Bob Doyle&lt;br /&gt;
* [http://www.midgard-project.org/community/events/ Midgard CMS Event calendar] - as [http://bergie.iki.fi/blog/new-event-calendar-for-midcom.html blogged by Henri Bergius] &lt;br /&gt;
* [http://www.iowamilitaryveteransband.com/schedule/ Iowa Military Veterans Band Schedule] - hCalendar markup [http://weblog.randomchaos.com/archive/2005/10/24/Microformats/ added by Scott Reynen]&lt;br /&gt;
* [http://www.funfairgames.net/weblog/posts/00000011.html Upcoming events on Jason A.R. Moody Amusements Weblog] posted by Jason Moody on 15 Oct 2005. [http://www.funfairgames.net/weblog/index.html His weblog] in general has hCalendar events posted inside the blog posts.&lt;br /&gt;
* [http://tantek.com/microformats/2005/syndicate/tracks-sessions-schedule.html Syndicate - Tracks &amp;amp;amp; Sessions]&lt;br /&gt;
* [http://tantek.com/microformats/2005/web2/program.html Web 2.0 Conference schedule page marked up with hCalendar]&lt;br /&gt;
* [http://www.thisiscmon.com/ C'MON] is a rock band from Canada, and their [http://www.thisiscmon.com/shows/ tour dates] have been marked up by [http://www.d2digitalmedia.com/ Ray Dickman] with hCalendar.&lt;br /&gt;
* [http://ifreebusy.com/ ifreebusy.com] will display freebusy information using hCalendar. See this [http://ifreebusy.com/neiljensen/freebusy/ example].&lt;br /&gt;
* [http://we05.com/ Web Essentials 05] has marked up their [http://we05.com/program.cfm program schedule table with hCalendar], using the 'axis' and 'headers' attributes.&lt;br /&gt;
* [http://www.asdvbonaparte.nl/ ASDV Bonaparte] is a Dutch debating society. Their events calendar has been marked up with the hCalendar conventions.&lt;br /&gt;
* [http://chocnvodka.blogware.com/blog Suw Charman] has marked up [http://suw.org.uk/archives/category/events/ her events] with hCalendar.&lt;br /&gt;
* [http://www.blogbusinesssummit.com/ Blog Business Summit] has published their [http://www.blogbusinesssummit.com/details.htm event details] marked up with hCalendar.&lt;br /&gt;
* [http://eventful.com Eventful.com] publishes all events with hCalendar and venues with [[hcard|hCard]].  Took them only 15 minutes to implement both! Their Atom feeds also contain hCalendar/hCard.&lt;br /&gt;
* [http://upcoming.org Upcoming.org] publishes all events and lists of events with hCalendar.  Took them only an hour to add hCalendar support to the site.&lt;br /&gt;
* The [http://laughingsquid.com/squidlist/calendar/ Laughing Squid Calendar] events, [http://laughingsquid.com/squidlist/calendar/9949/2005/5/9 e.g. this party], now supports hCalendar.&lt;br /&gt;
* [http://paulschreiber.com/ Paul] Schreiber's [http://concerts.shrub.ca/ Sunnyvale House Concerts] site publishes hCalendar event information for upcoming concerts.  In addition the [http://concerts.shrub.ca/shows Past Shows] page contains hCalendar events for all past concerts.&lt;br /&gt;
* [http://www.complexspiral.com/ Complex Spiral Consulting], both in the &amp;quot;Events&amp;quot; box on left side, and the separate [http://www.complexspiral.com/events/ Events page]. &lt;br /&gt;
* [http://tantek.com/log Tantek's Thoughts], specifically the &amp;quot;Events&amp;quot; roll in the right-most column.&lt;br /&gt;
* [http://suda.co.uk/projects/holidays/ Lesser Known Holidays], a list of holidays on [http://suda.co.uk suda.co.uk] that can be imported via iCal and hCal so you can compare actual transformation versus intended.&lt;br /&gt;
* [http://norman.walsh.name/2005/itinerary/ Norm Walsh's travel schedule] use hCalendar as well as GRDDL.&lt;br /&gt;
* [http://www.policyawareweb.org/2005/ftf2/paw-mtg Policy Aware Web (PAW) Project Meeting] uses hCalendar to record date-related decisions, and uses a vtodo microformat to record action items.&lt;br /&gt;
* The [http://lufgi4.informatik.rwth-aachen.de Laboratory for Dependable Distributed Systems] publishes it's [http://lufgi4.informatik.rwth-aachen.de/cfps list of notable CfPs on dependability and security] with hCalendar-todo elements.&lt;br /&gt;
* The [http://laughingsquid.com/laughing-squid-10th-anniversary-party/ Laughing Squid 10th Anniversary Party] has an hcalendar page.&lt;br /&gt;
* SPRACI has hcalendar versions of its nightlife/clubbing/gigs/festivals listings for many cities worldwide - eg: [http://www.spraci.com/listhcalendar.php?parea=sydney&amp;amp;category=all Events in Sydney] (check the [http://www.spraci.com/api/ API] pages in the faq section of [http://www.spraci.com/ SPRACI] for more info about the area/city keywords and category tags to use to get data for your city/categories&lt;br /&gt;
* WWF-Australia events calendars: [http://wwf.org.au/act/events/ What's on], [http://wwf.org.au/act/volunteer/ Volunteer]&lt;br /&gt;
* [http://rubyholic.com rubyholic] uses hCalendar to publish calendars for ruby groups.&lt;br /&gt;
* [http://www.bath.ac.uk/whats-on/ University of Bath What's On] uses hCalendar on individual event pages&lt;br /&gt;
* The [http://www.kiez-ev.de/ Kiez] is a small cinema and has published its [http://www.kiez-ev.de/programm program] marked up with hCalendar&lt;br /&gt;
&lt;br /&gt;
=== Examples with some problems ===&lt;br /&gt;
* [http://www.bokle.de/ s'Bokle] is a German music pub. Their events calendar has been marked up with hCalendar.&lt;br /&gt;
** improper use of rrule --[[User:RyanKing|RyanKing]] 16:04, 6 Jan 2006 (PST)&lt;br /&gt;
* [http://plan9.tryphon.org/nancy/list Plan9] - Uses hCalendar to mark up events !&lt;br /&gt;
** dtstart/dtend are implemented on span element [[User:TomArmitage|Tom Armitage]] June 23, 2006&lt;br /&gt;
* [http://www.socaltech.com socalTECH] is a news and information site. Their front page event listing is marked up with hCalendar.&lt;br /&gt;
** dtstart/dtend implemented on span element [[User:TomArmitage|Tom Armitage]] June 23, 2006&lt;br /&gt;
* [http://www.multipack.co.uk The Multipack] features a vevent for the next meeting information.&lt;br /&gt;
** dtstart/dtend are implemented on em element [[User:TomArmitage|Tom Armitage]] June 23, 2006&lt;br /&gt;
* [http://paulschreiber.com/ Paul] Schreiber's [http://iceoasis.shrub.ca/ unofficial schedule site] publishes hCalendar information for upcoming hockey games at [http://www.iceoasis.com/ Ice Oasis]&lt;br /&gt;
** dtstart/dtend are implemented on td element [[User:TomArmitage|Tom Armitage]] June 23, 2006&lt;br /&gt;
&lt;br /&gt;
- whilst Tails parses dtstart/dtend on &amp;lt;em&amp;gt;any&amp;lt;/em&amp;gt; element, technically it really needs to be on abbr. Technorati Microformats Search only looks for the title element on &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; tags, for instance.&lt;br /&gt;
&lt;br /&gt;
== Implementations ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
The following implementations have been developed which either generate or parse hCalendars. If you have an hCalendar implementation, feel free to add it to the top of this list.  Once the list grows too big, we'll make a separate wiki page.&lt;br /&gt;
&lt;br /&gt;
=== Authoring ===&lt;br /&gt;
Implementations you can use to author, create, and publish hCalendar events.&lt;br /&gt;
&lt;br /&gt;
==== Blogging and CMS tools ====&lt;br /&gt;
;Midgard CMS : [http://www.midgard-project.org/documentation/net-nemein-calendar/ Midgard CMS - net.nemein.calendar] - as [http://bergie.iki.fi/blog/new-event-calendar-for-midcom.html blogged by Henri Bergius] &lt;br /&gt;
&lt;br /&gt;
;Drupal module : [http://hybernaut.com/upcoming-hcal Drupal Upcoming.org syndication module emits hCalendar]&lt;br /&gt;
;MovableType and WordPress plug-ins : [http://structuredblogging.org/formats.php StructuredBlogging] is a set of plugins  [http://structuredblogging.org/structuredblogging-wp-latest.zip for  WordPress] and [http://structuredblogging.org/structuredblogging-wp-latest.zip for MovableType] that supports embedding hCalendar and other microformats in templates and blog posts.&lt;br /&gt;
;Textpattern plug-in : [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCalendar and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].&lt;br /&gt;
&lt;br /&gt;
==== Browser scripts and plug-ins ====&lt;br /&gt;
Browser plugins that work with existing authoring tools:&lt;br /&gt;
; Any browser with javascript and a little bit of CSS : [http://microformats.org/code/hcalendar/creator microformats.org hCalendar creator]  (see also original: [http://theryanking.com/ Ryan King] has an [http://theryanking.com/microformats/hcalendar-creator.html hCalendar creator]).&lt;br /&gt;
; Firefox Greasemonkey user script hCalendar creator : [http://www.decafbad.com/blog/2005/06/08/greasemonkey_magic magic_hcalendar Greasemonkey user script by Les Orchard] - allows easy form entry of an event into any textarea, e.g. into a blog post text area.&lt;br /&gt;
; Firefox Greasemonkey user script hCalendar to Google Calendar: [http://torrez.us Elias Torres] has created a [http://torrez.us/archives/2006/04/13/431/ simple script] that will parse hCalendar entries and create a link to add event to [http://www.google.com/calendar/ Google Calendar's] service. Based on [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats George's] and [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats Arve's] work.&lt;br /&gt;
&lt;br /&gt;
==== Desktop Authoring Tools ====&lt;br /&gt;
;Dreamweaver Extension : [http://www.webstandards.org/action/dwtf/microformats/ Extension suite] for Dreamweaver 8 from the [http://webstandards.org/ Web Standards Project].&lt;br /&gt;
;xfy : &lt;br /&gt;
In [https://www.xfytec.com/community/ xfy Community], there are some hCalendar implementations.&lt;br /&gt;
&lt;br /&gt;
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=15&amp;amp;lid=25 hCalendar via RSS] parses an RSS feed, retrieves XHTML documents linked from that feed, and syndicates hCalendars into a calendar view.&lt;br /&gt;
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=19&amp;amp;lid=23 hCalendar Marker XVCD] helps to mark up an event information in XHTML document with hCalendar. &lt;br /&gt;
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=15&amp;amp;lid=17 Simple RDF Calendar XVCD] is a schedule tool which uses RDF Calendar format. It also converts RDF Calendar format to iCalendar and hCalendar format.&lt;br /&gt;
&lt;br /&gt;
=== Search and Discovery ===&lt;br /&gt;
&lt;br /&gt;
* [http://kitchen.technorati.com/search Technorati Microformats Search] indexes [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] as [http://tantek.com/log/2006/05.html#d31t1802 announced by Tantek]. &lt;br /&gt;
&lt;br /&gt;
=== Conversion and Import ===&lt;br /&gt;
Implementations you can use to importing into a Calendar Application, typically by converting hCalendar to iCalendar/vCalendar.&lt;br /&gt;
&lt;br /&gt;
==== Web Services ====&lt;br /&gt;
These return iCalendar (.ics) and other calendar formats for easy importing into typical calendar programs or other processing.&lt;br /&gt;
* [http://feeds.technorati.com/events Technorati Events Feed service] uses X2V library to parse hCalendar and return iCalendar (.ics).  Note friendly URL, e.g. http://feeds.technorati.com/events/http%3A//microformats.org&lt;br /&gt;
* [http://suda.co.uk/projects/X2V/ X2V] parses hCalendar and produces a .ics (iCalendar) stream.  Note: needs to be updated to track changes in the specification as they occur.&lt;br /&gt;
* [http://lifelint.net/ Life Lint Parser] parses hCalendar and produces .ics, .rdf and debugging information and attempts to be more fully compliant to the iCal standard than previous implementations.  It can be used in the same manner as X2V.  Can output iCal (w optional Outlook 2002 compat), and RDF.&lt;br /&gt;
* [http://spanningsalesforce.com/ Spanning Salesforce] produces hCalendar-enabled RSS feeds and .ics calendars from Salesforce.com.&lt;br /&gt;
&lt;br /&gt;
==== Firefox Greasemonkey Plugins ====&lt;br /&gt;
* [http://george.hotelling.net/90percent/ George] has built a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script that detects hCalendar events and allows users to easily add them to their calendar application(s)].&lt;br /&gt;
* [http://inside.glnetworks.de/ Martin Rehfeld] has updated the work of [http://blogmatrix.blogmatrix.com/ David Janes] and produced a [[Greasemonkey]] [http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ script] that finds many microformat elements, including hCalendar events, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. The hCalendar to vCalendar conversion is done internally within the script. ''This will work with FireFox 1.5+/GreaseMonkey 0.6.4+ now.''&lt;br /&gt;
&lt;br /&gt;
==== Aggregators ====&lt;br /&gt;
* [http://placenamehere.com/mf/nnwextract/ Extract Microformats] is a script for NetNewsWire that supports extracting hCard and hCalendar data in blog posts (via technorati service). Written by [[User:ChrisCasciano|Chris Casciano]]&lt;br /&gt;
* [http://kula.jp/software/endo/screenshots/ Endo], an OS X aggregator, supports discovering hCal and adding those events to iCal. Look at the last screenshot at the bottom of the page.&lt;br /&gt;
&lt;br /&gt;
=== Browsing ===&lt;br /&gt;
Implementations that detect, display and otherwise highlight hCalendar events in pages.&lt;br /&gt;
&lt;br /&gt;
* In [http://www.xfytec.com/community/ xfy Community], there are some hCalendar implementations. &amp;quot;hCalendar via RSS&amp;quot; parses an RSS feed, retrieves XHTML documents linked from that feed, and syndicates hCalendars into a calendar view.&lt;br /&gt;
* [http://web.mit.edu/glasser/www/JSCalendar/ JSCalendar] parses hCalendar and produces a displayable HTML table/CSS-based calendar.&lt;br /&gt;
&lt;br /&gt;
==== Firefox extension ====&lt;br /&gt;
[http://blog.codeeg.com/tails-firefox-extension/ Tails is a Firefox Extension] that will display the presence of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage.&lt;br /&gt;
&lt;br /&gt;
==== Flock extension ====&lt;br /&gt;
[http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar&lt;br /&gt;
&lt;br /&gt;
=== Libraries ===&lt;br /&gt;
Open source libraries of hCalendar parsers and other related code for building hCalendar implementations.&lt;br /&gt;
; Javascript : [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats simple hCalendar parser] by [http://virtuelvis.com/ Arve Bersvendsen]&lt;br /&gt;
; PHP : [http://randomchaos.com/microformats/base/ Microformat Base] is an open-source PHP microformat aggregation crawler, currently recognizing hreview, hcalendar, and hcard.&lt;br /&gt;
; Ruby : [http://opensource.reevoo.com/2006/03/08/release-uformats-12/ uformats] is a ruby library that can parse [[hCalendar]], [[hCard]], [[hReview]] and [[rel-tag]]&lt;br /&gt;
; XSLT :&lt;br /&gt;
* X2V is available as an XSLT library&lt;br /&gt;
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] by [[User:DanC]] includes  toICal.xsl and test materials; it works much like xhtml2vcal.xsl in X2V. See also: [http://www.w3.org/2002/12/cal/ RDF Calendar workspace] with icalendar test materials.&lt;br /&gt;
&lt;br /&gt;
=== Potential implementations ===&lt;br /&gt;
&lt;br /&gt;
These are open source projects that could be potentially enhanced to support hCalendar.&lt;br /&gt;
&lt;br /&gt;
* [http://www.k5n.us/webcalendar.php?topic=About WebCalendar]&lt;br /&gt;
* [http://phpicalendar.net/documentation/index.php?title=Main_Page PHP iCalendar]&lt;br /&gt;
* [http://www.vcalendar.org VCalendar]&lt;br /&gt;
* Investigation: [http://wiki.mozilla.org/Calendar_Talk:Lightning#hCalendar_publish_and_subscribe_support Mozilla Calendar / Lightning / Sunbird hCalendar support discussion]&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
=== Normative References ===&lt;br /&gt;
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]&lt;br /&gt;
* [[hcard|hCard]]&lt;br /&gt;
* [http://www.ietf.org/rfc/rfc2445.txt iCalendar RFC2445]&lt;br /&gt;
&lt;br /&gt;
=== Informative References ===&lt;br /&gt;
* [http://w3.org/TR/REC-CSS1 CSS1]&lt;br /&gt;
* [http://tantek.com/log/2004/09.html#hcalendar hCalendar term introduced and defined on the Web, 20040930]&lt;br /&gt;
* [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation, 20040911]&lt;br /&gt;
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]&lt;br /&gt;
* [http://www.ietf.org/internet-drafts/draft-royer-ical-basic-04.txt iCal-Basic draft 04]&lt;br /&gt;
* Contributed from http://developers.technorati.com/wiki/hCalendar&lt;br /&gt;
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]&lt;br /&gt;
&lt;br /&gt;
==== Specifications That Use hCalendar ====&lt;br /&gt;
* [[hreview|hReview]]&lt;br /&gt;
&lt;br /&gt;
==== Similar Work ====&lt;br /&gt;
* [http://lists.osafoundation.org/pipermail/ietf-calsify/ IETF-calsify archives]&lt;br /&gt;
* [http://www.softwarestudio.org/iCal/2445Issues.html RFC2445 Issues List]&lt;br /&gt;
* [http://ietf.webdav.org/calsify/ CALSIFY WG Links And Resources]&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
* [http://microformats.org/code/hcalendar/creator hCalendar creator] ([[hcalendar-creator-feedback|feedback]]) - create your own hCalendar events.&lt;br /&gt;
* [[hcalendar-authoring|hCalendar authoring]] - learn how to add hCalendar markup to your existing events.&lt;br /&gt;
* [[hcalendar-faq|hCalendar FAQ]] - If you have any questions about hCalendar, check here, and if you don't find answers, add your questions!&lt;br /&gt;
* [[hcalendar-parsing|hCalendar parsing]] - Normatively details of how to parse hCalendar.&lt;br /&gt;
* [[hcalendar-issues|hCalendar issues]] - Please add any issues with the specification to the issues page.&lt;br /&gt;
* [[hcalendar-profile|hCalendar profile]] - The XMDP profile for hCalendar&lt;br /&gt;
&lt;br /&gt;
This 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.&lt;br /&gt;
&lt;br /&gt;
* [[hcalendar-brainstorming|hCalendar Brainstorming]] - where we are keeping our brainstorms and other explorations relating to hCard&lt;br /&gt;
* [[hcalendar-tests|hCalendar tests]] - a wiki page with actual embedded hCalendar events to try parsing.&lt;br /&gt;
* [[icalendar-implementations|iCalendar implementations]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Further Reading ==&lt;br /&gt;
* [http://www.livejournal.com/users/jwz/444651.html jwz - Hula] (required reading)&lt;br /&gt;
* [http://www.jwz.org/doc/groupware.html Groupware Bad by Jamie Zawinski] crystalizes the reason for hCalendar ('''emphasis''' added):&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;quot;Right now people can do that by publishing .ics files, but  it's not trivial to do so, and it's work on the part of other people  to look at them. '''If it's not HTML hanging off our friend's home page  that can be viewed in any browser on a public terminal in a library,  the bar to entry is too high and it's useless.'''&amp;quot;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* [http://muddybranch.thejkgroup.com/ Jason Klemow's blog]&lt;br /&gt;
* [http://weblog.infoworld.com/udell/2006/01/11.html#a1368 Moving forward with microformats] by [http://weblog.infoworld.com/udell Jon Udell] provides an hCalendar example and some discussion.&lt;br /&gt;
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page] and the [http://technorati.com/tags/hcalendar hCalendar tag]&lt;/div&gt;</summary>
		<author><name>Trovster</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hatom&amp;diff=7719</id>
		<title>hatom</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hatom&amp;diff=7719"/>
		<updated>2006-07-25T11:28:58Z</updated>

		<summary type="html">&lt;p&gt;Trovster: /* Examples in the wild */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt; hAtom 0.1 &amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
hAtom is a microformat for content that can be syndicated, primarily but not exclusively weblog postings. hAtom is based on a subset of the [http://www.atomenabled.org/ Atom] syndication format. hAtom is one of several [[microformats]] open standards.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
== Draft Specification ==&lt;br /&gt;
&lt;br /&gt;
=== Editor/Author ===&lt;br /&gt;
* [http://blogmatrix.blogmatrix.com/ David Janes], [http://www.blogmatrix.com BlogMatrix, Inc.]&lt;br /&gt;
&lt;br /&gt;
=== Contributors ===&lt;br /&gt;
* [http://members.optusnet.com.au/benjamincarlyle/benjamin/blog/ Benjamin Carlyle]&lt;br /&gt;
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]&lt;br /&gt;
&lt;br /&gt;
=== Copyright ===&lt;br /&gt;
{{MicroFormatCopyrightStatement2005}}&lt;br /&gt;
&lt;br /&gt;
=== Patents ===&lt;br /&gt;
{{MicroFormatPatentStatement}}&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
hAtom is a [[microformat]] for identifying semantic information in weblog posts and practically any other place [http://www.atomenabled.org/ Atom] may be used, such as news articles. hAtom content is easily added to most blogs by simple modifications to the blog's template definitions.&lt;br /&gt;
&lt;br /&gt;
== Semantic XHTML Design Principles ==&lt;br /&gt;
{{semantic-xhtml-design-principles}}&lt;br /&gt;
&lt;br /&gt;
== Format ==&lt;br /&gt;
=== In General ===&lt;br /&gt;
The [http://atomenabled.org/developers/syndication/#person Atom Syndication Format] provides the conceptual basis for this microformat, with the following caveats:&lt;br /&gt;
&lt;br /&gt;
* Atom provides a lot more functionality that we need for a &amp;quot;blog post&amp;quot; microformat, so we've taken the minimal number of elements needed.&lt;br /&gt;
* the &amp;quot;logical&amp;quot; model of hAtom is that of Atom. If there is a conflict, Atom should be taken as correct.&lt;br /&gt;
* the &amp;quot;physical&amp;quot; model of hAtom -- the actual writing of elements -- is a lot more varied than Atom provides for, due to the variety of ways weblogs are actually produced in the wild. The hAtom microformat provides a number of rules for &amp;quot;bridging the gap&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Schema ===&lt;br /&gt;
Schema elements are based on the Atom nomenclature and follow the microformat pattern of prefixing a unique identifier (in this case, '&amp;lt;code&amp;gt;h&amp;lt;/code&amp;gt;') on the outermost container elements -- the Feed or Entry. The parts of this microformat are based on analysis of many weblog, bulletin board and media posts and can be read [[blog-post-brainstorming#Discovered_Elements]].&lt;br /&gt;
&lt;br /&gt;
The hAtom schema consists of the following:&lt;br /&gt;
&lt;br /&gt;
* hfeed ('''&amp;lt;code&amp;gt;hfeed&amp;lt;/code&amp;gt;'''). optional.&lt;br /&gt;
* hentry ('''&amp;lt;code&amp;gt;hentry&amp;lt;/code&amp;gt;'''). &lt;br /&gt;
** '''&amp;lt;code&amp;gt;entry-title&amp;lt;/code&amp;gt;'''. required. text.&lt;br /&gt;
** '''&amp;lt;code&amp;gt;entry-content&amp;lt;/code&amp;gt;'''. optional (see field description). text.&lt;br /&gt;
** '''&amp;lt;code&amp;gt;entry-summary&amp;lt;/code&amp;gt;'''. optional. text.&lt;br /&gt;
** '''&amp;lt;code&amp;gt;updated&amp;lt;/code&amp;gt;'''. required using [[datetime-design-pattern]].&lt;br /&gt;
** '''&amp;lt;code&amp;gt;published&amp;lt;/code&amp;gt;'''. optional using [[datetime-design-pattern]].&lt;br /&gt;
** '''&amp;lt;code&amp;gt;author&amp;lt;/code&amp;gt;'''. required using '''[[hcard|hCard]]'''.&lt;br /&gt;
** '''&amp;lt;code&amp;gt;bookmark&amp;lt;/code&amp;gt;''' (permalink). optional, using '''[[rel-bookmark]]'''.&lt;br /&gt;
** tags. optional. keywords or phrases, using '''[[rel-tag]]'''.&lt;br /&gt;
&lt;br /&gt;
Some required elements have defaults if missing, see below.&lt;br /&gt;
&lt;br /&gt;
=== Field and Element Details ===&lt;br /&gt;
&lt;br /&gt;
===== Feed =====&lt;br /&gt;
* a Feed element is identified by the class name &amp;lt;code&amp;gt;hfeed&amp;lt;/code&amp;gt;&lt;br /&gt;
* a Feed element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.1.1 Atom feed]&lt;br /&gt;
* the Feed element is optional and, if missing, is assumed to be the page&lt;br /&gt;
* hAtom documents MAY have multiple Feed elements&lt;br /&gt;
&lt;br /&gt;
===== Feed Category =====&lt;br /&gt;
* a Feed Category element is identified by [[rel-tag]]&lt;br /&gt;
* a Feed MAY have a Feed Category&lt;br /&gt;
* a Feed Category element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.2 Atom category] inside a [http://www.atomenabled.org/developers/syndication/#optionalFeedElements feed]&lt;br /&gt;
* Feed Category elements MUST appear inside a Feed element but not inside an Entry element&lt;br /&gt;
* the [[rel-tag]] &amp;lt;code&amp;gt;href&amp;lt;/code&amp;gt; encodes the atom &amp;lt;code&amp;gt;category:term&amp;lt;/code&amp;gt;; the link text defines the atom &amp;lt;code&amp;gt;category:label&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Entry =====&lt;br /&gt;
* an Entry element is identified by class name &amp;lt;code&amp;gt;hentry&amp;lt;/code&amp;gt;&lt;br /&gt;
* an Entry element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.1.2 Atom entry]&lt;br /&gt;
* any microformat content inside a &amp;lt;code&amp;gt;&amp;amp;lt;blockquote&amp;gt;&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;&amp;amp;lt;q&amp;gt;&amp;lt;/code&amp;gt; element within the Entry is should not be considered part of the Entry.&lt;br /&gt;
: ''This allows quoting other microformated data without worry of corrupting the model''&lt;br /&gt;
&lt;br /&gt;
===== Entry Category =====&lt;br /&gt;
* an Entry Category element is identified by [[rel-tag]]&lt;br /&gt;
* an Entry MAY have an Entry Category&lt;br /&gt;
* an Entry Category element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.2 Atom category] inside an [http://www.atomenabled.org/developers/syndication/#optionalEntryElements entry]&lt;br /&gt;
* the [[rel-tag]] &amp;lt;code&amp;gt;href&amp;lt;/code&amp;gt; encodes the atom &amp;lt;code&amp;gt;category:term&amp;lt;/code&amp;gt;; the link text defines the atom &amp;lt;code&amp;gt;category:label&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Entry Title =====&lt;br /&gt;
* an Entry Title element is identified by the class name &amp;lt;code&amp;gt;entry-title&amp;lt;/code&amp;gt;&lt;br /&gt;
* an Entry SHOULD have an Entry Title&lt;br /&gt;
* an Entry Title element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.14 Atom entry title]&lt;br /&gt;
* if the Entry Title is missing, use&lt;br /&gt;
** the first &amp;lt;code&amp;gt;&amp;amp;lt;h#&amp;gt;&amp;lt;/code&amp;gt; element in the Entry, or&lt;br /&gt;
** the &amp;lt;code&amp;gt;&amp;amp;lt;title&amp;gt;&amp;lt;/code&amp;gt; of the page, if there is no enclosing Feed element, or&lt;br /&gt;
** assume it is the empty string&lt;br /&gt;
&lt;br /&gt;
===== Entry Content =====&lt;br /&gt;
* an Entry Content element is identified by class name &amp;lt;code&amp;gt;entry-content&amp;lt;/code&amp;gt;&lt;br /&gt;
* an Entry SHOULD have Entry Content&lt;br /&gt;
* an Entry Content element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#atomContent Atom content]&lt;br /&gt;
* an Entry MAY have 0 or more Entry Content elements. The &amp;quot;logical Entry Content&amp;quot; of an Entry is the concatenation, in order of appearance, of all the Entry Contents within the Entry&lt;br /&gt;
: ''Many weblogs split content into multiple sections with a &amp;quot;Read More&amp;quot; link and javascript tricks. This is also needed in cases where Entry Titles are coded inline and are considered part of the content.''&lt;br /&gt;
* if the Entry Content is missing, assume it is the empty string&lt;br /&gt;
&lt;br /&gt;
===== Entry Summary =====&lt;br /&gt;
* an Entry Summary element is identified by class name &amp;lt;code&amp;gt;entry-summary&amp;lt;/code&amp;gt;&lt;br /&gt;
* an Entry Summary element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.13 Atom summary]&lt;br /&gt;
* an Entry MAY have 0 or more Entry Summary elements. The &amp;quot;logical Entry Summary&amp;quot; of an Entry is the concatenation, in order of appearance, of all the Entry Summarys within the Entry&lt;br /&gt;
&lt;br /&gt;
===== Entry Permalink =====&lt;br /&gt;
* an Entry Permalink element is identified by [[rel-bookmark]]&lt;br /&gt;
* an Entry SHOULD have an Entry Permalink&lt;br /&gt;
* an Entry Permalink element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.7 Atom link in an entry]&lt;br /&gt;
* if the Entry Permalink is missing, use the URI of the page; if the Entry has an &amp;quot;id&amp;quot; attribute, add that as a fragment to the page URI to distinguish individual entries&lt;br /&gt;
&lt;br /&gt;
===== Entry Updated =====&lt;br /&gt;
* an Entry Updated element is identified by class name &amp;lt;code&amp;gt;updated&amp;lt;/code&amp;gt;&lt;br /&gt;
* an Entry Updated element represents the concept of [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.15 Atom updated]&lt;br /&gt;
* an Entry SHOULD have an Entry Updated element&lt;br /&gt;
* use the [[datetime-design-pattern]] to encode the updated datetime&lt;br /&gt;
* if there is no Entry Updated element,&lt;br /&gt;
** use the Entry Published element, if present&lt;br /&gt;
** otherwise the page is invalid hAtom&lt;br /&gt;
&lt;br /&gt;
===== Entry Published =====&lt;br /&gt;
* an Entry Published element is identified by the class name &amp;lt;code&amp;gt;published&amp;lt;/code&amp;gt;&lt;br /&gt;
* an Entry Published element represents the concept of [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.9 Atom published]&lt;br /&gt;
* use the [[datetime-design-pattern]] to encode the published datetime&lt;br /&gt;
&lt;br /&gt;
===== Entry Author =====&lt;br /&gt;
* an Entry Author element is represented by class name &amp;lt;code&amp;gt;author&amp;lt;/code&amp;gt;&lt;br /&gt;
* an Entry Author element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.1 Atom author]&lt;br /&gt;
* an Entry Author element MUST be encoded in an [[hcard|hCard]]&lt;br /&gt;
* an Entry Author element SHOULD be encoded in an &amp;lt;code&amp;gt;&amp;amp;lt;address&amp;gt;&amp;lt;/code&amp;gt; element&lt;br /&gt;
* an Entry SHOULD have at least one Entry Author element&lt;br /&gt;
* an Entry MAY have more than one Entry Author elements&lt;br /&gt;
* if the Entry Author is missing&lt;br /&gt;
** find the [[algorithm-nearest-in-parent|Nearest In Parent]] &amp;lt;code&amp;gt;&amp;amp;lt;address&amp;gt;&amp;lt;/code&amp;gt; element(s) with class name &amp;lt;code&amp;gt;author&amp;lt;/code&amp;gt; and that is/are a valid [[hcard|hCard]]&lt;br /&gt;
** otherwise the entry is invalid hAtom&lt;br /&gt;
&lt;br /&gt;
=== XMDP Profile ===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;dl class=&amp;quot;profile&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;dt&amp;gt;class&amp;lt;/dt&amp;gt;&lt;br /&gt;
 &amp;lt;dd&amp;gt;&amp;lt;p&amp;gt;&lt;br /&gt;
  &amp;lt;a rel=&amp;quot;help&amp;quot; href=&amp;quot;http://www.w3.org/TR/html401/struct/global.html#adef-class&amp;quot;&amp;gt;&lt;br /&gt;
   HTML4 definition of the 'class' attribute.&amp;lt;/a&amp;gt;&lt;br /&gt;
  This meta data profile defines some 'class' attribute values (class names) &lt;br /&gt;
  and their meanings as suggested by a &lt;br /&gt;
  &amp;lt;a href=&amp;quot;http://www.w3.org/TR/WD-htmllink-970328#profile&amp;quot;&amp;gt;&lt;br /&gt;
   draft of &amp;quot;Hypertext Links in HTML&amp;quot;&amp;lt;/a&amp;gt;.&lt;br /&gt;
  &amp;lt;dl&amp;gt;&lt;br /&gt;
   &amp;lt;dt&amp;gt;hfeed&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;&lt;br /&gt;
    The concept of atom:feed from &lt;br /&gt;
    &amp;lt;a href=&amp;quot;http://www.atomenabled.org/developers/syndication/atom-format-spec.php&amp;quot;&amp;gt;The Atom Syndication Format&amp;lt;/a&amp;gt;, &lt;br /&gt;
    constrained and modified as per the &amp;lt;a href=&amp;quot;http://microformats.org/wiki/hatom&amp;quot;&amp;gt;hAtom microformat spec&amp;lt;/a&amp;gt;.&lt;br /&gt;
   &amp;lt;/dd&amp;gt;&lt;br /&gt;
   &amp;lt;dt&amp;gt;hentry&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;&lt;br /&gt;
    The concept of atom:entry from &lt;br /&gt;
    &amp;lt;a href=&amp;quot;http://www.atomenabled.org/developers/syndication/atom-format-spec.php&amp;quot;&amp;gt;The Atom Syndication Format&amp;lt;/a&amp;gt;, &lt;br /&gt;
    constrained and modified as per the &amp;lt;a href=&amp;quot;http://microformats.org/wiki/hatom&amp;quot;&amp;gt;hAtom microformat spec&amp;lt;/a&amp;gt;.&lt;br /&gt;
   &amp;lt;/dd&amp;gt;&lt;br /&gt;
   &amp;lt;dt&amp;gt;entry-title&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;&lt;br /&gt;
    The concept of atom:title inside of an atom:entry from &lt;br /&gt;
    &amp;lt;a href=&amp;quot;http://www.atomenabled.org/developers/syndication/atom-format-spec.php&amp;quot;&amp;gt;The Atom Syndication Format&amp;lt;/a&amp;gt;, &lt;br /&gt;
    constrained and modified as per the &amp;lt;a href=&amp;quot;http://microformats.org/wiki/hatom&amp;quot;&amp;gt;hAtom microformat spec&amp;lt;/a&amp;gt;.&lt;br /&gt;
   &amp;lt;/dd&amp;gt;&lt;br /&gt;
   &amp;lt;dt&amp;gt;entry-content&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;&lt;br /&gt;
    The concept of atom:content from &lt;br /&gt;
    &amp;lt;a href=&amp;quot;http://www.atomenabled.org/developers/syndication/atom-format-spec.php&amp;quot;&amp;gt;The Atom Syndication Format&amp;lt;/a&amp;gt;, &lt;br /&gt;
    constrained and modified as per the &amp;lt;a href=&amp;quot;http://microformats.org/wiki/hatom&amp;quot;&amp;gt;hAtom microformat spec&amp;lt;/a&amp;gt;.&lt;br /&gt;
   &amp;lt;/dd&amp;gt;&lt;br /&gt;
   &amp;lt;dt&amp;gt;entry-summary&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;&lt;br /&gt;
    The concept of atom:summary from &lt;br /&gt;
    &amp;lt;a href=&amp;quot;http://www.atomenabled.org/developers/syndication/atom-format-spec.php&amp;quot;&amp;gt;The Atom Syndication Format&amp;lt;/a&amp;gt;, &lt;br /&gt;
    constrained and modified as per the &amp;lt;a href=&amp;quot;http://microformats.org/wiki/hatom&amp;quot;&amp;gt;hAtom microformat spec&amp;lt;/a&amp;gt;.&lt;br /&gt;
   &amp;lt;/dd&amp;gt;&lt;br /&gt;
   &amp;lt;dt&amp;gt;bookmark&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;&lt;br /&gt;
    The concept of atom:link (without any &amp;quot;rel&amp;quot;) with an atom:entry from &lt;br /&gt;
    &amp;lt;a href=&amp;quot;http://www.atomenabled.org/developers/syndication/atom-format-spec.php&amp;quot;&amp;gt;The Atom Syndication Format&amp;lt;/a&amp;gt;, &lt;br /&gt;
    constrained and modified as per the &amp;lt;a href=&amp;quot;http://microformats.org/wiki/hatom&amp;quot;&amp;gt;hAtom microformat spec&amp;lt;/a&amp;gt;.&lt;br /&gt;
   &amp;lt;/dd&amp;gt;&lt;br /&gt;
   &amp;lt;dt&amp;gt;published&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;&lt;br /&gt;
    The concept of atom:published from &lt;br /&gt;
    &amp;lt;a href=&amp;quot;http://www.atomenabled.org/developers/syndication/atom-format-spec.php&amp;quot;&amp;gt;The Atom Syndication Format&amp;lt;/a&amp;gt;, &lt;br /&gt;
    constrained and modified as per the &amp;lt;a href=&amp;quot;http://microformats.org/wiki/hatom&amp;quot;&amp;gt;hAtom microformat spec&amp;lt;/a&amp;gt;.&lt;br /&gt;
   &amp;lt;/dd&amp;gt;&lt;br /&gt;
   &amp;lt;dt&amp;gt;updated&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;&lt;br /&gt;
    The concept of atom:updated from &lt;br /&gt;
    &amp;lt;a href=&amp;quot;http://www.atomenabled.org/developers/syndication/atom-format-spec.php&amp;quot;&amp;gt;The Atom Syndication Format&amp;lt;/a&amp;gt;, &lt;br /&gt;
    constrained and modified as per the &amp;lt;a href=&amp;quot;http://microformats.org/wiki/hatom&amp;quot;&amp;gt;hAtom microformat spec&amp;lt;/a&amp;gt;.&lt;br /&gt;
   &amp;lt;/dd&amp;gt;&lt;br /&gt;
   &amp;lt;dt&amp;gt;author&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;&lt;br /&gt;
    The concept of atom:author from &lt;br /&gt;
    &amp;lt;a href=&amp;quot;http://www.atomenabled.org/developers/syndication/atom-format-spec.php&amp;quot;&amp;gt;The Atom Syndication Format&amp;lt;/a&amp;gt;, &lt;br /&gt;
    constrained and modified as per the &amp;lt;a href=&amp;quot;http://microformats.org/wiki/hatom&amp;quot;&amp;gt;hAtom microformat spec&amp;lt;/a&amp;gt;.&lt;br /&gt;
   &amp;lt;/dd&amp;gt;&lt;br /&gt;
  &amp;lt;/dl&amp;gt;&lt;br /&gt;
 &amp;lt;/dd&amp;gt;&lt;br /&gt;
&amp;lt;/dl&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
&lt;br /&gt;
See [[hatom-examples]].&lt;br /&gt;
&lt;br /&gt;
== Examples in the wild ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
=== 0.1 hAtom implementations ===&lt;br /&gt;
* [http://www.geekinthepark.co.uk Geek in the Park] uses hAtom for the comments. -- by [[User:Trovster|trovster]]&lt;br /&gt;
* [http://www.fberriman.com fberriman.com] uses hAtom 0.1 for blog posts (wordpress loop) and hCard throughout -- by [[User:Phae|Frances Berriman]]&lt;br /&gt;
* [http://www.capital.edu Capital University] uses hAtom 0.1 to mark up the feed of latest posts by student bloggers on its home page.&lt;br /&gt;
* [http://blog.davidjanes.com Ranting and Roaring] (David Janes)&lt;br /&gt;
* [http://ChunkySoup.net/ ChunkySoup.net] has redesigned using hAtom 0.1 and hCards on the entire site -- by [[User:ChrisCasciano|Chris Casciano]]&lt;br /&gt;
* [http://sedna.spip.org/sedna/ Sedna RSS] (a feed aggregator based on SPIP, by Fil, IZO and others; GPLd sources are available at [http://zone.spip.org/trac/spip-zone/browser/_squelettes_/sedna SPIP-Zone])&lt;br /&gt;
* [http://members.optusnet.com.au/benjamincarlyle/benjamin/blog/ Sound Advice] (Benjamin Carlyle)&lt;br /&gt;
* [http://quotedprintable.com/pages/scribbish Scribbish] is a Typo theme which uses hAtom.&lt;br /&gt;
* [http://rbach.priv.at/hAtom2Atom/Changelog/ hAtom2Atom.xsl’s Changelog] is published as hAtom and Atom.&lt;br /&gt;
* [http://federali.st/ federali.st]'s webbed Federalist Papers are each marked up in hAtom.&lt;br /&gt;
&lt;br /&gt;
=== Pre 0.1 hAtom implementations ===&lt;br /&gt;
These pages conform to an older draft standard and need to be updated.&lt;br /&gt;
&lt;br /&gt;
* [http://www.myelin.co.nz/post/ Second p0st] (Phil Pearson)&lt;br /&gt;
&lt;br /&gt;
== Implementations ==&lt;br /&gt;
&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
* the [http://www.trinityanne.com/tools/extract/ Almost Universal Microformat Parser] can extract hAtom content from webpages ([http://www.trinityanne.com/tools/extract/?uri=http%3A%2F%2Fblog.davidjanes.com&amp;amp;microformat=hatom&amp;amp;submit=Submit example])&lt;br /&gt;
* the [http://www.trinityanne.com/tools/greasemonkey/microformat-action.user.js microformat-action] [[greasemonkey|Greasemonkey]] script detects hAtom content on webpages and will call the [http://www.trinityanne.com/tools/extract/ Almost Universal Microformat Parser]&lt;br /&gt;
* [http://rbach.priv.at/hAtom2Atom/ hAtom2Atom.xsl] transforms hAtom to Atom (as the name suggests.)&lt;br /&gt;
* There is now an [http://www.lukearno.com/projects/hatom2atom/ hatom2atom proxy] that uses hAtom2Atom.xsl.&lt;br /&gt;
* [http://placenamehere.com/article/185/SubscribingTohAtomFeedsWithNetNewsWire Subscribe To hAtom] is a script that provides [http://ranchero.com/netnewswire/ NetNewsWire 2.x] users with the ability to subscribe to hAtom documents as they would any other feed. by [[User:ChrisCasciano|Chris Casciano]].&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
=== Normative References ===&lt;br /&gt;
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]&lt;br /&gt;
* [http://www.atomenabled.org/ Atom]&lt;br /&gt;
* [[hcard-parsing]]&lt;br /&gt;
&lt;br /&gt;
=== Informative References ===&lt;br /&gt;
&lt;br /&gt;
==== Specifications That Use hAtom ====&lt;br /&gt;
&lt;br /&gt;
==== Similar Work ====&lt;br /&gt;
&lt;br /&gt;
* [http://rdfs.org/sioc/ Semantically-Interlinked Online Communities (SIOC) RDF Ontology]&lt;br /&gt;
&lt;br /&gt;
== Work in progress ==&lt;br /&gt;
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. There is a separate document where we are keeping our brainstorms and other explorations relating to hAtom:&lt;br /&gt;
&lt;br /&gt;
* [[blog-post-brainstorming|blog-post Brainstorming]]&lt;br /&gt;
&lt;br /&gt;
=== Version 0.1 ===&lt;br /&gt;
&lt;br /&gt;
Version 0.1 was released 28 February 2006.&lt;br /&gt;
&lt;br /&gt;
== Discussions ==&lt;br /&gt;
&lt;br /&gt;
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].&lt;br /&gt;
&lt;br /&gt;
=== Q&amp;amp;A ===&lt;br /&gt;
* If you have any questions about hAtom, check the [[hatom-faq|hAtom FAQ]], and if you don't find answers, add your questions!&lt;br /&gt;
&lt;br /&gt;
=== Issues ===&lt;br /&gt;
* Please add any issues with the specification to the separate [[hatom-issues|hAtom issues]] document.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
* [[hatom|hAtom]] - the draft proposal&lt;br /&gt;
* [[hatom-hints|hAtom Hints]] - help for implementors&lt;br /&gt;
* [[hatom-issues]] - problems? complaints? ideas? Put them here&lt;br /&gt;
* [[hatom-faq]] - knowledge base&lt;br /&gt;
* [[blog-post-brainstorming]]&lt;br /&gt;
* [[blog-post-formats]]&lt;br /&gt;
* [[blog-post-examples]]&lt;br /&gt;
* [[blog-description-format]] - how to describe a blog (as opposed to the individual entries, which is what we're doing here)&lt;/div&gt;</summary>
		<author><name>Trovster</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hcard&amp;diff=7721</id>
		<title>hcard</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hcard&amp;diff=7721"/>
		<updated>2006-07-25T11:27:43Z</updated>

		<summary type="html">&lt;p&gt;Trovster: /* Examples in the wild */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt;hCard&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
hCard is a simple, open, distributed contact information format for people, companies, and organizations, which is suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. hCard is a 1:1 representation of the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in XHTML, one of several open [[microformats|microformat]] standards.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Specification ==&lt;br /&gt;
&lt;br /&gt;
=== Editor ===&lt;br /&gt;
[http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]&lt;br /&gt;
&lt;br /&gt;
=== Authors ===&lt;br /&gt;
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]&lt;br /&gt;
* [http://suda.co.uk/ Brian Suda]&lt;br /&gt;
&lt;br /&gt;
=== Copyright ===&lt;br /&gt;
{{MicroFormatCopyrightStatement2004}}&lt;br /&gt;
&lt;br /&gt;
=== Patents ===&lt;br /&gt;
{{MicroFormatPatentStatement}}&lt;br /&gt;
&lt;br /&gt;
=== Inspiration and Acknowledgments ===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), has been broadly interoperably implemented (e.g. Apple's &amp;quot;Address Book&amp;quot; application built into MacOSX).&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
This specification introduces the '''hCard''' format, which is a 1:1 representation of the aforementioned vCard standard, in semantic XHTML.  Bloggers can both embed vCards directly in their web pages, and style them with CSS to make them appear as desired.  In addition, hCard enables applications to retrieve information about such vCards directly from web pages without having to reference a separate file.&lt;br /&gt;
&lt;br /&gt;
Use the [http://microformats.org/code/hcard/creator hCard creator], copy the HTML code it generates to your blog or website to publish your contact info.&lt;br /&gt;
&lt;br /&gt;
== Semantic XHTML Design Principles ==&lt;br /&gt;
{{semantic-xhtml-design-principles}}&lt;br /&gt;
&lt;br /&gt;
== Format ==&lt;br /&gt;
=== In General ===&lt;br /&gt;
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) forms the basis of hCard.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== More Semantic Equivalents ===&lt;br /&gt;
However, for some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:&lt;br /&gt;
* &amp;lt;code&amp;gt;URL&amp;lt;/code&amp;gt; in vCard becomes  &amp;lt;code&amp;gt;&amp;lt;a class=&amp;quot;url&amp;quot; href=&amp;quot;...&amp;quot;&amp;gt;...&amp;lt;/a&amp;gt;&amp;lt;/code&amp;gt; inside the element with &amp;lt;code&amp;gt;class=&amp;quot;vcard&amp;quot;&amp;lt;/code&amp;gt; in hCard.&lt;br /&gt;
* Similarly, &amp;lt;code&amp;gt;EMAIL&amp;lt;/code&amp;gt; in vCard becomes &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;a class=&amp;quot;email&amp;quot; href=&amp;quot;mailto:...&amp;quot;&amp;gt;...&amp;lt;/a&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
* &amp;lt;code&amp;gt;PHOTO&amp;lt;/code&amp;gt; in vCard becomes &amp;lt;code&amp;gt;&amp;lt;img class=&amp;quot;photo&amp;quot; src=&amp;quot;...&amp;quot; alt=&amp;quot;Photo of ...&amp;quot; /&amp;gt;&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;&amp;lt;object class=&amp;quot;photo&amp;quot; data=&amp;quot;...&amp;quot; type=&amp;quot;...&amp;quot;&amp;gt;Photo of ...&amp;lt;/object&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
* &amp;lt;code&amp;gt;UID&amp;lt;/code&amp;gt; in vCard simply becomes another semantic applied to a specific URL (or EMAIL) for an hCard.&lt;br /&gt;
&lt;br /&gt;
=== Singular vs. Plural Properties ===&lt;br /&gt;
&lt;br /&gt;
For properties which are singular (e.g. &amp;quot;N&amp;quot; and &amp;quot;FN&amp;quot;), the first descendant element with that class should take effect, any others being ignored.&lt;br /&gt;
&lt;br /&gt;
For properties which can be plural (e.g. &amp;quot;TEL&amp;quot;), each class instance should create a instance of that property. Plural properties with subtypes (e.g. TEL with WORK, HOME, CELL) can be optimized to share a common element for the property itself, with each instance of subtype being an appropriately classed descendant of the property element.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==== Plural Properties Singularized ====&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Human vs. Machine readable ===&lt;br /&gt;
&lt;br /&gt;
If an &amp;lt;code&amp;gt;&amp;amp;lt;abbr&amp;amp;gt;&amp;lt;/code&amp;gt; element is used for a property, then the '&amp;lt;code&amp;gt;title&amp;lt;/code&amp;gt;' attribute of the &amp;lt;code&amp;gt;&amp;amp;lt;abbr&amp;gt;&amp;lt;/code&amp;gt; element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value.  &lt;br /&gt;
&lt;br /&gt;
If an &amp;lt;code&amp;gt;&amp;amp;lt;a&amp;amp;gt;&amp;lt;/code&amp;gt; element is used for one or more properties, it must be treated as follows:&lt;br /&gt;
# For the &amp;quot;PHOTO&amp;quot; property and any other property that takes a URL as its value, the &amp;lt;code&amp;gt;href=&amp;quot;...&amp;quot;&amp;lt;/code&amp;gt; attribute provides the property value.&lt;br /&gt;
# For other properties, the element's content is the value of the property.&lt;br /&gt;
&lt;br /&gt;
If an &amp;lt;code&amp;gt;&amp;amp;lt;img&amp;amp;gt;&amp;lt;/code&amp;gt; element is used for one or more properties, it must be treated as follows:&lt;br /&gt;
# For the &amp;quot;PHOTO&amp;quot; property and any other property that takes a URL as its value, the &amp;lt;code&amp;gt;src=&amp;quot;...&amp;quot;&amp;lt;/code&amp;gt; attribute provides the property value.&lt;br /&gt;
# For other properties, the &amp;lt;code&amp;gt;&amp;amp;lt;img&amp;gt;&amp;lt;/code&amp;gt; element's '&amp;lt;code&amp;gt;alt&amp;lt;/code&amp;gt;' attribute is the value of the property.&lt;br /&gt;
&lt;br /&gt;
If an &amp;lt;code&amp;gt;&amp;amp;lt;object&amp;amp;gt;&amp;lt;/code&amp;gt; element is used for one or more properties, it must be treated as follows:&lt;br /&gt;
# For the &amp;quot;PHOTO&amp;quot; property and any other property that takes a URL as its value, the &amp;lt;code&amp;gt;data=&amp;quot;...&amp;quot;&amp;lt;/code&amp;gt; attribute provides the property value.&lt;br /&gt;
# For other properties, the element's content is the value of the property.&lt;br /&gt;
&lt;br /&gt;
=== Value excerpting ===&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;&amp;lt;code&amp;gt;value&amp;lt;/code&amp;gt;&amp;quot; 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:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;home&amp;lt;/span&amp;gt;:&lt;br /&gt;
 &amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt;+1.415.555.1212&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This hCard fragment could be displayed as:&lt;br /&gt;
&lt;br /&gt;
 home: +1.415.555.1212&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Property Exceptions ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
# '''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 &amp;lt;code&amp;gt;&amp;lt;title&amp;gt;&amp;lt;/code&amp;gt; element in (X)HTML documents) to construct the NAME property, MAY output a PROFILE value of &amp;quot;&amp;lt;code&amp;gt;VCARD&amp;lt;/code&amp;gt;&amp;quot; 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 &amp;quot;3.0&amp;quot; (without quotes) per RFC2426 Section 3.6.9.&lt;br /&gt;
&lt;br /&gt;
=== Organization Contact Info ===&lt;br /&gt;
 &lt;br /&gt;
If the &amp;quot;FN&amp;quot; and &amp;quot;ORG&amp;quot; properties have the exact same value (typically because they are set on the same element, e.g. class=&amp;quot;fn org&amp;quot;), 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 &amp;quot;N&amp;quot; property, or set it (and any sub-properties) explicitly to the empty string &amp;quot;&amp;quot;.  Thus parsers should handle the missing &amp;quot;N&amp;quot; property in this case by implying empty values for all the &amp;quot;N&amp;quot; sub-properties.&lt;br /&gt;
&lt;br /&gt;
=== Implied &amp;quot;n&amp;quot; Optimization ===&lt;br /&gt;
&lt;br /&gt;
Although vCard requires that the &amp;quot;N&amp;quot; property be present, the authors of the vCard specification (RFC 2426) themselves do not include &amp;quot;N&amp;quot; properties in their vCards near the end of the spec (p.38).  This apparent contradiction can be resolved by simply allowing the &amp;quot;FN&amp;quot; property to imply &amp;quot;N&amp;quot; property values in typical cases provided in the spec.  We do so explicitly in hCard.&lt;br /&gt;
&lt;br /&gt;
If &amp;quot;FN&amp;quot; and &amp;quot;ORG&amp;quot; are not the same (see previous section), and the value of the &amp;quot;FN&amp;quot; property is exactly two words (separated by whitespace), and there is no explicit &amp;quot;N&amp;quot; property, then the &amp;quot;N&amp;quot; property is inferred from the &amp;quot;FN&amp;quot; property.  For &amp;quot;FN&amp;quot;s with either one word see below, and for three or more, the author MUST explicitly markup the &amp;quot;N&amp;quot;, except for the organization contact info case, [http://microformats.org/wiki/hcard#Organization_Contact_Info see above] for that.&lt;br /&gt;
&lt;br /&gt;
# The content of &amp;quot;FN&amp;quot; is broken into two &amp;quot;words&amp;quot; separated by whitespace.&lt;br /&gt;
# The ''first'' word of the &amp;quot;FN&amp;quot; is interpreted as the &amp;quot;given-name&amp;quot; for the &amp;quot;N&amp;quot; property.&lt;br /&gt;
# The ''second/last'' word of the &amp;quot;FN&amp;quot; is interpreted as the &amp;quot;family-name&amp;quot; for the &amp;quot;N&amp;quot; property.&lt;br /&gt;
# Exception: If the first word ends in a &amp;quot;,&amp;quot; comma OR if the second word is a single character (optionally followed by a period &amp;quot;.&amp;quot;), then the first word (minus the comma at the end if any) is interpreted as the &amp;quot;family-name&amp;quot; and the second word is interpreted as the &amp;quot;given-name&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
This allows simplification in the typical case of people stating:&lt;br /&gt;
* given-name (space) family-name&lt;br /&gt;
* family-name (comma) given-name&lt;br /&gt;
* family-name (comma) given-name-first-initial&lt;br /&gt;
* family-name (space) given-name-first-initial (optional period)&lt;br /&gt;
&lt;br /&gt;
=== Implied &amp;quot;nickname&amp;quot; Optimization ===&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;nickname&amp;quot; optimization to handle this.&lt;br /&gt;
&lt;br /&gt;
Similar to the implied &amp;quot;n&amp;quot; optimization, if &amp;quot;FN&amp;quot; and &amp;quot;ORG&amp;quot; are not the same, and the value of the &amp;quot;FN&amp;quot; property is exactly one word, and there is no explicit &amp;quot;N&amp;quot; property, then:&lt;br /&gt;
&lt;br /&gt;
# The content of the &amp;quot;FN&amp;quot; is treated as a &amp;quot;nickname&amp;quot; property value.&lt;br /&gt;
# Parsers should handle the missing &amp;quot;N&amp;quot; property by implying empty values for all the &amp;quot;N&amp;quot; sub-properties.&lt;br /&gt;
&lt;br /&gt;
Note: the hCard may have additional explicit &amp;quot;nickname&amp;quot; property values in addition to the implied nickname.&lt;br /&gt;
&lt;br /&gt;
=== Implied &amp;quot;organization-name&amp;quot; Optimization ===&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;ORG&amp;quot; property has two subproperties, organization-name and organization-unit. Very often authors only publish the organization-name.  Thus if an &amp;quot;ORG&amp;quot; property has no &amp;quot;organization-name&amp;quot; inside it, then its entire contents MUST be treated as the &amp;quot;organization-name&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== Tags as Categories ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Root Class Name ===&lt;br /&gt;
&lt;br /&gt;
The root class name for an hCard is &amp;quot;vcard&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== Property List ===&lt;br /&gt;
&lt;br /&gt;
This is the list of properties (and subproperties, in parentheses, like this) in hCard, taken from vCard:&lt;br /&gt;
&lt;br /&gt;
* fn, n (family-name, given-name, additional-name, honorific-prefix, honorific-suffix), nickname, sort-string&lt;br /&gt;
* url, email (type, value), tel (type, value)&lt;br /&gt;
* adr (post-office-box, extended-address, street-address, locality, region, postal-code, country-name, type, value), label&lt;br /&gt;
* geo (latitude, longitude), tz&lt;br /&gt;
* photo, logo, sound, bday&lt;br /&gt;
* title, role, org (organization-name, organization-unit)&lt;br /&gt;
* category, note&lt;br /&gt;
* class, key, mailer, uid, rev&lt;br /&gt;
==== type subproperty values ====&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;Home&amp;quot; is the same as &amp;quot;home&amp;quot;, as well as multivalued, e.g. a tel can be home and preferred:&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Home&amp;lt;/span&amp;gt; (&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;pref&amp;lt;/span&amp;gt;erred):&lt;br /&gt;
 &amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt;+1.415.555.1212&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following lists are ''informative''. See RFC2426 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.&lt;br /&gt;
&lt;br /&gt;
* adr type: INTL, POSTAL, PARCEL, WORK, dom, home, pref&lt;br /&gt;
* tel type: VOICE, home, msg, work, pref, fax, cell, video, pager, bbs, modem, car, isdn, pcs&lt;br /&gt;
* email type: INTERNET, x400, pref, &amp;quot;other IANA registered address types&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== XMDP Profile ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Parsing Details ===&lt;br /&gt;
&lt;br /&gt;
See [[hcard-parsing|hCard parsing]].&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
&lt;br /&gt;
This section is informative.&lt;br /&gt;
&lt;br /&gt;
=== Sample vCard ===&lt;br /&gt;
&lt;br /&gt;
Here is a sample vCard:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
BEGIN:VCARD&lt;br /&gt;
VERSION:3.0&lt;br /&gt;
N:Çelik;Tantek&lt;br /&gt;
FN:Tantek Çelik&lt;br /&gt;
URL:http://tantek.com/&lt;br /&gt;
ORG:Technorati&lt;br /&gt;
END:VCARD&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and an equivalent in hCard with various elements optimized appropriately.  See [[hcard-example1-steps| hCard Example 1]] for the derivation. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;a class=&amp;quot;url fn&amp;quot; href=&amp;quot;http://tantek.com/&amp;quot;&amp;gt;Tantek Çelik&amp;lt;/a&amp;gt;&lt;br /&gt;
 &amp;lt;div class=&amp;quot;org&amp;quot;&amp;gt;Technorati&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This hCard might be displayed as:&lt;br /&gt;
&lt;br /&gt;
[http://tantek.com/ Tantek Çelik]&amp;lt;br /&amp;gt;&lt;br /&gt;
Technorati&lt;br /&gt;
&lt;br /&gt;
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 &amp;lt;head&amp;gt; element.&lt;br /&gt;
&lt;br /&gt;
=== More Examples ===&lt;br /&gt;
&lt;br /&gt;
See [[hcard-examples]] for more examples, including all examples from vCard RFC 2426 converted into hCard.&lt;br /&gt;
&lt;br /&gt;
== Examples in the wild ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
The following sites have published hCards, and thus are a great place to start for anyone looking for examples &amp;quot;in the wild&amp;quot; to try parsing, indexing, organizing etc.  If you have an hCard on your own page, feel free to add it to the top of this list.  Once the list grows too big, we'll make a separate wiki page.&lt;br /&gt;
&lt;br /&gt;
=== New Examples ===&lt;br /&gt;
Please add new examples to this section.&lt;br /&gt;
* [http://www.geekinthepark.co.uk Geek in the Park] uses hCards for the speakers and people who comment.&lt;br /&gt;
* [http://www.besancon.fr/index.php?p=32 Official site of Besançon (France)] uses hCard for each page concerning the small towns surrounding Besançon.&lt;br /&gt;
* [http://2006.dconstruct.org/speakers/ d.Construct 2006 conference speakers list] is implemented using hCards.&lt;br /&gt;
* [http://local.yahoo.com Yahoo Local] now supports hCards for business and places in the search results&lt;br /&gt;
* [http://learningtheworld.eu/imprint/ Learning the World] has hcard information on the imprint, alas we didn't succeed to mark-up the work phone and fax numbers properly.&lt;br /&gt;
* The [http://www.fuckparade.org F’parade] website uses hcard, though I didn't find a type to distinguish mobile and landline phone numbers.&lt;br /&gt;
* [http://www.miranet.nl/contact.htm Miranet Webdesign] have added a hcard to their [http://www.miranet.nl/contact.htm 'contact' page]&lt;br /&gt;
* [http://weblog.200ok.com.au/ Ben Buchanan] has added a vCard to the [http://weblog.200ok.com.au/about/ 'About' page on The 200ok Weblog]&lt;br /&gt;
* [http://www.radiantcore.com Radiant Core] has their contact information [http://www.radiantcore.com/contact/ available in hCard].&lt;br /&gt;
* [http://www.mikerumble.co.uk/ Mike Rumble] has [http://www.mikerumble.co.uk/contact.html uploaded his hCard].&lt;br /&gt;
* [http://www.saumag.edu/ Southern Arkansas University] has its contact footer encoded as hCard&lt;br /&gt;
* [http://main.uab.edu/ University of Alabama at Birmingham] has its contact footer encoded as hCard&lt;br /&gt;
* [http://www.capital.edu Capital University] has contact footer and bloggers' names encoded as hCard. Also, all page-specific contact information is encoded as hCards (see [http://www.capital.edu/Internet/Default.aspx?pid=67 Admissions] page for an example)&lt;br /&gt;
* [http://main.uab.edu/shrp/ UAB School of Health Professions] uses hCard in its contact footer&lt;br /&gt;
* [http://green.carisenda.com/ Stephen Stewart] has his hCard on the front page of his weblog ('You are here' section)&lt;br /&gt;
* [http://www.fberriman.com/ Frances Berriman] has a hidden vCard in the footers of her website.&lt;br /&gt;
* [http://www.candlescience.com/ CandleScience Candle Supply] added a hidden hcard sitewide.&lt;br /&gt;
* [http://www.direction.es/ Direction] uses hCard for contact information.&lt;br /&gt;
* [http://audiobank.tryphon.org AudioBank] uses hCard to display member informations.&lt;br /&gt;
* [http://www.vivabit.com/atmedia2006/speakers/ @media speakers] are marked up with hCard (photos depend on BASE tag support which makes this a good test case)&lt;br /&gt;
* [http://www.dougransom.com Doug Ransom] uses hCard for his financial advisory practice. &lt;br /&gt;
* [http://rubyandrails.org/usergroups/newcastle/members.html ncl.rb] uses hCard for contact information.&lt;br /&gt;
* [http://www.snowinteractive.com/ Snow Interactive] uses hCard for contact information.&lt;br /&gt;
* [http://flickr.com Flickr] now supports [[hcard|hCard]] and [http://gmpg.org/xfn XFN] on profile pages.  See [http://flickr.com/photos/factoryjoe/113866484/ screenshot of Flickr UI in Flock browser using Flocktails extension - March 17th 2006].&lt;br /&gt;
* [http://www.ndiyo.org/contact Contact information for the Ndiyo project]&lt;br /&gt;
* [http://www.pixelenvy.co.uk/ Pixel Envy] uses hCard for contact information on every page&lt;br /&gt;
* [http://stilbuero.de/contact/ Klaus Hartl] uses hCard in the sidebar for contact information (maybe easier to parse through delivering xhtml as xml).&lt;br /&gt;
* [http://charlvn.virafrikaans.com/contact Charl van Niekerk's hCard]&lt;br /&gt;
* [http://billy-girlardo.com/WP/ BillyBLOGirlardo] uses hCard for contact information.&lt;br /&gt;
* [http://www.hicksdesign.co.uk/ Hicksdesign] uses hCard for contact information.&lt;br /&gt;
* http://www.gr0w.com/articles/press/growsearch_launched_press_release/ - hCard in a press release for the press contact info&lt;br /&gt;
* http://www.redmonk.com/cote/archives/2006/03/testing_out_mic.html - hCard with explanation&lt;br /&gt;
* [http://andy.ciordia.info/ it's my island], personal blog, hcard on the ''[http://andy.ciordia.info/pages/about_me About the Writer]'' page. [[User:Ciordia9|Andy Ciordia]]&lt;br /&gt;
* [http://www.windowonwoking.org.uk/ Window on Woking], a local community site in the UK, uses hCard in the homepage of each member organisation and local Councillor.&lt;br /&gt;
* [http://ChunkySoup.net/ ChunkySoup.net] has redesigned using hAtom 0.1 and hCards on the entire site -- by [[User:ChrisCasciano|Chris Casciano]]&lt;br /&gt;
* [http://www.30boxes.com/ 30 Boxes],a social calendar application and digital lifestyle aggregator, automatically creates an hcard for you with your account.  It is found under Settings &amp;gt; Syndication.&lt;br /&gt;
* [http://www.nearwhere.com/ Nearwhere.com] allow you to put an hcard on an interactive map.&lt;br /&gt;
* [http://www.brentozar.com/ Brent Ozar] added a [http://www.brentozar.com/contact.php contact] page hCard.&lt;br /&gt;
* [http://www.kerihenare.com/ Keri Henare] has rewritten his [http://www.kerihenare.com/contact/ contact] page hCard.  Now using &amp;lt;code&amp;gt;&amp;lt;object&amp;gt;&amp;lt;/code&amp;gt; instead of &amp;lt;code&amp;gt;&amp;lt;img&amp;gt;&amp;lt;/code&amp;gt; for photo. (Thanks Brian Suda for updating the vCard converter)&lt;br /&gt;
* [http://michaelraichelson.com/contact/ Michael Raichelson] had an hCard on his contact page before SXSW, but never thought to add it here until Tantek requested it.&lt;br /&gt;
* [http://www.commoner.com/~lsimon/lindsey_simon_hcard.html Lindsey Simon] has added an hCard to his website as per Tantek's SXSW request for folks to try it &lt;br /&gt;
* [http://www.davidgagne.net/ David Gagne] has an hCard in his sidebar.&lt;br /&gt;
* [http://www.churchzip.com/map/ Churchzip.com/map] and [http://www.skiwhere.com/map/ Skiwhere.com/map], provide churches, hotels, and ski resorts on the same maps.  Locations are formatted as hcards.&lt;br /&gt;
* All [http://www.iqdir.com/ IQ Directory Solutions] Yellow Pages web portals use [[hcard|hCard]] markup on listings. For example [http://www.yellowpages-cambodia.com/ Cambodia Yellow Pages] and [http://www.superpages.com.my/ Malaysia Super Pages]&lt;br /&gt;
* Ning's cloneable Group app uses fuzzy matching to map custom fields to [[hcard|hCard]] markup on its [http://group.ning.com/index.php?controller=person&amp;amp;action=view&amp;amp;content=JonathanAquino profile] pages.&lt;br /&gt;
* [http://claimid.com/factoryjoe Chris Messina' ClaimID hCard]&lt;br /&gt;
* [http://factoryjoe.com/blog/hcard Chris Messina' hCard]&lt;br /&gt;
* [http://flock.com/about Flock About]&lt;br /&gt;
* [http://tantek.com/microformats/2006/03-01-TechPlenAgenda.html Agenda: W3C Technical Plenary Day, March 1 2006] has [[hcard|hCard]] and [[hcalendar|hCalendar]] markup. ([http://www.w3.org/2006/03/01-TechPlenAgenda.html original here]).&lt;br /&gt;
* [http://www.gr0w.com/articles/press/growsearch_launched_press_release/ GrowSearch Launched (Press Release)] uses an hCard to provide Press Contact Point.&lt;br /&gt;
* The [http://www.arborday.org/ National Arbor Day Foundation] has started using hCards for their [http://arborday.org/programs/conferences/communityforestry/index.cfm upcoming] [http://arborday.org/programs/conferences/hazardtrees-treeplanting/ conferences].&lt;br /&gt;
* [http://www.multipack.co.uk The Multipack] has numerous hCards, especially on the [http://www.multipack.co.uk/members/ members page], as well as the next meeting information.&lt;br /&gt;
* [http://deadringrancor.livejournal.com/ Justin McDowell] used an hCard when [http://deadringrancor.livejournal.com/221332.html referring to a person in his blog post]&lt;br /&gt;
* [http://davecardwell.co.uk/cv/ Dave Cardwell] has included his hCard in his Curriculum Vitae.&lt;br /&gt;
* [http://blog.usweb.com/ Shaun Shull] has written a great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], and has included his [[hcard|hCard]] as one of the examples.&lt;br /&gt;
* [http://www.thefutureoftheweb.com/ Jesse Skinner] has written a simple [http://www.thefutureoftheweb.com/blog/2006/1/hcard tutorial with examples]&lt;br /&gt;
* [http://www.w3.org/2005/12/allgroupoverview.html 2006 W3C Technical Plenary Week] has marked up the venue, contacts, and program committee members all with hCard.&lt;br /&gt;
* [http://www.avf-nexus.co.uk AVF-Nexus] have a hCard on their [http://www.avf-nexus.co.uk/contact/ contact page] - (by [http://creation.uk.com Creation&amp;quot;])&lt;br /&gt;
* [http://www.thefantasticos.com/andrew/ Andrew White] posted [http://www.thefantasticos.com/andrew/index.php/my-hcard/ his hCard] and [http://www.thefantasticos.com/andrew/index.php/62/microformats-the-should-have-been-obvious-web-dev-tool/ blogged about it].&lt;br /&gt;
* [http://www.2sheds.ru Oleg &amp;quot;2sheds&amp;quot; Kourapov] in his [http://www.2sheds.ru/blog/ blog] ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog X2V]) has turned personal profile into hCard ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/hcard.html X2V]) and his blogroll - into combination XFN/hCards ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/friends.html X2V])&lt;br /&gt;
* [http://www.approveddesign.co.uk Approved Design Consultancy] have a hCard on their [http://www.approveddesign.co.uk/about/contact/ contact page] as well as on their [http://www.approveddesign.co.uk/about/people/ people section] - (by [http://creation.uk.com Creation&amp;quot;])&lt;br /&gt;
* [http://weblog.200ok.com.au/ Ben Buchanan] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&amp;amp;format=search Colin Morris] have [http://weblog.200ok.com.au/2006/01/griffith-phonebook-adds-hcard-and.html implemented hCards and vCards] for the [http://www.griffith.edu.au Griffith University] [http://www.griffith.edu.au/find/content_phonebook.html online phone book]. Eg. [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=ben+buchanan&amp;amp;format=search Ben's vCard] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&amp;amp;format=search Colin's vCard]&lt;br /&gt;
* WWF-Australia [http://wwf.org.au/about/contactdetails/ contact details page]&lt;br /&gt;
* [http://rasterweb.net/raster/ Pete Prodoehl] used the hCard format on his [http://rasterweb.net/raster/contact.html Contact page]&lt;br /&gt;
* [http://alexander-mette.de amette] uses the hCard format in a module of his TikiWiki powered blog&lt;br /&gt;
* [http://staff.washington.edu/oren/weblog2/ Oren Sreebny] has an hcard on his blog main index template &lt;br /&gt;
* [http://www.cs.brandeis.edu/~zippy/ Patrick Tufts] has an hCard on his homepage.&lt;br /&gt;
* [http://ascii20.blogspot.com/ Mathias Kolehmainen and Jamie Taylor] have hCards on their weblog.&lt;br /&gt;
* [http://www.hoppsan.org/jamesb/blogger/ Barnaby James] has a hCard on his weblog.&lt;br /&gt;
* [http://esa-education.com/schools/map ESA Education] Uses hCards for their 100+ schools and each of the individual school sites.&lt;br /&gt;
* [http://www.thereisnocat.com/#vcard Ralph Brandi] has added an hCard to the sidebar of his weblog as a result of Tantek Çelik's portion of the Microformats presentation at SXSW 2006.&lt;br /&gt;
* [http://www.pierce.ctc.edu/ephone/ Pierce College] -- community college directory uses hCard on all individual directory entries.&lt;br /&gt;
* [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/ the Institutional Web Management Workshop 2006] have marked up all their [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/committee/ speakers with hCard].&lt;br /&gt;
* http://wikitravel.org/en/Singapore/Sentosa. Wikitravel is experimenting with hcard on its travel guides. This guide uses hcard for all its business listings. More info on http://wikitravel.org/en/Wikitravel_talk:Listings.&lt;br /&gt;
* [http://www.musik-erber.de/ Musik-Erber] uses to present contact information at the sidebar&lt;br /&gt;
* [http://cdevroe.com/about/#contact Colin D. Devroe] uses hCard to display his contact information on his about page&lt;br /&gt;
* The ECS (Scool of Electronics and Computer Science  at the University of Southampton) [http://www.ecs.soton.ac.uk/people People Pages] use vCard. Contact cjg@ecs.soton.ac.uk if there's any bugs.&lt;br /&gt;
* [http://www.southwestern.edu/~ramseyp Pat Ramsey] has his contact information on his blog marked up with hCard. Contact [mailto:ramsey.pat@gmail.com ramsey.pat@gmail.com] if there are any bugs there.&lt;br /&gt;
* [http://www.meryl.net/ Meryl K. Evans] has a hidden hCard on her homepage.&lt;br /&gt;
* [http://www.vyre.com/comp&lt;br /&gt;
&lt;br /&gt;
== Implementations ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
The following implementations have been developed which either generate or parse hCards. If you have an hCard implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.&lt;br /&gt;
* [http://placenamehere.com/mf/nnwextract/ Extract Microformats] is a script for NetNewsWire that supports extracting hCard and hCalendar data in blog posts (via technorati service). Written by [[User:ChrisCasciano|Chris Casciano]]&lt;br /&gt;
* [http://allinthehead.com/hkit/ hKit] is an open source PHP 5 parsing library with support for hCard.&lt;br /&gt;
* [http://kitchen.technorati.com/search Technorati Microformats Search] indexes [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] as [http://tantek.com/log/2006/05.html#d31t1802 announced by Tantek].&lt;br /&gt;
** list of pages with indexing Issues so they can be looked into as to why data is not being extracted&lt;br /&gt;
** suda.co.uk/contact&lt;br /&gt;
** multipack.co.uk&lt;br /&gt;
&lt;br /&gt;
* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of hCards from within Dreamweaver 8.&lt;br /&gt;
* [http://scooch.gr0w.com/ Scooch] is a slide show and presentation creator that generates a [[hCard]] for individual slide show authors and comment authors with a CSS button to parse and download via [http://suda.co.uk/projects/X2V/ X2V]. Also uses [[hReview]] for slide ratings and [[rel-tag]] for categories.&lt;br /&gt;
* [http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar&lt;br /&gt;
*[http://opensource.reevoo.com/2006/03/08/release-uformats-12/ uformats] is a ruby library that can parse [[hCalendar]], [[hCard]], [[hReview]] and [[rel-tag]]&lt;br /&gt;
* [http://blog.codeeg.com/tails-firefox-extension/  Tails] is a Firefox Extension that will display the presence and details of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage. [https://addons.mozilla.org/firefox/2240/ Tails Export] is an extended version.&lt;br /&gt;
* [http://www.stripytshirt.co.uk/features/firefox/smartzilla Smartzilla is a Firefox Extension] that finds hCards on web pages and lets you add them to your addressbook.&lt;br /&gt;
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCard and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].&lt;br /&gt;
* There is [http://flickr.com/photos/factoryjoe/68755089/ evidence of built-in hCard support in the Konqueror browser].  Specifically, Konqueror 3.5, in KDE 3.5 (kubuntu Breezy w/ update).&lt;br /&gt;
* There is [http://tagcamp.org/index.cgi?ContactList evidence of a kwiki plugin for hCards].  Update: the [http://svn.kwiki.org/cwest/Kwiki-hCard/ hCard kwiki plugin svn repository].  See the [http://microwiki.caseywest.com/index.cgi?hCard documentation of the hCard kwiki plugin].&lt;br /&gt;
* [http://suda.co.uk/projects/X2V/ X2V] is a bookmarklet that parses hCard and produces a .vcf (vCard) stream.  Note: needs to be updated as the spec is refined&lt;br /&gt;
* [http://www.stripytshirt.co.uk Duncan Walker] has built [http://www.stripytshirt.co.uk/features/firefox/smartzilla a Firefox extension] that gets hCard data from a webpage, uses Brian Suda's XSL (locally) to transform it to vcard format and opens the resulting .vcf file.&lt;br /&gt;
* [http://george.hotelling.net/90percent/ George] has written a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script] that detects hCards and allows users to easily add them to their address book application.  Relies on the X2V web service to do the conversion.&lt;br /&gt;
* [http://inside.glnetworks.de/ Martin Rehfeld] has updated the work of [http://blogmatrix.blogmatrix.com/ David Janes] and produced a [[Greasemonkey]] [http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ script] that finds many microformat elements, including hCards, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. The hCard to vCard conversion is done internally within the script. ''This will work with FireFox 1.5+/GreaseMonkey 0.6.4+ now.''&lt;br /&gt;
* [http://diveintomark.org/ Mark Pilgrim] has also written an [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser Greasemonkey user script].  It is self-contained and does not rely on the X2V web service.&lt;br /&gt;
* [http://www.oliverbrown.me.uk/2005/09/03/a-working-microformats-extension-to-simplexml/ Oliver Brown] has written an &amp;quot;extension&amp;quot; to [http://www.php.net/simplexml SimpleXML] that gives simple access to hCard information in PHP 5.&lt;br /&gt;
* [http://thedredge.org/ Andrew D. Hume] has built a system (Wordpress plugin?) for [http://thedredge.org/2005/06/using-hcards-in-your-blog/ using hcards in your blog] to represent people leaving comments on blog posts.&lt;br /&gt;
* The [http://tantek.com/microformats/hcard-creator.html hCard creator] is a very simple, yet illustrative, open source user interface / form / script which creates an hCard in real-time as you type in a set of contact information. &lt;br /&gt;
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate hCard information ([http://ietf.org/rfc/rfc2629 RFC2629] is an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])&lt;br /&gt;
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - Open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards. &lt;br /&gt;
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] is a collection of palmpilot and sidekick tools. It includes X2V derivatives xhtml2hcard.xsl and toICal.xsl plus some [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest] materials&lt;br /&gt;
* [http://www.openpsa.org/ OpenPsa 2.x] CRM application uses hCard for all person listings. The widget is [http://www.midgard-project.org/midcom-permalink-922834501b71daad856f35ec593c7a6d reusable across Midgard CMS]&lt;br /&gt;
* [http://www.metonymie.com Emiliano Martínez Luque] has written an experimental [http://www.metonymie.com/hCard_extract/app.html hCard finder and structured search application] that finds hCards within a given set of URLs and returns the ones that match the specified search criteria.&lt;br /&gt;
* [http://randomchaos.com/microformats/base/ Microformat Base] is an open-source PHP microformat aggregation crawler, currently recognizing hreview, hcalendar, and hcard.&lt;br /&gt;
&lt;br /&gt;
== Additional Applications ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
There are numerous potential additional uses and applications for hCards on the Web.  The following are merely a few thoughts and possibilities that folks have come up with:&lt;br /&gt;
&lt;br /&gt;
* As an open standard/format for [http://www.gravatar.com/ Gravatars].&lt;br /&gt;
* Marking up individual authors of blog posts on a group blog&lt;br /&gt;
* Marking up people's names and URLs in a blogroll&lt;br /&gt;
* Any reference to people in blog posts (e.g. when citing them, or referencing them, or describing them, by name).&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
=== Normative References ===&lt;br /&gt;
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]&lt;br /&gt;
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426]&lt;br /&gt;
&lt;br /&gt;
=== Informative References ===&lt;br /&gt;
* [http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426]&lt;br /&gt;
* [http://w3.org/TR/REC-CSS1 CSS1]&lt;br /&gt;
* [http://tantek.com/log/2004/09.html#hcard hCard term introduced and defined on the Web, 20040930]&lt;br /&gt;
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]&lt;br /&gt;
* Contributed from http://developers.technorati.com/wiki/hCard.&lt;br /&gt;
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]&lt;br /&gt;
&lt;br /&gt;
==== Specifications That Use hCard ====&lt;br /&gt;
* [[adr]]&lt;br /&gt;
* [[geo]]&lt;br /&gt;
* [[hcalendar|hCalendar]]&lt;br /&gt;
* [[hreview|hReview]]&lt;br /&gt;
&lt;br /&gt;
==== Similar Work ====&lt;br /&gt;
* [http://www.intertwingly.net/wiki/pie/PaceBetterPersonElement Atom PaceBetterPersonElement]&lt;br /&gt;
* [http://www.jabber.org/jeps/jep-0054.html JEP-0054: vcard-temp]&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
* [http://microformats.org/code/hcard/creator hCard creator] ([[hcard-creator-feedback|feedback]]) - create your own hCard.&lt;br /&gt;
* [[hcard-authoring|hCard authoring]] - learn how to add hCard markup to your existing contact info.&lt;br /&gt;
* [[hcard-faq|hCard FAQ]] - If you have any questions about hCard, check here, and if you don't find answers, add your questions!&lt;br /&gt;
* [[hcard-parsing|hCard parsing]] - Normatively details of how to parse hCards.&lt;br /&gt;
* [[hcard-issues|hCard issues]] - Please add any issues with the specification to the issues page.&lt;br /&gt;
* [[hcard-profile|hCard profile]] - The XMDP profile for hCard&lt;br /&gt;
&lt;br /&gt;
This 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.&lt;br /&gt;
&lt;br /&gt;
* [[hcard-brainstorming|hCard Brainstorming]] - where we are keeping our brainstorms and other explorations relating to hCard&lt;br /&gt;
* [[hcard-tests|hCard tests]] - a wiki page with actual embedded hCards to try parsing.&lt;br /&gt;
&lt;br /&gt;
== Further Reading ==&lt;br /&gt;
* [http://www.digital-web.com/articles/microformats_primer/ Digital Web Magazine: Microformats Primer] by Garrett Dimon has a good intro to hCard&lt;br /&gt;
* [http://24ways.org/advent/practical-microformats-with-hcard Practical Microformats with hCard] by Drew McLellan&lt;br /&gt;
* [http://thedredge.org/ Andrew D. Hume] has written a blog post on [http://usabletype.com/articles/2005/usable-microformats/ usable microformats] which discusses hCard&lt;br /&gt;
* [http://www.thefutureoftheweb.com/blog/2006/1/hcard Jesse Skinner's introduction to hCard]&lt;br /&gt;
* [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.&lt;br /&gt;
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page] and the [http://technorati.com/tags/hcard hCard tag]&lt;/div&gt;</summary>
		<author><name>Trovster</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=User:Trovster&amp;diff=17287</id>
		<title>User:Trovster</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=User:Trovster&amp;diff=17287"/>
		<updated>2006-07-21T15:11:55Z</updated>

		<summary type="html">&lt;p&gt;Trovster: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Is a web developer from the UK who writes on [http://www.trovster.com trovster.com] and is part of the [http://www.multipack.co.uk Multipack].&lt;/div&gt;</summary>
		<author><name>Trovster</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=irc&amp;diff=7611</id>
		<title>irc</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=irc&amp;diff=7611"/>
		<updated>2006-07-21T15:10:11Z</updated>

		<summary type="html">&lt;p&gt;Trovster: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
= Microformats IRC =&lt;br /&gt;
&lt;br /&gt;
We have an IRC channel, [irc://irc.freenode.net#microformats #microformats on the freenode network].&lt;br /&gt;
&lt;br /&gt;
There's typically someone there at any point during the day, though there isn't always active discussion. Sometimes, though this is the best place to discuss issues that need lots of back and forth discussion.&lt;br /&gt;
&lt;br /&gt;
== People on irc ==&lt;br /&gt;
A list of IRC regulars and their normal timezones. (winter/summer)&lt;br /&gt;
&lt;br /&gt;
* [[User:Adam Craven|AdamCraven]] (+0000)&lt;br /&gt;
* [[User:Amette|amette]] (+1000)&lt;br /&gt;
* [[User:B.K._DeLong|bkdelong]] (-0500/-0400)&lt;br /&gt;
* [[User:Ben Ward|BenWard]] (+0000)&lt;br /&gt;
* [[User:BenjaminCarlyle|BenjaminCarlyle]] (+1000)&lt;br /&gt;
* [[User:Boneill|boneill]] (+0000)&lt;br /&gt;
* [[User:Brian|briansuda]] (-0600/-0500)&lt;br /&gt;
* [[User:ColinDDevroe|cdevroe]] (-0500/-0600)&lt;br /&gt;
* [[User:Cgriego|cgriego]] (-0600/-0500)&lt;br /&gt;
* [[User:ChrisCasciano|pnhChris]] (-0500/-0400)&lt;br /&gt;
* [[User:ChrisMessina|factoryjoe]] (-0800/-0700)&lt;br /&gt;
* [[User:ChristopherStJohn|cks]] (-0600/-0500)&lt;br /&gt;
* [[User:DanC|DanC]] (-0600/-0500)&lt;br /&gt;
** office hours: Wednesday afternoons, America/Chicago time&lt;br /&gt;
* [[User:Dave Cardwell|davecardwell]] (+0000)&lt;br /&gt;
* [[User:DimitriGlazkov|dglazkov]] (-0600/-0500)&lt;br /&gt;
* [[User:DrewMcLellan|drewinthehead]] (+0000/+0100)&lt;br /&gt;
* [[User:EdwardOConnor|hober]] (-0800/-0700)&lt;br /&gt;
* [[User:Enric|enric]] (-0800/-0700)&lt;br /&gt;
* [[User:Evan|evanpro]] (-0500)&lt;br /&gt;
* [[User:Fil|Fil]] (+0200)&lt;br /&gt;
* [[User:Grantbow|Grantbow]] (-0800/-0700)&lt;br /&gt;
* [[User:Hlb|hlb]] (+0800-0700)&lt;br /&gt;
* [[User:IanHickson|Hixie]] (-0800/-0700)&lt;br /&gt;
* [[User:Izo|IZO]]&lt;br /&gt;
* [[User:JoeGregorio|jcgregorio]]&lt;br /&gt;
* [[User:Jonathan_Arkell|jonnay]] (-0700/0600)&lt;br /&gt;
* [[User:Keri Henare|kerihenare]] (+1200)&lt;br /&gt;
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)&lt;br /&gt;
* [[User:Mark Mansour|Mark Mansour]] (+1100)&lt;br /&gt;
* [[User:MarkNormanFrancis|Mark Norman Francis]] (+0000/+0100)&lt;br /&gt;
* [[User:neuro|neuro`]]&lt;br /&gt;
* [[User:Phae|Phae]] (+0000/+0100)&lt;br /&gt;
* [[User:PriitLaes|plaes]] (+0200/+0300)&lt;br /&gt;
* [[User:Remi|Remi]] (-0500/-0400)&lt;br /&gt;
* [[User:RobertBachmann|RobertBachmann]] (+0100/+0200)&lt;br /&gt;
** Office hours: &amp;lt;del&amp;gt;Wednesday, 18:00-20:00 UTC&amp;lt;/del&amp;gt; (Currently no office hours)&lt;br /&gt;
* [[User:RyanKing|kingryan]] (-0800/-0700)&lt;br /&gt;
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC&lt;br /&gt;
* [[User:Csarven|csarven]] (-0500/-0400)&lt;br /&gt;
* [[User:Dana Benson|Snowden]] (-0800/-0700)&lt;br /&gt;
* [[User:Steve Ganz|SteveGanz]] (-0800/-0700)&lt;br /&gt;
* [[User:Tantek|Tantek]] (-0800/-0700)&lt;br /&gt;
* [[User:Trovster|trovster]] (-0800/-0700)&lt;br /&gt;
* [[User:Dan Kubb|dkubb]] (-0800/-0700)&lt;br /&gt;
* [[User:Ed Summers|edsu]] (-0500/-0400)&lt;br /&gt;
* [[User:Smackman|Steve Farrell]] (-0800/-0700)&lt;br /&gt;
* [[User:Enric|Enric]] (-0800/-0700)&lt;br /&gt;
* [[User:Charlvn|Charl]] (+0200/+0200)&lt;br /&gt;
* [[User:MarkoMrdjenovic|friedcell]] (+0100/+0200)&lt;br /&gt;
* [[User:Vant|vant]] (-0800/-0700)&lt;br /&gt;
* [[User:IwaiMasaharu|iwaim]] (+0900)&lt;br /&gt;
&lt;br /&gt;
=== Greetings ===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strong&amp;gt;Note:&amp;lt;/strong&amp;gt; jibot is currently &amp;lt;abbr title=&amp;quot;Missing in action&amp;quot;&amp;gt;MIA&amp;lt;/abbr&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
To display a brief description of who you are each time you join the channel, you can create a definition for your username. To do so pass the &amp;lt;tt&amp;gt;?def&amp;lt;/tt&amp;gt; command using something like the following convention (be brief):&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;?def jdoe is John Doe and can be found online at &amp;lt;nowiki&amp;gt;http://www.jdoewebsite.com&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
More information about using JiBot commands can be found on the [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot website]&lt;br /&gt;
&lt;br /&gt;
=== bots ===&lt;br /&gt;
&lt;br /&gt;
* [[mfbot]]&lt;br /&gt;
* [[mflogbot]]&lt;br /&gt;
* [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot]&lt;br /&gt;
&lt;br /&gt;
== Logs ==&lt;br /&gt;
&lt;br /&gt;
Available here: http://rbach.priv.at/Microformats-IRC/&lt;br /&gt;
&lt;br /&gt;
Atom feed of logs available here: http://microformat.makedatamakesense.com/log_feed/&lt;br /&gt;
&lt;br /&gt;
== IRC meetups ==&lt;br /&gt;
&lt;br /&gt;
The idea of having IRC meetups (that is, a set time for meeting on IRC) has been suggested by [[User:RyanKing|Ryan King]], as it appears to work well for the WordPress community and may help us from time-to-time. As of yet, there are no plans to have meetups, though.&lt;/div&gt;</summary>
		<author><name>Trovster</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hcalendar&amp;diff=6444</id>
		<title>hcalendar</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hcalendar&amp;diff=6444"/>
		<updated>2006-05-18T16:09:41Z</updated>

		<summary type="html">&lt;p&gt;Trovster: /* Examples in the wild */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt; hCalendar &amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
hCalendar is a simple, open, distributed calendaring and events format, based on the  iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]), suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. hCalendar is one of several open [[microformats|microformat]] standards.&lt;br /&gt;
&lt;br /&gt;
Want to get started with writing an [[hcalendar|hCalendar]] event?  Use the [http://microformats.org/code/hcalendar/creator hCalendar creator] to write up an event and publish it.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Draft Specification ==&lt;br /&gt;
&lt;br /&gt;
; Editor : [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc])&lt;br /&gt;
; Authors : [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]&lt;br /&gt;
: [http://suda.co.uk/ Brian Suda]&lt;br /&gt;
&lt;br /&gt;
=== Copyright ===&lt;br /&gt;
{{MicroFormatCopyrightStatement2004}}&lt;br /&gt;
&lt;br /&gt;
=== Patents ===&lt;br /&gt;
{{MicroFormatPatentStatement}}&lt;br /&gt;
&lt;br /&gt;
=== Inspiration and Acknowledgments ===&lt;br /&gt;
Thanks to:&lt;br /&gt;
* Adam Bosworth for leading the [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation] which brought together a critical mass of interested parties.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
The iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]), has been broadly interoperably implemented (e.g. Apple's &amp;quot;iCal&amp;quot; application built into MacOSX).&lt;br /&gt;
&lt;br /&gt;
In addition, bloggers often discuss events on their blogs -- upcoming events, writeups of past events, etc.  With just a tad bit of structure, bloggers can discuss events in their blog(s) in such a way that spiders and other aggregators can retrieve such events, automatically convert them to iCalendar, and use them in any iCalendar application or service.&lt;br /&gt;
&lt;br /&gt;
This specification introduces the '''hCalendar''' format, which is a 1:1 representation of the aforementioned iCalendar standard, in semantic XHTML.  Bloggers can both embed hCalendar events directly in their web pages, and style them with CSS to make them appear as desired.  In addition, hCalendar enables applications to retrieve information about such events directly from web pages without having to reference a separate file.&lt;br /&gt;
&lt;br /&gt;
== Semantic XHTML Design Principles ==&lt;br /&gt;
&lt;br /&gt;
{{semantic-xhtml-design-principles}}&lt;br /&gt;
&lt;br /&gt;
== Format ==&lt;br /&gt;
&lt;br /&gt;
=== In General ===&lt;br /&gt;
&lt;br /&gt;
The iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]) forms the basis of hCalendar.&lt;br /&gt;
&lt;br /&gt;
Note: the editor and authors of this specification are tracking the [http://lists.osafoundation.org/pipermail/ietf-calsify/ &amp;quot;iCal-Basic&amp;quot; effort] and intend to base the core hCalendar profile on iCal-Basic. See references for a link to the current draft.&lt;br /&gt;
&lt;br /&gt;
The basic format of hCalendar is to use iCalendar object/property names in lower-case for class names, and to map the nesting of iCalendar objects directly into nested XHTML.&lt;br /&gt;
&lt;br /&gt;
=== More Semantic Equivalents ===&lt;br /&gt;
&lt;br /&gt;
However, for some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:&lt;br /&gt;
* &amp;lt;code&amp;gt;URL&amp;lt;/code&amp;gt; in iCalendar becomes  &amp;lt;code&amp;gt;&amp;lt;a class=&amp;quot;url&amp;quot; href=&amp;quot;...&amp;quot;&amp;gt;...&amp;lt;/a&amp;gt;&amp;lt;/code&amp;gt; inside the element with &amp;lt;code&amp;gt;class=&amp;quot;vevent&amp;quot;&amp;lt;/code&amp;gt; in hCalendar.&lt;br /&gt;
* &amp;lt;code&amp;gt;ATTENDEE&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;CONTACT&amp;lt;/code&amp;gt;, and &amp;lt;code&amp;gt;ORGANIZER&amp;lt;/code&amp;gt; in iCalendar may be represented by an [[hcard|hCard]] in hCalendar .&lt;br /&gt;
* A named &amp;lt;code&amp;gt;LOCATION&amp;lt;/code&amp;gt; (potentially with an address and/or geo) in iCalendar may be represented by a nested [[hcard|hCard]] in hCalendar.  Similarly, an address &amp;lt;code&amp;gt;LOCATION&amp;lt;/code&amp;gt; may be represented by an [[adr]], and a geo (latitude and longitude) &amp;lt;code&amp;gt;LOCATION&amp;lt;/code&amp;gt; may be represented by a [[geo]].&lt;br /&gt;
* &amp;lt;code&amp;gt;UID&amp;lt;/code&amp;gt; in iCalendar simply becomes another semantic applied to a specific URL for an hCalendar event.&lt;br /&gt;
&lt;br /&gt;
=== Singular vs. Plural Properties ===&lt;br /&gt;
&lt;br /&gt;
For properties which are singular (e.g. &amp;quot;N&amp;quot; and &amp;quot;FN&amp;quot; from vCard), the first descendant element with that class should take effect, any others being ignored.&lt;br /&gt;
&lt;br /&gt;
For properties which can be plural (e.g. &amp;quot;TEL&amp;quot; from vCard), each class instance should create a instance of that property.  Plural properties with subtypes (e.g. TEL with WORK, HOME, CELL from vCard) can be optimized to share a common element for the property itself, with each instance of subtype being an appropriately classed descendant of the property element.&lt;br /&gt;
&lt;br /&gt;
==== Plural Properties Singularized ====&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Human vs. Machine readable ===&lt;br /&gt;
If an &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; element is used for a property, then the '&amp;lt;code&amp;gt;title&amp;lt;/code&amp;gt;' attribute of the &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; element is the value of the property, instead of the contents of the element,  which instead provide a human presentable version of the value.  This specification recommends that such &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; elements be used for the following iCalendar properties:&lt;br /&gt;
* DTSTART, DTEND, DURATION, RDATE, RRULE&lt;br /&gt;
&lt;br /&gt;
== Example ==&lt;br /&gt;
&lt;br /&gt;
Here is a sample event in an iCalendar:&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
BEGIN:VCALENDAR&lt;br /&gt;
PRODID:-//XYZproduct//EN&lt;br /&gt;
VERSION:2.0&lt;br /&gt;
BEGIN:VEVENT&lt;br /&gt;
URL:http://www.web2con.com/&lt;br /&gt;
DTSTART:20051005&lt;br /&gt;
DTEND:20051008&lt;br /&gt;
SUMMARY:Web 2.0 Conference&lt;br /&gt;
LOCATION:Argent Hotel\, San Francisco\, CA&lt;br /&gt;
END:VEVENT&lt;br /&gt;
END:VCALENDAR&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
and an equivalent event in hCalendar format with various elements optimized appropriately.  See [[hcalendar-example1-steps]] for the derivation.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;a class=&amp;quot;url&amp;quot; href=&amp;quot;http://www.web2con.com/&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;summary&amp;quot;&amp;gt;Web 2.0 Conference&amp;lt;/span&amp;gt;: &lt;br /&gt;
  &amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;2005-10-05&amp;quot;&amp;gt;October 5&amp;lt;/abbr&amp;gt;-&lt;br /&gt;
  &amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;2005-10-08&amp;quot;&amp;gt;7&amp;lt;/abbr&amp;gt;,&lt;br /&gt;
 at the &amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt;Argent Hotel, San Francisco, CA&amp;lt;/span&amp;gt;&lt;br /&gt;
 &amp;lt;/a&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
which could be displayed as:&lt;br /&gt;
&lt;br /&gt;
[http://www.web2con.com/ Web 2.0 Conference: October 5-7, at the Argent Hotel, San Francisco, CA]&lt;br /&gt;
&lt;br /&gt;
Note 1: The product information is not necessary since hCalendar is an interchange format.  When transforming hCalendar back into iCalendar, the transforming engine should add its own product ID.&lt;br /&gt;
&lt;br /&gt;
Note 2: A surrounding &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;span class=&amp;quot;vcalendar&amp;quot;&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; element is optional, and is left out as such.  It is optional since the context of a vcalendar is implied when a vevent is encountered.  The implied context/scope is that of the document.  Authors may explicitly use elements with class=&amp;quot;vcalendar&amp;quot; to wrap sets of vevents that all belong to the same calendar, e.g. when publishing multiple calendars on the same page.&lt;br /&gt;
&lt;br /&gt;
Note 3: The version information is unnecessary in hCalendar markup directly since the version will be defined by the profile of hCalendar that is used/referred to in the 'profile' attribute of the &amp;lt;head&amp;gt; element.&lt;br /&gt;
&lt;br /&gt;
Note 4: ISO8601 dates (required by iCalendar) are not very human friendly.  In addition, the year is often understood implicitly by humans from the context.  Thus &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; elements are used to simultaneously provide a human friendly date and/or time in the visible contents of the element, while placing the respective machine parsable comprehensive ISO8601 datetime in the 'title' attribute.&lt;br /&gt;
The notation YYYY-MM-DD should be used for better readability.&lt;br /&gt;
&lt;br /&gt;
Note 5: The difference between the DTEND ISO8601 date (2005-10-08) and the human readable date (7) is NOT a mistake.  [http://lists.osafoundation.org/pipermail/ietf-calsify/2005-September/000769.html DTEND is exclusive], meaning, that the event ends just before the DTEND. Thus for events which start on one day and end on another day, the DTEND date must be specified as the day after the day that a human would say is the last day of the event.&lt;br /&gt;
&lt;br /&gt;
Note 6: The location in this example contains implicit structure (venue name, city, state) which could be marked up explicitly as an [[hcard|hCard]].  See [http://microformats.org/wiki/hcalendar-brainstorming#hCard_locations hCalendar brainstorming: hCard locations] for a informative explanation of how to do this.&lt;br /&gt;
&lt;br /&gt;
See [[hcalendar-examples]] for more hCalendar examples&lt;br /&gt;
&lt;br /&gt;
== Examples in the wild ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
The following sites have implemented hCalendar, and thus are a great place to start for anyone looking for examples &amp;quot;in the wild&amp;quot; to try parsing, indexing, organizing etc.  If events on your pages are marked up with hCalendar, feel free to add it to the top of this list.  Once the list grows too big, we'll make a separate wiki page.&lt;br /&gt;
&lt;br /&gt;
=== New Examples ===&lt;br /&gt;
Please add new examples to this section.&lt;br /&gt;
* [http://www.worldcupkickoff.com/ World Cup KickOff] where you can download and keep all the fixtures you are interested in so you will never miss a single game of the 2006 football World Cup!&lt;br /&gt;
* [http://www.socaltech.com socalTECH] is a news and information site. Their front page event listing is marked up with hCalendar.&lt;br /&gt;
* [http://www.webanalyticsassociation.org/en/calendarevents/search.asp  Web Analytics Association] - hCalendar microformat is in place on all Tendenci sites on the calendar events search page and consolidated list page.&lt;br /&gt;
* [http://www.tendenci.com/en/calendarevents/search.asp Tendenci Calendar Events] with hCalendar&lt;br /&gt;
* [http://www.argolon.com/2006/04/17/web20-conference-in-dublin/ Web2.0 Conference in Dublin] hCalendar event&lt;br /&gt;
* [http://www.meetup.com/ Meetup.com] has marked up [http://www.meetup.com/cities/us/ny/new_york city event calendars], [http://photo.meetup.com/100/events/ group event lists], and [http://www.meetup.com/ signed-in homepages] with hCalendar.&lt;br /&gt;
* [http://ukwindsurfing.com/ ukwindsurfing.com] has marked upcoming events with hCalendar, and the [http://ukwindsurfing.com/events/ events page] in a table.&lt;br /&gt;
* [http://ocono.com/ ocono.com] has marked up it's &amp;quot;Upcoming Events&amp;quot; list with hCalendar.&lt;br /&gt;
* [http://www.austinbloggers.org/ Austin Bloggers] has marked up their &amp;quot;Upcoming Events&amp;quot; box with hCalendar ([http://www.austinbloggers.org/blog/a/001123.html announcement]).&lt;br /&gt;
* Ning's cloneable Group app has [[hcalendar|hCalendar]] markup on its [http://group.ning.com/index.php?controller=event&amp;amp;action=list event calendar] and [http://group.ning.com/index.php?controller=event&amp;amp;action=view&amp;amp;id=727220 event detail] pages.&lt;br /&gt;
* [http://tantek.com/microformats/2006/03-01-TechPlenAgenda.html Agenda: W3C Technical Plenary Day, March 1 2006] has [[hcard|hCard]] and [[hcalendar|hCalendar]] markup. ([http://www.w3.org/2006/03/01-TechPlenAgenda.html original here]).&lt;br /&gt;
* The National Arbor Day Foundation has started using hCalendars for their [http://arborday.org/programs/conferences/communityforestry/index.cfm upcoming] [http://arborday.org/programs/conferences/hazardtrees-treeplanting/ conferences].&lt;br /&gt;
* [http://www.multipack.co.uk The Multipack] features a vevent for the next meeting information.&lt;br /&gt;
* [http://www.stateofflux.com/ State of Flux street art site] has started adding events in hCalendar format&lt;br /&gt;
* The [http://barcamp.org/#BarCamps BarCamp home page lists upcoming BarCamps marked up with hCalendar] and even has a &amp;quot;Subscribe...&amp;quot; link.&lt;br /&gt;
* [http://www.w3.org/2005/12/allgroupoverview.html 2006 W3C Technical Plenary Week] has marked up the schedule and events for the week with hCalendar.&lt;br /&gt;
* [http://www.code4lib.org/2006/schedule code4lib Conference 2006 Schedule] is marked up with hCalendar as [http://www.code4lib.org/node/65 announced on their blog].&lt;br /&gt;
* [http://grouper.ieee.org/groups/754 IEEE 754 Working Group] - trying hCalendar for upcoming meetings.&lt;br /&gt;
* [http://www.pehuen.org/node/494  Elecciones 2005 Chile] - the first spanish language hCalendar event found in the wild.&lt;br /&gt;
* [http://www.codewitch.org/it/2005/11/17/no-creative-commons-no-party/ Giocolando » No Creative Commons? No Party!] is marked up with hCalendar&lt;br /&gt;
* [http://www.cmprofessionals.org/events/calendar.html CM Pros Events Calendar] by Bob Doyle&lt;br /&gt;
* [http://www.midgard-project.org/community/events/ Midgard CMS Event calendar] - as [http://bergie.iki.fi/blog/new-event-calendar-for-midcom.html blogged by Henri Bergius] &lt;br /&gt;
* [http://www.iowamilitaryveteransband.com/schedule/ Iowa Military Veterans Band Schedule] - hCalendar markup [http://weblog.randomchaos.com/archive/2005/10/24/Microformats/ added by Scott Reynen]&lt;br /&gt;
* [http://www.funfairgames.net/weblog/posts/00000011.html Upcoming events on Jason A.R. Moody Amusements Weblog] posted by Jason Moody on 15 Oct 2005. [http://www.funfairgames.net/weblog/index.html His weblog] in general has hCalendar events posted inside the blog posts.&lt;br /&gt;
* [http://tantek.com/microformats/2005/syndicate/tracks-sessions-schedule.html Syndicate - Tracks &amp;amp;amp; Sessions]&lt;br /&gt;
* [http://tantek.com/microformats/2005/web2/program.html Web 2.0 Conference schedule page marked up with hCalendar]&lt;br /&gt;
* [http://www.thisiscmon.com/ C'MON] is a rock band from Canada, and their [http://www.thisiscmon.com/shows/ tour dates] have been marked up by [http://www.d2digitalmedia.com/ Ray Dickman] with hCalendar.&lt;br /&gt;
* [http://ifreebusy.com/ ifreebusy.com] will display freebusy information using hCalendar. See this [http://ifreebusy.com/neiljensen/freebusy/ example].&lt;br /&gt;
* [http://we05.com/ Web Essentials 05] has marked up their [http://we05.com/program.cfm program schedule table with hCalendar], using the 'axis' and 'headers' attributes.&lt;br /&gt;
* [http://www.asdvbonaparte.nl/ ASDV Bonaparte] is a Dutch debating society. Their events calendar has been marked up with the hCalendar conventions.&lt;br /&gt;
* [http://chocnvodka.blogware.com/blog Suw Charman] has marked up [http://suw.org.uk/archives/category/events/ her events] with hCalendar.&lt;br /&gt;
* [http://www.blogbusinesssummit.com/ Blog Business Summit] has published their [http://www.blogbusinesssummit.com/details.htm event details] marked up with hCalendar.&lt;br /&gt;
* [http://eventful.com Eventful.com] publishes all events with hCalendar and venues with [[hcard|hCard]].  Took them only 15 minutes to implement both! Their Atom feeds also contain hCalendar/hCard.&lt;br /&gt;
* [http://upcoming.org Upcoming.org] publishes all events and lists of events with hCalendar.  Took them only an hour to add hCalendar support to the site.&lt;br /&gt;
* The [http://laughingsquid.com/squidlist/calendar/ Laughing Squid Calendar] events, [http://laughingsquid.com/squidlist/calendar/9949/2005/5/9 e.g. this party], now supports hCalendar.&lt;br /&gt;
* [http://paulschreiber.com/ Paul] Schreiber's [http://concerts.shrub.ca/ Sunnyvale House Concerts] site publishes hCalendar event information for upcoming concerts.  In addition the [http://concerts.shrub.ca/shows Past Shows] page contains hCalendar events for all past concerts.&lt;br /&gt;
* [http://paulschreiber.com/ Paul] Schreiber's [http://iceoasis.shrub.ca/ unofficial schedule site] publishes hCalendar information for upcoming hockey games at [http://www.iceoasis.com/ Ice Oasis]&lt;br /&gt;
* [http://www.complexspiral.com/ Complex Spiral Consulting], both in the &amp;quot;Events&amp;quot; box on left side, and the separate [http://www.complexspiral.com/events/ Events page]. &lt;br /&gt;
* [http://tantek.com/log Tantek's Thoughts], specifically the &amp;quot;Events&amp;quot; roll in the right-most column.&lt;br /&gt;
* [http://suda.co.uk/projects/holidays/ Lesser Known Holidays], a list of holidays on [http://suda.co.uk suda.co.uk] that can be imported via iCal and hCal so you can compare actual transformation versus intended.&lt;br /&gt;
* [http://norman.walsh.name/2005/itinerary/ Norm Walsh's travel schedule] use hCalendar as well as GRDDL.&lt;br /&gt;
* [http://www.policyawareweb.org/2005/ftf2/paw-mtg Policy Aware Web (PAW) Project Meeting] uses hCalendar to record date-related decisions, and uses a vtodo microformat to record action items.&lt;br /&gt;
* The [http://www.kiez-ev.de/ Kiez] is a small cinema and has published its [http://www.kiez-ev.de/programm.htm program] marked up with hCalendar.&lt;br /&gt;
* The [http://lufgi4.informatik.rwth-aachen.de Laboratory for Dependable Distributed Systems] publishes it's [http://lufgi4.informatik.rwth-aachen.de/cfps list of notable CfPs on dependability and security] with hCalendar-todo elements.&lt;br /&gt;
* The [http://laughingsquid.com/laughing-squid-10th-anniversary-party/ Laughing Squid 10th Anniversary Party] has an hcalendar page.&lt;br /&gt;
* SPRACI has hcalendar versions of its nightlife/clubbing/gigs/festivals listings for many cities worldwide - eg: [http://www.spraci.com/listhcalendar.php?parea=sydney&amp;amp;category=all Events in Sydney] (check the [http://www.spraci.com/api/ API] pages in the faq section of [http://www.spraci.com/ SPRACI] for more info about the area/city keywords and category tags to use to get data for your city/categories&lt;br /&gt;
* WWF-Australia events calendars: [http://wwf.org.au/act/events/ What's on], [http://wwf.org.au/act/volunteer/ Volunteer]&lt;br /&gt;
* [http://rubyholic.com rubyholic] uses hCalendar to publish calendars for ruby groups.&lt;br /&gt;
* [http://www.bath.ac.uk/whats-on/ University of Bath What's On] uses hCalendar on individual event pages&lt;br /&gt;
&lt;br /&gt;
=== Examples with some problems ===&lt;br /&gt;
* [http://www.bokle.de/ s'Bokle] is a German music pub. Their events calendar has been marked up with hCalendar.&lt;br /&gt;
** improper use of rrule --[[User:RyanKing|RyanKing]] 16:04, 6 Jan 2006 (PST)&lt;br /&gt;
&lt;br /&gt;
== Implementations ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
The following implementations have been developed which either generate or parse hCalendars. If you have an hCalendar implementation, feel free to add it to the top of this list.  Once the list grows too big, we'll make a separate wiki page.&lt;br /&gt;
&lt;br /&gt;
=== Authoring ===&lt;br /&gt;
Implementations you can use to author, create, and publish hCalendar events.&lt;br /&gt;
&lt;br /&gt;
==== Blogging and CMS tools ====&lt;br /&gt;
;Midgard CMS : [http://www.midgard-project.org/documentation/net-nemein-calendar/ Midgard CMS - net.nemein.calendar] - as [http://bergie.iki.fi/blog/new-event-calendar-for-midcom.html blogged by Henri Bergius] &lt;br /&gt;
&lt;br /&gt;
;Drupal module : [http://hybernaut.com/upcoming-hcal Drupal Upcoming.org syndication module emits hCalendar]&lt;br /&gt;
;MovableType and WordPress plug-ins : [http://structuredblogging.org/formats.php StructuredBlogging] is a set of plugins  [http://structuredblogging.org/structuredblogging-wp-latest.zip for  WordPress] and [http://structuredblogging.org/structuredblogging-wp-latest.zip for MovableType] that supports embedding hCalendar and other microformats in templates and blog posts.&lt;br /&gt;
;Textpattern plug-in : [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCalendar and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].&lt;br /&gt;
&lt;br /&gt;
==== Browser scripts and plug-ins ====&lt;br /&gt;
Browser plugins that work with existing authoring tools:&lt;br /&gt;
; Any browser with javascript and a little bit of CSS : [http://microformats.org/code/hcalendar/creator microformats.org hCalendar creator]  (see also original: [http://theryanking.com/ Ryan King] has an [http://theryanking.com/microformats/hcalendar-creator.html hCalendar creator]).&lt;br /&gt;
; Firefox Greasemonkey user script hCalendar creator : [http://www.decafbad.com/blog/2005/06/08/greasemonkey_magic magic_hcalendar Greasemonkey user script by Les Orchard] - allows easy form entry of an event into any textarea, e.g. into a blog post text area.&lt;br /&gt;
; Firefox Greasemonkey user script hCalendar to Google Calendar: [http://torrez.us Elias Torres] has created a [http://torrez.us/archives/2006/04/13/431/ simple script] that will parse hCalendar entries and create a link to add event to [http://www.google.com/calendar/ Google Calendar's] service. Based on [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats George's] and [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats Arve's] work.&lt;br /&gt;
&lt;br /&gt;
==== Desktop Authoring Tools ====&lt;br /&gt;
;Dreamweaver Extension : [http://www.webstandards.org/action/dwtf/microformats/ Extension suite] for Dreamweaver 8 from the [http://webstandards.org/ Web Standards Project].&lt;br /&gt;
;xfy : &lt;br /&gt;
In [https://www.xfytec.com/community/ xfy Community], there are some hCalendar implementations.&lt;br /&gt;
&lt;br /&gt;
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=15&amp;amp;lid=25 hCalendar via RSS] parses an RSS feed, retrieves XHTML documents linked from that feed, and syndicates hCalendars into a calendar view.&lt;br /&gt;
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=19&amp;amp;lid=23 hCalendar Marker XVCD] helps to mark up an event information in XHTML document with hCalendar. &lt;br /&gt;
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=15&amp;amp;lid=17 Simple RDF Calendar XVCD] is a schedule tool which uses RDF Calendar format. It also converts RDF Calendar format to iCalendar and hCalendar format.&lt;br /&gt;
&lt;br /&gt;
=== Conversion and Import ===&lt;br /&gt;
Implementations you can use to importing into a Calendar Application, typically by converting hCalendar to iCalendar/vCalendar.&lt;br /&gt;
&lt;br /&gt;
==== Web Services ====&lt;br /&gt;
These return iCalendar (.ics) and other calendar formats for easy importing into typical calendar programs or other processing.&lt;br /&gt;
* [http://feeds.technorati.com/events Technorati Events Feed service] uses X2V library to parse hCalendar and return iCalendar (.ics).  Note friendly URL, e.g. http://feeds.technorati.com/events/http%3A//microformats.org&lt;br /&gt;
* [http://suda.co.uk/projects/X2V/ X2V] parses hCalendar and produces a .ics (iCalendar) stream.  Note: needs to be updated to track changes in the specification as they occur.&lt;br /&gt;
* [http://lifelint.net/ Life Lint Parser] parses hCalendar and produces .ics, .rdf and debugging information and attempts to be more fully compliant to the iCal standard than previous implementations.  It can be used in the same manner as X2V.  Can output iCal (w optional Outlook 2002 compat), and RDF.&lt;br /&gt;
==== Firefox Greasemonkey Plugins ====&lt;br /&gt;
* [http://george.hotelling.net/90percent/ George] has built a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script that detects hCalendar events and allows users to easily add them to their calendar application(s)].&lt;br /&gt;
* [http://blogmatrix.blogmatrix.com/ David Janes] has produced a [[Greasemonkey]] [http://www.blogmatrix.com/include/microformat-find.user.js script] that finds many microformat elements, including hCalendar events, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. The hCalendar to vCalendar conversion is done internally within the script. ''This does not work with FireFox 1.5+/GreaseMonkey 0.6.4+.''&lt;br /&gt;
==== Aggregators ====&lt;br /&gt;
* [http://kula.jp/software/endo/screenshots/ Endo], an OS X aggregator, supports discovering hCal and adding those events to iCal. Look at the last screenshot at the bottom of the page.&lt;br /&gt;
&lt;br /&gt;
=== Browsing ===&lt;br /&gt;
Implementations that detect, display and otherwise highlight hCalendar events in pages.&lt;br /&gt;
&lt;br /&gt;
* In [http://www.xfytec.com/community/ xfy Community], there are some hCalendar implementations. &amp;quot;hCalendar via RSS&amp;quot; parses an RSS feed, retrieves XHTML documents linked from that feed, and syndicates hCalendars into a calendar view.&lt;br /&gt;
* [http://web.mit.edu/glasser/www/JSCalendar/ JSCalendar] parses hCalendar and produces a displayable HTML table/CSS-based calendar.&lt;br /&gt;
&lt;br /&gt;
==== Firefox extension ====&lt;br /&gt;
[http://blog.codeeg.com/tails-firefox-extension/ Tails is a Firefox Extension] that will display the presence of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage.&lt;br /&gt;
&lt;br /&gt;
==== Flock extension ====&lt;br /&gt;
[http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar&lt;br /&gt;
&lt;br /&gt;
=== Libraries ===&lt;br /&gt;
Open source libraries of hCalendar parsers and other related code for building hCalendar implementations.&lt;br /&gt;
; Javascript : [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats simple hCalendar parser] by [http://virtuelvis.com/ Arve Bersvendsen]&lt;br /&gt;
; PHP : [http://randomchaos.com/microformats/base/ Microformat Base] is an open-source PHP microformat aggregation crawler, currently recognizing hreview, hcalendar, and hcard.&lt;br /&gt;
; Ruby : [http://opensource.reevoo.com/2006/03/08/release-uformats-12/ uformats] is a ruby library that can parse [[hCalendar]], [[hCard]], [[hReview]] and [[rel-tag]]&lt;br /&gt;
; XSLT :&lt;br /&gt;
* X2V is available as an XSLT library&lt;br /&gt;
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] by [[User:DanC]] includes  toICal.xsl and test materials; it works much like xhtml2vcal.xsl in X2V. See also: [http://www.w3.org/2002/12/cal/ RDF Calendar workspace] with icalendar test materials.&lt;br /&gt;
&lt;br /&gt;
=== Potential implementations ===&lt;br /&gt;
&lt;br /&gt;
These are open source projects that could be potentially enhanced to support hCalendar.&lt;br /&gt;
&lt;br /&gt;
* [http://www.k5n.us/webcalendar.php?topic=About WebCalendar]&lt;br /&gt;
* [http://phpicalendar.net/documentation/index.php?title=Main_Page PHP iCalendar]&lt;br /&gt;
* [http://www.vcalendar.org VCalendar]&lt;br /&gt;
* Investigation: [http://wiki.mozilla.org/Calendar_Talk:Lightning#hCalendar_publish_and_subscribe_support Mozilla Calendar / Lightning / Sunbird hCalendar support discussion]&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
=== Normative References ===&lt;br /&gt;
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]&lt;br /&gt;
* [[hcard|hCard]]&lt;br /&gt;
* [http://www.ietf.org/rfc/rfc2445.txt iCalendar RFC2445]&lt;br /&gt;
&lt;br /&gt;
=== Informative References ===&lt;br /&gt;
* [http://w3.org/TR/REC-CSS1 CSS1]&lt;br /&gt;
* [http://tantek.com/log/2004/09.html#hcalendar hCalendar term introduced and defined on the Web, 20040930]&lt;br /&gt;
* [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation, 20040911]&lt;br /&gt;
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]&lt;br /&gt;
* [http://www.ietf.org/internet-drafts/draft-royer-ical-basic-04.txt iCal-Basic draft 04]&lt;br /&gt;
* Contributed from http://developers.technorati.com/wiki/hCalendar&lt;br /&gt;
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]&lt;br /&gt;
&lt;br /&gt;
==== Related ====&lt;br /&gt;
* [[icalendar-implementations|iCalendar implementations]]&lt;br /&gt;
* [[hcalendar-tests]]&lt;br /&gt;
* [http://lists.osafoundation.org/pipermail/ietf-calsify/ IETF-calsify archives]&lt;br /&gt;
* [http://www.livejournal.com/users/jwz/444651.html jwz - Hula] (required reading)&lt;br /&gt;
* [http://www.jwz.org/doc/groupware.html Groupware Bad by Jamie Zawinski] crystalizes the reason for hCalendar ('''emphasis''' added):&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;quot;Right now people can do that by publishing .ics files, but  it's not trivial to do so, and it's work on the part of other people  to look at them. '''If it's not HTML hanging off our friend's home page  that can be viewed in any browser on a public terminal in a library,  the bar to entry is too high and it's useless.'''&amp;quot;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* [http://muddybranch.thejkgroup.com/ Jason Klemow's blog]&lt;br /&gt;
* [http://www.softwarestudio.org/iCal/2445Issues.html RFC2445 Issues List]&lt;br /&gt;
* [http://ietf.webdav.org/calsify/ CALSIFY WG Links And Resources]&lt;br /&gt;
&lt;br /&gt;
=== Similar Work ===&lt;br /&gt;
* [[XOXO]]&lt;br /&gt;
&lt;br /&gt;
== Discussions ==&lt;br /&gt;
&lt;br /&gt;
This specification is a work in progress.  As additional aspects are discussed, understood, and written, they will be added.  There is a separate document where we are keeping our brainstorms and other explorations relating to hCalendar:&lt;br /&gt;
&lt;br /&gt;
* [[hcalendar-brainstorming]]&lt;br /&gt;
&lt;br /&gt;
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].&lt;br /&gt;
** [http://weblog.infoworld.com/udell/2006/01/11.html#a1368 Moving forward with microformats] by [http://weblog.infoworld.com/udell Jon Udell] provides an hCalendar example and some discussion.&lt;br /&gt;
&lt;br /&gt;
=== Q&amp;amp;A ===&lt;br /&gt;
* If you have any questions about hCalendar, check the [[hcalendar-faq]], and if you don't find answers, add your questions!&lt;br /&gt;
&lt;br /&gt;
=== Issues ===&lt;br /&gt;
* Please add any issues with the specification to the separate [[hcalendar-issues]] document.&lt;/div&gt;</summary>
		<author><name>Trovster</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hcalendar&amp;diff=4893</id>
		<title>hcalendar</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hcalendar&amp;diff=4893"/>
		<updated>2006-02-10T17:00:47Z</updated>

		<summary type="html">&lt;p&gt;Trovster: /* New Examples */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= hCalendar =&lt;br /&gt;
&lt;br /&gt;
hCalendar is a simple open, distributed calendaring and events format, based on the  iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]), suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. hCalendar is one of several open [[microformats|microformat]] standards.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Draft Specification ==&lt;br /&gt;
&lt;br /&gt;
=== Editor ===&lt;br /&gt;
[http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc])&lt;br /&gt;
&lt;br /&gt;
=== Authors ===&lt;br /&gt;
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]&lt;br /&gt;
* [http://suda.co.uk/ Brian Suda]&lt;br /&gt;
&lt;br /&gt;
=== Copyright ===&lt;br /&gt;
{{MicroFormatCopyrightStatement2004}}&lt;br /&gt;
&lt;br /&gt;
=== Patents ===&lt;br /&gt;
{{MicroFormatPatentStatement}}&lt;br /&gt;
&lt;br /&gt;
=== Inspiration and Acknowledgments ===&lt;br /&gt;
Thanks to:&lt;br /&gt;
* Adam Bosworth for leading the [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation] which brought together a critical mass of interested parties.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
The iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]), has been broadly interoperably implemented (e.g. Apple's &amp;amp;quot;iCal&amp;amp;quot; application built into MacOSX).&lt;br /&gt;
&lt;br /&gt;
In addition, bloggers often discuss events on their blogs -- upcoming events, writeups of past events, etc.  With just a tad bit of structure, bloggers can discuss events in their blog(s) in such a way that spiders and other aggregators can retrieve such events, automatically convert them to iCalendar, and use them in any iCalendar application or service.&lt;br /&gt;
&lt;br /&gt;
This specification introduces the '''hCalendar''' format, which is a 1:1 representation of the aforementioned iCalendar standard, in semantic XHTML.  Bloggers can both embed hCalendar events directly in their web pages, and style them with CSS to make them appear as desired.  In addition, hCalendar enables applications to retrieve information about such events directly from web pages without having to reference a separate file.&lt;br /&gt;
&lt;br /&gt;
== Semantic XHTML Design Principles ==&lt;br /&gt;
&lt;br /&gt;
{{semantic-xhtml-design-principles}}&lt;br /&gt;
&lt;br /&gt;
== Format ==&lt;br /&gt;
&lt;br /&gt;
=== In General ===&lt;br /&gt;
&lt;br /&gt;
The iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]) forms the basis of hCalendar.&lt;br /&gt;
&lt;br /&gt;
Note: the editor and authors of this specification are tracking the [http://lists.osafoundation.org/pipermail/ietf-calsify/ &amp;amp;quot;iCal-Basic&amp;amp;quot; effort] and intend to base the core hCalendar profile on iCal-Basic. See references for a link to the current draft.&lt;br /&gt;
&lt;br /&gt;
The basic format of hCalendar is to use iCalendar object/property names in lower-case for class names, and to map the nesting of iCalendar objects directly into nested XHTML.&lt;br /&gt;
&lt;br /&gt;
=== More Semantic Equivalents ===&lt;br /&gt;
&lt;br /&gt;
However, for some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:&lt;br /&gt;
* &amp;lt;code&amp;gt;URL&amp;lt;/code&amp;gt; in iCalendar becomes  &amp;lt;code&amp;gt;&amp;lt;a class=&amp;amp;quot;url&amp;amp;quot; href=&amp;amp;quot;...&amp;amp;quot;&amp;gt;...&amp;lt;/a&amp;gt;&amp;lt;/code&amp;gt; inside the element with &amp;lt;code&amp;gt;class=&amp;amp;quot;vevent&amp;amp;quot;&amp;lt;/code&amp;gt; in hCalendar.&lt;br /&gt;
* &amp;lt;code&amp;gt;ATTENDEE&amp;lt;/code&amp;gt; in iCalendar may in hCalendar be represented by an [[hcard]].&lt;br /&gt;
&lt;br /&gt;
=== Singular vs. Plural Properties ===&lt;br /&gt;
&lt;br /&gt;
For properties which are singular (e.g. &amp;amp;quot;N&amp;amp;quot; and &amp;amp;quot;FN&amp;amp;quot; from vCard), the first descendant element with that class should take effect, any others being ignored.&lt;br /&gt;
&lt;br /&gt;
For properties which can be plural (e.g. &amp;amp;quot;TEL&amp;amp;quot; from vCard), each class instance should create a instance of that property.  Plural properties with subtypes (e.g. TEL with WORK, HOME, CELL from vCard) can be optimized to share a common element for the property itself, with each instance of subtype being an appropriately classed descendant of the property element. &lt;br /&gt;
&lt;br /&gt;
=== Human vs. Machine readable ===&lt;br /&gt;
If an &amp;lt;code&amp;gt;&amp;amp;lt;abbr&amp;amp;gt;&amp;lt;/code&amp;gt; element is used for a property, then the '&amp;lt;code&amp;gt;title&amp;lt;/code&amp;gt;' attribute of the &amp;lt;code&amp;gt;&amp;amp;lt;abbr&amp;amp;gt;&amp;lt;/code&amp;gt; element is the value of the property, instead of the contents of the element,  which instead provide a human presentable version of the value.  This specification recommends that such &amp;lt;code&amp;gt;&amp;amp;lt;abbr&amp;amp;gt;&amp;lt;/code&amp;gt; elements be used for the following iCalendar properties:&lt;br /&gt;
* DTSTART, DTEND, DURATION, RDATE, RRULE&lt;br /&gt;
&lt;br /&gt;
== Example ==&lt;br /&gt;
&lt;br /&gt;
Here is a sample event in an iCalendar:&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
BEGIN:VCALENDAR&lt;br /&gt;
PRODID:-//XYZproduct//EN&lt;br /&gt;
VERSION:2.0&lt;br /&gt;
BEGIN:VEVENT&lt;br /&gt;
URL:http://www.web2con.com/&lt;br /&gt;
DTSTART:20051005&lt;br /&gt;
DTEND:20051008&lt;br /&gt;
SUMMARY:Web 2.0 Conference&lt;br /&gt;
LOCATION:Argent Hotel\, San Francisco\, CA&lt;br /&gt;
END:VEVENT&lt;br /&gt;
END:VCALENDAR&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
and an equivalent event in hCalendar format with various elements optimized appropriately.  See [[hcalendar-example1-steps]] for the derivation.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;amp;quot;vevent&amp;amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;a class=&amp;amp;quot;url&amp;amp;quot; href=&amp;amp;quot;http://www.web2con.com/&amp;amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;amp;quot;summary&amp;amp;quot;&amp;gt;Web 2.0 Conference&amp;lt;/span&amp;gt;: &lt;br /&gt;
  &amp;lt;abbr class=&amp;amp;quot;dtstart&amp;amp;quot; title=&amp;amp;quot;2005-10-05&amp;amp;quot;&amp;gt;October 5&amp;lt;/abbr&amp;gt;-&lt;br /&gt;
  &amp;lt;abbr class=&amp;amp;quot;dtend&amp;amp;quot; title=&amp;amp;quot;2005-10-08&amp;amp;quot;&amp;gt;7&amp;lt;/abbr&amp;gt;,&lt;br /&gt;
 at the &amp;lt;span class=&amp;amp;quot;location&amp;amp;quot;&amp;gt;Argent Hotel, San Francisco, CA&amp;lt;/span&amp;gt;&lt;br /&gt;
 &amp;lt;/a&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
which could be displayed as:&lt;br /&gt;
&lt;br /&gt;
[http://www.web2con.com/ Web 2.0 Conference: October 5-7, at the Argent Hotel, San Francisco, CA]&lt;br /&gt;
&lt;br /&gt;
Note 1: The product information is not necessary since hCalendar is an interchange format.  When transforming hCalendar back into iCalendar, the transforming engine should add its own product ID.&lt;br /&gt;
&lt;br /&gt;
Note 2: A surrounding &amp;lt;span class=&amp;amp;quot;vcalendar&amp;amp;quot;&amp;gt; element is optional, and is left out as such.  It is optional since the context of a vcalendar is implied when a vevent is encountered.  The implied context/scope is that of the document.  Authors may explicitly use elements with class=&amp;amp;quot;vcalendar&amp;amp;quot; to wrap sets of vevents that all belong to the same calendar, e.g. when publishing multiple calendars on the same page.&lt;br /&gt;
&lt;br /&gt;
Note 3: The version information is unnecessary in hCalendar markup directly since the version will be defined by the profile of hCalendar that is used/referred to in the 'profile' attribute of the &amp;lt;head&amp;gt; element.&lt;br /&gt;
&lt;br /&gt;
Note 4: ISO8601 dates (required by iCalendar) are not very human friendly.  In addition, the year is often understood implicitly by humans from the context.  Thus &amp;lt;code&amp;gt;&amp;amp;lt;abbr&amp;amp;gt;&amp;lt;/code&amp;gt; elements are used to simultaneously provide a human friendly date and/or time in the visible contents of the element, while placing the respective machine parsable comprehensive ISO8601 datetime in the 'title' attribute.&lt;br /&gt;
The notation YYYY-MM-DD should be used for better readability.&lt;br /&gt;
&lt;br /&gt;
Note 5: The difference between the DTEND ISO8601 date (2005-10-08) and the human readable date (7) is NOT a mistake.  [http://lists.osafoundation.org/pipermail/ietf-calsify/2005-September/000769.html DTEND is exclusive], meaning, that the event ends just before the DTEND. Thus for events which start on one day and end on another day, the DTEND date must be specified as the day after the day that a human would say is the last day of the event.&lt;br /&gt;
&lt;br /&gt;
See [[hcalendar-examples]] for more hCalendar examples&lt;br /&gt;
&lt;br /&gt;
== Examples in the wild ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
The following sites have implemented hCalendar, and thus are a great place to start for anyone looking for examples &amp;amp;quot;in the wild&amp;amp;quot; to try parsing, indexing, organizing etc.  If events on your pages are marked up with hCalendar, feel free to add it to the top of this list.  Once the list grows too big, we'll make a separate wiki page.&lt;br /&gt;
&lt;br /&gt;
=== New Examples ===&lt;br /&gt;
Please add new examples to this section.&lt;br /&gt;
* [http://www.multipack.co.uk The Multipack] features a vevent for the next meeting information.&lt;br /&gt;
* [http://www.stateofflux.com/ State of Flux street art site] has started adding events in hCalendar format&lt;br /&gt;
* The [http://barcamp.org/#BarCamps BarCamp home page lists upcoming BarCamps marked up with hCalenar] and even has a &amp;quot;Subscribe...&amp;quot; link.&lt;br /&gt;
* [http://www.w3.org/2005/12/allgroupoverview.html 2006 W3C Technical Plenary Week] has marked up the schedule and events for the week with hCalendar.&lt;br /&gt;
* [http://www.code4lib.org/2006/schedule code4lib Conference 2006 Schedule] is marked up with hCalendar as [http://www.code4lib.org/node/65 announced on their blog].&lt;br /&gt;
* [http://grouper.ieee.org/groups/754 IEEE 754 Working Group] - trying hCalendar for upcoming meetings.&lt;br /&gt;
* [http://www.pehuen.org/node/494  Elecciones 2005 Chile] - the first spanish language hCalendar event found in the wild.&lt;br /&gt;
* [http://www.codewitch.org/it/2005/11/17/no-creative-commons-no-party/ Giocolando » No Creative Commons? No Party!] is marked up with hCalendar&lt;br /&gt;
* [http://www.cmprofessionals.org/events/calendar.html CM Pros Events Calendar] by Bob Doyle&lt;br /&gt;
* [http://www.midgard-project.org/community/events/ Midgard CMS Event calendar] - as [http://bergie.iki.fi/blog/new-event-calendar-for-midcom.html blogged by Henri Bergius] &lt;br /&gt;
* [http://www.iowamilitaryveteransband.com/schedule/ Iowa Military Veterans Band Schedule] - hCalendar markup [http://weblog.randomchaos.com/archive/2005/10/24/Microformats/ added by Scott Reynen]&lt;br /&gt;
* [http://www.funfairgames.net/weblog/posts/00000011.html Upcoming events on Jason A.R. Moody Amusements Weblog] posted by Jason Moody on 15 Oct 2005. [http://www.funfairgames.net/weblog/index.html His weblog] in general has hCalendar events posted inside the blog posts.&lt;br /&gt;
* [http://tantek.com/microformats/2005/syndicate/tracks-sessions-schedule.html Syndicate - Tracks &amp;amp;amp; Sessions]&lt;br /&gt;
* [http://tantek.com/microformats/2005/web2/program.html Web 2.0 Conference schedule page marked up with hCalendar]&lt;br /&gt;
* [http://www.thisiscmon.com/ C'MON] is a rock band from Canada, and their [http://www.thisiscmon.com/shows/ tour dates] have been marked up by [http://www.d2digitalmedia.com/ Ray Dickman] with hCalendar.&lt;br /&gt;
* [http://ifreebusy.com/ ifreebusy.com] will display freebusy information using hCalendar. See this [http://ifreebusy.com/neiljensen/freebusy/ example].&lt;br /&gt;
* [http://we05.com/ Web Essentials 05] has marked up their [http://we05.com/program.cfm program schedule table with hCalendar], using the 'axis' and 'headers' attributes.&lt;br /&gt;
* [http://www.asdvbonaparte.nl/ ASDV Bonaparte] is a Dutch debating society. Their events calendar has been marked up with the hCalendar conventions.&lt;br /&gt;
* [http://chocnvodka.blogware.com/blog Suw Charman] has marked up [http://suw.org.uk/archives/category/events/ her events] with hCalendar.&lt;br /&gt;
* [http://www.blogbusinesssummit.com/ Blog Business Summit] has published their [http://www.blogbusinesssummit.com/details.htm event details] marked up with hCalendar.&lt;br /&gt;
* [http://evdb.com EVDB], the Events and Venues database, publishes all events with hCalendar and venues with [[hcard|hCard]].  Took them only 15 minutes to implement both!&lt;br /&gt;
* [http://upcoming.org Upcoming.org] publishes all events and lists of events with hCalendar.  Took them only an hour to add hCalendar support to the site.&lt;br /&gt;
* The [http://laughingsquid.com/squidlist/calendar/ Laughing Squid Calendar] events, [http://laughingsquid.com/squidlist/calendar/9949/2005/5/9 e.g. this party], now supports hCalendar.&lt;br /&gt;
* [http://paulschreiber.com/ Paul] Schreiber's [http://concerts.shrub.ca/ Sunnyvale House Concerts] site publishes hCalendar event information for upcoming concerts.  In addition the [http://concerts.shrub.ca/shows Past Shows] page contains hCalendar events for all past concerts.&lt;br /&gt;
* [http://paulschreiber.com/ Paul] Schreiber's [http://iceoasis.shrub.ca/ unofficial schedule site] publishes hCalendar information for upcoming hockey games at [http://www.iceoasis.com/ Ice Oasis]&lt;br /&gt;
* [http://www.complexspiral.com/ Complex Spiral Consulting], both in the &amp;amp;quot;Events&amp;amp;quot; box on left side, and the separate [http://www.complexspiral.com/events/ Events page]. &lt;br /&gt;
* [http://tantek.com/log Tantek's Thoughts], specifically the &amp;amp;quot;Events&amp;amp;quot; roll in the right-most column.&lt;br /&gt;
* [http://suda.co.uk/projects/holidays/ Lesser Known Holidays], a list of holidays on [http://suda.co.uk suda.co.uk] that can be imported via iCal and hCal so you can compare actual transformation versus intended.&lt;br /&gt;
* [http://norman.walsh.name/2005/itinerary/ Norm Walsh's travel schedule] use hCalendar as well as GRDDL.&lt;br /&gt;
* [http://www.policyawareweb.org/2005/ftf2/paw-mtg Policy Aware Web (PAW) Project Meeting] uses hCalendar to record date-related decisions, and uses a vtodo microformat to record action items.&lt;br /&gt;
* The [http://www.kiez-ev.de/ Kiez] is a small cinema and has published its [http://www.kiez-ev.de/programm.htm program] marked up with hCalendar.&lt;br /&gt;
* The [http://lufgi4.informatik.rwth-aachen.de Laboratory for Dependable Distributed Systems] publishes it's [http://lufgi4.informatik.rwth-aachen.de/cfps list of notable CfPs on dependability and security] with hCalendar-todo elements.&lt;br /&gt;
* The [http://laughingsquid.com/laughing-squid-10th-anniversary-party/ Laughing Squid 10th Anniversary Party] has an hcalendar page.&lt;br /&gt;
* SPRACI has hcalendar versions of its nightlife/clubbing/gigs/festivals listings for many cities worldwide - eg: [http://www.spraci.com/listhcalendar.php?parea=sydney&amp;amp;category=all Events in Sydney] (check the [http://www.spraci.com/api/ API] pages in the faq section of [http://www.spraci.com/ SPRACI] for more info about the area/city keywords and category tags to use to get data for your city/categories&lt;br /&gt;
* WWF-Australia events calendars: [http://wwf.org.au/act/events/ What's on], [http://wwf.org.au/act/volunteer/ Volunteer]&lt;br /&gt;
&lt;br /&gt;
=== Examples with some problems ===&lt;br /&gt;
* [http://www.webanalyticsassociation.org/en/calendarevents/search.asp  Web Analytics Association] - hCalendar microformat is in place on all Tendenci sites on the calendar events search page and consolidated list page.&lt;br /&gt;
** WARNINGS&lt;br /&gt;
*** has only dates where there should be datetime's&lt;br /&gt;
*** has abbr's with no title&lt;br /&gt;
*** should probably markup the description --[[User:RyanKing|RyanKing]] 16:04, 6 Jan 2006 (PST)&lt;br /&gt;
* [http://www.bokle.de/ s'Bokle] is a German music pub. Their events calendar has been marked up with hCalendar.&lt;br /&gt;
** improper use of rrule --[[User:RyanKing|RyanKing]] 16:04, 6 Jan 2006 (PST)&lt;br /&gt;
&lt;br /&gt;
== Implementations ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
The following implementations have been developed which either generate or parse hCalendars. If you have an hCalendar implementation, feel free to add it to the top of this list.  Once the list grows too big, we'll make a separate wiki page.&lt;br /&gt;
&lt;br /&gt;
=== Generation ===&lt;br /&gt;
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCalendar and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].&lt;br /&gt;
* [http://www.midgard-project.org/documentation/net-nemein-calendar/ Midgard CMS - net.nemein.calendar] - as [http://bergie.iki.fi/blog/new-event-calendar-for-midcom.html blogged by Henri Bergius] &lt;br /&gt;
* [http://www.decafbad.com/blog/2005/06/08/greasemonkey_magic magic_hcalendar Greasemonkey user script by Les Orchard] - allows easy form entry of an event into any textarea, e.g. into a blog post text area.&lt;br /&gt;
* [http://microformats.org/code/hcalendar/creator microformats.org hCalendar creator]&lt;br /&gt;
* [http://hybernaut.com/upcoming-hcal Drupal Upcoming.org syndication module emits hCalendar]&lt;br /&gt;
* [http://theryanking.com/ Ryan King] has an [http://theryanking.com/microformats/hcalendar-creator.html hCalendar creator].&lt;br /&gt;
&lt;br /&gt;
=== Conversion and consumption ===&lt;br /&gt;
* [http://lifelint.net/ Life Lint Parser] parses hCalendar and produces .ics, .rdf and debugging information and attempts to be more fully compliant to the iCal standard than previous implementations.  It can be used in the same manner as X2V.&lt;br /&gt;
* [http://blog.codeeg.com/tails-firefox-extension/ Tails is a Firefox Extension] that will display the presence of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage.&lt;br /&gt;
* In [http://www.xfytec.com/community/ xfy Community], there are some hCalendar implementations. &amp;quot;hCalendar via RSS&amp;quot; parses an RSS feed, retrieves XHTML documents linked from that feed, and syndicates hCalendars into a calendar view.&lt;br /&gt;
* [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats simple hCalendar parser] by [http://virtuelvis.com/ Arve Bersvendsen]&lt;br /&gt;
* [http://george.hotelling.net/90percent/ George] has built a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script that detects hCalendar events and allows users to easily add them to their calendar application(s)].&lt;br /&gt;
* [http://blogmatrix.blogmatrix.com/ David Janes] has produced a [[Greasemonkey]] [http://www.blogmatrix.com/include/microformat-find.user.js script] that finds many microformat elements, including hCalendar events, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. The hCalendar to vCalendar conversion is done internally within the script. ''This does not work with FireFox 1.5+/GreaseMonkey 0.6.4+.''&lt;br /&gt;
* [http://suda.co.uk/projects/X2V/ X2V] parses hCalendar and produces a .ics (iCalendar) stream.  Note: needs to be updated to track changes in the specification as they occur.&lt;br /&gt;
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] by [[User:DanC]] includes  toICal.xsl and test materials; it works much like xhtml2vcal.xsl in X2V. See also: [http://www.w3.org/2002/12/cal/ RDF Calendar workspace] with icalendar test materials.&lt;br /&gt;
* [http://web.mit.edu/glasser/www/JSCalendar/ JSCalendar] parses hCalendar and produces a displayable HTML table/CSS-based calendar.&lt;br /&gt;
&lt;br /&gt;
Investigation:&lt;br /&gt;
* [http://wiki.mozilla.org/Calendar_Talk:Lightning#hCalendar_publish_and_subscribe_support Mozilla Calendar / Lightning / Sunbird hCalendar support discussion]&lt;br /&gt;
&lt;br /&gt;
=== Potential implementations ===&lt;br /&gt;
&lt;br /&gt;
These are open source projects that could be potentially enhanced to support hCalendar.&lt;br /&gt;
&lt;br /&gt;
* [http://www.k5n.us/webcalendar.php?topic=About WebCalendar]&lt;br /&gt;
* [http://phpicalendar.net/documentation/index.php?title=Main_Page PHP iCalendar]&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
=== Normative References ===&lt;br /&gt;
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]&lt;br /&gt;
* [[hcard|hCard]]&lt;br /&gt;
* [http://www.ietf.org/rfc/rfc2445.txt iCalendar RFC2445]&lt;br /&gt;
&lt;br /&gt;
=== Informative References ===&lt;br /&gt;
* [http://w3.org/TR/REC-CSS1 CSS1]&lt;br /&gt;
* [http://tantek.com/log/2004/09.html#hcalendar hCalendar term introduced and defined on the Web, 20040930]&lt;br /&gt;
* [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation, 20040911]&lt;br /&gt;
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]&lt;br /&gt;
* [http://www.ietf.org/internet-drafts/draft-royer-ical-basic-02.txt iCal-Basic draft 02]&lt;br /&gt;
* Contributed from http://developers.technorati.com/wiki/hCalendar&lt;br /&gt;
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]&lt;br /&gt;
&lt;br /&gt;
==== Related ====&lt;br /&gt;
* [[icalendar-implementations|iCalendar implementations]]&lt;br /&gt;
* [http://lists.osafoundation.org/pipermail/ietf-calsify/ IETF-calsify archives]&lt;br /&gt;
* [http://www.livejournal.com/users/jwz/444651.html jwz - Hula] (required reading)&lt;br /&gt;
* [http://www.jwz.org/doc/groupware.html Groupware Bad by Jamie Zawinski] crystalizes the reason for hCalendar ('''emphasis''' added):&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;amp;quot;Right now people can do that by publishing .ics files, but  it's not trivial to do so, and it's work on the part of other people  to look at them. '''If it's not HTML hanging off our friend's home page  that can be viewed in any browser on a public terminal in a library,  the bar to entry is too high and it's useless.'''&amp;amp;quot;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* [http://muddybranch.thejkgroup.com/ Jason Klemow's blog]&lt;br /&gt;
* [http://www.softwarestudio.org/iCal/2445Issues.html RFC2445 Issues List]&lt;br /&gt;
* [http://ietf.webdav.org/calsify/ CALSIFY WG Links And Resources]&lt;br /&gt;
&lt;br /&gt;
=== Similar Work ===&lt;br /&gt;
* [[XOXO]]&lt;br /&gt;
&lt;br /&gt;
== Discussions ==&lt;br /&gt;
&lt;br /&gt;
This specification is a work in progress.  As additional aspects are discussed, understood, and written, they will be added.  There is a separate document where we are keeping our brainstorms and other explorations relating to hCalendar:&lt;br /&gt;
&lt;br /&gt;
* [[hcalendar-brainstorming]]&lt;br /&gt;
&lt;br /&gt;
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].&lt;br /&gt;
** [http://weblog.infoworld.com/udell/2006/01/11.html#a1368 Moving forward with microformats] by [http://weblog.infoworld.com/udell Jon Udell] provides an hCalendar example and some discussion.&lt;br /&gt;
&lt;br /&gt;
=== Q&amp;amp;A ===&lt;br /&gt;
* If you have any questions about hCalendar, check the [[hcalendar-faq]], and if you don't find answers, add your questions!&lt;br /&gt;
&lt;br /&gt;
=== Issues ===&lt;br /&gt;
* Please add any issues with the specification to the separate [[hcalendar-issues]] document.&lt;/div&gt;</summary>
		<author><name>Trovster</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hcard&amp;diff=4894</id>
		<title>hcard</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hcard&amp;diff=4894"/>
		<updated>2006-02-10T16:59:16Z</updated>

		<summary type="html">&lt;p&gt;Trovster: /* New Examples */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= hCard =&lt;br /&gt;
&lt;br /&gt;
hCard is a simple, open, distributed contact information format for people, companies, and organizations, which is suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. hCard is a 1:1 representation of the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in XHTML, one of several open [[microformats|microformat]] standards.&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Draft Specification ==&lt;br /&gt;
&lt;br /&gt;
=== Editor ===&lt;br /&gt;
[http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]&lt;br /&gt;
&lt;br /&gt;
=== Authors ===&lt;br /&gt;
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]&lt;br /&gt;
* [http://suda.co.uk/ Brian Suda]&lt;br /&gt;
&lt;br /&gt;
=== Copyright ===&lt;br /&gt;
{{MicroFormatCopyrightStatement2004}}&lt;br /&gt;
&lt;br /&gt;
=== Patents ===&lt;br /&gt;
{{MicroFormatPatentStatement}}&lt;br /&gt;
&lt;br /&gt;
=== Inspiration and Acknowledgments ===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), has been broadly interoperably implemented (e.g. Apple's &amp;quot;Address Book&amp;quot; application built into MacOSX).&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
This specification introduces the '''hCard''' format, which is a 1:1 representation of the aforementioned vCard standard, in semantic XHTML.  Bloggers can both embed vCards directly in their web pages, and style them with CSS to make them appear as desired.  In addition, hCard enables applications to retrieve information about such vCards directly from web pages without having to reference a separate file.&lt;br /&gt;
&lt;br /&gt;
Use the [http://microformats.org/code/hcard/creator hCard creator], copy the HTML code it generates to your blog or website to publish your contact info.&lt;br /&gt;
&lt;br /&gt;
== Semantic XHTML Design Principles ==&lt;br /&gt;
{{semantic-xhtml-design-principles}}&lt;br /&gt;
&lt;br /&gt;
== Format ==&lt;br /&gt;
=== In General ===&lt;br /&gt;
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) forms the basis of hCard.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== More Semantic Equivalents ===&lt;br /&gt;
However, for some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:&lt;br /&gt;
* &amp;lt;code&amp;gt;URL&amp;lt;/code&amp;gt; in vCard becomes  &amp;lt;code&amp;gt;&amp;lt;a class=&amp;quot;url&amp;quot; href=&amp;quot;...&amp;quot;&amp;gt;...&amp;lt;/a&amp;gt;&amp;lt;/code&amp;gt; inside the element with &amp;lt;code&amp;gt;class=&amp;quot;vcard&amp;quot;&amp;lt;/code&amp;gt; in hCard.&lt;br /&gt;
* Similarly, &amp;lt;code&amp;gt;EMAIL&amp;lt;/code&amp;gt; in vCard becomes &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;a class=&amp;quot;email&amp;quot; href=&amp;quot;mailto:...&amp;quot;&amp;gt;...&amp;lt;/a&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
* &amp;lt;code&amp;gt;PHOTO&amp;lt;/code&amp;gt; in vCard becomes &amp;lt;code&amp;gt;&amp;lt;img class=&amp;quot;photo&amp;quot; src=&amp;quot;...&amp;quot; alt=&amp;quot;Photo of ...&amp;quot; /&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Singular vs. Multivalued Properties ===&lt;br /&gt;
&lt;br /&gt;
For properties which are singular (e.g. &amp;quot;N&amp;quot; and &amp;quot;FN&amp;quot;), the first descendant element with that class should take effect, any others being ignored.&lt;br /&gt;
&lt;br /&gt;
For properties which can be plural (e.g. &amp;quot;TEL&amp;quot;), each class instance should create a instance of that property.&lt;br /&gt;
&lt;br /&gt;
==== Plural Properties Singularized ====&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Human vs. Machine readable ===&lt;br /&gt;
&lt;br /&gt;
If an &amp;lt;code&amp;gt;&amp;amp;lt;abbr&amp;gt;&amp;lt;/code&amp;gt; element is used for a property, then the '&amp;lt;code&amp;gt;title&amp;lt;/code&amp;gt;' attribute of the &amp;lt;code&amp;gt;&amp;amp;lt;abbr&amp;gt;&amp;lt;/code&amp;gt; element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value.  &lt;br /&gt;
&lt;br /&gt;
Similarly, if an &amp;lt;code&amp;gt;&amp;amp;lt;img&amp;gt;&amp;lt;/code&amp;gt; element is used for one or more properties, it must be treated as follows:&lt;br /&gt;
# For the &amp;quot;PHOTO&amp;quot; property and any other property that takes a URL as its value, the &amp;lt;code&amp;gt;src=&amp;quot;...&amp;quot;&amp;lt;/code&amp;gt; attribute provides the property value.&lt;br /&gt;
# For other properties, the &amp;lt;code&amp;gt;&amp;amp;lt;img&amp;gt;&amp;lt;/code&amp;gt; element's '&amp;lt;code&amp;gt;alt&amp;lt;/code&amp;gt;' attribute is the value of the property.&lt;br /&gt;
&lt;br /&gt;
=== Value excerpting ===&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;&amp;lt;code&amp;gt;value&amp;lt;/code&amp;gt;&amp;quot; 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:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;home&amp;lt;/span&amp;gt;:&lt;br /&gt;
 &amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt;+1.415.555.1212&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This hCard fragment could be displayed as:&lt;br /&gt;
&lt;br /&gt;
 home: +1.415.555.1212&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Property Exceptions ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
# '''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 &amp;lt;code&amp;gt;&amp;lt;title&amp;gt;&amp;lt;/code&amp;gt; element in (X)HTML documents) to construct the NAME property, MAY output a PROFILE value of &amp;quot;&amp;lt;code&amp;gt;VCARD&amp;lt;/code&amp;gt;&amp;quot; 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 &amp;quot;3.0&amp;quot; (without quotes) per RFC2426 Section 3.6.9.&lt;br /&gt;
&lt;br /&gt;
=== Implied &amp;quot;N&amp;quot; Optimization ===&lt;br /&gt;
&lt;br /&gt;
Although vCard requires that the &amp;quot;N&amp;quot; property be present, the authors of the vCard specification (RFC 2426) themselves do not include &amp;quot;N&amp;quot; properties in their vCards near the end of the spec (p.38).  This apparent contradiction can be resolved by simply allowing the &amp;quot;FN&amp;quot; property to imply &amp;quot;N&amp;quot; property values in typical cases provided in the spec.  We do so explicitly in hCard.&lt;br /&gt;
&lt;br /&gt;
If the value of the &amp;quot;FN&amp;quot; property is exactly two words (separated by whitespace.), and there is no explicit &amp;quot;N&amp;quot; property, then the &amp;quot;N&amp;quot; property is inferred from the &amp;quot;FN&amp;quot; property.  For &amp;quot;FN&amp;quot;s with either one word or three or more, then the author MUST explicitly markup the &amp;quot;N&amp;quot;, except for the organization contact info case, [http://microformats.org/wiki/hcard#Organization_Contact_Info see below] for that.&lt;br /&gt;
&lt;br /&gt;
# The content of &amp;quot;FN&amp;quot; is broken into two &amp;quot;words&amp;quot; separated by whitespace.&lt;br /&gt;
# The ''first'' word of the &amp;quot;FN&amp;quot; is interpreted as the &amp;quot;Given Name&amp;quot; for the &amp;quot;N&amp;quot; property.&lt;br /&gt;
# The ''second/last'' word of the &amp;quot;FN&amp;quot; is interpreted as the &amp;quot;Family Name&amp;quot; for the &amp;quot;N&amp;quot; property.&lt;br /&gt;
# Exception: If the first word ends in a &amp;quot;,&amp;quot; comma OR if the second word is a single character (optionally followed by a period &amp;quot;.&amp;quot;), then the first word (minus the comma at the end if any) is interpreted as the &amp;quot;Family Name&amp;quot; and the second word is interpreted as the &amp;quot;Given Name&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
This allows simplification in the typical case of people stating their firstname space lastname, or lastname comma firstname, or lastname comma firstinitial, or lastname space firstinitial.&lt;br /&gt;
&lt;br /&gt;
==== Organization Contact Info ====&lt;br /&gt;
&lt;br /&gt;
Contact info for a company or organization is a special case of the implied &amp;quot;N&amp;quot; optimization.&lt;br /&gt;
 &lt;br /&gt;
If the &amp;quot;FN&amp;quot; and &amp;quot;ORG&amp;quot; properties have the exact same value (typically because they are set on the same element, e.g. class=&amp;quot;fn org&amp;quot;), 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 &amp;quot;N&amp;quot; property, or set it (and any sub-properties) explicitly to the empty string &amp;quot;&amp;quot;.  Thus parsers should handle the missing &amp;quot;N&amp;quot; property in this case by implying empty values for all the &amp;quot;N&amp;quot; sub-properties.&lt;br /&gt;
&lt;br /&gt;
=== Implied &amp;quot;organization-name&amp;quot; Optimization ===&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;ORG&amp;quot; property has two subproperties, organization-name and organization-unit. Very often authors only publish the organization-name.  Thus if an &amp;quot;ORG&amp;quot; property has no &amp;quot;organization-name&amp;quot; inside it, then its entire contents MUST be treated as the &amp;quot;organization-name&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== Root Class Name ===&lt;br /&gt;
&lt;br /&gt;
The root class name for an hCard is &amp;quot;vcard&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== Property List ===&lt;br /&gt;
&lt;br /&gt;
This is the list of properties (and subproperties, in parantheses, like this) in hCard, taken from vCard:&lt;br /&gt;
&lt;br /&gt;
* fn, n (family-name, given-name, additional-name, honorific-prefix, honorific-suffix), nickname, sort-string&lt;br /&gt;
* url, email (type, value), tel (type, value)&lt;br /&gt;
* adr (post-office-box, extended-address, street-address, locality, region, postal-code, country-name, type, value), label&lt;br /&gt;
* geo (latitude, longitude), tz&lt;br /&gt;
* photo, logo, sound, bday&lt;br /&gt;
* title, role, org (organization-name, organization-unit)&lt;br /&gt;
* category, note&lt;br /&gt;
* class, key, mailer, uid, rev&lt;br /&gt;
==== type subproperty values ====&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;Home&amp;quot; is the same as &amp;quot;home&amp;quot;, as well as multivalued, e.g. a tel can be home and preferred:&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Home&amp;lt;/span&amp;gt; (&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;pref&amp;lt;/span&amp;gt;erred):&lt;br /&gt;
 &amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt;+1.415.555.1212&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following lists are ''informative''. See RFC2426 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.&lt;br /&gt;
&lt;br /&gt;
* adr type: INTL, POSTAL, PARCEL, WORK, dom, home, pref&lt;br /&gt;
* tel type: VOICE, home, msg, work, pref, fax, cell, video, pager, bbs, modem, car, isdn, pcs&lt;br /&gt;
* email type: INTERNET, x400, pref, &amp;quot;other IANA registered address types&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== XMDP Profile ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Parsing Details ===&lt;br /&gt;
&lt;br /&gt;
See [[hcard-parsing|hCard parsing]].&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
&lt;br /&gt;
This section is informative.&lt;br /&gt;
&lt;br /&gt;
=== Sample vCard ===&lt;br /&gt;
&lt;br /&gt;
Here is a sample vCard:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
BEGIN:VCARD&lt;br /&gt;
VERSION:3.0&lt;br /&gt;
N:Çelik;Tantek&lt;br /&gt;
FN:Tantek Çelik&lt;br /&gt;
URL:http://tantek.com&lt;br /&gt;
ORG:Technorati&lt;br /&gt;
END:VCARD&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and an equivalent in hCard with various elements optimized appropriately.  See [[hcard-example1-steps| hCard Example 1]] for the derivation. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;a class=&amp;quot;url fn&amp;quot; href=&amp;quot;http://tantek.com/&amp;quot;&amp;gt;Tantek Çelik&amp;lt;/a&amp;gt;&lt;br /&gt;
 &amp;lt;div class=&amp;quot;org&amp;quot;&amp;gt;Technorati&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This hCard might be displayed as:&lt;br /&gt;
&lt;br /&gt;
[http://tantek.com/ Tantek Çelik]&amp;lt;br /&amp;gt;&lt;br /&gt;
Technorati&lt;br /&gt;
&lt;br /&gt;
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 &amp;lt;head&amp;gt; element.&lt;br /&gt;
&lt;br /&gt;
=== More Examples ===&lt;br /&gt;
&lt;br /&gt;
See [[hcard-examples]] for more examples, including all examples from vCard RFC 2426 converted into hCard.&lt;br /&gt;
&lt;br /&gt;
== Examples in the wild ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
The following sites have published hCards, and thus are a great place to start for anyone looking for examples &amp;quot;in the wild&amp;quot; to try parsing, indexing, organizing etc.  If you have an hCard on your own page, feel free to add it to the top of this list.  Once the list grows too big, we'll make a separate wiki page.&lt;br /&gt;
&lt;br /&gt;
=== New Examples ===&lt;br /&gt;
Please add new examples to this section.&lt;br /&gt;
&lt;br /&gt;
* [http://www.multipack.co.uk The Multipack] has numerous hCards, especially on the [http://www.multipack.co.uk/members/ members page], as well as the next meeting information.&lt;br /&gt;
* [http://deadringrancor.livejournal.com/ Justin McDowell] used an hCard when [http://deadringrancor.livejournal.com/221332.html referring to a person in his blog post]&lt;br /&gt;
* [http://davecardwell.co.uk/cv/ Dave Cardwell] has included his hCard in his Curriculum Vitae.&lt;br /&gt;
* [http://blog.usweb.com/ Shaun Shull] has written a great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], and has included his [[hcard|hCard]] as one of the examples.&lt;br /&gt;
* [http://www.thefutureoftheweb.com/ Jesse Skinner] has written a simple [http://www.thefutureoftheweb.com/blog/2006/1/hcard tutorial with examples]&lt;br /&gt;
* [http://www.w3.org/2005/12/allgroupoverview.html 2006 W3C Technical Plenary Week] has marked up the venue, contacts, and program committee members all with hCard.&lt;br /&gt;
* [http://www.avf-nexus.co.uk AVF-Nexus] have a hCard on their [http://www.avf-nexus.co.uk/contact/ contact page] - (by [http://creation.uk.com Creation&amp;quot;])&lt;br /&gt;
* [http://www.thefantasticos.com/andrew/ Andrew White] posted [http://www.thefantasticos.com/andrew/index.php/my-hcard/ his hCard] and [http://www.thefantasticos.com/andrew/index.php/62/microformats-the-should-have-been-obvious-web-dev-tool/ blogged about it].&lt;br /&gt;
* [http://www.2sheds.ru Oleg &amp;quot;2sheds&amp;quot; Kourapov] in his [http://www.2sheds.ru/blog/ blog] ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog X2V]) has turned personal profile into hCard ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/hcard.html X2V]) and his blogroll - into combination XFN/hCards ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/friends.html X2V])&lt;br /&gt;
* [http://www.approveddesign.co.uk Approved Design Consultancy] have a hCard on their [http://www.approveddesign.co.uk/about/contact/ contact page] as well as on their [http://www.approveddesign.co.uk/about/people/ people section] - (by [http://creation.uk.com Creation&amp;quot;])&lt;br /&gt;
* [http://weblog.200ok.com.au/ Ben Buchanan] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&amp;amp;format=search Colin Morris] have [http://weblog.200ok.com.au/2006/01/griffith-phonebook-adds-hcard-and.html implemented hCards and vCards] for the [http://www.griffith.edu.au Griffith University] [http://www.griffith.edu.au/find/content_phonebook.html online phone book]. Eg. [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=ben+buchanan&amp;amp;format=search Ben's vCard] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&amp;amp;format=search Colin's vCard]&lt;br /&gt;
* WWF-Australia [http://wwf.org.au/about/contactdetails/ contact details page]&lt;br /&gt;
&lt;br /&gt;
=== Examples ===&lt;br /&gt;
* [http://thoughtport.blogspot.com/ Aiden Kenny] hasn't published his hCard yet, but he has [http://thoughtport.blogspot.com/2005/07/elemental-particles-of-web.html published his hCard icon]: http://photos1.blogger.com/blogger/4224/444/320/AK-Hcard-icon.gif&lt;br /&gt;
* [http://thedredge.org Andy Hume] uses the hcard format to mark-up the names and URLs of commentors on his blog. &lt;br /&gt;
* [http://www.bidclix.com/ BidClix]'s [http://www.bidclix.com/AboutContact.html Contact BidClix] page has it's ''contact info'' marked up with an hCard.&lt;br /&gt;
* [http://suda.co.uk/ Brian Suda] has managed to embed a photo in [http://suda.co.uk/contact/ his hCard] through the [http://www.ietf.org/rfc/rfc2397.txt data uri scheme] by converting the image to BASE64 code. View the Source to see how this is accomplished. [http://suda.co.uk/projects/X2V/get-vcard.php?uri=http%3A//suda.co.uk/contact/ The X2V link] will extract the image and encode it for a vCard which will be displayed in some address book applications.&lt;br /&gt;
* [http://cinematreasures.org Cinema Treasures] uses hCard to markup venue information for 10,000+ movie theaters.&lt;br /&gt;
* [http://www.w3.org/People/Connolly/events/ Dan Connolly's index of events and talks] has hCards for many of the people he has met at those events.&lt;br /&gt;
* [http://doncrowley.blogspot.com/ Don Crowley] has published [http://www.crowley.nl/hcard.html his hCard] as well as a nifty hCard button: http://www.crowley.nl/images/hcard.png&lt;br /&gt;
* [http://loadaveragezero.com/hnav/contact.php Douglas W. Clifton] added all types of contact information&lt;br /&gt;
* [http://evdb.com EVDB], the Events and Venues Database, publishes all venue detail pages with embedded hCards.&lt;br /&gt;
* [http://www.iowamilitaryveteransband.com/members/ Iowa Military Veterans Band Contacts] - 95 hCards [http://weblog.randomchaos.com/archive/2005/10/24/Microformats/ marked up by Scott Reynen]&lt;br /&gt;
* [http://JackWolfgang.blogspot.com Jack L. Wolfgang II] has [http://jack.randomata.com/resume/ converted the addresses in his resume to hCards].&lt;br /&gt;
* [http://www.efas.fupl.asso.fr/efas/_Mathieu-Drouet_.html Mathieu Drouet] and [http://www.efas.fupl.asso.fr/efas/_Annie-Leger_.html Annie Leger] both have hCards&lt;br /&gt;
* [http://www.ndunn.com Neil Dunn] has published his rather [http://www.ndunn.com/2005/10/7/hCard good looking hCard]&lt;br /&gt;
* [http://www.oliverbrown.me.uk/ Oliver Brown] has published his hCard.&lt;br /&gt;
* [http://www.paradigmproductions.org/contact/ Paradigm Productions] published a vcard as a ul (marked up by [http://www.linkingarts.com/ Peter Jacobson])&lt;br /&gt;
* [http://www.splintered.co.uk/ Patrick H. Lauke] has marked up [http://www.splintered.co.uk/about/ his contact info with hCard].&lt;br /&gt;
* [http://blah Paul Schreiber has published his hCard on [http://paulschreiber.com/about/?contact his about page].&lt;br /&gt;
* [http://paulschreiber.com/blog/ Paul Schreiber]'s [http://concerts.shrub.ca/ Sunnyvale House Concerts] site publishes hCards for upcoming artists, as well as an hCard for the page itself.  In addition the [http://concerts.shrub.ca/shows Past Shows] page contains hCards for all past artists.&lt;br /&gt;
* [http://www.paulmichaelsmith.com/blog/hcard.htm Paul Smith] has created an hCard page which is Human Readable, and a link to X2V passing the same hCard page to generate a vCard.&lt;br /&gt;
* [http://www.windley.com/archives/2005/07/hcards_trying_o.shtml Phil Windley has published] [http://phil.windley.org/hcard.html his hCard].&lt;br /&gt;
* [http://www.go-curiosity.com/about.htm Piercarlo Slavazza] has published an hCard.&lt;br /&gt;
* [http://zooibaai.nl/ Rob Mientjes] has published his hCard on [http://zooibaai.nl/about/ his about page].&lt;br /&gt;
* [http://rbach.priv.at/Contact Robert Bachmann] has published his hCard and [http://rbach.priv.at/Images/hcard a button].&lt;br /&gt;
* [http://blah Scott Reynen has published his hCard on [http://www.randomchaos.com/document.php?source=scott_reynen his profile page].&lt;br /&gt;
* [http://www.stackframe.com/ StackFrame, LLC] has published [http://www.stackframe.com/people/ employee] and [http://www.stackframe.com/contact/ general] contact information as hCards.&lt;br /&gt;
* [http://www.wolfsreign.com Steven Ametjan] has published his hCard on [http://www.wolfsreign.com/about/ his about page].&lt;br /&gt;
* [http://tantek.com/microformats/2005/syndicate/speakers-list.html Syndicate - Speaker List] as a set of hCards&lt;br /&gt;
* [http://tagcamp.org/index.cgi?ContactList TagCamp contact list]&lt;br /&gt;
* [http://tantek.com/log Tantek's Thoughts] includes an inline author hCard at the bottom of the page.&lt;br /&gt;
* [http://technorati.com/ Technorati]'s [http://www.technorati.com/about/ About page] lists their '''Media Contact'''&lt;br /&gt;
* [http://www.deadringerart.com/ The Brothers McDowell] have hCards at their Contact page.&lt;br /&gt;
* [http://twinsparc.com/ Twinsparc] put an hCard in the header and footer of all their pages.&lt;br /&gt;
* [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 Conference speakers page marked up with hCard]&lt;br /&gt;
* [http://we05.com/ Web Essentials 05] marked up all their [http://we05.com/presenters.cfm presenters with hCard].&lt;br /&gt;
&lt;br /&gt;
=== Examples with some problems ===&lt;br /&gt;
* [http://gbraad.nl/ Gerard Braad] has published an example on his [http://gbraad.nl/site/?p=profile profile] page that is almost consistent with his original [http://gbraad.nl/files/gbraad.vcf vCard] file. Also progress is made for transforming his [http://files.gbraad.nl/foaf.rdf FoaF] file to a hCard encoded representation. (also done for my spouse:[http://spouse.gbraad.nl/site/?p=profile Yong Yuan])&lt;br /&gt;
** (2005-09-27) PASSED, PASSED&lt;br /&gt;
** WARNINGS&lt;br /&gt;
*** uses 'n given-name' and 'n family-name' instead of nesting the given- and family- names inside the 'n'&lt;br /&gt;
*** has one 'tel' value with a bunch of values stuffed in&lt;br /&gt;
*** probably more problems --[[User:RyanKing|RyanKing]] 17:19, 5 Jan 2006 (PST)&lt;br /&gt;
* [http://www.kerihenare.com/ Keri Henare] has marked up his [http://www.kerihenare.com/contact/ contact info page] with hCard.&lt;br /&gt;
** (2005-09-27) PASSED&lt;br /&gt;
** (2005-11-01) hCard completely rewritten&lt;br /&gt;
** WARNING - type subproperty in classname&lt;br /&gt;
* [http://kinrowan.net/ Cori Schlegel] [http://kinrowan.net/blog/wp/archives/2005/07/08/a-problem-with-the-structured-blogging-plug-in-for-wordpress/ discusses how he has updated] [http://kinrowan.net/blog/contact his contact page with hCard]&lt;br /&gt;
** INVALID - using 'prefix' instead of 'honorific-prefix' and type's in classnames (in both adr and tel) and has two photo's (the second could be 'logo') --[[User:RyanKing|RyanKing]] 15:15, 5 Jan 2006 (PST)&lt;br /&gt;
* The good ship [http://styrheim.com/test/leonid.html Leonid Miloslavskiy] spotted in the North Atlantic&lt;br /&gt;
** INVALID  --[[User:RyanKing|RyanKing]] 00:50, 27 Oct 2005 (PDT)&lt;br /&gt;
*** class=&amp;quot;family&amp;quot; should probably be family-name&lt;br /&gt;
*** the &amp;quot;n&amp;quot; property is missing and the &amp;quot;n&amp;quot; optimization can't be applied&lt;br /&gt;
*** the first geo propery is empty, the second one is invalid (ie, it doesn't contain lat/long)&lt;br /&gt;
* [http://landsbank.fo/#hCard Landsbanki Føroya]&lt;br /&gt;
** INVALID - using embedded rdf/xml invalidly&lt;br /&gt;
* [http://chrischerry.name/blog/contact/ Chris Cherry's contact page with his hCard]&lt;br /&gt;
** WARNING - uses class=&amp;quot;cell&amp;quot; instead of &amp;amp;lt;span class=&amp;quot;type&amp;quot;&amp;amp;gt;cell&amp;amp;lt;/span&amp;amp;gt;&lt;br /&gt;
* [http://www.bath.ac.uk/contact/ University of Bath] Person Finder results are encoded with hCards so you can easily create a vCard from any result. &lt;br /&gt;
** ERROR - attempt to use Implied-N optimization where that's not possible. --[[User:RyanKing|RyanKing]] 14:29, 5 Jan 2006 (PST)&lt;br /&gt;
** Error appears for external users only. Won't be fixed any time soon. -- [[User:PhilWilson|PhilWilson]] 00:03, 28 Jan 2006 (GMT)&lt;br /&gt;
* [http://richi.co.uk/blog/2005/12/structured-blogging.html Richi Jennings] has put up his attempt&lt;br /&gt;
** INVALID, missing FN --[[User:RyanKing|RyanKing]] 12:47, 5 Jan 2006 (PST)&lt;br /&gt;
* [http://www.shiftingpixel.com/about/ shifting pixel photoblog] has published an hCard.&lt;br /&gt;
** &amp;quot;organization_name&amp;quot; should be &amp;quot;organization-name&amp;quot; (s/_/-/), otherwise good --[[User:RyanKing|RyanKing]] 14:01, 5 Jan 2006 (PST)&lt;br /&gt;
&lt;br /&gt;
== Implementations ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
The following implementations have been developed which either generate or parse hCards. If you have an hCard implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.&lt;br /&gt;
&lt;br /&gt;
* [http://blog.codeeg.com/tails-firefox-extension/ Tails is a Firefox Extension] that will display the presence and details of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage.&lt;br /&gt;
* [http://www.stripytshirt.co.uk/features/firefox/smartzilla Smartzilla is a Firefox Extension] that finds hCards on web pages and lets you add them to your addressbook.&lt;br /&gt;
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCard and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].&lt;br /&gt;
* There is [http://flickr.com/photos/factoryjoe/68755089/ evidence of built-in hCard support in the Konqueror browser].  Specifically, Konqueror 3.5, in KDE 3.5 (kubuntu Breezy w/ update).&lt;br /&gt;
* There is [http://tagcamp.org/index.cgi?ContactList evidence of a kwiki plugin for hCards].  Update: the [http://svn.kwiki.org/cwest/Kwiki-hCard/ hCard kwiki plugin svn repository].  See the [http://microwiki.caseywest.com/index.cgi?hCard documentation of the hCard kwiki plugin].&lt;br /&gt;
* [http://suda.co.uk/projects/X2V/ X2V] is a bookmarklet that parses hCard and produces a .vcf (vCard) stream.  Note: needs to be updated as the spec is refined&lt;br /&gt;
* [http://www.stripytshirt.co.uk Duncan Walker] has built [http://www.stripytshirt.co.uk/features/firefox/smartzilla a Firefox extension] that gets hCard data from a webpage, uses Brian Suda's XSL (locally) to transform it to vcard format and opens the resulting .vcf file.&lt;br /&gt;
* [http://george.hotelling.net/90percent/ George] has written a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script] that detects hCards and allows users to easily add them to their address book application.  Relies on the X2V web service to do the conversion.&lt;br /&gt;
* [http://blogmatrix.blogmatrix.com/ David Janes] has written a [[Greasemonkey]] [http://www.blogmatrix.com/include/microformat-find.user.js script] that finds many microformat elements, including hCards, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003376 provides a popup menu of actions]. The hCard to vCard conversion is done internally within the script. ''This does not work with FireFox 1.5+/GreaseMonkey 0.6.4+.''&lt;br /&gt;
* [http://diveintomark.org/ Mark Pilgrim] has also written an [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser Greasemonkey user script].  It is self-contained and does not rely on the X2V web service.&lt;br /&gt;
* [http://www.oliverbrown.me.uk/2005/09/03/a-working-microformats-extension-to-simplexml/ Oliver Brown] has written an &amp;quot;extension&amp;quot; to [http://www.php.net/simplexml SimpleXML] that gives simple access to hCard information in PHP 5.&lt;br /&gt;
* [http://thedredge.org/ Andrew D. Hume] has built a system (Wordpress plugin?) for [http://thedredge.org/2005/06/using-hcards-in-your-blog/ using hcards in your blog] to represent people leaving comments on blog posts.&lt;br /&gt;
* The [http://tantek.com/microformats/hcard-creator.html hCard creator] is a very simple, yet illustrative, open source user interface / form / script which creates an hCard in real-time as you type in a set of contact information. &lt;br /&gt;
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate hCard information ([http://ietf.org/rfc/rfc2629 RFC2629] is an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])&lt;br /&gt;
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - Open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards. &lt;br /&gt;
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] is a collection of palmpilot and sidekick tools. It includes X2V derivatives xhtml2hcard.xsl and toICal.xsl plus some [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest] materials&lt;br /&gt;
* [http://www.openpsa.org/ OpenPsa 2.x] CRM application uses hCard for all person listings. The widget is [http://www.midgard-project.org/midcom-permalink-922834501b71daad856f35ec593c7a6d reusable across Midgard CMS]&lt;br /&gt;
* [http://www.metonymie.com Emiliano Martínez Luque] has written an experimental [http://www.metonymie.com/hCard_extract/app.html hCard finder and structured search application] that finds hCards within a given set of URLs and returns the ones that match the specified search criteria.&lt;br /&gt;
&lt;br /&gt;
== Additional Applications ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
There are numerous potential additional uses and applications for hCards on the Web.  The following are merely a few thoughts and possibilities that folks have come up with:&lt;br /&gt;
&lt;br /&gt;
* As an open standard/format for [http://www.gravatar.com/ Gravatars].&lt;br /&gt;
* Marking up individual authors of blog posts on a group blog&lt;br /&gt;
* Marking up people's names and URLs in a blogroll&lt;br /&gt;
* Any reference to people in blog posts (e.g. when citing them, or referencing them, or describing them, by name).&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
=== Normative References ===&lt;br /&gt;
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]&lt;br /&gt;
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426]&lt;br /&gt;
&lt;br /&gt;
=== Informative References ===&lt;br /&gt;
* [http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426]&lt;br /&gt;
* [http://w3.org/TR/REC-CSS1 CSS1]&lt;br /&gt;
* [http://tantek.com/log/2004/09.html#hcard hCard term introduced and defined on the Web, 20040930]&lt;br /&gt;
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]&lt;br /&gt;
* Contributed from http://developers.technorati.com/wiki/hCard.&lt;br /&gt;
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]&lt;br /&gt;
&lt;br /&gt;
==== Specifications That Use hCard ====&lt;br /&gt;
* [[adr]]&lt;br /&gt;
* [[geo]]&lt;br /&gt;
* [[hcalendar|hCalendar]]&lt;br /&gt;
* [[hreview|hReview]]&lt;br /&gt;
&lt;br /&gt;
==== Similar Work ====&lt;br /&gt;
* [http://www.intertwingly.net/wiki/pie/PaceBetterPersonElement Atom PaceBetterPersonElement]&lt;br /&gt;
* [http://www.jabber.org/jeps/jep-0054.html JEP-0054: vcard-temp]&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
* [[hcard-profile|hCard profile]] - The XMDP profile for hCard&lt;br /&gt;
&lt;br /&gt;
This 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.&lt;br /&gt;
&lt;br /&gt;
* [[hcard-brainstorming|hCard Brainstorming]] - where we are keeping our brainstorms and other explorations relating to hCard&lt;br /&gt;
* [[hcard-tests|hCard tests]] - a wiki page with actual embedded hCards to try parsing.&lt;br /&gt;
* [[hcard-faq|hCard FAQ]] - If you have any questions about hCard, check here, and if you don't find answers, add your questions!&lt;br /&gt;
* [[hcard-issues|hCard issues]] - Please add any issues with the specification to the issues page.&lt;br /&gt;
&lt;br /&gt;
== Further Reading ==&lt;br /&gt;
* [http://www.digital-web.com/articles/microformats_primer/ Digital Web Magazine: Microformats Primer] by Garrett Dimon has a good intro to hCard&lt;br /&gt;
* [http://24ways.org/advent/practical-microformats-with-hcard Practical Microformats with hCard] by Drew McLellan&lt;br /&gt;
* [http://thedredge.org/ Andrew D. Hume] has written a blog post on [http://usabletype.com/articles/2005/usable-microformats/ usable microformats] which discusses hCard&lt;br /&gt;
* [http://www.thefutureoftheweb.com/blog/2006/1/hcard Jesse Skinner's introduction to hCard]&lt;br /&gt;
* [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.&lt;br /&gt;
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page] and the [http://technorati.com/tags/hcard hCard tag]&lt;/div&gt;</summary>
		<author><name>Trovster</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hcard&amp;diff=4153</id>
		<title>hcard</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hcard&amp;diff=4153"/>
		<updated>2006-01-14T23:43:49Z</updated>

		<summary type="html">&lt;p&gt;Trovster: /* New Examples */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= hCard =&lt;br /&gt;
&lt;br /&gt;
hCard is a simple, open, distributed contact information format for people, companies, and organizations, which is suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. hCard is a 1:1 representation of the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in XHTML, one of several open [[microformats|microformat]] standards.&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Draft Specification ==&lt;br /&gt;
&lt;br /&gt;
=== Editor ===&lt;br /&gt;
[http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]&lt;br /&gt;
&lt;br /&gt;
=== Authors ===&lt;br /&gt;
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]&lt;br /&gt;
* [http://suda.co.uk/ Brian Suda]&lt;br /&gt;
&lt;br /&gt;
=== Copyright ===&lt;br /&gt;
{{MicroFormatCopyrightStatement2004}}&lt;br /&gt;
&lt;br /&gt;
=== Patents ===&lt;br /&gt;
{{MicroFormatPatentStatement}}&lt;br /&gt;
&lt;br /&gt;
=== Inspiration and Acknowledgments ===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), has been broadly interoperably implemented (e.g. Apple's &amp;quot;Address Book&amp;quot; application built into MacOSX).&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
This specification introduces the '''hCard''' format, which is a 1:1 representation of the aforementioned vCard standard, in semantic XHTML.  Bloggers can both embed vCards directly in their web pages, and style them with CSS to make them appear as desired.  In addition, hCard enables applications to retrieve information about such vCards directly from web pages without having to reference a separate file.&lt;br /&gt;
&lt;br /&gt;
Use the [http://microformats.org/code/hcard/creator hCard creator], copy the HTML code it generates to your blog or website to publish your contact info.&lt;br /&gt;
&lt;br /&gt;
== Semantic XHTML Design Principles ==&lt;br /&gt;
{{semantic-xhtml-design-principles}}&lt;br /&gt;
&lt;br /&gt;
== Format ==&lt;br /&gt;
=== In General ===&lt;br /&gt;
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) forms the basis of hCard.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== More Semantic Equivalents ===&lt;br /&gt;
However, for some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:&lt;br /&gt;
* &amp;lt;code&amp;gt;URL&amp;lt;/code&amp;gt; in vCard becomes  &amp;lt;code&amp;gt;&amp;lt;a class=&amp;quot;url&amp;quot; href=&amp;quot;...&amp;quot;&amp;gt;...&amp;lt;/a&amp;gt;&amp;lt;/code&amp;gt; inside the element with &amp;lt;code&amp;gt;class=&amp;quot;vcard&amp;quot;&amp;lt;/code&amp;gt; in hCard.&lt;br /&gt;
* Similarly, &amp;lt;code&amp;gt;EMAIL&amp;lt;/code&amp;gt; in vCard becomes &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;a class=&amp;quot;email&amp;quot; href=&amp;quot;mailto:...&amp;quot;&amp;gt;...&amp;lt;/a&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
* &amp;lt;code&amp;gt;PHOTO&amp;lt;/code&amp;gt; in vCard becomes &amp;lt;code&amp;gt;&amp;lt;img class=&amp;quot;photo&amp;quot; src=&amp;quot;...&amp;quot; alt=&amp;quot;Photo of ...&amp;quot; /&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Singular vs. Multivalued Properties ===&lt;br /&gt;
&lt;br /&gt;
For properties which are singular (e.g. &amp;quot;N&amp;quot; and &amp;quot;FN&amp;quot;), the first descendant element with that class should take effect, any others being ignored.&lt;br /&gt;
&lt;br /&gt;
For properties which can be plural (e.g. &amp;quot;TEL&amp;quot;), each class instance should create a instance of that property.&lt;br /&gt;
&lt;br /&gt;
==== Plural Properties Singularized ====&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Human vs. Machine readable ===&lt;br /&gt;
&lt;br /&gt;
If an &amp;lt;code&amp;gt;&amp;amp;lt;abbr&amp;gt;&amp;lt;/code&amp;gt; element is used for a property, then the '&amp;lt;code&amp;gt;title&amp;lt;/code&amp;gt;' attribute of the &amp;lt;code&amp;gt;&amp;amp;lt;abbr&amp;gt;&amp;lt;/code&amp;gt; element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value.  &lt;br /&gt;
&lt;br /&gt;
Similarly, if an &amp;lt;code&amp;gt;&amp;amp;lt;img&amp;gt;&amp;lt;/code&amp;gt; element is used for one or more properties, it must be treated as follows:&lt;br /&gt;
# For the &amp;quot;PHOTO&amp;quot; property and any other property that takes a URL as its value, the &amp;lt;code&amp;gt;src=&amp;quot;...&amp;quot;&amp;lt;/code&amp;gt; attribute provides the property value.&lt;br /&gt;
# For other properties, the &amp;lt;code&amp;gt;&amp;amp;lt;img&amp;gt;&amp;lt;/code&amp;gt; element's '&amp;lt;code&amp;gt;alt&amp;lt;/code&amp;gt;' attribute is the value of the property.&lt;br /&gt;
&lt;br /&gt;
=== Value excerpting ===&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;&amp;lt;code&amp;gt;value&amp;lt;/code&amp;gt;&amp;quot; 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:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;home&amp;lt;/span&amp;gt;:&lt;br /&gt;
 &amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt;+1.415.555.1212&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This hCard fragment could be displayed as:&lt;br /&gt;
&lt;br /&gt;
 home: +1.415.555.1212&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Property Exceptions ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
# '''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 &amp;lt;code&amp;gt;&amp;lt;title&amp;gt;&amp;lt;/code&amp;gt; element in (X)HTML documents) to construct the NAME property, MAY output a PROFILE value of &amp;quot;&amp;lt;code&amp;gt;VCARD&amp;lt;/code&amp;gt;&amp;quot; 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 &amp;quot;3.0&amp;quot; (without quotes) per RFC2426 Section 3.6.9.&lt;br /&gt;
&lt;br /&gt;
=== Implied &amp;quot;N&amp;quot; Optimization ===&lt;br /&gt;
&lt;br /&gt;
Although vCard requires that the &amp;quot;N&amp;quot; property be present, the authors of the vCard specification (RFC 2426) themselves do not include &amp;quot;N&amp;quot; properties in their vCards near the end of the spec (p.38).  This apparent contradiction can be resolved by simply allowing the &amp;quot;FN&amp;quot; property to imply &amp;quot;N&amp;quot; property values in typical cases provided in the spec.  We do so explicitly in hCard.&lt;br /&gt;
&lt;br /&gt;
If the value of the &amp;quot;FN&amp;quot; property is exactly two words (separated by whitespace.), and there is no explicit &amp;quot;N&amp;quot; property, then the &amp;quot;N&amp;quot; property is inferred from the &amp;quot;FN&amp;quot; property.  For &amp;quot;FN&amp;quot;s with either one word or three or more, then the author MUST explicitly markup the &amp;quot;N&amp;quot;, except for the organization contact info case, [http://microformats.org/wiki/hcard#Organization_Contact_Info see below] for that.&lt;br /&gt;
&lt;br /&gt;
# The content of &amp;quot;FN&amp;quot; is broken into two &amp;quot;words&amp;quot; separated by whitespace.&lt;br /&gt;
# The ''first'' word of the &amp;quot;FN&amp;quot; is interpreted as the &amp;quot;Given Name&amp;quot; for the &amp;quot;N&amp;quot; property.&lt;br /&gt;
# The ''second/last'' word of the &amp;quot;FN&amp;quot; is interpreted as the &amp;quot;Family Name&amp;quot; for the &amp;quot;N&amp;quot; property.&lt;br /&gt;
# Exception: If the first word ends in a &amp;quot;,&amp;quot; comma OR if the second word is a single character (optionally followed by a period &amp;quot;.&amp;quot;), then the first word (minus the comma at the end if any) is interpreted as the &amp;quot;Family Name&amp;quot; and the second word is interpreted as the &amp;quot;Given Name&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
This allows simplification in the typical case of people stating their firstname space lastname, or lastname comma firstname, or lastname comma firstinitial, or lastname space firstinitial.&lt;br /&gt;
&lt;br /&gt;
==== Organization Contact Info ====&lt;br /&gt;
&lt;br /&gt;
Contact info for a company or organization is a special case of the implied &amp;quot;N&amp;quot; optimization.&lt;br /&gt;
 &lt;br /&gt;
If the &amp;quot;FN&amp;quot; and &amp;quot;ORG&amp;quot; properties have the exact same value (typically because they are set on the same element, e.g. class=&amp;quot;fn org&amp;quot;), 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 &amp;quot;N&amp;quot; property, or set it (and any sub-properties) explicitly to the empty string &amp;quot;&amp;quot;.  Thus parsers should handle the missing &amp;quot;N&amp;quot; property in this case by implying empty values for all the &amp;quot;N&amp;quot; sub-properties.&lt;br /&gt;
&lt;br /&gt;
=== Implied &amp;quot;organization-name&amp;quot; Optimization ===&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;ORG&amp;quot; property has two subproperties, organization-name and organization-unit. Very often authors only publish the organization-name.  Thus if an &amp;quot;ORG&amp;quot; property has no &amp;quot;organization-name&amp;quot; inside it, then its entire contents MUST be treated as the &amp;quot;organization-name&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== Root Class Name ===&lt;br /&gt;
&lt;br /&gt;
The root class name for an hCard is &amp;quot;vcard&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== Property List ===&lt;br /&gt;
&lt;br /&gt;
This is the list of properties (and subproperties, in parantheses, like this) in hCard, taken from vCard:&lt;br /&gt;
&lt;br /&gt;
* fn, n (family-name, given-name, additional-name, honorific-prefix, honorific-suffix), nickname, sort-string&lt;br /&gt;
* url, email (type, value), tel (type, value)&lt;br /&gt;
* adr (post-office-box, extended-address, street-address, locality, region, postal-code, country-name, type, value), label&lt;br /&gt;
* geo (latitude, longitude), tz&lt;br /&gt;
* photo, logo, sound, bday&lt;br /&gt;
* title, role, org (organization-name, organization-unit)&lt;br /&gt;
* category, note&lt;br /&gt;
* class, key, mailer, uid, rev&lt;br /&gt;
==== type subproperty values ====&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;Home&amp;quot; is the same as &amp;quot;home&amp;quot;, as well as multivalued, e.g. a tel can be home and preferred:&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Home&amp;lt;/span&amp;gt; (&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;pref&amp;lt;/span&amp;gt;erred):&lt;br /&gt;
 &amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt;+1.415.555.1212&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following lists are ''informative''. See RFC2426 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.&lt;br /&gt;
&lt;br /&gt;
* adr type: INTL, POSTAL, PARCEL, WORK, dom, home, pref&lt;br /&gt;
* tel type: VOICE, home, msg, work, pref, fax, cell, video, pager, bbs, modem, car, isdn, pcs&lt;br /&gt;
* email type: INTERNET, x400, pref, &amp;quot;other IANA registered address types&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== XMDP Profile ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Parsing Details ===&lt;br /&gt;
&lt;br /&gt;
See [[hcard-parsing|hCard parsing]].&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
&lt;br /&gt;
This section is informative.&lt;br /&gt;
&lt;br /&gt;
=== Sample vCard ===&lt;br /&gt;
&lt;br /&gt;
Here is a sample vCard:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
BEGIN:VCARD&lt;br /&gt;
VERSION:3.0&lt;br /&gt;
N:Çelik;Tantek&lt;br /&gt;
FN:Tantek Çelik&lt;br /&gt;
URL:http://tantek.com&lt;br /&gt;
ORG:Technorati&lt;br /&gt;
END:VCARD&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and an equivalent in hCard with various elements optimized appropriately.  See [[hcard-example1-steps| hCard Example 1]] for the derivation. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;a class=&amp;quot;url fn&amp;quot; href=&amp;quot;http://tantek.com/&amp;quot;&amp;gt;Tantek Çelik&amp;lt;/a&amp;gt;&lt;br /&gt;
 &amp;lt;div class=&amp;quot;org&amp;quot;&amp;gt;Technorati&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This hCard might be displayed as:&lt;br /&gt;
&lt;br /&gt;
[http://tantek.com/ Tantek Çelik]&amp;lt;br /&amp;gt;&lt;br /&gt;
Technorati&lt;br /&gt;
&lt;br /&gt;
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 &amp;lt;head&amp;gt; element.&lt;br /&gt;
&lt;br /&gt;
=== More Examples ===&lt;br /&gt;
&lt;br /&gt;
See [[hcard-examples]] for more examples, including all examples from vCard RFC 2426 converted into hCard.&lt;br /&gt;
&lt;br /&gt;
== Examples in the wild ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
The following sites have published hCards, and thus are a great place to start for anyone looking for examples &amp;quot;in the wild&amp;quot; to try parsing, indexing, organizing etc.  If you have an hCard on your own page, feel free to add it to the top of this list.  Once the list grows too big, we'll make a separate wiki page.&lt;br /&gt;
&lt;br /&gt;
=== New Examples ===&lt;br /&gt;
Please add new examples to this section.&lt;br /&gt;
&lt;br /&gt;
* [http://www.avf-nexus.co.uk AVF-Nexus] have a hCard on their [http://www.avf-nexus.co.uk/contact/ contact page] - (by [http://creation.uk.com Creation&amp;quot;])&lt;br /&gt;
* [http://www.thefantasticos.com/andrew/ Andrew White] posted [http://www.thefantasticos.com/andrew/index.php/my-hcard/ his hCard] and [http://www.thefantasticos.com/andrew/index.php/62/microformats-the-should-have-been-obvious-web-dev-tool/ blogged about it].&lt;br /&gt;
* [http://www.2sheds.ru Oleg &amp;quot;2sheds&amp;quot; Kourapov] in his [http://www.2sheds.ru/blog/ blog] ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog X2V]) has turned personal profile into hCard ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/hcard.html X2V]) and his blogroll - into combination XFN/hCards ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/friends.html X2V])&lt;br /&gt;
* [http://www.approveddesign.co.uk Approved Design Consultancy] have a hCard on their [http://www.approveddesign.co.uk/about/contact/ contact page] as well as on their [http://www.approveddesign.co.uk/about/people/ people section] - (by [http://creation.uk.com Creation&amp;quot;])&lt;br /&gt;
* [http://weblog.200ok.com.au/ Ben Buchanan] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&amp;amp;format=search Colin Morris] have implemented hCards and vCards for the [http://www.griffith.edu.au Griffith University] [http://www.griffith.edu.au/find/content_phonebook.html online phone book]. Eg. [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=ben+buchanan&amp;amp;format=search Ben's vCard] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&amp;amp;format=search Colin's vCard]&lt;br /&gt;
&lt;br /&gt;
=== Examples ===&lt;br /&gt;
* [http://thoughtport.blogspot.com/ Aiden Kenny] hasn't published his hCard yet, but he has [http://thoughtport.blogspot.com/2005/07/elemental-particles-of-web.html published his hCard icon]: http://photos1.blogger.com/blogger/4224/444/320/AK-Hcard-icon.gif&lt;br /&gt;
* [http://thedredge.org Andy Hume] uses the hcard format to mark-up the names and URLs of commentors on his blog. &lt;br /&gt;
* [http://www.bidclix.com/ BidClix]'s [http://www.bidclix.com/AboutContact.html Contact BidClix] page has it's ''contact info'' marked up with an hCard.&lt;br /&gt;
* [http://suda.co.uk/ Brian Suda] has managed to embed a photo in [http://suda.co.uk/contact/ his hCard] through the [http://www.ietf.org/rfc/rfc2397.txt data uri scheme] by converting the image to BASE64 code. View the Source to see how this is accomplished. [http://suda.co.uk/projects/X2V/get-vcard.php?uri=http%3A//suda.co.uk/contact/ The X2V link] will extract the image and encode it for a vCard which will be displayed in some address book applications.&lt;br /&gt;
* [http://cinematreasures.org Cinema Treasures] uses hCard to markup venue information for 10,000+ movie theaters.&lt;br /&gt;
* [http://www.w3.org/People/Connolly/events/ Dan Connolly's index of events and talks] has hCards for many of the people he has met at those events.&lt;br /&gt;
* [http://doncrowley.blogspot.com/ Don Crowley] has published [http://www.crowley.nl/hcard.html his hCard] as well as a nifty hCard button: http://www.crowley.nl/images/hcard.png&lt;br /&gt;
* [http://loadaveragezero.com/hnav/contact.php Douglas W. Clifton] added all types of contact information&lt;br /&gt;
* [http://evdb.com EVDB], the Events and Venues Database, publishes all venue detail pages with embedded hCards.&lt;br /&gt;
* [http://www.iowamilitaryveteransband.com/members/ Iowa Military Veterans Band Contacts] - 95 hCards [http://weblog.randomchaos.com/archive/2005/10/24/Microformats/ marked up by Scott Reynen]&lt;br /&gt;
* [http://JackWolfgang.blogspot.com Jack L. Wolfgang II] has [http://jack.randomata.com/resume/ converted the addresses in his resume to hCards].&lt;br /&gt;
* [http://www.efas.fupl.asso.fr/efas/_Mathieu-Drouet_.html Mathieu Drouet] and [http://www.efas.fupl.asso.fr/efas/_Annie-Leger_.html Annie Leger] both have hCards&lt;br /&gt;
* [http://www.ndunn.com Neil Dunn] has published his rather [http://www.ndunn.com/2005/10/7/hCard good looking hCard]&lt;br /&gt;
* [http://www.oliverbrown.me.uk/ Oliver Brown] has published his hCard.&lt;br /&gt;
* [http://www.paradigmproductions.org/contact/ Paradigm Productions] published a vcard as a ul (marked up by [http://www.linkingarts.com/ Peter Jacobson])&lt;br /&gt;
* [http://www.splintered.co.uk/ Patrick H. Lauke] has marked up [http://www.splintered.co.uk/about/ his contact info with hCard].&lt;br /&gt;
* [http://blah Paul Schreiber has published his hCard on [http://paulschreiber.com/about/?contact his about page].&lt;br /&gt;
* [http://paulschreiber.com/blog/ Paul Schreiber]'s [http://concerts.shrub.ca/ Sunnyvale House Concerts] site publishes hCards for upcoming artists, as well as an hCard for the page itself.  In addition the [http://concerts.shrub.ca/shows Past Shows] page contains hCards for all past artists.&lt;br /&gt;
* [http://www.paulmichaelsmith.com/blog/hcard.htm Paul Smith] has created an hCard page which is Human Readable, and a link to X2V passing the same hCard page to generate a vCard.&lt;br /&gt;
* [http://www.windley.com/archives/2005/07/hcards_trying_o.shtml Phil Windley has published] [http://phil.windley.org/hcard.html his hCard].&lt;br /&gt;
* [http://www.go-curiosity.com/about.htm Piercarlo Slavazza] has published an hCard.&lt;br /&gt;
* [http://zooibaai.nl/ Rob Mientjes] has published his hCard on [http://zooibaai.nl/about/ his about page].&lt;br /&gt;
* [http://rbach.priv.at/Contact Robert Bachmann] has published his hCard and [http://rbach.priv.at/Images/hcard a button].&lt;br /&gt;
* [http://blah Scott Reynen has published his hCard on [http://www.randomchaos.com/document.php?source=scott_reynen his profile page].&lt;br /&gt;
* [http://www.wolfsreign.com Steven Ametjan] has published his hCard on [http://www.wolfsreign.com/about/ his about page].&lt;br /&gt;
* [http://tagcamp.org/index.cgi?ContactList TagCamp contact list]&lt;br /&gt;
* [http://tantek.com/log Tantek's Thoughts] includes an inline author hCard at the bottom of the page.&lt;br /&gt;
* [http://technorati.com/ Technorati]'s [http://www.technorati.com/about/ About page] lists their '''Media Contact'''&lt;br /&gt;
* [http://www.deadringerart.com/ The Brothers McDowell] have hCards at their Contact page.&lt;br /&gt;
* [http://twinsparc.com/ Twinsparc] put an hCard in the header and footer of all their pages.&lt;br /&gt;
* [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 Conference speakers page marked up with hCard]&lt;br /&gt;
* [http://we05.com/ Web Essentials 05] marked up all their [http://we05.com/presenters.cfm presenters with hCard].&lt;br /&gt;
&lt;br /&gt;
=== Examples with some problems ===&lt;br /&gt;
* [http://gbraad.nl/ Gerard Braad] has published an example on his [http://gbraad.nl/site/?p=profile profile] page that is almost consistent with his original [http://gbraad.nl/files/gbraad.vcf vCard] file. Also progress is made for transforming his [http://files.gbraad.nl/foaf.rdf FoaF] file to a hCard encoded representation. (also done for my spouse:[http://spouse.gbraad.nl/site/?p=profile Yong Yuan])&lt;br /&gt;
** (2005-09-27) PASSED, PASSED&lt;br /&gt;
** WARNINGS&lt;br /&gt;
*** uses 'n given-name' and 'n family-name' instead of nesting the given- and family- names inside the 'n'&lt;br /&gt;
*** has one 'tel' value with a bunch of values stuffed in&lt;br /&gt;
*** probably more problems --[[User:RyanKing|RyanKing]] 17:19, 5 Jan 2006 (PST)&lt;br /&gt;
* [http://www.kerihenare.com/ Keri Henare] has marked up his [http://www.kerihenare.com/contact/ contact info page] with hCard.&lt;br /&gt;
** (2005-09-27) PASSED&lt;br /&gt;
** (2005-11-01) hCard completely rewritten&lt;br /&gt;
** WARNING - type subproperty in classname&lt;br /&gt;
* [http://kinrowan.net/ Cori Schlegel] [http://kinrowan.net/blog/wp/archives/2005/07/08/a-problem-with-the-structured-blogging-plug-in-for-wordpress/ discusses how he has updated] [http://kinrowan.net/blog/contact his contact page with hCard]&lt;br /&gt;
** INVALID - using 'prefix' instead of 'honorific-prefix' and type's in classnames (in both adr and tel) and has two photo's (the second could be 'logo') --[[User:RyanKing|RyanKing]] 15:15, 5 Jan 2006 (PST)&lt;br /&gt;
* The good ship [http://styrheim.com/test/leonid.html Leonid Miloslavskiy] spotted in the North Atlantic&lt;br /&gt;
** INVALID  --[[User:RyanKing|RyanKing]] 00:50, 27 Oct 2005 (PDT)&lt;br /&gt;
*** class=&amp;quot;family&amp;quot; should probably be family-name&lt;br /&gt;
*** the &amp;quot;n&amp;quot; property is missing and the &amp;quot;n&amp;quot; optimization can't be applied&lt;br /&gt;
*** the first geo propery is empty, the second one is invalid (ie, it doesn't contain lat/long)&lt;br /&gt;
* [http://landsbank.fo/#hCard Landsbanki Føroya]&lt;br /&gt;
** INVALID - using embedded rdf/xml invalidly&lt;br /&gt;
* [http://chrischerry.name/blog/contact/ Chris Cherry's contact page with his hCard]&lt;br /&gt;
** WARNING - uses class=&amp;quot;cell&amp;quot; instead of &amp;amp;lt;span class=&amp;quot;type&amp;quot;&amp;amp;gt;cell&amp;amp;lt;/span&amp;amp;gt;&lt;br /&gt;
* [http://www.bath.ac.uk/contact/ University of Bath] Person Finder results are encoded with hCards so you can easily create a vCard from any result. &lt;br /&gt;
** ERROR - attempt to use Implied-N optimization where that's not possible. --[[User:RyanKing|RyanKing]] 14:29, 5 Jan 2006 (PST)&lt;br /&gt;
** where? more detail and I will fix. -- [[User:PhilWilson|PhilWilson]] 23:22, 11 Jan 2006 (GMT)&lt;br /&gt;
* [http://richi.co.uk/blog/2005/12/structured-blogging.html Richi Jennings] has put up his attempt&lt;br /&gt;
** INVALID, missing FN --[[User:RyanKing|RyanKing]] 12:47, 5 Jan 2006 (PST)&lt;br /&gt;
* [http://www.shiftingpixel.com/about/ shifting pixel photoblog] has published an hCard.&lt;br /&gt;
** &amp;quot;organization_name&amp;quot; should be &amp;quot;organization-name&amp;quot; (s/_/-/), otherwise good --[[User:RyanKing|RyanKing]] 14:01, 5 Jan 2006 (PST)&lt;br /&gt;
&lt;br /&gt;
== Implementations ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
The following implementations have been developed which either generate or parse hCards. If you have an hCard implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.&lt;br /&gt;
&lt;br /&gt;
* There is [http://flickr.com/photos/factoryjoe/68755089/ evidence of built-in hCard support in the Konqueror browser].  Specifically, Konqueror 3.5, in KDE 3.5 (kubuntu Breezy w/ update).&lt;br /&gt;
* There is [http://tagcamp.org/index.cgi?ContactList evidence of a kwiki plugin for hCards].  Update: the [http://svn.kwiki.org/cwest/Kwiki-hCard/ hCard kwiki plugin svn repository].  See the [http://microwiki.caseywest.com/index.cgi?hCard documentation of the hCard kwiki plugin].&lt;br /&gt;
* [http://suda.co.uk/projects/X2V/ X2V] is a bookmarklet that parses hCard and produces a .vcf (vCard) stream.  Note: needs to be updated as the spec is refined&lt;br /&gt;
* [http://www.stripytshirt.co.uk Duncan Walker] has built [http://www.stripytshirt.co.uk/features/firefox/smartzilla a Firefox extension] that gets hCard data from a webpage, uses Brian Suda's XSL (locally) to transform it to vcard format and opens the resulting .vcf file.&lt;br /&gt;
* [http://george.hotelling.net/90percent/ George] has written a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script] that detects hCards and allows users to easily add them to their address book application.  Relies on the X2V web service to do the conversion.&lt;br /&gt;
* [http://blogmatrix.blogmatrix.com/ David Janes] has written a [[Greasemonkey]] [http://www.blogmatrix.com/include/microformat-find.user.js script] that finds many microformat elements, including hCards, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003376 provides a popup menu of actions]. The hCard to vCard conversion is done internally within the script. ''This does not work with FireFox 1.5+/GreaseMonkey 0.6.4+.''&lt;br /&gt;
* [http://diveintomark.org/ Mark Pilgrim] has also written an [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser Greasemonkey user script].  It is self-contained and does not rely on the X2V web service.&lt;br /&gt;
* [http://www.oliverbrown.me.uk/2005/09/03/a-working-microformats-extension-to-simplexml/ Oliver Brown] has written an &amp;quot;extension&amp;quot; to [http://www.php.net/simplexml SimpleXML] that gives simple access to hCard information in PHP 5.&lt;br /&gt;
* [http://thedredge.org/ Andrew D. Hume] has built a system (Wordpress plugin?) for [http://thedredge.org/2005/06/using-hcards-in-your-blog/ using hcards in your blog] to represent people leaving comments on blog posts.&lt;br /&gt;
* The [http://tantek.com/microformats/hcard-creator.html hCard creator] is a very simple, yet illustrative, open source user interface / form / script which creates an hCard in real-time as you type in a set of contact information. &lt;br /&gt;
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate hCard information ([http://ietf.org/rfc/rfc2629 RFC2629] is an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])&lt;br /&gt;
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - Open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards. &lt;br /&gt;
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] is a collection of palmpilot and sidekick tools. It includes X2V derivatives xhtml2hcard.xsl and toICal.xsl plus some [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest] materials&lt;br /&gt;
* [http://www.openpsa.org/ OpenPsa 2.x] CRM application uses hCard for all person listings. The widget is [http://www.midgard-project.org/midcom-permalink-922834501b71daad856f35ec593c7a6d reusable across Midgard CMS]&lt;br /&gt;
&lt;br /&gt;
== Additional Applications ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
There are numerous potential additional uses and applications for hCards on the Web.  The following are merely a few thoughts and possibilities that folks have come up with:&lt;br /&gt;
&lt;br /&gt;
* As an open standard/format for [http://www.gravatar.com/ Gravatars].&lt;br /&gt;
* Marking up individual authors of blog posts on a group blog&lt;br /&gt;
* Marking up people's names and URLs in a blogroll&lt;br /&gt;
* Any reference to people in blog posts (e.g. when citing them, or referencing them, or describing them, by name).&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
=== Normative References ===&lt;br /&gt;
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]&lt;br /&gt;
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426]&lt;br /&gt;
&lt;br /&gt;
=== Informative References ===&lt;br /&gt;
* [http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426]&lt;br /&gt;
* [http://w3.org/TR/REC-CSS1 CSS1]&lt;br /&gt;
* [http://tantek.com/log/2004/09.html#hcard hCard term introduced and defined on the Web, 20040930]&lt;br /&gt;
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]&lt;br /&gt;
* Contributed from http://developers.technorati.com/wiki/hCard.&lt;br /&gt;
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]&lt;br /&gt;
&lt;br /&gt;
==== Specifications That Use hCard ====&lt;br /&gt;
* [[adr]]&lt;br /&gt;
* [[geo]]&lt;br /&gt;
* [[hcalendar|hCalendar]]&lt;br /&gt;
* [[hreview|hReview]]&lt;br /&gt;
&lt;br /&gt;
==== Similar Work ====&lt;br /&gt;
* [http://www.intertwingly.net/wiki/pie/PaceBetterPersonElement Atom PaceBetterPersonElement]&lt;br /&gt;
* [http://www.jabber.org/jeps/jep-0054.html JEP-0054: vcard-temp]&lt;br /&gt;
&lt;br /&gt;
== Related Pages And Further Reading ==&lt;br /&gt;
* [[hcard-profile|hCard profile]] - The XMDP profile for hCard&lt;br /&gt;
&lt;br /&gt;
This 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.&lt;br /&gt;
&lt;br /&gt;
* [[hcard-brainstorming|hCard Brainstorming]] - where we are keeping our brainstorms and other explorations relating to hCard&lt;br /&gt;
* [[hcard-tests|hCard tests]] - a wiki page with actual embedded hCards to try parsing.&lt;br /&gt;
* [[hcard-faq|hCard FAQ]] - If you have any questions about hCard, check here, and if you don't find answers, add your questions!&lt;br /&gt;
* [[hcard-issues|hCard issues]] - Please add any issues with the specification to the issues page.&lt;br /&gt;
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].&lt;/div&gt;</summary>
		<author><name>Trovster</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hcard&amp;diff=4123</id>
		<title>hcard</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hcard&amp;diff=4123"/>
		<updated>2006-01-07T17:08:45Z</updated>

		<summary type="html">&lt;p&gt;Trovster: /* New Examples */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= hCard =&lt;br /&gt;
&lt;br /&gt;
hCard is a simple, open, distributed contact information format for people, companies, and organizations, which is suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. hCard is a 1:1 representation of the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in XHTML, one of several open [[microformats|microformat]] standards.&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Draft Specification ==&lt;br /&gt;
&lt;br /&gt;
=== Editor ===&lt;br /&gt;
[http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]&lt;br /&gt;
&lt;br /&gt;
=== Authors ===&lt;br /&gt;
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]&lt;br /&gt;
* [http://suda.co.uk/ Brian Suda]&lt;br /&gt;
&lt;br /&gt;
=== Copyright ===&lt;br /&gt;
{{MicroFormatCopyrightStatement2004}}&lt;br /&gt;
&lt;br /&gt;
=== Patents ===&lt;br /&gt;
{{MicroFormatPatentStatement}}&lt;br /&gt;
&lt;br /&gt;
=== Inspiration and Acknowledgments ===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), has been broadly interoperably implemented (e.g. Apple's &amp;quot;Address Book&amp;quot; application built into MacOSX).&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
This specification introduces the '''hCard''' format, which is a 1:1 representation of the aforementioned vCard standard, in semantic XHTML.  Bloggers can both embed vCards directly in their web pages, and style them with CSS to make them appear as desired.  In addition, hCard enables applications to retrieve information about such vCards directly from web pages without having to reference a separate file.&lt;br /&gt;
&lt;br /&gt;
Use the [http://microformats.org/code/hcard/creator hCard creator], copy the HTML code it generates to your blog or website to publish your contact info.&lt;br /&gt;
&lt;br /&gt;
== Semantic XHTML Design Principles ==&lt;br /&gt;
{{semantic-xhtml-design-principles}}&lt;br /&gt;
&lt;br /&gt;
== Format ==&lt;br /&gt;
=== In General ===&lt;br /&gt;
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) forms the basis of hCard.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== More Semantic Equivalents ===&lt;br /&gt;
However, for some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:&lt;br /&gt;
* &amp;lt;code&amp;gt;URL&amp;lt;/code&amp;gt; in vCard becomes  &amp;lt;code&amp;gt;&amp;lt;a class=&amp;quot;url&amp;quot; href=&amp;quot;...&amp;quot;&amp;gt;...&amp;lt;/a&amp;gt;&amp;lt;/code&amp;gt; inside the element with &amp;lt;code&amp;gt;class=&amp;quot;vcard&amp;quot;&amp;lt;/code&amp;gt; in hCard.&lt;br /&gt;
* Similarly, &amp;lt;code&amp;gt;EMAIL&amp;lt;/code&amp;gt; in vCard becomes &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;a class=&amp;quot;email&amp;quot; href=&amp;quot;mailto:...&amp;quot;&amp;gt;...&amp;lt;/a&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
* &amp;lt;code&amp;gt;PHOTO&amp;lt;/code&amp;gt; in vCard becomes &amp;lt;code&amp;gt;&amp;lt;img class=&amp;quot;photo&amp;quot; src=&amp;quot;...&amp;quot; alt=&amp;quot;Photo of ...&amp;quot; /&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Singular vs. Multivalued Properties ===&lt;br /&gt;
&lt;br /&gt;
For properties which are singular (e.g. &amp;quot;N&amp;quot; and &amp;quot;FN&amp;quot;), the first descendant element with that class should take effect, any others being ignored.&lt;br /&gt;
&lt;br /&gt;
For properties which can be plural (e.g. &amp;quot;TEL&amp;quot;), each class instance should create a instance of that property.&lt;br /&gt;
&lt;br /&gt;
==== Plural Properties Singularized ====&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Human vs. Machine readable ===&lt;br /&gt;
&lt;br /&gt;
If an &amp;lt;code&amp;gt;&amp;amp;lt;abbr&amp;gt;&amp;lt;/code&amp;gt; element is used for a property, then the '&amp;lt;code&amp;gt;title&amp;lt;/code&amp;gt;' attribute of the &amp;lt;code&amp;gt;&amp;amp;lt;abbr&amp;gt;&amp;lt;/code&amp;gt; element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value.  &lt;br /&gt;
&lt;br /&gt;
Similarly, if an &amp;lt;code&amp;gt;&amp;amp;lt;img&amp;gt;&amp;lt;/code&amp;gt; element is used for one or more properties, it must be treated as follows:&lt;br /&gt;
# For the &amp;quot;PHOTO&amp;quot; property and any other property that takes a URL as its value, the &amp;lt;code&amp;gt;src=&amp;quot;...&amp;quot;&amp;lt;/code&amp;gt; attribute provides the property value.&lt;br /&gt;
# For other properties, the &amp;lt;code&amp;gt;&amp;amp;lt;img&amp;gt;&amp;lt;/code&amp;gt; element's '&amp;lt;code&amp;gt;alt&amp;lt;/code&amp;gt;' attribute is the value of the property.&lt;br /&gt;
&lt;br /&gt;
=== Value excerpting ===&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;&amp;lt;code&amp;gt;value&amp;lt;/code&amp;gt;&amp;quot; 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:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;home&amp;lt;/span&amp;gt;:&lt;br /&gt;
 &amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt;+1.415.555.1212&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This hCard fragment could be displayed as:&lt;br /&gt;
&lt;br /&gt;
 home: +1.415.555.1212&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Property Exceptions ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
# '''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 &amp;lt;code&amp;gt;&amp;lt;title&amp;gt;&amp;lt;/code&amp;gt; element in (X)HTML documents) to construct the NAME property, MAY output a PROFILE value of &amp;quot;&amp;lt;code&amp;gt;VCARD&amp;lt;/code&amp;gt;&amp;quot; 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 &amp;quot;3.0&amp;quot; (without quotes) per RFC2426 Section 3.6.9.&lt;br /&gt;
&lt;br /&gt;
=== Implied &amp;quot;N&amp;quot; Optimization ===&lt;br /&gt;
&lt;br /&gt;
Although vCard requires that the &amp;quot;N&amp;quot; property be present, the authors of the vCard specification (RFC 2426) themselves do not include &amp;quot;N&amp;quot; properties in their vCards near the end of the spec (p.38).  This apparent contradiction can be resolved by simply allowing the &amp;quot;FN&amp;quot; property to imply &amp;quot;N&amp;quot; property values in typical cases provided in the spec.  We do so explicitly in hCard.&lt;br /&gt;
&lt;br /&gt;
If the value of the &amp;quot;FN&amp;quot; property is exactly two words (separated by whitespace.), and there is no explicit &amp;quot;N&amp;quot; property, then the &amp;quot;N&amp;quot; property is inferred from the &amp;quot;FN&amp;quot; property.  For &amp;quot;FN&amp;quot;s with either one word or three or more, then the author MUST explicitly markup the &amp;quot;N&amp;quot;, except for the organization contact info case, [http://microformats.org/wiki/hcard#Organization_Contact_Info see below] for that.&lt;br /&gt;
&lt;br /&gt;
# The content of &amp;quot;FN&amp;quot; is broken into two &amp;quot;words&amp;quot; separated by whitespace.&lt;br /&gt;
# The ''first'' word of the &amp;quot;FN&amp;quot; is interpreted as the &amp;quot;Given Name&amp;quot; for the &amp;quot;N&amp;quot; property.&lt;br /&gt;
# The ''second/last'' word of the &amp;quot;FN&amp;quot; is interpreted as the &amp;quot;Family Name&amp;quot; for the &amp;quot;N&amp;quot; property.&lt;br /&gt;
# Exception: If the first word ends in a &amp;quot;,&amp;quot; comma OR if the second word is a single character (optionally followed by a period &amp;quot;.&amp;quot;), then the first word (minus the comma at the end if any) is interpreted as the &amp;quot;Family Name&amp;quot; and the second word is interpreted as the &amp;quot;Given Name&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
This allows simplification in the typical case of people stating their firstname space lastname, or lastname comma firstname, or lastname comma firstinitial, or lastname space firstinitial.&lt;br /&gt;
&lt;br /&gt;
==== Organization Contact Info ====&lt;br /&gt;
&lt;br /&gt;
Contact info for a company or organization is a special case of the implied &amp;quot;N&amp;quot; optimization.&lt;br /&gt;
 &lt;br /&gt;
If the &amp;quot;FN&amp;quot; and &amp;quot;ORG&amp;quot; properties have the exact same value (typically because they are set on the same element, e.g. class=&amp;quot;fn org&amp;quot;), 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 &amp;quot;N&amp;quot; property, or set it (and any sub-properties) explicitly to the empty string &amp;quot;&amp;quot;.  Thus parsers should handle the missing &amp;quot;N&amp;quot; property in this case by implying empty values for all the &amp;quot;N&amp;quot; sub-properties.&lt;br /&gt;
&lt;br /&gt;
=== Implied &amp;quot;organization-name&amp;quot; Optimization ===&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;ORG&amp;quot; property has two subproperties, organization-name and organization-unit. Very often authors only publish the organization-name.  Thus if an &amp;quot;ORG&amp;quot; property has no &amp;quot;organization-name&amp;quot; inside it, then its entire contents MUST be treated as the &amp;quot;organization-name&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== Root Class Name ===&lt;br /&gt;
&lt;br /&gt;
The root class name for an hCard is &amp;quot;vcard&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== Property List ===&lt;br /&gt;
&lt;br /&gt;
This is the list of properties (and subproperties, in parantheses, like this) in hCard, taken from vCard:&lt;br /&gt;
&lt;br /&gt;
* fn, n (family-name, given-name, additional-name, honorific-prefix, honorific-suffix), nickname, sort-string&lt;br /&gt;
* url, email (type, value), tel (type, value)&lt;br /&gt;
* adr (post-office-box, extended-address, street-address, locality, region, postal-code, country-name, type, value), label&lt;br /&gt;
* geo (latitude, longitude), tz&lt;br /&gt;
* photo, logo, sound, bday&lt;br /&gt;
* title, role, org (organization-name, organization-unit)&lt;br /&gt;
* category, note&lt;br /&gt;
* class, key, mailer, uid, rev&lt;br /&gt;
==== type subproperty values ====&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;Home&amp;quot; is the same as &amp;quot;home&amp;quot;, as well as multivalued, e.g. a tel can be home and preferred:&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Home&amp;lt;/span&amp;gt; (&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;pref&amp;lt;/span&amp;gt;erred):&lt;br /&gt;
 &amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt;+1.415.555.1212&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following lists are ''informative''. See RFC2426 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.&lt;br /&gt;
&lt;br /&gt;
* adr type: INTL, POSTAL, PARCEL, WORK, dom, home, pref&lt;br /&gt;
* tel type: VOICE, home, msg, work, pref, fax, cell, video, pager, bbs, modem, car, isdn, pcs&lt;br /&gt;
* email type: INTERNET, x400, pref, &amp;quot;other IANA registered address types&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== XMDP Profile ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Parsing Details ===&lt;br /&gt;
&lt;br /&gt;
See [[hcard-parsing|hCard parsing]].&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
&lt;br /&gt;
This section is informative.&lt;br /&gt;
&lt;br /&gt;
=== Sample vCard ===&lt;br /&gt;
&lt;br /&gt;
Here is a sample vCard:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
BEGIN:VCARD&lt;br /&gt;
VERSION:3.0&lt;br /&gt;
N:Çelik;Tantek&lt;br /&gt;
FN:Tantek Çelik&lt;br /&gt;
URL:http://tantek.com&lt;br /&gt;
ORG:Technorati&lt;br /&gt;
END:VCARD&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and an equivalent in hCard with various elements optimized appropriately.  See [[hcard-example1-steps| hCard Example 1]] for the derivation. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;a class=&amp;quot;url fn&amp;quot; href=&amp;quot;http://tantek.com/&amp;quot;&amp;gt;Tantek Çelik&amp;lt;/a&amp;gt;&lt;br /&gt;
 &amp;lt;div class=&amp;quot;org&amp;quot;&amp;gt;Technorati&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This hCard might be displayed as:&lt;br /&gt;
&lt;br /&gt;
[http://tantek.com/ Tantek Çelik]&amp;lt;br /&amp;gt;&lt;br /&gt;
Technorati&lt;br /&gt;
&lt;br /&gt;
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 &amp;lt;head&amp;gt; element.&lt;br /&gt;
&lt;br /&gt;
=== More Examples ===&lt;br /&gt;
&lt;br /&gt;
See [[hcard-examples]] for more examples, including all examples from vCard RFC 2426 converted into hCard.&lt;br /&gt;
&lt;br /&gt;
== Examples in the wild ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
The following sites have published hCards, and thus are a great place to start for anyone looking for examples &amp;quot;in the wild&amp;quot; to try parsing, indexing, organizing etc.  If you have an hCard on your own page, feel free to add it to the top of this list.  Once the list grows too big, we'll make a separate wiki page.&lt;br /&gt;
&lt;br /&gt;
=== New Examples ===&lt;br /&gt;
Please add new examples to this section.&lt;br /&gt;
&lt;br /&gt;
* [http://www.approveddesign.co.uk Approved Design Consultancy] have a hCard on their [http://www.approveddesign.co.uk/about/contact/ contact page] - (by [http://creation.uk.com Creation&amp;quot;])&lt;br /&gt;
&lt;br /&gt;
=== Examples ===&lt;br /&gt;
* [http://thoughtport.blogspot.com/ Aiden Kenny] hasn't published his hCard yet, but he has [http://thoughtport.blogspot.com/2005/07/elemental-particles-of-web.html published his hCard icon]: http://photos1.blogger.com/blogger/4224/444/320/AK-Hcard-icon.gif&lt;br /&gt;
* [http://thedredge.org Andy Hume] uses the hcard format to mark-up the names and URLs of commentors on his blog. &lt;br /&gt;
* [http://www.bidclix.com/ BidClix]'s [http://www.bidclix.com/AboutContact.html Contact BidClix] page has it's ''contact info'' marked up with an hCard.&lt;br /&gt;
* [http://suda.co.uk/ Brian Suda] has managed to embed a photo in [http://suda.co.uk/contact/ his hCard] through the [http://www.ietf.org/rfc/rfc2397.txt data uri scheme] by converting the image to BASE64 code. View the Source to see how this is accomplished. [http://suda.co.uk/projects/X2V/get-vcard.php?uri=http%3A//suda.co.uk/contact/ The X2V link] will extract the image and encode it for a vCard which will be displayed in some address book applications.&lt;br /&gt;
* [http://cinematreasures.org Cinema Treasures] uses hCard to markup venue information for 10,000+ movie theaters.&lt;br /&gt;
* [http://www.w3.org/People/Connolly/events/ Dan Connolly's index of events and talks] has hCards for many of the people he has met at those events.&lt;br /&gt;
* [http://doncrowley.blogspot.com/ Don Crowley] has published [http://www.crowley.nl/hcard.html his hCard] as well as a nifty hCard button: http://www.crowley.nl/images/hcard.png&lt;br /&gt;
* [http://loadaveragezero.com/hnav/contact.php Douglas W. Clifton] added all types of contact information&lt;br /&gt;
* [http://evdb.com EVDB], the Events and Venues Database, publishes all venue detail pages with embedded hCards.&lt;br /&gt;
* [http://www.iowamilitaryveteransband.com/members/ Iowa Military Veterans Band Contacts] - 95 hCards [http://weblog.randomchaos.com/archive/2005/10/24/Microformats/ marked up by Scott Reynen]&lt;br /&gt;
* [http://JackWolfgang.blogspot.com Jack L. Wolfgang II] has [http://jack.randomata.com/resume/ converted the addresses in his resume to hCards].&lt;br /&gt;
* [http://www.efas.fupl.asso.fr/efas/_Mathieu-Drouet_.html Mathieu Drouet] and [http://www.efas.fupl.asso.fr/efas/_Annie-Leger_.html Annie Leger] both have hCards&lt;br /&gt;
* [http://www.ndunn.com Neil Dunn] has published his rather [http://www.ndunn.com/2005/10/7/hCard good looking hCard]&lt;br /&gt;
* [http://www.oliverbrown.me.uk/ Oliver Brown] has published his hCard.&lt;br /&gt;
* [http://www.paradigmproductions.org/contact/ Paradigm Productions] published a vcard as a ul (marked up by [http://www.linkingarts.com/ Peter Jacobson])&lt;br /&gt;
* [http://www.splintered.co.uk/ Patrick H. Lauke] has marked up [http://www.splintered.co.uk/about/ his contact info with hCard].&lt;br /&gt;
* [http://blah Paul Schreiber has published his hCard on [http://paulschreiber.com/about/?contact his about page].&lt;br /&gt;
* [http://paulschreiber.com/blog/ Paul Schreiber]'s [http://concerts.shrub.ca/ Sunnyvale House Concerts] site publishes hCards for upcoming artists, as well as an hCard for the page itself.  In addition the [http://concerts.shrub.ca/shows Past Shows] page contains hCards for all past artists.&lt;br /&gt;
* [http://www.paulmichaelsmith.com/blog/hcard.htm Paul Smith] has created an hCard page which is Human Readable, and a link to X2V passing the same hCard page to generate a vCard.&lt;br /&gt;
* [http://www.windley.com/archives/2005/07/hcards_trying_o.shtml Phil Windley has published] [http://phil.windley.org/hcard.html his hCard].&lt;br /&gt;
* [http://www.go-curiosity.com/about.htm Piercarlo Slavazza] has published an hCard.&lt;br /&gt;
* [http://zooibaai.nl/ Rob Mientjes] has published his hCard on [http://zooibaai.nl/about/ his about page].&lt;br /&gt;
* [http://rbach.priv.at/Contact Robert Bachmann] has published his hCard and [http://rbach.priv.at/Images/hcard a button].&lt;br /&gt;
* [http://blah Scott Reynen has published his hCard on [http://www.randomchaos.com/document.php?source=scott_reynen his profile page].&lt;br /&gt;
* [http://www.wolfsreign.com Steven Ametjan] has published his hCard on [http://www.wolfsreign.com/about/ his about page].&lt;br /&gt;
* [http://tagcamp.org/index.cgi?ContactList TagCamp contact list]&lt;br /&gt;
* [http://tantek.com/log Tantek's Thoughts] includes an inline author hCard at the bottom of the page.&lt;br /&gt;
* [http://technorati.com/ Technorati]'s [http://www.technorati.com/about/ About page] lists their '''Media Contact'''&lt;br /&gt;
* [http://www.deadringerart.com/ The Brothers McDowell] have hCards at their Contact page.&lt;br /&gt;
* [http://twinsparc.com/ Twinsparc] put an hCard in the header and footer of all their pages.&lt;br /&gt;
* [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 Conference speakers page marked up with hCard]&lt;br /&gt;
* [http://we05.com/ Web Essentials 05] marked up all their [http://we05.com/presenters.cfm presenters with hCard].&lt;br /&gt;
&lt;br /&gt;
=== Examples with some problems ===&lt;br /&gt;
* [http://gbraad.nl/ Gerard Braad] has published an example on his [http://gbraad.nl/site/?p=profile profile] page that is almost consistent with his original [http://gbraad.nl/files/gbraad.vcf vCard] file. Also progress is made for transforming his [http://files.gbraad.nl/foaf.rdf FoaF] file to a hCard encoded representation. (also done for my spouse:[http://spouse.gbraad.nl/site/?p=profile Yong Yuan])&lt;br /&gt;
** (2005-09-27) PASSED, PASSED&lt;br /&gt;
** WARNINGS&lt;br /&gt;
*** uses 'n given-name' and 'n family-name' instead of nesting the given- and family- names inside the 'n'&lt;br /&gt;
*** has one 'tel' value with a bunch of values stuffed in&lt;br /&gt;
*** probably more problems --[[User:RyanKing|RyanKing]] 17:19, 5 Jan 2006 (PST)&lt;br /&gt;
* [http://www.kerihenare.com/ Keri Henare] has marked up his [http://www.kerihenare.com/contact/ contact info page] with hCard.&lt;br /&gt;
** (2005-09-27) PASSED&lt;br /&gt;
** (2005-11-01) hCard completely rewritten&lt;br /&gt;
** WARNING - type subproperty in classname&lt;br /&gt;
* [http://kinrowan.net/ Cori Schlegel] [http://kinrowan.net/blog/wp/archives/2005/07/08/a-problem-with-the-structured-blogging-plug-in-for-wordpress/ discusses how he has updated] [http://kinrowan.net/blog/contact his contact page with hCard]&lt;br /&gt;
** INVALID - using 'prefix' instead of 'honorific-prefix' and type's in classnames (in both adr and tel) and has two photo's (the second could be 'logo') --[[User:RyanKing|RyanKing]] 15:15, 5 Jan 2006 (PST)&lt;br /&gt;
* The good ship [http://styrheim.com/test/leonid.html Leonid Miloslavskiy] spotted in the North Atlantic&lt;br /&gt;
** INVALID  --[[User:RyanKing|RyanKing]] 00:50, 27 Oct 2005 (PDT)&lt;br /&gt;
*** class=&amp;quot;family&amp;quot; should probably be family-name&lt;br /&gt;
*** the &amp;quot;n&amp;quot; property is missing and the &amp;quot;n&amp;quot; optimization can't be applied&lt;br /&gt;
*** the first geo propery is empty, the second one is invalid (ie, it doesn't contain lat/long)&lt;br /&gt;
* [http://landsbank.fo/#hCard Landsbanki Føroya]&lt;br /&gt;
** INVALID - using embedded rdf/xml invalidly&lt;br /&gt;
* [http://chrischerry.name/blog/contact/ Chris Cherry's contact page with his hCard]&lt;br /&gt;
** WARNING - uses class=&amp;quot;cell&amp;quot; instead of &amp;amp;lt;span class=&amp;quot;type&amp;quot;&amp;amp;gt;cell&amp;amp;lt;/span&amp;amp;gt;&lt;br /&gt;
* [http://www.bath.ac.uk/contact/ University of Bath] Person Finder results are encoded with hCards so you can easily create a vCard from any result. &lt;br /&gt;
** ERROR - attempt to use Implied-N optimization where that's not possible. --[[User:RyanKing|RyanKing]] 14:29, 5 Jan 2006 (PST)&lt;br /&gt;
* [http://richi.co.uk/blog/2005/12/structured-blogging.html Richi Jennings] has put up his attempt&lt;br /&gt;
** INVALID, missing FN --[[User:RyanKing|RyanKing]] 12:47, 5 Jan 2006 (PST)&lt;br /&gt;
* [http://www.shiftingpixel.com/about/ shifting pixel photoblog] has published an hCard.&lt;br /&gt;
** &amp;quot;organization_name&amp;quot; should be &amp;quot;organization-name&amp;quot; (s/_/-/), otherwise good --[[User:RyanKing|RyanKing]] 14:01, 5 Jan 2006 (PST)&lt;br /&gt;
&lt;br /&gt;
== Implementations ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
The following implementations have been developed which either generate or parse hCards. If you have an hCard implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.&lt;br /&gt;
&lt;br /&gt;
* There is [http://flickr.com/photos/factoryjoe/68755089/ evidence of built-in hCard support in the Konqueror browser].  Specifically, Konqueror 3.5, in KDE 3.5 (kubuntu Breezy w/ update).&lt;br /&gt;
* There is [http://tagcamp.org/index.cgi?ContactList evidence of a kwiki plugin for hCards].  Update: the [http://svn.kwiki.org/cwest/Kwiki-hCard/ hCard kwiki plugin svn repository].  See the [http://microwiki.caseywest.com/index.cgi?hCard documentation of the hCard kwiki plugin].&lt;br /&gt;
* [http://suda.co.uk/projects/X2V/ X2V] is a bookmarklet that parses hCard and produces a .vcf (vCard) stream.  Note: needs to be updated as the spec is refined&lt;br /&gt;
* [http://www.stripytshirt.co.uk Duncan Walker] has built [http://www.stripytshirt.co.uk/features/firefox/smartzilla a Firefox extension] that gets hCard data from a webpage, uses Brian Suda's XSL (locally) to transform it to vcard format and opens the resulting .vcf file.&lt;br /&gt;
* [http://george.hotelling.net/90percent/ George] has written a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script] that detects hCards and allows users to easily add them to their address book application.  Relies on the X2V web service to do the conversion.&lt;br /&gt;
* [http://blogmatrix.blogmatrix.com/ David Janes] has written a [[Greasemonkey]] [http://www.blogmatrix.com/include/microformat-find.user.js script] that finds many microformat elements, including hCards, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003376 provides a popup menu of actions]. The hCard to vCard conversion is done internally within the script. ''This does not work with FireFox 1.5+/GreaseMonkey 0.6.4+.''&lt;br /&gt;
* [http://diveintomark.org/ Mark Pilgrim] has also written an [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser Greasemonkey user script].  It is self-contained and does not rely on the X2V web service.&lt;br /&gt;
* [http://www.oliverbrown.me.uk/2005/09/03/a-working-microformats-extension-to-simplexml/ Oliver Brown] has written an &amp;quot;extension&amp;quot; to [http://www.php.net/simplexml SimpleXML] that gives simple access to hCard information in PHP 5.&lt;br /&gt;
* [http://thedredge.org/ Andrew D. Hume] has built a system (Wordpress plugin?) for [http://thedredge.org/2005/06/using-hcards-in-your-blog/ using hcards in your blog] to represent people leaving comments on blog posts.&lt;br /&gt;
* The [http://tantek.com/microformats/hcard-creator.html hCard creator] is a very simple, yet illustrative, open source user interface / form / script which creates an hCard in real-time as you type in a set of contact information. &lt;br /&gt;
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate hCard information ([http://ietf.org/rfc/rfc2629 RFC2629] is an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])&lt;br /&gt;
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - Open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards. &lt;br /&gt;
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] is a collection of palmpilot and sidekick tools. It includes X2V derivatives xhtml2hcard.xsl and toICal.xsl plus some [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest] materials&lt;br /&gt;
* [http://www.openpsa.org/ OpenPsa 2.x] CRM application uses hCard for all person listings. The widget is [http://www.midgard-project.org/midcom-permalink-922834501b71daad856f35ec593c7a6d reusable across Midgard CMS]&lt;br /&gt;
&lt;br /&gt;
== Additional Applications ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
There are numerous potential additional uses and applications for hCards on the Web.  The following are merely a few thoughts and possibilities that folks have come up with:&lt;br /&gt;
&lt;br /&gt;
* As an open standard/format for [http://www.gravatar.com/ Gravatars].&lt;br /&gt;
* Marking up individual authors of blog posts on a group blog&lt;br /&gt;
* Marking up people's names and URLs in a blogroll&lt;br /&gt;
* Any reference to people in blog posts (e.g. when citing them, or referencing them, or describing them, by name).&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
=== Normative References ===&lt;br /&gt;
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]&lt;br /&gt;
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426]&lt;br /&gt;
&lt;br /&gt;
=== Informative References ===&lt;br /&gt;
* [http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426]&lt;br /&gt;
* [http://w3.org/TR/REC-CSS1 CSS1]&lt;br /&gt;
* [http://tantek.com/log/2004/09.html#hcard hCard term introduced and defined on the Web, 20040930]&lt;br /&gt;
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]&lt;br /&gt;
* Contributed from http://developers.technorati.com/wiki/hCard.&lt;br /&gt;
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]&lt;br /&gt;
&lt;br /&gt;
==== Specifications That Use hCard ====&lt;br /&gt;
* [[adr]]&lt;br /&gt;
* [[geo]]&lt;br /&gt;
* [[hcalendar|hCalendar]]&lt;br /&gt;
* [[hreview|hReview]]&lt;br /&gt;
&lt;br /&gt;
==== Similar Work ====&lt;br /&gt;
* [http://www.intertwingly.net/wiki/pie/PaceBetterPersonElement Atom PaceBetterPersonElement]&lt;br /&gt;
* [http://www.jabber.org/jeps/jep-0054.html JEP-0054: vcard-temp]&lt;br /&gt;
&lt;br /&gt;
== Related Pages And Further Reading ==&lt;br /&gt;
* [[hcard-profile|hCard profile]] - The XMDP profile for hCard&lt;br /&gt;
&lt;br /&gt;
This 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.&lt;br /&gt;
&lt;br /&gt;
* [[hcard-brainstorming|hCard Brainstorming]] - where we are keeping our brainstorms and other explorations relating to hCard&lt;br /&gt;
* [[hcard-tests|hCard tests]] - a wiki page with actual embedded hCards to try parsing.&lt;br /&gt;
* [[hcard-faq|hCard FAQ]] - If you have any questions about hCard, check here, and if you don't find answers, add your questions!&lt;br /&gt;
* [[hcard-issues|hCard issues]] - Please add any issues with the specification to the issues page.&lt;br /&gt;
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].&lt;/div&gt;</summary>
		<author><name>Trovster</name></author>
	</entry>
</feed>