Microformats Wiki - User contributions [en]

hcalendar-implementations

2006-12-06T07:22:38Z

TKluge: added reference to phpMicroformats

<h1>hCalendar Implementations</h1>

This page is '''informative'''.

The following implementations have been developed which either generate or parse hCalendars. If you have an [[hcalendar|hCalendar]] implementation, feel free to add it to the New Implementations section.

==New Implementations==
Add new implementations here:
* ...

==Authoring==
Implementations you can use to author, create, and publish hCalendar events.

===Blogging and CMS tools===
;Midgard CMS : [http://www.midgard-project.org/documentation/net-nemein-calendar/ Midgard CMS - net.nemein.calendar] - as [http://bergie.iki.fi/blog/new-event-calendar-for-midcom.html blogged by Henri Bergius]

;Drupal module : [http://hybernaut.com/upcoming-hcal Drupal Upcoming.org syndication module emits hCalendar]
;MovableType and WordPress plug-ins : [http://structuredblogging.org/formats.php StructuredBlogging] is a set of plugins [http://structuredblogging.org/structuredblogging-wp-latest.zip for WordPress] and [http://structuredblogging.org/structuredblogging-wp-latest.zip for MovableType] that supports embedding hCalendar and other microformats in templates and blog posts.
;Textpattern plug-in : [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCalendar and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].

===Browser scripts and plug-ins===
Browser plugins that work with existing authoring tools:
; Any browser with javascript and a little bit of CSS : [http://microformats.org/code/hcalendar/creator microformats.org hCalendar creator] (see also original: [http://theryanking.com/ Ryan King] has an [http://theryanking.com/microformats/hcalendar-creator.html hCalendar creator]).
; Firefox Greasemonkey user script hCalendar creator : [http://www.decafbad.com/blog/2005/06/08/greasemonkey_magic magic_hcalendar Greasemonkey user script by Les Orchard] - allows easy form entry of an event into any textarea, e.g. into a blog post text area.
; Firefox Greasemonkey user script hCalendar to Google Calendar: [http://torrez.us Elias Torres] has created a [http://torrez.us/archives/2006/04/13/431/ simple script] that will parse hCalendar entries and create a link to add event to [http://www.google.com/calendar/ Google Calendar's] service. Based on [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats George's] and [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats Arve's] work.

===Desktop Authoring Tools===
;Dreamweaver Extension : [http://www.webstandards.org/action/dwtf/microformats/ Extension suite] for Dreamweaver 8 from the [http://webstandards.org/ Web Standards Project].
;xfy :
In [https://www.xfytec.com/community/ xfy Community], there are some hCalendar implementations.

* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=15&lid=25 hCalendar via RSS] parses an RSS feed, retrieves XHTML documents linked from that feed, and syndicates hCalendars into a calendar view.
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=19&lid=23 hCalendar Marker XVCD] helps to mark up an event information in XHTML document with hCalendar.
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=15&lid=17 Simple RDF Calendar XVCD] is a schedule tool which uses RDF Calendar format. It also converts RDF Calendar format to iCalendar and hCalendar format.

==Search and Discovery==

* [http://kitchen.technorati.com/search Technorati Microformats Search] indexes [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] as [http://tantek.com/log/2006/05.html#d31t1802 announced by Tantek].
* [http://leftlogic.com/info/articles/microformats_bookmarklet Microformats Bookmarklet] is a bookmarklet designed for Safari (works in Firefox and Camino) that overlays on the current page to allow users to import individual [[hcard|hCards]] or [[hcalendar|hCalendars]]. Written by [http://leftlogic.com Remy Sharp].

==Conversion and Import==
Implementations you can use to importing into a Calendar Application, typically by converting hCalendar to iCalendar/vCalendar.

===Web Services===
These return iCalendar (.ics) and other calendar formats for easy importing into typical calendar programs or other processing.
* [http://feeds.technorati.com/events Technorati Events Feed service] uses X2V library to parse hCalendar and return iCalendar (.ics). Note friendly URL, e.g. http://feeds.technorati.com/events/http%3A//microformats.org
* [http://suda.co.uk/projects/X2V/ X2V] parses hCalendar and produces a .ics (iCalendar) stream. Note: needs to be updated to track changes in the specification as they occur.
* [http://lifelint.net/ Life Lint Parser] parses hCalendar and produces .ics, .rdf and debugging information and attempts to be more fully compliant to the iCal standard than previous implementations. It can be used in the same manner as X2V. Can output iCal (w optional Outlook 2002 compat), and RDF.
* [http://spanningsalesforce.com/ Spanning Salesforce] produces hCalendar-enabled RSS feeds and .ics calendars from Salesforce.com.
* [http://makedatamakesense.com/myspace/event/ MySpace Events RSS Creator] creates RSS feeds of MySpace events with hCalendar markup.

===Firefox Greasemonkey Plugins===
* [http://george.hotelling.net/90percent/ George] has built a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script that detects hCalendar events and allows users to easily add them to their calendar application(s)].
* [http://inside.glnetworks.de/ Martin Rehfeld] has updated the work of [http://blogmatrix.blogmatrix.com/ David Janes] and produced a [[Greasemonkey]] [http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ script] that finds many microformat elements, including hCalendar events, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. The hCalendar to vCalendar conversion is done internally within the script. ''This will work with FireFox 1.5+/GreaseMonkey 0.6.4+ now.''

===Aggregators===
* [http://placenamehere.com/mf/nnwextract/ Extract Microformats] is a script for NetNewsWire that supports extracting hCard and hCalendar data in blog posts (via technorati service). Written by [[User:ChrisCasciano|Chris Casciano]]
* [http://kula.jp/software/endo/screenshots/ Endo], an OS X aggregator, supports discovering hCal and adding those events to iCal. Look at the last screenshot at the bottom of the page.

==Browsing==
Implementations that detect, display and otherwise highlight hCalendar events in pages.

* In [http://www.xfytec.com/community/ xfy Community], there are some hCalendar implementations. "hCalendar via RSS" parses an RSS feed, retrieves XHTML documents linked from that feed, and syndicates hCalendars into a calendar view.
* [http://web.mit.edu/glasser/www/JSCalendar/ JSCalendar] parses hCalendar and produces a displayable HTML table/CSS-based calendar.

===Firefox extension===
*[http://blog.codeeg.com/tails-firefox-extension/ Tails is a Firefox Extension] that will display the presence of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage.

====Pending====
*[http://reminderfox.mozdev.org/ ReminderFox] have hCalendar import on their "to do " list.

===Flock extension===
*[http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar

==Libraries==
Open source libraries of hCalendar parsers and other related code for building hCalendar implementations.
; Javascript : [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats simple hCalendar parser] by [http://virtuelvis.com/ Arve Bersvendsen]
; PHP :
*[http://randomchaos.com/microformats/base/ Microformat Base] is an open-source PHP microformat aggregation crawler, currently recognizing hreview, hcalendar, and hcard.
*[http://enarion.net/phpmicroformats/ phpMicroformats] is a PHP class library that generates microformats for calendar events (hCalendar) and vcards (hCard).
* [http://fresh.t-systems-sfr.com/unix/src/www/WebCalendar-devel-1.1.1.tar.gz:a/WebCalendar-1.1.1/includes/classes/hKit/hcal.profile.php hCalendar profile] for the [http://allinthehead.com/hkit/ hKit] parser.
; Ruby : [http://opensource.reevoo.com/2006/03/08/release-uformats-12/ uformats] is a ruby library that can parse [[hCalendar]], [[hCard]], [[hReview]] and [[rel-tag]]
; XSLT :
* X2V is available as an XSLT library
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] by [[User:DanC]] includes toICal.xsl and test materials; it works much like xhtml2vcal.xsl in X2V. See also: [http://www.w3.org/2002/12/cal/ RDF Calendar workspace] with icalendar test materials.

==Potential implementations==

These are open source projects that could be potentially enhanced to support hCalendar.

* [http://www.k5n.us/webcalendar.php?topic=About WebCalendar]
* [http://phpicalendar.net/documentation/index.php?title=Main_Page PHP iCalendar]
* [http://www.vcalendar.org VCalendar]
* Investigation: [http://wiki.mozilla.org/Calendar_Talk:Lightning#hCalendar_publish_and_subscribe_support Mozilla Calendar / Lightning / Sunbird hCalendar support discussion]

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

implementations

2006-12-02T22:13:41Z

TKluge:

<h1>Microformats Implementations and Implementers</h1>

This page lists the applications, plugins, sample code, services, tools that produce or consume microformats as well as companies, developers, and organizations who implement the aforementioned. This is only a partial list. If you know other companies implementing tools for microformats, please add them and list their services/tools and what specific microformats they support.
__TOC__

== Implementations vs. Examples in the Wild ==

This page is ''only'' for implementations of tools that publish or consume microformats. Companies simply ''using'' microformats on their pages/sites belong in the "Examples in the wild" sections of those respective microformats, e.g.:
* [[hcard-examples-in-wild|hCard Examples in the wild]]
* [[hcalendar-examples-in-wild|hCalendar Examples in the wild]]
* etc.

== Editing This Page ==

This page is primarily composed of two big lists:
* [[implementations#Applications_.2F_Plugins_.2F_Services_.2F_Tools|Applications / Plugins / Services / Tools]]
* [[implementations#Companies_.2F_Developers_.2F_Organizations|Companies / Developers / Organizations]]

When you find an implementation, first make sure that it is ''actually'' an implementation as opposed to ''just'' an [[hcard-examples-in-wild|example in the wild]] of publishing microformats (see above).

Second, note the name of the ''tool or service'' separately from the name of the ''developer(s)'' who wrote the tool/service.

Add a third level heading with the name of the tool/service ( <code>=== Name of Tool ===</code> ) to the Applications / Plugins / Services / Tools section, sorted alphabetically by name of tool/service. Add a top level list item (*) just below the heading with an external link to the tool/service, along with a link to evidence of their support for microformats, and mention (and locally link) each microformat that is supported.

Add a nested list item <code>* by Name of Developer</code> and local hyperlink the Name of Developer to a fragment identifier in this page, e.g. Apple Computer would be linked like this: <code><nowiki>[[implementations#Apple_Computer|Apple Computer]]</nowiki></code>

Check to see if there is an entry for the developer in the list of Companies / Developers / Organizations, if not add a third level heading with the name of the developer ( <code>=== Name of Developer ===</code> ), alphabetically sorted by name of developer. Add a link to the developer's home page followed by "has implemented microformats in:".

In the entry for the developer, add a list item <code>* Name of Tool</code> and local hyperlink the Name of Tool to a fragment identifier in this page, e.g. X2V would be linked like this: <code><nowiki>[[implementations#X2V|X2V]]</nowiki></code>

Save the page and make sure that each fragment ID local hyperlink when clicked scrolls you to the right spot (for the developer, and for the tool). Make any fix-up edits as necessary. That's it!

== Formats ==

Most microformat specifications have an "implementations" section, e.g.:
* [http://microformats.org/wiki/hcalendar#Implementations hCalendar], [http://microformats.org/wiki/hcard#Implementations hCard], [http://microformats.org/wiki/rel-tag#Implementations rel-tag], [http://microformats.org/wiki/vote-links#Implementations vote-links], [http://microformats.org/wiki/xoxo#Implementations XOXO] etc.

In addition, some microformat specifications have separate implementation pages:
* [[xfn-implementations]]

== Applications / Plugins / Services / Tools ==

This is an alphabetical listing of all applications, plugins (grouped with their app/tool), services and tools that implement microformats, along with the list of microformats that are supported, and the company and/or developers responsible for it.

As a user, the implementations listed below will automatically help you use microformats and help your data portability and interoperability with other apps and services.

Please help complete this list! If you know of additional apps/plugins/services/tools that support microformats, please add them!

Note: this section is only for listing specific ''implementations''. The list of ''implementors'' is in the [[implementations#Companies / Developers / Organizations|Companies / Developers / Organizations]] section below.

=== .Mac Webmail ===

* The [http://www.mac.com/webmail .Mac Webmail] ''service'' now [http://factoryjoe.com/blog/2006/10/28/apple-embraces-microformats-in-new-mac-webmail/ supports hcard].
** by [[implementations#Apple_Computer|Apple Computer]]

=== Blinksale ===
* [http://blinksale.com Blinksale] uses [[hcard|hCard]] standard throughout for people and companies.

=== BlogMatrix ===
* [http://www.blogmatrix.com BlogMatrix] - user information marked as [[hcard|hCard]], tag directories in [[xfolk]]/[[rel-tag]], enclosures are marked as [[rel-enclosure]].
** by [[implementations#David_Janes|David Janes]]

=== Blogmarks.net ===
* [http://www.blogmarks.net Blogmarks.net] publish user bookmarks in [[xfolk]]/[[rel-tag]].

=== Community Server ===
* [http://communityserver.org Community Server] supports tagging posts with [[rel-tag]], implements [[rel-nofollow]] on links in comments, and allows users to create link lists using [http://gmpg.org/xfn/ XFN].

=== Citycita===
* [http://www.citycita.org Citycita] supports [[hCal|hCal]] in all event pages for local social groups.
** by [[implementations#Rubio_Jamin|Rubio Jamin]]

=== Cork'd ===
* [http://corkd.com Cork'd] supports [[hcard|hCard]] for user profiles, [[hreview|hReview]] for wine reviews, along with [[rel-tag]] for tagging wines as announced in [http://www.simplebits.com/notebook/2006/06/10/wineformats.html Pairing Wine and Microformats]
** by [[implementations#Dan_Cederhold|Dan Cederholm]]

=== Dreamweaver ===
==== Microformats Extensions ====
* [http://www.webstandards.org/action/dwtf/microformats Dreamweaver Microformats Extensions] ([http://allinthehead.com/beta/microformats.mxp.zip download]) support authoring [[hcard|hCard]], [[hcalendar|hCalendar]], [http://gmpg.org/xfn XFN], [[rel-tag]], [[rel-license]] as [http://allinthehead.com/retro/282/microformats-in-dreamweaver announced by Drew]
** by [[implementations#Drew_Mclellan|Drew McLellan]]

=== Drupal ===
==== Upcoming module for Drupal ====
* [http://hybernaut.com/upcoming-module Drupal Upcoming.org syndication module] emits [[hcalendar|hCalendar]]
** by [[implementations#Brian_Del_Vecchio|Brian Del Vecchio]]

=== EVDB ===
* [http://evdb.com EVDB] / [http://eventful.com Eventful] supports [[hcalendar|hCalendar]] for over 1,000,000 event listings and [[hcard|hCard]] for venues.

=== Finetoothcog ===
* [http://finetoothcog.com/site/stolen_bikes Stolen Bikes] now supports [[hcalendar|hCalendar]] for reported stolen bikes. Also provides iCal subscription.

=== Firefox ===
* [[firefox-extensions]]
* [[greasemonkey]] scripts for Firefox
*Mozilla are "brainstorming" developments for Firefox 3.0 and beyond, and have a page on microformat handling at http://wiki.mozilla.org/Firefox/Feature_Brainstorming:Microformat_Handling

==== Tails Firefox Extension ====
* [http://blog.codeeg.com/tails-firefox-extension-03/ Tails Firefox Extension 0.3] by [[implementations#Calvin_Yu|Calvin Yu]]
** Latest Release: [http://codeeg.com/tails/tails-0.3.3.xpi Tails Firefox Extension 0.3.3] (Firefox 1.4+, Flock 0.7+)

==== Tails Export Firefox Extension ====
* [https://addons.mozilla.org/firefox/2240/ Tails Firefox Extension 0.3.1] by [[implementations#Robert_de_Bruin|Robert de Bruin]]
** Latest Release: [https://addons.mozilla.org/firefox/2240/ Tails Firefox Extension 0.3.1] (Firefox 1.5+)

=== FunAdvice ===
* [http://funadvice.com FunAdvice] supports using the rel-nofollow tag to prevent users posting content simply for the search engine benefit, to improve teh quality of the advice giving community.

=== Gravatar Commenters as hCards ===
* [http://thedredge.org Andy Hume] added code to his blogging software to automatically mark-up the names and URLs of commenters on his blog with [[hcard|hCard]].
** by [[implementations#Andy_Hume|Andy Hume]]
** Andy - any chance of open sourcing your code to turn Gravatars into hCards?

=== faberNovel ===
* [http://www.fabernovel.com/contact faberNovel] supports [[hcard|hCard]]
** by [[implementations#Marie-Caroline_Lanfranchi|Marie-Caroline Lanfranchi]]

=== Flickr People ===
* [http://flickr.com/ Flickr]'s profiles on its people pages supports both [[hcard|hCard]] and [http://gmpg.org/xfn XFN].
** by [[implementations#Cal_Henderson|Cal Henderson]]
**[http://flickr.com/people/tantek example]

=== Flickr Photos ===
* [http://flickr.com/map/ Flickr's geo tagged photos] are marked up with the [[geo]] microformat.

=== Flock Web Browser ===
* The [http://flock.com Flock web browser] supports the [[rel-tag]] microformat.
** by [[implementations#Flock|Flock]]

=== Google Search ===
* [http://google.com/ Google Search] - supports [[rel-nofollow]]
=== Google Creative Commons Search ===
* [http://www.google.com/webhp?as_rights=(cc_publicdomain%7Ccc_attribute%7Ccc_sharealike%7Ccc_noncommercial%7Ccc_nonderived) Google Creative Commons Search] - supports [[rel-license]]

=== hCalendar creator ===
* [http://microformats.org/code/hcalendar/creator hCalendar creator] (originally [http://theryanking.com/microformats/hcalendar-creator.html published by Ryan King]) is a javascript form for creating [[hcalendar|hCalendar]] events.
** by [[implementations#Ryan_King|Ryan King]]

=== hCard creator ===
* The open source [http://microformats.org/code/hcard/creator hCard creator] (originally [http://tantek.com/microformats/hcard-creator.html published by Tantek]) is a very simple, yet illustrative, open source user interface / form / script which creates an [[hcard|hCard]] in real-time as you type in a set of contact information.
** by [[implementations#Tantek_Çelik|Tantek Çelik]]

=== hKit Microformats Toolkit for PHP5 ===
* [http://allinthehead.com/hkit hKit Microformats Toolkit for PHP5] as [http://allinthehead.com/retro/291/hkit-microformats-toolkit-for-php announced by Drew McLellan]

=== hReview creator ===
* [http://microformats.org/code/hcalendar/creator hReview creator] (originally [http://theryanking.com/microformats/hreview-creator.html published by Ryan King]) is a javascript form for creating [[hreview|hReviews]].
** by [[implementations#Ryan_King|Ryan King]]

=== Ice Rocket ===
* [http://icerocket.com] - [http://blogs.icerocket.com/tag/ supports] [[rel-tag]]

=== iChat buddy list to hCards ===
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards.
** by [[implementations#Tantek_Çelik|Tantek Çelik]]

=== JSCalendar ===
* [http://web.mit.edu/glasser/www/JSCalendar/ JSCalendar] parses [[hcalendar|hCalendar]] and produces a displayable HTML table/CSS-based calendar.

=== Konqueror ===
* [http://www.konqueror.org/ Konqueror] - [http://flickr.com/photos/factoryjoe/68755089/ supports] [[hcard|hCard]]

=== Last.fm ===
* [http://last.fm Last.fm] - [http://factoryjoe.com/blog/2006/10/31/lastfm-adds-support-for-hcalendar/ Last.fm supports] [[hcalendar|hCalendar]]

=== Laughing Squid Calendar ===
* The [http://laughingsquid.com/squidlist/calendar/ Laughing Squid Calendar] events listings support [[hcalendar|hCalendar]].
** by [http://laughingsquid.com/ Laughing Squid]

===LinkedIn ===
* [http://www.linkedin.com LinkedIn] - LinkedIn includes [[hcard|hCard]] on profiles and [[hreview|hReview]] on service provider recommendations
** by [[implementations#Chris Saccheri|Chris Saccheri]]

=== LiveJournal ===
* [http://www.livejournal.com LiveJournal] - LiveJournal supports tagging posts with [[rel-tag]].

=== LJFind ===
* [http://www.ljfind.com LJ-Find] - LJFind supports tagging posts with [[rel-tag]].

=== Microformat Base ===
* [http://randomchaos.com/microformats/base/ Microformat Base]
** by [[implementations#Scott Reynen|Scott Reynen]]

=== Microformat Bookmarklet Overlay ===
* [http://leftlogic.com/info/articles/microformats_bookmarklet Microformats Bookmarklet] for Safari, Firefox and Camino, supports [[hcard|hCard]] and [[hcalendar|hCalendar]] and allows the user to import individual microformats on the fly.
** by [[implementations#Remy_Sharp|Remy Sharp]]

=== Microformat Parser for Ruby ===
* [http://blog.labnotes.org/2005/11/20/microformat-parser-for-ruby/ Microformat Parser for Ruby]
** by [[implementations#Assaf Arkin|Assaf Arkin]]

=== Nature Network Boston ===
* [http://network.nature.com/boston/ Nature Network Boston], a social networking community for scientists, supports [[reltag|rel-tag]], [[hcard|hCard]] for user profiles and [[hcalendar|hCalendar]] for marking up events across the site.
** by [[implementations#Nature Publishing Group|Nature Publishing Group]]

=== Nature Protocols ===
* [http://www.nature.com/nprot/ Nature Protocols], a forum for scientists to upload and comment on protocols, supports [[hcard|hCard]] and [[XOXO]].
** by [[implementations#Nature Publishing Group|Nature Publishing Group]]

=== Nutch ===
* [http://www.mail-archive.com/nutch-dev@lucene.apache.org/msg01295.html rel-nofollow support added]
* [http://www.mail-archive.com/nutch-commits@lucene.apache.org/msg01014.html rel-tag support checked in]

=== ODEO ===
* [http://odeo.com/ ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html noted] that they support microformats: [[rel-tag]], [[rel-enclosure]], [http://gmpg.org/xfn XFN].

=== phpMicroformats ===
* [http://enarion.net/phpmicroformats/ phpMicroformats] is a PHP class library that generates microformat entries for [[hcalendar|hCalendar]] and [[hcard|hCard]]. It is released under GPL.

=== Profiler ===
* [http://microformat.makedatamakesense.com/profiler/ Profiler] works as a proxy service adding microformat profiles to documents that appear to contain microformats.

=== RFC2629.xslt ===
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate [[hcard|hCard]] information ([http://ietf.org/rfc/rfc2629 RFC2629] in an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])

=== Salesforce ===
* [http://salesforce.com Salesforce] [http://flickr.com/photos/kingsleyj/175689109/ supports] [[hcard|hCard]]
** by [http://flickr.com/people/kingsleyj/ Kingsley Joseph]
==== Spanning Salesforce ====
* [http://spanningsalesforce.com/ Spanning Salesforce] supports [[hcalendar|hCalendar]].

=== Sivitools ===
<blockquote>
Sivitols is a Java library for microformats. Currently only the xFolk RC1 standard is implemented, but additional microformat support is planned. This library is being written and maintained for a tag sharing project undertaken by Video Vertigo.
</blockquote>
[http://blog.blip.tv/blog/microformats/ Annoucement], [http://pokkari.com/microformat/javadoc/ Docs]

=== SPRACI ===
* [http://www.spraci.com SPRACI] - nightlife/events - [[hcalendar|hCalendar]] published in events listings, aggregator can read hCalendar

=== Sunnyvale House Concerts ===
* [http://concerts.shrub.ca/shows Sunnyvale House Concerts] supports [[hcard|hCard]] and [[hcalendar|hCalendar]].

=== Technorati Contacts Feed Service ===
* [http://feeds.technorati.com/contacts/ Technorati Contacts Feed Service] is a deployment of [[implementations#X2V|X2V]] to convert [[hcard|hCards]] to vCard (.vcf) format.

=== Technorati Events Feed Service ===
* [http://feeds.technorati.com/events/ Technorati Events Feed Service] is a deployment of [[implementations#X2V|X2V]] to convert [[hcalendar|hCalendar]] events to iCalendar (.ics) format.

=== Technorati Microformats Search ===
* Technorati [http://kitchen.technorati.com/search/ Microformats Search]. Search for contacts ([[hcard|hCard]]), events ([[hcalendar|hCalendar]]), or reviews ([[hreview|hReview]]) published on blogs and other web sites.
** by [#implementations#Tantek_Çelik|Tantek Çelik]], [[implementations#Ryan_King|Ryan King]], [[implementations|Kevin_Marks|Kevin Marks]], [[implementations#Josh_Smith|Josh Smith]]

=== Technorati Search ===
* [http://technorati.com/ Technorati] [http://technorati.com/search Search] supports and handles both [[vote-links]] and [[rel-nofollow]] for indicating whether a link should have any/positive/negative weighting towards the destination.
** by [http://technorati.com/about/staff.html Technorati Staff]
=== Technorati Tags ===
* [http://technorati.com/tags/ Technorati Tags] pages aggregate blog posts tagged with the [[rel-tag]] open tagging standard, in addition to recent tagged photos and links.

=== Textpattern ===
==== Microformats Plugin ====
* [http://placenamehere.com/TXP/pnh_mf/ Textpattern Microformats Plugin] supports authoring [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [http://gmpg.org/xfn XFN], [[rel-tag]], [[rel-license]] in the [http://www.textpattern.com/ Textpattern] CMS/blogging tool
** by [http://placenamehere.com/ Chris Casciano]

=== Upcoming.org ===
* [http://upcoming.org Upcoming.org] - hCalendar support in events listings and individual events.
** by [[implementations#Andy_Baio|Andy Baio]], [[implementations#Leonard_Lin|Leonard Lin]], [[implementations#Gordon_Luk|Gordon Luk]]

=== WordPress ===
* [http://wordpress.org WordPress] supports [http://gmpg.org/xfn/ XFN] blogrolls through a very nice built-in user interface. (cf. [[xfn-implementations]])
** by [[implementations#Matt_Mullenweg|Matt Mullenweg]] and friends

==== WP Microformatted Blogroll ====
* The [http://factorycity.net/projects/wp-microformatted-blogroll/ WP Microformatted Blogroll 0.2] Wordpress plugin by [[implementations#Chris_Messina|Chris Messina]] supports [[hcard|hCard]] and [http://gmpg.org/xfn/ XFN].

==== WP Themes ====
* [http://www.plaintxt.org/themes/sandbox/ Sandbox] is a theme for Wordpress that uses [[hatom|hAtom]].
** The theme is also available to accounts on the <username>.wordpress.com hosting service.
* [http://www.whump.com/dropbox/Strangelove.zip Strangelove] is a modification of the default Wordpress theme (Kubrick) with [[hatom|hAtom]] support.
** It points to the hAtom2Atom proxy service as the link for syndication feeds.

=== X2V ===
* Brian Suda has created several XSLT files to extract microformats from HTML. From that the [http://suda.co.uk/projects/X2V/ X2V] webservice/favelet emerged. The XSLT and favelet extracts [[hcard|hCard]] and to produces .vcf (vCard) files and [[hcalendar|hCalendar]] to produce .ics (iCal) files. Also in the labs is a universal XMDP validator and a site-wide search spider that recognizes 'no-follow', 'license' and other microformats so they can be used in a more semantic way when displaying search results.
** by [[implementations#Brian_Suda|Brian Suda]]

=== Yahoo Creative Commons Search ===
* [http://search.yahoo.com/cc/ Yahoo Creative Commons Search] - supports [[rel-license]] specifically to search for Creative Commons licensed content.

=== Yahoo Local ===
* [http://local.yahoo.com Yahoo local] supports [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]].

=== Yahoo Tech ===
* [http://tech.yahoo.com Yahoo! Tech] supports [[hreview|hReview]].

=== Yahoo UK Movies ===
* [http://movies.yahoo.co.uk Yahoo! UK Movies] supports [[hreview|hReview]].
** by Mark Norman Francis

=== Yedda ===
* [http://yedda.com Yedda] supports [[hcard|hCard]] for exposing users information, [[hatom|hAtom]] for exposing data that is already exposed via feeds (like list of questions and answers) and [[rel-tag|rel-tag]] for every tag used to tag questions and users.

== Validators ==
This is an alphabetical listing of tools that have been created to validate implementations, and which formats they support.

Please add to this section if you have a validator/checker, no matter which or how many microformats you test for.

=== rel-lint ===
* [http://tools.microformatic.com/help/xhtml/rel-lint/ rel-lint] supports validation of [[rel-tag|rel-tag]] and [[xfn|XFN]]
* by [[implementations#Drew_McLellan|Drew McLellan]]

== Companies / Developers / Organizations ==

(Considering moving all of these to an [[implementors]] page of its own).

Thanks to all of the hardworking developers and innovative companies and organizations for supporting microformats.

This is an alphabetical listing of all companies, developers (by last name) and organizations who have built and shipped at least one implementation (see above for details of each implementation) that users can use.

Please help complete this list! If you have coded support for microformats and don't see your name, add it! If your company supports microformats in its applications, add it!

Note: please add direct links to specific applications, plugins, services, or tools to the list of [[implementations#Applications / Plugins / Services / Tools|Applications / Plugins / Services / Tools]] and then link to those from their implementor with a fragment identifier link, e.g. to link to the "Cork'd" wine review community:
* <nowiki>[[implementations#Cork'd|Cork'd]]</nowiki>
Similarly, for additional sites, put direct links to them in the [[implementations#Additional Sites|Additional Sites]] section and then link to them from their implementor with a fragment identifier link.

=== Apple Computer ===
[http://apple.com/ Apple Computer] has implemented microformats in:
* [[implementations#.Mac_Webmail|.Mac Webmail]]

=== Andy Hume ===
* [[implementations#Andy_Hume_Blog|Andy Hume Blog]]

=== Andy Baio ===
* [[implementations#upcoming.org|Upcoming.org]]

=== Assaf Arkin ===
* [[implementations#Microformat_Parser_for_Ruby|Microformat Parser for Ruby]]

=== Brian Del Vecchio ===
* [[implementations#upcoming_module_for_drupal| Upcoming module for Drupal]]

=== Brian Suda ===
* [[implementations#X2V|X2V]]

=== Chris Casciano ===
* [[implementations#Microformats_Plugin|Textpattern Microformats Plugin]]

=== Chris Saccheri ===
* [[implementations#LinkedIn|LinkedIn]]

=== Calvin Yu ===
* [http://blog.codeeg.com/ Calvin Yu blog: Don't Forget to Plant It!]
* [[implementations#Tails_Firefox_Extension|Tails Firefox Extension]]

=== Dan Cederholm ===
* [[implementations#Cork'd|Cork'd]]

=== David Janes ===
* [[implementations#BlogMatrix|BlogMatrix]]

=== David Long and James Myers ===
* [[implementations##ZDNet_UK|ZDNet]]

=== Drew McLellan ===
* [[implementations#Microformats_Extensions|Microformats Extensions]]
* [[implementations#hKit_Microformats_Toolkit_for_PHP5|hKit Microformats Toolkit for PHP5]]
* [[implementations#rel-lint|rel-lint Validator Tool]]

=== enarion.net ===
* [[implementations#phpMicroformats|phpMicroformats]]

=== Flock ===
* [[implementations#Flock Web Browser|Flock Web Browser]]

=== FunAdvice ===
* [[implementations#FunAdvice|FunAdvice]]

=== Google ===
* [[implementations#Google_Search|Google Search]]
* [[implementations#Google_Creative_Commons_Search|Google Creative Commons Search]]

=== Gordon Luk ===
[[implementations#upcoming.org|Upcoming.org]]

=== Josh Smith ===
* [[implementations#Technorati_Microformats_Search|Technorati Microformats Search]]

=== Kent Brewster ===
* [http://www.mindsack.com/?page_id=39 Extensible friends] -- JSON + XFN and bookmarklet

=== Kevin Marks ===
* [[implementations#Technorati_Microformats_Search|Technorati Microformats Search]]

=== Kingsley Joseph ===
[http://flickr.com/people/kingsleyj/ Kingsley Joseph]:
* [[implementations#Salesforce|Salesforce]]

=== Laughing Squid ===
* [[implementations#Laughing_Squid_Calendar|Laughing Squid Calendar]]

=== Leonard Lin ===
* [[implementations#upcoming.org|Upcoming.org]]

=== Marie-Caroline Lanfranchi ===
[http://flickr.com/people/mclanfranchi/ Marie-Caroline Lanfranchi]:
* [[implementations#faberNovel|faberNovel]]

=== Nature Publishing Group ===
* Nature Publishing Group are steadily rolling out microformats across their sites and titles. Current implementations include the following online services:
** [[implementations#Nature Network Boston|Nature Network Boston]]
** [[implementations#Nature Protocols|Nature Protocols]]
* as well the following additional site(s):
** [[implementations#Nature Home Page|Nature Home Page]]

=== Remy Sharp ===

* [[implementations#Microformats_Bookmarklet|Microformats Bookmarklet]]

=== Robert de Bruin ===
* [http://bordewolf.blogspot.com/ Robert de Bruin' s blog: Bor de Wolf]
* [[implementations#Tails_Export_Firefox_Extension|Tails Export Firefox Extension]]

=== Ryan King ===
* [[implementations#hCalendar_creator|hCalendar Creator]]
* [[implementations#hReview_creator|hReview Creator]]
* [[implementations#Technorati_Microformats_Search|Technorati Microformats Search]]

=== Scott Allan Wallick ===
* [[implementations#WP_Themes|Sandbox Wordpress Theme w/hAtom Support]]

=== Scott Reynen ===
* [[implementations#Microformat_Base|Microformat Base]]

=== SixApart ===
* [[implementations#LiveJournal|LiveJournal]]

=== Tantek Çelik ===
* [[implementations#hCard_creator|hCard Creator]]
* [[implementations#iChat_buddy_list_to_hCards|iChat Buddy List to hCard]]
* [[implementations#Technorati_Microformats_Search|Technorati Microformats Search]]

=== Technorati ===
* [[implementations#Technorati_Contacts_Feed_Service|Technorati Contacts Feed Service]]
* [[implementations#Technorati_Events_Feed_Service|Technorati Events Feed Service]]
* [[implementations#Technorati_Microformats_Search|Technorati Microformats Search]]
* [[implementations#Technorati_Search|Technorati Search]]
* [[implementations#Technorati_Tags|Technorati Tags]]

=== Yahoo ===
* [[implementations#Flickr_People|Flickr People]]
* [[implementations#Upcoming.org|Upcoming]]
* [[implementations#Yahoo_Creative_Commons_Search|Yahoo Creative Commons Search]]
* [[implementations#Yahoo_Local|Yahoo Local]]
* [[implementations#Yahoo_Tech|Yahoo Tech]]
* [[implementations#Yahoo_UK_Movies|Yahoo UK Movies]]

=== Yedda ===
* [[implementations#Yedda|Yedda]]

== Needs Fixing ==

* Re-format author names and links to display Surname Firstname - for better indexing, and complete cross-linking [[User:Phae|Frances Berriman]]

The following have been moved from the sections above due to problems, stated below:

=== Web Essentials ===
* [http://we05.com/ Web Essentials] - supports [[hcard|hCard]] and [[hcalendar|hCalendar]], e.g. in their [http://we05.com/presenters.cfm list of presenters] and [http://we05.com/program.cfm program schedule].
** John McKerrell tried to look at the site on 24th October 2006 but could not access the site, server didn't seem to be up.

== Other ==
Some notes on initial thoughts around [[implementation-guidelines|Guidelines and Strategies for Implementing Microformats]]

hcard-examples-rfc2426

2006-12-02T16:42:45Z

TKluge:

<h1>hCard examples</h1>

Example [[hcard|hCards]].

== Authors ==
* [http://tantek.com/log Tantek Çelik]
* Brian Suda

== Instructive Examples ==

=== Authors of Pages and Posts ===
[http://www.w3.org/TR/html401/struct/global.html#h-7.5.6 Per the HTML4.01 specification], authors should be using the <code><address></code> element to indicate the "contact information for a document or a major part of a document." E.g.

<pre><nowiki>
<address>
<a href="http://tantek.com/">Tantek Çelik</a>
</address>
</nowiki></pre>

By adding [[hcard|hCard]] to such existing semantic XHTML, you can explicitly indicate the name of the person, their URL, etc.:

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

This could be displayed as:

[http://tantek.com/ Tantek Çelik]

This works not only for whole pages, but also for "major part[s]" of pages, e.g. blog posts.

See the [http://microformats.org/blog/ microformats.org blog] (view the source) for a live example. The author of every blog post on the microformats.org blog is marked up as an <code><address class="vcard"></code> element like the example shown above.

=== References to People and Organizations ===

A common pattern in blog posts is to link mentions of people's names to their blogs, and/or organizations to their home pages. E.g.:

<pre><nowiki>
<cite><a href="http://meyerweb.com/">Eric Meyer</a></cite> wrote a post
(<cite><a href="http://meyerweb.com/eric/thoughts/2005/12/16/tax-relief/">Tax Relief</a></cite>)
about an unintentionally humorous letter he received from the
<a href="http://irs.gov/">Internal Revenue Service</a>.
</nowiki></pre>

By adding hCard to such markup, you can explicitly indicate both the person and the organization by name and URL:

<pre><nowiki>
<cite class="vcard"><a class="fn url" href="http://meyerweb.com/">Eric Meyer</a></cite> wrote a post
(<cite><a href="http://meyerweb.com/eric/thoughts/2005/12/16/tax-relief/">Tax Relief</a></cite>)
about an unintentionally humorous letter he received from the
<span class="vcard"><a class="fn org url" href="http://irs.gov/">Internal Revenue Service</a></span>.
</nowiki></pre>

Note the class names "fn org url" on the hyperlink surrounding the IRS. Using the same value (or element for that matter) for "fn" and "org" indicates that the hCard describes an organization rather than a person.

This could be displayed as:

''[http://meyerweb.com/ Eric Meyer]'' wrote a post (''[http://meyerweb.com/eric/thoughts/2005/12/16/tax-relief/ Tax Relief]'') about an unintentionally humorous letter
he received from the [http://irs.gov/ Internal Revenue Service].

=== hCard and XFN ===
==== References to People in Blog Posts ====

In the above example, one person (the blogger) is referring to another person (Eric Meyer). In addition to using hCard to explicitly mark up the reference as a person, the blogger can use [http://gmpg.org/xfn/ XFN] (the XHTML Friends Network) to indicate their relationship to Eric Meyer, e.g.:

<pre><nowiki>
<cite class="vcard"><a class="fn url" rel="friend colleague met" href="http://meyerweb.com/">Eric Meyer</a></cite> wrote a post
(<cite><a href="http://meyerweb.com/eric/thoughts/2005/12/16/tax-relief/">Tax Relief</a></cite>)
about an unintentionally humorous letter he received from the
<span class="vcard"><a class="fn org url" href="http://irs.gov/">Internal Revenue Service</a></span>.
</nowiki></pre>

It would be displayed the same as the previous example.

==== References to People in Blogrolls ====

Many bloggers are using XFN (often using an easy user interface like that built into [http://wordpress.org WordPress]) to explicitly indicate their relationships to the people in their blogrolls:

<pre><nowiki>
<ul>
<li><a href="http://meyerweb.com" rel="friend colleague met">Eric Meyer</a></li>
<li><a href="http://photomatt.net" rel="friend colleague met">Matt Mullenweg</a></li>
</ul>
</nowiki></pre>

By adding hCard markup to an XFN Friendly blogroll, you can explicitly indicate the name and URL of the person in addition to their relationship:

<pre><nowiki>
<ul>
<li class="vcard"><a class="fn url" href="http://meyerweb.com" rel="friend colleague met">Eric Meyer</a></li>
<li class="vcard"><a class="fn url" href="http://photomatt.net" rel="friend colleague met">Matt Mullenweg</a></li>
</ul>
</nowiki></pre>

This could be displayed as:
* [http://meyerweb.com Eric Meyer]
* [http://photomatt.net Matt Mullenweg]

For more information on XFN, see the [http://gmpg.org/xfn/ XFN home page], [http://gmpg.org/xfn/join joining XFN], and [http://gmpg.org/xfn/background background on XFN].

This technique is used in the [http://factorycity.net/projects/wp-microformatted-blogroll/ WP Microformatted Blogroll] plugin.

=== New Types of Contact Info ===

Since vCard was designed, there have been numerous other services that provide individuals with addresses or other means of contact, e.g. instant messaging, voip, etc.

Does this mean that vCard (and hence hCard) must be extended to represent these?

Thanks to the flexibility of the URL property, the answer is no, no extensions are necessary. Instead, we use the proper URL for the service which identifies the service (protocol, machine, and/or path), and place the individual's address inside that.

==== AOL Instant Messenger (AIM) ====

AOL Instant Messenger (AIM) ids can be represented using the <code>aim:</code> protocol. Many who publish their AIM ids do so with clickable URLs e.g.:

<pre><nowiki>
<a href="aim:goim?screenname=ShoppingBuddy">IM with the AIM ShoppingBuddy</a>
</nowiki></pre>

Thus for hCard, we will adopt this existing content publisher behavior, and simply capture it as another URL for the hCard:

<pre><nowiki>
<a class="url" href="aim:goim?screenname=ShoppingBuddy">IM with the AIM ShoppingBuddy</a>
</nowiki></pre>

==== Yahoo Messenger ====

Similarly, Yahoo Instant Messenger (YIM) ids can be represented using the <code>ymsgr:</code> protocol. And similarly many publish their YIM ids as clickable URLs e.g.:

<pre><nowiki>
<a href="ymsgr:sendIM?SomeYahooFriend">IM with SomeYahooFriend</a>
</nowiki></pre>

Again, for hCard, we will adopt this existing content publisher behavior, and simply capture it as another URL for the hCard:

<pre><nowiki>
<a class="url" href="ymsgr:sendIM?SomeYahooFriend">IM with SomeYahooFriend</a>
</nowiki></pre>

==== MSN Messenger ====

<strike>Unfortunately, AFAIK, there is no hacked up defacto protocol for opening an MSN IM session with an MSN userid (which themselves are just email addresses). Thus we must simply resort to marking them up as email addresses, and expect that consumers may use some heuristic, such as "hotmail.com email addresses are also MSN IM ids". -Tantek</strike>

MSN Messenger (MSNIM) ids can be represented using the <code>msnim:</code> protocol. And similarly many publish their MSNIM ids as clickable URLs e.g.:

<pre><nowiki>
<a href="msnim:chat?contact=joebob@hotmail.com">IM with joebob@hotmail.com</a>
</nowiki></pre>

For hCard, we will adopt this existing content publisher behavior, and simply capture it as another URL for the hCard:

<pre><nowiki>
<a class="url" href="msnim:chat?contact=joebob@hotmail.com">IM with joebob@hotmail.com</a>
</nowiki></pre>

Updated 14 May 2006 - [http://www.wackomenace.co.uk/ Ruben]

Ruben, I tried this, and "msnim:" is an unrecognized protocol on MacOSX.4 (this is with the latest MSN Messenger for Mac installed and running and logged int). Could you provide links to documentation about "msnim:" and links to actual pages that publish their MSNIM ids this way? I don't know of any - [http://tantek.com/ Tantek]

: Tantek, Wikipedia's [http://en.wikipedia.org/wiki/History_of_Windows_Live_Messenger History of Windows Live Messenger] states that MSN Messenger 7.5 for Windows, among other things, introduced: "the msnim protocol handler, allowing Web sites to provide links which automatically add a contact or start conversations (for example clicking on link msnim:chat?contact=login@passport.net will start chat conversation with user login@passport.net).". The Mac version is notoriously lagging behind, sadly. --''[[User:Chucker|chucker]] 11:33, 29 Jun 2006 (PDT)''

==== XMPP (Jabber) ====

[http://www.xmpp.org/ Extensible Messaging and Presence Protocol (XMPP)] ids can be represented using the <code>xmpp:</code> protocol, e.g.:

<pre><nowiki>
<a class="url" href="xmpp:username@jabberservice.com">IM with username@jammerservice.com</a>
</nowiki></pre>

The protocol allows much richer URLs, see [http://www.faqs.org/rfcs/rfc4622.html RFC4622].

There are not many current [http://wiki.jabber.org/index.php/XMPP_URIs#Jabber_Clients clients supporting the protocol].

==== Skype ====

Skype can be represented using the <code>skype:</code> protocol. It can be used to open a chat session or make a Skype call.

<pre><nowiki>
<a href="skype:echo-chinese?chat">IM with the Skype echo service (Chinese) </a>
</nowiki></pre>

<pre><nowiki>
<a href="skype:echo-chinese?call">Skype call to Skype echo service (Chinese) </a>
</nowiki></pre>

Thus for hCard, we could adopt this existing content publisher behavior, and simply capture it as another URL for the hCard:

<pre><nowiki>
<a class="url" href="skype:echo-chinese?chat">IM with the Skype echo service (Chinese)</a>
</nowiki></pre>

<pre><nowiki>
<a class="url" href="skype:echo-chinese?call">Skype call to Skype echo service (Chinese)</a>
</nowiki></pre>

==== Site profiles ====
Bloggers often indicate their identity on content hosting services using the URL to their home page, feed or profile on those services. By labeling them as URL properties, these additional facets of identity can be publish in an hCard as well.

* [http://del.icio.us delicious]:
** <code><a class="url" href="http://del.icio.us/rbach">Robert Bachmann's links</a></code>
* [http://flickr.com Flickr]:
** <code><a class="url" href="http://flickr.com/photos/tantek/">See my photos</a></code>
** <code><a class="url" href="http://flickr.com/people/tantek/">Flickr profile</a></code>
* [http://technorati.com/ Technorati]:
** <code><a class="url" href="http://technorati.com/profile/tantek/">Technorati profile</a></code>
* Add more here...
** ....

=== Organizations and Departments ===

Departments are marked up using the "organization-unit" class name inside the "org" element, with the "organization-name" specifically marked up to distinguish it from the department:

<pre><nowiki>
<div class="vcard">
<div class="org fn">
<div class="organization-name">Sprinkler Fitters U.A. Local 483</div>
<div class="organization-unit">Apprenticeship Training Center</div>
</div>
</div>
</nowiki></pre>

The department may also be part of the address, in which case, you may want to explicitly mark it up as the "extended-address" in addition to the "organization-unit".

<pre><nowiki>
<div class="vcard">
<div class="adr">
<div class="org fn">
<div class="organization-name">Sprinkler Fitters U.A. Local 483</div>
<div class="organization-unit extended-address">Apprenticeship Training Center</div>
</div>
<div class="street-address">2531 Barrington Court</div>
<span class="locality">Hayward</span>,
<abbr title="California" class="region">CA</abbr>
<span class="postal-code">94545</span>
</div>
</div>
</nowiki></pre>

Note that by nesting the org inside the address we avoided having to duplicate the department name.

== RFC 2426 examples in hCard ==

These are 1:1 hCard examples for each example in [http://www.ietf.org/rfc/rfc2426.txt RFC 2426].

Mark Pilgrim has made these hCard examples available as separate files:
* http://diveintomark.org/projects/greasemonkey/hcard/tests/

=== 2.4.2 VCARD ===

<pre><nowiki>
AGENT:BEGIN:VCARD\nFN:Joe Friday\nTEL:+1-919-555-7878\n
TITLE:Area Administrator\, Assistant\n EMAIL\;TYPE=INTERNET:\n
jfriday@host.com\nEND:VCARD\n
</nowiki></pre>

This vCard fragment has one property whose value is another vCard, and could be represented as an hCard fragment with an embedded hCard, literally (with the unnecessary type=internet default omitted, and the implied n optimization):

<pre><nowiki>
<div class="agent vcard">
<a class="email fn" href="mailto:jfriday@host.com">Joe Friday</a>
<div class="tel">+1-919-555-7878</div>
<div class="title">Area Administrator, Assistant</div>
</div>
</nowiki></pre>

this hCard could be displayed as:

[mailto:jfriday@host.com Joe Friday]<br />
+1-919-555-7878<br />
Area Administrator, Assistant

=== 3.1.1 FN Type Definition ===

<pre><nowiki>
FN:Mr. John Q. Public\, Esq.
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="fn">Mr. John Q. Public, Esq.</span>
</nowiki></pre>

this hCard fragment could be displayed as:

Mr. John Q. Public, Esq.

=== 3.1.2 N Type Definition ===

==== Example 1 ====

<pre><nowiki>
N:Public;John;Quinlan;Mr.;Esq.
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="n">
<span class="honorific-prefix">Mr.</span>
<span class="given-name">John</span>
<span class="additional-name">Quinlan</span>
<span class="family-name">Public</span>,
<span class="honorific-suffix">Esq.</span>
</span>
</nowiki></pre>

this hCard fragment could be displayed as:

Mr. John Quinlan Public, Esq.

==== Example 2 ====

<pre><nowiki>
N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P.
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="n">
<span class="honorific-prefix">Dr.</span>
<span class="given-name">John</span>
<span class="additional-name">Philip</span>
<span class="additional-name">Paul</span>
<span class="family-name">Stevenson</span>,
<span class="honorific-suffix">Jr.</span>,
<span class="honorific-suffix">M.D.</span>,
<span class="honorific-suffix">A.C.P.</span>
</span>
</nowiki></pre>

this hCard fragment would be displayed as:

Dr. John Philip Paul Stevenson, Jr., M.D., A.C.P.

=== 3.1.3 NICKNAME Type Definition ===

==== Example 1 ====

<pre><nowiki>
NICKNAME:Robbie
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="nickname">Robbie</span>
</nowiki></pre>

this hCard fragment could be displayed as:

Robbie

==== Example 2 ====

<pre><nowiki>
NICKNAME:Jim,Jimmie
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="nickname">Jim</span>,
<span class="nickname">Jimmie</span>
</nowiki></pre>

this hCard fragment would be displayed as:

Jim, Jimmie

=== 3.1.4 PHOTO Type Definition ===

==== Example 1 ====
<pre><nowiki>
PHOTO;VALUE=uri:http://www.abc.com/pub/photos/jqpublic.gif
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<img class="photo" src="http://www.abc.com/pub/photos/jqpublic.gif" alt="" />
</nowiki></pre>

==== Example 2 ====
<pre><nowiki>
PHOTO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...remainder of "B" encoded binary data...>
</nowiki></pre>

this vCard fragment as an hCard fragment (line breaks inserted into src value for readability):

<pre><nowiki>
<img class="photo" src="data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
...remainder of B encoded binary data..." alt="" />
</nowiki></pre>

=== 3.1.5 BDAY Type Definition ===

==== Example 1 ====

<pre><nowiki>
BDAY:1996-04-15
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<abbr class="bday" title="1996-04-15">April 15, 1996</abbr>
</nowiki></pre>

this hCard fragment could be displayed as:

<abbr class="bday" title="1996-04-15">April 15, 1996</abbr>

==== Example 2 ====

<pre><nowiki>
BDAY:1953-10-15T23:10:00Z
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<abbr class="bday" title="1953-10-15T23:10:00Z">Oct 15, 1953</abbr>
</nowiki></pre>

this hCard fragment could be displayed as:

<abbr class="bday" title="1953-10-15T23:10:00Z">Oct 15, 1953</abbr>

==== Example 3 ====

<pre><nowiki>
BDAY:1987-09-27T08:30:00-06:00
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<abbr class="bday" title="1987-09-27T08:30:00-06:00">Sept 9, 1987</abbr>
</nowiki></pre>

this hCard fragment could be displayed as:

<abbr class="bday" title="1987-09-27T08:30:00-06:00">Sept 9, 1987</abbr>

=== 3.2.1 ADR Type Definition ===

<pre><nowiki>
ADR;TYPE=dom,home,postal,parcel:;;123 Main
Street;Any Town;CA;91921-1234
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<div class="adr">
<abbr class="type" title="dom">US</abbr>
<span class="type">home</span> address, for
<abbr class="type" title="postal">mail</abbr> and
<abbr class="type" title="parcel">shipments</abbr>:
<div class="street-address">123 Main Street</div>
<span class="locality">Any Town</span>, <span class="region">CA</span>,
<span class="postal-code">91921-1234</span>
</div>
</nowiki></pre>

this hCard fragment could be displayed as:

<div class="adr">
<abbr class="type" title="dom">US</abbr>
<span class="type">home</span> address, for
<abbr class="type" title="postal">mail</abbr> and
<abbr class="type" title="parcel">shipments</abbr>:
<div class="street-address">123 Main Street</div>
<span class="locality">Any Town</span>, <span class="region">CA</span>,
<span class="postal-code">91921-1234</span>
</div>

=== 3.2.2 LABEL Type Definition ===

<pre><nowiki>
LABEL;TYPE=dom,home,postal,parcel:Mr.John Q. Public\, Esq.\n
Mail Drop: TNE QB\n123 Main Street\nAny Town\, CA 91921-1234
\nU.S.A.
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
Please use the following address label for
<div class="label">
<abbr class="type" title="dom">local delivery</abbr>
<abbr class="type" title="home">to my home</abbr>
<abbr class="type" title="postal">of mail</abbr>
<abbr class="type" title="parcel">and packages:</abbr>
<pre>
Mr.John Q. Public, Esq.
Mail Drop: TNE QB
123 Main Street
Any Town, CA 91921-1234
U.S.A.
</pre>
</div>
</nowiki></pre>

'''Note:''' the above hCard fragment uses a <pre> tag inside a property value to capture/represent explicit carriage returns ("\n" characters) from the vCard fragment.

this hCard fragment could be displayed as:

Please use the following address label for
<abbr class="type" title="dom">local delivery</abbr>
<abbr class="type" title="home">to my home</abbr>
<abbr class="type" title="postal">of mail</abbr>
<abbr class="type" title="parcel">and packages:</abbr>
<pre>
Mr.John Q. Public, Esq.
Mail Drop: TNE QB
123 Main Street
Any Town, CA 91921-1234
U.S.A.
</pre>

=== 3.3.1 TEL Type Definition ===

<pre><nowiki>
TEL;TYPE=work,voice,pref,msg:+1-213-555-1234
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="tel">
<abbr class="type" title="pref">my</abbr>
<span class="type">work</span>
<abbr class="type" title="voice">phone</abbr>, with
<abbr class="type" title="msg">voicemail</abbr>:
<span class="value">+1-213-555-1234</span>
</span>
</nowiki></pre>

this hCard fragment could be displayed as:

my work phone, with voicemail: +1-213-555-1234

=== 3.3.2 EMAIL Type Definition ===

==== Example 1 ====

<pre><nowiki>
EMAIL;TYPE=internet:jqpublic@xyz.dom1.com
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<a class="email" href="mailto:jqpublic@xyz.dom1.com">email jqpublic</a>
</nowiki></pre>

this hCard fragment could be displayed as:

[mailto:jqpublic@xyz.dom1.com email jqpublic]

==== Example 2 ====

<pre><nowiki>
EMAIL;TYPE=internet:jdoe@isp.net
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<a class="email" href="mailto:jdoe@isp.net">email jdoe</a>
</nowiki></pre>

this hCard fragment could be displayed as:

[mailto:jdoe@isp.net email jdoe]

==== Example 3 ====

<pre><nowiki>
EMAIL;TYPE=internet,pref:jane_doe@abc.com
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<a class="email" href="mailto:jane_doe@abc.com">
<abbr class="type" title="pref">preferred</abbr>
email for jane_doe
</a>
</nowiki></pre>

this hCard fragment could be displayed as:

[mailto:jane_doe@abc.com preferred email for jane_doe]

=== 3.3.3 MAILER Type Definition ===

<pre><nowiki>
MAILER:PigeonMail 2.1
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
Jane Doe uses <span class="mailer">PigeonMail 2.1</span> for email.
</nowiki></pre>

this hCard fragment could be displayed as:

Jane Doe uses <span class="mailer">PigeonMail 2.1</span> for email.

=== 3.4.1 TZ Type Definition ===

==== Example 1 ====

<pre><nowiki>
TZ:-05:00
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="tz">-05:00</span>
</nowiki></pre>

this hCard fragment could be displayed as:

-05:00
==== Example 2 ====

<pre><nowiki>
TZ;VALUE=text:-05:00; EST; Raleigh/North America
;This example has a single value, not a structure text value.
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<abbr class="tz"
title="-05:00; EST; Raleigh/North America;This example has a single value, not a structure text value.">
EST
</abbr>
</nowiki></pre>

this hCard fragment could be displayed as:

<abbr class="tz" title="-05:00; EST; Raleigh/North America;This example has a single value, not a structure text value.">EST</abbr>

=== 3.4.2 GEO Type Definition ===

<pre><nowiki>
GEO:37.386013;-122.082932
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="geo">
<span class="latitude">37.386013</span>,
<span class="longitude">-122.082932</span>
</span>
</nowiki></pre>

this hCard fragment could be displayed as:

37.386013, -122.082932

=== 3.5.1 TITLE Type Definition ===

<pre><nowiki>
TITLE:Director\, Research and Development
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="title">Director, Research and Development</span>
</nowiki></pre>

this hCard fragment could be displayed as:

Director, Research and Development

=== 3.5.2 ROLE Type Definition ===

<pre><nowiki>
ROLE:Programmer
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="role">Programmer</span>
</nowiki></pre>

this hCard fragment could be displayed as:

Programmer

=== 3.5.3 LOGO Type Definition ===

==== Example 1 ====

<pre><nowiki>
LOGO;VALUE=uri:http://www.abc.com/pub/logos/abccorp.jpg
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
<img class="logo" src="http://www.abc.com/pub/logos/abccorp.jpg" alt="my logo" />
</nowiki></pre>

this hCard fragment could be displayed as (note: I used a real URL for the image):

http://microformats.org/img/mf-lg-ora.gif

==== Example 2 ====

<pre><nowiki>
LOGO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of "B" encoded binary data...>
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
<img class="logo" src="data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
...remainder of B encoded binary data..." alt="" />
</nowiki></pre>

no display equivalent given, since data: URL from original example is incomplete.

=== 3.5.4 AGENT Type Definition ===

==== Example 1 ====

<pre><nowiki>
AGENT;VALUE=uri:
CID:JQPUBLIC.part3.960129T083020.xyzMail@host3.com
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
<a class="agent" href="CID:JQPUBLIC.part3.960129T083020.xyzMail@host3.com">JQPUBLIC</a>
</nowiki></pre>

this hCard fragment could be displayed as:

JQPUBLIC

==== Example 2 ====

<pre><nowiki>
AGENT:BEGIN:VCARD\nFN:Susan Thomas\nTEL:+1-919-555-
1234\nEMAIL\;INTERNET:sthomas@host.com\nEND:VCARD\n
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
<span class="agent vcard">
<a class="email fn n" href="mailto:sthomas@host.com">Susan Thomas</a>,
<span class="tel">+1-919-555-1234</span>
</span>
</nowiki></pre>

this hCard fragment could be displayed as:

[mailto:sthomas@host.com Susan Thomas], +1-919-555-1234

Note: the vCard in the AGENT property vCard fragment is actually invalid since it lacks an "N" property. However, the hCard version *is* valid, since I added the "n" class name to the example.

=== 3.5.5 ORG Type Definition ===

<pre><nowiki>
ORG:ABC\, Inc.;North American Division;Marketing
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="org">
<span class="organization-name">ABC, Inc.</span>,
<span class="organization-unit">North American Division</span>,
<span class="organization-unit">Marketing</span>,
</span>
</nowiki></pre>

this hCard fragment could be displayed as:

ABC, Inc., North American Division, Marketing

=== 3.6.1 CATEGORIES Type Definition ===

==== Example 1 ====

<pre><nowiki>
CATEGORIES:TRAVEL AGENT
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="category">TRAVEL AGENT</span>
</nowiki></pre>

this hCard fragment could be displayed as:

TRAVEL AGENT

==== Example 2 ====

<pre><nowiki>
CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="category">INTERNET</span>,
<span class="category">IETF</span>,
<span class="category">INDUSTRY</span>,
<span class="category">INFORMATION TECHNOLOGY</span>
</nowiki></pre>

this hCard fragment would be displayed as:

INTERNET, IETF, INDUSTRY, INFORMATION TECHNOLOGY

=== 3.6.2 NOTE Type Definition ===

<pre><nowiki>
NOTE:This fax number is operational 0800 to 1715
EST\, Mon-Fri.
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<p class="note">This fax number is operational 0800 to 1715 EST, Mon-Fri.</p>
</nowiki></pre>

this hCard fragment could be displayed as:

This fax number is operational 0800 to 1715 EST, Mon-Fri.

=== 3.6.3 PRODID Type Definition ===

<pre><nowiki>
PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN
</nowiki></pre>

Note, this vCard property actually doesn't make sense as a hCard property, since it really should be filled in by whatever code transforms the hCard into a vCard, e.g. Brian Suda's X2V.

=== 3.6.4 REV Type Definition ===

==== Example 1 ====

<pre><nowiki>
REV:1995-10-31T22:27:10Z
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<abbr class="rev" title="1995-10-31T22:27:10Z">Updated: 10/31 10:27p</abbr>
</nowiki></pre>

this hCard fragment could be displayed as:

<abbr class="rev" title="1995-10-31T22:27:10Z">Updated: 10/31 10:27p</abbr>

==== Example 2 ====

<pre><nowiki>
REV:1997-11-15
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<abbr class="rev" title="1997-11-15">Updated: November 15</abbr>
</nowiki></pre>

this hCard fragment could be displayed as:

<abbr class="rev" title="1997-11-15">Updated: November 15</abbr>

=== 3.6.5 SORT-STRING Type Definition ===

==== Example 1 ====

<pre><nowiki>
FN:Rene van der Harten
N:van der Harten;Rene;J.;Sir;R.D.O.N.
SORT-STRING:Harten
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="n"
<span class="honorific-prefix">Sir</span>
<span class="fn">
<span class="given-name">Rene</span>
<span class="family-name">
van der <span class="sort-string">Harten</span>
</span>
</span>
(<span class="additional-name">J.</span>),
<span class="honorific-suffix">R.D.O.N.</span>
</span>
</nowiki></pre>

Note: The string "Harten" was NOT repeated in the hCard, even though it WAS repeated in the vCard (3 times! In N, FN, and SORT-STRING). The "SORT-STRING" property provides another good demonstration of how hCard enables better adherence to the [http://microformats.org/wiki/hcard-example1-steps#hCard_example_iteration_1:_DRY DRY principle] than vCard.

this hCard fragment could be displayed as:

Sir Rene van der Harten (J.), R.D.O.N.

==== Example 2 ====

<pre><nowiki>
FN:Robert Pau Shou Chang
N:Pau;Shou Chang;Robert
SORT-STRING:Pau
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="fn n">
<span class="additional-name">Robert</span>
<span class="family-name sort-string">Pau</span>
<span class="given-name">Shou Chang</span>
</span>
</nowiki></pre>

Note: Not only was the string "Pau" was NOT repeated in the hCard (better [http://microformats.org/wiki/hcard-example1-steps#hCard_example_iteration_1:_DRY DRY principle] adherence again), even though it WAS repeated in the vCard, but in this case since the "family-name" and "sort-string" are the same, we were able to use [http://microformats.org/wiki/hcard-example1-steps#hCard_example_iteration_2:_element_conservation element conservation] and use only one element for both properties.

this hCard fragment could be displayed as:

Robert Pau Shou Chang

==== Example 3 ====

<pre><nowiki>
FN:Osamu Koura
N:Koura;Osamu
SORT-STRING:Koura
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="fn">
Osamu <span class="sort-string">Koura</span>
</span>
</nowiki></pre>

Note: This example, in addition to illustrating better support for the [http://microformats.org/wiki/hcard-example1-steps#hCard_example_iteration_1:_DRY DRY principle], also makes use of the [http://microformats.org/wiki/hcard#Implied_.22N.22_Optimization Implied "N" Optimization].

this hCard fragment could be displayed as:

Osamu Koura

==== Example 4 ====

<pre><nowiki>
FN:Oscar del Pozo
N:del Pozo Triscon;Oscar
SORT-STRING:Pozo
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="n">
<span class="fn">
<span class="given-name">Oscar</span>
del <span class="sort-string">Pozo</span>
</span>
<span class="family-name" style="display:none">
del Pozo Triscon
</span>
</span>
</nowiki></pre>

Note: This example unfortunately could not completely adhere to the DRY principle due to the "FN" using a *substring* of the family-name, and in addition thus had to hide the extra "family-name" string value using CSS display:none, which in general should be avoided. Suggestion welcome for improvements on this hCard fragement.

this hCard fragment could be displayed as:

Oscar del Pozo

==== Example 5 ====

<pre><nowiki>
FN:Christine d'Aboville
N:d'Aboville;Christine
SORT-STRING:Aboville
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="fn">
Christine d'<span class="sort-string">Aboville</span>
</span>
</nowiki></pre>

Note: This example re-demonstrates the same hCard advantages/efficiencies demonstrated in [http://microformats.org/wiki/hcard-examples#Example_3_3 example 3] above.

this hCard fragment could be displayed as:

Christine d'Aboville

=== 3.6.6 SOUND Type Definition ===

==== Example 1 ====

<pre><nowiki>
SOUND;TYPE=BASIC;VALUE=uri:CID:JOHNQPUBLIC.part8.
19960229T080000.xyzMail@host1.com
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
<object class="sound" type="audio/basic"
data="CID:JOHNQPUBLIC.part8.19960229T080000.xyzMail@host1.com">
pronounciation of "JOHN Q PUBLIC"
</object>
</nowiki></pre>

this hCard fragment would probably be displayed as

pronounciation of "JOHN Q PUBLIC"

unless your browser supports the MIME type "audio/basic" (defined in [http://www.rfc-editor.org/rfc/rfc2046.txt RFC2046 section 4.3]) and has some way of retrieving "CID:" urls.

==== Example 2 ====
<pre><nowiki>
SOUND;TYPE=BASIC;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of "B" encoded binary data...>
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
<object class="sound"
data="data:audio/basic;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
...the remainder of "B" encoded binary data...">
pronounciation
</object>
</nowiki></pre>

no display equivalent given, since data: URL from original example is incomplete.

=== 3.6.7 UID Type Definition ===

<pre><nowiki>
UID:19950401-080045-40000F192713-0052
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
Unique id:
<span class="uid">19950401-080045-40000F192713-0052</span>
</nowiki></pre>

this hCard fragment could be displayed as

Unique id:19950401-080045-40000F192713-0052

Note: in practice I don't think I've seen globally unique IDs for "contact info" records published on the web, but perhaps I am not considering enough examples.

=== 3.6.8 URL Type Definition ===

<pre><nowiki>
URL:http://www.swbyps.restaurant.french/~chezchic.html
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
<a class="url" href="http://www.swbyps.restaurant.french/~chezchic.html">Chez Chic</a>
</nowiki></pre>

this hCard fragment could be displayed as

[http://www.swbyps.restaurant.french/~chezchic.html Chez Chic]

=== 3.7.1 CLASS Type Definition ===

==== Example 1 ====

<pre><nowiki>
CLASS:PUBLIC
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
<span class="class">PUBLIC</span>
</nowiki></pre>

this hCard fragment could be displayed as

PUBLIC

==== Example 2 ====

<pre><nowiki>
CLASS:PRIVATE
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
<span class="class">PRIVATE</span>
</nowiki></pre>

this hCard fragment could be displayed as

PRIVATE

==== Example 3 ====

<pre><nowiki>
CLASS:CONFIDENTIAL
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
<span class="class">CONFIDENTIAL</span>
</nowiki></pre>

this hCard fragment could be displayed as

CONFIDENTIAL

=== 3.7.2 KEY Type Definition ===

<pre><nowiki>
KEY;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQA
wdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENbW11bmljYX
Rpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
ZW1zMRwwGgYDVQQDExNyb290Y2EubmV0c2NhcGUuY29tMB4XDTk3MDYwNj
E5NDc1OVoXDTk3MTIwMzE5NDc1OVowgYkxCzAJBgNVBAYTAlVTMSYwJAYD
VQQKEx1OZXRzY2FwZSBDb21tdW5pY2F0aW9ucyBDb3JwLjEYMBYGA1UEAx
MPVGltb3RoeSBBIEhvd2VzMSEwHwYJKoZIhvcNAQkBFhJob3dlc0BuZXRz
Y2FwZS5jb20xFTATBgoJkiaJk/IsZAEBEwVob3dlczBcMA0GCSqGSIb3DQ
EBAQUAA0sAMEgCQQC0JZf6wkg8pLMXHHCUvMfL5H6zjSk4vTTXZpYyrdN2
dXcoX49LKiOmgeJSzoiFKHtLOIboyludF90CgqcxtwKnAgMBAAGjNjA0MB
EGCWCGSAGG+EIBAQQEAwIAoDAfBgNVHSMEGDAWgBT84FToB/GV3jr3mcau
+hUMbsQukjANBgkqhkiG9w0BAQQFAAOBgQBexv7o7mi3PLXadkmNP9LcIP
mx93HGp0Kgyx1jIVMyNgsemeAwBM+MSlhMfcpbTrONwNjZYW8vJDSoi//y
rZlVt9bJbs7MNYZVsyF1unsqaln4/vy6Uawfg8VUMk1U7jt8LYpo4YULU7
UZHPYVUaSgVttImOHZIKi4hlPXBOhcUQ==
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
<object class="key" type="application/octet-stream"
data="data:application/octet-stream;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQA
wdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENbW11bmljYX
Rpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
ZW1zMRwwGgYDVQQDExNyb290Y2EubmV0c2NhcGUuY29tMB4XDTk3MDYwNj
E5NDc1OVoXDTk3MTIwMzE5NDc1OVowgYkxCzAJBgNVBAYTAlVTMSYwJAYD
VQQKEx1OZXRzY2FwZSBDb21tdW5pY2F0aW9ucyBDb3JwLjEYMBYGA1UEAx
MPVGltb3RoeSBBIEhvd2VzMSEwHwYJKoZIhvcNAQkBFhJob3dlc0BuZXRz
Y2FwZS5jb20xFTATBgoJkiaJk/IsZAEBEwVob3dlczBcMA0GCSqGSIb3DQ
EBAQUAA0sAMEgCQQC0JZf6wkg8pLMXHHCUvMfL5H6zjSk4vTTXZpYyrdN2
dXcoX49LKiOmgeJSzoiFKHtLOIboyludF90CgqcxtwKnAgMBAAGjNjA0MB
EGCWCGSAGG+EIBAQQEAwIAoDAfBgNVHSMEGDAWgBT84FToB/GV3jr3mcau
+hUMbsQukjANBgkqhkiG9w0BAQQFAAOBgQBexv7o7mi3PLXadkmNP9LcIP
mx93HGp0Kgyx1jIVMyNgsemeAwBM+MSlhMfcpbTrONwNjZYW8vJDSoi//y
rZlVt9bJbs7MNYZVsyF1unsqaln4/vy6Uawfg8VUMk1U7jt8LYpo4YULU7
UZHPYVUaSgVttImOHZIKi4hlPXBOhcUQ==">
Key
</object>

</nowiki></pre>

this hCard fragment could be displayed as

Key

Note: Because of the lack of a TYPE value in the RFC2426 example, I substituted application/octet-stream. Clearly for it to be of some use, the type specified must be some sort of key or certificate mime type.

=== 7. Authors' Addresses ===

<pre><nowiki>
BEGIN:vCard
VERSION:3.0
FN:Frank Dawson
ORG:Lotus Development Corporation
ADR;TYPE=WORK,POSTAL,PARCEL:;;6544 Battleford Drive
;Raleigh;NC;27613-3502;U.S.A.
TEL;TYPE=VOICE,MSG,WORK:+1-919-676-9515
TEL;TYPE=FAX,WORK:+1-919-676-9564
EMAIL;TYPE=INTERNET,PREF:Frank_Dawson@Lotus.com
EMAIL;TYPE=INTERNET:fdawson@earthlink.net
URL:http://home.earthlink.net/~fdawson
END:vCard

BEGIN:vCard
VERSION:3.0
FN:Tim Howes
ORG:Netscape Communications Corp.
ADR;TYPE=WORK:;;501 E. Middlefield Rd.;Mountain View;
CA; 94043;U.S.A.
TEL;TYPE=VOICE,MSG,WORK:+1-415-937-3419
TEL;TYPE=FAX,WORK:+1-415-528-4164
EMAIL;TYPE=INTERNET:howes@netscape.com
END:vCard
</nowiki></pre>

Note that both of these vCards are invalid since they lack the REQUIRED "N" property which is quite ironic, since these are the vCards of the authors themselves.

Nonetheless, these vCards can be represented by the following hCards:

<pre><nowiki>
<div class="vcard">
<a class="url fn" href="http://home.earthlink.net/~fdawson">Frank Dawson</a>
<div class="org">Lotus Development Corporation</div>
<div class="adr">
<span class="type">work</span> address
(<abbr class="type" title="postal">mail</abbr> and
<abbr class="type" title="parcel">packages</abbr>):
<div class="street-address">6544 Battleford Drive</div>
<span class="locality">Raleigh</span>
<span class="region">NC</span>
<span class="postal-code">27613-3502</span>
<div class="country-name">U.S.A.</div>
</div>
<div class="tel">
<span class="value">+1-919-676-9515</span>
(<abbr class="type" title="WORK">w</abbr>,
<abbr class="type" title="VOICE">v</abbr><abbr class="type" title="MSG">m</abbr>)
</div>
<div class="tel">
<span class="value">+1-919-676-9564</span>
(<abbr class="type" title="WORK">w</abbr><abbr class="type" title="FAX">f</abbr>)
</div>
<a class="email" href="mailto:Frank_Dawson@Lotus.com">
<span class="type">pref<span>erred</span> email</span>
</a>,
<a class="email" href="mailto:fdawson@earthlink.net">
alternate email
</a>
</div>
<div class="vcard">
<a class="email fn" href="mailto:howes@netscape.com">Tim Howes</a>
<div class="org">Netscape Communications Corp.</div>
<div class="adr">
<span class="type">work</span> address:
<div class="street-address">501 E. Middlefield Rd.</div>
<span class="locality">Mountain View</span>,
<span class="region">CA</span>
<span class="postal-code">94043</span>
<div class="country-name">U.S.A.</div>
</div>
<div class="tel">
<span class="value">+1-415-937-3419</span>
(<abbr class="type" title="WORK">w</abbr>,
<abbr class="type" title="VOICE">v</abbr><abbr class="type" title="MSG">m</abbr>)
</div>
<div class="tel">
<span class="value">+1-415-528-4164</span>
(<abbr class="type" title="WORK">w</abbr><abbr class="type" title="FAX">f</abbr>)
</div>
</div>
</nowiki></pre>

this hCards could be displayed as

<div class="vcard">
[http://home.earthlink.net/~fdawson Frank Dawson]
<div class="org">Lotus Development Corporation</div>
<div class="adr">
<span class="type">work</span> address
(<abbr class="type" title="postal">mail</abbr> and
<abbr class="type" title="parcel">packages</abbr>):
<div class="street-address">6544 Battleford Drive</div>
<span class="locality">Raleigh</span>
<span class="region">NC</span>
<span class="postal-code">27613-3502</span>
<div class="country-name">U.S.A.</div>
</div>
<div class="tel">
<span class="value">+1-919-676-9515</span>
(<abbr class="type" title="WORK">w</abbr>,
<abbr class="type" title="VOICE">v</abbr><abbr class="type" title="MSG">m</abbr>)
</div>
<div class="tel">
<span class="value">+1-919-676-9564</span>
(<abbr class="type" title="WORK">w</abbr><abbr class="type" title="FAX">f</abbr>)
</div>
[mailto:Frank_Dawson@Lotus.com preferred email],
[mailto:fdawson@earthlink.net alternate email]
</div>

<div class="vcard">
[mailto:howes@netscape.com Tim Howes]
<div class="org">Netscape Communications Corp.</div>
<div class="adr">
<span class="type">work</span> address:
<div class="street-address">501 E. Middlefield Rd.</div>
<span class="locality">Mountain View</span>,
<span class="region">CA</span>
<span class="postal-code">94043</span>
<div class="country-name">U.S.A.</div>
</div>
<div class="tel">
<span class="value">+1-415-937-3419</span>
(<abbr class="type" title="WORK">w</abbr>,
<abbr class="type" title="VOICE">v</abbr><abbr class="type" title="MSG">m</abbr>)
</div>
<div class="tel">
<span class="value">+1-415-528-4164</span>
(<abbr class="type" title="WORK">w</abbr><abbr class="type" title="FAX">f</abbr>)
</div>
</div>

== Test Cases ==

These are [[hcard|hCard]] examples which have been found to be particularly useful in finding bugs in hCard parsers (e.g. X2V).

=== Problem with BDAY Information ===

this example:

<pre>

<div class="bday">
<dt>Birthday</dt>
<dd>
<abbr class="value" title="1985-10-27T00:00:00Z">October 27, 1985</abbr>
</dd>
</div>
</pre>

ought to produce "BDAY:1985-10-27T00:00:00Z" but it produces "BDAY:Birthday October 27\, 1985". interesting is that the apple addressbook is still willing to accept it in this way.

=== case-INSENSITIVITY of type values ===

* "home" vs. "Home"

this example works with X2V:

<pre>
<div class="tel">
<dt>Phone (<span class="type">home</span>)</dt>
<dd><span class="value">+438123418</span></dd>
</div>
</pre>

this does not, but should. but instead it becomes just TEL without a type in the vcard

<pre>
<div class="tel">
<dt>Phone (<span class="type">Home</span>)</dt>
<dd><span class="value">+438123418</span></dd>
</div>
</pre>

=== GEO parsing ===
The following hCard:

<pre><nowiki>
<div class="vcard">
<span class="n">
<a class="url" href="http://t37.net">
<span class="given-name">Fréderic</span>
<span class="family-name">de Villamil</span>
</a>
</span>
<span class="nickname">neuro</span>
<a class="email" href="mailto:neuroNOSPAM@t37.net">
<span class="type">pref<span>erred</span> email</span>
</a>
<span class="org">Omatis</span>
<span class="adr">
<abbr class="type" title="dom">France</abbr>
<span class="type">home</span> address
<abbr class="type" title="postal">mail</abbr> and
<abbr class="type" title="parcel">shipments</abbr>:
<span class="street-address">12 rue Danton</span>
<span class="locality">Le Kremlin-Bicetre</span>
<span class="postal-code">94270</span>
<span class="country-name">France</span>
</span>
<span class="geo">
<abbr class="latitude" title="48.816667">N 48° 81.6667</abbr>
<abbr class="longitude" title="2.366667">E 2° 36.6667</abbr>
</span>
</div>
</nowiki>
</pre>

Should be translated into the following vCard:

<pre><nowiki>
BEGIN:VCARD
VERSION:3.0
URL:http://t37.net
ORG:Omatis;;
NICKNAME:neuro
N:de Villamil;Frederic;;Mr.;
EMAIL;TYPE=INTERNET,PREF:neuroNOSPAM@t37.net
ADR;TYPE=HOME:;;12 rue danton;le Kremlin-Bicetre;;94270;France
GEO:48.816667;2.366667
END:VCARD
</nowiki></pre>

X2V currently (2005-12-18) fails to parse/export the GEO property at all.

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