Microformats Wiki - User contributions [en]

mf2py

2018-02-27T21:40:58Z

TomMorris: mf2py moved from my personal github to microformats GitHub org

{{stub}}

This is a holding page for '''mf2py''', the [[microformats2]] parser for Python.

* [https://github.com/microformats/mf2py microformats/mf2py] on github
* [https://pypi.python.org/pypi/mf2py/ mf2py] on PyPI

You can test how mf2py parses HTML on the following pages:
* URL and/or textarea: https://kylewm.com/services/mf2
* URL entry: [https://mf2py.herokuapp.com/ mf2py.herokuapp.com]
* textarea entry: https://kartikprabhu.com/connection/mfparser
* another textarea: http://www.unmung.com/?html=

== See Also ==

* [[parsers]]
* [[microformats2]]
* [[validators]]

microformats2-parsing-rdf

2017-02-27T16:29:01Z

TomMorris: tidy

Below is a proposed mapping of the microformats2 data model to RDF.

== RDF model ==

In the document below, the RDF model is represented using the [https://en.wikipedia.org/wiki/Notation3 Notation3] syntax.

All RDF examples presume at least these basic external prefixes:

<source lang="text">
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
</source>

In addition, we shall use the profile defined on [[microformats-2]] as an RDF URI prefix:

<source lang="text">
@prefix uf: <http://microformats.org/profile/> .
</source>

== What is the subject? ==

In RDF, all data is in the form of subject, predicate, object triples. These map roughly to English statements. Subjects can be either URI references or blank nodes.

Mapping these adequately is problematic.

If the element which has the root class name for a microformats2 object also has an about attribute, that SHOULD be used to set the subject for the microformat.

If the element does not have an <code>'''about'''</code> attribute, or the HTML processor does not support parsing <code>'''about'''</code> attributes, then the subject for the microformat should be an RDF blank node.

If a parser is also parsing [[rdfa|RDFa]], it should use the same blank nodes as the subjects for microformats2 objects as it does for statements expressed in RDFa. Given this HTML:

<source lang="html4strict">
<div class="h-card p-name" typeof="foaf:Person" property="foaf:name">Tom Morris</div>
</source>

A microformats2 and RDFa-aware processor should produce Notation3 output with a singular blank node:

<source lang="text">
_:a a uf:h-card, foaf:Person;
foaf:name "Tom Morris";
uf:p-name "Tom Morris";
rdfs:label "Tom Morris" .
</source>

It should not separate out these two resources into separate blank nodes:

<source lang="text">
_:a a uf:h-card;
uf:p-name "Tom Morris";
rdfs:label "Tom Morris" .

_:b a foaf:Person;
foaf:name "Tom Morris" .
</source>

== Representing root class names ==

Root class names map neatly to <code>'''rdf:type'''</code>. In Notation3, this is represented with the shorthand <code>'''a'''</code>.

<source lang="html4strict">
<div class="h-card">Tom Morris</div>
</source>

<source lang="text">
_:bnode01 a uf:h-card .
</source>

This is compatible with the RDF specification, but differs from RDF best practice. As with Java and most programming languages, in RDF, it is customary to capitalize class names.

== Representing properties ==

Once we have inferred the class name, we need simply declare the properties.

For each <code>'''p-'''</code> prefixed property, an RDF statement should be produced with the subject being that of the microformats2 object, the property being the namespaced microformats property, and the object being either a plain literal or a language literal containing the string representation of the object (see language section below). This should be equal to the string value in the JSON output.

=== Multiple properties ===
If there are multiple instances of a property, this should result in multiple statements using the same property name.

This example hCard contains two category properties and two URL properties:

<source lang="html4strict">
<div class="h-card">
<img class="u-photo" alt="photo of Mitchell"
src="https://webfwd.org/content/about-experts/300.mitchellbaker/mentor_mbaker.jpg"/>
<a class="p-name u-url"
href="http://blog.lizardwrangler.com/"
>Mitchell Baker</a>
(<a class="u-url"
href="https://twitter.com/MitchellBaker"
>@MitchellBaker</a>)
<span class="p-org">Mozilla Foundation</span>
<p class="p-note">
Mitchell is responsible for setting the direction and scope of the Mozilla Foundation and its activities.
</p>
<span class="p-category">Strategy</span>
<span class="p-category">Leadership</span>
</div>
</source>

<source lang="text">
_:lizardwrangler a uf:h-card;
uf:u-photo <https://webfwd.org/content/about-experts/300.mitchellbaker/mentor_mbaker.jpg>;
uf:p-name "Mitchell Baker";
rdfs:label "Mitchell Baker";
uf:u-url <http://blog.lizardwrangler.com>;
uf:u-url <https://twitter.com/MitchellBaker>;
uf:p-org "Mozilla Foundation";
uf:p-note "Mitchell is responsible for setting the direction and scope of the Mozilla Foundation and its activities.";
uf:p-category "Strategy";
uf:p-category "Leadership" .
</source>

(In Notation3, it is possible to use commas as a shorthand form to represent multiple statements. This has been avoided in order to better illustrate the point in question.)

To convert from RDF to JSON, one should take all statements that have the same subject and property and group them together into an array.

=== Language ===
RDF allows three types of literal: plain literals, language literals and typed literals.

Typed literals contain a datatype annotation, language literals contain a language annotation (the same ISO country codes as is used in HTML's <code>'''lang'''</code> attribute and XML's <code>'''xml:lang'''</code> attribute).

Processors should work out the language tag (if any) of the elements containing microformat properties (using the latest RDFa specification) and emit language-tagged literals for p- prefixed properties. If no language tag is set in the HTML, emit plain literals for all p- prefixed properties.

For instance:

<source lang="html4strict">
<div class="h-card p-name" lang="ja">内閣総理大臣</div>

<div class="h-card p-name" lang="he">בִּנְיָמִין נְתַנְיָהוּ</div>
</source>

<source lang="text">
_:a a uf:h-card;
uf:p-name "内閣総理大臣"@ja .

_:b a uf:h-card;
uf:p-name "בִּנְיָמִין נְתַנְיָהוּ"@he .
</source>

=== rdfs:label ===
It is generally good practice for each resource to have an rdfs:label property. This maps to p-name.

Using Notation3 rules syntax:

<source lang="text">
@prefix log: <http://www.w3.org/2000/10/swap/log#> .
@forall ?s ?o .
{ :s uf:p-name :o . } log:implies { :s rdfs:label :o . } .
</source>

It is arguable that one may wish to then omit the p-name property from RDF representations of Microformats2 objects. The minor cost of extra duplication is outweighed by ensuring faithful representation and the ability to bidirectionally convert from RDF representations and JSON representations of Microformats2 objects.

== Representing nested microformats ==

This is easy. Each new object becomes a new RDF resource, and there is a relationship going from the parent object to the child object.

<source lang="html4strict">
<div class="h-event">
<a class="p-name u-url" href="http://indiewebcamp.com/2012">
IndieWebCamp 2012
</a>
from <time class="dt-start">2012-06-30</time>
to <time class="dt-end">2012-07-01</time> at
<span class="p-location h-card">
<a class="p-name p-org u-url" href="http://geoloqi.com/">
Geoloqi
</a>,
<span class="p-street-address">920 SW 3rd Ave. Suite 400</span>,
<span class="p-locality">Portland</span>,
<abbr class="p-region" title="Oregon">OR</abbr>
</span>
</div>
</source>

In Notation3, this would emit:

<source lang="text">
_:hevent1 a uf:h-event;
rdfs:label "IndieWebCamp 2012";
uf:p-name "IndieWebCamp 2012";
uf:u-url <http://indiewebcamp.com/2012>;
uf:dt-start "2012-06-30"^^xsd:date;
uf:dt-end "2012-07-01"^^xsd:date;
uf:location [
a uf:h-card;
rdfs:label "Geoloqi";
uf:p-name "Geoloqi";
uf:p-org "Geoloqi";
uf:u-url <http://geoloqi.com/>;
uf:p-street-address "920 SW 3rd Ave. Suite 400";
uf:p-locality "Portland";
uf:p-region "Oregon" .
].
</source>

== Mapping ==
:''See also'': [[microformats2-rdf-mapping]]

The RDF semantics of an hCard can be declared as an RDF document available from microformats.org. This can be used by RDF-minded parsers to draw inferences. In the case of hCard...

<source lang="text">
uf:h-card a owl:Class;
owl:sameAs <http://www.w3.org/2006/vcard/ns#VCard> .
</source>

Equivalent properties can also be declared:

<source lang="text">
uf:p-phone a owl:DatatypeProperty;
owl:sameAs <http://xmlns.com/foaf/0.1/phone>;
<http://schema.org/telephone> .
</source>

== Advanced: parsing microformats in context ==
=== Representative hCard parsing ===
:''See also:'' [[representative-hcard-parsing#representative_hCard_algorithm|representative hCard algorithm]], which operates on an already parsed data model, and thus works the same way.

If the parser is able to infer that a representative hCard is present on the page, one can represent this by using <var>foaf:primaryTopic</var> from the [http://xmlns.com/foaf/spec/#term_primaryTopic FOAF specification].

<source lang="text">
<> foaf:primaryTopic _:a .

_:a a uf:h-card;
uf:p-name "Tom Morris" .
</source>

hdita

2016-12-05T15:58:39Z

TomMorris: adding page for hdita

'''Lightweight DITA''' or '''HDITA''' is an HTML5-based ([[POSH]]) format for writing software documentation using the DITA model and to be compatible with the XML-based [[wikipedia:DITA|DITA]] toolchain to enable [[wikipedia:Topic-based authoring|topic-based authoring]].

== External links ==

* [http://dita.xml.org/blog/overview-of-lightweight-dita-xdita-and-hdita Overview of Lightweight DITA (XDITA and HDITA)]

hcalendar-fr

2016-12-05T15:48:38Z

TomMorris: Reverted edits by TomMorris (Talk) to last version by ChristopheDucamp

<entry-title>hCalendar 1.0</entry-title>
<span class="vcard"><span class="fn">[[User:Tantek|Tantek Çelik]]</span> (<span class="role">Editeur</span>, <span class="role">Auteur</span>)</span>, <span class="vcard"><span class="fn">[[User:Brian|Brian Suda]]</span> (<span class="role">Auteur</span>)</span>
(<span class="vcard"><span class="role">Traduction</span> : <span class="fn">[[User:ChristopheDucamp|Christophe Ducamp]]</span></span> : [[hcalendar|hCalendar - Seule la spécification originale fait référence]])
----

<dfn style="font-style:normal;font-weight:bold">hCalendar</dfn> est un format simple, ouvert pour publier des événements sur le web en utilisant une représentation 1:1 des propriétés VEVENT iCalendar ([[rfc-2445-fr|RFC2445]]) et valeurs en HTML. hCalendar est l'un des nombreux [[microformats-fr|microformats]] standards ouverts adaptable pour l'embarquement de données dans le HTML/HTML5, et Atom/RSS/XHTML ou autre XML.

Les déclarations de [[hcalendar-fr#Copyright|Copyright]] et [[hcalendar-fr#Brevets|brevets]] sont en vigueur.
Voir les [[hcalendar#Inspiration_et_Remerciements|remerciements]].

== Exemple ==
Voici un évènement simple en prose :
<blockquote><p>Le site microformats.org a été lancé le 2005-06-20 lors de la Conférence Supernova à San Francisco, CA, USA.</p></blockquote>

marqué avec hCalendar
<source lang=html4strict>
<span class="vevent">
<span class="summary">Le site microformats.org a été lancé</span>
le <span class="dtstart">2005-06-20</span>
lors de la Conférence Supernova
à <span class="location">San Francisco, CA, USA</span>.
</span>
</source>

'''Vous voulez démarrer par écrire un événement [[hcalendar-fr|hCalendar]] ?''' Utilisez le [http://microformats.org/code/hcalendar/creator hCalendar creator] pour écrire un événement et le publier, ou suivez les [[hcalendar-authoring-fr|trucs de publication hCalendar]] pour ajouter de la syntaxe hCalendar à votre page d'évènements à venir ou des événements que vous mentionnez dans vos billets de blogs, wikis, etc.

== Statut ==
hCalendar 1.0 est une spécification microformats.org. La discussion publique sur hCalendar a pris place sur [[hcalendar-feedback]], le canal [[irc-fr|irc]] #microformats sur irc.freenode.net, et la [http://microformats.org/discuss/mail/microformats-discuss/ liste de discussion microformats-discuss].

=== Langues disponibles ===
La [[hcalendar|version anglaise de cette spécification]] est la seule version normative. Pour les traductions de ce document, voir la section [[#traductions]].

=== Errata et Mises à Jour ===
Les erreurs connues et problématiques dans cette spécification sont corrigées dans les problématiques [[hcalendar-issues-resolved|résolues]] et [[hcalendar-issues-closed|fermées]]. Vérifiez-les svp avant de rapporter des [[hcalendar-issues|problématiques]].

Notez en particulier la [[dtend-issue-fr|problématique-dtend]] qui impacte les dates de fin. Les implémentations DEVRAIENT implémenter la résolution de cette question aussi rapidement que possible.

La mise à jour hCalendar 1.0.1 est actuellement en développement et incorpore les corrections connues tout comme le [[value-class-pattern-fr|modèle-de-classe-value]].

== Introduction ==
Le standard iCalendar ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]), a été très largement mis en œuvre avec interopérabilité (par exemple l'application "iCal" d'Apple intégrée dans MacOSX).

En outre, les blogueurs discutent souvent d'évènements sur leurs blogs -- événements à venir, compte-rendus des événements passés, etc. Avec simplement une tout petit peu de structure, les blogueurs peuvent discuter d'événements dans leurs blogs d'une manière telle que les spiders et autres agrégateurs puissent retrouver de tels événements, les convertir automatiquement vers iCalendar, et les utiliser dans n'importe quel service ou application iCalendar.

Cette spécification présente le format '''hCalendar''', qui est une représentation 1:1 du standard iCalendar précité en HTML sémantique. Les blogueurs peuvent embarquer à la fois les événements hCalendar directement dans leurs pages web, et les styliser avec CSS pour les faire apparaître comme désiré. En outre, hCalendar permet aux applications de retrouver l'information sur de tels événements à partir de pages Web sans avoir à référencer un fichier distinct.

{{rfc-2119-intro-fr}}

== Principes de Design XHTML Sémantique ==

{{semantic-xhtml-design-principles-fr}}

Pour les implémentations pratiques, il devrait être noté que le support d'Internet Explorer pour styliser les éléments <code><nowiki><abbr></nowiki></code> est pauvre et peut obliger à emballer les éléments.

== Format ==
=== En Général ===
Le standard iCalendar ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]) constitue la base de hCalendar.

Note : l'éditeur et les auteurs de cette spécification sont en train de suivre l'[http://lists.osafoundation.org/pipermail/ietf-calsify/ effort "iCal-Basic"] et ont l'intention de fonder le profil noyau du hcalendar sur iCal-Basic. Voir les références pour un lien vers le brouillon en cours.

Le format basique de hCalendar est d'utiliser les noms d'objet/propriété en bas de casse pour les noms de classes, et de mapper l'imbrication des objets iCalendar directement à l'intérieur des éléments XHTML imbriqués.

=== Nom de Classe Racine ===
Le nom de classe racine pour hCalendar est "vcalendar". Un élément avec un nom de classe "vcalendar" est lui-même appelé un ''hCalendar''.

Le nom de classe racine pour les événements est "vevent". Un élément avec un nom de classe "vevent" est lui-même appelé un ''événement hCalendar''.

Pour la commodité de publication, tant "vevent" et "vcalendar" sont traités comme des noms de classes racine pour les objectifs de parsage. Si un document contient des éléments avec le nom de classe "vevent" mais pas "vcalendar", la totalité du document a un contexte implicite "vcalendar".

'''vevent''' devrait être considéré comme obligatoire pour chaque inscription d'événement.

=== Propriétés et sous-propriétés ===
Les propriétés d'un hCalendar sont représentées par des éléments à l'intérieur du hCalendar. Les éléments avec les noms de classes des propriétés listées représentent les valeurs de ces propriétés. Quelques propriétés ont des sous-propriétés, et celles-ci sont représentées par des éléments à l'intérieur des éléments pour les propriétés.

=== Liste des Propriétés ===
Les propriétés hCalendar (sous-propriétés entre parenthèses comme ceci)

'''Requis :'''
* '''dtstart''' ([[iso-8601-fr|ISO date]])
* '''summary'''
Optionnel :
* location
* url
* dtend (ISO date), duration (ISO date duration)
* rdate, rrule
* category, description
* uid
* geo (latitude, longitude)
* attendee (partstat, role), contact, organizer
* attach
* status
* ... note de l'auteur : cette liste est incomplète (une liste incomplète est mieux que pas de liste) et est en train d'être rédigée à partir de la RFC2445 vers ici. La liste au-dessus des propriétés sont celles qui sont souvent utilisées dans hCalendar sur le web.

=== Profil ===
Le profil XMDP hCalendar est sur http://microformats.org/profile/hcalendar

Le contenu qui utilise hCalendar DEVRAIT référencer ce profil, c'est à dire :
<source lang=html4strict>
<head profile="http://microformats.org/profile/hcalendar">
</source>
ou
<source lang=html4strict>
<link rel="profile" href="http://microformats.org/profile/hcalendar">
</source>
ou
<source lang=html4strict>
Ce contenu utilise <a rel="profile" href="http://microformats.org/profile/hcalendar">hCalendar</a>.
</source>
Le contenu peut combiner les méthodes au-dessus.

=== Plus d'Equivalents Sémantiques ===
Pour quelques propriétés il existe un équivalent plus sémantique, et par conséquent elles reçoivent un traitement particulier, par exemple :
* <code>URL</code> dans iCalendar devient <code><a class="url" href="...">...</a></code> à l'intérieur de l'élément avec <code>class="vevent"</code> dans le hCalendar.
* <code>ATTENDEE</code>, <code>CONTACT</code>, et <code>ORGANIZER</code> dans le iCalendar PEUVENT être représentés par une [[hcard-fr|hCard]] dans le hCalendar .
* Un lieu nommé <code>LOCATION</code> (potentiellement avec une adresse et/ou geo) dans iCalendar PEUT être représenté par une [[hcard-fr|hCard]] imbriquée dans le hCalendar. De la même façon, une adresse <code>LOCATION</code> PEUT être représentée par un [[adr-fr|adr]] et un geo (latitude et longitude) <code>LOCATION</code> PEUT être représenté par un [[geo-fr|geo]].
* <code>UID</code> dans le iCalendar devient simplement une autre sémantique appliquée à un URL spécifique pour un événement hCalendar.
* <code>ATTACH</code> dans iCalendar devient un élément img ou object (où la valeur est stocké dans/retrouvée à partir des attributs 'src' ou 'data' respectivement). Un <code><a class="attach" href="...">...</a></code> peut aussi être utilisé, auquel cas l'attribut href est utilisé pour la valeur de propriété.

=== Propriétés Singulier vs Pluriel ===
Pour les propriétés qui sont singulières (par ex. "N" et "FN" extrait de vCard), le premier élément descendant avec cette classe-là devrait prendre effet, tous les autres étant ignorés.

Pour les propriétés qui peuvent être plurielles (par ex. "TEL" extrait de la vCard), chaque instance de classe devrait créer une instance de cette propriété.
Les propriétés plurielles avec des sous-types (par ex. TEL avec WORK, HOME, CELL extrait de la vCard) peuvent être optimisées pour partager un élément commun pour la propriété elle-même, avec chaque instance de sous-type étant un descendant proprement classé de l'élément propriété.

==== Propriétés Plurielles Singularisées ====
Parce que les noms de propriétés plurielles deviennent leurs équivalents singuliers, même si la propriété plurielle originale n'a permis seulement qu'une valeur unique avec plusieurs composants, ces composants-là multiples sont représentés chacun avec leurs propres singularités nommées propriété et la propriété a en fait plusieurs valeurs et est sujette au traitement ci-dessus des propriétés à plusieurs valeurs.

=== Lisible par des Humains vs Machines ===
Si un élément <code><nowiki><abbr></nowiki></code> est utilisé pour une propriété, alors l'attribut '<code>title</code>' de l'élément <code><nowiki><abbr></nowiki></code> est la valeur de la propriété, au lieu des contenus de l'élément, qui fournit à la place une version humainement présentable de la valeur. Cette spécification recommande que de tels éléments <code><nowiki><abbr></nowiki></code> soient utilisés pour les propriétés suivantes iCalendar :
* DTSTART, DTEND, DURATION, RDATE, RRULE

== Exemples ==

Voici un exemple échantillon avec plusieurs jours dans un iCalendar:

<source lang=text>
BEGIN:VCALENDAR
PRODID:-//XYZproduct//EN
VERSION:2.0
BEGIN:VEVENT
URL:http://conferences.oreillynet.com/pub/w/40/program.html
DTSTART:20051005
DTEND:20051008
SUMMARY:Web 2.0 Conference
LOCATION:Argent Hotel\, San Francisco\, CA
END:VEVENT
END:VCALENDAR
</source>

et un événement équivalent dans un format hCalendar avec différents éléments optimisés de façon appropriée. Voir [[hcalendar-example1-steps-fr|hCalendar-exemple1-étapes]] pour la dérivation.

<source lang=html4strict>
<div class="vevent">
<a class="url" href="http://conferences.oreillynet.com/pub/w/40/program.html">
http://conferences.oreillynet.com/pub/w/40/program.html
</a>
<span class="summary">Web 2.0 Conference</span>:
<abbr class="dtstart" title="2005-10-05">October 5</abbr>-
<abbr class="dtend" title="2005-10-07">7</abbr>,
at the <span class="location">Argent Hotel, San Francisco, CA</span>
</div>
</source>

Qui pourrait être affiché comme :

<div class="vevent">
<span class="url">http://conferences.oreillynet.com/pub/w/40/program.html</span> 
<span class="summary">Web 2.0 Conference</span>:
<abbr class="dtstart" title="2005-10-05">October 5</abbr>-
<abbr class="dtend" title="2005-10-07">7</abbr>,
at the <span class="location">Argent Hotel, San Francisco, CA</span>
</div>

Note 1 : Remarquez que c'est un microformat hCalendar '''live''', qui sera trouvé sur cette page par les parseurs.

Note 2 : Cet exemple avait "2005-10-08" comme la valeur de dtend, mais selon la résolution de la [[dtend-issue-fr|problématique-dtend]], cette valeur a été modifié en "2005-10-07" afin d'encourager les éditeurs/implémenteurs à mettre à jour immédiatement leur code/marquage et le [http://ufxtract.com/testsuite/hcalendar/hcalendar1.htm le tester].

Note 3 : Remarquez que le iCalendar dans la première partie de l'exemple a le code <code>DTEND:20051008</code>. Ce "8" n'est pas une faute de typo. iCalendar utilise des dates de fin globales<em>exclusives</em> (valeurs DTEND) et par conséquent requiert que la valeur DTEND soit réglée sur le jour complet <em>après</em> ce que les auteurs de contenu affichent de manière visible comme la date de fin d'un événement. La convention des dates de fin exclusives de iCalendar s'est avérée comme [[dtend-issue-fr|problematique et déroutante]] pour les auteurs de contenus et les éditeurs. Par conséquent, selon la résolution de la [[dtend-issue-fr|problématique dtend]] dans le hCalendar, la date de fin est déclarée exactement comme ce que publient les événements existants comme dates de fin visibles pour les humains, avec une date de fin <em>inclusive</em> (valeur de propriété dtend), dans cet exemple, 2005-10-07.

=== Exemple de réunion ===
L'<span id="Exemple_2">exemple</span> suivant spécifie un rendez-vous programmé qui commence
le 12 mars 1998 à 08:30 EST et se termine à 09:30 EST le 12 mars 1998.

<source lang=text>
BEGIN:VCALENDAR
BEGIN:VEVENT
UID:guid-1.host1.com
DTSTAMP:19980309T231000Z
DESCRIPTION:Project XYZ Review Meeting
SUMMARY:XYZ Project Review
DTSTART:19980312T133000Z
DTEND:19980312T143000Z
LOCATION:1CP Conference Room 4350
END:VEVENT
END:VCALENDAR
</source>

L'équivalent en hCalendar :

<source lang=html4strict>
<div class="vevent">
<h3 class="summary">XYZ Project Review</h3>
<p class="description">Project XYZ Review Meeting</p>
<p>To be held on
<span class="dtstart">
<abbr class="value" title="1998-03-12>the 12th of March</abbr>
from <span class="value">8:30am</span> <abbr class="value" title="-0500">EST</abbr>
</span> until
<span class="dtend">
<span class="value">9:30am</span> <abbr class="value" title="-0500">EST</abbr>
</span>
</p>
<p>Location: <span class="location">1CP Conference Room 4350</span></p>
<small>Booked by: <span class="uid">guid-1.host1.com</span> on
<span class="dtstamp">
<abbr class="value" title="1998-03-09">the 9th</abbr> at <span class="value">6:00pm</span>
</span>
</small>
</div>
</source>

Ceci pourrait s'afficher comme :

----

<div class="vevent">

<h3 class="summary">XYZ Project Review</h3>
<p class="description">Project XYZ Review Meeting</p>
<p>To be held on <time class="dtstart" datetime="1998-03-12 08:30:00-05:00">the 12th of March from 8:30am EST</time>
until <time class="dtend" datetime="1998-03-12 09:30:00-05:00">9:30am EST</time></p>
<p>Location: <span class="location">1CP Conference Room 4350</span></p>
<small>Booked by: <span class="uid">guid-1.host1.com</span> on <time class="dtstamp" datetime="1998-03-09 18:00">the 9th at 6:00pm</time></small></div>

----
Note 1 : L'information produit n'est pas nécessaire parce que le hCalendar est un format interchangeable. Quand hCalendar est transformé en iCalendar, le moteur transformant devrait ajouter sa propre ID produit.

Note 2 : Un élément entourant le <code><nowiki><span class="vcalendar"></nowiki></code> est optionnel et laissé comme ceci. Il est optionnel parce que le contexte d'un vcalendar est implicite quand un vevent est rencontré. Le contexte/étendue implicite est celui du document. Les auteurs peuvent explicitement utiliser des éléments avec class="vcalendar" pour emballer les ensembles de vevents qui appartiennent tous au même calendrier, par exemple au moment de publier plusieurs calendriers sur la même page.

Note 3 : L'information de version n'est pas nécessaire directement dans la syntaxe hCalendar parce que la version sera définie par le profil de qui est utilisé/référencé dans l'attribut 'profile' de l'élément <head>.

Note 4 : Les dates-horaires [[iso-8601-fr|ISO8601]] (requis par iCalendar) ne sont pas très humains. En outre, l'année est souvent comprise implicitement par les humains à partir du contexte. Par conséquent, le [[value-class-pattern-fr|modèle de classe value]] et les éléments <code><nowiki><abbr></nowiki></code> sont utilisés pour fournir simultanément des dates et/ou horaires compréhensibles par les humains dans les contenus visibles de l'élément, tout en plaçant respectivement des dates et horaires ISO8601 parsables par les machines si c'est nécessaire dans l'attribut 'title'. Selon le [[value-class-pattern-fr|modèle-de-classe-value]], les dates et horaires séparés DEVRAIENT être utilisés par les auteurs plutôt qu'un date-horaire complet ISO8601, et ce pour une meilleure lisibilité et écoute.

Note 5 : Selon la résolution [[dtend-issue-fr|dtend-problématique]], les dates DTEND sont fournies parce que les humains s'attendent à ce qu'elles soient (cohérentes avec le jour à laquelle un événement se termine), plutôt que la définition trompeuse de iCalendar (le jour d'après). De ce fait, les processeurs de hCalendar qui produisent des iCalendar doivent faire la transformation, ce qui revient à traiter une date de fin hCalendar globale <code>dtend</code> comme *inclusive*, et la convertir en une date de fin *[http://lists.osafoundation.org/pipermail/ietf-calsify/2005-September/000769.html DTEND exclusive]* au moment de produire iCalendar.

Note 6 : L'endroit (Location) dans cet exemple contient une structure implicite (nom du lieu de l'événement, ville, état) qui devrait être balisée explicitement sous une [[hcard-fr|hCard]]. Voir [http://microformats.org/wiki/hcalendar-brainstorming-fr#hCard_locations hCalendar brainstorming: hCard locations] pour une explication sur la façon de faire ça.

=== Plus d'exemples ===
Voir [[hcalendar-examples-fr|hCalendar exemples]] pour plus d'exemples, y compris des exemples extraits de la RFC 2445 iCalendar convertis en hCalendar.

== Exemples dans la jungle ==
Cette section est '''informative'''. Le nombre d'exemples hCalendar dans la jungle a grandi bien au-delà de la capacité de pouvoir être maintenus à l'intérieur de cette spécification. Ils ont été migrés vers une [[hcalendar-examples-in-wild-fr|page séparée]].

Voir [[hcalendar-examples-in-wild-fr|hCalendar Exemples dans la jungle]].

== Implémentations ==
Cette section est '''à des fins d'étude'''. Le nombre d'implémentations hCalendar a grandi bien au delà des capacités de pouvoir les maintenir dans la page. Elles ont été migrées vers une [[hcalendar-implementations-fr|page séparée]].

Voir [[hcalendar-implementations-fr|hCalendar Implementations]].

== Articles ==
Cette section est <strong>à des fins d'étude</strong>.

Voir : [[hcalendar-articles-fr|articles-hCalendar]].

==Boutons==
Cette section est <strong>à des fins d'étude</strong>. N'oubliez pas que vous pouvez ajouter un de nos [[buttons-fr#hCalendar|boutons]] vers la page, pour indiquer la présence de microformats hCalendar. Par exemple : http://www.boogdesign.com/images/buttons/microformat_hcalendar.png. Si vous pouvez le lier vers cette page (ou même sur une page sur votre site web, à propos de votre utilisation des microformats), plus il y en aura, mieux ce sera !

=== Copyright ===
Selon la parution dans le domaine public sur les pages utilisateur des auteurs ([[User:Tantek|Tantek Çelik]], [[User:Brian|Brian Suda]]), cette spécification est tombée dans le domaine public.

{{MicroFormatPublicDomainContributionStatement-fr}}

=== Brevets ===
{{MicroFormatPatentStatement-fr}}

== Références ==
=== Références Normatives ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [[hcard-fr|hCard]]
* [http://www.ietf.org/rfc/rfc2445.txt iCalendar RFC2445]
* [[iso-8601-fr|ISO8601]]

=== Références Informatives ===
* [http://w3.org/TR/REC-CSS1 CSS1]
* [http://tantek.com/log/2004/09.html#hcalendar terme hCalendar présenté et défini sur le Web, 20040930]
* [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation, 20040911]
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]
* [http://ietfreport.isoc.org/idref/draft-royer-ical-basic/ iCal-Basic (latest)] [http://www.faqs.org/ftp/pub/pub/internet-drafts/draft-royer-ical-basic-04.txt (draft 04)]
* [http://www.w3.org/TR/NOTE-datetime W3C Note sur les Formats de Dates et d'Heure]
* [http://www.imc.org/pdi/ Internet Mail Consortium Personal Data Interchange vCard and vCalendar]
* Contributed from http://developers.technorati.com/wiki/hCalendar

==== Spécifications qui utilisent hCalendar ====
* [[hreview-fr|hReview]]

==== Travaux en rapport ====
* [http://lists.osafoundation.org/pipermail/ietf-calsify/ IETF-calsify archives]
* [http://www.softwarestudio.org/iCal/2445Issues.html RFC2445 Issues List]
* [http://ietf.webdav.org/calsify/ CALSIFY WG Links And Resources]

== Pour aller plus loin ==
* [http://www.livejournal.com/users/jwz/444651.html jwz - Hula] (à lire)
* [http://www.jwz.org/doc/groupware.html Groupware Bad de Jamie Zawinski] critallise la raison pour hCalendar ('''emphase''' ajoutée ) :
<blockquote>"A cette heure, les gens font cela en publiant des fichiers .ics, mais ce n'est pas trivial de faire ainsi, et c'est du travail de la part des autres personnes pour les regarder. '''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.'''"</blockquote>

* [http://muddybranch.thejkgroup.com/ Jason Klemow's blog]
* [http://weblog.infoworld.com/udell/2006/01/11.html#a1368 Moving forward with microformats] de [http://weblog.infoworld.com/udell Jon Udell] fournit un exemple hCalendar et quelque discussion.
* Voir aussi les [http://www.technorati.com/cosmos/referer.html blogs qui discutent de cette page] et le [http://technorati.com/tags/hcalendar tag hCalendar]
* [http://fr.wikipedia.org/wiki/HCalendar article Wikipedia sur hCalendar] (requiert un remaniement, une expansion et une traduction)
* [http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-4-hcalendar/ Getting Semantic With Microformats, Part 4: hCalendar] par [http://www.ablognotlimited.com/ Emily Lewis] - ([http://microformateurs.org/2008/10/18/emily-lewis-parvenir-a-la-semantique-avec-les-microformats-4eme-partie-hcalendar/ Traduction en français])
* [http://www.peachpit.com/guides/content.aspx?g=webdesign&seqNum=356 Microformats: The Art of Markup: hCalendar] par [http://www.stuffandnonsense.co.uk/ Andy Clarke]
* [http://forabeautifulweb.com/blog/about/a_tribute_to_microformats_a_reader_question_answered/ A tribute to Microformats (a reader question answered)] par [http://www.stuffandnonsense.co.uk/ Andy Clarke]

=== Inspiration et Remerciements ===
Merci à :
* Adam Bosworth pour avoir mené la [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars présentation FOO Camp 2004 HTML For Calendars presentation] qui a rassemblé une masse critique de personnes intéressées.

== Pages Apparentées ==
{{hcalendar-related-pages-fr}}

== Traductions ==
Lisez la spécification hCalendar dans d'autres <span id="languages-fr">langues</span> :
* [[hcalendar|anglais-US]] - seule version normative de référence.
* [[hcalendar-ja|日本語]] (japonais)
* [[hcalendar-pl|Polski]] (polonais)
* [[hcalendar-ru|Русский]] (russe)

[[Category:Specifications]]
[[Category:hCalendar]]

hcard-fr

2016-12-05T15:47:57Z

TomMorris: Reverted edits by TomMorris (Talk) to last version by ChristopheDucamp

<entry-title>hCard 1.0</entry-title>
<span class="vcard"><span class="fn">[[User:Tantek|Tantek Çelik]]</span> (<span class="role">Editeur</span>, <span class="role">Auteur</span>)</span>, <span class="vcard"><span class="fn">[[User:Brian|Brian Suda]]</span> (<span class="role">Auteur</span>)</span>
(<span class="vcard"><span class="role">Traduction</span> : <span class="fn">[[User:ChristopheDucamp|Christophe Ducamp]]</span></span> : [[hcalendar|hCalendar - Seule la spécification originale fait référence]])

----
<dfn style="font-style:normal;font-weight:bold">hCard</dfn> est un format simple, ouvert pour publier sur le web des personnes, sociétés, organisations, en utilisant une représentation 1:1 des propriétés et des valeurs de la vCard ([[rfc-2426-fr|RFC2426]]) en HTML. hCard est l'un des nombreux standards [[microformats-fr|microformats]] ouverts adaptés pour l'embarquement dans le HTML/HTML5, et Atom/RSS/XHTML ou autre XML.

Les déclarations de [[hcard-fr#Copyright|Copyright]] et [[hcard-fr#Brevets|brevets]] sont en vigueur. Voir les [[hcard#Inspiration_et_Remerciements|remerciements]].

<div class="vcard">
; <span class="role">Editeur</span>
: <span class="fn">[[User:Tantek|Tantek Çelik]]</span> (<span class="url">http://tantek.com/</span>, et avant chez [http://technorati.com Technorati, Inc.] et [http://microsoft.com/ Microsoft Corporation])
</div>

; Auteurs
: [http://tantek.com/ Tantek Çelik] (affiliations ci-dessus)
: <span class="vcard"><span class="fn">[[User:Brian|Brian Suda]]</span> (<span class="url">http://suda.co.uk/</span>)</span>

Remerciements : Voir [[hcard-fr#Inspiration_et_Remerciements|Remerciements]].

Les déclarations de [[hcard-fr#Copyright|copyright]] et de [[hcard#brevets|brevets]] s'appliquent.

== Exemple ==
Les hCards sont le plus souvent utilisées pour représenter des personnes :
<source lang=html4strict>
<div class="vcard">
<a class="url fn" href="http://tantek.com/">Tantek Çelik</a>
</div>
</source>
et des organisations :
<source lang=html4strict>
<div class="vcard">
<a class="url fn org" href="http://microformats.org/">microformats.org</a>
</div>
</source>

La classe '''<code>vcard</code>''' est un ''[[hcard-fr#Nom_de_Classe_Racine|nom de classe racine]]'' qui indique la présence d'une hCard. Les classes '''<code>url</code>''', '''<code>fn</code>''', et '''<code>org</code>''' sont les ''propriétés'' qui indiquent les aspects de la hCard.

== Propriétés ==
<div style="white-space:nowrap;float:left">les propriétés communes de hCard (à l'intérieur de la classe <code>'''vcard'''</code>)
* <code>'''fn'''</code> - nom, formaté/complet. requis
* <code>'''n'''</code> - nom structuré, conteneur pour :
** <code>'''honorific-prefix'''</code> - par ex. Ms., Mr., Dr.
** <code>'''given-name'''</code> - nom donné (souvent en premier), le prénom
** <code>'''additional-name'''</code> - autre nom/milieu
** <code>'''family-name'''</code> - nom de famille (souvent en dernier)
** <code>'''honorific-suffix'''</code> - par ex. Ph.D., Esq.
* <code>'''nickname'''</code> - pseudo/alias, par ex. [[irc-fr|IRC]] <abbr title="nickname">nick</abbr>
* <code>'''org'''</code> - société/organisation
* <code>'''photo'''</code> - photo, icône, avatar
* <code>'''url'''</code> - page personnelle pour ce contact
* <code>'''email'''</code> - addresse e-mail
* <code>'''tel'''</code> - numéro de téléphone
* <code>'''[[adr]]'''</code> - adresse structurée, conteneur pour :
** <code>'''street-address'''</code> - rue <abbr title="number">#</abbr>+nom, <abbr title="apartment">appart.</abbr>/<abbr title="suite">suite</abbr>
** <code>'''locality'''</code> - ville ou village
** <code>'''region'''</code> - état ou province
** <code>'''postal-code'''</code> - code postal par ex. <abbr title="United States">U.S.</abbr> ZIP
** <code>'''country-name'''</code> - non du pays
* <code>'''bday'''</code> - anniversaire. [[date-pattern-fr|date ISO]].
* <code>'''category'''</code> - pour taguer les contacts
* <code>'''note'''</code> - notes concernant le contact
</div>
<div style="margin-top:-.4em; float:left;"><span style="display:none">Exemple de propriétés communes hCard :</span>
<ul style="list-style:none"><li><code><div class="'''vcard'''"></code>
<ul style="list-style:none; margin-top:-.02em">
<li><code><span class="'''fn'''">Sally Ride</span></code></li>
<li><code>(<span class="'''n'''"></code><ul style="list-style:none">
<li><code><span class="'''honorific-prefix'''">Dr.</span></code></li>
<li><code><span class="'''given-name'''">Sally</span></code></li>
<li><code><abbr class="'''additional-name'''">K.</abbr></code></li>
<li><code><span class="'''family-name'''">Ride</span></code></li>
<li><code><span class="'''honorific-suffix'''">Ph.D.</span></span>),</code></li></ul></li>
<li><code><span class="'''nickname'''">sallykride</span> (IRC)</code></li>
<li><code><div class="'''org'''">Sally Ride Science</div></code></li>
<li><code><img class="'''photo'''" src="<nowiki>http://example.com/sk.jpg</nowiki>"/> </code></li>
<li><code><a class="'''url'''" href="<nowiki>http://sally.example.com</nowiki>">w</a>,</code></li>
<li><code><a class="'''email'''" href="<nowiki>mailto:sally@example.com</nowiki>">e</a> </code></li>
<li><code><div class="'''tel'''">+1.818.555.1212</div></code></li>
<li><code><div class="'''adr'''"></code><ul style="list-style:none">
<li><code><div class="'''street-address'''">123 Main st.</div></code></li>
<li><code><span class="'''locality'''">Los Angeles</span>, </code></li>
<li><code><abbr class="'''region'''" title="California">CA</abbr>, </code></li>
<li><code><span class="'''postal-code'''">91316</span></code></li>
<li><code><div class="'''country-name'''">U.S.A</div></div></code></li></ul></li>
<li><code><time class="'''bday'''">1951-05-26</time> birthday</code></li>
<li><code><div class="'''category'''">physicist</div></code></li>
<li><code><div class="'''note'''">First American woman in space.</div></code></li></ul></li>
<li><code></div></code></li></ul>
</div>
<div style="clear:both; padding:1em 0 0.5em 0">Voir la [[hcard-fr#Liste_des_propriétés|liste complète des propriétés]] pour la liste complète.
</div>
__TOC__

=== Commencer à écrire une [[hcard-fr|hCard]] ===
* Utilisez le formulaire [http://microformats.org/code/hcard/creator hCard creator] saisir l'information de contact et la publier.
* Voir les [[hcard-authoring-fr|exemples de publication de hCard]] pour ajouter hCard à vos pages de contact actuelles.

== Statut ==
hCard 1.0 est une spécification microformats.org. La discussion publique a pris place sur [[hcard-feedback]], le canal [[irc-fr|irc]] #microformats sur irc.freenode.net et la [http://microformats.org/discuss/mail/microformats-discuss/ liste de diffusion microformats-discuss].

=== Langues disponibles ===
La version anglaise de cette spécification sur [[hCard]] est la seule version normative. Pour les traductions de ce document voir la section [[#traductions]].

=== Errata et Mises à jour ===
Les erreurs connues et problématiques de cette spécification sont corrigées dans les problématiques [[hcard-issues-resolved|résolues]] et [[hcard-issues-closed|fermées]]. Regardez-les svp avant de rendre compte de [[hcard-issues|problématiques]].

La mise à jour hCard 1.0.1 est actuellement en développement et incorpore les corrections connues tout comme le [[value-class-pattern-fr|modèle-de-classe-value]].

== Origines ==
Le standard vCard ([[rfc-2426-fr|RFC2426]]), a été largement implémenté de façon inter-opérable. (par ex. dans l'application "Carnet d'Adresses" d'Apple intégrée dans MacOSX).

En outre, beaucoup de blogueurs s'identifient eux-mêmes par un nom et discutent avec leurs amis et familles. Avec juste un peu de structure, les blogueurs peuvent discuter avec des personnes dans leurs blogs d'une telle façon que les spiders et autres agrégateurs peuvent retrouver cette information, la convertir automatiquement en vCards et l'utiliser dans n'importe quelle application ou service vCard.

Cette spécification présente le format '''hCard''', qui utilise une représentation 1:1 des propriétés et valeurs du standard vCard mentionné ci-dessus, en HTML sémantique. Les blogueurs peuvent tout à la fois embarquer directement les hCards dans leurs pages web et les styliser avec CSS pour les faire apparaître comme ils le désirent. En outre, hCard permet aux applications de retrouver directement l'information à partir des pages web sans avoir à référencer un fichier séparé.

Utilisez le [http://microformats.org/code/hcard/creator hCard creator] et copiez le code HTML qu'il génère sur votre blog ou site web pour publier votre information de contact.

== Conformité ==
{{rfc-2119-intro-fr}}

== Format ==
=== En Général ===
Le standard vCard ([[rfc-2426-fr|RFC2426]]) forme la base de hCard.

Le format basique de hCard est d'utiliser les noms d'objet/propriété vCard en bas de casse pour les noms de classes, et de mapper l'imbrication des objets vCard directement dans les éléments HTML imbriqués.

=== Nom de Classe Racine===
Le nom de classe racine pour une hcard est "vcard". Un élément avec un nom de classe "vcard" est lui même appelé une ''hCard''.

=== Propriétés et Sous-propriétés ===
Les propriétés d'une hCard sont représentées par les éléments à l'intérieur de la hCard. Les éléments avec des noms de classes des propriétés listées représentent les valeurs de ces propriétés. Quelques propriétés ont des sous-propriétés, et celles-ci sont représentées par les éléments à l'intérieur des éléments pour les propriétés.

=== Liste des propriétés ===
Propriétés hCard (sous-propriétés entre parenthèses comme ceci)

'''Requis :'''
* '''fn'''
* <span id="property-list-n">'''n'''<sup style="font-size:smaller">[[#note1|1]]</sup></span>
** family-name
** given-name
** additional-name
** honorific-prefix
** honorific-suffix
Optionnel :
* [[adr-fr|adr]]
** post-office-box
** extended-address
** street-address
** locality
** region
** postal-code
** country-name
** type
** value
* agent
* bday
* category
* class
* email (type, value)
* geo
** latitude
** longitude
* key
* label
* logo
* mailer
* nickname
* note
* org (organization-name, organization-unit)
* photo
* rev
* role
* sort-string
* sound
* <span id="property-list-tel">tel<sup style="font-size:smaller">[[#note2|2]]</sup> (type, value)</span>
* title
* tz
* uid
* url

=== Notes sur les Propriétés===
* <span id="note1">[[#property-list-n|1. ^]]</span> : La propriété 'n' est {{optional-fr}} si n'importe quelle [[hcard-fr#Optimisation_implicite_"n"|règle d'optimisation implicite 'n']] est en vigueur.<br />
* tel
** <span id="note2">[[#property-list-tel|2. ^]]</span>: tel - Les auteurs PEUVENT vouloir suivre le [http://en.wikipedia.org/wiki/E.123 standard E.123] pour écrire les valeurs de numéros de téléphone.
** Les valeurs lettre (par ex 1-555-FORMATS) DOIVENT être converties en nombres. Utilisez un <code>abbr</code> pour afficher les lettre et fournir simultanément une valeur numérique, par ex. <code><nowiki><abbr title="+15553676287">+1-555-FORMATS</abbr></nowiki></code>.

=== Propriétés Singulières vs. Plurielles ===
Les propriétés singulières : 'fn', 'n', 'bday', 'tz', 'geo', 'sort-string', 'uid', 'class', 'rev'. Pour les propriétés qui sont singulières, le premier élément descendant avec cette classe DEVRAIENT s'exécuter, toutes les autres étant ignorées.

Toutes les autres propriétés PEUVENT être plurielles. Chaque instance de classe de telles propriétés crée une instance de cette propriété.

=== Lisible par Humain vs. Machine ===
Les contenus de textes visibles par les humains d'un élément pour une propriété représente la valeur de cette propriété, avec quelques exceptions :

Si un élément <code><a></code> est utilisé pour une propriété, alors l'attribut '<code>title</code>' (si présent) de l'élément <code><abbr></code> est la valeur de la propriété, au lieu des contenus de l'élément, qui fournit à la place une version plus humainement présentable de la valeur.

Si un élément <code><a></code> est utilisé pour une ou plusieurs propriétés, il {{must-fr}} être traité comme suit :
# Pour la propriété 'photo' et toute autre propriété qui prend un URL comme sa valeur, l'attribut <code>href="..."</code> fournit la valeur de la propriété.
# Pour les autres propriétés, le contenu de l'élément est la valeur de la propriété.

Si un élément <code><img></code> est utilisé pour une ou plusieurs propriétés, il {{must-fr}} être traité comme suit :
# Pour la propriété 'photo' et toute autre propriété qui prend une URL comme sa valeur, l'attribut fournit la valeur de propriété.
# Pour les autres propriétés, l'attribut '<code>alt</code>' de l'élément <code><img></code> est la valeur de la propriété.

Si un élément <code><object></code> est utilisé pour une ou plusieurs propriétés, il {{must-fr}} être traité comme suit :
# Pour la propriété 'photo' et toute autre propriété qui prend une URL comme sa valeur, l'attribut <code>data="..."</code> fournit la valeur de la propriété.
# Pour les autres propriétés, le contenu de l'élément est la valeur de la propriété.

=== Extraction de Valeur ===
Parfois, seule une partie d'un élément qui est l'équivalent d'une propriété devrait être utilisée pour la valeur de la propriété. Ceci arrive typiquement quand une propriété a un sous-type, comme 'tel'. A cette intention, le nom de classe spécial "<code>value</code>" est introduit pour extraire le sous-ensemble de l'élément qui est la valeur de la propriété. Par exemple, voici un fragment hCard pour marquer un numéro de téléphone de domicile :<br />

vCard :
<source lang=html4strict>
TEL;TYPE=HOME:+1.415.555.1212
</source>

hCard :
<source lang=html4strict>
<span class="tel">
<span class="type">home</span>:
<span class="value">+1.415.555.1212</span>
</span>
</source>

Ce fragment de hCard pourrait s'afficher comme :
<div style="border: thin dashed black; width: 95%; padding: .5em 1em;">
<span class="tel">
<span class="type">home</span>:
<span class="value">+1.415.555.1212</span>
</span>
</div>

Vous pourriez vouloir personnaliser/localiser la ponctuation visible et ne pas vouloir que les machines la voient. Utilisez plusieurs éléments de classe "value" qui sont alors concaténés, par ex :

<source lang=html4strict>
<span class="tel">
<span class="type">home</span>:
<span class="value">+1</span>.<span class="value">415</span>.<span class="value">555</span>.<span class="value">1212</span></span>
</span>
</source>

Aucun changement à l'affichage, mais la valeur de propriété analysée devient alors en vCard :

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



=== Exceptions de Propriétés ===
vCard a plusieurs propriétés qui soit ne font pas de sens, ou sont déjà imbriquées dans le contexte d'une page web.
Cette section explique ce qu'il faut (ou ne pas) faire avec elles :

# Les propriétés de la vcard '''NAME''', '''PROFILE''', '''SOURCE''', '''PRODID''', '''VERSION''' sont définies dans les Sections 2.1.2, 2.1.3, 2.1.4, 3.6.3, 3.6.9 de la [[rfc-2426|RFC2426]]. Les éditeurs de contenus NE DOIVENT PAS ({{must-not-fr}}) utiliser ces propriétés dans leurs hCards, et par conséquent, les clients/parseurs de hCard DOIVENT ({{must-fr}}) IGNORER ces propriétés si elles sont trouvées dans une hCard. Au lieu de cela, les convertisseurs hCard vers vCard DEVRAIENT ({{should-fr}}) utiliser le titre de la page où la hCard est trouvée (c'est à dire l'élément <code><title></code> dans les documents HTML) pour construire la propriété NOM, et ils {{may-fr}} produire une valeur PROFILE de "<code>VCARD</code>" selon la [[rfc-2426-fr|RFC2426]], ils DEVRAIENT ({{should-fr}}) utiliser l'URL de la page où est trouvée la hCard pour construire la propriété SOURCE (c'est à dire peut-être comme un paramètre vers un URL/service qui convertir les hCards en vCards), pour un flux de sortie vCard (par ex. un fichier vcf).
Seuls les services/applications qui produisent de véritables vCards devraient écrire la propriété PRODID, avec l'identifiant produit pour l'application/service. De la même façon, seuls de tels services/applications devraient écrire la propriété VERSION, avec la valeur "3.0" (sans guillemets) selon la [[rfc-2426-fr|RFC2426]] Section 3.6.9.

=== Info Contact Organisation ===
Si les propriétés "FN" et "ORG" (organisation) ont exactement la même valeur (généralement parce qu'elles sont
réglées sur le même élément, par ex. class="fn org"), alors la hCard représente l'information de contact pour une société, une organisation ou un lieu et {{should-fr}} être traitée comme telle. Dans ce cas l'auteur {{must-not-fr}} NE DOIT aussi PAS régler la propriété "N", ou la régler (et n'importe quelles sous-propriétés) explicitement vers la chaîne vide "".
Par conséquent les parseurs {{should-fr}} devraient gérer dans ce cas la propriété manquante "N" en
sous-entendant des valeurs vides pour toutes les sous-propriétés "N".

=== Optimisation implicite "N" ===
Bien que vCard requiert que la propriété "N" soit présente, les auteurs de la spécification vCard ([[rfc-2426-fr|RFC2426]]) eux-mêmes n'incluent pas les propriétés "N" dans leurs vCards près de la fin de la spec (p.38). Cette contradiction apparente peut être résolue en permettant simplement à la propriété "FN" de sous-entendre les valeurs de la propriété "N" dans les cas typiques fournies dans la spécification. Nous faisons cela explicitement dans hCard.

Si "FN" et "ORG" ne sont pas les mêmes (voir section précédente) et si la valeur de la propriété "FN" est exactement de deux mots (séparés par un espace blanc) et s'il n'y a pas de propriété explicite "N", alors la propriété "N" est inférée à partir de la propriété "FN".
Pour les "FN"s avec soit un mot voir au-dessous, et pour trois mots ou plus, l'auteur {{must-fr}} DOIT explicitement baliser le "N", exception faite pour le cas de l'information de contact organisation, [[hcard-fr#Info_Contact_Organisation|voir au-dessus]] pour cela.

# Le contenu de "FN" est brisé en deux "mots" séparés par un espace blanc.
# Le ''premier'' mot de ''FN'' est interprété comme le "given-name" (prénom) pour la propriété "N".
# Le ''second/dernier'' mot de "FN" est interprété comme le "family-name" pour la propriété "N".
# Exception : Si le premier mot se finit par une "," virgule, alors le premier mot (moins la virgule à la fin s'il y en a) est interprété comme le "family-name" et le second mot est interprété comme le "given-name" (prénom).

Ceci permet une simplification dans le cas typique des gens déclarant :
* given-name (espace) family-name
* family-name (virgule) given-name

=== Optimisation implicite du "nickname" ===
Du fait de la prévalence de l'utilisation sur le web de pseudos/handles/nomsutilisateurs dans les contenus publiés sur le Web (par ex. les auteurs des [[hreview-fr|critiques]]), hCard a aussi une
optimisation implicite de "nickname" pour gérer cela.

De la même manière que l'optimisation sous-entendue "n", si "FN" et "ORG" ne sont pas les mêmes, et
si la valeur de la propriété "FN" est exactement d'un mot, et s'il n'y a pas de propriété "N" explicite, alors :

# Le contenu du "FN" {{must-fr}} être traité comme une valeur de propriété "nickname".
# Les parseurs devraient ({{should-fr}}) gérer la propriété manquante "N" par des valeurs vides implicites pour toutes les sous-propriétés "N".

Note : la hCard peut ({{may-fr}}) avoir des valeurs de propriétés explicites supplémentaires "nickname" en plus du nickname sous-entendu.

=== Optimisation implicite "organization-name" ===
La propriété "ORG" a deux sous-propriétés, organization-name et organization-unit. Très souvent les auteurs ne publient que organization-name. De ce fait si une propriété "ORG" n'a pas d'"organization-name" dedans, alors la totalité des contenus DOIT ({{must-fr}}) être traitée comme le "organization-name".

=== Tags en tant que Catégories ===
Les catégories dans hCard peuvent ({{may-fr}}) être représentées par des tags avec rel-tag.
Quand une propriété category est un rel-tag, le tag (comme défini par rel-tag) est utilisé pour cette catégorie.

=== valeurs sous-propriété type ===
La sous-propriété 'type' en particulier prend différentes valeurs selon quelle propriété est une sous-propriété de. Ces valeurs de sous-propriétés 'type' sont INSENSIBLES à la casse, ceci voulant dire que "Home" est équivalent à "home", tout comme elle est multivalorisée, par ex. un téléphone peut être home et pref (éré) :

vCard :
<source lang=html4strict>
TEL;TYPE=HOME,PREF:+1.415.555.1212
</source>

hCard :
<source lang=html4strict>
<span class="tel"><span class="type">Home</span> (<span class="type">pref</span>erred):
<span class="value">+1.415.555.1212</span>
</span>
</source>

Ceci pourrait être affiché sous :

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

==== type avec valeur non spécifiée ====
Quand le type d'une propriété est spécifié, et qu'il n'y ait pas de valeur explicite spécifiée, alors tout dans la propriété excepté le type est considéré la valeur de la propriété, par exemple :

<source lang=html4strict>
<span class="tel"><span class="type">Home</span> +1.415.555.1212</span>
</source>

est équivalent à :

<source lang=html4strict>
<span class="tel"><span class="type">Home</span><span class="value"> +1.415.555.1212</span></span>
</source>

Et ce fait le type est "home" et la valeur est "+1.415.555.1212".

==== adr tel email types ====

Les listes suivantes sont ''informative''s. Voir sections RFC2426 3.2.1 ADR, 3.3.1 TEL, et 3.3.2 EMAIL respectivement pour les valeurs type normatives. Elles sont répétées ici pour la facilité. La(es) valeur(s) de sous-propriétés type est (sont) d'abord dans chaque liste et toutes indiquées en LETTRES CAPITALES. Les types peuvent être multivalorisées.

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

=== Profil ===

Le <span id="Profil_XMDP">Profil XMDP</span> est sur http://microformats.org/profile/hcard

Le contenu qui utilise hCard DEVRAIT référencer ce profil, c'est à dire :
<source lang=html4strict>
<link rel="profile" href="http://microformats.org/profile/hcard">
</source>
ou
<source lang=html4strict>
Ce contenu utilise <a rel="profile" href="http://microformats.org/profile/hcard">hCard</a>.
</source>
ou
<source lang=html4strict>
<head profile="http://microformats.org/profile/hcard">
</source>
(L'attribut de profil est déprécié en HTML5)
Le contenu peut aussi combiner les méthodes au-dessus.

=== Détails Parsage ===
Voir [[hcard-parsing-fr|hCard parsing]].

== Exemples ==
Cette section est informative.

=== Echantillon vCard ===
Voilà une vCard échantillon.

<source lang=html4strict>
BEGIN:VCARD
VERSION:3.0
N:Çelik;Tantek
FN:Tantek Çelik
URL:http://tantek.com/
END:VCARD
</source>

et un équivalent en hCard avec différents éléments optimisés proprement.
Voir [[hcard-example1-steps-fr|hCard Exemple 1]] pour la dérivation.

<source lang=html4strict>
<div class="vcard">
<a class="url fn" href="http://tantek.com/">Tantek Çelik</a>
</div>
</source>

Cette carte pourrait être affichée comme :
<div style="border: thin dashed black; width: 95%; padding: .5em 1em;">
[http://tantek.com/ Tantek Çelik]
</div>

Note : L'information de version n'est pas directement nécessaire dans le balisage hCard parce que la version sera définie par le profil de hCard qui est utilisé/référencé dans l'attribut 'profile' de l'élément <head>.

===Exemple Live===
Voici les détails de contacts de [http://www.commerce.net/ Commercenet], sous forme d'une hCard vivante qui sera détectée, sur cette page, par les outils de parsage de microformats :

<div class="vcard">
<div class="fn org">'''CommerceNet'''</div>
<div class="url">'''<nowiki>http://www.commerce.net/</nowiki>'''</div>
<div class="adr">'''<span class="type">Work</span>:'''
<div class="street-address">'''169 University Avenue'''</div>
<span class="locality">'''Palo Alto'''</span>, <span class="region">'''CA'''</span>  <span class="postal-code">'''94301'''</span>
<div class="country-name">'''USA'''</div>
</div>
<div class="tel">'''<span class="type">Work</span> +1-650-289-4040'''</div>
<div class="tel">'''<span class="type">Fax</span> +1-650-289-4041'''</div>
<div>'''Email <span class="email"><nowiki>info@commerce.net</nowiki></span>'''</div>
</div>

Le marquage, graissage omis pour la clarté, avec les améliorations sémantiques suivantes :
* <code>abbr</code> pour épancher les abréviations
* hyperlien du nom de l'org avec l'url

<source lang=html4strict>
<div class="vcard">
<a class="fn org url" href="http://www.commerce.net/">CommerceNet</a>
<div class="adr">
<span class="type">Work</span>:
<div class="street-address">169 University Avenue</div>
<span class="locality">Palo Alto</span>,
<abbr class="region" title="California">CA</abbr>  
<span class="postal-code">94301</span>
<div class="country-name">USA</div>
</div>
<div class="tel">
<span class="type">Work</span> +1-650-289-4040
</div>
<div class="tel">
<span class="type">Fax</span> +1-650-289-4041
</div>
<div>Email:
<span class="email">info@commerce.net</span>
</div>
</div>
</source>

=== Plus d'Exemples ===
Voir [[hcard-examples-fr|exemples hCard]] pour plus d'exemples, y compris tous les exemples extraits de la [[rfc-2426-fr|RFC2426]] vCard convertie en hCard.

== exemples dans la jungle ==
Cette section est '''informative'''. Le nombre d'exemples de hCard dans la jungle a grandi bien au delà de la capacité de pouvoir être maintenu en ligne et associé à cette spécification. Ils ont migré sur une [[hcard-examples-in-wild-fr|page séparée]].

Voir [[hcard-examples-in-wild-fr|Exemples hCard dans la jungle]].

== Implémentations ==
Cette section est '''informative'''. Le nombre d'implémentations de hCard a aussi grandi au delà de la capacité de pouvoir les maintenir sur cette même page. Elles ont été migrées sur une [[hcard-implementations-fr|page séparée]].

Voir [[hcard-implementations-fr|Implémentations hCard]].

== Articles ==
Cette section est <strong>informative</strong>. Pour <span id="En_savoir_plus">en savoir plus</span> sur hCard, voir [[hcard-articles-fr|hCard-articles]].

==Boutons==
Vous pouvez utiliser ces boutons sur les pages avec des hCards. Voir [[buttons-fr#hCard]] pour toutes les additions récentes.
* http://www.crowley.nl/images/hcard.png (miroir : http://www.davidjanes.com/images/mf_hcard.png)
* http://rbach.priv.at/2006/buttons/hcard.png
* http://www.boogdesign.com/images/buttons/microformat_hcard.png
* boutons CSS, sur [http://re-run.com/about/microformat-badges microformat badges @ re-run]

== Copyright ==
Selon la sortie en domaine public sur les pages-utilisateurs des auteurs ([[User:Tantek|Tantek Çelik]], [[User:Brian|Brian Suda]]) cette specification est publiée dans le domaine public.

{{MicroFormatPublicDomainContributionStatement-fr}}

== Brevets==
{{MicroFormatPatentStatement-fr}}

== Références ==
=== Références Normatives ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426]
* [http://www.itu.int/rec/T-REC-E.123-200102-I/en ITU recommendation E.123] format des numéros de téléphone (document chargeable)
* [[rfc-2119-fr|RFC 2119]]

=== Références Informatives ===
* [[hcard-history-fr|histoire de la hCard]]
** [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 présentation Simple Semantic Formats, 2004-09-10]
** [http://tantek.com/log/2004/09.html#hcard terme hCard introduit et défini sur le Web, 2004-09-30]
** Contribué à partir de http://developers.technorati.com/wiki/hCard 2005-06-20
** Contributions provenant de http://developers.technorati.com/wiki/hCard.
* [http://www.dante.net/np/ds/osi/9594-6-X.520.A4.ps X.520 dans Postscript] ([http://72.14.253.104/search?q=cache:FjqzsFu4h20J:www.dante.net/np/ds/osi/9594-6-X.520.A4.ps HTMLization courtesy of Google Cache]) - vCard fait référence au ROLE comme étant "based on the X.520 Business Category explanatory attribute".
* [http://www.w3.org/2002/12/cal/rfc2426 version remise en forme HTML de la RFC2426]
* [http://w3.org/TR/REC-CSS1 CSS1]
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]
* [http://en.wikipedia.org/wiki/E.123 Résumé Wikipedia de la Recommandation ITU-T E.123] - pour les valeurs "TEL".
* [http://www.imc.org/pdi/ Internet Mail Consortium Personal Data Interchange vCard and vCalendar]
* [[iso-8601|ISO8601]]

==== Spécifications Qui Utilisent hCard ====
* [[adr-fr|adr]]
* [[geo-fr|geo]]
* [[hcalendar-fr|hCalendar]]
* [[hreview-fr|hReview]]

==== Travaux Equivalents ====
Cette section est '''informative'''.
* [http://www.intertwingly.net/wiki/pie/PaceBetterPersonElement Atom PaceBetterPersonElement]
* [http://www.jabber.org/jeps/jep-0054.html JEP-0054: vcard-temp]

== Inspiration et Remerciements ==
Cette section est '''informative'''.
Remerciements à mon bon ami [http://vadim.com/ Vadim] qui m'a présenté vCard il y a de ''nombreuses'' années,
et si j'avais prêté alors un peu plus d'attention, j'aurais pu peut-être aider beaucoup de personnes à éviter de perdre du temps à réinventer beaucoup de roues des standards.

== Notes sur la dérivation provenant de la vCard ==
Cette section est ''informative''.

=== Principes de Design XHTML Sémantique ===
{{semantic-xhtml-design-principles-fr}}

=== Plus d'Equivalents Sémantiques ===
Pour quelques propriétés, il existe quelques éléments HTML qui correspondent mieux et portent leurs sémantiques. Les propriétés suivantes DEVRAIENT être encodées avec le HTML suivant :
* <code>URL</code> dans vCard devient <code><a class="url" href="...">...</a></code> dans l'élément avec <code>class="vcard"</code> dans hCard.
* De la même manière, <code>EMAIL</code> dans la vCard devient <code><nowiki><a class="email" href="mailto:...">...</a></nowiki></code>
* <code>PHOTO</code> dans la vCard devient <code><img class="photo" src="..." alt="Photo de ..." /></code> ou <code><object class="photo" data="..." type="...">Photo de ...</object></code>
* <code>UID</code> dans vCard devient simplement une autre sémantique appliquée à un URL spécifique (ou EMAIL) pour une hCard.

==== Propriétés Singulières ====
Les propriétés Singulières : "FN", "N", "BDAY", "TZ", "GEO", "SORT-STRING", "UID", "CLASS".

Toutes les autres propriétés sont plurielles. Cette liste a été dérivée en analysant la sémantique des propriétés individuelles dans la RFC2426 vCard et en déterminant logiquement qu'elles DOIVENT être singulières selon leurs sémantiques. Voir [[hcard-singular-properties-fr|propriétés hcard singulier]] pour des explications.

==== Propriétés Plurielles Singularisées ====
Parce que les noms de propriétés plurielles deviennent leurs équivalents singuliers, même si la propriété plurielle originale ne permettait qu'une valeur unique avec plusieurs composants, ces composants multiples sont représentés chacun avec leur propre singularité appelée propriété
et la propriété est en fait multivalorisée et sujette au traitement ci-dessus des propriétés multivalorisées.

== Pages Apparentées ==
{{hcard-related-pages-fr}}

[[Category:Specifications]]
[[Category:hCard]]

== Traductions ==
Lisez la spécification hCard dans d'autres <span id="langues">langues</span> :
* [[hcard|anglais]] - la version normative de la spécification seule version de référence
* [[hcard-ru|Русский]]
* [[hcard-ja|日本語]]
* [[hcard-zh|漢語]]

Main Page-fr

2016-12-05T15:47:51Z

TomMorris: Reverted edits by TomMorris (Talk) to last version by ChristopheDucamp

<entry-title>Bienvenue sur le wiki des microformats !</entry-title>

'''Les <dfn>microformats</dfn>''' sont des extensions au HTML pour marquer les [[hcard-fr|personnes et organisations]], [[hcalendar-fr|événements]], [[adr-fr|endroits]], [[hatom-fr|billets de blog]], [[hproduct-fr|produits]], [[hreview-fr|critiques]], [[hresume-fr|C.V.]], [[hrecipe-fr|recettes]] etc. Les sites utilisent les microformats pour publier une API standard qui est consommée et utilisée par les [[search engines-fr|moteurs de recherche]], [[browsers-fr|navigateurs]] et d'autres outils. Regardez [[what-are-microformats-fr|C'est Quoi les Microformats]] pour en savoir plus.

* {{NewMarker-fr}} '''[[microformats2-fr|microformats2]]''' est la dernière extension de langage de marquage stable et interopérable. Utilisez-la sur les pages web publics de pour les APIs HTML.

==Introduction==
{{main-fr|introduction-fr}}
Ce wiki est la ressource centrale de la communauté microformats et fournit des guides de publication des microformats, des références, des spécifications, des drafts, des modèles de publication, de la recherche, du brainstorming et de la résolution de problème.

==Pour démarrer==
{{main-fr|get-started-fr}}
Pour démarrer avec les microformats :

* Premièrement, familiarisez-vous à écrire vos pages et applications avec du <abbr title="HyperText Mark-up Language">HTML</abbr> '<abbr title="Code HTML Intrinsèquement Classe">CHIC</abbr>'.
* Marquez votre information de contact avec [[hcard-fr|hCard]] (([[hcard-authoring-fr|trucs de publication]], [[hcard-examples-fr|exemples]]) et reliez-la à partir de votre site personnel vers vos autres profils personnels avec [[rel-me-fr|rel-me]].
* Vous avez des questions ? Lisez les [[faq-fr|questions souvent posées]], rejoignez le canal [[irc-fr|IRC]] et posez vos questions.
* Vous voulez apprendre avec de vraies personnes ? Regardez les [[events-fr|événements]] microformats.

==Définition==
{{main-fr|what-are-microformats-fr}}
Les microformats sont des petits modèles de HTML pour représenter des choses communément publiées comme des [[hcard-fr|personnes]], des [[hcalendar-fr|événements]] et des [[rel-tag-fr|mots-clé]] dans les pages web.

Les microformats sont le moyen le plus rapide et le plus simple pour fournir une API vers la data et l'information dans votre site web. Regardez [[what-can-you-do-with-microformats-fr|ce que vous pouvez faire avec les microformats]].

== Comment contribuer ? ==
Vous voulez nous rejoindre et contribuer ?
* [[get-started-fr|Commencez]] par ajouter des microformats à votre site web, services et produits.
* [[advocacy-fr|Soutenez]] l'utilisation des microformats.
* Lisez [[how-to-play-fr|Comment Jouer]] avant de modifier ce wiki
* Rejoignez le [[irc-fr|Canal IRC]] et les [[mail-fr|listes de diffusion]] pour apprendre et aider à répondre aux questions posées à propos des microformats. (lisez les [[mailing-lists-fr#Lignes_de_conduite_g.C3.A9n.C3.A9rales|lignes de conduite générales]] avant de poster).
* Écrivez un [[testimonial-fr|témoignage]]
* Écrivez un billet de blog sur : '''[[recently-in-microformats-fr|récemment dans les microformats]]'''
* Faites quelque chose sur la [[to-do|to-do-liste]] et la [[to-do-fr]]
* [[Main_Page-fr#traductions_wiki_microformats_en_d'autres_langues|Traduisez ce wiki des microformats en d'autres langues]] pour rendre les microformats plus accessibles aux lecteurs d'autres langues dans le monde entier.
* Avant de proposer tout nouveau microformat, assurez-vous que votre site web soit [[posh-fr|CHIC]], [[get-started-fr|utilise des microformats existants]], et puis lisez le [[process-fr|processus]].

Ce wiki a aussi un bon nombre d'améliorations pour aider au développement et aux contributions pour les microformats. Avant de commencer à modifier, regardez la [[wiki-2|page d'introduction wiki]] pour les instructions.

== Spécifications ==
La liste actuelle et stable des spécifications des [[microformats-fr|Microformats]] ouvertes et standards :
* {{NewMarker-fr}} '''[[microformats2-fr|microformats2]]''' est stable, a une suite de test, des auteurs et des implémentations interopérables. Commencez par les utiliser sur des pages web publiques et développez plus de parseurs et d'applications.
En outre, utilisez des microformats bien établis :
* [[hcalendar-fr|hCalendar]] - événements
* [[hcard-fr|hCard]] - personnes, organisations, contacts
* [[rel-license-fr|rel-license]] - contenu sous licence
* [[rel-nofollow-fr|rel-nofollow]] - liens dans les contenus tiers sans confiance
* [[rel-tag-fr|rel-tag]] - mots-clés sur les posts et pages par sujet
* [[xfn-fr|XFN]] - relations sociales et liens [[rel-me-fr|rel-me]] parmi les profils pour la même personne
* [[XMDP-fr|XMDP]] - définit un vocabulaire microformat / profil
* [[xoxo-fr|XOXO]] - outlines

== Drafts ==
Les drafts sont des microformats plus récents, qui sont encore en chemin dans le [[process-fr|processus]] pour devenir des spécifications. Les implémenteurs devraient se tenir prêts à des développements et modifications à venir. SVP suivez les pages wiki pour les mises à jour.

* [[adr-fr|adr]] - pour marquer l'information d'adresse
* [[geo-fr|geo]] - latitude & longitude de l'endroit (coordonnées géographiques [http://en.wikipedia.org/wiki/WGS84 WGS84])
* [[hatom-fr|hAtom]] - billets de blog et autres contenus chronodatés
* [[hlisting-fr|hListing]] - annonces classées pour produits et services
* [[hmedia-fr|hMedia]] - info medi concernant les images, video et audio
* [[hnews-fr|hNews]] - articles d'actualité, extension de hAtom
* [[hproduct-fr|hProduct]] - produits
* [[recipe-fr|hRecipe]] - recettes de cuisine et cuisson
* [[hresume-fr|hResume]] - résumés et CVs individuels
* [[hreview-fr|hReview]] - critiques individuelles
* [[hreview-aggregate-fr|hReview-aggregate]] - agrégation de critiques et notes
* [[rel-author-fr|rel-author]] - lien vers la page d'accueil de l'auteur (à partir d'un article)
* [[rel-home-fr|rel-home]] - lien vers la page d'accueil du site
* [[rel-payment-fr| rel-payment]] - lien vers un mécanisme de paiement

''Si vous êtes tenté(e) d'essayer d'écrire un microformat, regardez S.V.P. la page [[process-fr|processus]] en priorité !''

== Discussions Exploratoires ==
{{main-fr|exploratory-discussions-fr}}

Voir [[exploratory-discussions-fr|discussions-exploratoires]] pour les détails de la recherche et l'analyse d'[[examples-fr|exemples]] du vrai monde, de formats existants et un brainstormins sur les nouveaux microformats possibles, selon le [[process-fr|processus]] microformats.

== Modèles de Design ==
{{design_patterns-fr}} 

== Archivé ==
Les anciennes spécifications, drafts et discussions exploratoires qui ont soit manqué (ou perdu) un support de publication, de l'implémentation ou ont cédé la place à des specs. plus récentes (voir aussi [[process#related_issues_questions_regarding_document_stages: process|when does it make sense to demote a microformat spec]]). Celles-ci peuvent être retirées, dépréciées ou réincorporées dans d'autres discussions exploratoires.
* [[haudio-fr|hAudio]]
* [[rel-directory-fr]] - lien vers répertoires web
* [[rel-enclosure-fr]] - lien vers pièces jointes (par ex. fichiers) à télécharger et mettre en cache
* [[robots-exclusion-fr|robots exclusion]]
* [[vote-links-fr|VoteLinks]]
* [[xfolk-fr|xFolk]] - liens tagués

== Exemples ==
* [[examples-in-the-wild-fr|exemples dans la jungle]]
* [[implementations-fr|implémentations]]
* [[zen-garden-fr|zen-garden]]

== Ressources ==
Voir [[resources-fr|ressources]]

== Développement orienté utilisateur ==
*[[user-interface-fr|interface-utilisateur]]
*[[data-portability-fr|portabilité-des-données]]
*[[social-network-portability-fr|portabilité-du-réseau-social]]

== Espaces de collaboration partagés ==
* [[to-do-fr]] et [[to-do]]
* [[templates-fr|modèles]]
* [http://microformats.org/wiki/delete pages marquées pour l'effacement] 
* [[Special:Specialpages|"Special" wiki pages]]
* [[year-in-review]]

== Outils, tests de cas, recherche supplémentaire ==
Le premier endroit pour chercher des exemples, du code et des cas de tests se fait dans les pages de chaque microformat individuel. Il n'y a seulement que quelques [[tools-fr|outils et services]] qui aient besoin de traiter plus d'un microformat. Cette section est destinée pour les auteurs, éditeurs, [[parsers-fr|parseurs]], [[validators-fr|validateurs]], tests de cas et toute autre information pertinente relevant de plusieurs microformats.

== Traductions du microformats wiki ==
<span id="traductions_wiki_microformats_en_d'autres_langues">Vous pouvez lire et éditer des articles de microformats en de nombreuses autres langues :</span>
* langues avec plus de 200 articles
** [[Main_Page-fr|<span lang="fr">Français</span> (French)]] <span lang="fr">{{UpdateMarker-fr}}</span>
* langues avec plus de 10 articles
** [[Main_Page-ja|<span lang="ja">日本語</span> (Japonais)]]
** [[Main_Page-pt-br|<span lang="pt-br">Portugais</span> (Brésilien Portugais)]]
** [[Main_Page-ru|<span lang="ru">Русский</span> (Russe)]]
* langues avec plus de 2 articles
** [[Main_Page-cs|<span lang="cs">Česky</span> (Tchèque)]]
** [[Main_Page-zh|<span lang="zh">汉语</span> (Chinois)]]
** [[Main_Page-de|<span lang="de">Deutsch</span> (Allemand)]]
** [[Main_Page-es|<span lang="es">Español</span> (Espagnol)]]
** [[Main_Page-gl|<span lang="gl">Galego</span> (Galicien)]]
** [[Main_Page-id|<span lang="id">Indonesia</span> (Bahasa Indonesie)]]
** [[Main_Page-pl|<span lang="pl">Polski</span> (Polonais)]]
** [[Main_Page-ro|<span lang="ro">Română</span> (Roumain)]]
* langues justes démarrées
** [[Main_Page-ar|<span lang="ar">العربية</span> (Arabe)]]
** [[Main_Page-fa|<span lang="fa">پارسی</span> (Farsi)]] {{NewMarker}}
** [[Main_Page-ka|<span lang="ka">ქართული</span> (Georgian)]] {{NewMarker}} 

** [[Main_Page-it|<span lang="it">Italiano</span> (Italian)]] {{NewMarker-fr}}
** [[Main_Page-ko|<span lang="ko">한국어</span> (Korean)]] {{NewMarker-fr}}
** [[Main_Page-th|<span lang="th">ภาษาไทย</span> (Thai)]]
** [[Main_Page-tr|<span lang="tr">Türkçe</span> (Turkish)]] {{NewMarker}} 

* ailleurs
**[http://en.wikipedia.org/wiki/Microformat L'article de Wikipedia sur les microformats] a été traduit en d'autres langues.
*** [http://fr.wikipedia.org/wiki/Microformat en français]

Voir aussi les [[other-languages-fr|autres langues]] et [[how-to-start-new-translation-fr|comment-amorcer-une-nouvelle-traduction]].

rel-nofollow-pt-br

2016-12-05T15:47:46Z

TomMorris: Reverted edits by TomMorris (Talk) to last version by Tantek

= rel="nofollow" =
__TOC__

== Especificação 2005-01-10 ==

=== Editores ===
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]
* [http://epeus.blogspot.com/ Kevin Marks], [http://technorati.com Technorati, Inc.]

=== Conceito ===
* [http://www.google.com/googleblog/ Matt Cutts], [http://google.com Google, Inc]
* [http://www.shellen.com/ Jason Shellen], [http://www.blogger.com Blogger]/[http://www.google.com Google]

=== Copyright ===
{{MicroFormatCopyrightStatement2005}}

=== Patentes ===
{{MicroFormatPatentStatement}}

== Sumário ==
RelNoFollow é um [[elemental-microformat-pt-br|microformato elementar]], um dos diversos [[microformats|microformatos]] de padrões aberto. Ao adicionar <code>rel="nofollow"</code> a um hyperlink, uma página indica que aquele destino do hyperlink NÃO DEVE ser permitida qualquer importancia ou ranking por agentes de usuário que oferecem análise de link pelas páginas web (como máquinas de busca). Tipicamente usa casos incluído links criado pela comentários de 3rd party em blogs ou links que o autor gostaria de apontar, porém contra uma aprovação. Para mais informações contra aprovações (ou falta de) semântica, veja VoteLinks.

== Perfil XMDP ==
<pre><nowiki>
<dl class="profile">
<dt id="rel">rel</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel">
Definição HTML4 do atríbuto 'rel'.</a>
Aqui está um valor adicional.</p>
<dl>
<dt id="nofollow">nofollow</dt>
<dd>Indica que o recurso referido não foi necessariamente linkado pelo
autor da página, e tal referencia dita não deve oferecer qualquer recurso
adicional de importancia ou ranking por agentes de usuário.</dd>
</dl>
</dd>
</dl>
</nowiki></pre>

== referencia normativa ==
* [http://gmpg.org/xmdp/ XMDP]
* http://www.google.com/googleblog/2005/01/preventing-comment-spam.html
* http://googleblog.blogspot.com/2005/01/preventing-comment-spam.html

== referencias informativa ==
* VoteLinks pode ser usado pelo autor para estágio explicitamente apoiar ou contrariar, ou neutralidade para destino de um link. Implementadores implementam rel="nofollow" e VoteLinks não deve permitir paralelamente dar importância ou ranking para links com <code>rev="vote-abstain"</code> ou <code>rev="vote-against"</code>.
* Contribuído de http://developers.technorati.com/wiki/RelNoFollow

== assuntos aberto ==
Há assuntos aberto que tem sido levantados sobre rel="nofollow" que foi levantado em vários fórums, em particular, em público [http://lists.w3.org/Archives/Public/www-html W3C www-html mailing list]. Eles foram agrupados para quatro areas.

* '''Definition'''. nofollow indica um ambiente em vez de um relacionamento do qual o ambiente deve ser inferido como apropriado por useragent. Valores rel deve ser nome que indica o recurso referido é uma relação da origem.

* '''Name'''. nofollow é um nome ruim.
** overloading. não significa o mesmo que padrões de exclusão robots (robots.txt, meta robots) nofollow.
** does not mean what it says. não significa o que isso diz "não siga esse link", em vez de " não adicione importancia a esse link". [http://www.w3.org/mid/opsk3cccj9lo81gp@quark Asbjørn Ulsberg]
** not a noun. veja acima.
** alternativas sugerida:
*** noendorse - [http://lists.w3.org/Archives/Public/www-html/2005Jan/0046.html Micah Dubinko]
*** none
*** noweight
*** unendorsed - [http://lists.w3.org/Archives/Public/www-html/2005Jan/0057.html Lachlan Hunt]
*** unrelated - [http://lists.w3.org/Archives/Public/www-html/2005Jan/0049.html Jens Meiert]
*** untrusted
*** nonauth - [http://www.mnot.net/blog/2003/12/29/comment_spam_and_google Mark Baker]
*** norank - [http://www.digitalburg.com/ Ben Pierce]
* '''Efficacy'''. nofollow will not affect spamming behavior.
* '''Collateral Damage'''. If tools automatically add nofollow to all 3rd party links, then many legitimate non-spam links will be ignored or given reduced weight, and thus the destination of such links will be unfortunate casualties.

=== listas adicional de assuntos ===
Listas adicional de assuntos levantados contra rel="nofollow" pode ser encontrado nos sites seguido:
* http://www.nonofollow.net/

adr-fr

2016-12-05T15:46:31Z

TomMorris: Reverted edits by TomMorris (Talk) to last version by ChristopheDucamp

<entry-title> adr </entry-title>
{{DraftSpecification-fr}}

'''adr''' (nom de code pour travailler, prononcez "adeure" ; FAQ : [[hcard-faq-fr#Devrais-je_utiliser_ADDRESS_pour_les_hCards|pourquoi "adr"]] ?) est un format simple pour baliser l'information adresse, approprié pour l'embarquement dans le HTML, XHTML, Atom, RSS et le XML arbitraire. '''adr''' est une représentation 1:1 de la propriété ''adr'' dans le standard vCard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) en HTML, l'un des nombreux standards ouverts [[microformats-fr|microformats]]. C'est aussi une propriété de [[hcard-fr|hCard]].

== Spécification Brouillon ==
<div class="vcard">
; <span class="role">Editeur</span>/<span class="role">Auteur</span>
: <span class="fn">[[User:Tantek|Tantek Çelik]]</span> (<span class="url">http://tantek.com/</span>, et précédemment chez [http://technorati.com Technorati, Inc.])

;<span class="role">Traduction</span>
: <span class="fn">[[User:ChristopheDucamp|Christophe Ducamp]]</span>

</div>

=== Copyright ===
Selon la sortie dans le domaine public sur [[User:Tantek|ma page utilisateur]], cette spécification est publiée dans le domaine public.

{{MicroFormatPublicDomainContributionStatement-fr}}

=== Brevets ===
{{MicroFormatPatentStatement-fr}}

=== Inspiration et Remerciements ===
Merci à tous ceux qui ont participé dans le [[geo-bof-2005-06-30|Geo Microformat BOF at O'Reilly's Where 2.0 conference]], et tout particulièrement [http://radar.oreilly.com/nat/ Nat Torkington] et Vee McMillen de [http://oreilly.com O'Reilly] pour [http://conferences.oreillynet.com/cs/where2005/view/e_sess/7476 organiser et héberger le BOF].

== Introduction et Historique ==
Le standard vCard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), a été largement implémenté de façon interopérable (par ex. l'application carnet d'adresses d'Apple). Le microformat [[hcard-fr|hCard]] a de manière similaire reçu une adoption significative de la part de nombreux sites publiant le format des proxies hCards aux vCards, jusqu'aux parseurs javascript côté client.

A la [http://conferences.oreillynet.com/where/ conférence Where 2.0] en juin 2005, il y a eu une reconnaissance largement acceptée que la communauté avait besoin d'un moyen pour publier simplement et facilement sur le web une information d'adresse qui soit visible, extractible, compte tenu du fait que souvent les blogueurs et les nombreux autres sites publient des informations d'adresses. Le [[geo-bof-2005-06-30|geo microformat BOF]] a discuté tout particulièrement de ce sujet et conclu avec une décision consensuelle de simplement essayer d'utiliser ''adr'' venant de vCard/hCard.

Cette spécification présente le microformat '''adr''', qui est une représentation 1:1 de la propriété mentionnée ci-dessus ''adr'' extraite du standard vCard en réutilisant simplement la propriété ''adr'' et les sous-propriétés telles quelles extraites du microfomat [[hcard-fr|hCard]].

Les auteurs peuvent à la fois embarquer directement des adresses '''adr''' dans leurs pages web et fils, tout comme baliser des adresses existantes dans le contexte du reste de l'information dans leurs pages web et fils.

Si l'auteur connaît et publie le '''name''' de l'endroit en plus de son adresse, alors l'auteur DOIT utiliser [[hcard-fr|hCard]] au lieu de simplement '''adr''' pour publier le nom et l'adresse du lieu.

== Principes de Design XHTML Sémantique ==
{{semantic-xhtml-design-principles-fr}}

== Format ==
=== Propriétés Singulières ===
Voir [[hcard-fr#Propri.C3.A9t.C3.A9s_Singuli.C3.A8res_vs._Plurielles|hCard : Propriétés Singulières vs Plurielles]] pour la liste des propriétés "adr" (sous-propriétés dans la hCard) qui sont au singulier. Prenez note de l'analyse en cours : [[adr-singular-properties-fr]].

=== Lisible Humain vs Machine ===

Si un élément <code><abbr></code> est utilisé pour une propriété, alors l'attribut <code>title</code> de l'élément <code><abbr></code> est la valeur de la propriété, au lieu des contenus de l'élément, ce qui fournit à la place une version humainement présentable de la valeur.

De la même façon, si un élément <code><img></code> est utilisé pour une ou plusieurs propriétés, il doit être traité comme suit :
# Pour la propriété <code>PHOTO</code> et toute autre propriété qui prend un <abbr title="Uniform Resource Locator">URL</abbr> comme sa valeur, l'attribut <code>src</code> fournit la valeur de la propriété.
# Pour d'autres propriétés, l'attribut <code>alt</code> de <code><img></code> est la valeur de la propriété.

=== Extraction de Valeur ===
Parfois, seule la part d'un élément qui est l'équivalent pour une propriété devrait être utilisée pour la valeur de la propriété. A cette intention, le nom de classe <code>value</code> est utilisé pour extraire la partie de l'élément qui est la valeur de la propriété. Voir [[hcard-fr|hCard]] pour les détails à ce sujet.

=== Nom Classe Racine ===
Le nom de classe racine pour une adresse '''adr''' est <code>adr</code>.

=== Liste Propriétés ===
Ceci est la liste des propriétés dans '''adr''', extraite de [[hcard-fr|hCard]] :

* <code>post-office-box</code> (boîte postale)
* <code>extended-address</code> (suite adresse)
* <code>street-address</code> (adresse-rue)
* <code>locality</code> (localité)
* <code>region</code> (région)
* <code>postal-code</code> (code postal)
* <code>country-name</code> (nom du pays)

La sous-propriété <code>type</code> est omise parce que sans le contexte d'un type d'adresse pour ''whom'', cela ne fait pas beaucoup plus de sens.

=== Profil XMDP ===
Voir le [[hcard-profile-fr|profil hCard]] pour le profil [http://gmpg.org/xmdp XMDP] de hCard qui contient la liste complète au-dessus des propriétés, avec des références vers leurs définitions RFC 2426.

=== Détails Parsage ===
Voir le [[hcard-parsing-fr|parsage hCard]], avec la seule différence étant que "adr" est le nom de classe racine, plutôt que "vcard".

== Exemples ==
Cette section est informative.

=== Echantillon adr ===

Voilà un échantillon <code>adr</code> :

<source lang=html4strict>
<div class="adr">
<div class="street-address">50 rue Saint Denis</div>
<div class="extended-address">Suite 207</div>
<span class="postal-code">75001</span> <span class="locality">Paris</span>
<div class="region">Ile de France</div>
<div class="country-name">France</div>
</div>
</source>

qui pourrait être affichée comme :

<div class="adr"><div class="street-address">50 rue Saint Denis</div><div class="extended-address">Suite 207</div><span class="postal-code">75001</span> <span class="locality">Paris</span><div class="region">Ile de France</div><div class="country-name">France</div></div>

Remarquez que c'est un microformat <code>adr</code> vivant, qui sera trouvé sur cette page par les parseurs.

=== Plus d'exemples ===
Voir [[hcard-examples-fr#3.2.1_D.C3.A9finition_Type_ADR|exemples ADR hCard]] pour plus d'exemples.

Voir [http://microformats.org/wiki/adr-examples-fr exemples adr] pour des usages supplémentaires de ADR.

== Exemples dans la jungle ==
Cette section est '''informative'''.

Les sites suivants ont publié des adrs, en dehors de leur contexte normal pour les hCards, et sont de ce fait un endroit génial pour commencer à regarder des exemples "dans la jungle" afin d'essayer de parser, indexer, organiser, etc, en plus des exemples de [[hcard-fr|hCard]] dans la jungle. Si vous trouvez des adrs en dehors de hCards n'importe où, sentez-vous libre de les ajouter en haut de cette liste. Une fois que la liste aura trop grossi, nous produirons une page wiki séparée.
* [http://iprefer.com/ I Prefer Guest Benefit Program] utilise adr sur les pages de résultats de recherche pour l'information city/state/country information, exemple : [http://iprefer.com/luxury-hotel/Bangalore/ Search page for Bangalore]
* [http://preferredhotels.com/ Preferred Hotels and Resorts] utilise adr sur les pages de résultats de recherche pour l'information city/state/country information, exemple : [http://preferredhotels.com/luxury-hotel/London/ Search page for London]
* [http://sterlinghotels.com Sterling Hotels] utilise adr sur les pages de résultats de recherche pour l'information city/state/country information, exemple : [http://sterlinghotels.com/smart-hotel/Barcelona/ Search page for Barcelona]
* [http://www.growsonyou.com/visit Grows on You] uses the microformat to mark up the addresses of open gardens.
* [http://www.stems-florist.co.uk/ Stems Florist] uses the microformat on the front page to markup up the two store addresses
* [http://themechanism.com/locations/ theMechanism] uses the adr microformat to mark up the locations of
their offices.
* [http://www.mister-map.com/ Mister-Map.com] uses the adr microformat to mark up the streets, zip-codes, regions and country names.

(Voir aussi [[hcard-examples-in-wild-fr|hcard-exemples-dans-la-jungle]])

== Implémentations ==
Cette section est '''informative'''.

Les implémentations suivantes ont été développées et soit génèrent ou parsent des adrs en dehors du contexte des hCards. Si vous avez une implémentation adr, sentez-vous libre de l'ajouter en haut de la liste. Une fois que la liste sera devenue trop grosse, nous ferons une page wiki séparée.

* [http://georss.org/geopress GeoPress] est un plugin [http://wordpress.org WordPress] qui supporte l'embarquement des adrs, geo, maps (commutable dynamiquement entre le Cartes Google-Yahoo-Microsoft Maps), et les fils [http://georss.org GeoRSS].

* [http://code.highearthorbit.com/greaseroute/index.php GreaseRoute] est un script utilisateur GreaseMonkey (aussi disponibles comme une simple extension Firefox) qui ajoutera des icônes pour afficher l'endroit, ou la route vers une [[adr-fr|adr]] en utilisant une carte MapQuest. La route est affichée à partir du lieu de départ fondé sur l'Adresse-IP du spectateur déterminée par le service de géolocalisation [http://hostip.info HostIP].

* [http://code.highearthorbit.com/greaseroute/index.php GreaseRouteEmbed] est un autre script utilisateur GreaseMonkey qui embarquera une image de la route dans la page web quand l'utilisateur cliquera sur le lien "route".

* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] est un plugin pour [http://textpattern.com/ Textpattern] qui supporte l'embarquement des adrs et d'autres microformats dans les gabarits et billets de blog. Ecrit par [http://placenamehere.com/ Chris Casciano].

* Le [http://tantek.com/microformats/hcard-creator.html hCard creator], même s'il crée des hCards complètes, peut aussi être utilisé simplement pour créer des adrs en ne remplissant que la portion d'adresse et en copiant et collant simplement l'élément <div class="adr"> et ses contenus.

== Références ==
=== Références Normatives ===
* [[hcard-fr|hCard]]

=== Références Informatives ===
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426] ([http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426])
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]

=== Travaux Similaires ===
* [[geo-fr|geo]]
* [[hcalendar-fr|hCalendar]]
* [[XOXO-fr|XOXO]]

== Chantier en cours ==
Cette spécification est un travail en cours. Au fur et à mesure que des aspects additionnels seront discutés, compris et écrits, ils seront ajoutés.

== Discussions ==

* Voir [http://www.technorati.com/cosmos/referer.html les blogs qui discutent de cette page].

=== Q&R ===
* Si vous avez quelque question à propos de hCard, regardez d'abord les [[hcard-faq-fr|FAQ hCard]] et si vous ne trouvez pas de réponses, ajoutez vos questions ! (Les chances sont celles que toute question '''adr''' s'appliquera tout aussi bien à [[hcard-fr|hCard]]).
* Voir aussi [http://microformats.org/discuss/ pour d'autres méthodes de feedback].

=== Problématiques ===
* SVP, ajoutez toutes les problématiques avec la spécification sur le document séparé [[hcard-issues-fr|problématiques hCard]]. Ditto.

== Pages en rapport ==
* {{adr-fr}}

[[Category:Draft_Specifications]]
[[Category:hCard]]
[[Category:adr]]

adr-fr

2016-12-05T15:41:16Z

TomMorris: langcat: fr

hcalendar-fr

2016-12-05T15:40:44Z

TomMorris: langcat: fr

hcard-fr

2016-12-05T15:40:24Z

TomMorris: langcat: fr

Main Page-fr

2016-12-05T15:39:25Z

TomMorris: langcat: fr

rel-nofollow-pt-br

2016-12-05T15:38:10Z

TomMorris: langcat: pt-br

payment-method-examples

2016-08-04T12:24:35Z

TomMorris: adding some more

This page exists to document published examples of listing payment methods on websites.

* [https://tfl.gov.uk/fares-and-payments/contactless/what-is-contactless?intcmp=8610 TfL.gov.uk: What is a contactless payment card?]
*: "If your card was issued in the UK on Visa, MasterCard, Maestro or American Express and displays the contactless payment symbol (as shown), you should be able to use it to travel on bus, Tube, tram, DLR, London Overground, TfL Rail and most National Rail services in London."
* [http://help.marksandspencer.com/support/payments-and-offers/options-online Marks and Spencer: How do I pay for my order online?], [http://help.marksandspencer.com/support/payments-and-offers/payment-methods-accepted What payment methods are accepted?]
* [http://www.eurostar.com/uk-en/contact-us/frequently-asked-questions/payment/how-can-i-pay-my-eurostar-ticket Eurostar.com: How can I pay for my Eurostar ticket?]
*: "Mastercard, Visa, American Express, Maestro (GBP only), Switch (GBP only), Visa Electron(GBP only) and Delta (GBP only) cards."
* [http://www.airfrance.us/US/en/local/resainfovol/achat/moyens-de-paiement.htm Airfrance.us: Which payment methods are accepted on the Air France website?]
*: "We accept American Express, Diners Club, Discover, Mastercard, Visa, and UATP/AirPlus. Electronic debit cards (“e-cartes bleues”) are not accepted."
* Foursquare
*: example - [https://foursquare.com/v/hawksmoor/4e9d32995503b4a7c128d043 Hawksmoor, London] - "Credit Cards: Yes (incl. American Express & MasterCard)"
* [http://www.haringey.gov.uk/contact/payments/make-online-payment/help-online-payments Haringey Council, London]: "Maestro, Mastercard Debit, Mastercard Credit, Visa Credit, Visa Debit (Delta), Visa Electron. Note we do not accept American Express cards."
* [http://www.nottinghamshire.gov.uk/business-employment-and-benefits/doing-business-with-us/pay-an-invoice/pay-invoice-online Nottinghamshire County Council]: "Visa, Mastercard, Solo, Visa Delta, Visa Electron, Maestro. We cannot accept payment by: American Express, Diners Club."

icalendar-implementations

2016-04-19T18:54:12Z

TomMorris: /* contributors */ can't even remember my own username

<h1> iCalendar implementations </h1>
{{TOC-right}}
This is a list of calendar programs, applications and services that support the iCalendar {{RFC2445}} standard.

In addition, please note any quirks or bugs with implementations' handling of iCalendar - we've already discovered some in the development of [[hcalendar|hCalendar]] and proxies like X2V.

== libraries ==

=== libical ===
Open source C-based implementation of iCalendar.

* [https://github.com/libical/libical Github]

== Python iCalendar ==
Python implementation of iCalendar.

* [https://pypi.python.org/pypi/icalendar/ PyPI]

== services ==
=== Google Calendar ===
http://calendar.google.com/
* supports subscribing to "webcal:" and "http:" URLs to iCalendar

== products ==
=== Apple Calendar.app ===
Apple Calendar.app, formerly known as iCal.
* platform: OSX
* handles "webcal:" URLs and supports subscribing to events.

==== Apple iCal 2.0.5 ====
Apple iCal.app 2.0.5 build 1069 (AppleiCal205)

===== iCal 2.0.5 notes =====
* '''Requires dates and date-times without separators.''' Apple iCal 2.0.5 (and probably other versions) appears to require dates without "-" and times without ":" which appears to be consistent with the iCalendar spec due to:
** iCalendar section 4.3.4 Date - "date-value = date-fullyear date-month date-mday" (no separators)
** iCalendar section 4.3.12 Time - "time = time-hour time-minute time-second [time-utc]" (no separators)

As a result Apple iCal 2.0.5 ignores date and date-time properties (e.g. DTSTART, DTEND, etc.) when date components (year, month, day) are separated by "-" or when time components (hours, minutes, seconds) are separated by ":" (both as allowed by [[ISO8601]] and required by [[RFC3339]]).

However per [[accessibility]] research, dates and times with separators are more readable and accessible, and consequently explicitly allowed by hCalendar.

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date and date-time properties (e.g. DTSTART, DTEND, etc.) with separators, and remove separators when converting to iCalendar.

* '''Requires date-times with seconds explicitly specified.''' Apple iCal 2.0.5 (and probably other versions) appears to require date-times with the seconds explicitly specified, which appears to be consistent with the iCalendar spec:
** iCalendar section 4.3.12 Time - "time = time-hour time-minute time-second [time-utc]" (no separators)

However in practice (see [[hcalendar-examples-in-wild]]) hCalendar date-time properties often omit the seconds because when they are "00" for simplicity and easier/quicker readability.

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date-time properties (e.g. DTSTART, DTEND, etc.) without the seconds explicitly specified, and imply "00" seconds when converting to iCalendar.

* '''Requires floating or UTC date-times.''' Apple iCal 2.0.5 (and probably other versions) appears to require date-times which are either floating (no time zone) or explicitly specified to be UTC and ignores date-times which use timezone offsets, which appears to be consistent with the iCalendar spec:
** iCalendar section 4.3.12 Time - "time = time-hour time-minute time-second [time-utc]" (no separators) and: <blockquote><p>The form of time with UTC offset MUST NOT be used. For example, the following is NOT VALID for a time value:</p><pre>230000-0800 ;Invalid time format</pre></blockquote>

However, in practice (see [[hcalendar-examples-in-wild]]) hCalendar date-time properties often state the timezone offset in order to make the human visible time consistent with the machine readable time for easier verification (minimize DRY divergence probability).

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date-time properties (e.g. DTSTART, DTEND, etc.) with an explicit timezone offset, and convert the specified date-time value to a UTC value when converting to iCalendar.

All hCalendar processor requirements above should be documented thoroughly in [[hcalendar-parsing]].

==== Apple Calendar.app 8.0 (2092.3) ====

Timezone handling: Calendar.app is incompatible with timezone-aware dates produced by the Python iCalendar implementation which puts quotation marks around TZIDs. See [https://gist.github.com/tommorris/0aca78d680804c04bf1e35318893a34a this gist] for details.

=== KOrganizer ===
* platforms: All Linux, *BSD, etc. (Wherever KDE runs)
* supports the "webcal:" protocol, as well as "http:", "ftp:", "fish:", etc.

=== Evolution ===
* platform: Fedora Core 3
* supports "webcal:" protocol

=== Sunbird ===
[http://www.mozilla.org/projects/calendar/sunbird.html Mozilla Sunbird]
* platforms: Windows XP, others?
* supports "webcal:" protocol

=== Microsoft Outlook ===
==== Microsoft Outlook 2007 ====
Microsoft Outlook 2007 (MSOutlook2k7)
* platforms: Windows
* supports importing and subscribing to .ics files, "webcal:" URLs, etc.

==== Microsoft Outlook 2003 ====
Microsoft Outlook 2003 (MSOutlook2k3)
* platforms: Windows
* supports importing .ics files

===== MSOutlook2k3 general comments =====
For importing, MSOutlook2k3 apparently requires VEVENTS to have <code>UID</code>, <code>DTSTAMP</code>, and <code>METHOD</code> properties. ('''citation/platform/date tested info needed'''). If any of the three is not present, returns this message:

<pre>
This error can appear if you have attempted to save a recurring Lunar appointment in iCalendar format.
To avoid this error, set the appointment option to Gregorian instead of Lunar.
</pre>

After some testing, this seems to be the generic message to indicate a problem with event import.

No such restriction is placed on [[rfc-2445#vCalendar|vCalendar 1.0]] events. So, if <code>VERSION:1.0</code> is output instead of <code>VERSION:2.0</code>, the only required field is <code>DTSTART</code>.
Note that <code>VERSION</code> property may be omitted. In this case, value inferred as <code>1.0</code>.

* UID and DTSTAMP is required for Outlook to import. [[User:GeoffWebb|GeoffWebb]] 14:03, 9 Dec 2005 (PST)

===== Potential Security Related Issue w/ Outlook 2003 and Standard Account =====

I've been all over the web tracing the "Lunar" exception.
I believe I'm come across another lunar permutation.
I have an XP box running Outlook 2003 SP3 with Admin privileges, and I have an XP box running Outlook 2003 SP3 (same build number) running under a standard account.
The .ics will try to import correctly under the Admin account (aka, it will prompt you for acceptance, everything working as expected). HOWEVER, the same .ics file will throw the "lunar" exception on the ~standard~ account.

Here is my environment information just in case you're bumping your head on this issue.

Outlook 2003 with SP3 Build Number : 11.8325.8329

.ics file contents (aka, "known to work" file contents under the Admin account)

<pre>BEGIN:VCALENDAR
VERSION:2.0
PRODID:www.testMeiCalendar.net
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20101231T230000
DTEND:20110101T010000
SUMMARY:New Years Eve Reminder
LOCATION:Downtown
DESCRIPTION:Let's get together for New Years Eve
UID:ABCD1234
SEQUENCE:0
DTSTAMP:20101125T112600
END:VEVENT
END:VCALENDAR
</pre>

To be honest, I probably will just abandon trying to use it for this project because of this issue.
But I wanted to report it, so someone doesn't waste a day thinking the issue is the contents of the .ics file.

===== MSOutlook2k3 sample importable iCalendar =====
<pre>
BEGIN:VCALENDAR
VERSION:2.0
METHOD:PUBLISH
BEGIN:VEVENT
UID:0
DTSTAMP:20060601T080000
DTSTART:20060601T080000
END:VEVENT
END:VCALENDAR
</pre>

===== MSOutlook2k3 sample importable vCalendar =====
<pre>
BEGIN:VCALENDAR
BEGIN:VEVENT
DTSTART:20060601T080000
END:VEVENT
END:VCALENDAR
</pre>

=== Fantastical ===

* Platform: Mac and iOS
* supports importing ICS files and subscribing using webcal (tested using Facebok URL)
* Implemented using libical

== notes ==
* the "webcal:" URL protocol scheme is non-standard.

== contributors==
* Tantek Çelik
* [[DimitriGlazkov|Dimitri Glazkov]]
* [[User:TomMorris|Tom Morris]]

== related pages ==
{{hcalendar-related-pages}}

icalendar-implementations

2016-04-19T18:52:50Z

TomMorris: expanding

<h1> iCalendar implementations </h1>
{{TOC-right}}
This is a list of calendar programs, applications and services that support the iCalendar {{RFC2445}} standard.

In addition, please note any quirks or bugs with implementations' handling of iCalendar - we've already discovered some in the development of [[hcalendar|hCalendar]] and proxies like X2V.

== libraries ==

=== libical ===
Open source C-based implementation of iCalendar.

* [https://github.com/libical/libical Github]

== Python iCalendar ==
Python implementation of iCalendar.

* [https://pypi.python.org/pypi/icalendar/ PyPI]

== services ==
=== Google Calendar ===
http://calendar.google.com/
* supports subscribing to "webcal:" and "http:" URLs to iCalendar

== products ==
=== Apple Calendar.app ===
Apple Calendar.app, formerly known as iCal.
* platform: OSX
* handles "webcal:" URLs and supports subscribing to events.

==== Apple iCal 2.0.5 ====
Apple iCal.app 2.0.5 build 1069 (AppleiCal205)

===== iCal 2.0.5 notes =====
* '''Requires dates and date-times without separators.''' Apple iCal 2.0.5 (and probably other versions) appears to require dates without "-" and times without ":" which appears to be consistent with the iCalendar spec due to:
** iCalendar section 4.3.4 Date - "date-value = date-fullyear date-month date-mday" (no separators)
** iCalendar section 4.3.12 Time - "time = time-hour time-minute time-second [time-utc]" (no separators)

As a result Apple iCal 2.0.5 ignores date and date-time properties (e.g. DTSTART, DTEND, etc.) when date components (year, month, day) are separated by "-" or when time components (hours, minutes, seconds) are separated by ":" (both as allowed by [[ISO8601]] and required by [[RFC3339]]).

However per [[accessibility]] research, dates and times with separators are more readable and accessible, and consequently explicitly allowed by hCalendar.

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date and date-time properties (e.g. DTSTART, DTEND, etc.) with separators, and remove separators when converting to iCalendar.

* '''Requires date-times with seconds explicitly specified.''' Apple iCal 2.0.5 (and probably other versions) appears to require date-times with the seconds explicitly specified, which appears to be consistent with the iCalendar spec:
** iCalendar section 4.3.12 Time - "time = time-hour time-minute time-second [time-utc]" (no separators)

However in practice (see [[hcalendar-examples-in-wild]]) hCalendar date-time properties often omit the seconds because when they are "00" for simplicity and easier/quicker readability.

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date-time properties (e.g. DTSTART, DTEND, etc.) without the seconds explicitly specified, and imply "00" seconds when converting to iCalendar.

* '''Requires floating or UTC date-times.''' Apple iCal 2.0.5 (and probably other versions) appears to require date-times which are either floating (no time zone) or explicitly specified to be UTC and ignores date-times which use timezone offsets, which appears to be consistent with the iCalendar spec:
** iCalendar section 4.3.12 Time - "time = time-hour time-minute time-second [time-utc]" (no separators) and: <blockquote><p>The form of time with UTC offset MUST NOT be used. For example, the following is NOT VALID for a time value:</p><pre>230000-0800 ;Invalid time format</pre></blockquote>

However, in practice (see [[hcalendar-examples-in-wild]]) hCalendar date-time properties often state the timezone offset in order to make the human visible time consistent with the machine readable time for easier verification (minimize DRY divergence probability).

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date-time properties (e.g. DTSTART, DTEND, etc.) with an explicit timezone offset, and convert the specified date-time value to a UTC value when converting to iCalendar.

All hCalendar processor requirements above should be documented thoroughly in [[hcalendar-parsing]].

==== Apple Calendar.app 8.0 (2092.3) ====

Timezone handling: Calendar.app is incompatible with timezone-aware dates produced by the Python iCalendar implementation which puts quotation marks around TZIDs. See [https://gist.github.com/tommorris/0aca78d680804c04bf1e35318893a34a this gist] for details.

=== KOrganizer ===
* platforms: All Linux, *BSD, etc. (Wherever KDE runs)
* supports the "webcal:" protocol, as well as "http:", "ftp:", "fish:", etc.

=== Evolution ===
* platform: Fedora Core 3
* supports "webcal:" protocol

=== Sunbird ===
[http://www.mozilla.org/projects/calendar/sunbird.html Mozilla Sunbird]
* platforms: Windows XP, others?
* supports "webcal:" protocol

=== Microsoft Outlook ===
==== Microsoft Outlook 2007 ====
Microsoft Outlook 2007 (MSOutlook2k7)
* platforms: Windows
* supports importing and subscribing to .ics files, "webcal:" URLs, etc.

==== Microsoft Outlook 2003 ====
Microsoft Outlook 2003 (MSOutlook2k3)
* platforms: Windows
* supports importing .ics files

===== MSOutlook2k3 general comments =====
For importing, MSOutlook2k3 apparently requires VEVENTS to have <code>UID</code>, <code>DTSTAMP</code>, and <code>METHOD</code> properties. ('''citation/platform/date tested info needed'''). If any of the three is not present, returns this message:

<pre>
This error can appear if you have attempted to save a recurring Lunar appointment in iCalendar format.
To avoid this error, set the appointment option to Gregorian instead of Lunar.
</pre>

After some testing, this seems to be the generic message to indicate a problem with event import.

No such restriction is placed on [[rfc-2445#vCalendar|vCalendar 1.0]] events. So, if <code>VERSION:1.0</code> is output instead of <code>VERSION:2.0</code>, the only required field is <code>DTSTART</code>.
Note that <code>VERSION</code> property may be omitted. In this case, value inferred as <code>1.0</code>.

* UID and DTSTAMP is required for Outlook to import. [[User:GeoffWebb|GeoffWebb]] 14:03, 9 Dec 2005 (PST)

===== Potential Security Related Issue w/ Outlook 2003 and Standard Account =====

I've been all over the web tracing the "Lunar" exception.
I believe I'm come across another lunar permutation.
I have an XP box running Outlook 2003 SP3 with Admin privileges, and I have an XP box running Outlook 2003 SP3 (same build number) running under a standard account.
The .ics will try to import correctly under the Admin account (aka, it will prompt you for acceptance, everything working as expected). HOWEVER, the same .ics file will throw the "lunar" exception on the ~standard~ account.

Here is my environment information just in case you're bumping your head on this issue.

Outlook 2003 with SP3 Build Number : 11.8325.8329

.ics file contents (aka, "known to work" file contents under the Admin account)

<pre>BEGIN:VCALENDAR
VERSION:2.0
PRODID:www.testMeiCalendar.net
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20101231T230000
DTEND:20110101T010000
SUMMARY:New Years Eve Reminder
LOCATION:Downtown
DESCRIPTION:Let's get together for New Years Eve
UID:ABCD1234
SEQUENCE:0
DTSTAMP:20101125T112600
END:VEVENT
END:VCALENDAR
</pre>

To be honest, I probably will just abandon trying to use it for this project because of this issue.
But I wanted to report it, so someone doesn't waste a day thinking the issue is the contents of the .ics file.

===== MSOutlook2k3 sample importable iCalendar =====
<pre>
BEGIN:VCALENDAR
VERSION:2.0
METHOD:PUBLISH
BEGIN:VEVENT
UID:0
DTSTAMP:20060601T080000
DTSTART:20060601T080000
END:VEVENT
END:VCALENDAR
</pre>

===== MSOutlook2k3 sample importable vCalendar =====
<pre>
BEGIN:VCALENDAR
BEGIN:VEVENT
DTSTART:20060601T080000
END:VEVENT
END:VCALENDAR
</pre>

=== Fantastical ===

* Platform: Mac and iOS
* supports importing ICS files and subscribing using webcal (tested using Facebok URL)
* Implemented using libical

== notes ==
* the "webcal:" URL protocol scheme is non-standard.

== contributors==
* Tantek Çelik
* [[DimitriGlazkov|Dimitri Glazkov]]
* [[User:Tom Morris|Tom Morris]]

== related pages ==
{{hcalendar-related-pages}}

hreflang

2016-04-03T14:45:03Z

TomMorris: /* Places that should use hreflang */ Wordpress

'''hreflang''' is an attribute in HTML to mark that the target of links are in a particular language. When combined with [[rel-alternate]], it can be used to mark that another page has the same (or broadly similar) content but translated into another language.

== Places using hreflang properly ==
* Wikipedia
** e.g English article on [https://en.wikipedia.org/wiki/New_York_City New York City] links to foreign language versions. Each has an appropriate hreflang.

== Places that should use hreflang ==

* GOV.UK, the UK Government's official website, has content about the relationship of Britain with other countries. That content is often available in those languages. There's no hreflang links between content in different languages.
** e.g. [https://www.gov.uk/government/world/france France] (in English) vs. [https://www.gov.uk/government/world/france.fr France] (en Français).
** e.g. [https://www.gov.uk/government/world/brazil Brazil] (in English) vs. [https://www.gov.uk/government/world/brazil.pt Brasil] (em Português).
* Wordpress.org doesn't use hreflangs for links to localised content

hreflang

2016-04-03T14:41:28Z

TomMorris: /* Places using hreflang properly */ Wikipedia

hreflang

2016-04-03T14:39:38Z

TomMorris: creating

'''hreflang''' is an attribute in HTML to mark that the target of links are in a particular language. When combined with [[rel-alternate]], it can be used to mark that another page has the same (or broadly similar) content but translated into another language.

== Places using hreflang properly ==

== Places that should use hreflang ==

* GOV.UK, the UK Government's official website, has content about the relationship of Britain with other countries. That content is often available in those languages. There's no hreflang links between content in different languages.
** e.g. [https://www.gov.uk/government/world/france France] (in English) vs. [https://www.gov.uk/government/world/france.fr France] (en Français).
** e.g. [https://www.gov.uk/government/world/brazil Brazil] (in English) vs. [https://www.gov.uk/government/world/brazil.pt Brasil] (em Português).

rel-alternate

2016-04-03T14:34:58Z

TomMorris: linking to hreflang

{{stub}}

== Special Combinations ==
While <code>rel="alternate"</code> does by itself mean that the destination is some alternate representation or version of the current page, it combines in special ways with other <code>rel</code> values and other attributes to provide different more specific meanings, in particular:

=== With <code>rel stylesheet</code> ===
==== Alternate stylesheets ====
<code>rel="alternate stylesheet"</code> is [http://www.w3.org/TR/html4/present/styles.html#h-14.3.1 how you provide an alternate stylesheet] for the document. Note that the stylesheet is ''not'' an alternate representation of the current page.

=== With <code>hreflang</code> ===
==== Alternate language versions ====
When used in combination with the <code>hreflang</code> attribute (with a value other than that of the document itself), <code>rel="alternate"</code> means a link to a version of the current document, but in the language indicated by the <code>hreflang</code> attribute.

Example from http://gmpg.org/xfn/creator :
<source lang=html4strict>
<link href="creator-fr" rel="alternate" hreflang="fr" title="Créateur XFN 1.1" />
</source>

See also: [http://support.google.com/webmasters/bin/answer.py?hl=en&answer=189077 Google Webmaster Tools Help: rel="alternate" hreflang="x"] and [[hreflang]]

=== With <code>media</code> ===
==== Alternate devices and media ====
When used in combination with the <code>media</code> attribute, <code>rel="alternate"</code> means a link to a version of the current document, especially for the specified device or medium indicated by the <code>media</code> attribute.

For example, this is one possible way of linking to a site's mobile version:
<source lang="html4strict">
<a href="http://m.twitter.com" rel="alternate" media="handheld">Twitter mobile site</a>
</source>

=== With <code>type</code> ===
==== Page Feed ====

When used in combination with the <code>type</code> attribute (with a value other than that of the document itself; e.g. other than <code>"text/html"</code>), <code>rel="alternate"</code> means a link to a representation of the contents of the current document in a different format, as designated by the <code>type</code> attribute.

Examples:

<source lang="html4strict">
<link rel="alternate" type="application/rss+xml" href=".rss"
title="RSS feed for this page"/>
<link rel="alternate" type="application/atom+xml" href=".atom"
title="Atom feed for this page"/>
<link rel="alternate" type="application/activitystream+json" href=".as"
title="Activity Streams JSON feed for this page"/>
</source>

=== With <code>type</code> and <code>rel home</code> ===
==== Site Feed ====
{{main|rel-home#use_with_rel-alternate}}

'''Proposed:'''
When used in combination with the <code>type</code> attribute (with a value other than that of the document itself, e.g. other than <code>"text/html"</code>), <code>rel="alternate home"</code> means a link to a representation of the contents of the ''site'' (the home page for the current page) in a different format, as designated by the <code>type</code> attribute.

Examples:

<source lang="html4strict">
<link rel="alternate home" type="application/rss+xml" href=".rss"
title="RSS feed for this site"/>
<link rel="alternate home" type="application/atom+xml" href=".atom"
title="Atom feed for this site"/>
<link rel="alternate home" type="application/activitystream+json" href=".as"
title="Activity Streams JSON feed for this site"/>
</source>

== See Also ==
* [[existing-rel-values]]
* [[rel-faq]]
* [[rel-home]], in particular [[rel-home#use_with_rel-alternate|rel-home with rel-alternate proposal]]

phone-number

2015-12-11T10:16:46Z

TomMorris: creating page on phone numbers

A '''phone number''' is a series of digits that can be used to place a voice call or send a text message to a landline or mobile phone. This page exists to document efforts to parse, standardise and understand phone numbers.

== microformats ==

Phone numbers can be represented using the tel property in both [[h-card]] and the legacy [[hCard]] formats.

== parsers ==

=== libphonenumber ===

[https://github.com/googlei18n/libphonenumber libphonenumber] is a C++, Java and JavaScript library created by Google that attempts to validate phone numbers.

There are wrappers in a variety of languages:

* [https://github.com/daviddrysdale/python-phonenumbers python-phonenumbers] (Python)
* [https://github.com/sstephenson/global_phone global_phone] (Ruby)
* [https://github.com/giggsey/libphonenumber-for-php libphonenumber-for-php] (PHP)
* [https://github.com/erezak/libphonenumber-csharp libphonenumber-csharp] (C#)
* [https://github.com/iziz/libPhoneNumber-iOS libPhoneNumber-iOS] (Objective-C/iOS)

== lookup services ==

Twilio provide a [https://www.twilio.com/lookup lookup service] to validate phone numbers.

phone numbers

2015-12-11T10:12:05Z

TomMorris: redirect

#REDIRECT [[phone-number]]

phone number

2015-12-11T10:11:52Z

TomMorris: redirecting

#REDIRECT [[phone-number]]

hcard

2015-12-11T10:10:51Z

TomMorris: /* Properties */ redlinking phone number

<entry-title>hCard 1.0</entry-title>
{{latest|h-card}}
<span class="vcard"><span class="fn">[[User:Tantek|Tantek Çelik]]</span> (<span class="role">Editor</span>, <span class="role">Author</span>)</span>, <span class="vcard"><span class="fn">[[User:Brian|Brian Suda]]</span> (<span class="role">Author</span>)</span>
----
<dfn style="font-style:normal;font-weight:bold">hCard</dfn> is a simple, open format for publishing people, companies, organizations on the web, using a 1:1 representation of vCard ([[rfc-2426|RFC2426]]) properties and values in HTML. hCard is one of several open [[microformats|microformat]] standards suitable for embedding data in HTML/HTML5, and Atom/RSS/XHTML or other XML.

Translations: [[hcard-fr|<span lang="fr">Français</span>]] • [[hcard-ja|<span lang="ja">日本語</span>]] • [[hcard-ru|<span lang="ru">Русский</span>]] • [[hcard-th|<span lang="th">ภาษาไทย</span>]] • [[hcard-zh|<span lang="zh">漢語</span>]] • <span style="font-size:.8em">([[how-to-start-new-translation|Add your language]])</span><br/>
[[hcard#Copyright|Copyright]] and [[hcard#Patents|patents]] statements apply. See [[hcard#Inspiration_and_Acknowledgments|acknowledgments]].

== Example ==
hCards are most often used to represent people:
<source lang=html4strict>
<div class="vcard">
<a class="url fn" href="http://tantek.com/">Tantek Çelik</a>
</div>
</source>
and organizations:
<source lang=html4strict>
<div class="vcard">
<a class="url fn org" href="http://microformats.org/">microformats.org</a>
</div>
</source>
<div style="float:right;background:rgb(248, 247, 236); border:2px solid rgb(225, 229, 186); margin-left:2em" class="box">
=== Get started ===
http://microformats.org/wiki/skins/Microformats/images/bullet.gif Create a [http://microformats.org/code/hcard/creator new hCard]<br/>
http://microformats.org/wiki/skins/Microformats/images/bullet.gif Learn [[hcard-authoring|hCard authoring]]
</div>

The class '''<code>vcard</code>''' is a ''[[hcard#Root_Class_Name|root class name]]'' that indicates the presence of an hCard.

The classes '''<code>url</code>''', '''<code>fn</code>''', and '''<code>org</code>''' define ''properties'' of the hCard.

== Properties ==
<div style="white-space:nowrap;float:left">Common hCard properties (inside class <code>'''vcard'''</code>)
* <code>'''fn'''</code> - name, formatted/full. required
* <code>'''n'''</code> - structured name, container for:
** <code>'''honorific-prefix'''</code> - e.g. Ms., Mr., Dr.
** <code>'''given-name'''</code> - given (often first) name
** <code>'''additional-name'''</code> - other/middle name
** <code>'''family-name'''</code> - family (often last) name
** <code>'''honorific-suffix'''</code> - e.g. Ph.D., Esq.
* <code>'''nickname'''</code> - nickname/alias, e.g. [[IRC]] <abbr title="nickname">nick</abbr>
* <code>'''org'''</code> - company/organization
* <code>'''photo'''</code> - photo, icon, avatar
* <code>'''url'''</code> - home page for this contact
* <code>'''email'''</code> - email address
* <code>'''tel'''</code> - [[phone number|telephone number]]
* <code>'''[[adr]]'''</code> - structured address, container for:
** <code>'''street-address'''</code> - street <abbr title="number">#</abbr>+name, <abbr title="apartment">apt</abbr>/<abbr title="suite">ste</abbr>
** <code>'''locality'''</code> - city or village
** <code>'''region'''</code> - state or province
** <code>'''postal-code'''</code> - postal code, e.g. <abbr title="United States">U.S.</abbr> ZIP
** <code>'''country-name'''</code> - country name
* <code>'''bday'''</code> - birthday. [[date-pattern|ISO date]].
* <code>'''category'''</code> - for tagging contacts
* <code>'''note'''</code> - notes about the contact
</div>
<div style="margin-top:-.4em; float:left;"><span style="display:none">Example hCard of common properties:</span>
<ul style="list-style:none"><li><code><div class="'''vcard'''"></code>
<ul style="list-style:none; margin-top:-.02em">
<li><code><span class="'''fn'''">Sally Ride</span></code></li>
<li><code>(<span class="'''n'''"></code><ul style="list-style:none">
<li><code><span class="'''honorific-prefix'''">Dr.</span></code></li>
<li><code><span class="'''given-name'''">Sally</span></code></li>
<li><code><abbr class="'''additional-name'''">K.</abbr></code></li>
<li><code><span class="'''family-name'''">Ride</span></code></li>
<li><code><span class="'''honorific-suffix'''">Ph.D.</span></span>),</code></li></ul></li>
<li><code><span class="'''nickname'''">sallykride</span> (IRC)</code></li>
<li><code><div class="'''org'''">Sally Ride Science</div></code></li>
<li><code><img class="'''photo'''" src="<nowiki>http://example.com/sk.jpg</nowiki>"/> </code></li>
<li><code><a class="'''url'''" href="<nowiki>http://sally.example.com</nowiki>">w</a>,</code></li>
<li><code><a class="'''email'''" href="<nowiki>mailto:sally@example.com</nowiki>">e</a> </code></li>
<li><code><div class="'''tel'''">+1.818.555.1212</div></code></li>
<li><code><div class="'''adr'''"></code><ul style="list-style:none">
<li><code><div class="'''street-address'''">123 Main st.</div></code></li>
<li><code><span class="'''locality'''">Los Angeles</span>, </code></li>
<li><code><abbr class="'''region'''" title="California">CA</abbr>, </code></li>
<li><code><span class="'''postal-code'''">91316</span></code></li>
<li><code><div class="'''country-name'''">U.S.A</div></div></code></li></ul></li>
<li><code><time class="'''bday'''">1951-05-26</time> birthday</code></li>
<li><code><div class="'''category'''">physicist</div></code></li>
<li><code><div class="'''note'''">1st American woman in space.</div></code></li></ul></li>
<li><code></div></code></li></ul>
</div>
<div style="clear:both; padding:1em 0 0.5em 0">See the [[hcard#Property_List|full list of properties]] for the complete list.
</div>
__TOC__

== Status ==
hCard 1.0 is a microformats.org specification. Public discussion on hCard takes place on [[hcard-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-discuss/ microformats-discuss mailing list].

=== Errata and Updates ===
Known errors and issues in this specification are corrected in [[hcard-issues-resolved|resolved]] and [[hcard-issues-closed|closed]] issues. Please check there before reporting [[hcard-issues|issues]].

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

== Background ==
The vCard standard ([[rfc-2426|RFC2426]]), has been broadly interoperably implemented (e.g. Apple's "Address Book" application built into MacOSX).

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

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

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

== Conformance ==
{{rfc-2119-intro}}

== Format ==
=== In General ===
The vCard standard ([[rfc-2426|RFC2426]]) forms the basis of hCard.

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

=== Root Class Name ===
The root class name for an hCard is "vcard". An element with a class name of "vcard" is itself called an ''hCard''.

=== Properties and Sub-properties ===
The properties of an hCard are represented by elements inside the hCard. Elements with class names of the listed properties represent the values of those properties. Some properties have sub-properties, and those are represented by elements inside the elements for properties.

=== Property List ===
hCard properties (sub-properties in parentheses like this)

'''Required:'''
* '''fn'''
* <span id="property-list-n">'''n'''<sup style="font-size:smaller">[[#note1|1]]</sup></span>
** family-name
** given-name
** additional-name
** honorific-prefix
** honorific-suffix
Optional:
* [[adr]]
** post-office-box
** extended-address
** street-address
** locality
** region
** postal-code
** country-name
** type
** value
* agent
* bday
* category
* class
* email (type, value)
* geo
** latitude
** longitude
* key
* label
* logo
* mailer
* nickname
* note
* org (organization-name, organization-unit)
* photo
* rev
* role
* sort-string
* sound
* <span id="property-list-tel">tel<sup style="font-size:smaller">[[#note2|2]]</sup> (type, value)</span>
* title
* <span id="property-list-tz">tz<sup style="font-size:smaller">[[#note3|3]]</sup></span>
* uid
* url

=== Property Notes ===
<span id="note1">[[#property-list-n|1. ^]]</span>: The 'n' property is {{optional}} if any [[hcard#Implied_.22n.22_Optimization|implied 'n' optimization rules]] are in effect.<br />
<span id="note2">[[#property-list-tel|2. ^]]</span>: tel - Authors {{may}} follow the [http://en.wikipedia.org/wiki/E.123 E.123] standard for writing values of telephone numbers. Letter values (e.g. +1-555-FORMATS) {{must}} be converted to numbers. Use an <code>abbr</code> to display letters and provide a numerical value simultaneously, e.g. <code><nowiki><abbr title="+15553676287">+1-555-FORMATS</abbr></nowiki></code>.<br />
<span id="note3">[[#property-list-tz|3. ^]]</span>: tz - timezones are indicated with the timezone offset, e.g. <code>PST (<span class="tz">-08:00</span>)</code>.

=== Singular vs. Plural Properties ===
Singular properties: 'fn', 'n', 'bday', 'tz', 'geo', 'sort-string', 'uid', 'class', 'rev'. For properties which are singular, the first descendant element with that class {{should}} take effect, any others being ignored.

All other properties {{may}} be plural. Each class instance of such properties creates a new instance of that property.

=== Human vs. Machine readable ===
The human visible text contents of an element for a property represents the value of that property, with a few exceptions:

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

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

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

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

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

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

hCard:
<source lang=html4strict>
<span class="tel">
<span class="type">home</span>:
<span class="value">+1.415.555.1212</span>
</span>
</source>

This hCard fragment could be displayed as:

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

You may want to customize/localize the visible punctuation and not want to include it in what machines see. Use multiple class="value" elements which are then concatenated. E.g.

<source lang=html4strict>
<span class="tel">
<span class="type">home</span>:
<span class="value">+1</span>.<span class="value">415</span>.<span class="value">555</span>.<span class="value">1212</span></span>
</span>
</source>

No change in display, but the parsed hCard property value then becomes in vCard:

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



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

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

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

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

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

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

This allows simplification in the typical case of people stating:
* given-name (space) family-name
* family-name (comma) given-name

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

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

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

Though parsers {{must}} follow the implied nickname optimization, publishers {{should}} explicitly indicate the "nickname" even in this case, e.g.:

<source lang=html4strict>
<span class="vcard">
<span class="fn nickname">daveman692</span>
</span>
</source>

The hCard {{may}} have additional explicit "nickname" property values in addition to the implied nickname.

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

=== Tags as Categories ===
Categories in hCard {{may}} be represented by tags with [[rel-tag]]. When a category property is a rel-tag, the tag (as defined by rel-tag) is used for that category.

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

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

hCard:
<source lang=html4strict>
<span class="tel"><span class="type">Home</span> (<span class="type">pref</span>erred):
<span class="value">+1.415.555.1212</span>
</span>
</source>

This could be displayed as:

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

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

<source lang=html4strict>
<span class="tel"><span class="type">Home</span> +1.415.555.1212</span>
</source>

is equivalent to:

<source lang=html4strict>
<span class="tel"><span class="type">Home</span><span class="value"> +1.415.555.1212</span></span>
</source>

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

==== adr tel email types ====
The following lists are ''informative''. See [[rfc-2426|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.

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

=== Profile ===
The hCard <span id="XMDP_Profile">XMDP profile</span> is at http://microformats.org/profile/hcard

Content that uses hCard {{should}} reference this profile, e.g.
<source lang=html4strict>
<link rel="profile" href="http://microformats.org/profile/hcard">
</source>
or
<source lang=html4strict>
This content uses <a rel="profile" href="http://microformats.org/profile/hcard">hCard</a>.
</source>
or
<source lang=html4strict>
<head profile="http://microformats.org/profile/hcard">
</source>
(profile attribute is deprecated in HTML5)
Content may combine the above methods as well.

=== Parsing Details ===

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

== Examples ==

This section is informative.

=== Sample vCard ===

Here is a sample vCard:

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

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

<source lang=html4strict>
<div class="vcard">
<a class="url fn" href="http://tantek.com/">Tantek Çelik</a>
</div>
</source>

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

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

===Live example===

Here is [http://www.commerce.net/ Commercenet]'s contact details, as a live hCard which will be detected, on this page, by microformat parsing tools:

<div class="vcard">
<div class="fn org">'''CommerceNet'''</div>
<div class="url">'''<nowiki>http://www.commerce.net/</nowiki>'''</div>
<div class="adr">'''<span class="type">Work</span>:'''
<div class="street-address">'''169 University Avenue'''</div>
<span class="locality">'''Palo Alto'''</span>, <span class="region">'''CA'''</span>  <span class="postal-code">'''94301'''</span>
<div class="country-name">'''USA'''</div>
</div>
<div class="tel">'''<span class="type">Work</span> +1-650-289-4040'''</div>
<div class="tel">'''<span class="type">Fax</span> +1-650-289-4041'''</div>
<div>'''Email <span class="email"><nowiki>info@commerce.net</nowiki></span>'''</div>
</div>

The mark-up, emboldening omitted for clarity, with the following semantic improvements:
* <code>abbr</code> to expand abbreviations
* hyperlinking the org name with the url

<source lang=html4strict>
<div class="vcard">
<a class="fn org url" href="http://www.commerce.net/">CommerceNet</a>
<div class="adr">
<span class="type">Work</span>:
<div class="street-address">169 University Avenue</div>
<span class="locality">Palo Alto</span>,
<abbr class="region" title="California">CA</abbr>  
<span class="postal-code">94301</span>
<div class="country-name">USA</div>
</div>
<div class="tel">
<span class="type">Work</span> +1-650-289-4040
</div>
<div class="tel">
<span class="type">Fax</span> +1-650-289-4041
</div>
<div>Email:
<span class="email">info@commerce.net</span>
</div>
</div>
</source>

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

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

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

== Implementations ==
This section is '''informative'''. The number of hCard implementations has also expanded beyond the capacity of keeping them inline. They have been moved to a [[hcard-implementations|separate page]].

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

== Articles ==
This section is <strong>informative</strong>. For <span id="Further_Reading">further reading</span> on hCard see [[hcard-articles]].

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

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

== Copyright ==
Per the public domain release on the authors' user pages ([[User:Tantek|Tantek Çelik]], [[User:Brian|Brian Suda]]) this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

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

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

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

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

== Inspiration and Acknowledgments ==
This section is '''informative'''.
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.

== Notes on derivation from vCard ==
This section is ''informative''.

<div id="Semantic_XHTML_Design_Principles">See: [[hcard-design-methodology]].</div>

=== More Semantic Equivalents ===
For some properties there are HTML elements which better match and convey their semantics. The following properties SHOULD be encoded with the following HTML:
* <code>URL</code> in vCard becomes <code><a class="url" href="...">...</a></code> inside the element with <code>class="vcard"</code> in hCard.
* Similarly, <code>EMAIL</code> in vCard becomes <code><nowiki><a class="email" href="mailto:...">...</a></nowiki></code>
* <code>PHOTO</code> in vCard becomes <code><img class="photo" src="..." alt="Photo of ..." /></code> or <code><object class="photo" data="..." type="...">Photo of ...</object></code>
* <code>UID</code> in vCard simply becomes another semantic applied to a specific URL (or EMAIL) for an hCard.

=== Singular and Plural derivations ===
The [[hcard#Singular_vs._Plural_Properties|lists of singular and plural properties]] have been derived by analyzing the semantics of the individual properties in vCard RFC2426 and determining logically that they MUST be singular per their semantics. See [[hcard-singular-properties]] for explanations.

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

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

[[Category:Specifications]]
[[Category:hCard]]

== Translations ==
The English version of this specification is the only normative version. Read the hCard specification in additional <span id="languages">languages</span>:
* [[hcard-fr|<span lang="fr">Français</span>]]
* [[hcard-ja|<span lang="ja">日本語</span>]]
* [[hcard-ru|<span lang="ru">Русский</span>]]
* [[hcard-th|<span lang="th">ภาษาไทย</span>]]
* [[hcard-zh|<span lang="zh">漢語</span>]]
Help [[how-to-start-new-translation|translate hCard into more languages]].

design-patterns-examples

2015-11-05T11:42:13Z

TomMorris: creating

Many organisations publish design patterns and guides online. This page is to collect notable and interesting examples thereof.

== pattern libraries ==

* [https://www.gov.uk/service-manual GOV.UK Service Manual]
* [https://developer.yahoo.com/ypatterns/ Yahoo Design Patterns Library]

== meta ==
* [http://principles.adactio.com/ Design Principles], adactio.com

design-patterns

2015-11-05T09:07:34Z

TomMorris: redlinking design-patterns-examples

= Design Patterns =

{{design_patterns}}

== See Also ==
* [[anti-design-patterns]]
* [[design-patterns-examples]]

gender-examples

2015-10-23T13:54:58Z

TomMorris: adding Eurotunnel Advance Passenger Information gender selections

<entry-title>gender examples</entry-title>

This page documents how people currently publish [[gender]] information on the web (sometimes implicitly - so not easily machine parsable - such as names (Andrew, Andrea), titles (Mr, Mrs, Miss), relationships (husband, brother), pronouns (he, she), etc.)), and what gender terms are supported by current web user interfaces. This research will hopefully be useful to the [[genealogy]] microformat effort, as well as efforts to [[vcard-suggestions|extend vCard]], and therefore [[hcard|hCard]].

== examples ==
These examples are based on two primary sources of real world web site usage (e.g. on social network sites)

* user interfaces for editing (and displaying) [[user profile]] information
* user interfaces for doing faceted (field-based) search based on value(s) of a gender (or sex) field.

== sites and services ==

Social network sites typically publish the gender of the individual.

Sites and services that allow users to enter and publish their gender. Please add to this list.

In alphabetical order:
* [https://bagcheck.com/blog/01-the-gender-question Bagcheck] chose to ask which pronoun you want to use:
** Preferred Possessive Pronoun: ( )Her ( )His ( )Their
* [http://crush3r.com/ Crusher]'s [http://crush3r.com/account Edit My Account](requires login) page combines gender and person vs organization distinction in an interesting type picker among girl, boy, band, or other with a field.
** Type: ( ) Girl ( ) Boy ( ) Band ( ) Other: [______]
* Canada Council for the Arts (need citation to specific sign-up form URL) - [https://twitter.com/heathr/status/189492984188903424 according to Heather Gold]:
** Female, Male, Transgender, Other (please specify), No answer, Please specify [______]
** [http://twitter.com/#!/heathr/status/189492984188903424/photo/1/large http://p.twimg.com/AqE23XpCIAArFWA.png]
* [http://digg.com/ Digg]'s [http://digg.com/settings/about About Me settings page](requires login) has a Gender popup that appears to be inspired by Pownce's list:
** Guy, Girl, Dude, Lady, Fellow, Bird, Chap, grrrl, Gentleman, Damsel, Male, Female, Transgender, None of the Above
* [https://www.flirtbox.co.uk/hotornot.php?gender=f flirtbox]: "Women" and "girls"
* [http://www.eharmony.co.uk/ eHarmony]: "Woman" or "Man"
* [http://facebook.com facebook.com]: changed from "Male/Female" to Male/Female/Custom" on 2014-02-13
** custom must be from one of 56 choices, despite being a free-entry text box -
** (Agender, Androgyne, Androgynous, Bigender, Cis, Cisgender, Cis Female, Cis Male, Cis Man, Cis Woman, Cisgender Female, Cisgender Male, Cisgender Man, Cisgender Woman, Female to Male, FTM, Gender Fluid, Gender Nonconforming, Gender Questioning, Gender Variant, Genderqueer, Intersex, Male to Female, MTF, Neither, Neutrois, Non-binary, Other, Pangender, Trans, Trans*, Trans Female, Trans* Female, Trans Male, Trans* Male, Trans Man, Trans* Man, Trans Person, Trans* Person, Trans Woman, Trans* Woman, Transfeminine, Transgender, Transgender Female, Transgender Male, Transgender Man, Transgender Person, Transgender Woman, Transmasculine, Transsexual, Transsexual Female, Transsexual Male, Transsexual Man, Transsexual Person, Transsexual Woman, Two-Spirit)
** list from [http://www.slate.com/blogs/future_tense/2014/02/13/facebook_custom_gender_options_here_are_all_56_custom_options.html Will Oremus at Slate]
* [http://www.gay.com/ gay.com]: "Male", "Female", "MTF" and "FTM".
* http://www.adam4adam.com/: "Male", "Female"
* [https://plus.google.com Google+]:
** before 2014-12-10: Male, Female, Other
** after 2014-12-10: Male, Female, Decline to State, Custom - if Custom selected, a freeform text field is enabled to put in your gender. [https://plus.google.com/app/basic/stream/z12iz5ajslvxe3mup23nud451xfqcfj4l04 Post by Rachael Bennett]
* [http://www.livejournal.com/ LiveJournal]'s [http://www.livejournal.com/manage/profile/ Edit Profile](requires login) page provides a popup menu for gender with the values in order:
** (Unspecified), Male, Female
* [http://ma.gnolia.com Ma.gnolia]'s [http://ma.gnolia.com/account/profile Edit Your Profile on Ma.gnolia](requires login) page provides a popup menu for gender with the values in order:
** Female, Male, Other
* MediaWiki.org
** Radio button choice on Preferences: "(I prefer not to say)", "She edits wiki pages", "He edits wiki pages"
** [https://phabricator.wikimedia.org/T61643 Phabricator thread on non-binary gender preferences]
*[http://metatalk.metafilter.com/20050/Gender-Go-nuts-Somebody-did#838160 Cortex histogrammed] [http://metafilter.com metafilter's] 10-year-old free-form gender field- [http://stuff.metafilter.com/genders/genderfield.txt data dump]
** The first entry is blank/null fields; the difference between that and "total records" is the number of people who have put anything at all in the field: 9,325 mefites have as of a few minutes ago put something in that field. Reckoning from the previous note, that means that something like 17-18% of users have actually elected to put something in that field at some point in their membership here.
** Of the folks who have something in that field, just over 60% use one of the top four options: "male", "female", "m", or "f".
** Of the top dozen or so unambiguous labels provided, male-identifying terms (male, m, dude, xy, boy, guy, man, mail) account for about 49% of total labels used; female-identifying terms (female, f, lady, girl, xx, femme, chick) account for about 18%.
*[http://myspace.com/ MySpace.com] used to only allow male or female. There was a protest on MySpace by some genderqueer users who would put the word "genderqueer" into irrelevant metadata fields as a form of symbolic protest (source: tommorris' memory, [http://www.reddit.com/r/genderqueer/comments/1xtkq5/facebook_recognizes_nonbinary_genders_now/cfestqf reddit comment from tommorris])
*[http://www.okcupid.com/ OKCupid] - "I'm male" and "I'm female"
** This has led to a change.org petition: [https://www.change.org/petitions/ensure-that-all-okcupid-users-are-able-to-comfortably-identify-their-gender-and-sexual-orientation Ensure that all OkCupid users are able to comfortably identify their gender and sexual orientation!]
** In 2014-11, OKCupid modified the gender and sexuality options. You can now select up to five from each of the following lists
*** Gender: Woman, Man, Agender, Androgynous, Bigender, Cis Man, Cis Woman, Genderfluid, Genderqueer, Gender Nonconforming, Hijra, Intersex, Non-binary, Other, Pangender, Transfeminine, Transgender, Transmasculine, Transsexual, Trans Man, Trans Woman, Two Spirit
*** Sexuality: Straight, Gay, Bisexual, Asexual, Demisexual, Heteroflexible, Homoflexible, Lesbian, Pansexual, Queer, Questioning, Sapiosexual
*** Source: [http://www.pinknews.co.uk/2014/11/16/okcupid-begins-rolling-out-new-sexuality-and-gender-options/ pinknews.co.uk]
*[http://openid.net/specs/openid-attribute-exchange-1_0.html OpenID's Attribute Exchange] includes gender
* [http://pof.com/ POF]: "Male" or "Female"
* [http://pownce.com/ Pownce]'s [http://pownce.com/settings/ Profile Settings](requires login) interface has a Gender popup with the following values in order:
** Guy, Girl, Dude, Chicky-poo, Bloke, Bird, Lady, Gentleman, Male, Female, Transgender, None of the Above
* [http://blog.xkcd.com/2010/05/06/sex-and-gender/ XKCD] used 'do you have a Y chromosome?' as they were studying colour blindness

== government/healthcare ==

* NHS Family doctor services registration form ([http://www.nhs.uk/servicedirectories/documents/gms1.pdf GMS1]): male, female
** Individual medical practices may supplement this form with their own registration form. Some allow for non-binary options for trans and intersex individuals...
** [http://www.belgravia-surgery-sw1.nhs.uk/website/E87005/files/Under_16s_New_Patient_Questionnaire_-The_Belgravia_Surgery.pdf Belgravia Surgery] (PDF) SW1: Male or Female
** [http://www.chelwest.nhs.uk/services/hiv-sexual-health/clinics/56-dean-street Dean Street sexual health clinic]: as part of their computerised registration process, they ask whether you are transgender. If you answer 'no', they then ask whether you are male or female. This is used to determine which medical tests are conducted.
** [http://www.marvenmedicalpractice.co.uk/ Marven Medical Practice], SW1V: "male", "female", "indeterminate"
** [http://www.northamsurgery.nhs.uk/website/L83050/files/NORTHAM_SURGERY_New_Born_Registration_Form.pdf Northam Surgery] (PDF): Male or Female
** [http://www.sexualhealthoxfordshire.nhs.uk/wp-content/uploads/2014/03/registration.pdf Sexual Health Oxfordshire] (PDF): Male or Female
** [http://www.gowerplacepractice.nhs.uk/website/F83043/files/UCL-Students-Health-Registration-Form-Protected.pdf UCL Students Health Registration Form] (PDF): Male or Female
** [http://www.yorksurgeryilford.nhs.uk/website/F86657/files/New_Patient_Registration_Form_2013.pdf York Surgery, Ilford] (PDF): Male or Female

== travel ==

* Eurotunnel.com Advance Passenger Information - if you book a journey on Eurotunnel, you have to provide Advance Passenger Information before travel. This includes name, passport number and gender. Options: Male, Female, Unknown

== discussion elsewhere ==
* [http://www.myspace.com/queering_gender Because gender isn't binary]
* [http://community.livejournal.com/feminist/2925885.html Social networking sites & gender identity]
* [https://meta.wikimedia.org/wiki/Survey_best_practices Survey best practices] on meta.wikimedia.org
* [http://www.glaad.org/transgender/trans101 Transgender 101], GLAAD
* [https://tranarchism.wordpress.com/2010/11/26/not-your-moms-trans-101/ Not Your Mom's Trans 101], Asher at Tranarchism
* [https://blog.wikimedia.org/2015/03/09/gender-as-a-text-field/ Gender as a text field: What Wikipedia can learn from Facebook], Amanda Menking, Wikimedia Blog, 2015-03-09
* [http://43epnd.axshare.com/gender.html #genderUX – Some guiding principles for handling gender on forms]

== see also ==
* [[gender]]
* [[gender-formats]]
* [[gender-brainstorming]]
* [[profile-examples]]

== related ==
* [[genealogy]]
* [[hcard|hCard]]
* [[vcard-suggestions]]

microformats2-linting

2015-07-12T14:57:04Z

TomMorris: /* Notes */ response to tantek

This page is to work out possible rules for a future microformats2 linter/validator.

The job of a linter or validator is to help the user correctly implement microformats2 on their site by making helpful (if somewhat pedantic) comments about the markup.

== Possible linting rules ==

# If a document has an <var>h-feed</var> class, it shouldn't have any <var>h-entry</var> elements that are not children of the <var>h-feed</var>.
# A non-nested <var>h-entry</var> should be on an article.
#* -1 [[User:Tantek|Tantek]] 14:44, 12 July 2015 (UTC) see below
# If the outer <var>h-entry</var> is an article element, arguably nested <var>h-entry</var>s should also be articles. This is explicitly recommended by §4.3.2 of HTML5.
#* -1 article tag is unnecessary extra markup / and or constraint for the semantics of h-entry. [[User:Tantek|Tantek]] 14:44, 12 July 2015 (UTC)
# <var>dt-created</var> <= <var>dt-published</var> <= <var>dt-updated</var>.

== Notes ==
* <code><article></code> in practice seems to serve no purpose in HTML5.
** I've stopped using it for this reason. [[User:Tantek|Tantek]] 14:44, 12 July 2015 (UTC)
** I use it because it's the correct element for the job. There's a bit of a chicken and egg problem here: we ask for the new elements, WHATWG/W3C give them to us as blank slates to play with, then we complain that they don't do anything. And the semantics of an h-entry and an article match up pretty damn well. My view is that the point of a linter is to give people the hints to get better at writing not just microformats but at writing HTML too. You can ignore its advice if you choose though. —[[User:TomMorris|Tom Morris]] 14:57, 12 July 2015 (UTC)

microformats2-linting

2015-07-12T14:04:52Z

TomMorris: drafting some linting rules

microformats2-faq

2015-07-11T14:50:27Z

TomMorris: /* see also */ adding experimental properties link

<entry-title>microformats2 FAQ</entry-title>

Frequently asked questions about [[microformats2]].

== when using both h-card and vcard which should be first and why ==
Q: When using both microformats2 and traditional microformats for backwards compatibility, which class name should go first and why?
Another example: should "h-event" be first (before the "vevent") in the class attribute?

A: '''Use the microformats2 class names first,''' and in equivalent pairs when marking up more than one property. E.g.
<source lang=html4strict>
<span class="h-card vcard">
<a class="p-name fn p-org org u-url url"
href="http://microformats.org/">microformats.org</a>
</span>

<span class="h-event vevent">
<a class="p-name summary u-url url"
href="http://plancast.com/p/e83d">microformats meetup SF</a>,
<time class="dt-start dtstart">2012-11-14 18:00</time>
</span>
</source>
Here's how:
* [[microformats2#backward_compatible|using microformats2 and backward compatible microformats]].

And why:
* The prefixes (h-, p-, etc.) of microformats2 class names provide easier recognition (as class names ''for'' microformats), and when followed by the similarly named existing class name, they're more easily recognized as related and thus kept together when the markup is moved or maintained over time.

== why are microformats 2 properties prefixed ==
Q: Why do microformats 2 property class names have prefixes like 'p-', 'u-', 'dt-', 'e-' ?

A: For the benefit of both web authors and developers of parsers/consumers. By using class names with a small handful of short easily recognizable prefixes, it's easier to see which class names belong to microformats, and which may serve other purposes on the page. This helps web designers better recognize and maintain support for microformats across site redesigns for example. In particular:
* The 'p-' prefix is for typical string properties and parsing thereof.
* 'u-' is for URL-like properties whose values often come from another attribute such as the <a> 'href' or <img> 'src'.
* 'dt-' is for date and time related properties that have a particular format themselves, and ideally should make good use of the HTML5 <time> element, though for backward compatibility they work on any element.
* Finally, 'e-' is for properties whose value is the entirety of the text and HTML inside an element, as represented by the element's DOM. The 'e-entry-content' property from hAtom for example permits marking up and parsing/extracting an entire post from an HTML blog post page to an Atom feed entry with full markup/DOM fidelity of the original post.
Since prefixes determine specific parsing rules, parser developers are able to write simple and efficient generic microformats 2.0 parsers without needing to know any specific vocabularies, either currently or in the future. These are both advantages of microformats 2.0 over original microformats. For more details, including why and how microformats 2.0 class name prefixes were developed, see: [[microformats2-prefixes]].

== how do you use experimental microformats and property names ==
I.e. what is the correct way to start using experimental microformats and property names in microformats2?

Documented primarily as [[microformats2#VENDOR_EXTENSIONS|microformats2 vendor extensions]], here's a quick summary:

There are two cases:

'''1. Vendor-specific''' - extensions that either only make sense in or have a very specific detailed or other meaning (e.g. a shibboleth) in a particular company or organizational context.

Use <code>-vendorabbr-</code> immediately after a microformats2 prefix, where "vendorabbr" is an abbreviation for the company (e.g. stock symbol) or organiztion. E.g.
* <code>h-goog-volcano</code> for a proprietary "volcano" object
* <code>p-osm-shop</code> for an OSM-site specific "shop" property

'''2. Experimental''' - ideas that authors/developers want to experiment with in the wild without going through the microformats [[process]] to craft well-researched microformats and property names. Or for experimental formats that you're not even sure would be worth trying to standardize, may apply to a narrow / small community etc. (which might still grow as a result of experimentation, and thus eventually merit a format).

Use <code>-x-</code> immediately after a microformats2 prefix, e.g.:
* <code>h-x-test-fixture</code> for an experimental "text-fixture" format (e.g. for a [[test-suite]]).
* <code>p-x-prep-time</code> - a possible experimental preparation time property to be added to [[hRecipe]] upon consideration/documentation of real-world usage/uptake.

== how do h-adr and h-geo work with an implied name property ==

Q: Some microformats like h-adr and h-geo are usually used as just collections of properties and typically lack explicit names or "p-name" properties. How does the implied "name" property work with such microformats?

A: First, there is the use-case of named locations which aren't necessarily full h-card venues in and of themselves. For named locations, the name is published in visible text and should be marked up with e.g. class="p-name".

Other h-adr and h-geo microformats which lack an explicit name will have a name implied for them (e.g. from the full text of the element including all such visible property values in document order).

While at first it may seem silly to create a name for something which is merely an address or a latitude+longitude geolocation, there are some good reasons to imply a name even for such collections of properties.

Locations are often shown in a list (e.g. by [http://indiewebcamp.com/checkin Checkin] interfaces and applications). Lists showing all the locations on a page (e.g. all its h-card, h-adr, h-geo microformats) need labels for each item. The name of a location (whether explicit or implied) serves as the presentational label/title for that location in such lists.

Checkin location lists are just one use-case, there are many more. Any kind of page summarization tool (e.g. validators, linters) or anything which presents an interface to summaries of a page (e.g. web search results) benefits from having an explicit automatic way to determine how to label each and every microformat data item on a page.

Every such list of data items needs to label the items, and rather than just calling them "untitled item 1" etc., using the actual visible content of the item provides a nice clear connection to the specific item. Since the implied name comes directly from a snippet of text authored by a human, in the order that the human authored it as they intended it to be read (listened to), it will make sense as a label as well.

If an author explicitly wants an empty label for their microformat, while not recommended, they can explicitly specify as such: <code><span class="p-name"></span></code>

In practice this has yet to be seen, thus for now, any concerns about awkward or confusing implied names for things like h-adr or h-geo are categorized as a "theoretical issue". If someone finds a real world example where the implied "name" causes a bad user experience in some actual use-case, then we can re-explore this topic.

== does microformats 2 combine vocabularies and syntax ==
Q: Does microformats 2 combine vocabularies and syntax?

A: No. From a parsing perspective, microformats 2 syntax is independent of any particular vocabulary. There are some [[microformats2-brainstorming]] proposals that take advantage of semantic HTML to imply certain common properties (name, url, photo) but that's an extremely limited set that's been determined from common markup patterns.

== does microformats 2 split vocabularies and syntax ==
Q: Does microformats 2 split vocabularies and syntax?

A: Yes, microformats 2 specifies a syntax for parsing microformats which is independent of any specific vocabulary. So in that sense it can be said that microformats 2 splits vocabularies and syntax.

== are microformats 2 vocabularies available to other languages ==
Q: Are microformats 2 vocabularies available to other languages?

A: ''Existing'' microformats vocabularies have [http://microformats.org/profile profiles] which are already available to other languages. Each term is defined by a URL ending in a hash and the term. This is due to the design of [[XMDP]] which deliberately produces such URLs which are compatible with microdata, RDF, and any other LinkedData system. microformats 2 vocabularies will use the same profile format and thus also be available to other languages.

== how do you convert a microformats 2 example to RDFa syntax ==
Q: How do you convert a microformats 2 example to RDFa 1.1 syntax?

A: In short you have to use the 'typeof' attribute for the microformats 2 root class name, and use the 'property' attribute for microformats 2 properties.

E.g. this from the microformats 2 page:

<source lang=html4strict>
<h1 class="h-card">
<span class="p-name">
<span class="p-given-name">Chris</span>
<abbr class="p-additional-name">R.</abbr>
<span class="p-family-name">Messina</span>
</span>
</h1>
</source>

Here is the same markup with RDFa 1.1 syntax, using an implied or explicit RDFa Profile from somewhere else (undefined):

<source lang=html4strict>
<h1 typeof="h-card">
<span property="p-name">
<span property="p-given-name">Chris</span>
<abbr property="p-additional-name">R.</abbr>
<span property="p-family-name">Messina</span>
</span>
</h1>
</source>

The similarity of these two markup examples implies that it may be possible to extend RDFa 1.1 compliant parsers to become compliant microformats 2 parsers.

== see also ==
* [[microformats2]]
* [[microformats2-brainstorming]]
* [[microformats2-experimental-properties]]
* [[microformats2-prefixes]]
* [[microformats2-faq]]

microformats2-implied-properties

2015-07-11T14:50:13Z

TomMorris: /* see also */ adding experimental properties link

<entry-title>microformats2 implied properties</entry-title>
== summary ==
As part of the further simplifications in [[microformats-2]], the following generic properties are automatically implied by microformats with only a root class name with certain common semantic markup patterns.

* '''<code>p-name</code>''' on elements in general
* '''<code>u-url</code>''' on hyperlinks (<code><a href></code>) elements
* '''<code>u-photo</code>''' on images (<code><img src></code>) elements
and combinations thereof.

== root class only and name property ==
Web pages with microformats nearly always markup proper nouns, which have a primary label of some sort, commonly known as a ''name''.

Thus if a microformat only has a root class name and no properties, then the entire text contents of the element is parsed as the '''<code>p-name</code>''' property of the microformat.

Markup example:

Simple person reference:
<source lang=html4strict>
<span class="h-card">Frances Berriman</span>
</source>

Parsed JSON with implied name property:
<source lang=javascript>
{
"type": ["h-card"],
"properties": {
"name": ["Frances Berriman"]
}
}
</source>

to-do:
* try examples with organizations, events, products (however note that those are almost always capitalized thus implying proper noun / name semantics)

use-cases:
* every single proper noun on any web page.

related FAQ:
* [[microformats2-faq#how_do_h-adr_and_h-geo_work_with_an_implied_name_property|how do instances of h-adr and h-geo work with implied names]]? short answer: (implied) names are useful for labeling them when in lists.

=== aside name vs fn ===
In short, why use 'name' instead of the well established 'fn' from existing microformats? (per [[naming-principle]] etc.)
Per feedback:
* from microformats mailing-lists over the years
** numerous individuals preferring 'name'
** asking why 'fn' repeatedly despite FAQ
* Google Rich Snippets renaming 'fn' as 'name' in RDFa and microdata variants of vocabularies
* ...
Choosing to use 'name' as the generic term moving forward instead of 'fn' - the benefits outweigh costs.

== hyperlink and url property ==
A significant proportion of proper noun references on web pages are a hyperlink to a page about that proper noun, AKA a ''URL'' for a proper noun.

Thus if a microformat is on a hyperlink element with only a root class name and no properties, then in addition to implying the name from its text contents, the <code>href</code> of the element is parsed as the '''<code>u-url</code>''' property of the microformat.

Markup example:

Simple hyperlinked person reference
<source lang=html4strict>
<a class="h-card" href="http://benward.me">Ben Ward</a>
</source>

Parsed JSON:
<source lang=javascript>
{
"type": ["h-card"],
"properties": {
"name": ["Ben Ward"],
"url": ["http://benward.me"]
}
}
</source>

to-do:
* try examples with organizations, events, products

use-cases:
* nearly every link to a person ever like on blog posts, blog rolls etc. all the same data/use-cases that informed [[XFN]].

== image and name photo properties ==
Many proper noun references on web pages are simply an embedded image of that proper noun, typically a representative ''photo'' of the proper noun, often with its ''name'' as alt text.

Thus if a microformat is on an image element (<code><img src></code>) with only a root class name and no properties, then the <code>src</code> of the element is parsed as the '''<code>u-photo</code>''' property of the microformat, and if present, the <code>alt</code> of the element is parsed as the '''<code>p-name</code>''' property of the microformat.

Markup example:
<source lang=html4strict>
<img class="h-card" src="http://example.org/pic.jpg" alt="Chris Messina" />
</source>

Parsed JSON:
<source lang=javascript>
{
"type": ["h-card"],
"properties": {
"name": ["Chris Messina"],
"photo": ["http://example.org/pic.jpg"]
}
}
</source>

An object element with a data attribute works the same way as the img element with its src attribute.

to-do:
* try examples with organizations, events, products

use-cases:
* nearly every social networking site that shows a grid of people without text already does so with img tags and their names in the alt attribute. Most of those are linked too, which brings us to the next markup structure which implies properties:

== hyperlinked image and name photo url properties ==
Often proper noun references on web pages are a representative image of the proper noun that is hyperlinked to a page about that proper noun.

Thus if a microformat is on a hyperlink element with only a root class name and no properties, and that element has a single child element and that element is an image, then in addition to implying the the URL from its <code>href</code>, the <code>src</code> of the child image element is parsed as the '''<code>u-photo</code>''' property of the microformat, and if present, its <code>alt</code> attribute is parsed as the '''<code>p-name</code> property of the microformat.

Markup example:
<source lang=html4strict>
<a class="h-card" href="http://rohit.khare.org/">
<img alt="Rohit Khare"
src="https://s3.amazonaws.com/twitter_production/profile_images/53307499/180px-Rohit-sq_bigger.jpg" />
</a>
</source>

Parsed JSON:
<source lang=javascript>
{
"type": ["h-card"],
"properties": {
"name": ["Rohit Khare"],
"url": ["http://rohit.khare.org"],
"photo": ["https://s3.amazonaws.com/twitter_production/profile_images/53307499/180px-Rohit-sq_bigger.jpg"]
}
}
</source>

An object element with a data attribute works the same way as the img element with its src attribute. E.g. '''<code><a class="h-card" href><object type="image/..." data="..."></code>''' in addition to implying '''<code>u-url</code>''' from the <code>href</code>, implies '''<code>u-photo</code>''' from the object element's <code>data</code>, as well as '''<code>p-name</code>''' from the text contents of the object as with elements in general.

use-cases:
* nearly every social networking site that shows a grid of people without text already does so with hyperlinked img tags and their names in the alt attribute.

== root class with one child hyperlink ==
* '''<code><span class="h-card"><a href="http://example.com">Ace Brown</a></span></code>''' - '''treat single hyperlink child as existing single hyperlink case.''' I.e. imply '''<code>u-url</code>''' from its href. This markup is generated in MediaWiki installs (e.g. Wikipedia) when you surround a MediaWiki link like <nowiki>[URL label] or [[Wiki page name]]</nowiki> with a <code><span></code> with a microformats root class name. Real world examples:
** http://www.w3.org/wiki/TPAC2011-Committee
* '''<code><span class="h-card"><a href="http://example.com"><img src alt="Ace Brown"/></a></span></code>''' ...similarly with single hyperlink child itself with single img child etc.

== root class with one child element and text ==
* '''<code><a class="h-card" href><img alt="" src/> Ace Brown</a></code>''' - a variant of the hyperlink with image pattern, this is an example where the alt text is provided as actual visible text rather than an alternative, and therefore an explicitly empty alt="" is provided to avoid duplicate/redundant information in non-visual renderings (e.g. speech). Imply '''<code>u-url</code>''' from href, '''<code>u-photo</code>''' from src, and '''<code>p-name</code>''' from the text content of the root element, with leading/trailing white-space removed. Real world examples:
** real world example: http://test.waterpigs.co.uk/activity/ - the element with class name "microcard"
** minimal markup-only example for discussion: http://krijnhoetmer.nl/irc-logs/microformats/20120901#l-147 from aaronpk
** minimal markup example with real values: http://krijnhoetmer.nl/irc-logs/microformats/20120901#l-150 from aaronpk
*** similar: https://gist.github.com/3585643 - has an explicit span around the text after the image, but is otherwise similar. If there is an actual use case for having the second child span around the visible text, then we should consider expanding to allow implied properties for that too (general pattern of image and then something else which has the name, e.g. span/b etc.).

== parsing ==
See: http://microformats.org/wiki/microformats2-parsing#parsing_for_implied_properties

== to do ==
to-do:
* try examples with organizations, events, products

== additional markup patterns to consider ==
Document more use-cases from actual publishing examples in the wild of simple items, e.g. from Wikipedia.

And some per the principle of least surprise - fleshing out some of the patterns to consider additional different combinations of elements, but in the same basic pattern(s).

=== root class on one element ===
Let's consider root class only on:
* '''<code><abbr class="h-card" title></code>''' - imply '''<code>p-name</code>''' from <code>title</code>. Example(s)/use-case(s):
** <code>(<abbr class="h-card" title="Richard Posner">Posner</abbr> 2010)</code>
*** from [[citation-formats#TCMOS_permalink|citation format styles TCMOS permalink]] (note abbreviated parenthetical style at end of that subsection). Longer form including surrounding [[citation-brainstorming#web_citations|h-cite]] markup:
<source lang=html4strict>
<cite class="p-author h-cite">
(<abbr class="h-card" title="Richard Posner">Posner</abbr>
<time class="dt-published">2010</time>)
</cite>
</source>
Note the problem of lacking an explicit "name" for the work being cited. Perhaps such an abbreviated citation reference could hyperlink to a full citation, and either:
<div class="discussion">
* incorporate the name of the work being cited by reference from that full citation, or
* perhaps create a new, smaller microformat as a subset of h-cite like abbreviated cite, or a cite reference. Try to pick a name according to what TCMOS calls those parenthetical references.
</div>

* '''<code><object class="h-card" type="image/..." data="..."></code>''' - imply '''<code>u-photo</code>''' from <code>data</code> and '''<code>p-name</code>''' from text contents as with elements in general.
* ...
==== rejected root only markup patterns ====
Is there anything that should be implied semantically from root class only on:
* <code><audio src></code> - no, because there is no common practice of simple audio element usage for proper nouns, it's nearly always nested in a broader context.
* <code><time datetime></code> - no, because there are no microformats that are just a datetime
* <code><video src></code> - no, because there is no common practice of simple video element usage, it's nearly always nested in a broader context.

Use-case counter-examples welcome.

=== root element and one child ===
* '''<code><a class="h-card" href><abbr title></code>''' - imply '''<code>u-url</code>''' from <code>href</code> and imply '''<code>p-name</code>''' from the abbr element's <code>title</code>. Similar to the abbr root element case above (if that's allowed, we should strongly consider allowing this too).

== see also ==
* [[microformats2]]
* [[microformats2-brainstorming]]
* [[microformats2-experimental-properties]]
* [[microformats2-prefixes]]
* [[microformats2-implied-properties]]
* [[microformats2-parsing]]
* [[microformats2-faq]]

microformats2-brainstorming

2015-07-11T14:49:28Z

TomMorris: /* see also */ linking to experimental properties

Brainstorming experimental / undeveloped / rejected ideas for [[microformats-2]].

== further simplifications ==

=== more on allow root class name only ===
This has been stable for a while, see:
* [[microformats-2-implied-properties]]

== incorporate rel ==
Many microformats use 'rel' attribute values, e.g. [[rel-tag]], [[rel-license]], [[rel-me]]. It would be good to continue supporting 'rel' values explicitly in the microformats2 model. Here are some existing use-cases and ways we would support them.

=== profile h-card rel-me ===
Many sites have profile pages (personal home pages, and social networks), marked up with hCard, and permitting one or more rel-me values to other profiles, e.g. if this content were on <nowiki>http://tantek.com/</nowiki> :

Tantek Çelik ([https://twitter.com/t @t], [http://github.com/tantek github.com/tantek])

with source:

<source lang=html4strict>
<span class="h-card">
<span class="p-name">Tantek Çelik</span>
(<a class="u-url" rel="me"
href="https://twitter.com/t"
>@t</a>,
<a class="u-url" rel="me"
href="http://github.com/tantek"
>github.com/tantek</a>)
</span>
</source>

Parsed JSON per microformats2 properties:
<source lang=javascript>
{
"items": [{
"type": ["h-card"],
"properties": {
"name": ["Tantek Çelik"],
"url": ["https://twitter.com/t",
"http://github.com/tantek"]
}
}]
}
</source>

We could incorporate rel property parsing either as just another property (like a 'u-' property) scoped to the microformat:
<source lang=javascript>
{
"items": [{
"type": ["h-card"],
"properties": {
"name": ["Tantek Çelik"],
"url": ["https://twitter.com/t",
"http://github.com/tantek"],
"rel-me": ["https://twitter.com/t",
"http://github.com/tantek"]
}
}]
}

</source>

Or as always within global scope (closer to HTML5's currently defined scoping for 'rel' attributed links in a document):
<source lang=javascript>
{
"items": [{
"url": "http://tantek.com/",
"rel-stylesheet": ["...", "..."],
"rel-me": ["https://twitter.com/t",
"http://github.com/tantek"]
},
{
"type": ["h-card"],
"properties": {
"name": ["Tantek Çelik"],
"url": ["https://twitter.com/t",
"http://github.com/tantek"],
}
}]
}
</source>

Note: "url" in that root level object is the URL of the document itself, which is necessary for:
* 'rel' semantics: which URL from to which other URL the rels apply to.
* vCard .vcf export "SOURCE:" property (URL that the vCards were derived from).

== document url ==
As described above in the rel section, it's useful to have a root context object which provides the URL of the document itself.

== adopt itemref ==
There many existing real-world use-cases where either:
* several microformats in a page want to share some common data without repeating it.
** e.g. a page about a product with multiple reviews of that product (very common, products sites, Amazon/CNET et al, review aggregators, Yelp et al)
** e.g. representing the author of multiple hAtom entries on a page. Currently this is possible with the <code><address class="hcard"></code> optimisation, which would be rendered obsolete by the proposed new generic parsing rules.
* a microformat in a page needs to incorporate information spread across different parts of a page, without assigning the entire page to that microformat

The [[include-pattern]] provides the necessary functionality for existing microformats (1.0).

For 2.0 it may be reasonable to simply re-use the nice <code>itemref</code> attribute from microdata, with identical/analogous functionality.

That is, when present on the root element of a microformat, the <code>itemref</code> attribute provides a space separated list of ids of elements in the document which are then incorporated as children of the microformat, before its actual children in the document. This is a simple coarse summary of course, and the actual itemref inclusion algorithm should be followed.

Questions and possible issues:
<div class="discussion">
* Does use of 'itemref' mean requiring [[HTML5]]?
** No, <code>itemref</code> is not part of the HTML5 specification, it is currently only part of the [[microdata]] ''last call'' working draft. Thus we would be adding a "new" attribute to HTML above and beyond HTML5, though one that is already specified, and validated by current HTML validators.
* Is 'itemref' documented as a stable draft?
** 'itemref' is defined in the Last Call Working Draft of microdata. Being "last call" it has some amount of stability, but could still change before it goes to candidate recommendation (CR).
* Doesn't microformats try to avoid introducing new attributes? (e.g. from RDFa in the past).
** Yes, in general microformats try to avoid introducing new attributes. It may be ok for the set of use-cases that need "itemref". That is, they *are* a minority of actual use-cases, and thus making them use a new attribute is probably ok.
* Wouldn't it be dangerous to adopt features of separate technologies that are unstable, may change, or may disappear?
** Indeed any time we consider adopting anything from technologies in working drafts we should consider their stability and dependability on a case-by-case basis. When we do decide to re-use such technologies, we should be sure to ''copy'' their definition/functionality and provide a non-normative reference to the source, rather than normatively depend on anything that could change or disappear. In the case of 'itemref', it's been stable for a while, and if we believe the [[schema.org]] implementation announcements, there are multiple real-world implementations that surface it in common ([[search]]) user interfaces.
* Wasn't RDFa a ''stable'' augmentation of HTML, and yet we resisted incorporated attributes from it?
** In practice, no, RDFa has continued to change evolve (which is good) in response to market feedback about its complexity. There was very little real world use (and thus exercising) of RDFa until Google provided it as a Rich Snippets alternative syntax in 2009. At this point, it may be reasonable to also consider attributes from RDFa (e.g. 'vocab' instead of 'profile'), however for this particular purpose (providing inclusion functionality), the 'itemref' attribute/feature makes the most sense.
</div>

== hReview item backward compatibility ==
It maybe necessary (pending research/evidence) to add backward compatible parsing for the class name "item" inside the backward compatible parsing for the root class name "hreview". If so, here are some notes on how to add that to the [[microformats2]] spec on v2 vocabularies.

=== h-item ===
...

For backward compatibility, microformats 2 parsers {{should}}, when parsing an "hreview" for backwards compatibility, detect the following root class name and property names. A microformats 2 parser may use existing microformats [[parsers]] to extract these properties. If an "h-item" is found, don't look for an "item" on the same element.

compat root class name: <code id="item">item</code><br/>
properties: (parsed as '''p-''' plain text unless otherwise specified)
* <code>fn</code> - parse as '''<code>p-name</code>'''
* <code>photo</code> - parse as '''<code>u-photo</code>'''
* <code>url</code> - parse as '''<code>u-url</code>'''

Note: we should analyze [[hreview-examples-in-wild]] to see if there are any that actually depend on parsing for "item", or if simply looking for "fn", "photo", and "url" directly inside a root class name of "hreview" is sufficient. If so, we should '''DROP''' this backward-compat parsing for the class name "item" as it may otherwise produce too many false positives ("item" is a fairly common term).

=== h-review ===
...
* <code>item</code> - including compat root vcard|vevent in the absence of h-card|h-event
...

Note: we should analyze [[hreview-examples-in-wild]] to see if there are any that actually depend on parsing for "item", or if simply looking for "fn", "photo", and "url" directly inside a root class name of "hreview" is sufficient. If so, we should '''DROP''' the backward-compat parsing for the class name "item" as it may otherwise produce too many false positives ("item" is a fairly common term).

=== register a mime type? ===
See [[microformats2-mime-type]].

== rejected ideas ==

=== n prefix for multiple numbers ===
Idea:

* '''"n-*" for (one or more) numbers''', e.g. "n-rating", "n-geo", leaving the semantics of more than one number up to specific format. e.g. for an "n-rating" inside an "h-review", the first number would presumably be the rating value, when only two numbers the second would be the "best" value (e.g. rated <code><span class="n-rating">3 out of 4</span></code>), when three numbers the second would be the "worst" and the third would be the "best" (e.g. <code><span class="n-rating">7.5 out of 1 to 10</span></code>). similarly "n-geo" would specify the first number to be the latitude and the second to be the longitude.

Rejected because while this *might* work for some properties in *English* it will NOT localize/internationalize well (orders of numbers in phrases change in different languages), and it will also limit the human expressivity of the plain text. Thanks to Ben Ward for this feedback at the 2011-06-02 microformats dinner. [[User:Tantek|Tantek]] 14:25, 9 June 2011 (UTC)

== see also ==
* [[microformats2]]
* [[microformats2-brainstorming]]
* [[microformats2-experimental-properties]]
* [[microformats2-prefixes]]
* [[microformats2-implied-properties]]
* [[microformats2-faq]]
* [[html-stripping-examples]]

microformats2-experimental-properties

2015-07-11T14:47:27Z

TomMorris: /* h-x-username */ adding tantek example

== h-as-* ==
ActivityStreams-based post types, usually done in combination with h-entry.

=== Usage ===

* [http://glennjones.net/ glennjones.net] ([http://glennjones.net/notes/2015-07-11 example: h-as-note])

== h-x-username ==

=== Usage ===

* [http://glennjones.net/ glennjones.net] ([http://glennjones.net/notes/2015-07-11 example])
* [http://tantek.com/ tantek.com] ([http://tantek.com/2015/191/t1/indiewebcamp-pre-party example])

== p-x-dietary-preference ==

For dietary preferences (vegetarian, vegan etc.) - the intention is to help event organisers organise catering by aggregating together the dietary preferences of attendees.

=== Suggested values ===
* ovo-lacto vegetarian
* lacto vegetarian
* ovo vegetarian
* vegan
* pescatarian
* omnivore
* gluten-free
* lactose-free

=== Usage ===
* [https://tommorris.org/ tommorris.org]

== p-x-pronoun-* ==

Properties to identify a user's preferred pronouns

; p-x-pronoun-nominative: the user's preferred nominative pronoun (e.g. he, she, they)
; p-x-pronoun-oblique: the user's preferred oblique pronoun (e.g. him, her, them)
; p-x-pronoun-possessive: the user's preferred possessive pronoun (e.g. his, hers, theirs)

=== Usage ===

* [https://waterpigs.co.uk/ waterpigs.co.uk]

== p-x-sexual-orientation ==

For when we eventually build the open web dating service.

;Suggested values:
:* straight or heterosexual
:* bisexual
:* pansexual
:* gay or lesbian or homosexual
:* asexual

=== Usage ===
* [https://tommorris.org/ tommorris.org]

microformats2-experimental-properties

2015-07-11T14:44:31Z

TomMorris: /* p-x-dietary-preference */ switching broken DL to headers

== h-as-* ==
ActivityStreams-based post types, usually done in combination with h-entry.

=== Usage ===

* [http://glennjones.net/ glennjones.net] ([http://glennjones.net/notes/2015-07-11 example: h-as-note])

== h-x-username ==

=== Usage ===

* [http://glennjones.net/ glennjones.net] ([http://glennjones.net/notes/2015-07-11 example])

== p-x-dietary-preference ==

For dietary preferences (vegetarian, vegan etc.) - the intention is to help event organisers organise catering by aggregating together the dietary preferences of attendees.

=== Suggested values ===
* ovo-lacto vegetarian
* lacto vegetarian
* ovo vegetarian
* vegan
* pescatarian
* omnivore
* gluten-free
* lactose-free

=== Usage ===
* [https://tommorris.org/ tommorris.org]

== p-x-pronoun-* ==

Properties to identify a user's preferred pronouns

; p-x-pronoun-nominative: the user's preferred nominative pronoun (e.g. he, she, they)
; p-x-pronoun-oblique: the user's preferred oblique pronoun (e.g. him, her, them)
; p-x-pronoun-possessive: the user's preferred possessive pronoun (e.g. his, hers, theirs)

=== Usage ===

* [https://waterpigs.co.uk/ waterpigs.co.uk]

== p-x-sexual-orientation ==

For when we eventually build the open web dating service.

;Suggested values:
:* straight or heterosexual
:* bisexual
:* pansexual
:* gay or lesbian or homosexual
:* asexual

=== Usage ===
* [https://tommorris.org/ tommorris.org]

microformats2-experimental-properties

2015-07-11T14:42:55Z

TomMorris: creating

== h-as-* ==
ActivityStreams-based post types, usually done in combination with h-entry.

=== Usage ===

* [http://glennjones.net/ glennjones.net] ([http://glennjones.net/notes/2015-07-11 example: h-as-note])

== h-x-username ==

=== Usage ===

* [http://glennjones.net/ glennjones.net] ([http://glennjones.net/notes/2015-07-11 example])

== p-x-dietary-preference ==

For dietary preferences (vegetarian, vegan etc.) - the intention is to help event organisers organise catering by aggregating together the dietary preferences of attendees.

;Suggested values
:* ovo-lacto vegetarian
:* lacto vegetarian
:* ovo vegetarian
:* vegan
:* pescatarian
:* omnivore
:* gluten-free
:* lactose-free

=== Usage ===
* [https://tommorris.org/ tommorris.org]

== p-x-pronoun-* ==

Properties to identify a user's preferred pronouns

; p-x-pronoun-nominative: the user's preferred nominative pronoun (e.g. he, she, they)
; p-x-pronoun-oblique: the user's preferred oblique pronoun (e.g. him, her, them)
; p-x-pronoun-possessive: the user's preferred possessive pronoun (e.g. his, hers, theirs)

=== Usage ===

* [https://waterpigs.co.uk/ waterpigs.co.uk]

== p-x-sexual-orientation ==

For when we eventually build the open web dating service.

;Suggested values:
:* straight or heterosexual
:* bisexual
:* pansexual
:* gay or lesbian or homosexual
:* asexual

=== Usage ===
* [https://tommorris.org/ tommorris.org]

microformats2

2015-07-11T14:24:57Z

TomMorris: /* SEE ALSO */ link to experimental properties list

<entry-title>microformats 2</entry-title>
Welcome to the microformats2 home page.

== Summary ==
Microformats2 is the simplest way to markup structured information in HTML. Microformats2 improves ease of use and implementation for <em>both</em> authors (publishers) and developers ([[microformats2-parsing|parser]] implementers).

Microformats2 replaces and supersedes both classic microformats, as well as incorporates lessons learned from [[microdata]] and [[RDFa]].

=== simple microformats 2 examples ===
Here are a few simple microformats2 examples along with canonical [[JSON]].

==== person example ====
* Simple person reference:
<source lang=html4strict>
<span class="h-card">Frances Berriman</span>
</source>

Parsed JSON:
<source lang=javascript>
{
"items": [{
"type": ["h-card"],
"properties": {
"name": ["Frances Berriman"]
}
}]
}
</source>

----

==== hyperlinked person ====
* Simple hyperlinked person reference
<source lang=html4strict>
<a class="h-card" href="http://benward.me">Ben Ward</a>
</source>

Parsed JSON:
<source lang=javascript>
{
"items": [{
"type": ["h-card"],
"properties": {
"name": ["Ben Ward"],
"url": ["http://benward.me"]
}
}]
}
</source>

----

==== hyperlinked person image ====
* Simple hyperlinked person image
<source lang=html4strict>
<a class="h-card" href="http://rohit.khare.org/">
<img alt="Rohit Khare"
src="https://s3.amazonaws.com/twitter_production/profile_images/53307499/180px-Rohit-sq_bigger.jpg" />
</a>
</source>

Parsed JSON:
<source lang=javascript>
{
"items": [{
"type": ["h-card"],
"properties": {
"name": ["Rohit Khare"],
"url": ["http://rohit.khare.org"],
"photo": ["https://s3.amazonaws.com/twitter_production/profile_images/53307499/180px-Rohit-sq_bigger.jpg"]
}
}]
}
</source>

Additional simple cases details in [[microformats-2-implied-properties]].

----

==== detailed person example ====
* More detailed person
<source lang=html4strict>
<div class="h-card">
<img class="u-photo" alt="photo of Mitchell"
src="https://webfwd.org/content/about-experts/300.mitchellbaker/mentor_mbaker.jpg"/>
<a class="p-name u-url"
href="http://blog.lizardwrangler.com/"
>Mitchell Baker</a>
(<a class="u-url"
href="https://twitter.com/MitchellBaker"
>@MitchellBaker</a>)
<span class="p-org">Mozilla Foundation</span>
<p class="p-note">
Mitchell is responsible for setting the direction and scope of the Mozilla Foundation and its activities.
</p>
<span class="p-category">Strategy</span>
<span class="p-category">Leadership</span>
</div>
</source>

Parsed JSON:
<source lang=javascript>
{
"items": [{
"type": ["h-card"],
"properties": {
"photo": ["https://webfwd.org/content/about-experts/300.mitchellbaker/mentor_mbaker.jpg"],
"name": ["Mitchell Baker"],
"url": [
"http://blog.lizardwrangler.com/",
"https://twitter.com/MitchellBaker"
],
"org": ["Mozilla Foundation"],
"note": ["Mitchell is responsible for setting the direction and scope of the Mozilla Foundation and its activities."],
"category": [
"Strategy",
"Leadership"
]
}
}]
}
</source>

----
Notes:
# The JSON <code>"type"</code> uses the full microformat root class name (e.g. <code>"h-card"</code>) for consistent identification.
# all properties are optional and syntactically plural with parsed values provided in document order; particular microformats (and applications there-of) may apply specific/singular semantics to first value of a property.

=== microformats2 design ===
microformats2 has the following key design aspects:
# '''Prefixes for class names.''' Class names used for microformats use prefixes that start with with <code>'h-' 'p-' 'u-' 'dt-', 'e-'</code>. These are '''syntax independent from vocabularies''', which can then be developed separately.
#* 'h-*' for root class names, e.g. 'h-card'
#* 'p-*' for simple (text) properties, e.g. 'p-name'
#* 'u-*' for URL properties, e.g. 'u-photo'
#* 'dt-*' for date/time properties, e.g. 'dt-bday'
#* 'e-*' for embedded markup properties, e.g. 'e-note'. See [[microformats2#naming_conventions_for_generic_parsing|prefix naming conventions]] for more details.
# '''Flat sets of optional properties.''' All microformats consist of a root, and a collection of properties. Hierarchical data is represented with nested microformats, typically as property values themselves. Properties are all optional and potentially multivalued (applications needing a singular semantic may use first instance).
# '''Single class markup for common uses.''' Common simple markup patterns require only a single microformat root class name, which parsers use to find a few generic properties: <code>name, url, photo</code>. The simple microformats2 examples above demonstrate these.

Parsing details for each of these (including how to generate canonical JSON) are specified step-by-step in the:
* '''[[microformats2-parsing|microformats2 parsing specification]]'''

== v2 vocabularies ==
Status: '''<span id="draft_v2_vocabularies">draft</span>'''. Please review and provide feedback in [[IRC]].
* [[h-adr]]
* [[h-card]]
* [[h-entry]]
* [[h-event]]
* [[h-feed]]
* [[h-geo]]
* [[h-item]]
* [[h-listing]]
* [[h-product]]
* [[h-recipe]]
* [[h-resume]]
* [[h-review]]
* [[h-review-aggregate]]

See below for vocabulary summaries.

=== h-adr ===
{{main|h-adr}}

The '''h-adr''' microformat is for marking up structured locations such as addresses, physical and/or postal. This is an update to [[adr]].

root class name: '''<code>h-adr</code>'''<br/>
profile/itemtype: <nowiki>http://microformats.org/profile/h-adr</nowiki>

properties:
* '''<code>p-post-office-box</code>'''
* '''<code>p-extended-address</code>'''
* '''<code>p-street-address</code>'''
* '''<code>p-locality</code>'''
* '''<code>p-region</code>'''
* '''<code>p-postal-code</code>'''
* '''<code>p-country-name</code>'''
* '''<code>p-label</code>''' - new in [[vCard4]] ([[RFC6350]])
* '''<code>p-geo</code>''' (or '''<code>u-geo</code>''' with a RFC 5870 geo: URL) - new in [[vCard4]] ([[RFC6350]])
* '''<code>p-latitude</code>''' - new in [[vCard4]] ([[RFC6350]] from RFC 5870)
* '''<code>p-longitude</code>''' - new in [[vCard4]] ([[RFC6350]] from RFC 5870)
* '''<code>p-altitude</code>''' - new in [[vCard4]] ([[RFC6350]] from RFC 5870)

For backward compatibility, microformats 2 parsers {{should}} detect the following root class name and property names. A microformats 2 parser may use existing microformats [[parsers]] to extract these properties. If an "h-adr" is found, don't look for an "adr" on the same element.

compat root class name: <code id="adr">adr</code><br/>
properties: (parsed as '''p-''' plain text unless otherwise specified)
* <code>post-office-box</code>
* <code>extended-address</code>
* <code>street-address</code>
* <code>locality</code>
* <code>region</code>
* <code>postal-code</code>
* <code>country-name</code>

=== h-card ===
{{main|h-card}}

The '''h-card''' microformat is for marking up people and organizations. This is an update to [[hCard]].

root class name: '''<code>h-card</code>'''<br/>
profile/itemtype: <nowiki>http://microformats.org/profile/h-card</nowiki>

properties:
* '''<code>p-name</code>'''
* '''<code>p-honorific-prefix</code>'''
* '''<code>p-given-name</code>'''
* '''<code>p-additional-name</code>'''
* '''<code>p-family-name</code>'''
* '''<code>p-sort-string</code>'''
* '''<code>p-honorific-suffix</code>'''
* '''<code>p-nickname</code>'''
* '''<code>u-email</code>'''
* '''<code>u-logo</code>'''
* '''<code>u-photo</code>'''
* '''<code>u-url</code>'''
* '''<code>u-uid</code>'''
* '''<code>p-category</code>'''
* '''<code>p-adr</code>'''
* '''<code>p-post-office-box</code>'''
* '''<code>p-extended-address</code>'''
* '''<code>p-street-address</code>'''
* '''<code>p-locality</code>'''
* '''<code>p-region</code>'''
* '''<code>p-postal-code</code>'''
* '''<code>p-country-name</code>'''
* '''<code>p-label</code>'''
* '''<code>p-geo</code>''' or '''<code>u-geo</code>''' with a RFC 5870 geo: URL, new in [[vCard4]] ([[RFC6350]])
* '''<code>p-latitude</code>'''
* '''<code>p-longitude</code>'''
* '''<code>p-altitude</code>''' - new in [[vCard4]] ([[RFC6350]] from RFC 5870)
* '''<code>p-tel</code>'''
* '''<code>p-note</code>'''
* '''<code>dt-bday</code>'''
* '''<code>u-key</code>'''
* '''<code>p-org</code>'''
* '''<code>p-job-title</code>''' - previously 'title' in hCard, disambiguated.
* '''<code>p-role</code>
* '''<code>u-impp</code>''' per RFC 4770, new in [[vCard4]] ([[RFC6350]])
* '''<code>p-sex</code>''' new in [[vCard4]] ([[RFC6350]])
* '''<code>p-gender-identity</code>''' new in [[vCard4]] ([[RFC6350]])
* '''<code>dt-anniversary</code>''' new in [[vCard4]] ([[RFC6350]])
* ...

Reserved properties: (properties not used much (if at all) in practice)
* '''<code>p-organization-name</code>'''
* '''<code>p-organization-unit</code>'''
* '''<code>p-tz</code>'''
* '''<code>dt-rev</code>'''
* ...

For backward compatibility, microformats 2 parsers {{should}} detect the following root class name and property names. A microformats 2 parser may use existing microformats [[parsers]] to extract these properties. If an "h-card" is found, don't look for a "vcard" on the same element.

compat root class name: <code id="vcard">vcard</code><br/>
properties: (parsed as '''p-''' plain text unless otherwise specified)
* <code>fn</code> - parse as '''<code>p-name</code>'''
* <code>honorific-prefix</code>
* <code>given-name</code>
* <code>additional-name</code>
* <code>family-name</code>
* <code>honorific-suffix</code>
* <code>nickname</code>
* <code>email</code> - parse as '''u-'''
* <code>logo</code> - parse as '''u-'''
* <code>photo</code> - parse as '''u-'''
* <code>url</code> - parse as '''u-'''
* <code>uid</code> - parse as '''u-'''
* <code>category</code>
* <code>adr</code> - parse as '''<code>p-adr h-adr</code>''' including compat root class <code>adr</code>
* <code>extended-address</code>
* <code>street-address</code>
* <code>locality</code>
* <code>region</code>
* <code>postal-code</code>
* <code>country-name</code>
* <code>label</code>
* <code>geo</code> - parse as '''<code>p-geo h-geo</code>''' including compat root class <code>geo</code>
* <code>latitude</code>
* <code>longitude</code>
* <code>tel</code>
* <code>note</code>
* <code>bday</code> - parse as '''dt-'''
* <code>key</code> - parse as '''u-'''
* <code>org</code>
* <code>organization-name</code>
* <code>organization-unit</code>
* <code>title</code> - parse as '''p-job-title'''
* <code>role</code>
* ...

Reserved: (backward compat properties that parsers {{may}} implement, if they do, they {{must}} implement in this way:
* <code>tz</code>
* <code>rev</code> - parse as '''dt-'''
* ...

Note: use of 'value' within 'tel' should be automatically handled by the support of the [[value-class-pattern]]. And for now, the 'type' subproperty of 'tel' is dropped/ignored. If there is demonstrable documented need for additional tel types (e.g. fax), we can introduce new flat properties as needed (e.g. p-tel-fax).

=== h-entry ===
{{main|h-entry}}

The '''h-entry''' microformat is for marking up syndicatable content such as blog posts, notes, articles, comments, photos and similar. This is an update to [[hAtom]].

root class name: '''<code>h-entry</code>'''<br/>
profile/itemtype: <nowiki>http://microformats.org/profile/h-entry</nowiki>

properties:
* '''<code>p-name</code>''' (was p-entry-title, see issues)
* '''<code>p-summary</code>''' (was p-entry-summary, see issues)
* '''<code>e-content</code>''' (was e-entry-content, see issues)
* '''<code>dt-published</code>'''
* '''<code>dt-updated</code>'''
* '''<code>p-author</code>'''
* '''<code>p-category</code>'''
* '''<code>u-url</code>'''
* '''<code>u-uid</code>'''
* '''<code>p-geo</code>'''
* '''<code>p-latitude</code>'''
* '''<code>p-longitude</code>'''

This is an update to [[hAtom]].

Brainstorming:

The following properties are proposed additions to h-entry above and beyond what hAtom (or Atom) provides, based on various existing link preview markup conventions:
* '''<code>u-photo</code>'''
* '''<code>u-audio</code>''' - consider special u- parsing rules for <code><audio></code>
* '''<code>u-video</code>''' - consider special u- parsing rules for <code><video></code>
* '''<code>u-in-reply-to</code>''' - for links to other posts that this post is a reply to (comment regarding, etc.)

Backward compatibility:

(*)hAtom-specific implementations that perform custom display or translation (e.g. to Atom XML) {{should}} prefer <code>p-name</code> over <code>p-entry-title</code>, and use <code>p-entry-title</code> value(s) as a fallback if there is no <code>p-name</code>.

For hAtom backward compatibility, microformats 2 parsers {{should}} detect the following root class name and property names. A microformats 2 parser may use existing microformats [[parsers]] to extract these properties. If an "h-entry" is found, don't look for a "hentry" on the same element.

compat root class name: <code id="hentry">hentry</code><br/>
properties: (parsed as '''p-''' plain text unless otherwise specified)
* <code>entry-title</code> - parse as '''<code>p-name</code>'''
* <code>entry-summary</code>
* <code>entry-content</code> - parse as '''e-'''
* <code>published</code> - parse as '''dt-'''
* <code>updated</code> - parse as '''dt-'''
* <code>author</code> - including compat root <code>vcard</code> in the absence of <code>h-card</code>
* <code>category</code>
* <code>geo</code> - parse as '''<code>p-geo h-geo</code>''' including compat root <code>geo</code>
* <code>latitude</code>
* <code>longitude</code>
* ...

<span id="h-entry-faq">FAQ:</span>
<div class="discussion">
* '''What is the <code>p-name</code> of a [http://indiewebcamp.com/note note]?'''
** A few options, from simplest to most detailed.
*** '''same as the p-content/e-content''' property.
*** '''same as the <code>title</code> element''' on the note permalink post page. When publishing a note on its own permalink post page, the contents of the note are likely abbreviated for the title of the page. The same abbreviation can be used for the p-name.
*** '''first sentence of the p-content/e-content''' property. It may be better for [http://indiewebcamp.com/syndication syndication] and [[link-preview]] purposes to provide just the first sentence of the note as the <code>p-name</code>. Similarly if only a portion of the content is syndicated to other sites, that portion can be marked up as the <code>p-summary</code>.
* ...
</div>

Resolved Issues:
* 2012-245 Resolved. See [http://krijnhoetmer.nl/irc-logs/microformats/20120830#l-120 2012-243 IRC discussion/consensus] for:
** Use '''<code>p-summary</code> instead of <code>p-entry-summary</code>'''. The historical semantic of "entry-summary" is not different from "summary" in any significant (or discernible way). Collapsing the two will simplify the overall microformats2 vocabularies further. In microformats2, entry-summary is no more.
** Use '''<code>e-content</code> instead of <code>e-entry-content</code>'''. Same point and advantage. In microformats2, entry-content is no more.
** '''drop <code>p-entry-title</code>'''. Unnecessary and subsumed by "p-name". Would consider move to backward compat only if cases are presented - known publishing uses are expected to be updated shortly.

=== h-event ===
{{main|h-event}}

The '''h-event''' microformat is for marking up events. This is an update to [[hCalendar]].

root class name: '''<code>h-event</code>'''<br/>
profile/itemtype: <nowiki>http://microformats.org/profile/h-event</nowiki>

properties:
* '''<code>p-name</code>'''
* '''<code>p-summary</code>'''(*)
* '''<code>dt-start</code>'''
* '''<code>dt-end</code>'''
* '''<code>dt-duration</code>'''
* '''<code>p-description</code>'''
* '''<code>u-url</code>'''
* '''<code>p-category</code>'''
* '''<code>p-location</code>'''
* '''<code>p-geo</code>'''
* '''<code>p-latitude</code>'''
* '''<code>p-longitude</code>'''
* ...

This is an update to [[hCalendar]].

(*)hCalendar-specific implementations that perform custom display or translation (e.g. to iCalendar .ics) {{should}} prefer <code>p-name</code> over <code>p-summary</code>, and use <code>p-summary</code> value(s) as a fallback if there is no <code>p-name</code>.

For backward compatibility, microformats 2 parsers {{should}} detect the following root class name and property names. A microformats 2 parser may use existing microformats [[parsers]] to extract these properties. If an "h-event" is found, don't look for a "vevent" on the same element.

compat root class name: <code id="vevent">vevent</code><br/>
properties: (parsed as '''p-''' plain text unless otherwise specified)
* <code>summary</code> - parse as '''<code>p-name</code>'''
* <code>dtstart</code> - parse as '''<code>dt-start</code>'''
* <code>dtend</code> - parse as '''<code>dt-end</code>'''
* <code>duration</code> - parse as '''<code>dt-duration</code>'''
* <code>description</code>
* <code>url</code> - parse as '''u-'''
* <code>category</code>
* <code>location</code> - including compat root <code>vcard</code> in the absence of <code>h-card</code>, and compat root <code>adr</code> in the absence of <code>h-adr</code>
* <code>geo</code> - parse as '''<code>p-geo h-geo</code>''' including compat root <code>geo</code>
* <code>latitude</code>
* <code>longitude</code>
* ...

=== h-geo ===
{{main|h-geo}}

The '''h-geo''' microformat is for marking up WGS84 geophysical coordinates. This is an update to [[geo]].

root class name: '''<code>h-geo</code>'''<br/>
profile/itemtype: <nowiki>http://microformats.org/profile/h-geo</nowiki>

properties:
* '''<code>p-latitude</code>'''
* '''<code>p-longitude</code>'''
* '''<code>p-altitude</code>''' - new in [[vCard4]] ([[RFC6350]] from RFC 5870)

For backward compatibility, microformats 2 parsers {{should}} detect the following root class name and property names. A microformats 2 parser may use existing microformats [[parsers]] to extract these properties. If an "h-geo" is found, don't look for an "geo" on the same element.

compat root class name: <code id="geo">geo</code>
properties: (parsed as '''p-''' plain text unless otherwise specified)
* <code>latitude</code>
* <code>longitude</code>

=== h-item ===
{{main|h-item}}

The '''h-item''' microformat is for marking up the item of an [[h-review]] or [[h-product]]. This is an update to part of [[hReview]].

root class name: '''<code>h-item</code>'''<br/>
profile/itemtype: <nowiki>http://microformats.org/profile/h-item</nowiki>

properties:
* '''<code>p-name</code>'''
* '''<code>u-photo</code>'''
* '''<code>u-url</code>'''

Note: in practice, due to the microformats2 implied property rules, it is expected that most uses of "h-item" won't require any explicit properties at all (since microformats2 parsers will infer name, photo, and url properties from the structure of the element with "h-item" and its contained content/elements if any).

=== h-product ===
{{main|h-product}}

The '''h-product''' microformat is for marking up products. This is an update to [[hProduct]].

root class name: '''<code>h-product</code>'''<br/>
profile/itemtype: <nowiki>http://microformats.org/profile/h-product</nowiki>

properties:
* '''<code>p-name</code>''' - name of the product
* '''<code>u-photo</code>''' - photo of the product
* '''<code>p-brand</code>''' - manufacturer, can also be a nested <code>h-card</code>
* '''<code>p-category</code>''' - freeform categories or tags applied to the item by the reviewer
* '''<code>e-description</code>'''
* '''<code>u-url</code>''' - URL of the product
* '''<code>u-identifier</code>''' - includes type (e.g. mpn, upc, isbn, issn, sn, vin, sku etc.) and value.
* '''<code>p-review</code>''' - a review of the product, can also be a nested <code>h-review</code>
* '''<code>p-price</code>''' - retail price of the product

For backward compatibility, microformats 2 parsers {{should}} detect the following root class name and property names. A microformats 2 parser may use existing microformats [[parsers]] to extract these properties. If an "h-product" is found, don't look for an "hproduct" on the same element.

compat root class name: <code id="hproduct">hproduct</code><br/>
properties: (parsed as '''p-''' plain text unless otherwise specified)
* <code>fn</code> - parse as '''<code>p-name</code>'''
* <code>photo</code> - parse as '''u-'''
* <code>brand</code>
* <code>category</code>
* <code>description</code>
* <code>identifier</code> - parse as '''u-'''
* <code>url</code> - parse as '''u-'''
* <code>review</code> - including compat root class <code>hreview</code> in the absence of <code>h-review</code>
* <code>price</code>

Note: [[hProduct]] has at least one experimental property which has real world adoption due to [[Google]] and [[Bing]] search support of hProduct. Currently this is: '''price'''

=== h-recipe ===
{{main|h-recipe}}

The '''h-recipe''' microformat is for marking up food recipes. This is an update to [[hRecipe]].

root class name: '''<code>h-recipe</code>'''<br/>
profile/itemtype: <nowiki>http://microformats.org/profile/h-recipe</nowiki>

properties:
* '''<code>p-name</code>''' - the name of the recipe
* '''<code>p-ingredient</code>''' - describes one or more ingredients used in the recipe.
* '''<code>p-yield</code>''' - Specifies the quantity produced by the recipe, like how many persons it satisfyies
* '''<code>e-instructions</code>''' - the method of the recipe.
* '''<code>dt-duration</code>''' - the time it takes to prepare the meal described by the recipe.
* '''<code>u-photo</code>''' - an accompanying image

Experimental properties with wide adoption
* '''<code>p-summary</code>''' - provides a short summary or introduction
* '''<code>p-author</code>''' - the person who wrote the recipe with <code>h-card</code>
* '''<code>dt-published</code>''' - the date the recipe was published
* '''<code>p-nutrition</code>''' - nutritional information like calories, fat, dietary fiber etc.
* ...

For backward compatibility, microformats 2 parsers {{should}} detect the following root class name and property names. A microformats 2 parser may use existing microformats [[parsers]] to extract these properties. If an "h-recipe" is found, don't look for an "hrecipe" on the same element.

compat root class name: <code id="hrecipe">hrecipe</code><br/>
properties: (parsed as '''p-''' plain text unless otherwise specified)
* <code>fn</code> - parse as '''<code>p-name</code>'''
* <code>ingredient</code>
* <code>yield</code>
* <code>instructions</code> - parse as '''e-'''
* <code>duration</code> - parse as '''dt-'''
* <code>photo</code> - parse as '''u-'''
* <code>summary</code>
* <code>author</code> - including compat root <code>vcard</code> in the absence of <code>h-card</code>
* <code>nutrition</code>

Note: [[hRecipe]] has a number of experimental properties which have real world adoption due to [[Google]] recipe search support of hRecipe. These are: summary, author, published and nutrition

=== h-resume ===
{{main|h-resume}}

The '''h-resume''' microformat is for marking up resumes. This is an update to [[hResume]].

root class name: '''<code>h-resume</code>'''<br/>
profile/itemtype: <nowiki>http://microformats.org/profile/h-resume</nowiki>

properties:
* '''<code>p-summary</code>''' - overview of qualifications and objectives
* '''<code>p-contact</code>''' - current contact info in an <code>h-card</code>
* '''<code>p-education</code>''' - an education <code>h-calendar</code> event, years, nested <code>h-card</code> of the school, location.
* '''<code>p-experience</code>''' - a job or other professional experience <code>h-calendar</code> event, years, nested <code>h-card</code> of the organization, location, job-title.
* '''<code>p-skill</code>''' - a skill or ability, optionally including level and/or duration of experience
* '''<code>p-affiliation</code>''' - an affiliation with an <code>h-card</code> organization

For backward compatibility, microformats 2 parsers {{should}} detect the following root class name and property names. A microformats 2 parser may use existing microformats [[parsers]] to extract these properties. If an "h-resume" is found, don't look for an "hresume" on the same element.

compat root class name: <code id="hresume">hresume</code><br/>
properties: (parsed as '''p-''' plain text unless otherwise specified)
* <code>summary</code>
* <code>contact</code> - including compat root <code>vcard</code> in the absence of <code>h-card</code>
* <code>education</code> - including compat root <code>vevent</code> in the absence of <code>h-event</code>
* <code>experience</code> - including compat root <code>vevent</code> in the absence of <code>h-event</code>
* <code>skill</code>
* <code>affiliation</code> - including compat root <code>vcard</code> in the absence of <code>h-card</code>

Note: skill has a [[hresume-skill-brainstorm|proposed expansion into competency]] with explicit summary, rating and/or duration components. Based on existing real world adoption, we should consider an h-competency vocabulary with p-summary, p-rating, and dt-duration properties.

=== h-review ===
{{main|h-review}}

The '''h-review''' microformat is for marking up reviews. This is an update to [[hReview]]. See also [[h-item]].

root class name: '''<code>h-review</code>'''<br/>
profile/itemtype: <nowiki>http://microformats.org/profile/h-review</nowiki>

properties:
* '''<code>p-name</code>''' - name of the review
* '''<code>p-item</code>''' - thing been reviewed i.e. business or person (h-card), event (h-event), place (h-adr or h-geo), product (h-product), website, url, or other item ([[h-item]]).
* '''<code>p-reviewer</code>''' - person who authored the review
* '''<code>dt-reviewed</code>''' - date time of when the review was written
* '''<code>p-rating</code>''' - value from 1-5 indicating a rating for the item (5 best).
* '''<code>p-best</code>''' - define best rating value. can be numerically lower than worst.
* '''<code>p-worst</code>''' - define worst rating value. can be numerically higher than best.
* '''<code>e-description</code>''' - the full text written evaluation and opinion of the reviewer
* '''<code>p-category</code>''' - freeform categories or tags applied to the item by the reviewer
* '''<code>u-url</code>''' - URL of the review

For backward compatibility, microformats 2 parsers {{should}} detect the following root class name and property names. A microformats 2 parser may use existing microformats [[parsers]] to extract these properties. If an "h-review" is found, don't look for an "hreview" on the same element.

compat root class name: <code id="hreview">hreview</code><br/>
properties: (parsed as '''p-''' plain text unless otherwise specified)
* <code>summary</code> parse as '''<code>p-name</code>'''
* <code>fn</code> - parse as '''p-name''' of the item being reviewed (p-item h-item p-name)
* <code>photo</code> - parse as '''u-photo''' of the item being reviewed (p-item h-item u-photo)
* <code>url</code> - parse as '''u-url''' of the item being reviewed (p-item h-item u-url)
* <code>reviewer</code> - including compat root vcard in the absence of h-card
* <code>dtreviewed</code> - parse as '''dt-'''
* <code>rating</code>
* <code>best</code>
* <code>worst</code>
* <code>description</code> - parse as '''e-'''
* <code>rel="tag"</code> - parse as '''p-category'''
* <code>rel="self bookmark"</code> - parse as '''u-url'''. note that <code>rel</code> attribute value is treated as a space separated set, thus any presence of "self" and "bookmark" within such a set in a rel value is accepted.

Note: The [[hReview]] format has three properties which make use of <code>rel</code> attribute, these are <code>tag</code>, permalink (via the <code>self</code> and <code>bookmark</code> values) and <code>license</code>. Microformats 2 parsers {{should}} map these URLs into the page scoped rel collection.

=== h-review-aggregate ===
{{main|h-review-aggregate}}

The '''h-review-aggregate''' microformat is for marking up aggregate reviews of a single item. This is an update to [[hreview-aggregate]]. See also [[h-item]].

root class name: '''<code>h-review-aggregate</code>'''<br/>
profile/itemtype: <nowiki>http://microformats.org/profile/h-review-aggregate</nowiki>

properties:
* '''<code>p-name</code>''' - name of the review
* '''<code>p-item</code>''' - thing been reviewed i.e. business or person (h-card), event (h-event), place (h-adr or h-geo), product (h-product), website, url, or other item (h-item).
* '''<code>p-rating</code>''' - value from 1-5 indicating average rating for the item (5 best).
* '''<code>p-best</code>''' - define best rating value. can be numerically lower than worst.
* '''<code>p-worst</code>''' - define worst rating value. can be numerically higher than best.
* '''<code>p-count</code>''' - number of reviews aggregated.
* '''<code>p-votes</code>''' - number of reviewers who have rated the product, thus contributing to the average rating.
* '''<code>p-category</code>''' - freeform categories or tags applied to the item by the reviewer
* '''<code>u-url</code>''' - URL of the review

For backward compatibility, microformats 2 parsers {{should}} detect the following root class name and property names. A microformats 2 parser may use existing microformats [[parsers]] to extract these properties. If an "h-review-aggregate" is found, don't look for an "hreview-aggregate" on the same element.

compat root class name: <code id="hreview-aggregate">hreview-aggregate</code><br/>
properties: (parsed as '''p-''' plain text unless otherwise specified)
* <code>summary</code> parse as '''<code>p-name</code>'''
* <code>fn</code> - parse as '''p-name''' of the item being reviewed (p-item h-item p-name)
* <code>photo</code> - parse as '''u-photo''' of the item being reviewed (p-item h-item u-photo)
* <code>url</code> - parse as '''u-url''' of the item being reviewed (p-item h-item u-url)
* <code>rating</code>
* <code>best</code>
* <code>worst</code>
* <code>count</code>
* <code>votes</code>
* <code>rel="tag"</code> - parse as '''p-category'''
* <code>rel="self bookmark"</code> - parse as '''u-url'''. note that <code>rel</code> attribute value is treated as a space separated set, thus any presence of "self" and "bookmark" within such a set in a rel value is accepted.

=== v2 vocab notes ===
Notes:
* All v2 vocabularies are defined as flat lists of properties of an object/item, and thus can be used in microformats-2 syntax as shown, or in microdata items, or RDFa. The microformats-2 property parsing prefixes "p-", "u-", "dt-", "e-" are omitted when using defined properties in microdata itemprop and RDFa property as those syntaxes have their own element-specific parsing rules.
* Profile URLs are provided for use with the HTML4 <code>profile</code> attribute, microdata <code>itemtype</code> attribute, and RDFa <code>vocab</code> & <code>typeof</code> attributes (though the latter requires slicing off the trailing segment of the profile for the typeof attribute, and leaving the rest in vocab).
* microformats 2 properties may also be explicitly bound as URIs using [[rel-profile]], the [[html5-profile]] attribute proposal, or an HTML5 'vocab' attribute instead. If URI bound terms are important to you, please express interest on [[rel-profile]], [[html5-profile]], or contribute to an [[html5-vocab]] draft.

=== v2 vocab to-do ===
To do:
* write a simple tutorial for creating/getting started with microformats-2 markup for new content
* examples in each h-* spec listed above of how to embed other microformats in them
* actual profile documents at <nowiki>http://microformats.org/profile/h-*</nowiki> URLs mentioned above.
* Provide any necessary microdata-specific language as needed (e.g. to be comparably understandable to the [http://www.whatwg.org/specs/web-apps/current-work/#vcard sample vCard4/hCard1 microdata vocabulary]. Also provide any necessary RDFa-specific language as needed. Both preferably in a generic vocabulary-independent way.
* write a porting guide mapping v1 property -> v2 property
** use-case: simple search/replace in templates (e.g. in case web author doesn't remember existing microformats vocabs and where they used them).
** advise using *both* in existing templates (e.g. in case some CSS depends on the existing microformats)
* analyzie/document how well the microformats2 model and vocabularies satisfy the [http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-May/019681.html use-cases used to design/create microdata].

== combining microformats ==
Since microformats 2 uses simple flat sets of properties for each microformat, multiple microformats are combined to indicate additional structure.

=== h-event location h-card ===
Events commonly have venue information with additional structure, like address information. For example:

<source lang=html4strict>
<div class="h-event">
<a class="p-name u-url" href="http://indiewebcamp.com/2012">
IndieWebCamp 2012
</a>
from <time class="dt-start">2012-06-30</time>
to <time class="dt-end">2012-07-01</time> at
<span class="p-location h-card">
<a class="p-name p-org u-url" href="http://geoloqi.com/">
Geoloqi
</a>,
<span class="p-street-address">920 SW 3rd Ave. Suite 400</span>,
<span class="p-locality">Portland</span>,
<abbr class="p-region" title="Oregon">OR</abbr>
</span>
</div>
</source>

The nested h-card used to structure the p-location of the h-event is represented as a structured value for "location" in the JSON, which has an additional key, "value" that represents the plain text version parsed from the p-location.

Parsed JSON:
<source lang=javascript>
{
"items": [{
"type": ["h-event"],
"properties": {
"name": ["IndieWebCamp 2012"],
"url": ["http://indiewebcamp.com/2012"],
"start": ["2012-06-30"],
"end": ["2012-07-01"],
"location": [{
"value": "Geoloqi, 920 SW 3rd Ave. Suite 400, Portland, OR",
"type": ["h-card"],
"properties": {
"name": ["Geoloqi"],
"org": ["Geoloqi"],
"url": ["http://geoloqi.com/"],
"street-address": ["920 SW 3rd Ave. Suite 400"],
"locality": ["Portland"],
"region": ["Oregon"]
}
}]
}
}]
}
</source>

Questions:
<div class="discussion">
* Should the nested hCard be present also as a top-level item in the JSON? - [[User:Tantek|Tantek]] 02:02, 19 June 2012 (UTC)
** My current (2012-243) leaning is no. - [[User:Tantek|Tantek]] 18:53, 30 August 2012 (UTC)
** If so, how do we avoid expansion of the JSON geometrically proportional to the depth of microformat nesting? (Or do we not worry about it?)
* Should there be a canonical hierarchical JSON and a canonical flattened JSON? - [[User:Tantek|Tantek]] 02:02, 19 June 2012 (UTC)
** My current (2012-243) leaning is no, we stick with one canonical JSON for uf2 which is hierarchical. - [[User:Tantek|Tantek]] 18:53, 30 August 2012 (UTC)
** If so, should the flattened JSON have references from properties to nested microformats that have been pushed to the top level per flattening? - [[User:Tantek|Tantek]] 02:02, 19 June 2012 (UTC)
*** If so, what convention does/do JSON follow for such synthetic local reference identifiers? - [[User:Tantek|Tantek]] 02:02, 19 June 2012 (UTC)
</div>

Notes:
* The 'location' value reflects the visible text of its element, including spaces and punctuation, as well as the state abbreviation 'OR'. The 'h-card' property values are only what is marked up, and thus include structure values without extra punctuation, and the state takes the expanded form from the <code>title</code> attribute of its <code><abbr></code> element.

=== h-card org h-card ===
People often publish information general to their company rather than specific to them, in which case, they may wish to encapsulate that in separately nested microformat. E.g. here is a simple h-card example with org property:

[http://blog.lizardwrangler.com Mitchell Baker] (Mozilla Foundation)

with source:
<source lang=html4strict>
<div class="h-card">
<a class="p-name u-url"
href="http://blog.lizardwrangler.com/"
>Mitchell Baker</a>
(<span class="p-org">Mozilla Foundation</span>)
</div>
</source>

Parsed JSON:
<source lang=javascript>
{
"items": [{
"type": ["h-card"],
"properties": {
"name": ["Mitchell Baker"],
"url": ["http://blog.lizardwrangler.com/"],
"org": ["Mozilla Foundation"]
}
}]
}
</source>

Sometimes such organization affiliations are hyperlinked to the website of the organization:

[http://blog.lizardwrangler.com Mitchell Baker] ([http://mozilla.org/ Mozilla Foundation])

You can mark that up with a nested h-card:
<source lang=html4strict>
<div class="h-card">
<a class="p-name u-url"
href="http://blog.lizardwrangler.com/"
>Mitchell Baker</a>
(<a class="p-org h-card"
href="http://mozilla.org/"
>Mozilla Foundation</a>)
</div>
</source>

Parsed JSON:
<source lang=javascript>
{
"items": [{
"type": ["h-card"],
"properties": {
"name": ["Mitchell Baker"],
"url": ["http://blog.lizardwrangler.com/"],
"org": [{
"value": "Mozilla Foundation",
"type": ["h-card"],
"properties": {
"name": ["Mozilla Foundation"],
"url": ["http://mozilla.org/"]
}
}]
}
}]
}
</source>

Note: the nested h-card has implied 'name' and 'url' properties, just like any other root-class-name-only h-card on an <code><a href></code> would.

'''FOR PARSERS ONLY:'''

The nested 'h-card' could be marked up as an 'h-org' as well, which adds it to the nested microformat's type array, all as part of the property specified by the 'p-org'.

<source lang=html4strict>
<div class="h-card">
<a class="p-name u-url"
href="http://blog.lizardwrangler.com/"
>Mitchell Baker</a>
(<a class="p-org h-card h-org"
href="http://mozilla.org/"
>Mozilla Foundation</a>)
</div>
</source>

Parsed JSON:
<source lang=javascript>
{
"items": [{
"type": ["h-card"],
"properties": {
"name": ["Mitchell Baker"],
"url": ["http://blog.lizardwrangler.com/"],
"org": [{
"value": "Mozilla Foundation",
"type": ["h-card", "h-org"],
"properties": {
"name": ["Mozilla Foundation"],
"url": ["http://mozilla.org/"]
}
}]
}
}]
}
</source>

'''FOR PARSERS ONLY:'''

Without a property class name like 'p-org' holding all the nested objects together, we need to introduce another array for nested children (similar to the existing DOM element notion of children) of a microformat that are not attached to a specific property:

<source lang=html4strict>
<div class="h-card">
<a class="p-name u-url"
href="http://blog.lizardwrangler.com/"
>Mitchell Baker</a>
(<a class="h-org h-card"
href="http://mozilla.org/"
>Mozilla Foundation</a>)
</div>
</source>

Parsed JSON:
<source lang=javascript>
{
"items": [{
"type": ["h-card"],
"properties": {
"name": ["Mitchell Baker"],
"url": ["http://blog.lizardwrangler.com/"]
},
"children": [{
"type": ["h-card","h-org"],
"properties": {
"name": ["Mozilla Foundation"],
"url": ["http://mozilla.org/"]
}
}]
}]
}
</source>

Since there's no property class name on the element with classes 'h-card' and 'h-org', the microformat representing that element is collected into the children array.

Such a nested microformat implies some relationship (containment, being related), but is not as useful as if the nested microformat was a specific property of its parent.

For this reason it's recommended that authors should not publish nested microformats without a property class name, and instead, when nesting microformats, authors should always specify a property class name (like 'p-org') on the same element as the root class name(s) of the nested microformat(s) (like 'h-card' and/or 'h-org').

'''FOR PARSERS ONLY:'''

Or the nested object could be only marked up with 'h-card'. Source:

<source lang=html4strict>
<div class="h-card">
<a class="p-name u-url"
href="http://blog.lizardwrangler.com/"
>Mitchell Baker</a>
(<a class="h-card"
href="http://mozilla.org/"
>Mozilla Foundation</a>)
</div>
</source>

Parsed JSON:
<source lang=javascript>
{
"items": [{
"type": ["h-card"],
"properties": {
"name": ["Mitchell Baker"],
"url": ["http://blog.lizardwrangler.com/"]
},
"children": [{
"type": ["h-card"],
"properties": {
"name": ["Mozilla Foundation"],
"url": ["http://mozilla.org/"]
}
}]
}]
}
</source>

'''TO DO: Add h-event h-card example and JSON, per real world publishing examples like [http://www.swingtime.co.uk/List/ClSouth.html Swing Time: Classes in Southern England].'''

== authoring ==
=== minimal markup ===
The best way to use microformats-2 is with as little additional markup as possible. This keeps your code cleaner, improves its maintainability, and thus the quality and longevity of your microformats.

One big advantage of microformats-2 over previous microformats (and others) is the ability to add one class name to an existing element to create a structured item.

See the [[microformats-2#simple_microformats_2_examples|simple examples at the top]] for a start, e.g.

Simple hCards work just by adding <code>class="h-card"</code> :
<source lang=html4strict>
<span class="h-card">Frances Berriman</span>

<a class="h-card" href="http://benward.me">Ben Ward</a>

<img class="h-card" alt="Sally Ride"
src="http://upload.wikimedia.org/wikipedia/commons/a/a4/Ride-s.jpg"/>

<a class="h-card" href="http://tantek.com">
<img alt="Tantek Çelik" src="http://ttk.me/logo.jpg"/>
</a>
</source>

* Tip: Inside an open tag, put the <code>class</code> attribute <em>first</em>, then any human text content attributes (e.g. <code>alt</code>), then URL attributes (e.g. <code>href</code> <code>src</code>), and lastly other attributes (e.g. <code>style</code>). Putting the class attribute first ties it closely to the element name/tag itself, makes it more obvious, and thus more likely to be kept up to date.

=== backward compatible ===
If you depend on current microformats [[implementations]], while they're being updated to support [[microformats-2]], you can include both existing microformats and microformats-2 markup.

In short: use both sets of class names simultaneously.

When doing so, use them on the same element, with the microformats-2 class name first, followed immediately by the existing microformats class name.

Here are the microformats-2 hCards from above with current [[hCard]] markup as well, which may require adding a wrapping element (e.g. a <code><span></code>) to separate the root class name element from explicit property class name elements:

<source lang=html4strict>
<span class="h-card vcard">
<span class="p-name fn">Frances Berriman</span>
</span>

<span class="h-card vcard">
<a class="p-name fn u-url url" href="http://benward.me">Ben Ward</a>
</span>

<span class="h-card vcard">
<img class="p-name fn u-photo photo" alt="Sally Ride"
src="http://upload.wikimedia.org/wikipedia/commons/a/a4/Ride-s.jpg"/>
</span>

<span class="h-card vcard">
<a class="u-url url" href="http://tantek.com">
<img class="p-name fn u-photo photo" alt="Tantek Çelik"
src="http://ttk.me/logo.jpg"/>
</a>
</span>
</source>

Tips:
* use the microformats-2 class name first, e.g.
** <code>class="h-card vcard"</code>
** <code>class="u-url url"</code>
* and pair them when using an element for multiple properties, e.g.:
** <code>class="p-name fn u-url url"</code>
** <code>class="p-name fn u-photo photo"</code>
* put microformats classes after classes for CSS (since page authors will likely interact more with their own classes for design than with microformats classes), e.g. as used on individual microformats [[events]] pages:
** <code>class="event-page h-event vevent"</code>

The prefixes (h-, p-, etc.) of microformats2 class names provide easier recognition, and when followed by the similarly named existing class name, they're more easily recognized as related and thus kept together when the markup is maintained over time.

Related FAQ: [[microformats2-faq#when_using_both_h-card_and_vcard_which_should_be_first_and_why|When using both h-card and vcard which should be first and why?]]

== validators ==
microformats2 validators:

{{new}} Test your microformatted web page with:
* https://pin13.net/mf2/

Barnaby Walters has a hosted version of the open source php-mf2 [[parser]] where you can enter your markup into a textarea and see how it's parsed:
* http://waterpigs.co.uk/php-mf2/

See the [[validators]] page for a longer list of validators.

== Examples in the wild ==
Please add new examples in the wild of microformats-2 to the top of this list. When it gets too big we can move it to a separate page like [[microformats-2-examples-in-wild]].

* ...
* David John Mead marks up his profile, blog posts and comments with h-card, h-entry and h-cite on [http://davidjohnmead.com davidjohnmead.com]
* [[User:Brian|Brian Suda]] marks up his blog posts up with h-entry and h-card on [http://optional.is/required/ optional.is]
* Ashton McAllen marks up his blog posts, reposts, comments and likes with h-entry, h-card and h-cite on [http://acegiak.net/ acegiak.net]
* Emma Kuo marks up her blog posts and notes with h-entry and h-card on [http://notenoughneon.com/ notenoughneon.com]
* Scott Jenson marks up his blog posts with h-entry and h-card on [http://jenson.org/ jenson.org]
* Emily McAllen marks up her blog posts with h-entry and h-card on [http://blackwoolholiday.com/ blackwoolholiday.com]
* Ryan Barrett marks up his blog posts, notes, replies and likes with h-entry and h-card on [https://snarfed.org/ snarfed.org]
* Barry Frost marks up his notes with h-entry, h-card and h-cite on [http://barryfrost.com/ barryfrost.com]
* Amber Case marks up her profile, blog posts, replies and notes with h-entry and h-card on [http://caseorganic.com/ caseorganic.com]
* Johannes Ernst marks up his blog posts with h-entry on [http://upon2020.com/blog/ upon2020.com]
* Michiel de Jong marks up his profile and notes with h-entry and h-card on [https://michielbdejong.com/ michielbdejong.com]
* Mike Taylor marks up his profile and blog posts with h-card and h-entry on [https://bear.im/bearlog/ bear.im]
* Erin Jo Ritchey marks up her profile, posts and comments using h-card, h-entry and h-cite with idno on [http://erinjo.is/ erinjo.is]
* Jeena Paradies marks up his profile, blog posts, notes and comments using h-card, h-entry and h-cite on [https://jeena.net/ jeena.net]
* Andy Sylvester marks up his profile, blog posts and comments using h-card and h-entry on [http://andysylvester.com/2014/03/01/howto-setting-up-the-selfoss-feed-reader-with-microformats-support/ andysylvester.com] (note: as of 2014-03-13 using h-entry for comments instead of correct h-cite --[[User:Barnabywalters|bw]] 14:44, 13 March 2014 (UTC))
* Hakan Demir marks up his Coupon and Voucher blog posts with h-entry and h-card on [http://www.gutscheinflagge.de/ gutscheinflagge.de]
* Chloe Weil marks up her blog posts with h-entry on [http://chloeweil.com/blog chloeweil.com]
* Christophe Ducamp marks up his blog posts and profile with h-entry and h-card on [http://christopheducamp.com/ christopheducamp.com]
* Glenn Jones marks up his blog posts, notes, replies, profile and comments with h-entry, h-card and h-cite on [http://glennjones.net/ glennjones.net]
* Marcus Povey marks up his blog posts and profile with h-entry and h-card on [http://www.marcus-povey.co.uk/ marcus-povey.co.uk]
* Eugen Busoiu marks up his web profile with h-card on [http://eugenbusoiu.com/#utm_source=microformats2&utm_medium=h-card&utm_campaign=Microformats eugenbusoiu.com]]
* Matthias Pfefferle marks up his blog posts, comments and profile with h-card, h-cite and h-entry on [http://notizblog.org/ notizblog.org]
* Kyle Mahan marks up his profile and notes with h-card and h-entry on [http://kylewm.com/ kylewm.com]
* Okinawan-lyrics marks up his blog posts with h-entry and h-card ([http://www.okinawan-lyrics.com/ example])
* Emil Björklund marks up his blog posts with h-entry and h-card ([http://thatemil.com/blog/2013/09/16/webmentioning-adactio/ example])
* App.net rolled out support for h-card and h-entry on all profile pages and permalink pages as of 2013-08-06 ([https://alpha.app.net/voidfiles example])
* Brett Comnes marks up his posts with h-entry and h-card ([http://bret.io/2013/06/29/getting-started-with-bower/ example])
* Ben Werdmuller marks up his posts with h-card and h-entry, u-in-reply-to and u-like ([http://werd.io/view/51d5097fbed7ded0633a5956 example])
* Sandeep Shetty marks his posts up with h-card and h-entry, as well as draft u-in-reply-to and experimental u-like properties ([http://sandeep.io/101 example])
* Laurent Eschenauer marks up his posts with h-entry ([http://eschnou.com/entry/first-autonomous-flight-of-my-nodecopter-62-24992.html example])
* Tom Morris marks up his posts using h-entry ([http://tommorris.org/posts/8417 example])
* Sinolandquality marks up some of their content using h-feed and h-entry on [http://www.sinolandquality.com/Blog/?page_id=3516&utm_content=buffere4d40&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer sinolandquality.com]
* [http://www.w3.org/conf/ W3Conf 2013] uses h-event for the main event, and h-card for all the speakers and notable attendees. The h-cards make particularly good use of implied name, url, and photo properties.
* [http://wordpress.org/extend/themes/sempress SemPress] is a WordPress theme that supports h-card, h-feed/h-entry and h-as-*
* [http://the-pastry-box-project.net/ The Pastry Box Project] use h-card and h-entry markup on their homepage and individual thoughts pages
* Tom Morris uses h-card and [[XFN]] to markup [http://tommorris.org/pages/blogroll his blogroll].
* Aaron Parecki uses h-card to markup both authorship and references to people in his notes permalinks, e.g. [http://aaronparecki.com/2012/230/reply/1 2012/230/reply/1].
* [http://tantek.com/ Tantek Çelik] uses h-card, h-event, and h-entry on his home page, as well as h-entry on all post permalinks, e.g. [http://tantek.com/2012/243/t1/name-beats-title-modern-use-dubline-core-wrong-uf2 2012-243 post], with [[rel-prev]]/[[rel-next]] (if applicable) to indicate prev/next posts, and with [[rel-author]] to his home page with canonical hCard to indicate authorship.
* [http://waterpigs.co.uk/ Barnaby Walters] uses h-card on his home page, h-card, h-entry and XFN markup on his [http://waterpigs.co.uk/notes notes page].
** 2013-01-25 Barnaby Walters: <cite>[http://waterpigs.co.uk/articles/experimental-markup Experimental Markup]</cite> - describes how he's using microformats2 vocabularies: <code>h-adr</code>, <code>h-card</code>, <code>h-entry</code>, <code>h-event</code>, <code>h-geo</code>, <code>h-review</code>, and experimental vocabularies: <code>h-feed</code> (embedded for update histories), [[activity-streams]] objects <code>h-as-article</code>, <code>h-as-collection</code>, <code>h-as-note</code>, <code>h-as-update</code>, as well as experimental properties: <code>u-alternate</code> and <code>u-as-downstream-duplicate</code> (links to POSSE copies), and <code>u-in-reply-to</code> (links to content that the posts are in reply to).
* [http://tantek.com/presentations/2012/06/microformats microformats.org at 7 years] presentation with h-event and h-card markup for people and organizations.
* [http://tantek.com/presentations/2012/06/pdf2012-indieweb.html Rise of the Indie Web hCards] (from Personal Democracy Forum 2012 #pdf12 #pdf2012) has [[microformats-2]] h-calendar and h-card markup
* WebMaker by Mozilla has [[microformats-2]] h-calendar and h-card on event search (e.g. [https://webmaker.org/en-US/events/near/?lat=45.5234515&lng=-122.6762071 search near Portland Oregon]) and event pages (e.g. [https://webmaker.org/en-US/events/192f56eb9/ IndieWebCamp 2012]).[https://twitter.com/microformats/status/212207925643587585]
* WebFWD by Mozilla has [[microformats-2]] h-card markup on [https://webfwd.org/about/experts/ experts] and [https://webfwd.org/about/team/ team] pages
* [http://indiewebcamp.com IndieWebCamp] has [[microformats-2]] h-event markup with nested h-cards for the organizers and the location.
* [https://wiki.mozilla.org/Events Mozilla Events] page has [[microformats-2]] h-event markup with attendees marked up with h-card.
* The [http://pdx.esri.com/blog/2013/10/17/introducing-mapattack/ Esri PDX Blog] has h-entry markup on all blog posts (as of 2013-10-19), and h-product markup on [http://pdx.esri.com/projects/terraformer/ project pages]

=== offline ===
* spreadly marks up share permalink pages with h-entry, as well as minimal h-cards and experimental p-like properties ([http://my.spread.ly/share/51d570bc09e9486562000002 example])

== Implementations ==
{{new}} Test your microformatted web page with:
* https://pin13.net/mf2/ (where it says "Microformats Parser")

=== Blogging tools ===
* '''Storytlr''' parses the 'target' from [http://indiewebcamp.com/pingback pingbacks] for [https://github.com/storytlr/storytlr/blob/master/protected/application/public/controllers/PingbackController.php#L63 h-entry with properties and nested h-card] for information to automatically display in the [http://eschnou.com/entry/testing-indieweb-federation-with-waterpigscouk-aaronpareckicom-and--62-24908.html comments section on a post].

=== Converters ===

* '''[https://github.com/snarfed/activitystreams-unofficial activitystreams-unofficial]''' is a library and REST API that converts between silo APIs, [[ActivityStreams]] and [[microformats2]] (all directions). Supported silos include Facebook, Twitter, Instagram and Google+. Users include [http://brid.gy/ Bridgy], [http://reader.kylewm.com/ Woodwind], and [https://facebook-atom.appspot.com/ facebook-atom] and [https://twitter-atom.appspot.com/ twitter-atom], among others.

* '''[http://pipes.yahoo.com/pipes/pipe.info?_id=afc5568b4e8643bfb05436b1caaf91bc microformats to RSS]''' - a Yahoo! pipe that converts a URL containing an [[h-feed]] containing h-entries, into an [[RSS]] feed ([http://waterpigs.co.uk/notes/4SeNi5/ 2013-10-21 blog post announcing])

=== Parsers ===
Parsers, open source libraries:
==== Go ====
* '''andyleap/microformats''' Golang microformats2 parser
** github open source: https://github.com/andyleap/microformats
** live textarea entry: http://mf2.vendaria.net
==== Java ====
* '''mf2j''' An early-stage Java microformats2 parser
* github open source: https://github.com/kylewm/mf2j
* live: https://mf2j.herokuapp.com/?url={http://example.com}

==== Javascript ====
* '''microformat-node''' Node.js microformats2 parser
** github open source: https://github.com/glennjones/microformat-node
** test suite: https://github.com/microformats/tests
** blog post: http://glennjones.net/2013/01/brand-new-microformats-2-parser/
** live: http://glennjones.net/tools/microformats/
* '''microformat-shiv''' - cross browser javascript microformats 2 parser which can also be used in browser extensions.
** http://microformatshiv.com/
** github open source: https://github.com/glennjones/microformat-shiv

==== PHP ====
* '''<span id="php-mf2">php-mf2</span>''' - PHP microformats2 parser
** github open source: https://github.com/indieweb/php-mf2
** Packagist: https://packagist.org/packages/mf2/mf2
** live:
*** textarea entry: http://waterpigs.co.uk/php-mf2/
*** URL entry: https://pin13.net/mf2/
==== Python ====
* ''mf2py'' Python microformats2 parser
** main entry: [[mf2py]]
** github open source: https://github.com/tommorris/mf2py
** live:
*** URL entry: [https://mf2py.herokuapp.com/ mf2py.herokuapp.com]
*** textarea entry: https://kartikprabhu.com/connection/mfparser
*** another textarea: http://www.unmung.com/?html=
*** URL and/or textarea: https://kylewm.com/services/mf2
==== Ruby ====
* '''G5/microformats2''' Ruby microformats2 parser
** github open source: https://github.com/G5/microformats2

== Presentations ==
Presentations about microformats2:
* 2013-01-24 <cite>[http://waterpigs.co.uk/presentations/microformats-2/ Microformats 2]</cite> presentation by [[User:Barnabywalters|Barnaby Walters]] at the [[events/2013-01-24-exeter-web-meetup|Exeter Web Meetup]] in Devon, UK.
* 2012-09-21 <cite>[http://tantek.com/presentations/2012/09/microformats2/ microformats2 & bits of HTML5: The Evolution Of Web Data]</cite> presentation by [[User:Tantek|Tantek Çelik]] ([http://twitter.com/t @t]) at [[events/2012-09-21-refreshlx|RefreshLX]] in Lisbon, Portugal.
* 2012-07-21 <cite>[http://tantek.com/presentations/2012/07/html5-uf2/ HTML5 and microformats2: The Evolution Of Web Data]</cite> presentation by [[User:Tantek|Tantek Çelik]] ([http://twitter.com/t @t]) at [[events/2012-07-21-cascadesf|Innovators of the Web conference]] in San Francisco, CA.
* 2012-07-14 <cite>[http://tantek.com/presentations/2012/07/html5-microformats2/ HTML5 and microformats2: The Evolution Of Web Data]</cite> presentation by [[User:Tantek|Tantek Çelik]] ([http://twitter.com/t @t]) at [[events/2012-07-14-open-web-camp-4|Open Web Camp IV]] in San Jose, CA.

== Testimonials ==
* <blockquote class="twitter-tweet">To prove the web standards community can come up with better standards than the SE’s, compare this: http://microformats.org/wiki/microformats-2 with schema . org — Joost de Valk (@yoast) [https://twitter.com/yoast/status/298907685452124160 2013-02-05 13:35]</blockquote>
* <blockquote class="twitter-tweet">... I’m hoping SE’s will pick up microformats2. It’s SO much cleaner. — Joost de Valk (@yoast) [https://twitter.com/yoast/status/298911287117758464 2013-02-05 13:49]</blockquote>
* <blockquote class="twitter-tweet">... But damn Microformats2 are sexy. — Joost de Valk (@yoast) [https://twitter.com/yoast/status/298912179292344320 2013-02-05 13:53]</blockquote>

== About This Brainstorm ==
The rest of this page is a brainstorm currently written in narrative / exploratory format, that is, acknowledging the success that microformats have had, why so, and then a walk through of known issues with microformats in general along with iteration of ways to address said issues, ending up with the current microformats 2 design as a conclusion.

The proposals build on each other resulting in a solution that addresses the vast majority of general issues. The proposed changes merit a major version number increment, hence microformats 2.

This mathematical proof/derivation style is used to explicitly encourage understanding (and double-checking) of the rational steps taken in the development of microformats 2. Reasons are documented, sometimes along with alternatives considered (and reasons for rejection of those alternatives).

When the microformats 2 brainstorm has evolved sufficiently to demonstrate some degree of stability, usability, and implementability, it will be rewritten in a more declarative specification style, and this narrative/derivation will be archived to a background development page for historical purposes.

— [[User:Tantek|Tantek]]

== Background ==

2004: In early February microformats were introduced as a concept at eTech, and in September [[hCard]] and [[hCalendar]] were proposed at FOO Camp.

2010:
* 34% of webdevs use microformats ([http://www.webdirections.org/sotw10/markup/#semantics 2010 State of Web Development survey])
* 1.88 billion hCards (per [[Yahoo]] SearchMonkey)
* 36 million hCalendar events (ibid)

* XFN -> Social Graph API -> Web as Social Network / Address Book

== Addressing Issues ==
=== AUTHORS and PUBLISHING ===
Authors and publishers are perhaps the most important constituency in the microformats community. There are more of them than there are developers, programmers, parsers, etc. and they're the ones that solved the chicken-egg problem by publishing microformats even before tools were available for consuming them.

Therefore we must first address author/publisher general issues with microformats.

==== can we make the simplest case simpler ====
Issue: '''How can we make it easier for authors to publish microformats?'''

Currently the simplest hCard:
<source lang=html4strict>
<span class="vcard">
<span class="fn">
Chris Messina
</span>
</span>
</source>

requires 2 elements (nested, with perhaps at least one being pre-existing), and 2 class names.

Web authors/designers are used to the simplicity of most HTML tags, e.g. to mark up a heading:

<source lang=html4strict>
<h1>Chris Messina</h1>
</source>

requires just 1 element.

[http://zeldman.com/ Jeffrey Zeldman] pointed out this apparent perceived incremental complexity (2 elements vs 1) during a microformats workshop in 2009 in New York City.

'''How can we make microformats just as easy?'''

'''Proposal: allow root class name only.'''

This would enable:

<source lang=html4strict>
<h1 class="vcard">Chris Messina</h1>
</source>

requiring only 1 class name for the simplest case.

==== renaming for usability ====
Otherwise known as, choosing one form of consistency over another.

'''Can we do even better?'''

One of the most common questions asked about hCard is:

[[hcard-faq#Why_does_hCard_use_vcard_as_the_root_class_name|Why does hCard use vcard as the root class name?]]

This slight inconsistency between the name of the format and the name of the root class name consistently causes confusion in a large percentage of newcomers to microformats.
* See [[issues#hcard-vs-vcard-name]] for details/links.

Though in microformats we believe very strongly in the [[principle]] of [[reuse]], we have to admit that in this case experience/evidence has shown that this may be a case where we re-used something too far beyond it's original meaning. Thus:

'''Proposal: use root class name "hcard" instead of "vcard" for future hCards.'''

This would result in:

<source lang=html4strict>
<h1 class="hcard">Chris Messina</h1>
</source>

making the simple case even simpler:

Just 1 additional class name, named the same as the format you're adding. Think hCard, markup class="hcard".

At a minimum for compatibility we should document that parsers should accept "hcard" as an alternative to "vcard" as the root class name for hCard 1.0, and similarly for hCalendar 1.0: "hcalendar" in addition to "vcalendar", "hevent" in addition to "vevent".

However, for [[microformats-2]] we are going to distinguish root class names further by using an "h-" prefix (e.g. "h-card"). Read on to understand why.

==== simplifying to only needing one element ====
It's very important for the simple case to be as simple as possible, to enable the maximum number of people to get started with minimum effort. (The idea of using a single class name for a microformat was proposed by Ryan Cannon in 2006 specifically [[hcard-implied|for hCard]], and rediscovered by [[User:Tantek|Tantek]] in 2010 and subsequently generalized to all microformats.)

From there on, it's ok to require incremental effort for incremental return.

E.g. to add any additional information about a person, add explicit property names.

'''How does this simple root-only case work?'''

* root class name reflects name of the microformat
* every microformat must require at most 1 property (preferably 0)
** admit that requiring a field in an application just results in noise (the 90210 problem - apps which require zip code get lots of false 90210 entries), and specify that any application use cases which appear to "require" specific properties must instead define how to imply sensible defaults for them.
* when only a root class name is specified, imply the entire text contents of the element as the value of the primary property of the microformat. e.g.
** "hcard" implies "fn"
** hcalendar event - "hevent" - implies "summary"
** "hreview" implies "summary"
** "hentry" implies "entry-summary" (perhaps collapse into "summary" - in practice they're not sufficiently semantically distinct to require separate property names)
** '''OR''' instead of making the one implied property be vocabulary specific, introduce a new generic (applicable to all vocabularies) 'p-name' property (subsuming hCard's 'fn'). See [[microformats-2-brainstorming#further_simplifications|microformats 2 brainstorming: further simplifications]] for latest thoughts along these lines, including the following specific mark-up implied generic properties across all microformats (based on existing published markup use-cases)
*** 'p-name'
*** 'u-url'
*** 'u-photo'

==== flat sets of properties ====
'''What more can we simplify about microformats?'''

Numerous individuals have provided the feedback that whenever there is more than one level of hierarchy in a microformat, many (most?) developers get confused - in particular Kavi Goel of Google / Rich Snippets provided this feedback at a microformats dinner. Thus depending on multiple levels of hierarchy is likely resulting in a loss of authorability, perhaps even accuracy as confusion undoubtedly leads to more errors. Thus:

'''Proposal: simplify all microformats to flat sets of properties. '''

What this means:
* all microformats are simply an object with a set of properties with values.
* no more subproperties- drop the notion of subproperties.
* use composition of multiple microformats for any further hierarchy, e.g. the "location" of an hCalendar event can be an hCard, or the "agent" of one hCard can be another hCard.

For example for hCard this would mean the following specific changes to keep relevant functionality:
* drop "n", promote all "n" subproperties to full properties
** given-name, family-name, additional-name, honorific-prefix, honorific-suffix
* treat "geo" as a nested microformat
* treat "adr" as a nested microformat (what to do about adr's "type"?)
* treat "org" as a flat string and drop "organization-name" and "organization-unit" (in practice rarely used, also not revealed or ignored in contact management user interfaces - e.g. Address Book)

Example: add a middle initial to the previous example Chris Messina's name, and markup each name component:

<source lang=html4strict>
<h1 class="hcard">
<span class="fn">
<span class="given-name">Chris</span>
<abbr class="additional-name">R.</abbr>
<span class="family-name">Messina</span>
</span>
</h1>
</source>

Note:
# use of an explicit span with "fn" to markup his entire formatted name
# use of the abbr element to explicitly indicate the semantic that "R." is merely an abbreviation for his additional-name.

==== distinguishing properties from other classes ====
Current microformats properties re-use generic terms like "summary", "photo", "updated" both for ease of use and understanding.

However, through longer term experience, we've seen sites that accidentally drop (or break) their microformats support (e.g. Upcoming.org, Facebook) because web authors sometimes rewrite all their class names, and either are unaware that microformats were in the page, or couldn't easily distinguish microformats property class names from other site-specific class names.

This issue has been reported by a number of web authors.
* See: [[issues#class-collisions]]

Thus microformats 2 uses ''prefixes'' for property class names, e.g.:
* '''p-summary''' instead of ''summary''
* '''u-photo''' instead of ''photo''
* '''dt-updated''' instead of ''updated''

Such prefixing of all microformats class names was first suggested by Scott Isaacs of Microsoft to Tantek on a visit to Microsoft sometime in 2006/2007, but specifically aimed at making microformats easier to parse. At the time the suggestion was rejected since microformats were focused on web authors rather than parsers.

However, since experience has shown that distinguishing property class names is an issue for '''both web authors and parser developers''', this is a key change that microformats 2 is adopting. See the next section for details.

=== COMMUNITY and TOOLS ===
The second most important constituency in the microformats community are the developers, programmers, tool-makers.

A non-trivial number of them have been sufficiently frustrated with some general issues with microformats that they've done the significant extra work to support very different and less friendly alternatives (microdata, RDFa). Based on this real-world data (market behavior), it behooves us to address these general issues with microformats for this constituency.

==== existing microformats parsing requirements ====
COMMUNITY and TOOLS (that) USE MICROFORMATS
* parser / parsing
* structured
* getting the data out
* json - 1:1 mapping

[[parsing]] microformats currently requires
# a list of root class names of each microformat to be parsed
# a list of properties for each specific microformats, along with knowledge of the type of each property in order to parse their data from potentially different portions of the HTML markup
# some number of format-specific specific rules (markup/content optimizations)

This has meant that whenever a new microformat is drafted/specificied/adopted, parsers need to updated to handle it correctly, at a minimum to parse them when inside other microformats and avoid errantly implying properties from one to the other (containment, [[mfo]] problem).

==== naming conventions for generic parsing ====
I think there is a fairly simple solution to #1 and #2 from the above list, and we can make progress towards minimizing #3. In short:

'''Proposal: a set of naming conventions for microformat root class names and properties that make it obvious when:'''
* a class name represents a microformat root class name
* a class name represents a microformat property name
* a class name represents a microformat property that needs special parsing (specific type of property).

In particular - derived from the real world examples of existing proven microformats (rather than any abstraction of what a schema should have)
* '''"h-*" for root class names''', e.g. "h-card", "h-event", "h-entry"
** The 'h-' prefix is based on the existing microformats naming pattern of starting with 'h'.
* '''"p-*" for simple (text) properties''', e.g. "p-fn", "p-summary"
** vocabulary generic parsing, element text in general, treat certain HTML element/attribute combination as special and use those first, e.g. img/alt, abbr/title.
** The 'p-' prefix is based on the word "property" starting with 'p'.
* '''"u-*" for URL properties''', e.g. "u-url", "u-photo", "u-logo"
** special parsing required: prefer a/href, img/src, object/data etc. attributes to element contents.
** The 'u-' prefix is based on URL/URI starting with the letter 'u', which is the type of most of these related properties.
* '''"dt-*" for datetime properties''', e.g. "dt-start", "dt-end", "dt-bday"
** special parsing required: [[value-class-pattern]], in particular separate date time value parsing for better human readabillity / DRY balance.
** The 'dt-' prefix is based on "date time" having the initials "dt" and the preponderance of existing date time properties starting with "dt", e.g. dtstart, dtend, dtstamp, dtreviewed.
* '''"e-*" for element tree properties''' where the entire contained element hierarchy is the value, e.g. "e-content" (formerly "entry-content") for [[hAtom]]. The 'e-' prefix can also be mnemonically remembered as "element tree", "embedded markup", or "encapsulated markup".
** special parsing required: follow the [http://www.whatwg.org/specs/web-apps/current-work/multipage/the-end.html#serializing-html-fragments HTML spec: Serializing HTML Fragments algorithm] to create a serialization.

This provides a simpler transition/education story for existing microformats authors/publishers:
* "h*" to "h-*", "dt*" to "dt-*", url-like properties to "u-*", entire embedded markup to "e-*", and "p-*" for all "plain text" properties.

See [[microformats-2-prefixes]] for further thoughts and discussions on these and other class prefixes.

Example: taking that simple heading hCard example forward:

<source lang=html4strict>
<h1 class="h-card">Chris Messina</h1>
</source>

As part of microformats 2 we would immediately define root class names and property names for all existing microformats and drafts consistent with this naming convention, and require support thereof from all new implementations, as well as strongly encouraging existing implementations to adopt the simplified microformats 2 syntax and mechanism. Question: which microformats deserve explicit backward compatibility?

As a community we would continue to use the microformats [[process]] both for researching and determining the need for new microformats, and for naming new microformat property names for maximum re-use and interoperability of a shared vocabulary.

If it turns out we need a new property type in the future, we can use one of the remaining single-letter-prefixes to add it to microformats 2. This would require updating of parsers of course, but in practice the number of different types of properties has grown very slowly, and we know from other schema/programming languages that there's always some small limited number of scalar/atomic property types that you need, and using those you can create compound types/objects that represent richer / more complicated types of data. See [[microformats-2-prefixes]] for documentation of existing single-letter class name prefixes in practice.

=== ADVANTAGES ===
This has numerous advantages:
* '''better maintainability''' - much more obvious to web authors/designers/publishers which class names are for/from microformats.
* '''no chance of collision''' - for all practical purposes with existing class names and thus avoiding any need to add more complex CSS style rules to prevent unintended styling effects.
* '''simpler parsing''' - parsers can now do a simple stream-parse (or in-order DOM tree walk) and parse out '''all''' microformat objects, properties, and values, without having to know anything about any specific microformats.
* '''separation of syntax and vocabulary''' - by abstracting microformats 2 syntax independent of any vocabulary, it allows and encourages development of shared vocabularies that can work in alternative syntaxes.

More examples: here is that same heading example with name components:

<source lang=html4strict>
<h1 class="h-card">
<span class="p-fn">
<span class="p-given-name">Chris</span>
<abbr class="p-additional-name">R.</abbr>
<span class="p-family-name">Messina</span>
</span>
</h1>
</source>

with a hyperlink to Chris's URL:

<source lang=html4strict>
<h1 class="h-card">
<a class="p-fn u-url" href="http://factoryjoe.com/">
<span class="p-given-name">Chris</span>
<abbr class="p-additional-name">R.</abbr>
<span class="p-family-name">Messina</span>
</a>
</h1>
</source>

=== COMPATIBILITY ===

microformats 2 is backwards compatible in that in permits content authors to markup with both old and new class names for compatibility with old tools.

Here is a simple example:

<source lang=html4strict>
<h1 class="h-card vcard">
<span class="fn">Chris Messina</span>
</h1>
</source>

a microformats 2 parser would see the class name "h-card" and imply the one required property from the contents, while a microformats 1.0 parser would find the class name "vcard" and then look for the class name "fn". no data duplication is required. this is a very important continuing application of the <abbr title="don't repeat yourself">DRY</abbr> [[principle]].

And the above hyperlinked example with both sets of class names:

<source lang=html4strict>
<h1 class="h-card vcard">
<a class="p-fn u-url n fn url" href="http://factoryjoe.com/">
<span class="p-given-name given-name">Chris</span>
<abbr class="p-additional-name additional-name">R.</abbr>
<span class="p-family-name family-name">Messina</span>
</a>
</h1>
</source>

=== VENDOR EXTENSIONS ===

(this section was only discussed verbally and not written up during discussions - capturing here as it is topical)

Proprietary extensions to formats have typically been shortlived experimental failures with one big recent exception.

Proprietary or experimental CSS3 property implementations have been very successful.

There has been much use of border radius properties and animations/transitions which use CSS properties with vendor-specific prefixes like:

* -moz-border-radius
* -webkit-border-radius

etc.

Note that these are merely string '''prefixes''', not bound to any URL, and thus not namespaces in any practical sense of the word. This is quite an important distinction, as avoiding the need to bind to a URL has made them easier to support and use.

This use of vendor specific CSS properties has in recent years allowed the larger web design/development/implementor communities to experiment and iterate on new CSS features while the features were being developed and standardized.

The benefits have been two-fold:
* designers have been able to make more attractive sites sooner (at least in some browsers)
* features have been market / real-world tested before being fully standardized, thus resulting in better features

Implementers have used/introduced "x-" prefixes for IETF MIME/content-types for experimental content-types, MIME parameter extensions, and HTTP header extensions, per RFC 2045 Section 6.3, RFC 3798 section 3.3, and [https://secure.wikimedia.org/wikipedia/en/wiki/List_of_HTTP_header_fields#Common_non-standard_headers Wikipedia: HTTP header fields - non-standard headers] (could use RFC reference instead) respectively, like:

* application/x-latex (per [https://secure.wikimedia.org/wikipedia/en/wiki/Internet_media_type#Type_x Wikipedia Internet media type: Type x])
* x-spam-score (in email headers)
* X-Pingback (per [http://en.wikipedia.org/wiki/Pingback Wikipedia:Pingback])

Some standard types started as experimental "x-" types, thus demonstrating this experiment first, standardize later approach has worked for at least some cases:

* image/x-png (standardized as image/png, both per [http://tools.ietf.org/html/rfc2083 RFC2083])

There have been times when specific sites have wanted to extend microformats beyond what the set of properties in the microformat, and currently lack any '''experimental''' way to do so - to try and see if a feature (or even a whole format) is interesting in the real world before bothering to pursue researching and walking it through the microformats process. Thus:

'''Proposal:'''
* '*-x-' + '-' + meaningful name for root and property class names
** where "*" indicates the single-character-prefix as defined above
** where "x" indicates a literal 'x' for an experimental extension OR
** OR "x" indicates a vendor prefix (more than one character, e.g. like CSS vendor extension abbreviations, or some stock symbols, avoiding first words/phrases/abbreviations of microformats properties like dt-)
** e.g.
** "h-bigco-one-ring" - a hypothetical "bigco" vendor-specific "one-ring" microformat root class name.
** "p-goog-preptime" - to represent [http://www.google.com/support/webmasters/bin/answer.py?answer=173379 Google's "preptime" property extension] to [[hRecipe]] (aside: "duration" may be another property type to consider separate from "datetime" as it may be subject to different parsing rules.)
** "p-x-prep-time" - a possible experimental property name to be added to hRecipe upon consideration/documentation of real-world usage/uptake.

Background - this proposal is a composition of the following (at least somewhat) successful vendor extension syntaxes
* [http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords CSS 2.1 4.1.2.1 Vendor-specific extensions]
* IETF MIME/content-type "x-*" extensions per RFC 2045 Section 6.3. [http://en.wikipedia.org/wiki/Internet_media_type]
* IETF MIME experimental fields (e.g. x-spam-score)
* HTTP header extensions (e.g. x-pingback)
* note also [http://www.mnot.net/blog/2009/02/18/x- some critical thoughts from mnot]

=== USERS ===
Need more tools and interfaces that:
* publish
* copy/paste
* right-click on a microformat
* share
* search results

discussed some existing like: [[H2VX]] converts hCard to vCard, hCalendar to iCalendar

how would we re-implement Live Clipboard today, making it easier for publishers and developers?

=== SEE ALSO ===
* [[microformats2]]
* [[microformats2-brainstorming]] - moving more experimental / undeveloped / and rejected thoughts ideas here to simplify/progress *this* page further.
* [[microformats2-experimental-properties]] - listing experimental (-x- prefixed) properties and their use
* [[microformats2-prefixes]]
* [[microformats2-faq]]
* [[microformats2-parsing]]
* 2010-05-02 [[events/2010-05-02-microformats-2-0|microformats 2.0 discussion session at FOO East]]

payment-method-examples

2015-06-19T23:18:06Z

TomMorris: syntax error

payment-method-examples

2015-06-19T23:17:51Z

TomMorris: starting page documenting payment method examples

This page exists to document published examples of listing payment methods on websites.

* [https://tfl.gov.uk/fares-and-payments/contactless/what-is-contactless?intcmp=8610 TfL.gov.uk: What is a contactless payment card?]
*: "If your card was issued in the UK on Visa, MasterCard, Maestro or American Express and displays the contactless payment symbol (as shown), you should be able to use it to travel on bus, Tube, tram, DLR, London Overground, TfL Rail and most National Rail services in London."
* [http://help.marksandspencer.com/support/payments-and-offers/options-online Marks and Spencer: How do I pay for my order online?], [http://help.marksandspencer.com/support/payments-and-offers/payment-methods-accepted What payment methods are accepted?]
* [http://www.eurostar.com/uk-en/contact-us/frequently-asked-questions/payment/how-can-i-pay-my-eurostar-ticket Eurostar.com:
How can I pay for my Eurostar ticket?]
*: "Mastercard, Visa, American Express, Maestro (GBP only), Switch (GBP only), Visa Electron(GBP only) and Delta (GBP only) cards."
* [http://www.airfrance.us/US/en/local/resainfovol/achat/moyens-de-paiement.htm Airfrance.us: Which payment methods are accepted on the Air France website?]
*: "We accept American Express, Diners Club, Discover, Mastercard, Visa, and UATP/AirPlus. Electronic debit cards (“e-cartes bleues”) are not accepted."
* Foursquare
*: example - [https://foursquare.com/v/hawksmoor/4e9d32995503b4a7c128d043 Hawksmoor, London] - "Credit Cards: Yes (incl. American Express & MasterCard)"

invisible-data-considered-harmful

2015-06-16T09:45:09Z

TomMorris: /* invisible metadata failures */ PERSONDATA has been deprecated! Hallelujah!

<entry-title>invisible data considered harmful</entry-title>

'''This article is a stub.'''

Invisible data or metadata for that matter is undesirable. The general problem with invisible data is that being invisible, nobody sees when it's wrong. If something is wrong on a web page and it's visible, a visitor can see it, a page author (without technical abilities) can see it. Invisible data doesn't get seen and errors inside it are not found as easily as visible data is.

See [http://tantek.com/log/2005/06.html#d03t2359 Principles of visibility and human friendliness].

Also known as, "dark data", "meta tags", "side files".

== invisible metadata failures ==
* meta keywords
** popular in the 1990s, eventually spammed, and rotten, ignored by Google, Yahoo, and other search engines.

* meta ICBM
** people move, don't bother to update their meta ICBM
** people get it wrong (because it's not obviously visible)
*** swapping lat and long
*** "correcting" negative values to positive (or vice versa)
*** note clusters of sites in the middle of oceans or other open spaces that correlate with inverse (or negated) coordinates of actual cities

* lang="en"
** lots of templates, CMS's shipped with this default
** people used them worldwide
** now lang="en" is effectively meaningless/untrustworthy since tons of non-en sites all have it (from abovementioned templates etc.)

* unintentional privacy violations through EXIF data
** See [http://privacypatterns.org/patterns/Strip-invisible-metadata privacypatterns.org: Strip invisible metadata]
** A number of people have unintentionally released their geolocation through its inclusion in EXIF data attached to photographs uploaded to social networking sites like Twitter. Twitter now strip EXIF data and Flickr allow users to remove EXIF data if needed.

* Wikipedia's [https://en.wikipedia.org/wiki/Wikipedia:Persondata persondata] template
** Contains invisible data. Not necessarily updated when someone dies or when errors are found.
** [https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28proposals%29/Archive_122#RfC:_Should_Persondata_template_be_deprecated_and_methodically_removed_from_articles.3F Deprecated on 2015-05-26].

== related ==
* [[namespaces-considered-harmful]]
* [[namespaced-attributes-considered-harmful]]
* [[principles]]
* [http://en.wikipedia.org/wiki/Don%C2%B4t_repeat_yourself The "DRY" principle]

admin-to-do

2015-06-15T12:41:37Z

TomMorris: /* wiki problems */ bumping

<entry-title>admin to-do</entry-title>
Filtered and processed [[to-do]] items specifically for [[admins]].

Only [[admins]] should edit this page with non-minor edits.

Please add to-do suggestions for admins to the general [[to-do#Admins|to-do page's Admins section]]. Thanks!

Items here may list who originally suggested the item on the [[to-do]] page.

Related: [[admin-how-to]].

== inbox ==
Per GTD, here are inbox items that seem reasonable and thus have been moved here by admins from the [[to-do#Admins|to-do page's Admins section]].

Main site home page:
* The microformats2 page, should also be referred from the main page of the website http://microformats.org/ like perhaps a new small right box in between "What are microformats?" and "Microformat specifications" saying something like "Microformat version" as a title and place both versions, the old one is the latest with a short description, and the new one should be imediately under the title, with the same description below.
** +1 agreed. We need a home page redesign with at least this, maybe also @microformats tweets. [[User:Tantek|Tantek]] 13:32, 15 September 2013 (UTC)

ex: [http://screencast.com/t/77YHGASumqm Homepage with the right box implemented] .

Wiki area suggestion:
*Wiki creates duplicate content by allowing duplicate pages for microformats2: the main one is http://microformats.org/wiki/microformats2 and the other one is http://microformats.org/wiki/microformats-2 .

To eliminate this problem, the 2nd page http://microformats.org/wiki/microformats-2, in the <head> section of the source code, should contain the following line <link rel="canonical" href="http://microformats.org/wiki/microformats2" />. This will tell Search Engines that this page is a duplicate content, thus it won't be indexed.

This implementation should be done on all other duplicate content pages of the website.

* This sounds like a good request. Is there a MediaWiki extension/plugin for adding rel=canonical to redirect handling pages? - [[User:Tantek|Tantek]] 13:32, 15 September 2013 (UTC)

Mirror server requests:
* Note that requests from 88.190.13.197 are for a mirror server run by [[User:Neuro|neuro]] at 88.190.224.126.
* ...

== next actions and projects ==
Per GTD, here are processed next-actions for admins, grouped by area/project

* [[events/2008-03-10-sxsw-admins-meetup#next_actions|next-actions from 2008-03-10 sxsw admins meetup]]
** noted here for tracking purposes.
*** This was a very long time ago - we need to reprocess this item to see what is still relevant >5 years later! - [[User:Tantek|Tantek]] 13:33, 15 September 2013 (UTC)

=== web server ===
* redirect www.microformats.* to canonical microformats.org URLs.
* Investigate an upgrade of PHP from 5.2.

=== irc ===
* Pibb integration for the #microformats IRC channel. It is relatively simple to [http://janrain.com/blog/2007/08/08/how-to-embed-pibb/ embed the Pibb chat widget] into a webpage that bridges to the #microformats IRC channel. This would allow for greater access and transparency to the IRC discussions as well as allow people to participate using only their web browser. [[User:Chris_Messina]] 16:50, 31 Aug 2007 (PDT)

* maintainer for [[mfbot]]. Ryan King has indicated that he no longer has time to maintain [[mfbot]] and would like another admin to pick up the maintenance and running of mfbot.

=== wiki ===
==== for site update to microformats2 ====
* about
** create [[about]] from updated version of http://microformats.org/about
** change "about" link to /wiki/about

* get-started
** update [[get-started]] with info from http://microformats.org/2014/03/05/getting-started-with-microformats2

==== wiki problems ====
Problems with the microformats wiki that an admin needs to look at and resolve:

* MediaWiki needs updating
** Last time update attempt broke the theme, didn't have time time debug and fix. - [[User:BenWard]]

* http://microformats.org/wiki/Special:Version looks weird
** suggested culprit from cweiske: https://github.com/microformats/mediawiki-entry-title-override (so maybe that needs debugging in this case?)
** suggested troubleshooting from Tom Morris:
*** do a diff between microformats.org wiki and the old version of MW
*** see what's different between the two, then we can see what the likely cause of the problems are
*** perhaps document differences on our [[mediawiki customization]] page for future better troubleshooting

* Password reset page doesn't work:
** http://microformats.org/wiki/Special:PasswordReset
** as of 2015-06-15, this is still a problem and is now affecting users. [http://logs.glob.uno/?c=freenode%23microformats&s=15+Jun+2015&e=15+Jun+2015#c81446 relevant irc log]

==== wiki documentation ====
Need more documentation about how we have the wiki setup, so more [[admins]] are able to fix/update it.
* Update our [[mediawiki customization]] documentation with specifically:
** What plug-ins/add-ons are installed?
** What customizations / patches have been made to MediaWiki?
** What special things does the microformats mediawiki theme depend on?
** [[User:BenWard]] likely best knows these things.

==== wiki feature requests ====
===== spam fighting =====
* Install [https://www.mediawiki.org/wiki/Extension:AbuseFilter AbuseFilter]. This would allow admins to set up custom rules (similar to email rules like in Outlook/Thunderbird/Gmail etc.) that could be adapted to current spam on-the-fly.
* Install [http://www.mediawiki.org/wiki/Extension:TitleBlacklist TitleBlackList Extension] and then block creation of pages with "http:" or ".com" in the title to stop spammers from creating autolinks in the IRC logs of wiki edits.
* Consider additional mediawiki.org anti-spam strategies: https://www.mediawiki.org/wiki/Manual:Combating_spam (from Tom Morris)
** also: add reCAPTCHA setting for ConfirmEdit and SimpleAntiSpam (GPHemsley added them to the WAHTWG wiki on 2012-296)

===== semantic requests =====
* Try adding https://github.com/microformats/LinkAttributes to our wiki install to permit rel and class on links in wiki pages.
* Add Extensions - especially those that help implement more microformats on the wiki itself!
** Evaluate against Wikipedia's [http://en.wikipedia.org/wiki/Special:Version Version Page] for a list of currently installed extensions on the English Wikipedia.
** I'd personally advise getting [http://www.mediawiki.org/wiki/Extension:Cite Cite], [http://meta.wikimedia.org/wiki/ParserFunctions ParserFunctions] --[[User:JimboJW|JimboJW]] 13:38, 25 Sep 2007 (PDT) (Syntax Highlighting is done in Wiki 2.0)
** [http://www.mediawiki.org/wiki/Extension:HTML_Profiles HTML Profiles] - allows people editing the wiki to add URIs to <code><head profile></code> [[User:TobyInk|TobyInk]] 16:52, 9 March 2009 (UTC)
*** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)
** [http://www.mediawiki.org/wiki/Extension:Link_Attributes Link Attributes] - allows easy-ish setting of rel/rev/class attributes on links. [[User:TobyInk|TobyInk]] 16:52, 9 March 2009 (UTC)
*** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)
* add a class, <code>noprint</code> to the site's CSS, so that sections (such as "related pages" footers) can be made non- printing.
** ‘noprint’ isn't so semantic, but we should get a proper print stylesheet, for sure.
* Allow <kbd>webcal://</kbd>, <kbd>javascript:</kbd> (for posting [[favelets]]/bookmarklets on the wiki) and perhaps (other) x-protocols to be linkified
** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)
* Would be great to have a video template that embeds an object. [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)
* Can we imply <code>entry-title</code> from <code>h1</code>? [[User:Tantek|Tantek]]

===== misc requests =====
* Set up a cron job to export the wiki database (without user details), and make it available in a public location.
* Install creation template extension(s)(see: http://meta.wikimedia.org/wiki/Inputbox or http://www.mediawiki.org/wiki/Extension:CreateBox or http://www.mediawiki.org/wiki/Extension:CreateArticle) [[User:RobManson]] 14:00, 20 Jul 2007 (AEST)
* Add admins sidebar (quick ban list access)
* Do something to allow easy copying of sample input (e.g. add ‘Copy’ UI, or abuse <code>input</code> element
* Fix MediaWiki to lowercase URLs — especially fragment identifiers generated from headings. Content ''should not'' be sub-optimally edited according to the requirements of the CMS.
* Update the interwiki-links table to allow for sensible linking to other wikis doing similar work. See [https://www.mediawiki.org/wiki/Manual:Interwiki help page on mediawiki.org] and [http://microformats.org/wiki/api.php?action=query&meta=siteinfo&siprop=interwikimap current interwikimap as XML from MediWiki API].
** some plausible interwiki links: Wikipedia and other Wikimedia sites, IndieWebCamp, W3C Wiki, WHATWG wiki.

=== forum ===
In the past there have been requests (e.g. on the lists) for an online forum for microformats discussions.

If there is an admin who's interested in helping run a forum (has the time to community manage it), take a look at:

* consider create a new forum on microformats.org
** e.g. install http://vanillaforums.org/ (Geoloqi uses it successfully on https://community.geoloqi.com/ and highly recommends it)

== ongoing ==
Ongoing and as neeeded duties/tasks:

* Delete spam and block spammers from the wiki.
* Send emails to the microformats list(s) guiding the community per our [[mailing-lists]] guidelines.
* Helped out with questions on [[IRC]]
* Accepted / filtered comments on the blog (or posted!)
* Help with web server matintenence:
** Apache (reboot Apache if it hangs, debug Apache server problems)
** WordPress (including upgrading installs as needed)
** Mailman (clearing of internal spam queues)
** MediaWiki (upgrades, help package mods for resubmission back to core)
* Provide guidance to other admins
* Remove [http://microformats.org/wiki?title=Special:Whatlinkshere&target=delete pages awaiting deletion]

== waiting for ==
Per GTD, here are next-actions for admins that are awaiting some external dependency.

Waiting-for: a decent OpenID user experience for the OpenID MediaWiki plugin, in order to:
* install and make available OpenID login, on behalf of a requests a while ago from [[User:DanC]] and [[User:Chris_Messina]] (especially for comments in WordPress). [[User:Chris_Messina]] 16:50, 31 Aug 2007 (PDT)
** The plug-in is installed, but the user experience of exposing it to commenting visitors is poor. There's no other registration function, so it's not being pushed for the time being.
*** Regarding OpenID Log-in. Needs lightweight extension. Current extension turns the wiki into an OpenID *provider*. DO NOT WANT. Anyone want to write a simple OpenID login extension for MediaWiki?
**** You could always install the OpenID extension and then use Apache to block access to ''Special:OpenIDServer''.

== someday maybe ==
Per GTD, here are parked and otherwise deemed low-priority next-actions and projects for admins.

=== someday actions ===
* Make the edit comment UI better — textarea, not single line box. (Dev Status: Might be impossible without hacking the core)

=== someday maybe projects ===
==== improved issue tracking ====
<div class="discussion">
Issue tracking at microformats.org is poor. The wiki is difficult to track, resolutions get lost. A proper bug tracking system is desirable: However, the adminstration overhead of our current infrastructure is too high for volunteers. Questionable whether maintain another custom install of something is the direct we want to move in.
* I don't think this is worth pursuing - issue tracking systems are notoriously problematic, and at least with the wiki, editing/resolving many issues at once is far more efficient - and efficiency for microformats maintainers is an important priority since all this work is all-volunteer. [[User:Tantek|Tantek]] 02:38, 10 September 2009 (UTC)
* I think there are a few benefits to having a tracker. The primary one is simply to track proposals and have an easy platform for people to suggest new ones. That way there is a decent place for a high-level overview of what is going on. But, all of the suggested solutions suck. If it is to be done, we should investigate a custom built tracker for our needs. [[User:Garbee|Garbee]] 00:43, 3 June 2013 (UTC)
</div>

* Investigate possibility/santity of using Launchpad/Github/Google Code for spec issue tracking
* Wiki is excellent documentation tool. Terrible issue tracking tool.
* External services avoid large maintenance burden
* Could better handle this todo list
* Better handle issue resolutions
* Better handle issue discussions

* Evaluate options
** Consider integration points with µf.org
** Consider open standards a plus (OpenID)
** Consider effort in porting existing content
* Copy over issues from each wiki page as standalone bugs
* Ensure that each spec editor is added with suitable authorities to manage issues

=====Custom Install of Trac=====
* + Reliable
* + Well Established
* + Can customise to look like µf.org
* + Flexible milestones etc.
* + Hook into source repository of our choosing
* + OpenID support
* + Support whatever licensing we like
* - Administration overhead

Need to check permissions structures. Can the hCard editor have control over /hcard, but not over /haudio? Do we care?

=====Google Code=====
Chris Messina has ‘microformats’ on Google Code

* + Reliably Hosted, minimal admin overhead
* + Very flexible milestones/tagging
* + SVN repository for test cases, libraries
* - Can't be styled to µf.org
* - No OpenID
* - Ugly as sin
* - No Public Domain license support

=====Launchpad=====
Ben Ward has ‘microformats’ on Launchpad

* + BZR repository for test cases, libraries
* + Public Domain License Support
* - Not instantly intuitive
* - Seems better suited to software than specifications
* - Can't style like µf.org, but, quite pretty
* - No OpenID

=====Github=====
* + Git repository for test cases, libraries
* - Issue tracking is external (Lighthouse)
* - No OpenID

== related ==
* [[to-do]]
* [[admins]]
* [[admin-how-to]]

microformats2-parsing-rdf

2015-05-31T17:17:27Z

TomMorris: Changed protection level for "microformats2-parsing-rdf": changed protection so elf can edit [move=sysop]

Draft Microformats2-to-RDF mapping

Tantek asked me to draft up a Microformats2-to-RDF mapping. It's pretty straightforward to do. This is rough and will need cleaning up.

== RDF model ==

In the document below, the RDF model is represented using the [https://en.wikipedia.org/wiki/Notation3 Notation3] syntax.

All RDF examples presume at least these basic external prefixes:

<source lang="text">
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
</source>

In addition, we shall use the profile defined on [[microformats-2]] as an RDF URI prefix:

<source lang="text">
@prefix uf: <http://microformats.org/profile/> .
</source>

== What is the subject? ==

In RDF, all data is in the form of subject, predicate, object triples. These map roughly to English statements. Subjects can be either URI references or blank nodes.

Mapping these adequately is problematic.

If the element which has the root class name for a microformats2 object also has an about attribute, that SHOULD be used to set the subject for the microformat.

If the element does not have an <code>'''about'''</code> attribute, or the HTML processor does not support parsing <code>'''about'''</code> attributes, then the subject for the microformat should be an RDF blank node.

If a parser is also parsing [[rdfa|RDFa]], it should use the same blank nodes as the subjects for microformats2 objects as it does for statements expressed in RDFa. Given this HTML:

<source lang="html4strict">
<div class="h-card p-name" typeof="foaf:Person" property="foaf:name">Tom Morris</div>
</source>

A microformats2 and RDFa-aware processor should produce Notation3 output with a singular blank node:

<source lang="text">
_:a a uf:h-card, foaf:Person;
foaf:name "Tom Morris";
uf:p-name "Tom Morris";
rdfs:label "Tom Morris" .
</source>

It should not separate out these two resources into separate blank nodes:

<source lang="text">
_:a a uf:h-card;
uf:p-name "Tom Morris";
rdfs:label "Tom Morris" .

_:b a foaf:Person;
foaf:name "Tom Morris" .
</source>

== Representing root class names ==

Root class names map neatly to <code>'''rdf:type'''</code>. In Notation3, this is represented with the shorthand <code>'''a'''</code>.

<source lang="html4strict">
<div class="h-card">Tom Morris</div>
</source>

<source lang="text">
_:bnode01 a uf:h-card .
</source>

This is compatible with the RDF specification, but differs from RDF best practice. As with Java and most programming languages, in RDF, it is customary to capitalize class names.

== Representing properties ==

Once we have inferred the class name, we need simply declare the properties.

For each <code>'''p-'''</code> prefixed property, an RDF statement should be produced with the subject being that of the microformats2 object, the property being the namespaced microformats property, and the object being either a plain literal or a language literal containing the string representation of the object (see language section below). This should be equal to the string value in the JSON output.

=== Multiple properties ===
If there are multiple instances of a property, this should result in multiple statements using the same property name.

This example hCard contains two category properties and two URL properties:

<source lang="html4strict">
<div class="h-card">
<img class="u-photo" alt="photo of Mitchell"
src="https://webfwd.org/content/about-experts/300.mitchellbaker/mentor_mbaker.jpg"/>
<a class="p-name u-url"
href="http://blog.lizardwrangler.com/"
>Mitchell Baker</a>
(<a class="u-url"
href="https://twitter.com/MitchellBaker"
>@MitchellBaker</a>)
<span class="p-org">Mozilla Foundation</span>
<p class="p-note">
Mitchell is responsible for setting the direction and scope of the Mozilla Foundation and its activities.
</p>
<span class="p-category">Strategy</span>
<span class="p-category">Leadership</span>
</div>
</source>

<source lang="text">
_:lizardwrangler a uf:h-card;
uf:u-photo <https://webfwd.org/content/about-experts/300.mitchellbaker/mentor_mbaker.jpg>;
uf:p-name "Mitchell Baker";
rdfs:label "Mitchell Baker";
uf:u-url <http://blog.lizardwrangler.com>;
uf:u-url <https://twitter.com/MitchellBaker>;
uf:p-org "Mozilla Foundation";
uf:p-note "Mitchell is responsible for setting the direction and scope of the Mozilla Foundation and its activities.";
uf:p-category "Strategy";
uf:p-category "Leadership" .
</source>

(In Notation3, it is possible to use commas as a shorthand form to represent multiple statements. This has been avoided in order to better illustrate the point in question.)

To convert from RDF to JSON, one should take all statements that have the same subject and property and group them together into an array.

=== Language ===
RDF allows three types of literal: plain literals, language literals and typed literals.

Typed literals contain a datatype annotation, language literals contain a language annotation (the same ISO country codes as is used in HTML's <code>'''lang'''</code> attribute and XML's <code>'''xml:lang'''</code> attribute).

Processors should work out the language tag (if any) of the elements containing microformat properties (using the latest RDFa specification) and emit language-tagged literals for p- prefixed properties. If no language tag is set in the HTML, emit plain literals for all p- prefixed properties.

For instance:

<source lang="html4strict">
<div class="h-card p-name" lang="ja">内閣総理大臣</div>

<div class="h-card p-name" lang="he">בִּנְיָמִין נְתַנְיָהוּ</div>
</source>

<source lang="text">
_:a a uf:h-card;
uf:p-name "内閣総理大臣"@ja .

_:b a uf:h-card;
uf:p-name "בִּנְיָמִין נְתַנְיָהוּ"@he .
</source>

=== rdfs:label ===
It is generally good practice for each resource to have an rdfs:label property. This maps to p-name.

Using Notation3 rules syntax:

<source lang="text">
@prefix log: <http://www.w3.org/2000/10/swap/log#> .
@forall ?s ?o .
{ :s uf:p-name :o . } log:implies { :s rdfs:label :o . } .
</source>

It is arguable that one may wish to then omit the p-name property from RDF representations of Microformats2 objects. The minor cost of extra duplication is outweighed by ensuring faithful representation and the ability to bidirectionally convert from RDF representations and JSON representations of Microformats2 objects.

== Representing nested microformats ==

This is easy. Each new object becomes a new RDF resource, and there is a relationship going from the parent object to the child object.

<source lang="html4strict">
<div class="h-event">
<a class="p-name u-url" href="http://indiewebcamp.com/2012">
IndieWebCamp 2012
</a>
from <time class="dt-start">2012-06-30</time>
to <time class="dt-end">2012-07-01</time> at
<span class="p-location h-card">
<a class="p-name p-org u-url" href="http://geoloqi.com/">
Geoloqi
</a>,
<span class="p-street-address">920 SW 3rd Ave. Suite 400</span>,
<span class="p-locality">Portland</span>,
<abbr class="p-region" title="Oregon">OR</abbr>
</span>
</div>
</source>

In Notation3, this would emit:

<source lang="text">
_:hevent1 a uf:h-event;
rdfs:label "IndieWebCamp 2012";
uf:p-name "IndieWebCamp 2012";
uf:u-url <http://indiewebcamp.com/2012>;
uf:dt-start "2012-06-30"^^xsd:date;
uf:dt-end "2012-07-01"^^xsd:date;
uf:location [
a uf:h-card;
rdfs:label "Geoloqi";
uf:p-name "Geoloqi";
uf:p-org "Geoloqi";
uf:u-url <http://geoloqi.com/>;
uf:p-street-address "920 SW 3rd Ave. Suite 400";
uf:p-locality "Portland";
uf:p-region "Oregon" .
].
</source>

== Mapping ==
:''See also'': [[microformats2-rdf-mapping]]

The RDF semantics of an hCard can be declared as an RDF document available from microformats.org. This can be used by RDF-minded parsers to draw inferences. In the case of hCard...

<source lang="text">
uf:h-card a owl:Class;
owl:sameAs <http://www.w3.org/2006/vcard/ns#VCard> .
</source>

Equivalent properties can also be declared:

<source lang="text">
uf:p-phone a owl:DatatypeProperty;
owl:sameAs <http://xmlns.com/foaf/0.1/phone>;
<http://schema.org/telephone> .
</source>

== Advanced: parsing microformats in context ==
=== Representative hCard parsing ===
:''See also:'' [[representative-hcard-parsing#representative_hCard_algorithm|representative hCard algorithm]], which operates on an already parsed data model, and thus works the same way.

If the parser is able to infer that a representative hCard is present on the page, one can represent this by using <var>foaf:primaryTopic</var> from the [http://xmlns.com/foaf/spec/#term_primaryTopic FOAF specification].

<source lang="text">
<> foaf:primaryTopic _:a .

_:a a uf:h-card;
uf:p-name "Tom Morris" .
</source>

neaby-metro-station

2015-05-13T06:56:28Z

TomMorris: adding Wikipedia example

This page is to document websites and offline material that provides information about the closeness to train, metro, tram or other transport station data on pages.

== Rationale ==

In London, people commonly refer to an area by the London Underground station closest to it and that station name often becomes a shorthand for the area near it. For example, the area around King's Cross station is commonly referred to as "King's Cross" rather than its older, pre-railway name, Somers Town.

Some London area names are not widely known: Nine Elms is close to Vauxhall station but if one wished to provide directions to that area, simply stating it is "near Vauxhall" is more instructive for most people.

Obviously, directing people to a nearby station serves a practical purpose - enabling people to get to a location via public transport.

Why not just take the geo coordinates of a location and then (using data from a service like OpenStreetMap, perhaps) find the nearest train station? Simply working out as the crow flies where the nearest station is won't necessarily help. Sometimes a station might be a short distance further but provide more reliable or frequent connections. Sometimes the walk to a closer station might take longer for pedestrians because of a complex road system and having to make lots of crossings. Perhaps a natural feature like a river is in the way.

== Examples ==

=== Web ===

* [http://www.beerintheevening.com/ Beer in the Evening]: [http://www.beerintheevening.com/pubs/s/14/14594/Royal_Vauxhall_Tavern/Vauxhall example listing], shows distance from nearby London Underground and National Rail stations
* [http://www.rightmove.co.uk/ Rightmove]: [http://www.rightmove.co.uk/property-to-rent/property-51986918.html example listing], shows distance to 3 nearest London Underground/Overground and National Rail stations
* Wikipedia: "Nearby transit access" - e.g. [https://en.wikipedia.org/wiki/Chisenhale_Gallery Chisenhale Gallery, London]
* ...feel free to add more...

=== Print ===
* ''Frommer's England'' and ''Frommer's London'' travel guidebooks

microformats2-parsing-brainstorming

2015-05-08T00:25:27Z

TomMorris: use cases plz

<entry-title>microformats2 parsing brainstorming</entry-title>

This page is for brainstorming, discussion, and other questions and explorations about [[microformats2]] parsing.

For the microformats2 parsing algorithm, see:
* [[microformats2-parsing]]

__TOC__
== more information for alternates ==
Raised 2015-04-24 by [[User:Kevin Marks|Kevin Marks]]

The existing <code>alternate</code> parsing is omitting <code>title</code> - that should be added. The <code>text</code> would make sense to add here too.

Use-case: labels for presenting alternates

<div class="discussion">
* +1 Makes sense. [[User:Tantek|Tantek]] 03:41, 25 April 2015 (UTC)
</div>

== more information for rel-based formats ==
Raised 2015-04-18 by [[User:Kevin Marks|Kevin Marks]]

Several rel-based formats have additional information that is useful beyond the link itself, which is all we capture at the moment. As I am trying to update the Universal feedparser to support mf2 based I will show examples from the [https://github.com/kevinmarks/feedparser/tree/365623a9470e99246f393a8c1f49a0db567826b8/feedparser/tests/microformats testcases] there.

The main change is to add a <code>rel-urls</code> entry for more information about the attributes and text of the urls pointed to by rel's in the document

A fork of mf2py that implements these changes is at https://github.com/kevinmarks/mf2py
=== rel-tag ===

<code><a rel="tag" href="http://del.icio.us/tag/tech">Technology</a> </code>

currently parses to:

<code>{"rels": {"tag": ["http://del.icio.us/tag/tech"]}, "items": []} </code>

This loses the link text, which is useful as a label.

We add a <code>rel-urls</code> element to the parsed output with this extra data that can be looked up from the rels, which doesn't break backward compatibility and works better with xfn (see below)

<code><pre>
{
"rels": {
"tag": [
"http://del.icio.us/tag/tech"
]
},
"items": [],
"rel-urls": {
"http://del.icio.us/tag/tech": {
"rels": [
"tag"
],
"text": "Technology"
}
}
}
</pre></code>

=== xfn ===

<code><a rel="coworker" href="http://example.com/johndoe">John Doe</a></code>

currently parses to:

<code>{"rels": {"coworker": ["http://example.com/johndoe"]}, "items": []}</code>

This loses the link text, which is the person's name. Suggested output using the urls object:

<code><pre>
{
{
"rels": {
"coworker": [
"http://example.com/johndoe"
]
},
"items": [],
"rel-urls": {
"http://example.com/johndoe": {
"rels": [
"coworker"
],
"text": "John Doe"
}
}
}
</pre></code>

with multiple xfn values

<code><a rel="coworker friend" href="http://example.com/johndoe">John Doe</a></code>
we get this:

<code><pre>
{
"rels": {
"coworker": [
"http://example.com/johndoe"
],
"friend": [
"http://example.com/johndoe"
]
},
"items": [],
"rel-urls": {
"http://example.com/johndoe": {
"rels": [
"coworker",
"friend"
],
"text": "John Doe"
}
}
}
</pre></code>

=== rel-enclosure ===

<code><a rel="enclosure" href="http://example.com/movie.mp4" type="video/mpeg" title="real title">my movie</a></code>

currently parses to:

<code>'{"rels": {"enclosure": ["http://example.com/movie.mp4"]}, "items": []}'</code>

This loses the link text, which is the title and the attributes which give type. Suggested output:

<code><pre>
{
"rels": {
"enclosure": [
"http://example.com/movie.mp4"
]
},
"items": [],
"rel-urls": {
"http://example.com/movie.mp4": {
"rels": [
"enclosure"
],
"text": "my movie",
"type": "video/mpeg",
"title": "real title"
}
}
}
</pre></code>

This generalises to other rel's too, such as [[rel-feed]] and [[rel-alternate]] that have type, lang etc attributes.

(updated to include changes from feedback below) [[User:Kevin Marks|Kevin Marks]] 22:13, 26 April 2015 (UTC)

=== attributes parsed ===
Attributes currently parsed are:
* <code>hreflang</code> for alternate and enclosure
* <code>media</code> for alternate and enclosure
* <code>title</code> for alternate and enclosure
* <code>type</code> for alternate and enclosure

Attributes we may consider parsing if we have a use case are
* <code>sizes</code> for icon - need use-case documentation
* <code>coords</code> for area - possibly for people tagging - no examples yet, and unnecessary as people-tagging requires using h-* microformats
* <code>shape</code> for area - possibly for people tagging - no examples yet, and unnecessary as people-tagging requires using h-* microformats

In addition there is a special attribute <s><code>name</code> </s><code>text</code> which is the text contents of the link, which is useful in rel-tag rel-enclosure and xfn, and in alternate when used for feeds. It's also clarifying for rel-me links.

Tantek [http://logs.glob.uno/?c=freenode%23microformats&s=today#c79057 suggests] we use <code>textContent</code> for this instead, and make it a single string, not a list as <code>name</code> is elsewhere in mf2 parsing

=== feedback on more rel info ===
<div class="discussion">
# "name" is bad because it misleadingly conflates with use of "name" elsewhere in microformats2.
#* Suggested alternative: [https://developer.mozilla.org/en-US/docs/Web/API/Node/textContent textContent] - since that's literally what is being returned there. [[User:Tantek|Tantek]] 02:35, 25 April 2015 (UTC)
#** as all other mf2 keys are lowercase-with-hyphens, [http://logs.glob.uno/?c=freenode%23microformats&s=today#c79101 Tantek suggests] 'text' as that isn't going to be an html [[User:Kevin Marks|Kevin Marks]] 07:28, 25 April 2015 (UTC)
# no need for array for "name"/textContent - since there is always only one at most
#* E.g. should be "textContent": "my movie" [[User:Tantek|Tantek]] 02:35, 25 April 2015 (UTC)
# "urls" key is misleading - implies all URLs in the document, which is neither true, nor desired (takes much more parsing time and work and code)
#* Suggested alternative: "rel-urls". And open to better alternatives too. [[User:Tantek|Tantek]] 02:35, 25 April 2015 (UTC)

</div>

== Nested h-* objects' "value" property ==
Raised 2015-01-06 by [[User:Kylewm]];

If a child element has a microformat (h-*) and is a property element (p-*, u-*, dt-*, e-*), the parser will add a "value" property to the resulting object. The value should attempt to be a useful representation of the object for consumers that do not have semantic knowledge of the particular h-* type. Ref: [[microformats2-parsing#parse_an_element_for_class_microformats]].

To determine the "value", we parse the property element simply (as if it did not have a h-* class), which works well for simple h-* objects, e.g. <code><a class="u-like-of h-cite" href="...">...</a></code>

<div class="discussion">
* To handle more complex microformats, I propose that "value" for a p-* property element take on the first explicit "name" property of the nested microformat, and for a u-* property, the first explicit "url" property. Parsing will fall back on the current rules if an explicit property does not exist.
** This makes sense to me, and fits with the use-cases and examples I've seen. [[User:Tantek|Tantek]] 19:31, 6 January 2015 (UTC)
** A similar (possibly simpler?) formulation would use the implied name and url rules to determine the "value" for p-* and u-* properties respectively
*** I don't think that's needed, as there are already implied rules on a property that should handle that. I'd start with just the "first explicit" scoping to be more conservative, and then see if we find any use-cases that (and existing implied rules) don't/doesn't catch. [[User:Tantek|Tantek]] 19:31, 6 January 2015 (UTC)
**** Agreement at [[2015-01-20]] meetup.
</div>

For example:

<code><pre>
<div class="h-entry">
<div class="u-in-reply-to h-cite">
<a class="p-author h-card" href="http://example.com">Example Author</a>
<a class="p-name u-url" href="http://example.com/post">Example Post</a>
</div>
</div>
</pre></code>

The nested u-in-reply-to object would parse as

<code><pre>
...
"in-reply-to": [{
"type": ["h-cite"],
"properties": {
"name": ["Example Post"],
"url": ["http://example.com/post"],
"author": [{
"type":["h-card"],
"properties": {
"url": ["http://example.com"],
"name": ["Example Author"],
"value": "Example Author"
}
}],
},
"value": "http://example.com/post"
}]
...
</pre></code>

where the outer "value" gets the in-reply-to h-cite's u-url property, and the inner "value" gets the author's p-name property.

<div class="discussion">
* Because there are no implied properties of the dt-* and e-* types, and no obvious defaults, the value rules for these types would not change.
** A possibility for dt-* h-*: The dt-* could take either the first dt-* of the h-*, or (perhaps if no dt-* in the h-*,) the first <code><time></code> element inside. [[User:Tantek|Tantek]] 19:31, 6 January 2015 (UTC)
** First dt-* seems reasonable, predictable, and usable. Consensus at [[2015-01-20]] meetup.
</div>

== Canonicalization of datetime output ==

It would be useful to choose a (more) uniform output format for datetimes to make it easier for users of the parser to consume datetimes. Microformats2 parsers already do sophisticated pattern matching to recognize date vs. time vs. datetimes, so converting this to any specific format should not add overhead.

<div class="discussion">
Specifically:
* Choose either 'T' or space as the date/time separator.
** Prefer space as it is more human friendly/readable, which matters even for syntaxes/formats, as human still develop, debug them. [[User:Tantek|Tantek]] 19:31, 6 January 2015 (UTC)
* Choose either +XXYY or +XX:YY as the timezone specification (and convert 'Z' to +0000).
** Would appreciate some study / input here as to which timezone offset syntax is more human friendly. I lean slightly toward +/-NNNN (without the colon) because in the context of seeing a time, leaving out the colon makes it less likely the offset will be confused for a time. E.g. "07:00-08:00" looks like 7-8am, even if it meant 07:00 in PST. [[User:Tantek|Tantek]] 19:31, 6 January 2015 (UTC)
** Space is fine - consensus [[2015-01-20]] meetup.
* Parsers should ''not'' attempt make datetimes more exact than specified. They should not add time, seconds, or timezone if omitted in the original. [[User:Kylewm|Kylewm]] 04:02, 14 May 2014 (UTC)
** Agreed. [[User:Tantek|Tantek]] 19:31, 6 January 2015 (UTC)
** or month, day per Tom Morris
** consensus [[2015-01-20]] meetup

* Counterpoint: PHP's builtin date parsing does not require strict formatting. And the equivalent functionality for Python is provided by the widely used python-dateutil library. [[User:Kylewm|Kylewm]] 19:02, 14 May 2014 (UTC)
** However we cannot (must not) depend on either PHP or Python's "smart" "fixing" or Postelian "liberal handling", or any other language/framework's for that matter, as they all differ in how "intelligent" they are. [[User:Tantek|Tantek]] 19:31, 6 January 2015 (UTC)
</div>

Perhaps just provide a guideline for these based on the above consensus.

== Add meta http-equiv to microformats2 parsing model ==
Similar to document level parsing of <code>rel</code> attributes, it makes sense simultaneously to parse <code><meta http-equiv></code> elements, perhaps treating "Status" in a special way (only using first number (sequence of digits) for its "value").

Use case: IndieWeb "deleted" indication inline in content for static file services that don't support HTTP return codes.
* http://indiewebcamp.com/deleted#HTML_meta_http-equiv_for_status

HTTP Header example:
* <samp>Content-Type: text/html; charset=utf-8</samp>
HTML equivalent:
* <code><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></code>

Related:
* https://www.w3.org/International/O-HTTP-charset

<div class="discussion">
* Interesting thought. Are you suggesting a top level "http-equivs:" collection similar to "rels:" in the parsed output? Should we consider "metas:" instead or in addition? [[User:Tantek|Tantek]] 19:31, 6 January 2015 (UTC)
* What's the use case for this? Also, http-equiv on its own is useless. http-equiv is only a supplement to the data stored in headers. And headers aren't always there: what happens in the context of someone debugging a page who pastes the source into the textarea of an mf2 parser? Without a compelling use case for including headers (and then over-riding some of them with http-equivs), I'm not sure why an implementor want to do this. —[[User:TomMorris|Tom Morris]] 00:25, 8 May 2015 (UTC)
</div>

E.g. from https://gist.github.com/aaronpk/10297489

<source lang="html4strict">
<meta http-equiv="Status" content="410 GONE"/>
</source>

<source lang="javascript">
{
"items": [],
"rels": {},
"http": {
"status": 410
}
}
</source>

<div class="discussion">
* Maybe make this an optional pass in the parser? - Tom Morris [[2015-01-20]]
* For now, don't bother with metas until someone provides a use-case. Tom Morris
* Agreed on both counts. [[User:Tantek|Tantek]] 06:56, 21 January 2015 (UTC)
</div>

==MIME type==
See [[microformats2-mime-type]]

----

==Other Interpretation Parsing Notes==
Note: most of these need to be written up as separate [[microformats2-parsing-issues]]

Author: [[User:BenWard|Ben Ward]]

[[microformats-2|Microformats 2]] proposes a new, all encompassing syntax modification of [[microformats-2-prefixes|prefixes]] that will allow microformats to be parsed from pages by processors without prior knowledge of a vocabulary. The core components of this model are quite simple, are quite simple to implement, but there are a number of conflicts that emerge with the functionality of existing microformats parsers that need to be handled. This page documents a proposed model to separate these concerns clearly in a way that can be applied to the documentation of generic microformats parsing rules, and the documentation of individual vocabularies.

Collection of other unresolved parsing issues in a generic model:

This is good material for documenting as [[microformats-2-issues]], [[microformats-2-faq]], and perhaps some of the more technical details in [[microformats-2-parsing-faq]].

* The include pattern references other elements from elsewhere in a document. A generic parser needs to track IDs and fill them in after walking the DOM. (also, <code>itemref</code> if adopted.)
** The current thinking per [[microformats-2-brainstorming]] is to adopt <code>itemref</code> and drop the [[include-pattern]]. [[User:Tantek|Tantek]]
* Will <code>itemref</code> always map to an <code>item</code> property name?
** No, <code>itemref</code> maps to one or more elements by ids, and their children. Those referenced elements may have property class names themselves, or they may contain elements that do. [[User:Tantek|Tantek]]
* [[hAtom]] implies <code>author</code> from an hCard in a page that uses an <code>address</code> element. This requires format knowledge, but a generic parser does not currently track the element type of a property node. Should it?
** It should not. element-specific handling (e.g. using "alt" from img, and "title" from abbr) is completely done at parse time. The JSON data model does not reflect which element type or attribute the value came from. Additionally, [[hAtom]] is an example where we created far too many vocabulary-specific rules, in practice they're not necessary, and only complicate the microformat for both publisher understanding and parser implementation. [[User:Tantek|Tantek]]
* [[hAtom]] defines that the highest level heading within an entry implies <code>entry-title</code>. This particular optimisation might be better off dead.
** Agreed, this is gone in microformats 2. [[User:Tantek|Tantek]]
* [[hAtom]] defines that permalinks be parsed from <code>rel</code> attributes, not <code>class</code>
** In practice this has been one of the more problematic/error prone aspects of hAtom implementations, and it's also inconsistent with other microformats (although [[hReview]] tried to use both rel permalinks and "url"). The dependence upon [[rel-bookmark]] for permalinks is dropped in h-atom in preference to re-using "u-url" and "u-uid". [[User:Tantek|Tantek]]
* [[XFN]] is entirely built on <code>rel</code> (although, has various other differences from structural microformats, as do vote-links, so perhaps are excluded from this discussion and will always be handled by dedicated parsers/queries regardless?)
** The best (easiest and most reliable) use of 'rel' microformats in practice is when they are orthogonal to 'class' microformats. This is true both with [[XFN]] and some newer [[existing-rel-values|rel values]] like [[rel-author]]. In addition, it was very clear at the recent [[schema.org]] workshop's syntax session that RDFa's decision to apparently arbitrarily mix use of 'rel' and 'property' attributes for specifying different types of properties (it wasn't clear to people in the room when you use which for what) has caused a high degree of confusion among publishers and thus high error-rates. Thus if anything we should learn from both the mistakes of RDFa and our own experiences with even very deliberate/specific mixing of rel microformats in class microformats, and keep them defined as separate orthogonal building blocks that work together, but don't depend on each other. [[User:Tantek|Tantek]]
*** Relatedly to this: <code>rel-tag</code> in hAtom. --[[User:BenWard|BenWard]] 06:50, 5 October 2011 (UTC)
**** Yes, and two related things here. First, despite my (and others') objection and (past) interoperable post/entry-specific treatment by Technorati and Ice Rocket, Hixie has redefined rel-tag in [[HTML5]] to mean applying to the whole page, not a single post. Second, I've explicitly added 'p-category' to the draft 'h-atom' vocabulary in [[microformats-2]]. [[User:Tantek|Tantek]] 07:12, 5 October 2011 (UTC)
* HTML's <code>time</code> element includes an optional <code>pubdate</code> attribute. Simply: We should parse this as <code>dt-published</code>. --[[User:BenWard|BenWard]] 06:12, 10 October 2011 (UTC)
** *If* there is even some reasonable data on actual use of the "pubdate" attribute (I don't think there is, frankly, especially with the removal of the algorithm to produce Atom from HTML5), then we could consider parsing "pubdate" as backwards compatible option for "dt-published". As a general rule, however, it is bad (demonstrably/experienced) design to depend on additional attributes (c.f. RDFa confusion over "property" vs. "rel"), especially for an instance where no additional attribute is necessary. I would leave this out for now until there is non-trivial (more than just test pages or folks who've written HTML5 books, ahem) use in the wild. When there is such use in the wild, it should be documented on a wiki page. We don't want to encourage more complex (additional attribute) publishing as a result of supporting it. [[User:Tantek|Tantek]] 12:12, 10 October 2011 (UTC)
* [[value-class-pattern]]: In microformats-2, since there are no sub-properties, there will presumably no-longer be a 'value' property in any parsed model. Properties such as 'tel > type' in hCard are, as I recall, deprecated due to underuse anyway, so 'tel > value' becomes redundant. (There's also potentially some clarification around 'price > value' in hListing, whereby value was used in a pattern. So, what does this mean for value class parsing, with regard to value-title patterns and date separation patterns. Are we looking for a 'p-value' and 'p-value-title' classname, but treating them specially (excluding them from regular property parsing.) Or, are we giving them a special prefix (v-text, v-title? That seems confusing, but could be a concept.) I'm fine with p- for both, and just having the parser ignore them since they're special, but need clarification and naming confirmation. --[[User:BenWard|BenWard]] 09:35, 10 October 2011 (UTC)
** A few things:
*** 1. Yes, no more subproperties. 'tel' becomes just 'p-tel'. If there is demand for a structured 'tel' value, then we can use that demand (and research into publishing in practice) to brainstorm and create an 'h-tel' structured telephone number (with perhaps fields like 'type', 'extension', some indication of it being local dialing (an extra 0 in some countries) or international dialing, etc.) Or, we address the different 'tel' types as their own flat properties (again as justified by research), e.g. perhaps 'p-tel-fax', or 'p-tel-mobile'. Something for hcard-2-brainstorming.
*** 2. For prices, e.g. hListing, either we're going to need to encode how to parse monetary amounts including monetary symbols, or consider creating an 'h-price' structured price. Not sure what the right answer is here, again, will need to be informed by analysis of documented actual price publication practices.
*** 3. We should avoid introducing a new prefix 'v-' just for value-class-pattern. As we've noted elsewhere, each new prefix adds complexity and should be avoided without substantial advantage.
*** 4. Using 'p-value-title' is strange, as it would be an exception to 'p-' parsing, since it would get the value from the 'title' attribute whereas 'p-' properties don't normally do that (exception: abbr).
*** 5. Using 'p-value' is also strange, as it wouldn't generate a 'value' property in the JSON data model.
*** 6. Class name 'value-title' is already sufficiently prefixed - we've found or even heard of no collisions in practice.
*** 7. Class name 'value' can, by its simpler naming nature, be expected to potentially collide with other web designer class name usage though we have no documentation/mention thereof. We could consider a renaming, or providing of alternative, such as 'value-string', or 'value-content', etc. However, let's keep that as a backup plan to use only if/when evidence is presented that we need to.
** Conclusions: for now, in microformats-2, keep using 'value' and 'value-title' as defined in the [[value-class-pattern]], and add the additional (obvious) interpretation that [[value-class-pattern#Date_and_time_parsing|value class pattern: date and time parsing]] applies to all 'dt-' properties. - [[User:Tantek|Tantek]] 12:12, 10 October 2011 (UTC)

== see also ==
* [[microformats2]]
* [[microformats2-brainstorming]]
* [[microformats2-prefixes]]
* [[microformats2-faq]]
* [[microformats2-issues]]
* [[microformats2-parsing-faq]]

microformats2-parsing-brainstorming

2015-05-08T00:22:06Z

TomMorris: adding MIME type

<entry-title>microformats2 parsing brainstorming</entry-title>

This page is for brainstorming, discussion, and other questions and explorations about [[microformats2]] parsing.

For the microformats2 parsing algorithm, see:
* [[microformats2-parsing]]

__TOC__
== more information for alternates ==
Raised 2015-04-24 by [[User:Kevin Marks|Kevin Marks]]

The existing <code>alternate</code> parsing is omitting <code>title</code> - that should be added. The <code>text</code> would make sense to add here too.

Use-case: labels for presenting alternates

<div class="discussion">
* +1 Makes sense. [[User:Tantek|Tantek]] 03:41, 25 April 2015 (UTC)
</div>

== more information for rel-based formats ==
Raised 2015-04-18 by [[User:Kevin Marks|Kevin Marks]]

Several rel-based formats have additional information that is useful beyond the link itself, which is all we capture at the moment. As I am trying to update the Universal feedparser to support mf2 based I will show examples from the [https://github.com/kevinmarks/feedparser/tree/365623a9470e99246f393a8c1f49a0db567826b8/feedparser/tests/microformats testcases] there.

The main change is to add a <code>rel-urls</code> entry for more information about the attributes and text of the urls pointed to by rel's in the document

A fork of mf2py that implements these changes is at https://github.com/kevinmarks/mf2py
=== rel-tag ===

<code><a rel="tag" href="http://del.icio.us/tag/tech">Technology</a> </code>

currently parses to:

<code>{"rels": {"tag": ["http://del.icio.us/tag/tech"]}, "items": []} </code>

This loses the link text, which is useful as a label.

We add a <code>rel-urls</code> element to the parsed output with this extra data that can be looked up from the rels, which doesn't break backward compatibility and works better with xfn (see below)

<code><pre>
{
"rels": {
"tag": [
"http://del.icio.us/tag/tech"
]
},
"items": [],
"rel-urls": {
"http://del.icio.us/tag/tech": {
"rels": [
"tag"
],
"text": "Technology"
}
}
}
</pre></code>

=== xfn ===

<code><a rel="coworker" href="http://example.com/johndoe">John Doe</a></code>

currently parses to:

<code>{"rels": {"coworker": ["http://example.com/johndoe"]}, "items": []}</code>

This loses the link text, which is the person's name. Suggested output using the urls object:

<code><pre>
{
{
"rels": {
"coworker": [
"http://example.com/johndoe"
]
},
"items": [],
"rel-urls": {
"http://example.com/johndoe": {
"rels": [
"coworker"
],
"text": "John Doe"
}
}
}
</pre></code>

with multiple xfn values

<code><a rel="coworker friend" href="http://example.com/johndoe">John Doe</a></code>
we get this:

<code><pre>
{
"rels": {
"coworker": [
"http://example.com/johndoe"
],
"friend": [
"http://example.com/johndoe"
]
},
"items": [],
"rel-urls": {
"http://example.com/johndoe": {
"rels": [
"coworker",
"friend"
],
"text": "John Doe"
}
}
}
</pre></code>

=== rel-enclosure ===

<code><a rel="enclosure" href="http://example.com/movie.mp4" type="video/mpeg" title="real title">my movie</a></code>

currently parses to:

<code>'{"rels": {"enclosure": ["http://example.com/movie.mp4"]}, "items": []}'</code>

This loses the link text, which is the title and the attributes which give type. Suggested output:

<code><pre>
{
"rels": {
"enclosure": [
"http://example.com/movie.mp4"
]
},
"items": [],
"rel-urls": {
"http://example.com/movie.mp4": {
"rels": [
"enclosure"
],
"text": "my movie",
"type": "video/mpeg",
"title": "real title"
}
}
}
</pre></code>

This generalises to other rel's too, such as [[rel-feed]] and [[rel-alternate]] that have type, lang etc attributes.

(updated to include changes from feedback below) [[User:Kevin Marks|Kevin Marks]] 22:13, 26 April 2015 (UTC)

=== attributes parsed ===
Attributes currently parsed are:
* <code>hreflang</code> for alternate and enclosure
* <code>media</code> for alternate and enclosure
* <code>title</code> for alternate and enclosure
* <code>type</code> for alternate and enclosure

Attributes we may consider parsing if we have a use case are
* <code>sizes</code> for icon - need use-case documentation
* <code>coords</code> for area - possibly for people tagging - no examples yet, and unnecessary as people-tagging requires using h-* microformats
* <code>shape</code> for area - possibly for people tagging - no examples yet, and unnecessary as people-tagging requires using h-* microformats

In addition there is a special attribute <s><code>name</code> </s><code>text</code> which is the text contents of the link, which is useful in rel-tag rel-enclosure and xfn, and in alternate when used for feeds. It's also clarifying for rel-me links.

Tantek [http://logs.glob.uno/?c=freenode%23microformats&s=today#c79057 suggests] we use <code>textContent</code> for this instead, and make it a single string, not a list as <code>name</code> is elsewhere in mf2 parsing

=== feedback on more rel info ===
<div class="discussion">
# "name" is bad because it misleadingly conflates with use of "name" elsewhere in microformats2.
#* Suggested alternative: [https://developer.mozilla.org/en-US/docs/Web/API/Node/textContent textContent] - since that's literally what is being returned there. [[User:Tantek|Tantek]] 02:35, 25 April 2015 (UTC)
#** as all other mf2 keys are lowercase-with-hyphens, [http://logs.glob.uno/?c=freenode%23microformats&s=today#c79101 Tantek suggests] 'text' as that isn't going to be an html [[User:Kevin Marks|Kevin Marks]] 07:28, 25 April 2015 (UTC)
# no need for array for "name"/textContent - since there is always only one at most
#* E.g. should be "textContent": "my movie" [[User:Tantek|Tantek]] 02:35, 25 April 2015 (UTC)
# "urls" key is misleading - implies all URLs in the document, which is neither true, nor desired (takes much more parsing time and work and code)
#* Suggested alternative: "rel-urls". And open to better alternatives too. [[User:Tantek|Tantek]] 02:35, 25 April 2015 (UTC)

</div>

== Nested h-* objects' "value" property ==
Raised 2015-01-06 by [[User:Kylewm]];

If a child element has a microformat (h-*) and is a property element (p-*, u-*, dt-*, e-*), the parser will add a "value" property to the resulting object. The value should attempt to be a useful representation of the object for consumers that do not have semantic knowledge of the particular h-* type. Ref: [[microformats2-parsing#parse_an_element_for_class_microformats]].

To determine the "value", we parse the property element simply (as if it did not have a h-* class), which works well for simple h-* objects, e.g. <code><a class="u-like-of h-cite" href="...">...</a></code>

<div class="discussion">
* To handle more complex microformats, I propose that "value" for a p-* property element take on the first explicit "name" property of the nested microformat, and for a u-* property, the first explicit "url" property. Parsing will fall back on the current rules if an explicit property does not exist.
** This makes sense to me, and fits with the use-cases and examples I've seen. [[User:Tantek|Tantek]] 19:31, 6 January 2015 (UTC)
** A similar (possibly simpler?) formulation would use the implied name and url rules to determine the "value" for p-* and u-* properties respectively
*** I don't think that's needed, as there are already implied rules on a property that should handle that. I'd start with just the "first explicit" scoping to be more conservative, and then see if we find any use-cases that (and existing implied rules) don't/doesn't catch. [[User:Tantek|Tantek]] 19:31, 6 January 2015 (UTC)
**** Agreement at [[2015-01-20]] meetup.
</div>

For example:

<code><pre>
<div class="h-entry">
<div class="u-in-reply-to h-cite">
<a class="p-author h-card" href="http://example.com">Example Author</a>
<a class="p-name u-url" href="http://example.com/post">Example Post</a>
</div>
</div>
</pre></code>

The nested u-in-reply-to object would parse as

<code><pre>
...
"in-reply-to": [{
"type": ["h-cite"],
"properties": {
"name": ["Example Post"],
"url": ["http://example.com/post"],
"author": [{
"type":["h-card"],
"properties": {
"url": ["http://example.com"],
"name": ["Example Author"],
"value": "Example Author"
}
}],
},
"value": "http://example.com/post"
}]
...
</pre></code>

where the outer "value" gets the in-reply-to h-cite's u-url property, and the inner "value" gets the author's p-name property.

<div class="discussion">
* Because there are no implied properties of the dt-* and e-* types, and no obvious defaults, the value rules for these types would not change.
** A possibility for dt-* h-*: The dt-* could take either the first dt-* of the h-*, or (perhaps if no dt-* in the h-*,) the first <code><time></code> element inside. [[User:Tantek|Tantek]] 19:31, 6 January 2015 (UTC)
** First dt-* seems reasonable, predictable, and usable. Consensus at [[2015-01-20]] meetup.
</div>

== Canonicalization of datetime output ==

It would be useful to choose a (more) uniform output format for datetimes to make it easier for users of the parser to consume datetimes. Microformats2 parsers already do sophisticated pattern matching to recognize date vs. time vs. datetimes, so converting this to any specific format should not add overhead.

<div class="discussion">
Specifically:
* Choose either 'T' or space as the date/time separator.
** Prefer space as it is more human friendly/readable, which matters even for syntaxes/formats, as human still develop, debug them. [[User:Tantek|Tantek]] 19:31, 6 January 2015 (UTC)
* Choose either +XXYY or +XX:YY as the timezone specification (and convert 'Z' to +0000).
** Would appreciate some study / input here as to which timezone offset syntax is more human friendly. I lean slightly toward +/-NNNN (without the colon) because in the context of seeing a time, leaving out the colon makes it less likely the offset will be confused for a time. E.g. "07:00-08:00" looks like 7-8am, even if it meant 07:00 in PST. [[User:Tantek|Tantek]] 19:31, 6 January 2015 (UTC)
** Space is fine - consensus [[2015-01-20]] meetup.
* Parsers should ''not'' attempt make datetimes more exact than specified. They should not add time, seconds, or timezone if omitted in the original. [[User:Kylewm|Kylewm]] 04:02, 14 May 2014 (UTC)
** Agreed. [[User:Tantek|Tantek]] 19:31, 6 January 2015 (UTC)
** or month, day per Tom Morris
** consensus [[2015-01-20]] meetup

* Counterpoint: PHP's builtin date parsing does not require strict formatting. And the equivalent functionality for Python is provided by the widely used python-dateutil library. [[User:Kylewm|Kylewm]] 19:02, 14 May 2014 (UTC)
** However we cannot (must not) depend on either PHP or Python's "smart" "fixing" or Postelian "liberal handling", or any other language/framework's for that matter, as they all differ in how "intelligent" they are. [[User:Tantek|Tantek]] 19:31, 6 January 2015 (UTC)
</div>

Perhaps just provide a guideline for these based on the above consensus.

== Add meta http-equiv to microformats2 parsing model ==
Similar to document level parsing of <code>rel</code> attributes, it makes sense simultaneously to parse <code><meta http-equiv></code> elements, perhaps treating "Status" in a special way (only using first number (sequence of digits) for its "value").

Use case: IndieWeb "deleted" indication inline in content for static file services that don't support HTTP return codes.
* http://indiewebcamp.com/deleted#HTML_meta_http-equiv_for_status

HTTP Header example:
* <samp>Content-Type: text/html; charset=utf-8</samp>
HTML equivalent:
* <code><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></code>

Related:
* https://www.w3.org/International/O-HTTP-charset

<div class="discussion">
* Interesting thought. Are you suggesting a top level "http-equivs:" collection similar to "rels:" in the parsed output? Should we consider "metas:" instead or in addition? [[User:Tantek|Tantek]] 19:31, 6 January 2015 (UTC)
</div>

E.g. from https://gist.github.com/aaronpk/10297489

<source lang="html4strict">
<meta http-equiv="Status" content="410 GONE"/>
</source>

<source lang="javascript">
{
"items": [],
"rels": {},
"http": {
"status": 410
}
}
</source>

<div class="discussion">
* Maybe make this an optional pass in the parser? - Tom Morris [[2015-01-20]]
* For now, don't bother with metas until someone provides a use-case. Tom Morris
* Agreed on both counts. [[User:Tantek|Tantek]] 06:56, 21 January 2015 (UTC)
</div>

----

==MIME type==
See [[microformats2-mime-type]]

==Other Interpretation Parsing Notes==
Note: most of these need to be written up as separate [[microformats2-parsing-issues]]

Author: [[User:BenWard|Ben Ward]]

[[microformats-2|Microformats 2]] proposes a new, all encompassing syntax modification of [[microformats-2-prefixes|prefixes]] that will allow microformats to be parsed from pages by processors without prior knowledge of a vocabulary. The core components of this model are quite simple, are quite simple to implement, but there are a number of conflicts that emerge with the functionality of existing microformats parsers that need to be handled. This page documents a proposed model to separate these concerns clearly in a way that can be applied to the documentation of generic microformats parsing rules, and the documentation of individual vocabularies.

Collection of other unresolved parsing issues in a generic model:

This is good material for documenting as [[microformats-2-issues]], [[microformats-2-faq]], and perhaps some of the more technical details in [[microformats-2-parsing-faq]].

* The include pattern references other elements from elsewhere in a document. A generic parser needs to track IDs and fill them in after walking the DOM. (also, <code>itemref</code> if adopted.)
** The current thinking per [[microformats-2-brainstorming]] is to adopt <code>itemref</code> and drop the [[include-pattern]]. [[User:Tantek|Tantek]]
* Will <code>itemref</code> always map to an <code>item</code> property name?
** No, <code>itemref</code> maps to one or more elements by ids, and their children. Those referenced elements may have property class names themselves, or they may contain elements that do. [[User:Tantek|Tantek]]
* [[hAtom]] implies <code>author</code> from an hCard in a page that uses an <code>address</code> element. This requires format knowledge, but a generic parser does not currently track the element type of a property node. Should it?
** It should not. element-specific handling (e.g. using "alt" from img, and "title" from abbr) is completely done at parse time. The JSON data model does not reflect which element type or attribute the value came from. Additionally, [[hAtom]] is an example where we created far too many vocabulary-specific rules, in practice they're not necessary, and only complicate the microformat for both publisher understanding and parser implementation. [[User:Tantek|Tantek]]
* [[hAtom]] defines that the highest level heading within an entry implies <code>entry-title</code>. This particular optimisation might be better off dead.
** Agreed, this is gone in microformats 2. [[User:Tantek|Tantek]]
* [[hAtom]] defines that permalinks be parsed from <code>rel</code> attributes, not <code>class</code>
** In practice this has been one of the more problematic/error prone aspects of hAtom implementations, and it's also inconsistent with other microformats (although [[hReview]] tried to use both rel permalinks and "url"). The dependence upon [[rel-bookmark]] for permalinks is dropped in h-atom in preference to re-using "u-url" and "u-uid". [[User:Tantek|Tantek]]
* [[XFN]] is entirely built on <code>rel</code> (although, has various other differences from structural microformats, as do vote-links, so perhaps are excluded from this discussion and will always be handled by dedicated parsers/queries regardless?)
** The best (easiest and most reliable) use of 'rel' microformats in practice is when they are orthogonal to 'class' microformats. This is true both with [[XFN]] and some newer [[existing-rel-values|rel values]] like [[rel-author]]. In addition, it was very clear at the recent [[schema.org]] workshop's syntax session that RDFa's decision to apparently arbitrarily mix use of 'rel' and 'property' attributes for specifying different types of properties (it wasn't clear to people in the room when you use which for what) has caused a high degree of confusion among publishers and thus high error-rates. Thus if anything we should learn from both the mistakes of RDFa and our own experiences with even very deliberate/specific mixing of rel microformats in class microformats, and keep them defined as separate orthogonal building blocks that work together, but don't depend on each other. [[User:Tantek|Tantek]]
*** Relatedly to this: <code>rel-tag</code> in hAtom. --[[User:BenWard|BenWard]] 06:50, 5 October 2011 (UTC)
**** Yes, and two related things here. First, despite my (and others') objection and (past) interoperable post/entry-specific treatment by Technorati and Ice Rocket, Hixie has redefined rel-tag in [[HTML5]] to mean applying to the whole page, not a single post. Second, I've explicitly added 'p-category' to the draft 'h-atom' vocabulary in [[microformats-2]]. [[User:Tantek|Tantek]] 07:12, 5 October 2011 (UTC)
* HTML's <code>time</code> element includes an optional <code>pubdate</code> attribute. Simply: We should parse this as <code>dt-published</code>. --[[User:BenWard|BenWard]] 06:12, 10 October 2011 (UTC)
** *If* there is even some reasonable data on actual use of the "pubdate" attribute (I don't think there is, frankly, especially with the removal of the algorithm to produce Atom from HTML5), then we could consider parsing "pubdate" as backwards compatible option for "dt-published". As a general rule, however, it is bad (demonstrably/experienced) design to depend on additional attributes (c.f. RDFa confusion over "property" vs. "rel"), especially for an instance where no additional attribute is necessary. I would leave this out for now until there is non-trivial (more than just test pages or folks who've written HTML5 books, ahem) use in the wild. When there is such use in the wild, it should be documented on a wiki page. We don't want to encourage more complex (additional attribute) publishing as a result of supporting it. [[User:Tantek|Tantek]] 12:12, 10 October 2011 (UTC)
* [[value-class-pattern]]: In microformats-2, since there are no sub-properties, there will presumably no-longer be a 'value' property in any parsed model. Properties such as 'tel > type' in hCard are, as I recall, deprecated due to underuse anyway, so 'tel > value' becomes redundant. (There's also potentially some clarification around 'price > value' in hListing, whereby value was used in a pattern. So, what does this mean for value class parsing, with regard to value-title patterns and date separation patterns. Are we looking for a 'p-value' and 'p-value-title' classname, but treating them specially (excluding them from regular property parsing.) Or, are we giving them a special prefix (v-text, v-title? That seems confusing, but could be a concept.) I'm fine with p- for both, and just having the parser ignore them since they're special, but need clarification and naming confirmation. --[[User:BenWard|BenWard]] 09:35, 10 October 2011 (UTC)
** A few things:
*** 1. Yes, no more subproperties. 'tel' becomes just 'p-tel'. If there is demand for a structured 'tel' value, then we can use that demand (and research into publishing in practice) to brainstorm and create an 'h-tel' structured telephone number (with perhaps fields like 'type', 'extension', some indication of it being local dialing (an extra 0 in some countries) or international dialing, etc.) Or, we address the different 'tel' types as their own flat properties (again as justified by research), e.g. perhaps 'p-tel-fax', or 'p-tel-mobile'. Something for hcard-2-brainstorming.
*** 2. For prices, e.g. hListing, either we're going to need to encode how to parse monetary amounts including monetary symbols, or consider creating an 'h-price' structured price. Not sure what the right answer is here, again, will need to be informed by analysis of documented actual price publication practices.
*** 3. We should avoid introducing a new prefix 'v-' just for value-class-pattern. As we've noted elsewhere, each new prefix adds complexity and should be avoided without substantial advantage.
*** 4. Using 'p-value-title' is strange, as it would be an exception to 'p-' parsing, since it would get the value from the 'title' attribute whereas 'p-' properties don't normally do that (exception: abbr).
*** 5. Using 'p-value' is also strange, as it wouldn't generate a 'value' property in the JSON data model.
*** 6. Class name 'value-title' is already sufficiently prefixed - we've found or even heard of no collisions in practice.
*** 7. Class name 'value' can, by its simpler naming nature, be expected to potentially collide with other web designer class name usage though we have no documentation/mention thereof. We could consider a renaming, or providing of alternative, such as 'value-string', or 'value-content', etc. However, let's keep that as a backup plan to use only if/when evidence is presented that we need to.
** Conclusions: for now, in microformats-2, keep using 'value' and 'value-title' as defined in the [[value-class-pattern]], and add the additional (obvious) interpretation that [[value-class-pattern#Date_and_time_parsing|value class pattern: date and time parsing]] applies to all 'dt-' properties. - [[User:Tantek|Tantek]] 12:12, 10 October 2011 (UTC)

== see also ==
* [[microformats2]]
* [[microformats2-brainstorming]]
* [[microformats2-prefixes]]
* [[microformats2-faq]]
* [[microformats2-issues]]
* [[microformats2-parsing-faq]]

neaby-metro-station

2015-05-05T12:49:37Z

TomMorris: expanding

This page is to document websites and offline material that provides information about the closeness to train, metro, tram or other transport station data on pages.

== Rationale ==

In London, people commonly refer to an area by the London Underground station closest to it and that station name often becomes a shorthand for the area near it. For example, the area around King's Cross station is commonly referred to as "King's Cross" rather than its older, pre-railway name, Somers Town.

Some London area names are not widely known: Nine Elms is close to Vauxhall station but if one wished to provide directions to that area, simply stating it is "near Vauxhall" is more instructive for most people.

Obviously, directing people to a nearby station serves a practical purpose - enabling people to get to a location via public transport.

Why not just take the geo coordinates of a location and then (using data from a service like OpenStreetMap, perhaps) find the nearest train station? Simply working out as the crow flies where the nearest station is won't necessarily help. Sometimes a station might be a short distance further but provide more reliable or frequent connections. Sometimes the walk to a closer station might take longer for pedestrians because of a complex road system and having to make lots of crossings. Perhaps a natural feature like a river is in the way.

== Examples ==

=== Web ===

* [http://www.beerintheevening.com/ Beer in the Evening]: [http://www.beerintheevening.com/pubs/s/14/14594/Royal_Vauxhall_Tavern/Vauxhall example listing], shows distance from nearby London Underground and National Rail stations
* [http://www.rightmove.co.uk/ Rightmove]: [http://www.rightmove.co.uk/property-to-rent/property-51986918.html example listing], shows distance to 3 nearest London Underground/Overground and National Rail stations
* ...feel free to add more...

=== Print ===
* ''Frommer's England'' and ''Frommer's London'' travel guidebooks

User talk:Redrobix

2015-05-05T11:02:52Z

TomMorris: spam warning

== Vandalism/spam ==
Hi Redrobix,

If you add examples to [[hcard-examples-in-wild]], please link to a specific page that actually has an hCard (either legacy or microformats2) on them. If you persist in adding examples that don't actually contain hCard markup, I will have to assume you are spamming the wiki and block your account. —[[User:TomMorris|Tom Morris]] 11:02, 5 May 2015 (UTC)

hcard-examples-in-wild

2015-05-05T10:59:56Z

TomMorris: removing joob.sg: doesn't use hCard at all.

<entry-title>hCard Examples in the wild</entry-title>
<div style="height:7.5em;text-align:center;font-weight:bold;font-size:larger">
<span style="padding:3em 0;float:left;width:33%">[[hcard-examples-in-wild#examples_by_category|Want hCards]]</span><span style="padding:3em 0;float:left;width:33%">[[hcard-examples-in-wild#new_and_uncategorized_examples|Have hCards]]</span>
</div>

This page is an '''informative''' section of the [[hcard|hCard specification]].

The following sites have published [[hcard|hCards]], and thus are a great place to start for anyone looking for examples "in the wild" for inspiration, or try parsing and indexing.

== new and uncategorized examples ==
'''Have hCard?''' If you have a site with hCard(s), add it to the top of this list. Include at least one URL to a page that includes actual [[hcard|hCard]] markup. Examples without direct links to pages with hCard(s) will be removed. Check back after a few days, to see if anyone has found any problems with the examples supplied. Note that examples may be categorized and moved to the grouped section below.

You may want to use these buttons on your pages with hCards. See [[buttons#hCard]] for any recent additions.

http://www.davidjanes.com/images/mf_hcard.png   http://www.boogdesign.com/images/buttons/microformat_hcard.png

* http://www.cadmap.co.uk/ Cadmap Land & Building Surveyors uses hCard markup on the footer of each page.
* [http://expertdent.ca/en ExpertDent dental clinics] uses hCard markup in the header as well as the contact section for its three dental care clinics].
*http://drcadieuxlangevin.com/ It is with great pleasure that we will answer all your questions!
* [http://www.us-inverters.com/ US-Inverters.com] uses hCard markup in many places, such as the home page, [http://www.us-inverters.com/ contact page] and [http://www.us-inverters.com/where-to-buy/china.php distributor pages].
* [http://www.henryandjames.co.uk/contact/ Henry & James Estate Agents] use hCard markup on their contact page.
* [http://wpoosc.com.au/ West Pymble Out of School Care] uses hCard markup for their physical address in the sidebar.
* [http://www.your-move.co.uk/ YOUR MOVE estate agents]uses hCard markup for branch addresses. Example: [http://www.your-move.co.uk/estate-agent/york.html York Branch Page]
* [http://telcoavi.es Telco Audio Vídeo e Ilumianción] uses hCards on the contact page. Example:[http://telcoavi.es/contacto.php Contacto]
* [http://nicolasbouliane.com Nicolas Bouliane - Conception de sites internet] uses hCards on the contact page as well as in the header and footer.
* [http://www.lslps.co.uk/ LSL Property Services]uses hCard markup for details of Press Contacts. Example: [http://www.lslps.co.uk/news Property News Page]
* [http://www.breaflorist.net/pages/Florist-La-Habra/display La Habra Florist] - Uses hCard markup in their la habra florsit page below.
* [http://iprefer.com/ I Prefer Guest Benefit Program] uses hCard for each property page. Example: [http://iprefer.com/luxury-hotel/Campinas/Royal-Palm-Tower/ Royal Palm Tower, Design Hotels in Campinas]
* [http://preferredhotels.com/ Preferred Hotels and Resorts] uses hCard for each property page. Example: [http://preferredhotels.com/luxury-hotel/Singapore/The-Fullerton-Hotel-Singapore/ The Fullerton Hotel Singapore, Luxury Hotels in Singapore]
* [http://www.binvisions.com/ CSS3 and HTML5 Blog] - uses hCard to get vCard of users who make comments on blog posts. Example: [http://www.binvisions.com/articles/seo-using-css-text-indent-or-images-for-logos/ CSS Text-Indent or Images for Logos in SEO?]
* [http://collectiverecyclers.com Collective Recyclers] - Uses hCard for contact details.
* [http://www.stylebar.de/ stylebar websolutions] Uses an hCard for the contact information on the right site in the website.
* [http://southpawed.com/ Steve Holland] uses hCard for his contact details.
* [http://sterlingdesignhotels.com Sterling Design Hotels] uses hCard for each property page on their website, e.g. [http://sterlingdesignhotels.com/design-hotel/Miami/Hotel-Urbano-AT-Brickell/ Hotel Urbano AT Brickell, Design Hotels in Miami]
* [http://sterlinghotels.com Sterling Hotels] uses hCard for each property page on their website, e.g. [http://sterlinghotels.com/smart-hotel/Hong-Kong/The-Fleming/ The Fleming, Smart Hotels in Hong Kong]
* [http://daniele.gobbetti.name daniele.gobbetti.name] uses hCard for his own profile. The template is released under CC-BY-SA and available on [https://github.com/danielegobbetti/about-me github]
* [http://www.sabzoo.de SABZOO.de] uses hCard for the about us page. Here is the direct link: [http://www.sabzoo.de/ueber-sabzoo/impressum.html About us]
* [http://www.coinspcgs.com Coins PCGS] uses hCard for the about us page. Example: [http://www.coinspcgs.com/p/about.html About PCGS Coins]
* [http://summithotels.com Summit Hotels and Resorts] uses hCard for each property page on the website. Example: [http://summithotels.com/luxury-hotel/Honolulu/Waikiki-Parc-Hotel/ Waikiki Parc Hotel, Luxury Hotels in Honolulu]
* [https://plus.google.com/ Google+] uses hCard for each user profile and company page. Example: [https://plus.google.com/112111196451586545452/ ReadWriteWeb profile page]
* [http://www.coatncast.de/ Coat'n Cast] has hCard formatted address information in the page markup, mainly to provide data to geolocation services.
* [http://preferredboutique.com/ Preferred Boutique] uses hCard for each property page on their website, e.g. [http://preferredboutique.com/luxury-hotel/Atlanta/TWELVE-Atlantic-Station/ TWELVE Atlantic Station, Luxury Boutique Hotels in Atlanta.]
* [http://www.last.fm Last.fm] uses hCard for event pages and user profile pages (however user profile hCard information is very incomplete and sub-optimal) e.g. [http://www.last.fm/event/1448900+She+-+Him+at+Millennium+Park+on+7+June+2010 She & Him at Millennium Park (Chicago) on 7 Jun 2010 – Last.fm]
* [http://www.msichicago.org/ The Museum of Science and Industry in Chicago] uses hCard for their address in the "museum location" area on each page.
* [http://www.brewcamp.com/ Brew Camp | Chicago's Local Home Brew Shop] uses hCard for the address under the map on the main page.
* [http://www.larsbeck.info/ larsbeck.info] uses hCard for personal contact information.
* [http://www.linkedin.com LinkedIn] uses hCard for each user profile page.
* [http://www.tripadvisor.com TripAdvisor] uses hCard on property pages, however it appears that they have lumped in locality, region, and postal-code into locality. Example: [http://microformatique.com/optimus/?uri=http://www.tripadvisor.com/Hotel_Review-g42763-d90229-Reviews-Detroit_Marriott_Troy-Troy_Michigan.html Detroit Marriott Troy]
* [http://www.megatravel.com.mx/ Mega Travel] uses an hcard for the contact information in the web site footer [http://www.megatravel.com.mx/ Mega Travel].
* [http://www.thebasketcasedeli.com The Basket Case Deli] uses hCard for organizational addresses as well as employee contact information e.g. [http://thebasketcasedeli.com/about.php About The Basket Case Deli].
* [http://www.thejokes.net TheJokes.Network] uses hCard markup on user profile pages e.g. [http://thejokes.net/profile.php?uid=3 User Profile for Sid Parker]
* [http://www.therecipedepository.com The Recipe Depository] uses hCard markup on user profile pages e.g. [http://www.therecipedepository.com/user/jay User Profile for Jay Allen].
* [http://www.airconditioningdetroit.org/ Air Conditioning Repair Detroit] uses hCard markup on the homepage of their air conditioning website.
* [http://losangeles.trenchless-sewer.com/ Los Angeles Trenchless Sewer] implements hcard on the footer of their trenchless sewer website.
* [http://www.granitecountertopsdetroit.org/ Granite Countertops Detroit] uses hCard markup on the footer of their kitchen counter top website.
* [http://www.web-id.nl/ Web-id. Webdesign, SEO and Software] Uses an hCard for the contact information.
* [http://advanced-simple.de/ Advanced Simple] uses an hcard for the contact information in the page footer of their website.
* [http://profispan.de/galerie/ Profi Span GmbH - Holz in aller Form] uses hcard for the contact information box on the right side of nearly every page.
* [http://hochzeiten-partys-feten.de/ Hochzeiten Partys & Feten] uses hcard markup for the contact information box on every page.
* [http://www.partyrentalsplace.com/ Party Rental Place] uses hCard markup on the testimonials page of their website.
* [http://www.getlocalmaps.com/ Google Map Marketing] is using hCard on the contact page of their website.
* [http://www.hardcoreepoxyflooringdetroit.com/ Hardcore Epoxy Floors] is using hCard on the footer section of their epoxy paint website. Click [http://www.hardcoreepoxyflooringdetroit.com/ epoxy michigan] to view example.
* [http://www.internetmarketingnuke.com/internet-marketing-tools/bookmarking-demon-review-1/ Bookmarking demon review]. Uses an hCard on their contact page.
* [http://www.themexicanjewelry.com/index.php?route=information/information&information_id=14 The Mexican Jewlry]. Uses an hCard for the contact information with OpenCart.
* [http://www.garmentprintiIng.co.uk/contact-us.php Garment Printing]. Uses an hCard for the contact information.
* [http://www.cabs.co.za/ CABS Car hire]. Uses an hCard for the contact information on page footers.
* [http://www.mlgphotography.co.za/ MLG Wedding Photography]. Uses an hCard for the contact information.
* [http://www.e-kyttaritida.gr/ Κυτταρίτιδα]. E-kyttaritida.gr uses an hCard on their contact page.
* [http://www.tierarztpraxis-kellerberg.de/ Tierarztpraxis Kellerberg Steingaden]. A veterinary practice that uses hCard markup to provide contact information.
* [http://www.bastajulborden.se/julbord-p%C3%A5-junibacken.html]. Uses an hCard for the contact information.
* [http://www.bastajulborden.se/.html]. Uses an hCard for the contact information.
* [https://www.redflymarketing.com/contact-us/ Redfly Ireland]. Uses an hCard for the contact information.
* [http://www.designliga.com Designliga] uses hCard markup with company contact information on its Contact and Imprint pages.
* [http://allinsuranceinfo.org/agents/alabama/montgomery.html AllInsuranceInfo.org] uses hCard markup to format insurance agents directory.
* [http://www.seveermedia.com/ Seveer Media] uses hCard markup and allow for vCard download on their contact page.
* [http://london.alleycats.co London.Alleycats.co], by Alleycats.co, uses hCard to format all their fixed-gear directory listings.
* [http://www.spaachat.com Spaachat.com], by Aquavia Spa, uses hCard and Microdata markup in the contact section and the retailers list.
* [http://www.waketoolz.de/info/impressum.html Waketoolz] uses hCard markup on their contact page.

* [http://tigermechanical.net/ Tiger Mechanical] uses hCard markukp throughout the website, inside the copyright area, [http://tigermechanical.net/ appliance repair gilbert] and in the sub domain [http://paradise-valley-appliance-repair.tigermechanical.net/ appliance repair paradise valley].
* [http://www.thedentureclinic.co.uk/ The Denture & Implant Clinic] uses hCard markup and allow for vCard download on their contact page.
* [http://ReallyGoodEnergy.com/ RGE] uses hCard markup and allows for vCard download on their page footers.
* [http://pHElixir.com/ pH Elixir] uses hCard markup and allows for vCard download on their page footers.
* [http://www.air-bourne.com/ Airbourne AC and Heating] uses hCard in footer of the air conditioning website. Example: [http://www.air-bourne.com/ Houston Air Conditioning]
* [http://theworkoutwarehouse.net/ Gym Riverview MI] uses hCard inside the footer of the workout fitness website. Example: [http://theworkoutwarehouse.net/ Weight Training Riverview MI]
* [http://www.carleasinguk.com/ www.carleasinguk.com] uses hCard markup and allow for vCard download on their page footers.
* [http://www.naples-fl-real-estate.com Naples Florida Real Estate] uses hCard markup and allow for vCard download on their contact page.
* [http://www.technicsgroup.com/ Technics Group] uses hCard markup and allow for vCard download on their page footers.
* [http://www.manageathome.co.uk/ Manage At Home] uses hCard markup and allow for vCard download on their contact page.
* [http://www.cleverelectric.com/ San Jose Electrician] uses hCard electrian footer page of their website. to see an example in action visit [http://www.cleverelectric.com/san-jose-electrical-service.html/ San Jose Electrical Contractor]
* [http://www.skin-care-health.org/spots-on-skin.html Skin Care & Health] uses hCard markup on their contact page.
* [http://www.bed-bugs-handbook.com/bed-bugs.html Bed Bugs Handbook] uses hCard markup on their contact page.
* [http://www.oakleydental.co.uk/ Oakley Dental] uses hCard markup on their address which can be downloaded as a vCard.
* [http://www.appliancerepairmedic.com/ Appliance Repair Bergen County] implements hCard in the footer area of their appliance repair site.
* [http://www.cahilldentalcare.co.uk/ Cahill Dental Care] uses hCard markup on their address in the footer which can be downloaded as a vCard.
* [http://www.returnondigital.com/ Return On Digital] uses hCard markup on their site wide footer addresses and on their [http://www.returnondigital.com/about-us/dave-ashworth.php staff pages] - these can also be downloaded as vCards.
* [http://www.arouatek.com/eng/ Aroua Range hoods] uses hCard markup on their [http://www.arouatek.com/eng/contact.php Contact] page.
* [http://www.gembuild.co.uk/contact.htm Gem Build UK ] uses an hCard on their contact page.
* [http://www.1host.gr/web-hosting/ web hosting] uses hCard markup with company contact information on its Contact and Imprint pages.
* [http://nwnasalestraining.com/contact/ Noel Walsh] - uses hCard on the contact page as well as a downloadable vCard.
* [http://www.formundcode.de/ Form & Code] - uses hCard with company contact details in page header.
* [http://www.dptraining.co.uk/contact/ DP Training] - uses hCard with H2VX's bookmarklet to allow users to download the details as a vCard.
* [http://starthilfeberlin.de/ Starthilfe Berlin] - uses hCard (and geo, XFN, rel-license, rel-profile) in (Joomla HTML5) '<#footer role="contentinfo" <footer #footertrademark <address' in all pages.
* [http://trade-service.eu/kontakt/ Trade-Service] - uses hCard in (WP HTML5) '<.address role="contentinfo" <address' in all pages, and extended hCard in the [http://trade-service.eu/kontakt/ contact page].
* [http://lanceguyatt.com/ lanceguyatt.com] - uses hCard as the index page.
* [http://www.easi-services.fr easi services] utilise hCard dans sa page de [http://www.easi-services.fr/contact contact].
* [http://www.umovefree.com/ UMoveFree] - Uses hCard for rental property address. Example: [http://www.umovefree.com/Apartment/cirque-apartments-dallas-tx/ Cirque Apartments Dallas].
* [http://www.newtosandiego.com/ NewToSanDiego] - Uses hCard for organization and business address. Example: [http://www.newtosandiego.com/Ocean-Beach-People's-Organic-Foods-Co-op/ Ocean Beach People's Organic Foods Co op].
* [http://www.northwooduk.com/ Northwood Estate Agents] use hCard on their branch landing pages, here is [http://www.northwooduk.com/letting-agents/edinburgh an example].
* [http://www.signsbannerswraps-houston.com/ Car Wraps Houston] uses hCard on the footer section at the bottom of page see [http://www.signsbannerswraps-houston.com/vehicle-graphics-and-car-wraps-houston.html vehicle wraps houston] page.
* [http://www.elevatelocal.co.uk Elevatelocal] uses hCard on their [http://www.elevatelocal.co.uk/contact Contact Us] page.
* [http://lucumalabs.com Lúcuma labs] uses hCard in the index page.
* [http://railsjobs.co.uk Ruby on Rails Jobs UK] uses hCard in the footer.
* [http://www.ufirstgroup.com/ UFirst Group] uses an hCards in the footer of every page
* [http://www.brodwax.com/ Brodwax Lighting] uses an hCard on their [http://www.brodwax.com/fluorescent-lighting-fixtures.html fluorescent light fixtures] page.
* [http://tripedge.co.uk Tripedge] uses hCard in the footer
* [http://www.appliancerepairbergencountynj.com/ Appliance Repair Bergen County NJ] uses hCard code in the footer of the appliance repair site.
* [http://www.morgenson.com/ Morgenson Realty] uses hCard on their [http://www.morgenson.com/cameron-heights-apartments.php Apartment Listing] pages.
* [http://www.bientek.com/ BienTek] uses hCard on their [http://www.bientek.com/about-us/ About page].
* [http://www.yourtraces.com YourTraces] uses hCard on their profiles [http://www.yourtraces.com/biography/1120.html example].
* [http://www.findwell.com findwell Real Estate] uses hCard on their [http://www.findwell.com/contact Contact Us] page.
* [http://droidvsiphone.org Droid vs iPhone] uses hCard in the footer
* [http://howdoyouknowifyouhavebedbugs.com HowDoYouKnowIfYouHaveBedBugs.com] uses hCard in the footer
* [http://www.schiessle.org schiessle.org] uses hCard at the index/contact page
* [http://www.deadbedbugs.co.uk/ deadbedbugs] deadbedbugs use hCard on their [http://www.deadbedbugs.co.uk/contact.html contact page].
* [http://johanramon.fr/ Johan Ramon] uses hCard on his resume.
* [http://www.saveontapestries.com/ Wall Art Shop] uses hCards on all contact pages, including their [http://www.saveontapestries.com/blog/ Wall Art Blog] and [http://www.saveontapestries.com/message.php Contact Us] Page
* [http://www.placedash.com/ placedash] uses hCard on all place pages, such as [http://accountants.placedash.com/b/4591 Steven R Aron CPA] and [http://taxconsultants.placedash.com/b/21916885 KPMG]
* [http://www.slimmeria.com/bookings-contact Slimmeria Detox Retreat ] in the UK uses an hCard on the Bookings and Contact page.
* [http://www.airbourneairconditioning.com/houston-ac-repair.html Houston AC Repair ] in Houston uses an hCard on the footer of the air conditioning website..
* [http://www.iluminacionmidava.com/ Iluminación Midava, SL ] in Spain uses an hCard on their pages.
* [http://shop.artgpa.com.ua/contacts.html ArtGPA SHOP in Ukraine ] uses an hCard on their contact page.
* [http://clothesonline.info/ ClothesOnline] uses hCard to identify clothing brands, shops and users. Example: [http://clothesonline.info/shops/mark-spencer Mark & Spencer].
* [http://www.beltmann.com Beltmann Relocation Group] uses an hCard on their [http://www.beltmann.com/atlanta-movers.aspx Atlanta Movers] page.
* [http://www.therapistinlondon.com/ Therapist in London ] Delma Walsh uses an hCards in the footer of every page.
* [http://www.novelwebdesigns.com/ Web Design & SEO] NWD uses an hCard on their contact page.
* [http://www.webscatalunya.com/ Webs Catalunya ] uses an hCards in the footer of every page.
* [http://rinklinks.ca/ RinkLinks.ca: A Comprehensive Rinks and Arenas Directory for North America] uses an hCard for every listing in their directory.
* [http://immotek.fr/ Immotek general contractor in Toulouse, France] uses hCard in the footer of every page (plus hAtom on entries).
* [http://www.aoinstitute.com/ Advanced Orthopaedic Institute ] uses an hCards on the footer of every page.
* [http://www.orchard-barn.co.uk/contact.htm Orchard House B&B ] uses an hCard on their contact page.
* [http://www.medivisas.com/contact.asp Medi Visas UK ] uses an hCard on their contact page.
* [http://www.premierlogos.co.uk/page/contact Premier Logo T Shirts ] uses hCard on the contact page.
* [http://eastsideentrepreneurs.ning.com/profile/MrsClean/ Mrs Clean House Cleaning ] uses hCards in the profile page.
* [http://www.thesanfordhouse.com/ The Sanford House Bed & Breakfast ] uses hCards in the footer of every page.
* [http://www.imap.cat/ Imap Internet Marketing] uses hCards in the footer of every page.
* [http://www.haraldjoergens.com/Copyright.html Harald Joergens Photography ] uses hCards on the page and in the footer of every page (see blog post [http://www.haraldjoergens.com/blog "From website to address book in one click"]).
* [http://www.ethoseo.com/ Ethoseo Internet Marketing in Washington State ] uses hCards in the footer of every page.
* [http://www.roofingandsidingdetroit.com/ Roofing Detroit] uses hCards inside the footer of every page on their roofing website.
* [http://www.iobuild.co.uk/ IO Garden Buildings] is using hCard on their [http://www.iobuild.co.uk/garden_home_offices_about_us.asp About Us] page.
* [http://www.popalockofjacksonville.com/ Pop-A-Lock Locksmith Jacksonville] is using hCard in the footer on all the pages on their website and the hReview code on their testimonials page [http://www.popalockofjacksonville.com/jacksonville-reliable-safe-locksmith.html/ Pop-A-Lock Locksmith Jacksonville Testimonials]
* [http://Tutiendadeinformatica.com/ oferta de portatiles] - uses hCard as the index page.

* [http://www.harleytherapy.co.uk Harley Therapy, Counselling London] uses an hCard (Organisation) on the home page as well as an hcard for an individual practitioner on the [http://www.harleytherapy.co.uk/psychiatrists-london.htm Psychiatrist] page.
* [http://www.mwmachineshop.com/ M & W Machine Shop] is using hCard in the footer on the entire site.
* [http://carmela.co.uk/ Carmela Make-up] is using hCard on most pages of her site, including the [http://carmela.co.uk/wedding-make-up.htm wedding make-up] page.
* [http://www.findaporsche.com/ Find a Porsche] is using hCard on their [http://www.findaporsche.com/?page_id=17 Contact Us] page.
* [http://www.atrendyhome.com/ A Trendy Home - Home Improvement Store] is using hCard on their [http://www.atrendyhome.com/contactus.html Contact Us] page.
* [http://tedswoodworkingplan.com/ Teds Woodworking] uses hcard for their site information.
* [http://www.mrscleanusa.com/ Mrs. Clean's Cleaning Service] is using hCard on their [http://www.mrscleanusa.com/en/cleaning-services/mrs-clean/about-us.html About Us] page.
* [http://www.merrittsforhair.co.uk/ Merritts for Hair] is using hCard on their [http://www.merrittsforhair.co.uk/contacts/ Contact Us] page.
* [http://www.alwaysonmessage.com/contact/get-in-touch.aspx Always on Message] is using hCard on their Contact Us page and are interested to see/hear how hCard's can be used in Smartphone Apps,
* [http://sroe.home.cern.ch/sroe/sroe/Welcome.html Shaun Roe] is using hCard on his work page at CERN,
* [http://www.localdatabase.com/ Local Database] uses hCard on all category and business profile pages, [http://www.localdatabase.com/texas/Houston/Veterinarians/ Houston Vets]
* [http://www.pinbud.ca/ www.PinBud.ca and www.PinBud.com (a search and get quotes website)] uses hCard on all the listing pages, example: [http://www.pinbud.ca/list-services/475-Personal-trainers-in-Calgary,%20AB Personal trainers in Calgary]
* [http://www.quippd.com/popular quippd] uses hCard on profile pages and story listings.
* [http://www.davidrivers.name David Rivers] uses hCard markup on his [http://www.davidrivers.name/contact Contact David Rivers] page
* [http://www.pabloestrada.us/pe/pablo.estrada.html Pablo Estrada] uses hcard on his resume page.
* [http://www.nieruchomosci-czubak.pl/ AJ Czubak Nieruchomości] uses hcard markup in the fixed contact info section on the left and within the [http://www.nieruchomosci-czubak.pl/kontakt.html contact subpage]
* [http://www.metalgigs.de Metalgigs.de] uses hcard for the profile pages at metalgigs.de/userpage/username, see [http://www.metalgigs.de/userpage/Testuser]
* [http://www.ankeboelens.nl/ Anke Boelens Interieurvormgeving] uses hcard markup in page footer
* [http://ragtagntextile.org.uk Rag Tag 'n' Textile] - Mental health charity in Skye and Lochalsh, the Highlands of Scotland - uses hCards for locations of head office and craft shops]
* [http://atzkey.org/ Denis Bakunovitch] — IT professional — has nicely styled hCard
* [http://www.olaru.ca/ Maria Olaru - lawyer / avocat - Montreal Law Firm] uses hCard for the law office.
* [http://www.epinux.co.uk/contact Mike Shutlar at Epinux] uses hCard markup on his contact page.
* [http://nzia.org/practitioner-directory/ New Zealand Institute of Acupuncture] uses hCards to display member's contact details.
* [http://www.mamscatering.nl/ MAMS Catering] uses the drupal hCard module for contact information on the website.
* [http://www.ialphan.com Alphan Gunaydin] uses hCard markup throughout the home page (index).
* [http://www.phytodoc.de/therapeuten-suche/ PhytoDoc's database for therapists in Germany] uses hCards for contact data on the detail pages of every therapist. [http://www.phytodoc.de/therapeut/wiesloch/berthold-musselmann/ Examplary therapist's page].
* [http://www.charleschurch.com Charles Church House Builder] uses hCard for property development addresses and geo latitude and longitude. See [http://www.charleschurch.com/carmarthenshire_ammanford/pen-y-bryn-1067 Homes for sale in Ammanford] page for embedded hcard on property development pages.
* [http://www.canisphouse.com Canisp House Bed and Breakfast]Establishment uses hcard to mark up business address. Validates with Google Rich Snippets.
* [http://www.jondon.com/stores/index.htm Local Stores Locations Page], the store details on store pages are Hcard.
* [http://www.sucklings.co.nz/contact-us Contact page of Sucklings Shoes Store], the store details are an Hcard.
* [http://www.a3architekten.com/ Contact details of a3architekten]. A combination of two hCards looking like one.
* [http://www.imap.cat]. A combination of two hCards looking like one.
* [http://www.sigmacom.nl/ Corporate website of Sigmacom]. hCards were implemented in the footer
* [http://www.fpc.wa.gov.au Forest Products Commission] hCards to markup addresses & contact info for:
** all its offices and media contacts: [http://www.fpc.wa.gov.au/content_migration/about_us/contacting_us.aspx office locations]
** search results for suppliers of timber within Western Australia: [http://www.fpc.wa.gov.au/BuyTimber/Search?Species=&Region= find a timber supplier]
* [http://www.hirners.com Hirners Hotel Guide] uses hCards to markup addresses and contact info of every property, including geo coordinates. Example: [http://www.hirners.com/properties/4-atlanta-hotel-in-vienna-austria Hotel Atlanta in Vienna, Austria]
* [http://www.cartuse-imprimante.ro/ Cartuse Imprimante], printers and printer cartridges supplier, uses an hCard on home page and contact page of the website.
* [http://www.seminee-bellfires.ro/ Seminee Bellfires], interior fireplaces design company uses an hCard on every page of the website.
* [http://www.eurodata.com.ro/ Eurodata Serv], IT consulting and service company uses an hCard on every page of the website.
* [http://www.chipwreck.de/blog/contact/ Mario Fischer] uses a hCard with his contact information
* [http://joebergantine.com/contact Joe Bergantine] has marked up his contact information with hCard and XFN
* [http://www.nonleaguegrounds.com nonleaguegrounds.com], a database of English non-league football stadiums, uses hCards on every specific club detail page. Example: [http://www.nonleaguegrounds.com/gb/london/afc-wimbledon AFC Wimbledon]
* [http://thetruthaboutabs1.com/ Thetruthaboutabs] uses hcard for their site information.
* [http://www.simourix.nl/ Simourix Hosting] uses an hCard for contact information on the website.
* [http://www.aquastop-vochtwering.nl/ Aquastop vochtwering] uses an hCard on every page of the website.
* [http://www.kennysaunders.com/ Kenny Saunders] uses an hCard on for contact information on this business card website.
* [http://thesilverfishbug.com/ Silverfish Bug] uses hcard for their site information.
* [http://annuaire.leperon.fr/ L’Annuaire du Cheval] is a French directory of equestrian professionals. We have just added hCards to all the client pages. Sample one here [http://annuaire.leperon.fr/client/0b1s/tarder-camille-et-frederic Tarder]. We also added an 'add to your address book' button but had to take it out again as some Windows machines choked on the accents, not recognising the UTF-8.
*[http://www.cheapholidays.com/ Cheap Holidays] uses an hCard on each page footer.
*[http://www.flightline.co.uk/ Flightline] uses an hCard on each page footer.
*[http://www.affordablestorage.net.nz/contactus.html Affordable Storage] Uses hCard for contact information.
* [http://www.norfolkblackhistorymonth.org.uk/contact.html Norfolk Black History Month] - Uses hCard on the Contact page and throughout the site, providing contact information for event locations, organisers and partner organisations.
* [http://www.veganusofa.com/ VeganUSofA] - Uses hCard for organization and business address. Example: [http://www.veganusofa.com/index.php?listing=4 The All Vegan Store].
*[http://adrianindo.blogspot.com ADRIAN'S BLOG] have included hCard to introduce myself more closely with the visitors of my blog. the hCard has been listed as a name, blog url and organizations. This hCard you can see on the lower right sidebar of my blog layout.
* [http://www.canadianpokerexpo.com The Canadian Poker Expo (Toronto)], a Poker Lifestyle Expo focusing specifically on the Toronto market, is using hCard for [http://www.canadianpokerexpo.com/Contact-Us/Contact-Form their contact page] as part of their efforts to increase the site's local relavance.
* [http://www.semineeas.ro Seminee As], a Romanian fireplace manufacturer, uses hCard for [http://www.semineeas.ro/contact/ contact info] with optional vCard download.
*[http://www.gastrohep.com/aboutus.asp GastroHep.com] About Us page uses an hCard for the contact address.
*[http://wedding-slideshows.net/ Wedding Slideshows] uses hCard for business address and contact details.
*[http://leemannphotography.ca/?p=contact Lee Mann Photography] Uses an hCard on the main Contact page as well as the blog.Ideally it will soon be on the footer of every single page.
*[http://www.kimburgess.info Kim Burgess] Minimalist info website with hCard markup positioned throughout.
*[http://www.plumbset.co.uk/ContactUs.asp PlumbSet UK Ltd] Uses hCard for the contact address, including multiple street-address entries.
*[http://www.manuhealth.com/products/manuka-soap-75gm Manuhealth Natural Remedies] Uses hCard for the return address on product pages.
*[http://www.farmaciasarria.com/esp/mapa.php Farmàcia Sarrià - Farmàcia Finestres Capdevila] uses an hCard for his contact information.
*[http://www.naturesbestshot.com Nature's Best Shot Photography] - uses an hcard on the contact page
*[http://www.noomii.com/life-coach Noomii.com Coach Directory] - each professional life coach in the directory is an hcard
*[http://www.ethical-junction.org/member/org-2012.html Ethical Junction CIC - Profile page] We use hCard for every organisation on their profile page
*[http://www.bowtietv.com Bow Tie Television] Uses hCard for contact information on every page and in the contacts section.
*[http://www.tauruslogistics.co.nz/about/contact Taurus Logistics] Uses hCard for contact information.
*[http://www.professdiamond.com/ professdiamond] encodes Thai as UTF8 in an inline hCard at the bottom of every page.
*[http://avonvalleylocalguide.iinet.net.au/ Avon Valley Local Guide] uses hCard for contact information of advertisers.
*[http://www.arizonafirstresponse.com/ Arizona First Response] uses an hCard on each page footer.
*[http://dillingham.me.uk/ Iain Dillingham] uses an hCard on each page footer, and has a styled example (with the microformats logo) on his [http://dillingham.me.uk/contact.html contact page].
*[http://www.pixeflips.com/ Pixelflips Web & Interface Design] hCard is used in the footer of all pages for easy access to contact information.
*[http://www.herminesperr.at/ Hermine Sperr, Qualified Practitionier of the Grinberg Method® in Wien/Austria] A hcard is used for contact information on every page on her website.
* [http://www.ivycat.com/ IvyCat Website Services] - Web design & hosting firm uses hCard for business contact info. Example: [http://www.ivycat.com/contact/ Contact Us].
* [http://www.modeltrainswithlarry.com/ ModelTrainsWithLarry] - Uses hCard for organization and business address. Example: [http://www.modeltrainswithlarry.com/index.php?listing=502 Choo Choo Barn].
* [http://www.gardeningwithlarry.com/ GardeningWithLarry] - Uses hCard for organization and business address. Example: [http://www.gardeningwithlarry.com/index.php?listing=2681 United States Botanic Garden].
* [http://abyrvalg.com/ Abyrvalg] - russian city community. Uses hCard to display local businesses address. Example: [http://moscow.abyrvalg.com/biz/faq-cafe FAQ cafe in Moscow].
* [http://www.jdclark.org/v1 Jordan Clark], from the Swansea area of Wales in the United Kingdom, uses [http://www.jdclark.org/card hcard for contact information].
* [http://whichtwitterapp.com/ WhichTwitterApp] provides [http://whichtwitterapp.com/reviews/iphone/tweetie reviews of twitter apps] using hCard, hReview, rel-tag and rel-home.
* [http://www.robinleysen.be/Robin.html Robin Leysen] has a hCard on a separate page. Tried to be as complete as possible. hCard validated with Optimus.
* [http://www.jay-photographics.de/ Jay Photographics] Photographer from Stuttgart, Germany. The hcard format is used on all pages for contact information.
* [http://www.uniquesite.co.uk/ UNIQUEsite] Website designer based in Brighton, UK. Uses the hcard format for contact information.
* [http://www.slideshare.net/ SlideShare] uses hcard to identify its users. see [http://hcard.geekhood.net/?url=http%3A%2F%2Fwww.slideshare.net%2Fkcmani#result Validated hcard] and [http://www.slideshare.net/kcmani Mani's SlideShare profile]
* [http://chrisruppel.com Chris Ruppel], a web developer in Dallas, TX, uses an hcard for contact information site-wide (as well as XFN)
* [http://greenspiritgardeners.com/ Green Spirit Gardeners] uses the hCard format throughout the site, including on the portfolio page for [http://greenspiritgardeners.com/portfolio/ commercial clients] and the [http://greenspiritgardeners.com/contact/ contact] page.
* [http://www.dorettebos.nl/ Dorette Bos Coaching & Training] uses hcard microformat on the [http://www.dorettebos.nl/contact.php contactpage]
* [http://volunteers.st/ Steffi & the volunteers] is an Austrian band and uses hcards for [http://volunteers.st/ band-contact in the footer] and on the page of the [http://volunteers.st/crew.html crew]
* Turkish business directory website [http://www.firmasec.com/ firmasec.com] implements valid hCard and hReview-Aggregate for companies, contact information with geo tags and user comments. Example: [http://www.firmasec.com/firma/mmfzz-caprice-palace-hotel-didim/ Caprice palace hotel profile page]
* [http://www.textundkonzept.at Bernhard Ulrich] an Austrian copywriter uses the hcard format [http://www.textundkonzept.at on all pages of his website] for his contact information
* [http://www.powerbrand.at/contact.html POWERBRAND] a brand name development agency uses a [http://www.powerbrand.at/contact.html hcard for contact information]
*[http://www.koerperarbeit.net/ Anita Braunsberger, Qualified Practitionier of the Grinberg Method® in Linz/Austria] A hcard is used for contact information on her website.
*[http://www.carpetscleansandiego.com Durbin's Carpet Care] displays a vCard for contact information and relevancy
*[http://www.nationalrural.org/organisation.aspx?id=96a3fc04-5c03-4d31-bb8a-2c55cc29aed4 National Rural Knowledge Exchange] uses an hCard with geo tags when displaying an organisations information
* [http://www.tinstar.co.uk/about-tinstar-design/contact-tinstar-design.html Tinstar Design] uses an hCard for company contact information.
* [http://www.interdixit.com/esp/contacto.php Interdixit] uses an hCard for his contact information.
* [http://www.sisnova.com/ Sisnova] uses hCard for his location pages.
* [http://www.fenoyarquitectura.com/esp/situacion.php Eduard Fenoy i Associats] uses an hCard.
* [http://www.deltronic.com/ Deltronic Corporation] of Santa Ana, CA has posted an hCard with geo tags on its [http://www.deltronic.com/contact.shtml Contact] page. Background image of a contact card reinforces content. For those without enabling browser extensions, both hCard "logo" and text link make vCard available via external parser.
* [http://transitionsmft.org/ Transitions Marriage and Family Therapy] has an hCard with geo tags in the footer of each page. There is also an hCard for each counselor on the [http://transitionsmft.org/about.php About] and [http://transitionsmft.org/contact.php Contact]pages.
* [http://ball.in.th/ ball.in.th] uses hCard to display all usernames.
* Italian business directory and community portal [http://www.cylex.it/ cylex.it] implements hCard for companies’ contact information with geo tags. Example: [http://www.cylex.it/azienda/computerland-10559319.html company profile]
* [http://jermy.musicremedy.com/ Jermy Leeuwis MSc] uses an hCard for his contact information.
* [http://idoinfotech.com Gary Eckstein] uses an hCard for [http://idoinfotech.com/contact contact information].
* [http://www.drsuarez.net/ Dr. Suarez] uses hCard on his [http://www.drsuarez.net/cvitae.html resume page]
* [http://sourceforge.net/projects/adx/ addressbook.xml] provides hCard support: [http://elektronengehirn.net/addressbook/addressbook.html adx live example]
* [http://aplawrence.com APlawrence.com] is using hCard for its [http://aplawrence.com/Links/consultants.html Unix and Linux Consultants Page]
* [http://www.afonsoduarte.com Afonso Duarte's Portfolio]. Uses an hCard for the contact information.
* [http://www.rafe.me Web development by Rafe Harwood]. Uses an hCard for the contact line in the footer of every page.
* [http://www.frogmeat.com Los Angeles Web Design]. Uses an hCard for contact information.
* [http://www.arbea.basilicata.it/ ARBEA - Agenzia della Regione Basilicata per le Erogazioni in Agricoltura]. hCard is used both for classic [http://www.arbea.basilicata.it/index.php?option=com_contact&view=contact&id=4&Itemid=101 Contact page] and for farms showcase ("Vetrina Aziende Agricole") available for registered users. I've embedded it modifying Joomla! 1.5 com_contact core component. Users of this CMS can [http://joomlacode.org/gf/project/hcardcontact/ download my patch].
* [http://trumps.net Los Angeles Search Engine Optimization] Uses hCard in the footer of all pages.
* [http://www.oasisroofinginc.com/ Seattle Roofing] Uses hCard in the footer of their roofing website see [http://www.oasisroofinginc.com/ Roofing Seattle WA] to see the hcard.
* [http://reaganvick.com Personal Portfolio of Lance Reagan Vick]. Includes examples of PGP and SSH public keys I have not seen used anywhere else. Hopefully someone finds it helpful!
* [http://www.fracturedstudios.com Los Angeles Search Engine Optimization] uses hCard to provide address information at bottom of page
* [http://www.csid.upt.ro/home.php The Distance Learning Center - CSID, "Politehnica" University Timisoara], Romania uses hCard, including geo information, in every page's footer for encoding the University address. hCard is also used for [http://www.csid.upt.ro/personal.php staff] and student contact information.
* [http://rehabpizza.co.uk Rehab Restaurant] London restaurant, see the sidebar for link to [http://rehabpizza.co.uk/rehab.hcard the hcard].
* [http://www.outdoorla.org/ Los Angeles Hiking Trails] at the bottom right, our contact information is marked up as an hcard.
* [http://c7.se Code7 Interactive] uses a hCard for Peter's [http://c7.se/contact contact details].
* The [http://www.austinartcollective.com Austin Art Collective] is a group dedicated to helping emerging artists sell their artwork online. There is space for users to submit [http://www.austinartcollective.com/gallery/Art-City-Austin.html art gallery reviews] as well, [http://www.austinartcollective.com/austin-galleries/Downtown.html organized by neighborhood] in Austin, TX USA.
* [http://www.squaremeal.co.uk/ Square Meal Restaurant Guide] uses hCards and hReviews for all restaurant listings and [http://www.squaremeal.co.uk/review/Ristorante_Semplice/1596 visitor reviews].
* [http://www.vegan-nottingham.co.uk/ Vegan Nottingham Guide] uses hcards, including geo information, for each entry in the guide.
* [http://www.cgtworld.com/ Cybernation Gamers Tournament] uses hCard in all users profiles like [http://www.cgtworld.com/profile/id-1/ Moonlext's Profile] and in the [http://www.cgtworld.com/about/press.html press page of CGT].
* [http://fcctlh.org First Christian Church of Tallahassee] Uses hCard in the footer of all pages.
* [http://www.pseps.com/vc-people/a.cfm The PSEPS Venture Capital and Private Equity Directory] Venture capital and private equity directory using microformats (both for professionals and firms).
* [http://www.koningskindkadootjes.nl koningskindkadootjes.nl] Hcard located at the bottom of the pages.
* [http://www.futurix.nl futurix.nl website and webshop development] At the bottom of the pages you'll find the hcard. With a link to technorati the hcard is used to get a vcard out of the hcard.
* [http://romjon.com/contact-us romjon.com website design & development] Contact Us page using hcard to markup address details. By using Operator, Google Maps and Yahoo! Maps can be made to open with the pointer, respectively, in pretty much and more or less exactly the right place.
* [http://www.thebeanmachine.nl/ The Bean Machine] at the bottom right, our contact information is marked up as a hcard
* [http://www.universalmedicalid.com/canada Universal Medical ID Canada] uses hCard to provide address information at bottom of page, as well as on a number of pages within the site.
* [http://www.floristfullerton.com/ fullerton florsit] uses an hcard for the web site footer [http://www.floristfullerton.com/ florist fullerton].
* [http://puronicsorangecounty/ Puronics Orange County] uses an hcard for example view footer [http://puronicsorangecounty.com/ water softener orange county].
* [http://web.mac.com/a.gibson/ Alex Gibson Web Developer] uses hCard for contact info on his homepage.
* [http://www.wardelldesign.com/html/contact/index.php Wardell Design] uses hCard for contact info with optional vCard download.
* [http://www.drfosterhealth.co.uk/hospital-guide/ Dr Foster Hospital Guide] uses hCard to mark up hospital addresses. See [http://www.drfosterhealth.co.uk/hospital-guide/hospital/nhs/Basingstoke-and-North-Hampshire-Hospital-366.aspx Basingstoke hospital page] for example.
* [http://www.drfosterhealth.co.uk/complementary-therapist-guide/ Dr Foster Complementary therapist guide] The [http://www.drfosterhealth.co.uk/complementary-therapist-guide/objectlist.aspx?w=32&p=8&obid=&sub=0 regulatory bodies page] uses hCard for contact details.
* [http://wayne.edu/ Wayne State University] uses hCard for University address and contact details in the global footer used on most web pages.
* [http://www.brakemeters.co.nz/ Portable Brake Meters N.Z. Ltd] uses hCard for business address and contact details.
* [http://www.tallpoppieshamilton.co.nz/ Tall Poppies Florist] uses hCard for business address and contact details.
* [http://www.livingcolour.co.nz/ Living Colour Florist] uses hCard for business address and contact details. See [http://www.livingcolour.co.nz/Information.aspx Information] page
* [http://www.dallasfamilyhomes.com/ DallasFamilyHomes.com] uses hCard for property addresses and geo latitude and longitude. See [http://www.dallasfamilyhomes.com/dallas-homes/ Dallas Homes] page for embedded hcards and property detail pages.
** Pretty good. An improvement might be to use <code>agent</code> to mark up the agent's contact details, and <code>note</code> to mark up the property descriptions. [[User:TobyInk|TobyInk]] 16:22, 4 December 2008 (UTC)
** Thanks for the suggestion Toby. Added the <code>note</code> for the description to the homes listings and home detail pages.
* [http://www.jabz.de/ Jabz | Internet Marketing Agentur] uses hCard for business address and contact details. See [http://www.jabz.de/kontakt/ Contact Page]
* [http://www.headyperfume.com/ Headyperfume.com] Uses hCard for contact information.
* [http://sixthirteendesign.com/ Six Thirteen Design] uses an embedded hCard along with other contact details on the footer of each page (http://sixthirteendesign.com/)
** ''Problems:'' page also includes class="vcard" used in a non-hCard context (for a VCARD download); types for telephone number and e-mail address are improper. [[User:TobyInk|TobyInk]] 16:22, 4 December 2008 (UTC)
* [http://www.locanto.com/ Locanto - Free Classifieds] uses hcards to geolocate their classified listings. Visit the ad pages for examples.
* [http://www.yalwa.com/ Yalwa - Local Directory] uses hcard on their directory listings. Example: [http://wiesbaden.yalwa.de/ID_102318221/Yalwa-GmbH.html Yalwa Address Listing]
* [http://www.fluendi.com/Contact Fluendi Consulting] uses hcard on their contact page (http://www.fluendi.com/Contact)
* [http://www.badbedbugs.com/ Bed Bugs] uses hcard for their site information. See the [http://www.badbedbugs.com/about-bad-bed-bugs/ about bed bugs] page.
* [http://www.lawyer-directory.net/ Lawyer Directory] uses hcard for addresses within the lawyer directory. Example [http://www.lawyer-directory.net/lawyer/Grand-Rapids-Bar-Association-Grand-Rapids-law434032.htm listing]
* [http://www.hanfmuseum.de/about About Hanf Museum Berlin] uses hcard for addresses and contact informations.
* [http://maps.google.com/ Google Maps] uses hCards for addresses. See [http://googlemapsapi.blogspot.com/2007/06/microformats-in-google-maps.html Microformats in Google Maps].
* [http://local.mapquest.com/ MapQuest Local] uses hCards for locations, hCalendar for events and supports the draft Geo format when lat/lng data is provided. See [http://blog.mapquest.com/2008/09/25/microformat-support-on-mapquest-local/ Microformat Support on MapQuest Local] for more information.
* [http://www.whitepoppy.com/ WhitePoppy.com] uses hCard for business address. See [http://www.whitepoppy.com/Contact.aspx Contact Page]
* [http://www.hightechcville.com/ HighTechCville] uses hcard to mark up people and organizations. See [http://www.hightechcville.com/people/72-eric-pugh Eric Pugh] for an example.
* [http://www.cleanertoday.com/ Cleaner Today] uses hcard to mark up contact details. (see [http://www.cleanertoday.com/Cleaner-Today-a/1.htm Contact Page])
* [http://www.aduk.org Audience Data UK] use hcard on their [http://www.aduk.org/contact.php contact page] and [http://www.aduk.org/directory.php directory of related organisations]
* [http://georgebrock.com georgebrock.com] used hcard for George's contact details
* [http://suggestionbox.com/ SuggestionBox] uses hcard for companies listed on its site. Example: [http://transfercar.suggestionbox.com/ Transfercar].
* [http://www.vcventerprise.com/wp/ Christopia] uses hcard to mark up contact details. (see [http://vcventerprise.com/wp/contact/])
* [http://www.rossirovetti.com/ Rossi & Rovetti Flowers in San Francisco] uses hcard to mark up company details in the about us page of the website. (see [http://www.rossirovetti.com/scripts/aboutus.asp example])
* [http://youtube.com YouTube] uses hcard to identify video contributors (see [http://www.flickr.com/photos/factoryjoe/2793731119/in/photostream/ screenshot]]
* [http://sewmyheadon.com/contact sewmyheadon.com] uses hcard to mark up contact details on contact and about pages.
* [http://www.kleinassoc.com/ Klein & Associates - Estate Planning] used hcard to mark up contact details on law firm's contact page.
* [http://www.markuspage.com/markus/en/contact Markus Kilås] uses hCard to mark up his contact details.
* [http://www.southsidewarriors.com/impressum.cfm Southside Warriors] uses hcard to mark up contact details on the imprint page.
* [http://applesold.com/ Apple Realty - Bristol Real Estate Company] uses hcard to mark up company details in the footer of website.
* [http://www.surfcom.co.uk/app/contact/ Surf Commission] uses hcard to mark up company contact details with option to download vcard.
* [http://www.k9yardpatch.com/contact-us/ K9YardPatch] uses hcard to markup company contact details with option to download.
* [http://www.ecovian.com Ecovian] uses hCard to mark up eco-friendly business contact details, see [http://www.ecovian.com/l/san-francisco-ca/jardiniere-restaurant example]
* [http://www.dischord.com/ Dischord Records] uses hCard to mark up company contact details in the footer of the home page.
* [http://www.thinkambient.co.uk/ ThinkAmbient] uses hCard to mark up company contact details.
* [http://proofile.org/ Proofile] extensive profiles with hCard, vCard, XFN and FOAF support.
* [http://www.ebycattle.com/horses/index.html Eby Ranch] uses hCard for the different branches of the company, with option to download the vCard.
* [http://www.clavex.com/contactus.aspx Clavex - A Latin America Financial Institution ] Uses hCard and geo for the contact information. Simple but effective.
* [http://www.dancefederation.co.uk Dance Federation Salsa Dancing & Jive Dancing Lessons and Events ] Directory for classes, lessons and events users hcard on its lessons and events -- region and url properties are empty. Is that an error?
* [http://mop.ardom.co.il/contact.php Southern Arava Research and Development Center] uses hCard for their contact details on their contact page and in sub pages with contact info. -- one card has two fn properties.
* [http://www.itma.org.uk/find-expert/London] - ITMA Trade Mark Attorney search presents results as hCards
* [http://interkonect.com Interkonect > Website Application Specialists] Office contact details marked up using vcard.
* [http://library.christchurch.org.nz/ContactUs/ Christchurch City Libraries (N.Z.)] contact page plus each of our libraries' individual pages linked from [http://library.christchurch.org.nz/Community/Libraries/ Library Locations map].
* [http://www.leftclick.com/about-us/ LeftClick] uses hcards for contact information.
* [http://ideas.veer.com/skinny Veer's Skinny Blog] implements hcard for comments and post authors.
* [http://wolpy.com/missha Wolpy] Uses hcards for contacts and [http://wolpy.com/missha/profile profile].
* [http://www.veganworldorder.com/index.php?m=vegguide Vegan World Order | Restaurants ] Uses hcards for restaurant listings.
* [http://mahalo.com Mahalo] per the announcement [http://www.seanpercival.com/blog/2008/04/23/mahalo-adds-microformats/]
* [http://www.buythatlocally.com BuyThatLocally ] uses hcards for local business information.
* [http://www.firmendb.de Firmendb] uses hCard for individual business contacts, e.g. [http://www.firmendb.de/firmen/15592.php]
* [http://autopendium.com Autopendium] has resources (e.g. suppliers, clubs) marked up with throughout the site, e.g. [http://autopendium.com/clubs/8-Volvo-Enthusiasts-Club]
* [http://display-block.co.uk Display-Block] uses hCard contacts for People and Companies on my personal Blog.
* [http://www.codesignville.com/ Codesignville] uses hCard for his contact details.
* [http://fan-expo.com/Contactez-nous,2 Forum des Acteurs du NumÃ©rique] (a French trade show and exhibition dedicated to content management) uses hCard for contact information (exhibition staff and exhibitors). It also makes use of hCalendar as well as rel-tag when relevant.
* [http://www.corewhisperer.com/ The Core Whisperer] (Paul Ransom) Geological Services uses hCard for contact information.
* [http://chairmanship.mfa.md/en/ The regional presidencies] of Republic of Moldova to the SEECP, CEI, MAG-RACVIAC, SEEHN, CEFTA uses hCard on [http://chairmanship.mfa.md/seecp-contacts/ contacts pages]
* [http://www.viget.com/about/team Viget Labs] - Team page and Individuals' Pages.
* [http://www.re3elstance.com RE3EL STANCE] - Entrepreneurship: Rebel Style.
* [http://www.worldeventsguide.com World Events Guide] - Events occuring around the world marked up with hCard.
* [http://www.amaliahotel.eu/en/contact.html Amalia Hotel Apartments] uses hCard in the contact-info page.
* [http://www.sslcertificaten.nl/contact.php Xolphin SSL Certificaten] uses hCard for their contact details
* [http://examples.tobyinkster.co.uk/hcard hCard + RDFa Example] - raising the bar for parsers...
* [http://competitiondiva.com/ Competition Diva] uses hCard in its page footer (and plans on it for the upcoming profile pages).
* [http://sanisoft.com/ SANIsoft] uses hCard in its page footer
* [http://www.bossalive.com BossaLive] uses [[hcard|hCard]] on user profile pages.
** Example: [http://www.bossalive.com/user/barry Barry's Profile]
** Also uses rel-tag microformat for tagging music. Publishes rel-tags for album, artist and genre.
* [http://hillhursthardware.com/ Hillhurst Hardware's] contact info w.logo uses hcard.
* Birmingham's [http://bigcityplan.org.uk/ Big City Plan] (England)
* Producer [http://www.sun-treader.com/contact.html Christopher Davis] uses hCard markup on his contact page.
* [http://www.tpexpress.co.uk/Liverpool08-Capital-of-Culture/ First TransPennine Express - Liverpool 08, Capital of Culture] - uses hCard to markup suggested venues.
* [http://anand.ws/ Anand's Musings] uses hCard to mark up authors for comments and posts.
* [http://www.onyomo.com/ OnYoMo] uses hCard markup for all addresses listed in their local search results.
* [http://www.dctalks.org/design/ DC Design Talks] used hCard to mark up the speakers for this one-day event.
* [http://www.entidi.it eNTiDi software] provides a basic hCard sample.
* [http://quickbase.intuit.com QuickBase] uses hCard markup on our contact us page.
* [http://www.pixsense.com/contact_us.html PixSense.com] uses hCard markup for addresses across the PixSense website.
* [http://www.areaguides.net areaguides.net] uses hCard markup for all addresses across the site.
** Examples: http://chicagoil.areaguides.net/ypcyellowpg/restaurants.html, http://newyorkny.areaguides.net/hotels.html
* [http://www.ll.georgetown.edu/ Georgetown University Law Library] in Washington, D.C. now uses hCard for our address on all pages. Also, library staff biography pages use hCard such as [http://www.ll.georgetown.edu/staff/bio.cfm?id_no=105 here] and [http://www.ll.georgetown.edu/staff/bio.cfm?id_no=32 here].
* [http://www.ll.georgetown.edu/ Georgetown University Law Library] in Washington, D.C. now uses hCard for our address on all pages. Also, library staff biography pages use hCard such as [http://www.ll.georgetown.edu/staff/bio.cfm?id_no=105 here] and [http://www.ll.georgetown.edu/staff/bio.cfm?id_no=32 here].

* [http://www.mtgd.gov.md/ Ministry of Transport and Road Industry] of Republic of Moldova. First Moldavian governmental site using hCards on [http://www.mtgd.gov.md/ministrul/ staff pages], [http://www.mtgd.gov.md/subdiviziunile-ministerului/ subdivisions page] and in the footer of each page (contact information)
**Only [http://www.mtgd.gov.md/ Romanian] and [http://www.mtgd.gov.md/ru/ Russian] versions available yet
* [http://www.auctionlink.com.au/ AuctionLink] uses hCard for Auctioneer records like [http://www.auctionlink.com.au/Auctioneers/Auctioneer/Cam_Brown_Auctions/ Cam Brown Auctions] (also uses hCalendar)
* [http://www.wlzine.com/ WLZine] uses hcard to mark up contact details for diet programs (see [http://wlzine.com/south-beach-diet-one-of-the-best-diets-out-there/ South Beach Diet]
* [[User:WebOrganics|User WebOrganics]] The Microformats wiki has hcards on its user pages.
* [http://www.ontwerpkliniek.nl Ontwerpkliniek - Bureau voor Visuele Identiteit] uses the hCard contact information at the frontpage and the contact page.
* [http://www.instantdes.com L'instant des...] uses the hCard format for all photographers published on this collective photoblog.
* the mediadesigner groupblog [http://www.pixeltapete.de Pixeltapete] uses the hCard for the contactinformation of the authorpages of [http://www.pixeltapete.de/alex Alex] and [http://www.pixeltapete.de/carsten Carsten] and also for the [http://www.pixeltapete.de/kontakt imprint]. [http://www.pixeltapete.de Pixeltapete] uses its own [http://www.pixeltapete.de/2007/11/hcard-sidebarwidget-fuer-wordpress/ hcard widget] for wordpress sidebars.
* [http://www.thorsten-ott.de Thorsten Ott] uses hCard format for the contact section of his online resume.
* [http://rosebleed.net/ Rosebleed] supports [[hCard user profiles]] - your profile URL is <nowiki>http://rosebleed.net/users/profile.php/</nowiki> followed by your username, e.g. [http://rosebleed.net/users/profile.php/silvermoon82 silvermoon82].
**'''Fixed''' profiles now explicitly mark up 'n' where possible, otherwise omits it
* [http://www.whitepages.com WhitePages.com] Now WhitePages.com main implemented hCard on all its listings. Over 120 million hCards! Includes work information.
* [http://www.warmoth.com Warmoth Guitar Products] features hCard contact information in two places, [http://www.warmoth.com/customerservice/customer.cfm?fuseaction=order How To Order] and all of the [http://www.warmoth.com/catalog Warmoth E-Store]
* [http://www.bbc.co.uk/worldservice/bangladeshboat BBC World Service Bangladesh River Journey] a social network mashup, with hCard & other microformats. See [http://dharmafly.com/blog/bangladeshboat Dharmafly blog discussion].
* [http://www.amants-du-chocolat.net/ ACCP:Les Amants du Chocolat de la Couronne Parisienne] uses hCard on their contact page and in the chocolate maker they've reviewed.
* [http://www.accountviewsoftware.nl/ AccountviewSoftware.nl] makes use of hCards for the dealer directory [http://www.accountviewsoftware.nl/dir/ (directory)]
* [http://www.crystalvision.co.il/ CrystalVision] uses hCard on their contact page and in the footer throughout the site.
* [http://www.joshuamcginnis.com Joshua McGinnis] uses hCard to display his contact information to potential clients.
* [http://www.bo.ingv.it/contents/INGV-Bologna/Staff.html INGV Bologna] implemented hCards for staff-members, marked-up as HTML table-rows ([[include-pattern]] also used to add organization-name and fax-number to each hCard).
* [http://www.lefora.com Lefora] is a free forum hosting site (using custom forum software). Every user's profile contains an hCard. (Example forum for testing: [http://funstuff.lefora.com funstuff.lefora.com])
* [http://theultimates.whitepages.com WhitePages.com] A special version of whitepages.com has all its listings marked up in hCard.
* [http://piermontweb.com/contact/ Piermont Web Design] uses hCard on its contact page.
* [http://www.ie.asm.md/en/ The Institute of Power Engineering] of the Academy of Science of Moldova. First Moldavian site using hCards on staff pages, e.g [http://www.ie.asm.md/employees/oleschuk-valentin/]
**Also in Russian: [http://www.ie.asm.md/employees-ru/sit-michail-lvovich/] and Romanian: [http://www.ie.asm.md/angajati/chiorsac-mihail/]
* The good ship [http://styrheim.com/test/leonid.html Leonid Miloslavskiy] spotted in the North Atlantic
* [http://richi.co.uk/blog/2005/12/structured-blogging.html Richi Jennings] has put up his attempt
*[http://oberrycavanaugh.com O'Berry|Cavanaugh] has an organization hCard in the footer on every page as while as individual hCards on the [http://oberrycavanaugh.com/team.php Team] page.
* [http://fortisgc.com Fortis General Counsel], e. g. [http://fortisgc.com/joyce_lan_kim.html Joyce Kim's profile], uses hCard for profile and contact information.
* [http://peryplo.com Peryplo.com], e. g. [http://peryplo.com/personal/7e6786e711c6d051a39a1b7085f34955 Sample Page], uses hCard for Hotels, Gastronomy Places and services for tourists.
* [http://www.navitraveler.com/places/629/ NaviTraveler], e. g. [http://www.navitraveler.com/places/629/Lincoln_Memorial.html Lincoln Memorial], including [[geo|Geo]].
* [http://corewar.atspace.com/about.html sfghoul] has marked her contact info with [[hcard|hCard]]
* [http://www.zaadz.com Zaadz] uses [[hcard|hCard]] and [http://gmpg.org/xfn XFN] for friends on a user's profile page.
*[http://www.xoxiety.com/about.html Xoxiety] uses hCards on its about page, linking data from a within a block of text.
*[http://yedda.com Yedda] - Yedda provides hcard based identities on all of the people's profiles
*[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.
* [http://www.goldenglovepromotions.com/ Golden Glove Promotions] used hcards on the footer of every page to store contact information.
* Australian national news sites The Australian and Australian IT use hCard on their contact pages: [http://www.theaustralian.com.au/contactus The Australian (contact us)] and [http://www.australianit.news.com.au/contactus Australian IT (contact us)]
* [http://www.thekiwiholiday.com/ The Kiwi Holiday] uses hCards for [http://www.thekiwiholiday.com/view-hostels New Zealand Hostels], [http://www.thekiwiholiday.com/view-restaurants New Zealand Restaurants], and [http://www.thekiwiholiday.com/view-activities New Zealand Activities]. Also provides hCard "download to address book" functionality on listing detail pages, e.g. [http://www.thekiwiholiday.com/restaurant/tonys-steak Tonys Steak Restaurant]
* [http://www.qcindustries.com/ QC Industries Conveyors] uses hcards to store contact information in the site footer and in their [http://www.qcindustries.com/news/press-releases/ press releases].
* [http://www.confuciusinstitute.ac.uk/ The Confucius Institute for Scotland at the University of Edinburgh] has their used a hcard to store contact information in the footer of the page.
* [http://admnj.com/ Affiliated Direct Mail] is a New Jersey based direct mail company that has their contact information and footer in hCard format.
* [http://www.golfdigest.com/ Golf Digest] now supports hCard in its [http://www.golfdigest.com/courses/places Course Finder] detail pages. [http://www.golfdigest.com/courses/places/2483 example]
* [http://dev.opera.com/authors/ Dev Opera] Opera's developer site uses hCards on the author details pages.
* [http://chrischerry.name/ Chris Cherry's contact page with his hCard]
* [http://www.kiteboarder.com.au/php/search.php www.kiteboarder.com.au] A new Australian kiteboarding portal. Microformats have been used so that users can export the shops <s>directly to outlook</s>. I was able to learn microformats through the Media 2007 conference in London. Author: Damien King
* [http://krevi.dk/ KREVI] A Danish research institute. Using hCard in the footer of each page and on staff list. This is the first known danish website from the public sector of Denmark using microformats.[http://krevi.dk/om-krevi/organisation/medarbejdere example staff list]
* [http://www.hss.ed.ac.uk/web-team/ College of Humanities and Social Science Web Team's site], University of Edinburgh uses a hCard in the footer of each page.
* [http://www.theglobeandmail.com/ globeandmail.com] Canada's National Newspaper uses an hCard for their contact information.
* [http://www.logisteam.pl/ Krzysztof Rucinski] uses an hCard for his contact details on [http://www.logisteam.pl/kontakt.html Logisteam keylogger contact] page.
* Creation design & 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]
* [http://www.thomsonlocal.com/ ThomsonLocal.com], major UK business directory publisher, use hcard on the search results and company information pages.
* [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.
* [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.
* [http://www.feike.de/Kontakt.html Feike Contact] has a hCard on to top of the page.
* [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 cityguide page, and you can also find some hreviews as well (like on the [http://www.londondrum.com/hotels/athenaeum.php Athenaeum Hotel page])
* [http://www.regels-stadskanaal.nl/ Regelingenbank Stadskanaal] has a hCard on each page, containing Geo-information too.
* [http://www.tomstone.se Tom Stone - Trollkarl] has a hCard in the footer of each page of the site.
* [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.
* [http://twitter.com Twitter] uses hCard for user information (along with [http://ihack.us/2007/05/14/twitter-gets-microformatted/ several other microformats])
* [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.
*[http://www.pats.ua.ac.be/group PATS Group Members] uses hCard to mark up member contact information.
*[http://couchsurfing.com CouchSurfing] has limited information in hCard available on members' profiles (such as [http://www.couchsurfing.com/people/guaka Guaka's]).
* [http://kpumuk.info Dmytro Shteflyuk] uses an hCard on his [http://kpumuk.info/contact/ contact] and [http://kpumuk.info/curriculum-vitae/ curriculum vitae] pages.
* 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]
* [http://people.cs.uchicago.edu/~mpschaef/index.html Merrick Schaefer] is psyched to use hCard on his homepage for his contact info.
* Christian Hess (from San JosÃ©, Costa Rica) has an hCard in his [http://www.hess-cr.com home page], [http://www.hess-cr.com/utilidades/correo.shtml#postal contact] and [http://www.hess-cr.com/secciones/curriculum/datos.shtml personal rÃ©sumÃ©] pages (all in Spanish). He also recommends using the [https://addons.mozilla.org/es-ES/firefox/addon/4106 Operator] extension in Firefox to check them out.
* [http://www.JamPlanet.com Jam Planet] uses hCard in Contact Us page; application can generate hCard for a contact.
* [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].
* [http://www.buy-our-honeymoon.com/ Buy Our Honeymoon], a [http://www.buy-our-honeymoon.com/registry honeymoon registry] service, uses hCard in their [http://www.buy-our-honeymoon.com/contact Contact Us] page.
* '''W3C webmaster''' [http://www.w3.org/People/Jean-Gui/ Jean-Guilhem Rouel] now has an hCard.
* [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]
* [http://david.weekly.org/ David Weekly] has added an hCard to his home page for himself.
* [http://ficlets.com/stories/12 Ficlets] story page uses hCard for author bio.
* [http://redmonk.com/contact/ RedMonk Contact page] uses hCard for RedMonk firm as well as each analysts.
* [http://source.ibegin.com/ iBegin Source] uses hCard to identify business information for all 10.5+ million businesses listed.
* [http://cloudislands.com/contact.php Cloud Islands] uses hCard for our Contact Info.
* [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])
* [http://www.giraffo.de giraffo.de] has different hCards on every page (+ geo in "kontakt")
* [http://www.enap.com ENAP, Inc.] lists the HR Contact in hCard format on the [http://www.enap.com/career.aspx Career Opportunities] page.
* [http://sxsw07.conferenceer.com/people Conferenceer] lists panelists and participants to the 2007 South by Southwest interactive conference in hCard format
* [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.
* [http://www.wikiservice.at/fractal/wikidev.cgi?FR/EveMoreau ValÃ©rie-Eve Moreau] has an hCard on her wiki-homepage.
* [http://en.wikipedia.org/wiki/St_George%27s_Minster%2C_Doncaster St George's Minster, Doncaster, on Wikipedia]
* AOL Journals publishes hCards for authors. [http://journals.aol.com/carowill/whats-happening Example]
* Ian McKellar's [http://ian.mckellar.org/ home page] is an hCard that's styled to look like a business card.
* [[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&id=FR/MicroFormats/ChristopheDucamp edit it]. Any suggestions welcome.
* [http://www.matthewwest.co.uk Matthew West] has an hCard on his [http://www.matthewwest.co.uk/email contact] page.
*[http://www.webmaster.waw.pl PaweÅ Wrzosek] Freelance webdeveloper`s portfolio
*[http://www.stanford.edu/ Stanford.edu] hCard markup is included in the footer of the homepage and all subsequent pages within the /home directory.
*[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.
* [http://www.qwertycars.co.uk/garages/mechanics-near-tadworth-kt20.aspx UK Car Garages] Address of car mechanics in the UK, in hCard format.
* [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.
* [http://www.pointermix.com Pointermix Design] uses the hCard format.
* [http://eight6.com/contact/ eight6]'s contact page uses the hCard format.
* [http://www.raveaboutit.com.au Rave About It]'s business listings use the hCard format.
* [http://optics.org/cws/Contact/OurTeam.do optics.org]'s team page.
* [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.)
* [http://seattleu.edu Seattle University] uses hCard on it's front page and most pages that share an official template.
* [http://www.josemarti.waw.pl Jose Marti XXII Secondary School in Warsaw] includes hCard on Contact and About Author sections
* [http://www.jaama.co.uk Jaama] have their company details as a vCard download on their [http://www.jaama.co.uk/Contact.aspx contact] page.
* [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]
* [http://jc-development.co.uk/ JC's Development] has company contact details as hCard.
* [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]
* [http://www.xlntads.com XLNTads] has their contact information marked up in hCard, as well as their development schedule/timeline in hCalendar
* [http://derrick.pallas.us Derrick Pallas] tells people to look for him here.
* [http://bluemonkcreative.com/contact/ Bill Turner] adds an hCard to the contact page of his freelance business' website.
* [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.
* [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].
* [http://www.boogdesign.com/aboutus.html boogdesign.com] has added hCard markup on the contact page.
* [http://www.gptg.org/ Great Places To Golf], hCards for golf clubs around the world, e.g. [http://www.gptg.org/club/12/]
*[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.
* 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]].
*[http://wizardishungry.com/blog/ wizardishungry/blog] has the author's hCard in the footer of every page with a link to X2V.
* [http://www.walkerfineart.com Walker Fine Art Gallery] Most pages contain an hCard in the footer.
* [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.
* Scott Allan Wallick's hCard is [[User:ScottWallick|his user page]] and on his blog, [http://www.plaintxt.org/about/2/ plaintxt.org]
* [[User:Bob_Jonkman|Bob Jonkman's hCard]] '''on this 'wiki''''
* [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.
*OffshoreAgile.com, a subsite of Starsoft Development Labs, uses hCard in the [http://www.offshoreagile.com/company/contact/ Starsoft Contacts] and Media Inquiries sections
*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
* 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])
*[http://72ppi.us 72ppi], uses hCard in the footer.
*[http://www.csarven.ca Sarven Capadisli] uses hCard throughout the site (including user comments in articles).
* [https://www.urbanbody.com/information/contact-us Urban Body Men's Clothing] uses hCard for business locations and hCalendar for business hours.
* [http://www.iqair.us/ IQAir North America], uses hCard for contact information.
* [http://www.infoiasi.ro/ The website of the Faculty of Computer Science], "A. I. Cuza" University Iaşi, Romania uses hCard for each staff member.
* [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.
* 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.
* 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.
* [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
* [http://www.carolinemockett.com/design/about.aspx Caroline Mockett] has an hCard on her About Me page
* [http://wait-till-i.com Christian Heilmann] has a footer address using hCard
*[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.
* [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.
* [http://www.micatholicconference.org/ Michigan Catholic Conference] uses hCard for contact information in the sidebar.
* [http://www.adambunn.co.uk/ Adam Bunn] provides contact details in the sidebar using hCard.
* [http://www.belkin.com/pressroom/releases/uploads/10_10_06NotebookExpansionDock.html Belkin Press Releases] are using hCards for PR contacts and corporate offices.
* [http://mybank.com myBank.com] uses hCard for its listings of every branch of every FDIC-insured bank in the United States.
* [http://leftlogic.com Left Logic] uses hCard for embedded contact information.
* [http://inga-art.co.uk/artist Inga Scholes] uses hCard for contact information in the sidebar.
* [http://www.lussumo.com/ Lussumo] uses hCards on user profile pages in its open-source [http://www.getvanilla.com/ Vanilla] Discussions Forum software.
* [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.
* [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.
* 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.
* [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).
* [http://www.brown.edu Brown University] now uses hCard on the front page
* [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 & future contact pages for clients.
* [http://southamptonrubberstamp.com Southampton Rubber Stamp Company] now has hCard markup with a vCard download link on every page.
* [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 "Find"] 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.
* [http://dsingleton.co.uk/ David Singleton] has added a hCard to his blog.
* [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.
* [http://www.informatik.uni-hamburg.de/SVS/personnel/henrich/index.php Henrich C. Pöhls] has marked up his about page using hcard, including his PGP-Key that is stored in an abbr title, using class=key.
* [http://www.yalf.de Yalf Webentwicklung] has [http://www.yalf.de/kontakt contact information] available as hCard (and vCard).
* [http://www.zeldman.com/about/ Jeffrey Zeldman]. Jeffrey Zeldman has marked up his about page using hcard.
* [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.
* [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).
* [http://www.webdirections.org Web Directions]. hCard is used as contact information for the conference, while speakers are marked up with hCard.
* [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.
* [http://www.msiinet.com/contact/ MSI Systems Integrators] has its "Contact MSI" page encoded with hCards.
* [http://www.coolblue.nl/ Corporate website of Coolblue BV]. hCards were implemented in both the footer of each page, and in the "News" section for press contact information.
* [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.
* [http://2006.dconstruct.org/speakers/ d.Construct 2006 conference speakers list] is implemented using hCards.
* [http://local.yahoo.com Yahoo Local] now supports hCards for business and places in the search results
* [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.
* The [http://www.fuckparade.org Fâparade] website uses hCard, though I didn't find a type to distinguish mobile and landline phone numbers.
**Use <code>cell</code> for mobiles.
* [http://www.miranet.nl/contact.htm Miranet Webdesign] have added a hcard to their [http://www.miranet.nl/contact.htm 'contact' page]
* [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]
* [http://www.radiantcore.com Radiant Core] has their contact information [http://www.radiantcore.com/contact/ available in hCard].
* [http://www.mikerumble.co.uk/ Mike Rumble] has [http://www.mikerumble.co.uk/contact.html uploaded his hCard].
* [http://www.saumag.edu/ Southern Arkansas University] has its contact footer encoded as hCard
* [http://main.uab.edu/ University of Alabama at Birmingham] has its contact footer encoded as hCard
* [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)
* [http://main.uab.edu/shrp/ UAB School of Health Professions] uses hCard in its contact footer
* [http://green.carisenda.com/ Stephen Stewart] has his hCard on the front page of his weblog ('You are here' section)
* [http://www.direction.es/ Direction] uses hCard for contact information.
* [http://audiobank.tryphon.org AudioBank] uses hCard to display member informations.
* [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)
* [http://www.dougransom.com Doug Ransom] uses hCard for his financial advisory practice.
* [http://rubyandrails.org/usergroups/newcastle/members.html ncl.rb] uses hCard for contact information.
* [http://www.snowinteractive.com/ Snow Interactive] uses hCard for contact information.
* [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].
* [http://www.ndiyo.org/contact Contact information for the Ndiyo project]
* [http://www.pixelenvy.co.uk/ Pixel Envy] uses hCard for contact information on every page
* [http://stilbuero.de/contact/ Klaus Hartl] uses hCard in the sidebar for contact information (maybe easier to parse through delivering xhtml as xml).
* [http://charlvn.virafrikaans.com/contact Charl van Niekerk's hCard]
* [http://billy-girlardo.com/WP/ BillyBLOGirlardo] uses hCard for contact information.
* [http://www.hicksdesign.co.uk/ Hicksdesign] uses hCard for contact information.
* http://www.gr0w.com/articles/press/growsearch_launched_press_release/ - hCard in a press release for the press contact info
* http://www.redmonk.com/cote/archives/2006/03/testing_out_mic.html - hCard with explanation
* [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]]
* [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.
* [http://ChunkySoup.net/ ChunkySoup.net] has redesigned using hAtom 0.1 and hCards on the entire site -- by [[User:ChrisCasciano|Chris Casciano]]
* [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 > Syndication.
* [http://www.nearwhere.com/ Nearwhere.com] allow you to put an hcard on an interactive map.
* [http://www.brentozar.com/ Brent Ozar] added a [http://www.brentozar.com/contact.php contact] page hCard.
* [http://www.kerihenare.com/ Keri Henare] has rewritten his [http://www.kerihenare.com/contact/ contact] page hCard. Now using <code><object></code> instead of <code><img></code> for photo. (Thanks Brian Suda for updating the vCard converter)
* [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.
* [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
* [http://www.davidgagne.net/ David Gagne] has an hCard in his sidebar.
* [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.
* 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]
* 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&action=view&content=JonathanAquino profile] pages.
* [http://claimid.com/factoryjoe Chris Messina' ClaimID hCard]
* [http://factoryjoe.com/ Chris Messina' homepage]
* [http://flock.com/about Flock About]
* [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]).
* [http://www.gr0w.com/articles/press/growsearch_launched_press_release/ GrowSearch Launched (Press Release)] uses an hCard to provide Press Contact Point.
* 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].
* [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.
* [http://deadringrancor.livejournal.com/ Justin McDowell] used an hCard when [http://deadringrancor.livejournal.com/221332.html referring to a person in his blog post]
* [http://davecardwell.co.uk/cv/ Dave Cardwell] has included his hCard in his Curriculum Vitae.
* [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.
* [http://www.thefutureoftheweb.com/ Jesse Skinner] has written a simple [http://www.thefutureoftheweb.com/blog/2006/1/hcard tutorial with examples]
* [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.
* [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"])
* [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].
* [http://www.2sheds.ru Oleg "2sheds" 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])
* [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"])
* [http://weblog.200ok.com.au/ Ben Buchanan] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&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&format=search Ben's vCard] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&format=search Colin's vCard]
* WWF-Australia [http://wwf.org.au/about/contactdetails/ contact details page]
* [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]
* [http://amette.eu amette] uses the hCard format in a module of his TikiWiki powered blog and a more complete hCard on his [http://amette.eu/contact contact page]
* [http://staff.washington.edu/oren/weblog2/ Oren Sreebny] has an hcard on his blog main index template
* [http://www.cs.brandeis.edu/~zippy/ Patrick Tufts] has an hCard on his homepage.
* [http://ascii20.blogspot.com/ Mathias Kolehmainen and Jamie Taylor] have hCards on their weblog.
* [http://www.hoppsan.org/jamesb/blogger/ Barnaby James] has a hCard on his weblog.
* [http://esa-education.com/schools/map ESA Education] Uses hCards for their 100+ schools and each of the individual school sites.
* [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.
* [http://www.pierce.ctc.edu/ephone/ Pierce College] -- community college directory uses hCard on all individual directory entries.
* [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].
* 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.
* [http://www.musik-erber.de/ Musik-Erber] uses to present contact information at the sidebar
* [http://cdevroe.com/about/#contact Colin D. Devroe] uses hCard to display his contact information on his about page
* 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.
* [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.
* [http://www.vyre.com/company/contact-us/ VYRE] is a CMS development company with a "contact us" hCard
* [http://www.lefdal.cc/info.php Alf KÃ¥re Lefdal] uses hCard in the markup of his contact information
* [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
* [http://www.applianceman-repair-fortbend.com/ac-air-conditioning-repair-katy-tx.html Air Conditioning Katy TX] uses hCard in the footer of the air conditioning repair website. To view an example visit [http://www.applianceman-repair-fortbend.com/sugar-land-appliance-repair.html Appliance Repair Sugar Land]
* [http://kollitsch.de/ Patrick Kollitsch] has built his personal Profil as hCard
* [http://www.audiophile.pl/ Car Audio] uses the hCard in his contacts section.
* [http://www.hbs.edu/faculty/dspar/ Harvard Business School] has hCards on their faculty pages
* [http://openmikes.org/ openmikes.org] uses hCards for open mike venue addresses in its listing detail pages.
* [http://www.intertecnollc.com/ InterTecno, LCC] publishes an hCard on the home page and contact page.
* [http://canaltcm.com/ver/sobre-tcm Turner Classic Movies TCM Spanish website] has published contact details as a hCard
* [http://rejuvenation.com/ Rejuvenation] is now using hCard for contact information.
* [http://www.mattash.com/contact/ Matthew Ash] uses the hCard in his contacts section.
* [http://www.atbbuildinginc.com/ Kitchen Remodeling Detroit] uses the hCard in the footer section of the home remodeling website. To view an example visit [http://www.atbbuildinginc.com/kitchen-remodeling-farmington-hills.html kitchen remodeling farmington hills mi]
* [http://www.metrohomeimprovementsinc.com/ General Contractor Detroit] uses the hCard in the header section of the contractor website. To see example visit [http://www.metrohomeimprovementsinc.com/insulation.html insulation contractor detroit]
* [http://yarmouthguide.com/business.php Yarmouth Guide] uses hCard for each business details page.
* [http://www.merchantcircle.com MerchantCircle] has embedded an hCard in every one of their 15+ million US business listings.
* [http://citizenspace.us/citizens Citizen Space Citizens] is a list of tenants for a coworking space in San Francisco. The issue was raised that ''nicknames'' are usually located in the middle of ''fn'', which is not valid as per the [http://microformats.org/wiki/hcard-brainstorming#Implied_FN_from_N Implied_FN_from_N] rule. It seems that it should be possible, however, to include a ''nickname'' in the middle of an FN or even between a ''given-name'' and a ''family-name''.

* [http://www.brownbook.net The Brownbook - the open yellow pages] The Brownbook is a peer-produced (like a wiki, but not a using a wiki engine) local business search website. It Uses hCard to allow users to export local business contact details to Outlook or other desktop apps, plus for providing detailed maps from Google.
** Example of a search results page: [http://www.brownbook.net/business/search/?tag=hair+in+egham&x=21&y=4 Hairdressers in Egham]
*** '''suboptimal''': Adresses, e.g "2 Station Rd North, Egham, Surrey", are marked up as <code>street-address</code>
** Example of a single business's details [http://www.brownbook.net/business/view/122516 The Hair Emporium].
*** '''suboptimal''': Adresses, e.g "2 Station Rd North, Egham, Surrey", are marked up as <code>street-address</code>
* [http://www.Sylphen.com Sylphen] is a IT-solutions-provider and uses hCards on the [http://www.sylphen.com/content/kontakt/kontakt.htm Contact]
** '''invalid''' two of the three examples lack the required <code>fn</code> or <code>fn org</code> property
* [http://www.cosmotourist.com www.cosmotourist.com] and [http://www.cosmotourist.de www.cosmotourist.de] A new German and English portal around travel tips. Using hidden hCard for hotel listings, wherever address data is available.
**Hidden.
* [http://www.venncommunications.com/contact/ Venn] uses a hidden hCard on the contact page.
**Hidden.
* [http://www.last.fm Last FM] has hCards hidden on their profile pages e.g. [http://www.last.fm/user/Crok/?scrobbling=t1].
**Hidden.
* [http://krisswatt.co.uk/ Kriss Watt] has hidden an hCard his blog footer.
**Hidden.
* [http://www.fberriman.com/ Frances Berriman] has a hidden vCard in the footers of her website.
**Hidden.
* [http://www.candlescience.com/ CandleScience Candle Supply] added a hidden hcard sitewide.
**Hidden.
* [http://www.meryl.net/ Meryl K. Evans] has a hidden hCard on her homepage.
**Hidden.
* [http://www.highflyerscareers.com High Flyers Careers], India's first flight-crew placement agency uses microformats for their [http://www.highflyerscareers.com/corporate/ corporate information] page. Using standards couldn't be easier or better.
**Has honorific prefixes as part of "fn", rather than marked up separatley.
* Spotstor.com eg - [http://spotstor.com/] uses hCard on profile pages (where user has elected to show contact information).

* [http://www.naturalengland.org.uk/press/default.htm Natural England] (new UK government agency, formed 2006-10-01).
** No "fn" - which makes it invalid.
*[http://drop-off.co.uk G3:2] uses hCard with geo tags in the copyright and on the about me page
** Address data is hidden using CSS.
* [http://zdnet.co.uk/misc/contact/ ZDnet Contact Us Page] supports [[hcard|hCard]].
** by [http://www.subtleasafish.com/ James Myers] and [http://www.fromthefrontend.co.uk/2006/11/23/zdnet-uses-microformats/ David Long]
**Images and e-mail addresses are hidden; telephone numbers do not comply with [http://en.wikipedia.org/wiki/E.123 E.123]
* [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])
** (2005-09-27) PASSED, PASSED
** WARNINGS
*** uses 'n given-name' and 'n family-name' instead of nesting the given- and family- names inside the 'n'
*** has one 'tel' value with a bunch of values stuffed in
*** probably more problems --[[User:RyanKing|RyanKing]] 17:19, 5 Jan 2006 (PST)
* [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]
** 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)
* [http://landsbank.fo/#hCard Landsbanki FÃ¸roya]
** INVALID - using embedded RDF/XML invalidly

* [http://www.yellowpencil.com/contact/ Yellow Pencil] Using microformats to present company contact information
** First hcard has empty "fn" and no "n". "fn" should be with "org" -- [[User: ScottReynen |ScottReynen]] 21:29, 19 Jun 2006 (CST)

* [http://www.art-switch.com/ArtSwitch/contactUs.html Art-Switch Exchange Limited] uses hCard for their contact details on their contact page.
* [http://onyomo.com/ OnYoMo] uses hCard markup for all addresses listed in their local search results.
* [http://vcardplus.info/show.asp?uid=Z9959-06323 Greg Bays], the author of vCardPlus! has made his sites vCard display page hCard complaint.
* [http://www.rosenblittdentistry.com/contact.php Dr. Jon Rosenblitt] uses hCard icon with '''Add to Address Book''' link.
* [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].
* [http://shiftingpixel.com/about/the-artist shifting pixel photoblog] has published an hCard.
* [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
* [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 "Using hCards in your blog"].
* [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.
* [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.
** Inspired by this I thought to try the same for SVG at [http://barefoot-ceramics.com/find Barefoot] ...
** <img class="photo" style="display:none;" src="data:image/svg+xml;text,<?xml version='1.0' encoding='UTF-8' standalone='no'?><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'><defs id='defs3959' /><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' /></svg>" alt="Barefoot">
** Does it work?? Well it parses OK. Some automated tools replace the < 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.
* [http://cinematreasures.org Cinema Treasures] uses hCard to markup venue information for 10,000+ movie theaters.
* [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.
* [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
* [http://loadaveragezero.com/hnav/contact.php Douglas W. Clifton] added all types of contact information
* [http://eventful.com Eventful] publishes all of its venue information pages with embedded hCards.
* [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]
* [http://JackWolfgang.blogspot.com Jack L. Wolfgang II] has [http://jack.randomata.com/resume/ converted the addresses in his resume to hCards].
* [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
* [http://www.oliverbrown.me.uk/ Oliver Brown] has published his hCard.
* [http://www.paradigmproductions.org/contact/ Paradigm Productions] published a vCard as a <code>ul</code> (marked up by [http://www.linkingarts.com/ Peter Jacobson])
* [http://www.splintered.co.uk/ Patrick H. Lauke] has marked up [http://www.splintered.co.uk/about/ his contact info with hCard].
* [http://blah Paul Schreiber has published his hCard on [http://paulschreiber.com/about/?contact his about page].
* [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.
* [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.
* [http://www.windley.com/archives/2005/07/hcards_trying_o.shtml Phil Windley has published] [http://phil.windley.org/hcard.html his hCard].
* [http://www.go-curiosity.com/about.htm Piercarlo Slavazza] has published an hCard.
* [http://zooibaai.nl/ Rob Mientjes] has published his hCard on [http://zooibaai.nl/about/ his about page].
* [http://www.dumpsterrentalsdetroit.com/ Dumpster Rental Detroit] has published their hCard on the footer of every page see [http://www.dumpsterrentalsdetroit.com/ Kincaide Dumpster Rental].
* [http://rbach.priv.at/Contact Robert Bachmann] has published his hCard and [http://rbach.priv.at/Images/hcard a button].
* [http://blah Scott Reynen has published his hCard on [http://www.randomchaos.com/document.php?source=scott_reynen his profile page].
* [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.
* [http://www.wolfsreign.com Steven Ametjan] has published his hCard on [http://www.wolfsreign.com/about/ his about page].
* [http://tantek.com/microformats/2005/syndicate/speakers-list.html Syndicate - Speaker List] as a set of hCards
* [http://tagcamp.org/index.cgi?ContactList TagCamp contact list]
* [http://www.deadringerart.com/ The Brothers McDowell] have hCards at their Contact page.
* [http://twinsparc.com/ Twinsparc] put an hCard in the header and footer of all their pages.
* [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 Conference speakers page marked up with hCard]
* [http://www.uoguelph.ca/directory/ The University of Guelph] includes hCard info in its directory.
* [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!
* [http://www.cadforless.com/partners/ CADforless, Inc.] we listed our partners using hCard
* [http://avon.com/ Avon] - publishes all 40,000+ Avon representatives' contact info with hCard.
* [http://flock.com/about Flock About] page supports hCard microformat.
** by [[implementations#Flock|Flock]]
* [http://www.iowamilitaryveteransband.com/members/ Iowa Military Veterans Band]
* [http://www.nature.com/ Nature homepage], uses [[XOXO]].
** by [[implementations#Nature Publishing Group|Nature Publishing Group]]
* [http://concerts.shrub.ca/shows Sunnyvale House Concerts] supports hCard and [[hcalendar|hCalendar]].
* [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/139897 Mr T Natt] page.
* [http://www.monster-prague.cz/ Monster Prague Openings] supports hCard, e.g. home page, contact list to come.
* [http://www.vogelelaw.com/contact.html Colette Vogele] has an hCard on her contact page with many types of name and contact information. (Marked up by [http://www.talkingtiger.net Naomi Raine]).
* [http://www.fixya.com/repair/cars/us/ca/san_francisco FixYa] (the troubleshooting site) has an hCard (vCard) in the repair directory displaying information about all kinds service providers.
* [http://www.alive77.cn/ z.Yleo77] it's my blog, from now on,supports hCard, eg: article pages..
* [http://www.wfl-networks.co.uk/ WFL-Networks Computer Repair in Aylesbury] a localised IT Support company in Buckinghamshire, UK supporting hCard on its contact pages.
* [http://www.elcafedelcentre.com/index.html El Cafè del Centre] uses an hCard for his contact information in firts place.
* [http://www.petardos.org/index.php Petardos 4x4] uses an hCard for his contact information at the footer in all pages.
* [http://www.artimap.com artimap.com] uses vCards for helping the javascript in-page local search-engine.
* [http://www.handballkreis-koeln-rheinberg.de Handballkreis Köln/Rheinberg] uses hCard for contact informations of officials
* [http://www.evopapetarie.ro] uses hCard for contact page.
* [http://www.musiktagespflege-leichlingen.de Musiktagespflege Leichlingen] uses hCard for imprint and contact informations.
* [http://www.siam-property.com Siam Property Thailand] uses hCard for property consultants.
* [http://www.atbbuildinginc.com/ ATB Building Royal Oak MI] is using hCard on the contact page of their website.
* [http://www.badspiderbites.com/ Bad Spider Bites] uses hCard on their about page for customer submissions and contact information.
* [http://www.xn--mxacivya8br.net/ Φαψεβοοκ] Φαψεβοοκ uses hCard on their about page for customer contact information.
* [http://www.xn--oxaagxsa.com.gr/ Γοογλε] Γοογλε uses hCard on their [http://www.γοογλε.com.gr/terms/about-us/ about page] for their name and URL.
** one valid hCard, one invalid one.

== examples by category ==
'''Want hCard?''' Get started with writing an [[hcard|hCard]] using the [http://microformats.org/code/hcard/creator hCard creator] to write up some contact information, [[validators#hCard|validate]] and publish it, or following the [[hcard-authoring|hCard authoring tips]] to add hCard markup to your current site. Check out this section for similar examples of types of pages that benefit from hCard markup.

This section organizes examples into several rough categories as follows. If an example fits in more than one category, use the *last* matching category in this list that matches the specific hCard example(s) in the wild that you are trying to categorize.
# '''[[hcard-examples-in-wild#Individuals|Individuals]]''' - one card per person, perhaps sort alphabetically by "family-name". People with their own hCards (typically) on their own site.
# '''[[hcard-examples-in-wild#Organizations|Organizations]]''' - one card per organization, alphabetical by "fn". Organizations with their own hCard(s) (typically) on their own site.
# '''[[hcard-examples-in-wild#Institutions|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 "org" with perhaps a few individuals listed in a single sub-bullet, comma delimited, sorted by "family-name".
# '''[[hcard-supporting-user-profiles|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 company / service name.
# '''[[hcard-examples-in-wild#Online_Venues|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 "fn".
# '''[[hcard-examples-in-wild#Event_Speakers|Event Speakers]]''' - event pages where the speaker for the event is marked up with hCard.
# '''[[hcard-examples-in-wild#Speakers_Listings|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 "family-name".
# '''[[hcard-examples-in-wild#Group_Blogs|Group Blogs]]''' - blogs with multiple authors marked up with hCard
# '''[[hcard-examples-in-wild#Wiki_Templates|Wiki templates]]''' - community wikis that have templates that automatically generate hCards on pages
# '''[[hcard-examples-in-wild#Authors|Authors]]''' - pages about some other thing, such as books, perhaps reviews etc., which have marked up their authors with hCard
# '''[[hcard-examples-in-wild#Search_Results|Search Results]]''' - results pages from search engines (either generic or for people/organizations) that return people marked up with hCards.
# '''[[hcard-examples-in-wild#Listing_Contact|Listing Contact]]''' - contact information for a listing like a job posting, for sale offering, etc.

In addition there is a separate "[[hcard-examples-in-wild#UTF8_Examples|UTF8 Examples]]" 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.

As each section itself become quite large (we might be there already, once we sort through the above "Reviewed Examples"), 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.

=== Individuals ===
Groupings alphabetically by "family-name".

Nicely styled:
* [http://www.jaredhanson.net/ Jared Hanson]'s home page has a beautiful hCard with numerous ways of contacting him, and live updating of his online status on various messaging networks (uses javascript).
* [http://rogieking.com/#contact Rogie King]'s contact info is marked up with hCard and very nicely styled.
* [http://timvandamme.com/ Tim Van Damme]'s home page is a beautiful hCard.
* [http://paultarjan.com Paul Tarjan]'s home page has hCard and is a rel="me" hub
** needs a few minor fixes: http://tr.im/hctvd (links to hCard validator results)

Simple web pages (sorted by family name)
* [http://dbaron.org/ David Baron]'s home page is marked up with hCard.
* [http://abernier.name Antoine Bernier]'s UID hcard:
** Dynamic VCF download link (through [http://suda.co.uk/projects/microformats/hcard/get-contact.php?uri= hcard parser])
** Dynamic QRcode (through [http://microform.at/hcard2qrcode/ hcard2qrcode])
** Dynamic avatar (through [http://www.gravatar.com/ Gravatar])
** [http://wiki2008.openid.net/Delegation openID] ready
** [http://hcard.geekhood.net/?url=http%3A%2F%2Fabernier.name valid]
* [http://tantek.com/ Tantek Çelik]'s home page includes an inline author hCard at the bottom of the page.
* [http://christophertcressman.com/ Christopher T. Cressman] put his contact details on [http://christophertcressman.com/ Who is Chris Cressman?] and marked them up with hCard.

* [http://monkinetic.com/ Steve Ivy] with hCard and [http://monkinetic.com/about-this-site.html about page] with the usual suspects + XFN on 'url's, photo.
* [http://www.ryanmjones.com Ryan Jones]'s home page is also an hCard.
* [http://factoryjoe.com/hcard.html Chris Messina] has a page set aside with his contact details.
* [http://madebyjordan.com/ Jordan Moore]'s blog contains an inline hCard.
* [http://blog.roub.net/ Paul Roub] has an hCard for himself on his blog's home page.
* [http://www.w3.org/People/Smith/hcard/ Michael(tm) Smith has an hCard] on a page linked from [http://www.w3.org/People/Smith/ his W3C staff page]
** note lack of 'n' property but explicit use of 'given-name' and 'family-name' - more evidence we should drop the 'n' requirement (flatter is better) [[User:Tantek|Tantek]] 04:10, 6 May 2011 (UTC)
* Patrick Trettenbrein is the operator of [http://skateboardspot.info/ skateboardspot.info] and uses hCard on its [http://skateboardspot.info/cat/about#operator "about" page] for his contact info.
* [http://blogs.msdn.com/cwilso/ Chris Wilson] has an hCard for himself on [http://blogs.msdn.com/cwilso/about.aspx his about page].
* ...

Hidden! Invisible data is strongly discouraged, these examples have been grouped here in the hopes that the authors will someday make their hCards visible:
* [http://ajbrown.org/ A.J. Brown]'s home page includes a hidden hCard at the bottom of the page.

Former. URLs that seem to have broken.
* <nowiki>http://tomleo.com/about.html</nowiki> Tom Leo's about page had an hCard. (missing as of 2009-08-23)
* <nowiki>http://bogomil.info?l=en/</nowiki> Bogomil Shopov had an hCard for himself (missing as of 2011-125)

=== Organizations ===
Sites for specific organizations with their own hCard on home page, or contact/about page(s). Grouped by country, sorted alphabetically. When this section gets too big we can make a separate business directory page.

==== US orgs ====
* [http://www.pinewoodgroup.com/ Pinewood Shepperton plc] includes an hCard on their home page, and several more upon clicking their "Contact Us" button (found via [http://www.thedrum.co.uk/news/2011/09/07/25776-pinewood-studios-launch-website-created-by-multiply/ 2011-09-07 Pinewood Studios launch website created by Multiply] [[press]] article).
* [http://www.primerica.com/public/contact.html Primerica] uses hCard on "Contact Primerica" page for home office address.
* [http://RippleFxInc.com/ RippleFxInc.com] including both [http://blog.RippleFxInc.com/ Ideas Blog @ Ripple FX] and [http://wiki.RippleFxInc.com/ Knowledge Wiki @ Ripple FX] use hCard markup and allows for vCard download on their page footers; because they care, the same is standard on every site they design.
* [http://www.sfmoma.org/ San Francisco Museum of Modern Art] (SFMOMA)'s home page and pages in general have their address marked up in hCard.

==== Australia orgs ====
* [http://www.brdatasystems.com.au/contact-us.html B&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.

==== England orgs ====
* [http://www.alexandersremovals.co.uk/ Alexanders Removals] uses hCard for business address and contact details.
* [http://www.confidence2smile.co.uk/ Confidence 2 Smile] uses hCard for business address and contact details.
* [http://www.dovetaildental.co.uk/ Dovetail Dental] uses hCard for business address and contact details.
* [http://www.electricalcerts.co.uk/ Electrical Certs] uses hCard for business address and contact details.

==== Germany orgs ====
* [http://www.hsg-kl.de/impressum/index.php Hohenstaufen Gymnasium Kaiserslautern] has hCard contact info
** '''suboptimal''': <code>adr</code> subproperties are not recognized due to lack of explicit "adr" property.
*** evidence that has helped drive the flatter design of [[microformats-2]] including h-card which permits adr properties, e.g. 'street-address' directly inside the hCard instead of requiring an explicit 'adr' in the hierarchy. - [[User:Tantek|Tantek]] 01:46, 17 May 2012 (UTC)

==== Georgia orgs ====
* [http://www.serviceklimatistikon.gr/contact/ magiClima's contact page] uses for customer contact information.

==== Netherlands orgs ====
* [http://www.kdvkabouterbos.nl/ Kinderdagverblijf Kabouterbos], a day care / nursery that uses an hCard for their contact information (footer).

Mis-sorted - this should be moved to a search results section:
* [http://www.michrome.com Michrome Marketing Lists (UK)] use hCard on all their search result data. For example, [http://michrome.com/free-leads/162-Bradford-BD9 Startup Companies in Bradford].

Old: (these sites used to have hCard, some may have gone offline)
* <nowiki>http://technorati.com Technorati</nowiki> (2004-2011)
** <nowiki>http://technorati.com/about/ about, http://technorati.com/press/ press, and http://technorati.com/about/contact.html contact</nowiki> pages with hCard and have "Add to Address Book" links with the <nowiki>http://feed.technorati.com/contacts/ Technorati Contacts Feed service</nowiki>.
* <nowiki>http://technorati.jp Technorati Japan</nowiki> (2004-2011)
** <nowiki>http://technorati.jp/about/contact.html contact</nowiki> page marked up with hCard.

=== Institutions ===
* Mozilla's WebFWD [https://webfwd.org/about/experts/ experts] and [https://webfwd.org/about/team/ team] pages have hCards, including [[microformats-2]] h-card markup.
* [http://conferences.oreillynet.com/contacts.csp O'Reilly's Conferences Team page] has hCards for their team (~14) with a link to "Download the below contact info in vcf format" that uses the old Technorati contacts feed service to convert the hCards into vCards.
** needs updating to use [[H2VX]] instead of Technorati
** '''suboptimal''': The "org" shouldn't be hidden with "display:none". Instead, use the [[include-pattern]] to include the "org" from text elsewhere on the page (to avoid duplicating the text).

'''with some problems:'''
* The [http://www.ibm.com/contact/employees/ IBM Employee Directory] returns hCards in its query results
** E.g. [http://www.ibm.com/contact/employees/servlets/lookup?country=us&language=en&search_country=all&lastname=Kaply&firstname=Michael search for Michael Kaply],
** but with some problems:
*** '''invalid''': no "fn" (would be addressed by the [[hcard-brainstorming#Implied_FN_from_N|implied fn from n proposal]])
*** '''suboptimal''': adr has no children and thus is not providing any data (may be addressed by the [[hcard-brainstorming#implied_adr_subproperties|implied adr subproperties proposal]])
* [http://www.boltonmuseums.org.uk Bolton Museum and Archive Service] uses hCard on its
**[http://www.boltonmuseums.org.uk/about/contact/ Contacts] page
***'''invalid''': Several have no "fn"
**and on each of its visitor attractions pages e.g. on the [http://www.boltonmuseums.org.uk/visiting/findhallthwood/ Hall i' th' Wood location page].
***'''suboptimal''': "email" and "tel" properties mistakenly include "Email:" and "Telephone:" labels.
* [http://soap.stanford.edu/ Stanford Online Accessibility Program] has implemented hCard on every page
** '''suboptimal''': positioned off screen via CSS
* [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.
** '''invalid''': Example has 1 (out of 3) invalid hCard due to lack of "fn".
* [http://www.alexa.com Alexa Internet] marked up its [http://www.alexa.com/site/company/managers managers' page] with hCard.
** '''suboptimal''': job "title" is included inside within "fn" property.
* ...

old:
* 2005-2010(?) <nowiki>http://technorati.com/about/staff.html Technorati's Staff page had hCards for its employees (~31)</nowiki>
** E.g. <nowiki>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, etc.</nowiki>

=== Online Profiles ===
* See [[hcard-supporting-profiles]].

=== Online Venues ===
* [http://www.airfix.com/stockists-and-distributors/ Airfix Stockists and Distributors], e.g. [http://www.airfix.com/stockists-and-distributors/?postcode=b1+1bb&root_rid=1&search.x=0&search.y=0&search=search]
**'''suboptimal''': <code>street-address</code> contains street address, locality and region (e.g. "99 Hobs Moat Rd, Solihull, W. Midlands")
**'''suboptimal''': <code>postal-code</code> and <code>country-name</code> include preprended commas
**'''suboptimal''': <code>fn</code> is used; should be <code>fn org</code>
* [http://citysearch.com/ Citysearch] supports hCard (e.g. [http://seattle.citysearch.com/profile/10767458/seattle_wa/tulio_ristorante.html Tulio Ristorante in Seattle] and [http://sanfrancisco.citysearch.com/profile/46396865/san_francisco_ca/four_barrel_coffee.html Four Barrel in SF]) nested inside an [[hreview-aggregate]].
* [http://www.easthampshire.org/ easthampshire.org] - hCard on events and events map - e.g. http://easthampshire.org/eventdetail/wine_society_evening/1372606 and http://easthampshire.org/eventmap/wine_society_evening/1372606 built by [http://www.callendercreates.com Callender Creates]
* [http://rinklinks.ca/ RinkLinks.ca: A Comprehensive Rinks and Arenas Directory for North America] supports an hCards for listings in their directory.
* [http://www.sydneydirectory.org/ Sydney Directory Wiki] supports hCard and geographical coordinates for locations, e.g. the [http://www.sydneydirectory.org/index.php/Opera_House Sydney Opera House].

=== Event Speakers ===
* [http://fluentconf.com/fluent2012 O'Reilly fluent conference 2012] sessions, e.g. [http://fluentconf.com/fluent2012/public/schedule/detail/25831 Federated Wiki Mashes Data in Your Browser] have speakers marked up with hCard.
* ...

=== Speakers Listings ===
* ... lots more to add from events since 2007, e.g. every dConstruct etc.

==== 2007 ====
[[to-do]]: check 2007 [[presentations]] as they likely contain links to conferences that marked up their speakers page(s) with hCard.
* 09: [http://2006.dconstruct.org/speakers/ d.Construct 2007 speakers]
==== 2006 ====
[[to-do]]: check 2006 [[presentations]] as they likely contain links to conferences that marked up their speakers page(s) with hCard.
* 09: [http://2006.dconstruct.org/speakers/ d.Construct 2006 speakers]
==== 2005 ====
[[to-do]]: check 2005 [[presentations]] as they likely contain links to conferences that marked up their speakers page(s) with hCard.
* 12: [http://tantek.com/microformats/2005/syndicate/speakers-list.html Syndicate - Speaker List] (hCarded version hosted at tantek.com)
* 10: [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 Conference 2005 -- Speakers] (hCarded version hosted at tantek.com)
* 09: [http://web.archive.org/web/20051102094339/we05.com/ Web Essentials 05] - [http://web.archive.org/web/20051102094339/we05.com/presenters.cfm The Presenters] <nowiki>original URL: http://we05.com/presenters.cfm</nowiki> (appears to have stopped working as of 2007-12-18, perhaps earlier). Web Essentials 2005 (we05) was the [http://tantek.com/log/2005/10.html#d06t1720 first conference to adopt hCard and hCalendar] on their website and marked up all their presenters with hCard.

=== Group Blogs ===
* The [http://www.ibm.com/shortcuts/ IBM Shortcuts Podcast] has authors marked up with hCard but has some problems:
** '''hidden''': The root hCard element as well as every property contained therein is made invisible through a style attribute containing "position:absolute; visibility:hidden".

=== Wiki Templates ===
* Wikipedia
**Wikipedia-EN
*** People. 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 "infobox scientist; there's also "infobox military people", "infobox musician" and so on, almost ad infinitum). DoB is only included if it's entered using a birth-date template, not as raw text.
*** Places/orgs. 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.
***[http://en.wikipedia.org/wiki/Category:Templates_generating_Geo Wikipedia templates generating Geo]
****'''hidden''' - for example [http://en.wikipedia.org/wiki/List_of_Minnesota_State_Parks List of Minnesota state parks]; [http://en.wikipedia.org/w/index.php?title=Alberta_Highway_60&diff=prev&oldid=157308650 Alberta Highway 60]
****Note also removal of hCard properties, e.g. [http://en.wikipedia.org/w/index.php?title=List_of_Gaudi_Buildings&diff=prev&oldid=157704557 List_of_Gaudi_Buildings]
*** 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]
***Unfortunately, [http://en.wikipedia.org/w/index.php?title=Template:Infobox_Protected_area&diff=prev&oldid=152308153 other editors are already breaking some of the implementations on Wikipedia]; e.g. [http://en.wikipedia.org/wiki/Grand_Canyon_National_Park Grand Canyon National Park]; [http://en.wikipedia.org/w/index.php?title=List_of_islands_of_Argentina&diff=prev&oldid=155590535 removal of "region" attributes]
*** <s> 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]</s>
**Wikipedia-UK (Ukranian) 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]
* Wikiqueer
** [http://www.wikiqueer.org/w/Category:Templates_generating_hCards Wikiqueer templates generating hCards]
** [http://www.wikiqueer.org/w/Category:Templates_generating_microformats Wikiqueer templates generating microformats] in general

=== Authors ===
* [http://time.com TIME.com] marks up articles with hAtom including authors with hCard, e.g. [http://techland.time.com/2012/05/10/like-to-brag-on-facebook-or-twitter-thats-because-self-disclosure-is-like-eating-and-sex-says-study/ Like to Brag on Facebook or Twitter? That’s Because Self-Disclosure Is like Eating and Sex, Says Study]
* [http://lazylibrary.com LazyLibrary] uses author hCard's on every book page. Example: [http://lazylibrary.com/book/0751370576]
** '''suboptimal''' [http://lazylibrary.com/book/0751370576 Example] has an fn of "Dorling Kindersley, David West Reynolds" which should be split into two hCards! (site would also benefit from hReview).
* ... many more (e.g. see unsorted list above, verify and move here)

=== Search Results ===
* [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.
** '''invalid''': attempt to use Implied-N optimization where that's not possible,
** '''suboptimal''': honorific-prefix could be explicitly marked up
*** Error appears for external users only. Won't be fixed any time soon. -- [[User:PhilWilson|PhilWilson]] 00:03, 28 Jan 2006 (GMT)
* [http://www.yourtraces.com/social_index.php YourTraces SocialSearch] Try ''high results'' (hohe Relevanz) to get only websites marked with hcard as a person.

=== Listing Contact ===
Contact information for listings, e.g. job postings, items for sale, etc.
* [http://bestsecurityjobs.co.uk/ Best Security Jobs] is a UK jobs board that uses hCard on the homepage for job listings.
* [http://seogadget.co.uk/search-marketing-executive-upto-30k-portsmouth/ search marketing executive] published by [http://seogadget.co.uk/ SEOgadget].
** '''invalid url property''' - href of the url property element lacks <nowiki>http://</nowiki>, thus being invalid and linking to a non-existent relative URL.
** '''invalid XHTML''' - W3C validator reports this page as [http://validator.w3.org/check?uri=http://seogadget.co.uk/search-marketing-executive-upto-30k-portsmouth/ XHTML 1.0 Transitional] (109 errors as of 2009-08-20).

===UTF8 Examples===
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. Sorted roughly alphabetically (per Unicode).
* [http://imageconcept.ru/contacts.html ImageConcept (ИмиджКонцепт)] embedded UTF8 encoded hCard with Russian characters in «Contacts» page of website.
* [http://sphinx.net.ru/author/ Dmitry Dzhus] embedded his UTF8 encoded hCard with Russian characters in Â«AuthorÂ» page of his website.
* [http://ecdlweb.com/ ECDLWeb.com] encodes hCard and Geo information of ECDL and ICDL test centres in UTF-8. Test case for Central European ([http://ecdlweb.com/en/czech-republic/sps-ceska-lipa Czech], [http://ecdlweb.com/en/hungary/athene-idegenforgalmi-informatikai-es-uzletemberkepzo-szakkozepiskola Hungarian] etc.) and [http://ecdlweb.com/en/belarus/belhard Cyrillic] characters.
* [http://tantek.com/ Tantek's Thoughts] encodes Ãelik as inline UTF8.
* [http://technorati.jp/about/contact.html Technorati Japan contact information] encodes Japanese as inline UTF8.
* [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))

==== nickname only ====
These UTF8 examples only have UTF8 for the "nickname" property and are thus are a bit easier for testing than the previous examples.
* Various Wikipedia-EN articles, e.g. the "nickname" 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)

===non-HTML examples===
* [http://dannyayers.com/misc/microformats/hcard-svg Danny Ayers' SVG hCard demo]

=== missing ===
Examples that used to have one or more hCards but now don't seem to have any. If you do find one, please include direct links to at least two (assuming there are two or more) pages at the referenced site that have one or more hCards.
* [http://mapquest.com Mapquest] now supports hCards for business and places in the search results (e.g. [http://www.mapquest.com/maps/map.adp?searchtype=address&country=US&searchtab=home&formtype=address&cat=Whole+Foods&city=san+francisco&state=ca search for Whole Foods in San Francisco])
** appears to be missing hCards as of 2008-09-07

== related pages ==
{{hcard-related-pages}}
* [[hcalendar-examples-in-wild|hCalendar examples in the wild]]

hcard-examples-in-wild

2015-05-05T10:56:50Z

TomMorris: we can do without the promotional copy...

<entry-title>hCard Examples in the wild</entry-title>
<div style="height:7.5em;text-align:center;font-weight:bold;font-size:larger">
<span style="padding:3em 0;float:left;width:33%">[[hcard-examples-in-wild#examples_by_category|Want hCards]]</span><span style="padding:3em 0;float:left;width:33%">[[hcard-examples-in-wild#new_and_uncategorized_examples|Have hCards]]</span>
</div>

This page is an '''informative''' section of the [[hcard|hCard specification]].

The following sites have published [[hcard|hCards]], and thus are a great place to start for anyone looking for examples "in the wild" for inspiration, or try parsing and indexing.

== new and uncategorized examples ==
'''Have hCard?''' If you have a site with hCard(s), add it to the top of this list. Include at least one URL to a page that includes actual [[hcard|hCard]] markup. Examples without direct links to pages with hCard(s) will be removed. Check back after a few days, to see if anyone has found any problems with the examples supplied. Note that examples may be categorized and moved to the grouped section below.

You may want to use these buttons on your pages with hCards. See [[buttons#hCard]] for any recent additions.

http://www.davidjanes.com/images/mf_hcard.png   http://www.boogdesign.com/images/buttons/microformat_hcard.png

* http://www.cadmap.co.uk/ Cadmap Land & Building Surveyors uses hCard markup on the footer of each page.
* [http://www.joob.sg JOOB Singapore] uses hCard markup in the juice content and juice product pages].
* [http://expertdent.ca/en ExpertDent dental clinics] uses hCard markup in the header as well as the contact section for its three dental care clinics].
*http://drcadieuxlangevin.com/ It is with great pleasure that we will answer all your questions!
* [http://www.us-inverters.com/ US-Inverters.com] uses hCard markup in many places, such as the home page, [http://www.us-inverters.com/ contact page] and [http://www.us-inverters.com/where-to-buy/china.php distributor pages].
* [http://www.henryandjames.co.uk/contact/ Henry & James Estate Agents] use hCard markup on their contact page.
* [http://wpoosc.com.au/ West Pymble Out of School Care] uses hCard markup for their physical address in the sidebar.
* [http://www.your-move.co.uk/ YOUR MOVE estate agents]uses hCard markup for branch addresses. Example: [http://www.your-move.co.uk/estate-agent/york.html York Branch Page]
* [http://telcoavi.es Telco Audio Vídeo e Ilumianción] uses hCards on the contact page. Example:[http://telcoavi.es/contacto.php Contacto]
* [http://nicolasbouliane.com Nicolas Bouliane - Conception de sites internet] uses hCards on the contact page as well as in the header and footer.
* [http://www.lslps.co.uk/ LSL Property Services]uses hCard markup for details of Press Contacts. Example: [http://www.lslps.co.uk/news Property News Page]
* [http://www.breaflorist.net/pages/Florist-La-Habra/display La Habra Florist] - Uses hCard markup in their la habra florsit page below.
* [http://iprefer.com/ I Prefer Guest Benefit Program] uses hCard for each property page. Example: [http://iprefer.com/luxury-hotel/Campinas/Royal-Palm-Tower/ Royal Palm Tower, Design Hotels in Campinas]
* [http://preferredhotels.com/ Preferred Hotels and Resorts] uses hCard for each property page. Example: [http://preferredhotels.com/luxury-hotel/Singapore/The-Fullerton-Hotel-Singapore/ The Fullerton Hotel Singapore, Luxury Hotels in Singapore]
* [http://www.binvisions.com/ CSS3 and HTML5 Blog] - uses hCard to get vCard of users who make comments on blog posts. Example: [http://www.binvisions.com/articles/seo-using-css-text-indent-or-images-for-logos/ CSS Text-Indent or Images for Logos in SEO?]
* [http://collectiverecyclers.com Collective Recyclers] - Uses hCard for contact details.
* [http://www.stylebar.de/ stylebar websolutions] Uses an hCard for the contact information on the right site in the website.
* [http://southpawed.com/ Steve Holland] uses hCard for his contact details.
* [http://sterlingdesignhotels.com Sterling Design Hotels] uses hCard for each property page on their website, e.g. [http://sterlingdesignhotels.com/design-hotel/Miami/Hotel-Urbano-AT-Brickell/ Hotel Urbano AT Brickell, Design Hotels in Miami]
* [http://sterlinghotels.com Sterling Hotels] uses hCard for each property page on their website, e.g. [http://sterlinghotels.com/smart-hotel/Hong-Kong/The-Fleming/ The Fleming, Smart Hotels in Hong Kong]
* [http://daniele.gobbetti.name daniele.gobbetti.name] uses hCard for his own profile. The template is released under CC-BY-SA and available on [https://github.com/danielegobbetti/about-me github]
* [http://www.sabzoo.de SABZOO.de] uses hCard for the about us page. Here is the direct link: [http://www.sabzoo.de/ueber-sabzoo/impressum.html About us]
* [http://www.coinspcgs.com Coins PCGS] uses hCard for the about us page. Example: [http://www.coinspcgs.com/p/about.html About PCGS Coins]
* [http://summithotels.com Summit Hotels and Resorts] uses hCard for each property page on the website. Example: [http://summithotels.com/luxury-hotel/Honolulu/Waikiki-Parc-Hotel/ Waikiki Parc Hotel, Luxury Hotels in Honolulu]
* [https://plus.google.com/ Google+] uses hCard for each user profile and company page. Example: [https://plus.google.com/112111196451586545452/ ReadWriteWeb profile page]
* [http://www.coatncast.de/ Coat'n Cast] has hCard formatted address information in the page markup, mainly to provide data to geolocation services.
* [http://preferredboutique.com/ Preferred Boutique] uses hCard for each property page on their website, e.g. [http://preferredboutique.com/luxury-hotel/Atlanta/TWELVE-Atlantic-Station/ TWELVE Atlantic Station, Luxury Boutique Hotels in Atlanta.]
* [http://www.last.fm Last.fm] uses hCard for event pages and user profile pages (however user profile hCard information is very incomplete and sub-optimal) e.g. [http://www.last.fm/event/1448900+She+-+Him+at+Millennium+Park+on+7+June+2010 She & Him at Millennium Park (Chicago) on 7 Jun 2010 – Last.fm]
* [http://www.msichicago.org/ The Museum of Science and Industry in Chicago] uses hCard for their address in the "museum location" area on each page.
* [http://www.brewcamp.com/ Brew Camp | Chicago's Local Home Brew Shop] uses hCard for the address under the map on the main page.
* [http://www.larsbeck.info/ larsbeck.info] uses hCard for personal contact information.
* [http://www.linkedin.com LinkedIn] uses hCard for each user profile page.
* [http://www.tripadvisor.com TripAdvisor] uses hCard on property pages, however it appears that they have lumped in locality, region, and postal-code into locality. Example: [http://microformatique.com/optimus/?uri=http://www.tripadvisor.com/Hotel_Review-g42763-d90229-Reviews-Detroit_Marriott_Troy-Troy_Michigan.html Detroit Marriott Troy]
* [http://www.megatravel.com.mx/ Mega Travel] uses an hcard for the contact information in the web site footer [http://www.megatravel.com.mx/ Mega Travel].
* [http://www.thebasketcasedeli.com The Basket Case Deli] uses hCard for organizational addresses as well as employee contact information e.g. [http://thebasketcasedeli.com/about.php About The Basket Case Deli].
* [http://www.thejokes.net TheJokes.Network] uses hCard markup on user profile pages e.g. [http://thejokes.net/profile.php?uid=3 User Profile for Sid Parker]
* [http://www.therecipedepository.com The Recipe Depository] uses hCard markup on user profile pages e.g. [http://www.therecipedepository.com/user/jay User Profile for Jay Allen].
* [http://www.airconditioningdetroit.org/ Air Conditioning Repair Detroit] uses hCard markup on the homepage of their air conditioning website.
* [http://losangeles.trenchless-sewer.com/ Los Angeles Trenchless Sewer] implements hcard on the footer of their trenchless sewer website.
* [http://www.granitecountertopsdetroit.org/ Granite Countertops Detroit] uses hCard markup on the footer of their kitchen counter top website.
* [http://www.web-id.nl/ Web-id. Webdesign, SEO and Software] Uses an hCard for the contact information.
* [http://advanced-simple.de/ Advanced Simple] uses an hcard for the contact information in the page footer of their website.
* [http://profispan.de/galerie/ Profi Span GmbH - Holz in aller Form] uses hcard for the contact information box on the right side of nearly every page.
* [http://hochzeiten-partys-feten.de/ Hochzeiten Partys & Feten] uses hcard markup for the contact information box on every page.
* [http://www.partyrentalsplace.com/ Party Rental Place] uses hCard markup on the testimonials page of their website.
* [http://www.getlocalmaps.com/ Google Map Marketing] is using hCard on the contact page of their website.
* [http://www.hardcoreepoxyflooringdetroit.com/ Hardcore Epoxy Floors] is using hCard on the footer section of their epoxy paint website. Click [http://www.hardcoreepoxyflooringdetroit.com/ epoxy michigan] to view example.
* [http://www.internetmarketingnuke.com/internet-marketing-tools/bookmarking-demon-review-1/ Bookmarking demon review]. Uses an hCard on their contact page.
* [http://www.themexicanjewelry.com/index.php?route=information/information&information_id=14 The Mexican Jewlry]. Uses an hCard for the contact information with OpenCart.
* [http://www.garmentprintiIng.co.uk/contact-us.php Garment Printing]. Uses an hCard for the contact information.
* [http://www.cabs.co.za/ CABS Car hire]. Uses an hCard for the contact information on page footers.
* [http://www.mlgphotography.co.za/ MLG Wedding Photography]. Uses an hCard for the contact information.
* [http://www.e-kyttaritida.gr/ Κυτταρίτιδα]. E-kyttaritida.gr uses an hCard on their contact page.
* [http://www.tierarztpraxis-kellerberg.de/ Tierarztpraxis Kellerberg Steingaden]. A veterinary practice that uses hCard markup to provide contact information.
* [http://www.bastajulborden.se/julbord-p%C3%A5-junibacken.html]. Uses an hCard for the contact information.
* [http://www.bastajulborden.se/.html]. Uses an hCard for the contact information.
* [https://www.redflymarketing.com/contact-us/ Redfly Ireland]. Uses an hCard for the contact information.
* [http://www.designliga.com Designliga] uses hCard markup with company contact information on its Contact and Imprint pages.
* [http://allinsuranceinfo.org/agents/alabama/montgomery.html AllInsuranceInfo.org] uses hCard markup to format insurance agents directory.
* [http://www.seveermedia.com/ Seveer Media] uses hCard markup and allow for vCard download on their contact page.
* [http://london.alleycats.co London.Alleycats.co], by Alleycats.co, uses hCard to format all their fixed-gear directory listings.
* [http://www.spaachat.com Spaachat.com], by Aquavia Spa, uses hCard and Microdata markup in the contact section and the retailers list.
* [http://www.waketoolz.de/info/impressum.html Waketoolz] uses hCard markup on their contact page.

* [http://tigermechanical.net/ Tiger Mechanical] uses hCard markukp throughout the website, inside the copyright area, [http://tigermechanical.net/ appliance repair gilbert] and in the sub domain [http://paradise-valley-appliance-repair.tigermechanical.net/ appliance repair paradise valley].
* [http://www.thedentureclinic.co.uk/ The Denture & Implant Clinic] uses hCard markup and allow for vCard download on their contact page.
* [http://ReallyGoodEnergy.com/ RGE] uses hCard markup and allows for vCard download on their page footers.
* [http://pHElixir.com/ pH Elixir] uses hCard markup and allows for vCard download on their page footers.
* [http://www.air-bourne.com/ Airbourne AC and Heating] uses hCard in footer of the air conditioning website. Example: [http://www.air-bourne.com/ Houston Air Conditioning]
* [http://theworkoutwarehouse.net/ Gym Riverview MI] uses hCard inside the footer of the workout fitness website. Example: [http://theworkoutwarehouse.net/ Weight Training Riverview MI]
* [http://www.carleasinguk.com/ www.carleasinguk.com] uses hCard markup and allow for vCard download on their page footers.
* [http://www.naples-fl-real-estate.com Naples Florida Real Estate] uses hCard markup and allow for vCard download on their contact page.
* [http://www.technicsgroup.com/ Technics Group] uses hCard markup and allow for vCard download on their page footers.
* [http://www.manageathome.co.uk/ Manage At Home] uses hCard markup and allow for vCard download on their contact page.
* [http://www.cleverelectric.com/ San Jose Electrician] uses hCard electrian footer page of their website. to see an example in action visit [http://www.cleverelectric.com/san-jose-electrical-service.html/ San Jose Electrical Contractor]
* [http://www.skin-care-health.org/spots-on-skin.html Skin Care & Health] uses hCard markup on their contact page.
* [http://www.bed-bugs-handbook.com/bed-bugs.html Bed Bugs Handbook] uses hCard markup on their contact page.
* [http://www.oakleydental.co.uk/ Oakley Dental] uses hCard markup on their address which can be downloaded as a vCard.
* [http://www.appliancerepairmedic.com/ Appliance Repair Bergen County] implements hCard in the footer area of their appliance repair site.
* [http://www.cahilldentalcare.co.uk/ Cahill Dental Care] uses hCard markup on their address in the footer which can be downloaded as a vCard.
* [http://www.returnondigital.com/ Return On Digital] uses hCard markup on their site wide footer addresses and on their [http://www.returnondigital.com/about-us/dave-ashworth.php staff pages] - these can also be downloaded as vCards.
* [http://www.arouatek.com/eng/ Aroua Range hoods] uses hCard markup on their [http://www.arouatek.com/eng/contact.php Contact] page.
* [http://www.gembuild.co.uk/contact.htm Gem Build UK ] uses an hCard on their contact page.
* [http://www.1host.gr/web-hosting/ web hosting] uses hCard markup with company contact information on its Contact and Imprint pages.
* [http://nwnasalestraining.com/contact/ Noel Walsh] - uses hCard on the contact page as well as a downloadable vCard.
* [http://www.formundcode.de/ Form & Code] - uses hCard with company contact details in page header.
* [http://www.dptraining.co.uk/contact/ DP Training] - uses hCard with H2VX's bookmarklet to allow users to download the details as a vCard.
* [http://starthilfeberlin.de/ Starthilfe Berlin] - uses hCard (and geo, XFN, rel-license, rel-profile) in (Joomla HTML5) '<#footer role="contentinfo" <footer #footertrademark <address' in all pages.
* [http://trade-service.eu/kontakt/ Trade-Service] - uses hCard in (WP HTML5) '<.address role="contentinfo" <address' in all pages, and extended hCard in the [http://trade-service.eu/kontakt/ contact page].
* [http://lanceguyatt.com/ lanceguyatt.com] - uses hCard as the index page.
* [http://www.easi-services.fr easi services] utilise hCard dans sa page de [http://www.easi-services.fr/contact contact].
* [http://www.umovefree.com/ UMoveFree] - Uses hCard for rental property address. Example: [http://www.umovefree.com/Apartment/cirque-apartments-dallas-tx/ Cirque Apartments Dallas].
* [http://www.newtosandiego.com/ NewToSanDiego] - Uses hCard for organization and business address. Example: [http://www.newtosandiego.com/Ocean-Beach-People's-Organic-Foods-Co-op/ Ocean Beach People's Organic Foods Co op].
* [http://www.northwooduk.com/ Northwood Estate Agents] use hCard on their branch landing pages, here is [http://www.northwooduk.com/letting-agents/edinburgh an example].
* [http://www.signsbannerswraps-houston.com/ Car Wraps Houston] uses hCard on the footer section at the bottom of page see [http://www.signsbannerswraps-houston.com/vehicle-graphics-and-car-wraps-houston.html vehicle wraps houston] page.
* [http://www.elevatelocal.co.uk Elevatelocal] uses hCard on their [http://www.elevatelocal.co.uk/contact Contact Us] page.
* [http://lucumalabs.com Lúcuma labs] uses hCard in the index page.
* [http://railsjobs.co.uk Ruby on Rails Jobs UK] uses hCard in the footer.
* [http://www.ufirstgroup.com/ UFirst Group] uses an hCards in the footer of every page
* [http://www.brodwax.com/ Brodwax Lighting] uses an hCard on their [http://www.brodwax.com/fluorescent-lighting-fixtures.html fluorescent light fixtures] page.
* [http://tripedge.co.uk Tripedge] uses hCard in the footer
* [http://www.appliancerepairbergencountynj.com/ Appliance Repair Bergen County NJ] uses hCard code in the footer of the appliance repair site.
* [http://www.morgenson.com/ Morgenson Realty] uses hCard on their [http://www.morgenson.com/cameron-heights-apartments.php Apartment Listing] pages.
* [http://www.bientek.com/ BienTek] uses hCard on their [http://www.bientek.com/about-us/ About page].
* [http://www.yourtraces.com YourTraces] uses hCard on their profiles [http://www.yourtraces.com/biography/1120.html example].
* [http://www.findwell.com findwell Real Estate] uses hCard on their [http://www.findwell.com/contact Contact Us] page.
* [http://droidvsiphone.org Droid vs iPhone] uses hCard in the footer
* [http://howdoyouknowifyouhavebedbugs.com HowDoYouKnowIfYouHaveBedBugs.com] uses hCard in the footer
* [http://www.schiessle.org schiessle.org] uses hCard at the index/contact page
* [http://www.deadbedbugs.co.uk/ deadbedbugs] deadbedbugs use hCard on their [http://www.deadbedbugs.co.uk/contact.html contact page].
* [http://johanramon.fr/ Johan Ramon] uses hCard on his resume.
* [http://www.saveontapestries.com/ Wall Art Shop] uses hCards on all contact pages, including their [http://www.saveontapestries.com/blog/ Wall Art Blog] and [http://www.saveontapestries.com/message.php Contact Us] Page
* [http://www.placedash.com/ placedash] uses hCard on all place pages, such as [http://accountants.placedash.com/b/4591 Steven R Aron CPA] and [http://taxconsultants.placedash.com/b/21916885 KPMG]
* [http://www.slimmeria.com/bookings-contact Slimmeria Detox Retreat ] in the UK uses an hCard on the Bookings and Contact page.
* [http://www.airbourneairconditioning.com/houston-ac-repair.html Houston AC Repair ] in Houston uses an hCard on the footer of the air conditioning website..
* [http://www.iluminacionmidava.com/ Iluminación Midava, SL ] in Spain uses an hCard on their pages.
* [http://shop.artgpa.com.ua/contacts.html ArtGPA SHOP in Ukraine ] uses an hCard on their contact page.
* [http://clothesonline.info/ ClothesOnline] uses hCard to identify clothing brands, shops and users. Example: [http://clothesonline.info/shops/mark-spencer Mark & Spencer].
* [http://www.beltmann.com Beltmann Relocation Group] uses an hCard on their [http://www.beltmann.com/atlanta-movers.aspx Atlanta Movers] page.
* [http://www.therapistinlondon.com/ Therapist in London ] Delma Walsh uses an hCards in the footer of every page.
* [http://www.novelwebdesigns.com/ Web Design & SEO] NWD uses an hCard on their contact page.
* [http://www.webscatalunya.com/ Webs Catalunya ] uses an hCards in the footer of every page.
* [http://rinklinks.ca/ RinkLinks.ca: A Comprehensive Rinks and Arenas Directory for North America] uses an hCard for every listing in their directory.
* [http://immotek.fr/ Immotek general contractor in Toulouse, France] uses hCard in the footer of every page (plus hAtom on entries).
* [http://www.aoinstitute.com/ Advanced Orthopaedic Institute ] uses an hCards on the footer of every page.
* [http://www.orchard-barn.co.uk/contact.htm Orchard House B&B ] uses an hCard on their contact page.
* [http://www.medivisas.com/contact.asp Medi Visas UK ] uses an hCard on their contact page.
* [http://www.premierlogos.co.uk/page/contact Premier Logo T Shirts ] uses hCard on the contact page.
* [http://eastsideentrepreneurs.ning.com/profile/MrsClean/ Mrs Clean House Cleaning ] uses hCards in the profile page.
* [http://www.thesanfordhouse.com/ The Sanford House Bed & Breakfast ] uses hCards in the footer of every page.
* [http://www.imap.cat/ Imap Internet Marketing] uses hCards in the footer of every page.
* [http://www.haraldjoergens.com/Copyright.html Harald Joergens Photography ] uses hCards on the page and in the footer of every page (see blog post [http://www.haraldjoergens.com/blog "From website to address book in one click"]).
* [http://www.ethoseo.com/ Ethoseo Internet Marketing in Washington State ] uses hCards in the footer of every page.
* [http://www.roofingandsidingdetroit.com/ Roofing Detroit] uses hCards inside the footer of every page on their roofing website.
* [http://www.iobuild.co.uk/ IO Garden Buildings] is using hCard on their [http://www.iobuild.co.uk/garden_home_offices_about_us.asp About Us] page.
* [http://www.popalockofjacksonville.com/ Pop-A-Lock Locksmith Jacksonville] is using hCard in the footer on all the pages on their website and the hReview code on their testimonials page [http://www.popalockofjacksonville.com/jacksonville-reliable-safe-locksmith.html/ Pop-A-Lock Locksmith Jacksonville Testimonials]
* [http://Tutiendadeinformatica.com/ oferta de portatiles] - uses hCard as the index page.

* [http://www.harleytherapy.co.uk Harley Therapy, Counselling London] uses an hCard (Organisation) on the home page as well as an hcard for an individual practitioner on the [http://www.harleytherapy.co.uk/psychiatrists-london.htm Psychiatrist] page.
* [http://www.mwmachineshop.com/ M & W Machine Shop] is using hCard in the footer on the entire site.
* [http://carmela.co.uk/ Carmela Make-up] is using hCard on most pages of her site, including the [http://carmela.co.uk/wedding-make-up.htm wedding make-up] page.
* [http://www.findaporsche.com/ Find a Porsche] is using hCard on their [http://www.findaporsche.com/?page_id=17 Contact Us] page.
* [http://www.atrendyhome.com/ A Trendy Home - Home Improvement Store] is using hCard on their [http://www.atrendyhome.com/contactus.html Contact Us] page.
* [http://tedswoodworkingplan.com/ Teds Woodworking] uses hcard for their site information.
* [http://www.mrscleanusa.com/ Mrs. Clean's Cleaning Service] is using hCard on their [http://www.mrscleanusa.com/en/cleaning-services/mrs-clean/about-us.html About Us] page.
* [http://www.merrittsforhair.co.uk/ Merritts for Hair] is using hCard on their [http://www.merrittsforhair.co.uk/contacts/ Contact Us] page.
* [http://www.alwaysonmessage.com/contact/get-in-touch.aspx Always on Message] is using hCard on their Contact Us page and are interested to see/hear how hCard's can be used in Smartphone Apps,
* [http://sroe.home.cern.ch/sroe/sroe/Welcome.html Shaun Roe] is using hCard on his work page at CERN,
* [http://www.localdatabase.com/ Local Database] uses hCard on all category and business profile pages, [http://www.localdatabase.com/texas/Houston/Veterinarians/ Houston Vets]
* [http://www.pinbud.ca/ www.PinBud.ca and www.PinBud.com (a search and get quotes website)] uses hCard on all the listing pages, example: [http://www.pinbud.ca/list-services/475-Personal-trainers-in-Calgary,%20AB Personal trainers in Calgary]
* [http://www.quippd.com/popular quippd] uses hCard on profile pages and story listings.
* [http://www.davidrivers.name David Rivers] uses hCard markup on his [http://www.davidrivers.name/contact Contact David Rivers] page
* [http://www.pabloestrada.us/pe/pablo.estrada.html Pablo Estrada] uses hcard on his resume page.
* [http://www.nieruchomosci-czubak.pl/ AJ Czubak Nieruchomości] uses hcard markup in the fixed contact info section on the left and within the [http://www.nieruchomosci-czubak.pl/kontakt.html contact subpage]
* [http://www.metalgigs.de Metalgigs.de] uses hcard for the profile pages at metalgigs.de/userpage/username, see [http://www.metalgigs.de/userpage/Testuser]
* [http://www.ankeboelens.nl/ Anke Boelens Interieurvormgeving] uses hcard markup in page footer
* [http://ragtagntextile.org.uk Rag Tag 'n' Textile] - Mental health charity in Skye and Lochalsh, the Highlands of Scotland - uses hCards for locations of head office and craft shops]
* [http://atzkey.org/ Denis Bakunovitch] — IT professional — has nicely styled hCard
* [http://www.olaru.ca/ Maria Olaru - lawyer / avocat - Montreal Law Firm] uses hCard for the law office.
* [http://www.epinux.co.uk/contact Mike Shutlar at Epinux] uses hCard markup on his contact page.
* [http://nzia.org/practitioner-directory/ New Zealand Institute of Acupuncture] uses hCards to display member's contact details.
* [http://www.mamscatering.nl/ MAMS Catering] uses the drupal hCard module for contact information on the website.
* [http://www.ialphan.com Alphan Gunaydin] uses hCard markup throughout the home page (index).
* [http://www.phytodoc.de/therapeuten-suche/ PhytoDoc's database for therapists in Germany] uses hCards for contact data on the detail pages of every therapist. [http://www.phytodoc.de/therapeut/wiesloch/berthold-musselmann/ Examplary therapist's page].
* [http://www.charleschurch.com Charles Church House Builder] uses hCard for property development addresses and geo latitude and longitude. See [http://www.charleschurch.com/carmarthenshire_ammanford/pen-y-bryn-1067 Homes for sale in Ammanford] page for embedded hcard on property development pages.
* [http://www.canisphouse.com Canisp House Bed and Breakfast]Establishment uses hcard to mark up business address. Validates with Google Rich Snippets.
* [http://www.jondon.com/stores/index.htm Local Stores Locations Page], the store details on store pages are Hcard.
* [http://www.sucklings.co.nz/contact-us Contact page of Sucklings Shoes Store], the store details are an Hcard.
* [http://www.a3architekten.com/ Contact details of a3architekten]. A combination of two hCards looking like one.
* [http://www.imap.cat]. A combination of two hCards looking like one.
* [http://www.sigmacom.nl/ Corporate website of Sigmacom]. hCards were implemented in the footer
* [http://www.fpc.wa.gov.au Forest Products Commission] hCards to markup addresses & contact info for:
** all its offices and media contacts: [http://www.fpc.wa.gov.au/content_migration/about_us/contacting_us.aspx office locations]
** search results for suppliers of timber within Western Australia: [http://www.fpc.wa.gov.au/BuyTimber/Search?Species=&Region= find a timber supplier]
* [http://www.hirners.com Hirners Hotel Guide] uses hCards to markup addresses and contact info of every property, including geo coordinates. Example: [http://www.hirners.com/properties/4-atlanta-hotel-in-vienna-austria Hotel Atlanta in Vienna, Austria]
* [http://www.cartuse-imprimante.ro/ Cartuse Imprimante], printers and printer cartridges supplier, uses an hCard on home page and contact page of the website.
* [http://www.seminee-bellfires.ro/ Seminee Bellfires], interior fireplaces design company uses an hCard on every page of the website.
* [http://www.eurodata.com.ro/ Eurodata Serv], IT consulting and service company uses an hCard on every page of the website.
* [http://www.chipwreck.de/blog/contact/ Mario Fischer] uses a hCard with his contact information
* [http://joebergantine.com/contact Joe Bergantine] has marked up his contact information with hCard and XFN
* [http://www.nonleaguegrounds.com nonleaguegrounds.com], a database of English non-league football stadiums, uses hCards on every specific club detail page. Example: [http://www.nonleaguegrounds.com/gb/london/afc-wimbledon AFC Wimbledon]
* [http://thetruthaboutabs1.com/ Thetruthaboutabs] uses hcard for their site information.
* [http://www.simourix.nl/ Simourix Hosting] uses an hCard for contact information on the website.
* [http://www.aquastop-vochtwering.nl/ Aquastop vochtwering] uses an hCard on every page of the website.
* [http://www.kennysaunders.com/ Kenny Saunders] uses an hCard on for contact information on this business card website.
* [http://thesilverfishbug.com/ Silverfish Bug] uses hcard for their site information.
* [http://annuaire.leperon.fr/ L’Annuaire du Cheval] is a French directory of equestrian professionals. We have just added hCards to all the client pages. Sample one here [http://annuaire.leperon.fr/client/0b1s/tarder-camille-et-frederic Tarder]. We also added an 'add to your address book' button but had to take it out again as some Windows machines choked on the accents, not recognising the UTF-8.
*[http://www.cheapholidays.com/ Cheap Holidays] uses an hCard on each page footer.
*[http://www.flightline.co.uk/ Flightline] uses an hCard on each page footer.
*[http://www.affordablestorage.net.nz/contactus.html Affordable Storage] Uses hCard for contact information.
* [http://www.norfolkblackhistorymonth.org.uk/contact.html Norfolk Black History Month] - Uses hCard on the Contact page and throughout the site, providing contact information for event locations, organisers and partner organisations.
* [http://www.veganusofa.com/ VeganUSofA] - Uses hCard for organization and business address. Example: [http://www.veganusofa.com/index.php?listing=4 The All Vegan Store].
*[http://adrianindo.blogspot.com ADRIAN'S BLOG] have included hCard to introduce myself more closely with the visitors of my blog. the hCard has been listed as a name, blog url and organizations. This hCard you can see on the lower right sidebar of my blog layout.
* [http://www.canadianpokerexpo.com The Canadian Poker Expo (Toronto)], a Poker Lifestyle Expo focusing specifically on the Toronto market, is using hCard for [http://www.canadianpokerexpo.com/Contact-Us/Contact-Form their contact page] as part of their efforts to increase the site's local relavance.
* [http://www.semineeas.ro Seminee As], a Romanian fireplace manufacturer, uses hCard for [http://www.semineeas.ro/contact/ contact info] with optional vCard download.
*[http://www.gastrohep.com/aboutus.asp GastroHep.com] About Us page uses an hCard for the contact address.
*[http://wedding-slideshows.net/ Wedding Slideshows] uses hCard for business address and contact details.
*[http://leemannphotography.ca/?p=contact Lee Mann Photography] Uses an hCard on the main Contact page as well as the blog.Ideally it will soon be on the footer of every single page.
*[http://www.kimburgess.info Kim Burgess] Minimalist info website with hCard markup positioned throughout.
*[http://www.plumbset.co.uk/ContactUs.asp PlumbSet UK Ltd] Uses hCard for the contact address, including multiple street-address entries.
*[http://www.manuhealth.com/products/manuka-soap-75gm Manuhealth Natural Remedies] Uses hCard for the return address on product pages.
*[http://www.farmaciasarria.com/esp/mapa.php Farmàcia Sarrià - Farmàcia Finestres Capdevila] uses an hCard for his contact information.
*[http://www.naturesbestshot.com Nature's Best Shot Photography] - uses an hcard on the contact page
*[http://www.noomii.com/life-coach Noomii.com Coach Directory] - each professional life coach in the directory is an hcard
*[http://www.ethical-junction.org/member/org-2012.html Ethical Junction CIC - Profile page] We use hCard for every organisation on their profile page
*[http://www.bowtietv.com Bow Tie Television] Uses hCard for contact information on every page and in the contacts section.
*[http://www.tauruslogistics.co.nz/about/contact Taurus Logistics] Uses hCard for contact information.
*[http://www.professdiamond.com/ professdiamond] encodes Thai as UTF8 in an inline hCard at the bottom of every page.
*[http://avonvalleylocalguide.iinet.net.au/ Avon Valley Local Guide] uses hCard for contact information of advertisers.
*[http://www.arizonafirstresponse.com/ Arizona First Response] uses an hCard on each page footer.
*[http://dillingham.me.uk/ Iain Dillingham] uses an hCard on each page footer, and has a styled example (with the microformats logo) on his [http://dillingham.me.uk/contact.html contact page].
*[http://www.pixeflips.com/ Pixelflips Web & Interface Design] hCard is used in the footer of all pages for easy access to contact information.
*[http://www.herminesperr.at/ Hermine Sperr, Qualified Practitionier of the Grinberg Method® in Wien/Austria] A hcard is used for contact information on every page on her website.
* [http://www.ivycat.com/ IvyCat Website Services] - Web design & hosting firm uses hCard for business contact info. Example: [http://www.ivycat.com/contact/ Contact Us].
* [http://www.modeltrainswithlarry.com/ ModelTrainsWithLarry] - Uses hCard for organization and business address. Example: [http://www.modeltrainswithlarry.com/index.php?listing=502 Choo Choo Barn].
* [http://www.gardeningwithlarry.com/ GardeningWithLarry] - Uses hCard for organization and business address. Example: [http://www.gardeningwithlarry.com/index.php?listing=2681 United States Botanic Garden].
* [http://abyrvalg.com/ Abyrvalg] - russian city community. Uses hCard to display local businesses address. Example: [http://moscow.abyrvalg.com/biz/faq-cafe FAQ cafe in Moscow].
* [http://www.jdclark.org/v1 Jordan Clark], from the Swansea area of Wales in the United Kingdom, uses [http://www.jdclark.org/card hcard for contact information].
* [http://whichtwitterapp.com/ WhichTwitterApp] provides [http://whichtwitterapp.com/reviews/iphone/tweetie reviews of twitter apps] using hCard, hReview, rel-tag and rel-home.
* [http://www.robinleysen.be/Robin.html Robin Leysen] has a hCard on a separate page. Tried to be as complete as possible. hCard validated with Optimus.
* [http://www.jay-photographics.de/ Jay Photographics] Photographer from Stuttgart, Germany. The hcard format is used on all pages for contact information.
* [http://www.uniquesite.co.uk/ UNIQUEsite] Website designer based in Brighton, UK. Uses the hcard format for contact information.
* [http://www.slideshare.net/ SlideShare] uses hcard to identify its users. see [http://hcard.geekhood.net/?url=http%3A%2F%2Fwww.slideshare.net%2Fkcmani#result Validated hcard] and [http://www.slideshare.net/kcmani Mani's SlideShare profile]
* [http://chrisruppel.com Chris Ruppel], a web developer in Dallas, TX, uses an hcard for contact information site-wide (as well as XFN)
* [http://greenspiritgardeners.com/ Green Spirit Gardeners] uses the hCard format throughout the site, including on the portfolio page for [http://greenspiritgardeners.com/portfolio/ commercial clients] and the [http://greenspiritgardeners.com/contact/ contact] page.
* [http://www.dorettebos.nl/ Dorette Bos Coaching & Training] uses hcard microformat on the [http://www.dorettebos.nl/contact.php contactpage]
* [http://volunteers.st/ Steffi & the volunteers] is an Austrian band and uses hcards for [http://volunteers.st/ band-contact in the footer] and on the page of the [http://volunteers.st/crew.html crew]
* Turkish business directory website [http://www.firmasec.com/ firmasec.com] implements valid hCard and hReview-Aggregate for companies, contact information with geo tags and user comments. Example: [http://www.firmasec.com/firma/mmfzz-caprice-palace-hotel-didim/ Caprice palace hotel profile page]
* [http://www.textundkonzept.at Bernhard Ulrich] an Austrian copywriter uses the hcard format [http://www.textundkonzept.at on all pages of his website] for his contact information
* [http://www.powerbrand.at/contact.html POWERBRAND] a brand name development agency uses a [http://www.powerbrand.at/contact.html hcard for contact information]
*[http://www.koerperarbeit.net/ Anita Braunsberger, Qualified Practitionier of the Grinberg Method® in Linz/Austria] A hcard is used for contact information on her website.
*[http://www.carpetscleansandiego.com Durbin's Carpet Care] displays a vCard for contact information and relevancy
*[http://www.nationalrural.org/organisation.aspx?id=96a3fc04-5c03-4d31-bb8a-2c55cc29aed4 National Rural Knowledge Exchange] uses an hCard with geo tags when displaying an organisations information
* [http://www.tinstar.co.uk/about-tinstar-design/contact-tinstar-design.html Tinstar Design] uses an hCard for company contact information.
* [http://www.interdixit.com/esp/contacto.php Interdixit] uses an hCard for his contact information.
* [http://www.sisnova.com/ Sisnova] uses hCard for his location pages.
* [http://www.fenoyarquitectura.com/esp/situacion.php Eduard Fenoy i Associats] uses an hCard.
* [http://www.deltronic.com/ Deltronic Corporation] of Santa Ana, CA has posted an hCard with geo tags on its [http://www.deltronic.com/contact.shtml Contact] page. Background image of a contact card reinforces content. For those without enabling browser extensions, both hCard "logo" and text link make vCard available via external parser.
* [http://transitionsmft.org/ Transitions Marriage and Family Therapy] has an hCard with geo tags in the footer of each page. There is also an hCard for each counselor on the [http://transitionsmft.org/about.php About] and [http://transitionsmft.org/contact.php Contact]pages.
* [http://ball.in.th/ ball.in.th] uses hCard to display all usernames.
* Italian business directory and community portal [http://www.cylex.it/ cylex.it] implements hCard for companies’ contact information with geo tags. Example: [http://www.cylex.it/azienda/computerland-10559319.html company profile]
* [http://jermy.musicremedy.com/ Jermy Leeuwis MSc] uses an hCard for his contact information.
* [http://idoinfotech.com Gary Eckstein] uses an hCard for [http://idoinfotech.com/contact contact information].
* [http://www.drsuarez.net/ Dr. Suarez] uses hCard on his [http://www.drsuarez.net/cvitae.html resume page]
* [http://sourceforge.net/projects/adx/ addressbook.xml] provides hCard support: [http://elektronengehirn.net/addressbook/addressbook.html adx live example]
* [http://aplawrence.com APlawrence.com] is using hCard for its [http://aplawrence.com/Links/consultants.html Unix and Linux Consultants Page]
* [http://www.afonsoduarte.com Afonso Duarte's Portfolio]. Uses an hCard for the contact information.
* [http://www.rafe.me Web development by Rafe Harwood]. Uses an hCard for the contact line in the footer of every page.
* [http://www.frogmeat.com Los Angeles Web Design]. Uses an hCard for contact information.
* [http://www.arbea.basilicata.it/ ARBEA - Agenzia della Regione Basilicata per le Erogazioni in Agricoltura]. hCard is used both for classic [http://www.arbea.basilicata.it/index.php?option=com_contact&view=contact&id=4&Itemid=101 Contact page] and for farms showcase ("Vetrina Aziende Agricole") available for registered users. I've embedded it modifying Joomla! 1.5 com_contact core component. Users of this CMS can [http://joomlacode.org/gf/project/hcardcontact/ download my patch].
* [http://trumps.net Los Angeles Search Engine Optimization] Uses hCard in the footer of all pages.
* [http://www.oasisroofinginc.com/ Seattle Roofing] Uses hCard in the footer of their roofing website see [http://www.oasisroofinginc.com/ Roofing Seattle WA] to see the hcard.
* [http://reaganvick.com Personal Portfolio of Lance Reagan Vick]. Includes examples of PGP and SSH public keys I have not seen used anywhere else. Hopefully someone finds it helpful!
* [http://www.fracturedstudios.com Los Angeles Search Engine Optimization] uses hCard to provide address information at bottom of page
* [http://www.csid.upt.ro/home.php The Distance Learning Center - CSID, "Politehnica" University Timisoara], Romania uses hCard, including geo information, in every page's footer for encoding the University address. hCard is also used for [http://www.csid.upt.ro/personal.php staff] and student contact information.
* [http://rehabpizza.co.uk Rehab Restaurant] London restaurant, see the sidebar for link to [http://rehabpizza.co.uk/rehab.hcard the hcard].
* [http://www.outdoorla.org/ Los Angeles Hiking Trails] at the bottom right, our contact information is marked up as an hcard.
* [http://c7.se Code7 Interactive] uses a hCard for Peter's [http://c7.se/contact contact details].
* The [http://www.austinartcollective.com Austin Art Collective] is a group dedicated to helping emerging artists sell their artwork online. There is space for users to submit [http://www.austinartcollective.com/gallery/Art-City-Austin.html art gallery reviews] as well, [http://www.austinartcollective.com/austin-galleries/Downtown.html organized by neighborhood] in Austin, TX USA.
* [http://www.squaremeal.co.uk/ Square Meal Restaurant Guide] uses hCards and hReviews for all restaurant listings and [http://www.squaremeal.co.uk/review/Ristorante_Semplice/1596 visitor reviews].
* [http://www.vegan-nottingham.co.uk/ Vegan Nottingham Guide] uses hcards, including geo information, for each entry in the guide.
* [http://www.cgtworld.com/ Cybernation Gamers Tournament] uses hCard in all users profiles like [http://www.cgtworld.com/profile/id-1/ Moonlext's Profile] and in the [http://www.cgtworld.com/about/press.html press page of CGT].
* [http://fcctlh.org First Christian Church of Tallahassee] Uses hCard in the footer of all pages.
* [http://www.pseps.com/vc-people/a.cfm The PSEPS Venture Capital and Private Equity Directory] Venture capital and private equity directory using microformats (both for professionals and firms).
* [http://www.koningskindkadootjes.nl koningskindkadootjes.nl] Hcard located at the bottom of the pages.
* [http://www.futurix.nl futurix.nl website and webshop development] At the bottom of the pages you'll find the hcard. With a link to technorati the hcard is used to get a vcard out of the hcard.
* [http://romjon.com/contact-us romjon.com website design & development] Contact Us page using hcard to markup address details. By using Operator, Google Maps and Yahoo! Maps can be made to open with the pointer, respectively, in pretty much and more or less exactly the right place.
* [http://www.thebeanmachine.nl/ The Bean Machine] at the bottom right, our contact information is marked up as a hcard
* [http://www.universalmedicalid.com/canada Universal Medical ID Canada] uses hCard to provide address information at bottom of page, as well as on a number of pages within the site.
* [http://www.floristfullerton.com/ fullerton florsit] uses an hcard for the web site footer [http://www.floristfullerton.com/ florist fullerton].
* [http://puronicsorangecounty/ Puronics Orange County] uses an hcard for example view footer [http://puronicsorangecounty.com/ water softener orange county].
* [http://web.mac.com/a.gibson/ Alex Gibson Web Developer] uses hCard for contact info on his homepage.
* [http://www.wardelldesign.com/html/contact/index.php Wardell Design] uses hCard for contact info with optional vCard download.
* [http://www.drfosterhealth.co.uk/hospital-guide/ Dr Foster Hospital Guide] uses hCard to mark up hospital addresses. See [http://www.drfosterhealth.co.uk/hospital-guide/hospital/nhs/Basingstoke-and-North-Hampshire-Hospital-366.aspx Basingstoke hospital page] for example.
* [http://www.drfosterhealth.co.uk/complementary-therapist-guide/ Dr Foster Complementary therapist guide] The [http://www.drfosterhealth.co.uk/complementary-therapist-guide/objectlist.aspx?w=32&p=8&obid=&sub=0 regulatory bodies page] uses hCard for contact details.
* [http://wayne.edu/ Wayne State University] uses hCard for University address and contact details in the global footer used on most web pages.
* [http://www.brakemeters.co.nz/ Portable Brake Meters N.Z. Ltd] uses hCard for business address and contact details.
* [http://www.tallpoppieshamilton.co.nz/ Tall Poppies Florist] uses hCard for business address and contact details.
* [http://www.livingcolour.co.nz/ Living Colour Florist] uses hCard for business address and contact details. See [http://www.livingcolour.co.nz/Information.aspx Information] page
* [http://www.dallasfamilyhomes.com/ DallasFamilyHomes.com] uses hCard for property addresses and geo latitude and longitude. See [http://www.dallasfamilyhomes.com/dallas-homes/ Dallas Homes] page for embedded hcards and property detail pages.
** Pretty good. An improvement might be to use <code>agent</code> to mark up the agent's contact details, and <code>note</code> to mark up the property descriptions. [[User:TobyInk|TobyInk]] 16:22, 4 December 2008 (UTC)
** Thanks for the suggestion Toby. Added the <code>note</code> for the description to the homes listings and home detail pages.
* [http://www.jabz.de/ Jabz | Internet Marketing Agentur] uses hCard for business address and contact details. See [http://www.jabz.de/kontakt/ Contact Page]
* [http://www.headyperfume.com/ Headyperfume.com] Uses hCard for contact information.
* [http://sixthirteendesign.com/ Six Thirteen Design] uses an embedded hCard along with other contact details on the footer of each page (http://sixthirteendesign.com/)
** ''Problems:'' page also includes class="vcard" used in a non-hCard context (for a VCARD download); types for telephone number and e-mail address are improper. [[User:TobyInk|TobyInk]] 16:22, 4 December 2008 (UTC)
* [http://www.locanto.com/ Locanto - Free Classifieds] uses hcards to geolocate their classified listings. Visit the ad pages for examples.
* [http://www.yalwa.com/ Yalwa - Local Directory] uses hcard on their directory listings. Example: [http://wiesbaden.yalwa.de/ID_102318221/Yalwa-GmbH.html Yalwa Address Listing]
* [http://www.fluendi.com/Contact Fluendi Consulting] uses hcard on their contact page (http://www.fluendi.com/Contact)
* [http://www.badbedbugs.com/ Bed Bugs] uses hcard for their site information. See the [http://www.badbedbugs.com/about-bad-bed-bugs/ about bed bugs] page.
* [http://www.lawyer-directory.net/ Lawyer Directory] uses hcard for addresses within the lawyer directory. Example [http://www.lawyer-directory.net/lawyer/Grand-Rapids-Bar-Association-Grand-Rapids-law434032.htm listing]
* [http://www.hanfmuseum.de/about About Hanf Museum Berlin] uses hcard for addresses and contact informations.
* [http://maps.google.com/ Google Maps] uses hCards for addresses. See [http://googlemapsapi.blogspot.com/2007/06/microformats-in-google-maps.html Microformats in Google Maps].
* [http://local.mapquest.com/ MapQuest Local] uses hCards for locations, hCalendar for events and supports the draft Geo format when lat/lng data is provided. See [http://blog.mapquest.com/2008/09/25/microformat-support-on-mapquest-local/ Microformat Support on MapQuest Local] for more information.
* [http://www.whitepoppy.com/ WhitePoppy.com] uses hCard for business address. See [http://www.whitepoppy.com/Contact.aspx Contact Page]
* [http://www.hightechcville.com/ HighTechCville] uses hcard to mark up people and organizations. See [http://www.hightechcville.com/people/72-eric-pugh Eric Pugh] for an example.
* [http://www.cleanertoday.com/ Cleaner Today] uses hcard to mark up contact details. (see [http://www.cleanertoday.com/Cleaner-Today-a/1.htm Contact Page])
* [http://www.aduk.org Audience Data UK] use hcard on their [http://www.aduk.org/contact.php contact page] and [http://www.aduk.org/directory.php directory of related organisations]
* [http://georgebrock.com georgebrock.com] used hcard for George's contact details
* [http://suggestionbox.com/ SuggestionBox] uses hcard for companies listed on its site. Example: [http://transfercar.suggestionbox.com/ Transfercar].
* [http://www.vcventerprise.com/wp/ Christopia] uses hcard to mark up contact details. (see [http://vcventerprise.com/wp/contact/])
* [http://www.rossirovetti.com/ Rossi & Rovetti Flowers in San Francisco] uses hcard to mark up company details in the about us page of the website. (see [http://www.rossirovetti.com/scripts/aboutus.asp example])
* [http://youtube.com YouTube] uses hcard to identify video contributors (see [http://www.flickr.com/photos/factoryjoe/2793731119/in/photostream/ screenshot]]
* [http://sewmyheadon.com/contact sewmyheadon.com] uses hcard to mark up contact details on contact and about pages.
* [http://www.kleinassoc.com/ Klein & Associates - Estate Planning] used hcard to mark up contact details on law firm's contact page.
* [http://www.markuspage.com/markus/en/contact Markus Kilås] uses hCard to mark up his contact details.
* [http://www.southsidewarriors.com/impressum.cfm Southside Warriors] uses hcard to mark up contact details on the imprint page.
* [http://applesold.com/ Apple Realty - Bristol Real Estate Company] uses hcard to mark up company details in the footer of website.
* [http://www.surfcom.co.uk/app/contact/ Surf Commission] uses hcard to mark up company contact details with option to download vcard.
* [http://www.k9yardpatch.com/contact-us/ K9YardPatch] uses hcard to markup company contact details with option to download.
* [http://www.ecovian.com Ecovian] uses hCard to mark up eco-friendly business contact details, see [http://www.ecovian.com/l/san-francisco-ca/jardiniere-restaurant example]
* [http://www.dischord.com/ Dischord Records] uses hCard to mark up company contact details in the footer of the home page.
* [http://www.thinkambient.co.uk/ ThinkAmbient] uses hCard to mark up company contact details.
* [http://proofile.org/ Proofile] extensive profiles with hCard, vCard, XFN and FOAF support.
* [http://www.ebycattle.com/horses/index.html Eby Ranch] uses hCard for the different branches of the company, with option to download the vCard.
* [http://www.clavex.com/contactus.aspx Clavex - A Latin America Financial Institution ] Uses hCard and geo for the contact information. Simple but effective.
* [http://www.dancefederation.co.uk Dance Federation Salsa Dancing & Jive Dancing Lessons and Events ] Directory for classes, lessons and events users hcard on its lessons and events -- region and url properties are empty. Is that an error?
* [http://mop.ardom.co.il/contact.php Southern Arava Research and Development Center] uses hCard for their contact details on their contact page and in sub pages with contact info. -- one card has two fn properties.
* [http://www.itma.org.uk/find-expert/London] - ITMA Trade Mark Attorney search presents results as hCards
* [http://interkonect.com Interkonect > Website Application Specialists] Office contact details marked up using vcard.
* [http://library.christchurch.org.nz/ContactUs/ Christchurch City Libraries (N.Z.)] contact page plus each of our libraries' individual pages linked from [http://library.christchurch.org.nz/Community/Libraries/ Library Locations map].
* [http://www.leftclick.com/about-us/ LeftClick] uses hcards for contact information.
* [http://ideas.veer.com/skinny Veer's Skinny Blog] implements hcard for comments and post authors.
* [http://wolpy.com/missha Wolpy] Uses hcards for contacts and [http://wolpy.com/missha/profile profile].
* [http://www.veganworldorder.com/index.php?m=vegguide Vegan World Order | Restaurants ] Uses hcards for restaurant listings.
* [http://mahalo.com Mahalo] per the announcement [http://www.seanpercival.com/blog/2008/04/23/mahalo-adds-microformats/]
* [http://www.buythatlocally.com BuyThatLocally ] uses hcards for local business information.
* [http://www.firmendb.de Firmendb] uses hCard for individual business contacts, e.g. [http://www.firmendb.de/firmen/15592.php]
* [http://autopendium.com Autopendium] has resources (e.g. suppliers, clubs) marked up with throughout the site, e.g. [http://autopendium.com/clubs/8-Volvo-Enthusiasts-Club]
* [http://display-block.co.uk Display-Block] uses hCard contacts for People and Companies on my personal Blog.
* [http://www.codesignville.com/ Codesignville] uses hCard for his contact details.
* [http://fan-expo.com/Contactez-nous,2 Forum des Acteurs du NumÃ©rique] (a French trade show and exhibition dedicated to content management) uses hCard for contact information (exhibition staff and exhibitors). It also makes use of hCalendar as well as rel-tag when relevant.
* [http://www.corewhisperer.com/ The Core Whisperer] (Paul Ransom) Geological Services uses hCard for contact information.
* [http://chairmanship.mfa.md/en/ The regional presidencies] of Republic of Moldova to the SEECP, CEI, MAG-RACVIAC, SEEHN, CEFTA uses hCard on [http://chairmanship.mfa.md/seecp-contacts/ contacts pages]
* [http://www.viget.com/about/team Viget Labs] - Team page and Individuals' Pages.
* [http://www.re3elstance.com RE3EL STANCE] - Entrepreneurship: Rebel Style.
* [http://www.worldeventsguide.com World Events Guide] - Events occuring around the world marked up with hCard.
* [http://www.amaliahotel.eu/en/contact.html Amalia Hotel Apartments] uses hCard in the contact-info page.
* [http://www.sslcertificaten.nl/contact.php Xolphin SSL Certificaten] uses hCard for their contact details
* [http://examples.tobyinkster.co.uk/hcard hCard + RDFa Example] - raising the bar for parsers...
* [http://competitiondiva.com/ Competition Diva] uses hCard in its page footer (and plans on it for the upcoming profile pages).
* [http://sanisoft.com/ SANIsoft] uses hCard in its page footer
* [http://www.bossalive.com BossaLive] uses [[hcard|hCard]] on user profile pages.
** Example: [http://www.bossalive.com/user/barry Barry's Profile]
** Also uses rel-tag microformat for tagging music. Publishes rel-tags for album, artist and genre.
* [http://hillhursthardware.com/ Hillhurst Hardware's] contact info w.logo uses hcard.
* Birmingham's [http://bigcityplan.org.uk/ Big City Plan] (England)
* Producer [http://www.sun-treader.com/contact.html Christopher Davis] uses hCard markup on his contact page.
* [http://www.tpexpress.co.uk/Liverpool08-Capital-of-Culture/ First TransPennine Express - Liverpool 08, Capital of Culture] - uses hCard to markup suggested venues.
* [http://anand.ws/ Anand's Musings] uses hCard to mark up authors for comments and posts.
* [http://www.onyomo.com/ OnYoMo] uses hCard markup for all addresses listed in their local search results.
* [http://www.dctalks.org/design/ DC Design Talks] used hCard to mark up the speakers for this one-day event.
* [http://www.entidi.it eNTiDi software] provides a basic hCard sample.
* [http://quickbase.intuit.com QuickBase] uses hCard markup on our contact us page.
* [http://www.pixsense.com/contact_us.html PixSense.com] uses hCard markup for addresses across the PixSense website.
* [http://www.areaguides.net areaguides.net] uses hCard markup for all addresses across the site.
** Examples: http://chicagoil.areaguides.net/ypcyellowpg/restaurants.html, http://newyorkny.areaguides.net/hotels.html
* [http://www.ll.georgetown.edu/ Georgetown University Law Library] in Washington, D.C. now uses hCard for our address on all pages. Also, library staff biography pages use hCard such as [http://www.ll.georgetown.edu/staff/bio.cfm?id_no=105 here] and [http://www.ll.georgetown.edu/staff/bio.cfm?id_no=32 here].
* [http://www.ll.georgetown.edu/ Georgetown University Law Library] in Washington, D.C. now uses hCard for our address on all pages. Also, library staff biography pages use hCard such as [http://www.ll.georgetown.edu/staff/bio.cfm?id_no=105 here] and [http://www.ll.georgetown.edu/staff/bio.cfm?id_no=32 here].

* [http://www.mtgd.gov.md/ Ministry of Transport and Road Industry] of Republic of Moldova. First Moldavian governmental site using hCards on [http://www.mtgd.gov.md/ministrul/ staff pages], [http://www.mtgd.gov.md/subdiviziunile-ministerului/ subdivisions page] and in the footer of each page (contact information)
**Only [http://www.mtgd.gov.md/ Romanian] and [http://www.mtgd.gov.md/ru/ Russian] versions available yet
* [http://www.auctionlink.com.au/ AuctionLink] uses hCard for Auctioneer records like [http://www.auctionlink.com.au/Auctioneers/Auctioneer/Cam_Brown_Auctions/ Cam Brown Auctions] (also uses hCalendar)
* [http://www.wlzine.com/ WLZine] uses hcard to mark up contact details for diet programs (see [http://wlzine.com/south-beach-diet-one-of-the-best-diets-out-there/ South Beach Diet]
* [[User:WebOrganics|User WebOrganics]] The Microformats wiki has hcards on its user pages.
* [http://www.ontwerpkliniek.nl Ontwerpkliniek - Bureau voor Visuele Identiteit] uses the hCard contact information at the frontpage and the contact page.
* [http://www.instantdes.com L'instant des...] uses the hCard format for all photographers published on this collective photoblog.
* the mediadesigner groupblog [http://www.pixeltapete.de Pixeltapete] uses the hCard for the contactinformation of the authorpages of [http://www.pixeltapete.de/alex Alex] and [http://www.pixeltapete.de/carsten Carsten] and also for the [http://www.pixeltapete.de/kontakt imprint]. [http://www.pixeltapete.de Pixeltapete] uses its own [http://www.pixeltapete.de/2007/11/hcard-sidebarwidget-fuer-wordpress/ hcard widget] for wordpress sidebars.
* [http://www.thorsten-ott.de Thorsten Ott] uses hCard format for the contact section of his online resume.
* [http://rosebleed.net/ Rosebleed] supports [[hCard user profiles]] - your profile URL is <nowiki>http://rosebleed.net/users/profile.php/</nowiki> followed by your username, e.g. [http://rosebleed.net/users/profile.php/silvermoon82 silvermoon82].
**'''Fixed''' profiles now explicitly mark up 'n' where possible, otherwise omits it
* [http://www.whitepages.com WhitePages.com] Now WhitePages.com main implemented hCard on all its listings. Over 120 million hCards! Includes work information.
* [http://www.warmoth.com Warmoth Guitar Products] features hCard contact information in two places, [http://www.warmoth.com/customerservice/customer.cfm?fuseaction=order How To Order] and all of the [http://www.warmoth.com/catalog Warmoth E-Store]
* [http://www.bbc.co.uk/worldservice/bangladeshboat BBC World Service Bangladesh River Journey] a social network mashup, with hCard & other microformats. See [http://dharmafly.com/blog/bangladeshboat Dharmafly blog discussion].
* [http://www.amants-du-chocolat.net/ ACCP:Les Amants du Chocolat de la Couronne Parisienne] uses hCard on their contact page and in the chocolate maker they've reviewed.
* [http://www.accountviewsoftware.nl/ AccountviewSoftware.nl] makes use of hCards for the dealer directory [http://www.accountviewsoftware.nl/dir/ (directory)]
* [http://www.crystalvision.co.il/ CrystalVision] uses hCard on their contact page and in the footer throughout the site.
* [http://www.joshuamcginnis.com Joshua McGinnis] uses hCard to display his contact information to potential clients.
* [http://www.bo.ingv.it/contents/INGV-Bologna/Staff.html INGV Bologna] implemented hCards for staff-members, marked-up as HTML table-rows ([[include-pattern]] also used to add organization-name and fax-number to each hCard).
* [http://www.lefora.com Lefora] is a free forum hosting site (using custom forum software). Every user's profile contains an hCard. (Example forum for testing: [http://funstuff.lefora.com funstuff.lefora.com])
* [http://theultimates.whitepages.com WhitePages.com] A special version of whitepages.com has all its listings marked up in hCard.
* [http://piermontweb.com/contact/ Piermont Web Design] uses hCard on its contact page.
* [http://www.ie.asm.md/en/ The Institute of Power Engineering] of the Academy of Science of Moldova. First Moldavian site using hCards on staff pages, e.g [http://www.ie.asm.md/employees/oleschuk-valentin/]
**Also in Russian: [http://www.ie.asm.md/employees-ru/sit-michail-lvovich/] and Romanian: [http://www.ie.asm.md/angajati/chiorsac-mihail/]
* The good ship [http://styrheim.com/test/leonid.html Leonid Miloslavskiy] spotted in the North Atlantic
* [http://richi.co.uk/blog/2005/12/structured-blogging.html Richi Jennings] has put up his attempt
*[http://oberrycavanaugh.com O'Berry|Cavanaugh] has an organization hCard in the footer on every page as while as individual hCards on the [http://oberrycavanaugh.com/team.php Team] page.
* [http://fortisgc.com Fortis General Counsel], e. g. [http://fortisgc.com/joyce_lan_kim.html Joyce Kim's profile], uses hCard for profile and contact information.
* [http://peryplo.com Peryplo.com], e. g. [http://peryplo.com/personal/7e6786e711c6d051a39a1b7085f34955 Sample Page], uses hCard for Hotels, Gastronomy Places and services for tourists.
* [http://www.navitraveler.com/places/629/ NaviTraveler], e. g. [http://www.navitraveler.com/places/629/Lincoln_Memorial.html Lincoln Memorial], including [[geo|Geo]].
* [http://corewar.atspace.com/about.html sfghoul] has marked her contact info with [[hcard|hCard]]
* [http://www.zaadz.com Zaadz] uses [[hcard|hCard]] and [http://gmpg.org/xfn XFN] for friends on a user's profile page.
*[http://www.xoxiety.com/about.html Xoxiety] uses hCards on its about page, linking data from a within a block of text.
*[http://yedda.com Yedda] - Yedda provides hcard based identities on all of the people's profiles
*[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.
* [http://www.goldenglovepromotions.com/ Golden Glove Promotions] used hcards on the footer of every page to store contact information.
* Australian national news sites The Australian and Australian IT use hCard on their contact pages: [http://www.theaustralian.com.au/contactus The Australian (contact us)] and [http://www.australianit.news.com.au/contactus Australian IT (contact us)]
* [http://www.thekiwiholiday.com/ The Kiwi Holiday] uses hCards for [http://www.thekiwiholiday.com/view-hostels New Zealand Hostels], [http://www.thekiwiholiday.com/view-restaurants New Zealand Restaurants], and [http://www.thekiwiholiday.com/view-activities New Zealand Activities]. Also provides hCard "download to address book" functionality on listing detail pages, e.g. [http://www.thekiwiholiday.com/restaurant/tonys-steak Tonys Steak Restaurant]
* [http://www.qcindustries.com/ QC Industries Conveyors] uses hcards to store contact information in the site footer and in their [http://www.qcindustries.com/news/press-releases/ press releases].
* [http://www.confuciusinstitute.ac.uk/ The Confucius Institute for Scotland at the University of Edinburgh] has their used a hcard to store contact information in the footer of the page.
* [http://admnj.com/ Affiliated Direct Mail] is a New Jersey based direct mail company that has their contact information and footer in hCard format.
* [http://www.golfdigest.com/ Golf Digest] now supports hCard in its [http://www.golfdigest.com/courses/places Course Finder] detail pages. [http://www.golfdigest.com/courses/places/2483 example]
* [http://dev.opera.com/authors/ Dev Opera] Opera's developer site uses hCards on the author details pages.
* [http://chrischerry.name/ Chris Cherry's contact page with his hCard]
* [http://www.kiteboarder.com.au/php/search.php www.kiteboarder.com.au] A new Australian kiteboarding portal. Microformats have been used so that users can export the shops <s>directly to outlook</s>. I was able to learn microformats through the Media 2007 conference in London. Author: Damien King
* [http://krevi.dk/ KREVI] A Danish research institute. Using hCard in the footer of each page and on staff list. This is the first known danish website from the public sector of Denmark using microformats.[http://krevi.dk/om-krevi/organisation/medarbejdere example staff list]
* [http://www.hss.ed.ac.uk/web-team/ College of Humanities and Social Science Web Team's site], University of Edinburgh uses a hCard in the footer of each page.
* [http://www.theglobeandmail.com/ globeandmail.com] Canada's National Newspaper uses an hCard for their contact information.
* [http://www.logisteam.pl/ Krzysztof Rucinski] uses an hCard for his contact details on [http://www.logisteam.pl/kontakt.html Logisteam keylogger contact] page.
* Creation design & 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]
* [http://www.thomsonlocal.com/ ThomsonLocal.com], major UK business directory publisher, use hcard on the search results and company information pages.
* [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.
* [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.
* [http://www.feike.de/Kontakt.html Feike Contact] has a hCard on to top of the page.
* [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 cityguide page, and you can also find some hreviews as well (like on the [http://www.londondrum.com/hotels/athenaeum.php Athenaeum Hotel page])
* [http://www.regels-stadskanaal.nl/ Regelingenbank Stadskanaal] has a hCard on each page, containing Geo-information too.
* [http://www.tomstone.se Tom Stone - Trollkarl] has a hCard in the footer of each page of the site.
* [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.
* [http://twitter.com Twitter] uses hCard for user information (along with [http://ihack.us/2007/05/14/twitter-gets-microformatted/ several other microformats])
* [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.
*[http://www.pats.ua.ac.be/group PATS Group Members] uses hCard to mark up member contact information.
*[http://couchsurfing.com CouchSurfing] has limited information in hCard available on members' profiles (such as [http://www.couchsurfing.com/people/guaka Guaka's]).
* [http://kpumuk.info Dmytro Shteflyuk] uses an hCard on his [http://kpumuk.info/contact/ contact] and [http://kpumuk.info/curriculum-vitae/ curriculum vitae] pages.
* 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]
* [http://people.cs.uchicago.edu/~mpschaef/index.html Merrick Schaefer] is psyched to use hCard on his homepage for his contact info.
* Christian Hess (from San JosÃ©, Costa Rica) has an hCard in his [http://www.hess-cr.com home page], [http://www.hess-cr.com/utilidades/correo.shtml#postal contact] and [http://www.hess-cr.com/secciones/curriculum/datos.shtml personal rÃ©sumÃ©] pages (all in Spanish). He also recommends using the [https://addons.mozilla.org/es-ES/firefox/addon/4106 Operator] extension in Firefox to check them out.
* [http://www.JamPlanet.com Jam Planet] uses hCard in Contact Us page; application can generate hCard for a contact.
* [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].
* [http://www.buy-our-honeymoon.com/ Buy Our Honeymoon], a [http://www.buy-our-honeymoon.com/registry honeymoon registry] service, uses hCard in their [http://www.buy-our-honeymoon.com/contact Contact Us] page.
* '''W3C webmaster''' [http://www.w3.org/People/Jean-Gui/ Jean-Guilhem Rouel] now has an hCard.
* [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]
* [http://david.weekly.org/ David Weekly] has added an hCard to his home page for himself.
* [http://ficlets.com/stories/12 Ficlets] story page uses hCard for author bio.
* [http://redmonk.com/contact/ RedMonk Contact page] uses hCard for RedMonk firm as well as each analysts.
* [http://source.ibegin.com/ iBegin Source] uses hCard to identify business information for all 10.5+ million businesses listed.
* [http://cloudislands.com/contact.php Cloud Islands] uses hCard for our Contact Info.
* [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])
* [http://www.giraffo.de giraffo.de] has different hCards on every page (+ geo in "kontakt")
* [http://www.enap.com ENAP, Inc.] lists the HR Contact in hCard format on the [http://www.enap.com/career.aspx Career Opportunities] page.
* [http://sxsw07.conferenceer.com/people Conferenceer] lists panelists and participants to the 2007 South by Southwest interactive conference in hCard format
* [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.
* [http://www.wikiservice.at/fractal/wikidev.cgi?FR/EveMoreau ValÃ©rie-Eve Moreau] has an hCard on her wiki-homepage.
* [http://en.wikipedia.org/wiki/St_George%27s_Minster%2C_Doncaster St George's Minster, Doncaster, on Wikipedia]
* AOL Journals publishes hCards for authors. [http://journals.aol.com/carowill/whats-happening Example]
* Ian McKellar's [http://ian.mckellar.org/ home page] is an hCard that's styled to look like a business card.
* [[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&id=FR/MicroFormats/ChristopheDucamp edit it]. Any suggestions welcome.
* [http://www.matthewwest.co.uk Matthew West] has an hCard on his [http://www.matthewwest.co.uk/email contact] page.
*[http://www.webmaster.waw.pl PaweÅ Wrzosek] Freelance webdeveloper`s portfolio
*[http://www.stanford.edu/ Stanford.edu] hCard markup is included in the footer of the homepage and all subsequent pages within the /home directory.
*[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.
* [http://www.qwertycars.co.uk/garages/mechanics-near-tadworth-kt20.aspx UK Car Garages] Address of car mechanics in the UK, in hCard format.
* [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.
* [http://www.pointermix.com Pointermix Design] uses the hCard format.
* [http://eight6.com/contact/ eight6]'s contact page uses the hCard format.
* [http://www.raveaboutit.com.au Rave About It]'s business listings use the hCard format.
* [http://optics.org/cws/Contact/OurTeam.do optics.org]'s team page.
* [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.)
* [http://seattleu.edu Seattle University] uses hCard on it's front page and most pages that share an official template.
* [http://www.josemarti.waw.pl Jose Marti XXII Secondary School in Warsaw] includes hCard on Contact and About Author sections
* [http://www.jaama.co.uk Jaama] have their company details as a vCard download on their [http://www.jaama.co.uk/Contact.aspx contact] page.
* [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]
* [http://jc-development.co.uk/ JC's Development] has company contact details as hCard.
* [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]
* [http://www.xlntads.com XLNTads] has their contact information marked up in hCard, as well as their development schedule/timeline in hCalendar
* [http://derrick.pallas.us Derrick Pallas] tells people to look for him here.
* [http://bluemonkcreative.com/contact/ Bill Turner] adds an hCard to the contact page of his freelance business' website.
* [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.
* [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].
* [http://www.boogdesign.com/aboutus.html boogdesign.com] has added hCard markup on the contact page.
* [http://www.gptg.org/ Great Places To Golf], hCards for golf clubs around the world, e.g. [http://www.gptg.org/club/12/]
*[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.
* 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]].
*[http://wizardishungry.com/blog/ wizardishungry/blog] has the author's hCard in the footer of every page with a link to X2V.
* [http://www.walkerfineart.com Walker Fine Art Gallery] Most pages contain an hCard in the footer.
* [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.
* Scott Allan Wallick's hCard is [[User:ScottWallick|his user page]] and on his blog, [http://www.plaintxt.org/about/2/ plaintxt.org]
* [[User:Bob_Jonkman|Bob Jonkman's hCard]] '''on this 'wiki''''
* [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.
*OffshoreAgile.com, a subsite of Starsoft Development Labs, uses hCard in the [http://www.offshoreagile.com/company/contact/ Starsoft Contacts] and Media Inquiries sections
*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
* 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])
*[http://72ppi.us 72ppi], uses hCard in the footer.
*[http://www.csarven.ca Sarven Capadisli] uses hCard throughout the site (including user comments in articles).
* [https://www.urbanbody.com/information/contact-us Urban Body Men's Clothing] uses hCard for business locations and hCalendar for business hours.
* [http://www.iqair.us/ IQAir North America], uses hCard for contact information.
* [http://www.infoiasi.ro/ The website of the Faculty of Computer Science], "A. I. Cuza" University Iaşi, Romania uses hCard for each staff member.
* [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.
* 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.
* 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.
* [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
* [http://www.carolinemockett.com/design/about.aspx Caroline Mockett] has an hCard on her About Me page
* [http://wait-till-i.com Christian Heilmann] has a footer address using hCard
*[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.
* [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.
* [http://www.micatholicconference.org/ Michigan Catholic Conference] uses hCard for contact information in the sidebar.
* [http://www.adambunn.co.uk/ Adam Bunn] provides contact details in the sidebar using hCard.
* [http://www.belkin.com/pressroom/releases/uploads/10_10_06NotebookExpansionDock.html Belkin Press Releases] are using hCards for PR contacts and corporate offices.
* [http://mybank.com myBank.com] uses hCard for its listings of every branch of every FDIC-insured bank in the United States.
* [http://leftlogic.com Left Logic] uses hCard for embedded contact information.
* [http://inga-art.co.uk/artist Inga Scholes] uses hCard for contact information in the sidebar.
* [http://www.lussumo.com/ Lussumo] uses hCards on user profile pages in its open-source [http://www.getvanilla.com/ Vanilla] Discussions Forum software.
* [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.
* [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.
* 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.
* [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).
* [http://www.brown.edu Brown University] now uses hCard on the front page
* [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 & future contact pages for clients.
* [http://southamptonrubberstamp.com Southampton Rubber Stamp Company] now has hCard markup with a vCard download link on every page.
* [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 "Find"] 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.
* [http://dsingleton.co.uk/ David Singleton] has added a hCard to his blog.
* [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.
* [http://www.informatik.uni-hamburg.de/SVS/personnel/henrich/index.php Henrich C. Pöhls] has marked up his about page using hcard, including his PGP-Key that is stored in an abbr title, using class=key.
* [http://www.yalf.de Yalf Webentwicklung] has [http://www.yalf.de/kontakt contact information] available as hCard (and vCard).
* [http://www.zeldman.com/about/ Jeffrey Zeldman]. Jeffrey Zeldman has marked up his about page using hcard.
* [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.
* [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).
* [http://www.webdirections.org Web Directions]. hCard is used as contact information for the conference, while speakers are marked up with hCard.
* [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.
* [http://www.msiinet.com/contact/ MSI Systems Integrators] has its "Contact MSI" page encoded with hCards.
* [http://www.coolblue.nl/ Corporate website of Coolblue BV]. hCards were implemented in both the footer of each page, and in the "News" section for press contact information.
* [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.
* [http://2006.dconstruct.org/speakers/ d.Construct 2006 conference speakers list] is implemented using hCards.
* [http://local.yahoo.com Yahoo Local] now supports hCards for business and places in the search results
* [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.
* The [http://www.fuckparade.org Fâparade] website uses hCard, though I didn't find a type to distinguish mobile and landline phone numbers.
**Use <code>cell</code> for mobiles.
* [http://www.miranet.nl/contact.htm Miranet Webdesign] have added a hcard to their [http://www.miranet.nl/contact.htm 'contact' page]
* [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]
* [http://www.radiantcore.com Radiant Core] has their contact information [http://www.radiantcore.com/contact/ available in hCard].
* [http://www.mikerumble.co.uk/ Mike Rumble] has [http://www.mikerumble.co.uk/contact.html uploaded his hCard].
* [http://www.saumag.edu/ Southern Arkansas University] has its contact footer encoded as hCard
* [http://main.uab.edu/ University of Alabama at Birmingham] has its contact footer encoded as hCard
* [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)
* [http://main.uab.edu/shrp/ UAB School of Health Professions] uses hCard in its contact footer
* [http://green.carisenda.com/ Stephen Stewart] has his hCard on the front page of his weblog ('You are here' section)
* [http://www.direction.es/ Direction] uses hCard for contact information.
* [http://audiobank.tryphon.org AudioBank] uses hCard to display member informations.
* [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)
* [http://www.dougransom.com Doug Ransom] uses hCard for his financial advisory practice.
* [http://rubyandrails.org/usergroups/newcastle/members.html ncl.rb] uses hCard for contact information.
* [http://www.snowinteractive.com/ Snow Interactive] uses hCard for contact information.
* [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].
* [http://www.ndiyo.org/contact Contact information for the Ndiyo project]
* [http://www.pixelenvy.co.uk/ Pixel Envy] uses hCard for contact information on every page
* [http://stilbuero.de/contact/ Klaus Hartl] uses hCard in the sidebar for contact information (maybe easier to parse through delivering xhtml as xml).
* [http://charlvn.virafrikaans.com/contact Charl van Niekerk's hCard]
* [http://billy-girlardo.com/WP/ BillyBLOGirlardo] uses hCard for contact information.
* [http://www.hicksdesign.co.uk/ Hicksdesign] uses hCard for contact information.
* http://www.gr0w.com/articles/press/growsearch_launched_press_release/ - hCard in a press release for the press contact info
* http://www.redmonk.com/cote/archives/2006/03/testing_out_mic.html - hCard with explanation
* [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]]
* [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.
* [http://ChunkySoup.net/ ChunkySoup.net] has redesigned using hAtom 0.1 and hCards on the entire site -- by [[User:ChrisCasciano|Chris Casciano]]
* [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 > Syndication.
* [http://www.nearwhere.com/ Nearwhere.com] allow you to put an hcard on an interactive map.
* [http://www.brentozar.com/ Brent Ozar] added a [http://www.brentozar.com/contact.php contact] page hCard.
* [http://www.kerihenare.com/ Keri Henare] has rewritten his [http://www.kerihenare.com/contact/ contact] page hCard. Now using <code><object></code> instead of <code><img></code> for photo. (Thanks Brian Suda for updating the vCard converter)
* [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.
* [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
* [http://www.davidgagne.net/ David Gagne] has an hCard in his sidebar.
* [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.
* 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]
* 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&action=view&content=JonathanAquino profile] pages.
* [http://claimid.com/factoryjoe Chris Messina' ClaimID hCard]
* [http://factoryjoe.com/ Chris Messina' homepage]
* [http://flock.com/about Flock About]
* [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]).
* [http://www.gr0w.com/articles/press/growsearch_launched_press_release/ GrowSearch Launched (Press Release)] uses an hCard to provide Press Contact Point.
* 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].
* [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.
* [http://deadringrancor.livejournal.com/ Justin McDowell] used an hCard when [http://deadringrancor.livejournal.com/221332.html referring to a person in his blog post]
* [http://davecardwell.co.uk/cv/ Dave Cardwell] has included his hCard in his Curriculum Vitae.
* [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.
* [http://www.thefutureoftheweb.com/ Jesse Skinner] has written a simple [http://www.thefutureoftheweb.com/blog/2006/1/hcard tutorial with examples]
* [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.
* [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"])
* [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].
* [http://www.2sheds.ru Oleg "2sheds" 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])
* [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"])
* [http://weblog.200ok.com.au/ Ben Buchanan] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&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&format=search Ben's vCard] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&format=search Colin's vCard]
* WWF-Australia [http://wwf.org.au/about/contactdetails/ contact details page]
* [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]
* [http://amette.eu amette] uses the hCard format in a module of his TikiWiki powered blog and a more complete hCard on his [http://amette.eu/contact contact page]
* [http://staff.washington.edu/oren/weblog2/ Oren Sreebny] has an hcard on his blog main index template
* [http://www.cs.brandeis.edu/~zippy/ Patrick Tufts] has an hCard on his homepage.
* [http://ascii20.blogspot.com/ Mathias Kolehmainen and Jamie Taylor] have hCards on their weblog.
* [http://www.hoppsan.org/jamesb/blogger/ Barnaby James] has a hCard on his weblog.
* [http://esa-education.com/schools/map ESA Education] Uses hCards for their 100+ schools and each of the individual school sites.
* [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.
* [http://www.pierce.ctc.edu/ephone/ Pierce College] -- community college directory uses hCard on all individual directory entries.
* [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].
* 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.
* [http://www.musik-erber.de/ Musik-Erber] uses to present contact information at the sidebar
* [http://cdevroe.com/about/#contact Colin D. Devroe] uses hCard to display his contact information on his about page
* 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.
* [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.
* [http://www.vyre.com/company/contact-us/ VYRE] is a CMS development company with a "contact us" hCard
* [http://www.lefdal.cc/info.php Alf KÃ¥re Lefdal] uses hCard in the markup of his contact information
* [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
* [http://www.applianceman-repair-fortbend.com/ac-air-conditioning-repair-katy-tx.html Air Conditioning Katy TX] uses hCard in the footer of the air conditioning repair website. To view an example visit [http://www.applianceman-repair-fortbend.com/sugar-land-appliance-repair.html Appliance Repair Sugar Land]
* [http://kollitsch.de/ Patrick Kollitsch] has built his personal Profil as hCard
* [http://www.audiophile.pl/ Car Audio] uses the hCard in his contacts section.
* [http://www.hbs.edu/faculty/dspar/ Harvard Business School] has hCards on their faculty pages
* [http://openmikes.org/ openmikes.org] uses hCards for open mike venue addresses in its listing detail pages.
* [http://www.intertecnollc.com/ InterTecno, LCC] publishes an hCard on the home page and contact page.
* [http://canaltcm.com/ver/sobre-tcm Turner Classic Movies TCM Spanish website] has published contact details as a hCard
* [http://rejuvenation.com/ Rejuvenation] is now using hCard for contact information.
* [http://www.mattash.com/contact/ Matthew Ash] uses the hCard in his contacts section.
* [http://www.atbbuildinginc.com/ Kitchen Remodeling Detroit] uses the hCard in the footer section of the home remodeling website. To view an example visit [http://www.atbbuildinginc.com/kitchen-remodeling-farmington-hills.html kitchen remodeling farmington hills mi]
* [http://www.metrohomeimprovementsinc.com/ General Contractor Detroit] uses the hCard in the header section of the contractor website. To see example visit [http://www.metrohomeimprovementsinc.com/insulation.html insulation contractor detroit]
* [http://yarmouthguide.com/business.php Yarmouth Guide] uses hCard for each business details page.
* [http://www.merchantcircle.com MerchantCircle] has embedded an hCard in every one of their 15+ million US business listings.
* [http://citizenspace.us/citizens Citizen Space Citizens] is a list of tenants for a coworking space in San Francisco. The issue was raised that ''nicknames'' are usually located in the middle of ''fn'', which is not valid as per the [http://microformats.org/wiki/hcard-brainstorming#Implied_FN_from_N Implied_FN_from_N] rule. It seems that it should be possible, however, to include a ''nickname'' in the middle of an FN or even between a ''given-name'' and a ''family-name''.

* [http://www.brownbook.net The Brownbook - the open yellow pages] The Brownbook is a peer-produced (like a wiki, but not a using a wiki engine) local business search website. It Uses hCard to allow users to export local business contact details to Outlook or other desktop apps, plus for providing detailed maps from Google.
** Example of a search results page: [http://www.brownbook.net/business/search/?tag=hair+in+egham&x=21&y=4 Hairdressers in Egham]
*** '''suboptimal''': Adresses, e.g "2 Station Rd North, Egham, Surrey", are marked up as <code>street-address</code>
** Example of a single business's details [http://www.brownbook.net/business/view/122516 The Hair Emporium].
*** '''suboptimal''': Adresses, e.g "2 Station Rd North, Egham, Surrey", are marked up as <code>street-address</code>
* [http://www.Sylphen.com Sylphen] is a IT-solutions-provider and uses hCards on the [http://www.sylphen.com/content/kontakt/kontakt.htm Contact]
** '''invalid''' two of the three examples lack the required <code>fn</code> or <code>fn org</code> property
* [http://www.cosmotourist.com www.cosmotourist.com] and [http://www.cosmotourist.de www.cosmotourist.de] A new German and English portal around travel tips. Using hidden hCard for hotel listings, wherever address data is available.
**Hidden.
* [http://www.venncommunications.com/contact/ Venn] uses a hidden hCard on the contact page.
**Hidden.
* [http://www.last.fm Last FM] has hCards hidden on their profile pages e.g. [http://www.last.fm/user/Crok/?scrobbling=t1].
**Hidden.
* [http://krisswatt.co.uk/ Kriss Watt] has hidden an hCard his blog footer.
**Hidden.
* [http://www.fberriman.com/ Frances Berriman] has a hidden vCard in the footers of her website.
**Hidden.
* [http://www.candlescience.com/ CandleScience Candle Supply] added a hidden hcard sitewide.
**Hidden.
* [http://www.meryl.net/ Meryl K. Evans] has a hidden hCard on her homepage.
**Hidden.
* [http://www.highflyerscareers.com High Flyers Careers], India's first flight-crew placement agency uses microformats for their [http://www.highflyerscareers.com/corporate/ corporate information] page. Using standards couldn't be easier or better.
**Has honorific prefixes as part of "fn", rather than marked up separatley.
* Spotstor.com eg - [http://spotstor.com/] uses hCard on profile pages (where user has elected to show contact information).

* [http://www.naturalengland.org.uk/press/default.htm Natural England] (new UK government agency, formed 2006-10-01).
** No "fn" - which makes it invalid.
*[http://drop-off.co.uk G3:2] uses hCard with geo tags in the copyright and on the about me page
** Address data is hidden using CSS.
* [http://zdnet.co.uk/misc/contact/ ZDnet Contact Us Page] supports [[hcard|hCard]].
** by [http://www.subtleasafish.com/ James Myers] and [http://www.fromthefrontend.co.uk/2006/11/23/zdnet-uses-microformats/ David Long]
**Images and e-mail addresses are hidden; telephone numbers do not comply with [http://en.wikipedia.org/wiki/E.123 E.123]
* [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])
** (2005-09-27) PASSED, PASSED
** WARNINGS
*** uses 'n given-name' and 'n family-name' instead of nesting the given- and family- names inside the 'n'
*** has one 'tel' value with a bunch of values stuffed in
*** probably more problems --[[User:RyanKing|RyanKing]] 17:19, 5 Jan 2006 (PST)
* [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]
** 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)
* [http://landsbank.fo/#hCard Landsbanki FÃ¸roya]
** INVALID - using embedded RDF/XML invalidly

* [http://www.yellowpencil.com/contact/ Yellow Pencil] Using microformats to present company contact information
** First hcard has empty "fn" and no "n". "fn" should be with "org" -- [[User: ScottReynen |ScottReynen]] 21:29, 19 Jun 2006 (CST)

* [http://www.art-switch.com/ArtSwitch/contactUs.html Art-Switch Exchange Limited] uses hCard for their contact details on their contact page.
* [http://onyomo.com/ OnYoMo] uses hCard markup for all addresses listed in their local search results.
* [http://vcardplus.info/show.asp?uid=Z9959-06323 Greg Bays], the author of vCardPlus! has made his sites vCard display page hCard complaint.
* [http://www.rosenblittdentistry.com/contact.php Dr. Jon Rosenblitt] uses hCard icon with '''Add to Address Book''' link.
* [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].
* [http://shiftingpixel.com/about/the-artist shifting pixel photoblog] has published an hCard.
* [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
* [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 "Using hCards in your blog"].
* [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.
* [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.
** Inspired by this I thought to try the same for SVG at [http://barefoot-ceramics.com/find Barefoot] ...
** <img class="photo" style="display:none;" src="data:image/svg+xml;text,<?xml version='1.0' encoding='UTF-8' standalone='no'?><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'><defs id='defs3959' /><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' /></svg>" alt="Barefoot">
** Does it work?? Well it parses OK. Some automated tools replace the < 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.
* [http://cinematreasures.org Cinema Treasures] uses hCard to markup venue information for 10,000+ movie theaters.
* [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.
* [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
* [http://loadaveragezero.com/hnav/contact.php Douglas W. Clifton] added all types of contact information
* [http://eventful.com Eventful] publishes all of its venue information pages with embedded hCards.
* [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]
* [http://JackWolfgang.blogspot.com Jack L. Wolfgang II] has [http://jack.randomata.com/resume/ converted the addresses in his resume to hCards].
* [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
* [http://www.oliverbrown.me.uk/ Oliver Brown] has published his hCard.
* [http://www.paradigmproductions.org/contact/ Paradigm Productions] published a vCard as a <code>ul</code> (marked up by [http://www.linkingarts.com/ Peter Jacobson])
* [http://www.splintered.co.uk/ Patrick H. Lauke] has marked up [http://www.splintered.co.uk/about/ his contact info with hCard].
* [http://blah Paul Schreiber has published his hCard on [http://paulschreiber.com/about/?contact his about page].
* [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.
* [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.
* [http://www.windley.com/archives/2005/07/hcards_trying_o.shtml Phil Windley has published] [http://phil.windley.org/hcard.html his hCard].
* [http://www.go-curiosity.com/about.htm Piercarlo Slavazza] has published an hCard.
* [http://zooibaai.nl/ Rob Mientjes] has published his hCard on [http://zooibaai.nl/about/ his about page].
* [http://www.dumpsterrentalsdetroit.com/ Dumpster Rental Detroit] has published their hCard on the footer of every page see [http://www.dumpsterrentalsdetroit.com/ Kincaide Dumpster Rental].
* [http://rbach.priv.at/Contact Robert Bachmann] has published his hCard and [http://rbach.priv.at/Images/hcard a button].
* [http://blah Scott Reynen has published his hCard on [http://www.randomchaos.com/document.php?source=scott_reynen his profile page].
* [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.
* [http://www.wolfsreign.com Steven Ametjan] has published his hCard on [http://www.wolfsreign.com/about/ his about page].
* [http://tantek.com/microformats/2005/syndicate/speakers-list.html Syndicate - Speaker List] as a set of hCards
* [http://tagcamp.org/index.cgi?ContactList TagCamp contact list]
* [http://www.deadringerart.com/ The Brothers McDowell] have hCards at their Contact page.
* [http://twinsparc.com/ Twinsparc] put an hCard in the header and footer of all their pages.
* [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 Conference speakers page marked up with hCard]
* [http://www.uoguelph.ca/directory/ The University of Guelph] includes hCard info in its directory.
* [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!
* [http://www.cadforless.com/partners/ CADforless, Inc.] we listed our partners using hCard
* [http://avon.com/ Avon] - publishes all 40,000+ Avon representatives' contact info with hCard.
* [http://flock.com/about Flock About] page supports hCard microformat.
** by [[implementations#Flock|Flock]]
* [http://www.iowamilitaryveteransband.com/members/ Iowa Military Veterans Band]
* [http://www.nature.com/ Nature homepage], uses [[XOXO]].
** by [[implementations#Nature Publishing Group|Nature Publishing Group]]
* [http://concerts.shrub.ca/shows Sunnyvale House Concerts] supports hCard and [[hcalendar|hCalendar]].
* [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/139897 Mr T Natt] page.
* [http://www.monster-prague.cz/ Monster Prague Openings] supports hCard, e.g. home page, contact list to come.
* [http://www.vogelelaw.com/contact.html Colette Vogele] has an hCard on her contact page with many types of name and contact information. (Marked up by [http://www.talkingtiger.net Naomi Raine]).
* [http://www.fixya.com/repair/cars/us/ca/san_francisco FixYa] (the troubleshooting site) has an hCard (vCard) in the repair directory displaying information about all kinds service providers.
* [http://www.alive77.cn/ z.Yleo77] it's my blog, from now on,supports hCard, eg: article pages..
* [http://www.wfl-networks.co.uk/ WFL-Networks Computer Repair in Aylesbury] a localised IT Support company in Buckinghamshire, UK supporting hCard on its contact pages.
* [http://www.elcafedelcentre.com/index.html El Cafè del Centre] uses an hCard for his contact information in firts place.
* [http://www.petardos.org/index.php Petardos 4x4] uses an hCard for his contact information at the footer in all pages.
* [http://www.artimap.com artimap.com] uses vCards for helping the javascript in-page local search-engine.
* [http://www.handballkreis-koeln-rheinberg.de Handballkreis Köln/Rheinberg] uses hCard for contact informations of officials
* [http://www.evopapetarie.ro] uses hCard for contact page.
* [http://www.musiktagespflege-leichlingen.de Musiktagespflege Leichlingen] uses hCard for imprint and contact informations.
* [http://www.siam-property.com Siam Property Thailand] uses hCard for property consultants.
* [http://www.atbbuildinginc.com/ ATB Building Royal Oak MI] is using hCard on the contact page of their website.
* [http://www.badspiderbites.com/ Bad Spider Bites] uses hCard on their about page for customer submissions and contact information.
* [http://www.xn--mxacivya8br.net/ Φαψεβοοκ] Φαψεβοοκ uses hCard on their about page for customer contact information.
* [http://www.xn--oxaagxsa.com.gr/ Γοογλε] Γοογλε uses hCard on their [http://www.γοογλε.com.gr/terms/about-us/ about page] for their name and URL.
** one valid hCard, one invalid one.

== examples by category ==
'''Want hCard?''' Get started with writing an [[hcard|hCard]] using the [http://microformats.org/code/hcard/creator hCard creator] to write up some contact information, [[validators#hCard|validate]] and publish it, or following the [[hcard-authoring|hCard authoring tips]] to add hCard markup to your current site. Check out this section for similar examples of types of pages that benefit from hCard markup.

This section organizes examples into several rough categories as follows. If an example fits in more than one category, use the *last* matching category in this list that matches the specific hCard example(s) in the wild that you are trying to categorize.
# '''[[hcard-examples-in-wild#Individuals|Individuals]]''' - one card per person, perhaps sort alphabetically by "family-name". People with their own hCards (typically) on their own site.
# '''[[hcard-examples-in-wild#Organizations|Organizations]]''' - one card per organization, alphabetical by "fn". Organizations with their own hCard(s) (typically) on their own site.
# '''[[hcard-examples-in-wild#Institutions|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 "org" with perhaps a few individuals listed in a single sub-bullet, comma delimited, sorted by "family-name".
# '''[[hcard-supporting-user-profiles|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 company / service name.
# '''[[hcard-examples-in-wild#Online_Venues|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 "fn".
# '''[[hcard-examples-in-wild#Event_Speakers|Event Speakers]]''' - event pages where the speaker for the event is marked up with hCard.
# '''[[hcard-examples-in-wild#Speakers_Listings|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 "family-name".
# '''[[hcard-examples-in-wild#Group_Blogs|Group Blogs]]''' - blogs with multiple authors marked up with hCard
# '''[[hcard-examples-in-wild#Wiki_Templates|Wiki templates]]''' - community wikis that have templates that automatically generate hCards on pages
# '''[[hcard-examples-in-wild#Authors|Authors]]''' - pages about some other thing, such as books, perhaps reviews etc., which have marked up their authors with hCard
# '''[[hcard-examples-in-wild#Search_Results|Search Results]]''' - results pages from search engines (either generic or for people/organizations) that return people marked up with hCards.
# '''[[hcard-examples-in-wild#Listing_Contact|Listing Contact]]''' - contact information for a listing like a job posting, for sale offering, etc.

In addition there is a separate "[[hcard-examples-in-wild#UTF8_Examples|UTF8 Examples]]" 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.

As each section itself become quite large (we might be there already, once we sort through the above "Reviewed Examples"), 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.

=== Individuals ===
Groupings alphabetically by "family-name".

Nicely styled:
* [http://www.jaredhanson.net/ Jared Hanson]'s home page has a beautiful hCard with numerous ways of contacting him, and live updating of his online status on various messaging networks (uses javascript).
* [http://rogieking.com/#contact Rogie King]'s contact info is marked up with hCard and very nicely styled.
* [http://timvandamme.com/ Tim Van Damme]'s home page is a beautiful hCard.
* [http://paultarjan.com Paul Tarjan]'s home page has hCard and is a rel="me" hub
** needs a few minor fixes: http://tr.im/hctvd (links to hCard validator results)

Simple web pages (sorted by family name)
* [http://dbaron.org/ David Baron]'s home page is marked up with hCard.
* [http://abernier.name Antoine Bernier]'s UID hcard:
** Dynamic VCF download link (through [http://suda.co.uk/projects/microformats/hcard/get-contact.php?uri= hcard parser])
** Dynamic QRcode (through [http://microform.at/hcard2qrcode/ hcard2qrcode])
** Dynamic avatar (through [http://www.gravatar.com/ Gravatar])
** [http://wiki2008.openid.net/Delegation openID] ready
** [http://hcard.geekhood.net/?url=http%3A%2F%2Fabernier.name valid]
* [http://tantek.com/ Tantek Çelik]'s home page includes an inline author hCard at the bottom of the page.
* [http://christophertcressman.com/ Christopher T. Cressman] put his contact details on [http://christophertcressman.com/ Who is Chris Cressman?] and marked them up with hCard.

* [http://monkinetic.com/ Steve Ivy] with hCard and [http://monkinetic.com/about-this-site.html about page] with the usual suspects + XFN on 'url's, photo.
* [http://www.ryanmjones.com Ryan Jones]'s home page is also an hCard.
* [http://factoryjoe.com/hcard.html Chris Messina] has a page set aside with his contact details.
* [http://madebyjordan.com/ Jordan Moore]'s blog contains an inline hCard.
* [http://blog.roub.net/ Paul Roub] has an hCard for himself on his blog's home page.
* [http://www.w3.org/People/Smith/hcard/ Michael(tm) Smith has an hCard] on a page linked from [http://www.w3.org/People/Smith/ his W3C staff page]
** note lack of 'n' property but explicit use of 'given-name' and 'family-name' - more evidence we should drop the 'n' requirement (flatter is better) [[User:Tantek|Tantek]] 04:10, 6 May 2011 (UTC)
* Patrick Trettenbrein is the operator of [http://skateboardspot.info/ skateboardspot.info] and uses hCard on its [http://skateboardspot.info/cat/about#operator "about" page] for his contact info.
* [http://blogs.msdn.com/cwilso/ Chris Wilson] has an hCard for himself on [http://blogs.msdn.com/cwilso/about.aspx his about page].
* ...

Hidden! Invisible data is strongly discouraged, these examples have been grouped here in the hopes that the authors will someday make their hCards visible:
* [http://ajbrown.org/ A.J. Brown]'s home page includes a hidden hCard at the bottom of the page.

Former. URLs that seem to have broken.
* <nowiki>http://tomleo.com/about.html</nowiki> Tom Leo's about page had an hCard. (missing as of 2009-08-23)
* <nowiki>http://bogomil.info?l=en/</nowiki> Bogomil Shopov had an hCard for himself (missing as of 2011-125)

=== Organizations ===
Sites for specific organizations with their own hCard on home page, or contact/about page(s). Grouped by country, sorted alphabetically. When this section gets too big we can make a separate business directory page.

==== US orgs ====
* [http://www.pinewoodgroup.com/ Pinewood Shepperton plc] includes an hCard on their home page, and several more upon clicking their "Contact Us" button (found via [http://www.thedrum.co.uk/news/2011/09/07/25776-pinewood-studios-launch-website-created-by-multiply/ 2011-09-07 Pinewood Studios launch website created by Multiply] [[press]] article).
* [http://www.primerica.com/public/contact.html Primerica] uses hCard on "Contact Primerica" page for home office address.
* [http://RippleFxInc.com/ RippleFxInc.com] including both [http://blog.RippleFxInc.com/ Ideas Blog @ Ripple FX] and [http://wiki.RippleFxInc.com/ Knowledge Wiki @ Ripple FX] use hCard markup and allows for vCard download on their page footers; because they care, the same is standard on every site they design.
* [http://www.sfmoma.org/ San Francisco Museum of Modern Art] (SFMOMA)'s home page and pages in general have their address marked up in hCard.

==== Australia orgs ====
* [http://www.brdatasystems.com.au/contact-us.html B&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.

==== England orgs ====
* [http://www.alexandersremovals.co.uk/ Alexanders Removals] uses hCard for business address and contact details.
* [http://www.confidence2smile.co.uk/ Confidence 2 Smile] uses hCard for business address and contact details.
* [http://www.dovetaildental.co.uk/ Dovetail Dental] uses hCard for business address and contact details.
* [http://www.electricalcerts.co.uk/ Electrical Certs] uses hCard for business address and contact details.

==== Germany orgs ====
* [http://www.hsg-kl.de/impressum/index.php Hohenstaufen Gymnasium Kaiserslautern] has hCard contact info
** '''suboptimal''': <code>adr</code> subproperties are not recognized due to lack of explicit "adr" property.
*** evidence that has helped drive the flatter design of [[microformats-2]] including h-card which permits adr properties, e.g. 'street-address' directly inside the hCard instead of requiring an explicit 'adr' in the hierarchy. - [[User:Tantek|Tantek]] 01:46, 17 May 2012 (UTC)

==== Georgia orgs ====
* [http://www.serviceklimatistikon.gr/contact/ magiClima's contact page] uses for customer contact information.

==== Netherlands orgs ====
* [http://www.kdvkabouterbos.nl/ Kinderdagverblijf Kabouterbos], a day care / nursery that uses an hCard for their contact information (footer).

Mis-sorted - this should be moved to a search results section:
* [http://www.michrome.com Michrome Marketing Lists (UK)] use hCard on all their search result data. For example, [http://michrome.com/free-leads/162-Bradford-BD9 Startup Companies in Bradford].

Old: (these sites used to have hCard, some may have gone offline)
* <nowiki>http://technorati.com Technorati</nowiki> (2004-2011)
** <nowiki>http://technorati.com/about/ about, http://technorati.com/press/ press, and http://technorati.com/about/contact.html contact</nowiki> pages with hCard and have "Add to Address Book" links with the <nowiki>http://feed.technorati.com/contacts/ Technorati Contacts Feed service</nowiki>.
* <nowiki>http://technorati.jp Technorati Japan</nowiki> (2004-2011)
** <nowiki>http://technorati.jp/about/contact.html contact</nowiki> page marked up with hCard.

=== Institutions ===
* Mozilla's WebFWD [https://webfwd.org/about/experts/ experts] and [https://webfwd.org/about/team/ team] pages have hCards, including [[microformats-2]] h-card markup.
* [http://conferences.oreillynet.com/contacts.csp O'Reilly's Conferences Team page] has hCards for their team (~14) with a link to "Download the below contact info in vcf format" that uses the old Technorati contacts feed service to convert the hCards into vCards.
** needs updating to use [[H2VX]] instead of Technorati
** '''suboptimal''': The "org" shouldn't be hidden with "display:none". Instead, use the [[include-pattern]] to include the "org" from text elsewhere on the page (to avoid duplicating the text).

'''with some problems:'''
* The [http://www.ibm.com/contact/employees/ IBM Employee Directory] returns hCards in its query results
** E.g. [http://www.ibm.com/contact/employees/servlets/lookup?country=us&language=en&search_country=all&lastname=Kaply&firstname=Michael search for Michael Kaply],
** but with some problems:
*** '''invalid''': no "fn" (would be addressed by the [[hcard-brainstorming#Implied_FN_from_N|implied fn from n proposal]])
*** '''suboptimal''': adr has no children and thus is not providing any data (may be addressed by the [[hcard-brainstorming#implied_adr_subproperties|implied adr subproperties proposal]])
* [http://www.boltonmuseums.org.uk Bolton Museum and Archive Service] uses hCard on its
**[http://www.boltonmuseums.org.uk/about/contact/ Contacts] page
***'''invalid''': Several have no "fn"
**and on each of its visitor attractions pages e.g. on the [http://www.boltonmuseums.org.uk/visiting/findhallthwood/ Hall i' th' Wood location page].
***'''suboptimal''': "email" and "tel" properties mistakenly include "Email:" and "Telephone:" labels.
* [http://soap.stanford.edu/ Stanford Online Accessibility Program] has implemented hCard on every page
** '''suboptimal''': positioned off screen via CSS
* [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.
** '''invalid''': Example has 1 (out of 3) invalid hCard due to lack of "fn".
* [http://www.alexa.com Alexa Internet] marked up its [http://www.alexa.com/site/company/managers managers' page] with hCard.
** '''suboptimal''': job "title" is included inside within "fn" property.
* ...

old:
* 2005-2010(?) <nowiki>http://technorati.com/about/staff.html Technorati's Staff page had hCards for its employees (~31)</nowiki>
** E.g. <nowiki>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, etc.</nowiki>

=== Online Profiles ===
* See [[hcard-supporting-profiles]].

=== Online Venues ===
* [http://www.airfix.com/stockists-and-distributors/ Airfix Stockists and Distributors], e.g. [http://www.airfix.com/stockists-and-distributors/?postcode=b1+1bb&root_rid=1&search.x=0&search.y=0&search=search]
**'''suboptimal''': <code>street-address</code> contains street address, locality and region (e.g. "99 Hobs Moat Rd, Solihull, W. Midlands")
**'''suboptimal''': <code>postal-code</code> and <code>country-name</code> include preprended commas
**'''suboptimal''': <code>fn</code> is used; should be <code>fn org</code>
* [http://citysearch.com/ Citysearch] supports hCard (e.g. [http://seattle.citysearch.com/profile/10767458/seattle_wa/tulio_ristorante.html Tulio Ristorante in Seattle] and [http://sanfrancisco.citysearch.com/profile/46396865/san_francisco_ca/four_barrel_coffee.html Four Barrel in SF]) nested inside an [[hreview-aggregate]].
* [http://www.easthampshire.org/ easthampshire.org] - hCard on events and events map - e.g. http://easthampshire.org/eventdetail/wine_society_evening/1372606 and http://easthampshire.org/eventmap/wine_society_evening/1372606 built by [http://www.callendercreates.com Callender Creates]
* [http://rinklinks.ca/ RinkLinks.ca: A Comprehensive Rinks and Arenas Directory for North America] supports an hCards for listings in their directory.
* [http://www.sydneydirectory.org/ Sydney Directory Wiki] supports hCard and geographical coordinates for locations, e.g. the [http://www.sydneydirectory.org/index.php/Opera_House Sydney Opera House].

=== Event Speakers ===
* [http://fluentconf.com/fluent2012 O'Reilly fluent conference 2012] sessions, e.g. [http://fluentconf.com/fluent2012/public/schedule/detail/25831 Federated Wiki Mashes Data in Your Browser] have speakers marked up with hCard.
* ...

=== Speakers Listings ===
* ... lots more to add from events since 2007, e.g. every dConstruct etc.

==== 2007 ====
[[to-do]]: check 2007 [[presentations]] as they likely contain links to conferences that marked up their speakers page(s) with hCard.
* 09: [http://2006.dconstruct.org/speakers/ d.Construct 2007 speakers]
==== 2006 ====
[[to-do]]: check 2006 [[presentations]] as they likely contain links to conferences that marked up their speakers page(s) with hCard.
* 09: [http://2006.dconstruct.org/speakers/ d.Construct 2006 speakers]
==== 2005 ====
[[to-do]]: check 2005 [[presentations]] as they likely contain links to conferences that marked up their speakers page(s) with hCard.
* 12: [http://tantek.com/microformats/2005/syndicate/speakers-list.html Syndicate - Speaker List] (hCarded version hosted at tantek.com)
* 10: [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 Conference 2005 -- Speakers] (hCarded version hosted at tantek.com)
* 09: [http://web.archive.org/web/20051102094339/we05.com/ Web Essentials 05] - [http://web.archive.org/web/20051102094339/we05.com/presenters.cfm The Presenters] <nowiki>original URL: http://we05.com/presenters.cfm</nowiki> (appears to have stopped working as of 2007-12-18, perhaps earlier). Web Essentials 2005 (we05) was the [http://tantek.com/log/2005/10.html#d06t1720 first conference to adopt hCard and hCalendar] on their website and marked up all their presenters with hCard.

=== Group Blogs ===
* The [http://www.ibm.com/shortcuts/ IBM Shortcuts Podcast] has authors marked up with hCard but has some problems:
** '''hidden''': The root hCard element as well as every property contained therein is made invisible through a style attribute containing "position:absolute; visibility:hidden".

=== Wiki Templates ===
* Wikipedia
**Wikipedia-EN
*** People. 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 "infobox scientist; there's also "infobox military people", "infobox musician" and so on, almost ad infinitum). DoB is only included if it's entered using a birth-date template, not as raw text.
*** Places/orgs. 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.
***[http://en.wikipedia.org/wiki/Category:Templates_generating_Geo Wikipedia templates generating Geo]
****'''hidden''' - for example [http://en.wikipedia.org/wiki/List_of_Minnesota_State_Parks List of Minnesota state parks]; [http://en.wikipedia.org/w/index.php?title=Alberta_Highway_60&diff=prev&oldid=157308650 Alberta Highway 60]
****Note also removal of hCard properties, e.g. [http://en.wikipedia.org/w/index.php?title=List_of_Gaudi_Buildings&diff=prev&oldid=157704557 List_of_Gaudi_Buildings]
*** 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]
***Unfortunately, [http://en.wikipedia.org/w/index.php?title=Template:Infobox_Protected_area&diff=prev&oldid=152308153 other editors are already breaking some of the implementations on Wikipedia]; e.g. [http://en.wikipedia.org/wiki/Grand_Canyon_National_Park Grand Canyon National Park]; [http://en.wikipedia.org/w/index.php?title=List_of_islands_of_Argentina&diff=prev&oldid=155590535 removal of "region" attributes]
*** <s> 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]</s>
**Wikipedia-UK (Ukranian) 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]
* Wikiqueer
** [http://www.wikiqueer.org/w/Category:Templates_generating_hCards Wikiqueer templates generating hCards]
** [http://www.wikiqueer.org/w/Category:Templates_generating_microformats Wikiqueer templates generating microformats] in general

=== Authors ===
* [http://time.com TIME.com] marks up articles with hAtom including authors with hCard, e.g. [http://techland.time.com/2012/05/10/like-to-brag-on-facebook-or-twitter-thats-because-self-disclosure-is-like-eating-and-sex-says-study/ Like to Brag on Facebook or Twitter? That’s Because Self-Disclosure Is like Eating and Sex, Says Study]
* [http://lazylibrary.com LazyLibrary] uses author hCard's on every book page. Example: [http://lazylibrary.com/book/0751370576]
** '''suboptimal''' [http://lazylibrary.com/book/0751370576 Example] has an fn of "Dorling Kindersley, David West Reynolds" which should be split into two hCards! (site would also benefit from hReview).
* ... many more (e.g. see unsorted list above, verify and move here)

=== Search Results ===
* [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.
** '''invalid''': attempt to use Implied-N optimization where that's not possible,
** '''suboptimal''': honorific-prefix could be explicitly marked up
*** Error appears for external users only. Won't be fixed any time soon. -- [[User:PhilWilson|PhilWilson]] 00:03, 28 Jan 2006 (GMT)
* [http://www.yourtraces.com/social_index.php YourTraces SocialSearch] Try ''high results'' (hohe Relevanz) to get only websites marked with hcard as a person.

=== Listing Contact ===
Contact information for listings, e.g. job postings, items for sale, etc.
* [http://bestsecurityjobs.co.uk/ Best Security Jobs] is a UK jobs board that uses hCard on the homepage for job listings.
* [http://seogadget.co.uk/search-marketing-executive-upto-30k-portsmouth/ search marketing executive] published by [http://seogadget.co.uk/ SEOgadget].
** '''invalid url property''' - href of the url property element lacks <nowiki>http://</nowiki>, thus being invalid and linking to a non-existent relative URL.
** '''invalid XHTML''' - W3C validator reports this page as [http://validator.w3.org/check?uri=http://seogadget.co.uk/search-marketing-executive-upto-30k-portsmouth/ XHTML 1.0 Transitional] (109 errors as of 2009-08-20).

===UTF8 Examples===
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. Sorted roughly alphabetically (per Unicode).
* [http://imageconcept.ru/contacts.html ImageConcept (ИмиджКонцепт)] embedded UTF8 encoded hCard with Russian characters in «Contacts» page of website.
* [http://sphinx.net.ru/author/ Dmitry Dzhus] embedded his UTF8 encoded hCard with Russian characters in Â«AuthorÂ» page of his website.
* [http://ecdlweb.com/ ECDLWeb.com] encodes hCard and Geo information of ECDL and ICDL test centres in UTF-8. Test case for Central European ([http://ecdlweb.com/en/czech-republic/sps-ceska-lipa Czech], [http://ecdlweb.com/en/hungary/athene-idegenforgalmi-informatikai-es-uzletemberkepzo-szakkozepiskola Hungarian] etc.) and [http://ecdlweb.com/en/belarus/belhard Cyrillic] characters.
* [http://tantek.com/ Tantek's Thoughts] encodes Ãelik as inline UTF8.
* [http://technorati.jp/about/contact.html Technorati Japan contact information] encodes Japanese as inline UTF8.
* [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))

==== nickname only ====
These UTF8 examples only have UTF8 for the "nickname" property and are thus are a bit easier for testing than the previous examples.
* Various Wikipedia-EN articles, e.g. the "nickname" 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)

===non-HTML examples===
* [http://dannyayers.com/misc/microformats/hcard-svg Danny Ayers' SVG hCard demo]

=== missing ===
Examples that used to have one or more hCards but now don't seem to have any. If you do find one, please include direct links to at least two (assuming there are two or more) pages at the referenced site that have one or more hCards.
* [http://mapquest.com Mapquest] now supports hCards for business and places in the search results (e.g. [http://www.mapquest.com/maps/map.adp?searchtype=address&country=US&searchtab=home&formtype=address&cat=Whole+Foods&city=san+francisco&state=ca search for Whole Foods in San Francisco])
** appears to be missing hCards as of 2008-09-07

== related pages ==
{{hcard-related-pages}}
* [[hcalendar-examples-in-wild|hCalendar examples in the wild]]

neaby-metro-station

2015-05-04T18:42:19Z

TomMorris: documenting

This page is to document websites and offline material that provides information about the closeness to train, metro, tram or other transport station data on pages.

== Rationale ==

In London, people commonly refer to an area by the London Underground station closest to it and that station name often becomes a shorthand for the area near it. For example, the area around King's Cross station is commonly referred to as "King's Cross" rather than its older, pre-railway name, Somers Town.

Some London area names are not widely known: Nine Elms is close to Vauxhall station but if one wished to provide directions to that area, simply stating it is "near Vauxhall" is more instructive for most people.

Obviously, directing people to a nearby station serves a practical purpose - enabling people to get to a location via public transport.

Why not just take the geo coordinates of a location and then (using data from a service like OpenStreetMap, perhaps) find the nearest train station? Simply working out as the crow flies where the nearest station is won't necessarily help. Sometimes a station might be a short distance further but provide more reliable or frequent connections. Sometimes the walk to a closer station might take longer for pedestrians because of a complex road system and having to make lots of crossings. Perhaps a natural feature like a river is in the way.

== Examples ==


* [http://www.beerintheevening.com/ Beer in the Evening]: [http://www.beerintheevening.com/pubs/s/14/14594/Royal_Vauxhall_Tavern/Vauxhall example listing], shows distance from nearby London Underground and National Rail stations
* [http://www.rightmove.co.uk/ Rightmove]: [http://www.rightmove.co.uk/property-to-rent/property-51986918.html example listing], shows distance to 3 nearest London Underground/Overground and National Rail stations
* ...feel free to add more...

location-examples

2015-05-04T18:28:33Z

TomMorris: nearby metro station

<h1>location examples</h1>
{{TOC-right}}
Part of the [[location]] microformat efforts.

== anecdotal ==
Originally added to [[location-formats]], people have seen:

* links to mapping services, canonical URLs to 3rd party services like:
** Google Maps
** Map Quest
** Yahoo Maps

* human / named / legislated formats
** named places, e.g. Westin St. Francis
** addresses, including zip codes

* global/mathematical/geometrical
** Latitude / Longitude / Altitude
*** MAKE has a GeoURL button
*** Geo in RSS. Means a particular blog post is associated with a specific lat/long. Not specific about whether it means the location that the post was made from or the location was the post was about.
*** Most systems do not contemplate or support the altitude component of a coordinate. As 3D terrain mapping grows in popularity (Google Earth), expect geocoding systems to provide the altitude.

Find URLs for each of the above, and move them from this '''anecdotal''' section to the below '''real world examples''' section.

== real world examples ==
Links to public web pages, either popular or insightful.

=== latitude longitude ===
People actually do publish latitude and longitude in human visible text.

* [http://lhc-first-beam.web.cern.ch/lhc%2Dfirst%2Dbeam/practical.html LHC First Beam] announcement page:
** "<nowiki>GPS: 46°13'59'' N; 6°3'20'' E</nowiki>"

== existing practices ==
Summary of common patterns discovered.

== see also ==
* [[location]]
* [[location-formats]]
* [[location-brainstorming]]
* [[neaby-metro-station]]