hcard-examples-rfc2426

(Difference between revisions)

Jump to: navigation, search
(7. Authors' Addresses: fix invalid hCards)
Current revision (04:58, 7 April 2013) (view source)
m (Reverted edits by ABIDEEN10 (Talk) to last version by Tantek)
 
(7 intermediate revisions not shown.)
Line 1: Line 1:
-
<h1>hCard examples</h1>
+
:'''This is a sub-page of [[hcard-examples]]'''
-
{{TOC-right}}
+
-
 
+
-
Example [[hcard|hCards]].
+
-
 
+
-
== Authors ==
+
-
* [http://tantek.com/ 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>&lt;address&gt;</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>&lt;address class="vcard"&gt;</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>
+
-
 
+
-
Which could be displayed as:
+
-
* [http://meyerweb.com Eric Meyer]
+
-
* [http://photomatt.net Matt Mullenweg]
+
-
 
+
-
This is referred to as [[hcard-xfn-supporting-friends-lists]], and is a key building block of [[social-network-portability]].
+
-
 
+
-
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].
+
-
 
+
-
The technique is used in the [http://factorycity.net/projects/wp-microformatted-blogroll/ WP Microformatted Blogroll] plugin for WordPress.
+
-
 
+
-
=== 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 ====
+
-
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>
+
-
 
+
-
See related [[hcard-examples-issues#MSN_Messenger|issue(s)]].
+
-
 
+
-
==== 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>
+
-
 
+
-
==== ICQ ====
+
-
ICQ does not have a URL scheme.  Rather ICQ links on the web use HTTP hyperlinks to download a resource of content-type <code>application/x-icq</code> which then the operating system opens with the user's ICQ client.
+
-
 
+
-
Thus we can markup those HTTP hyperlinks with the content-type set explicitly to communicate the ICQ semantic:
+
-
 
+
-
<pre><nowiki>
+
-
<a class="url"
+
-
  type="application/x-icq"
+
-
  href="http://www.icq.com/people/cmd.php?uin=[ICQNUMBER]&action=message">
+
-
Contact with ICQ</a>
+
-
</nowiki></pre>
+
-
 
+
-
Replacing [ICQNUMBER] with the user's actual ICQ number.
+
-
 
+
-
=== 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 published in an hCard as well.
+
-
 
+
-
* <code>[http://del.icio.us delicious]:</code>
+
-
** <code>&lt;a class="url" href="http://del.icio.us/rbach"&gt;Robert Bachmann's links&lt;/a&gt;</code>
+
-
* <code>[http://flickr.com Flickr]:</code>
+
-
** <code>&lt;a class="url" href="http://flickr.com/photos/tantek/"&gt;See my photos&lt;/a&gt;</code>
+
-
** <code>&lt;a class="url" href="http://flickr.com/people/tantek/"&gt;Flickr profile&lt;/a&gt;</code>
+
-
* <code>[http://technorati.com/ Technorati]:</code>
+
-
** <code>&lt;a class="url" href="http://technorati.com/profile/tantek/"&gt;Technorati profile&lt;/a&gt;</code>
+
-
* Add more here...
+
-
** ....
+
-
 
+
-
==== listing your other profiles ====
+
-
The most common case of sites listing other profiles is a blogger listing their own other profiles, or a site enabling a user to list on his or her profile on that site, links to his or her other profiles.  Since clearly the author/user is indicating that all those profiles mean the same person, it's best to mark them up with [[XFN]]'s <code>rel="me"</code> for explicit identity consolidation, e.g. if those links were on Tantek's blog or other social network profile:
+
-
 
+
-
* <code>[http://del.icio.us delicious]:</code>
+
-
** <code>&lt;a class="url" href="http://del.icio.us/rbach"&gt;Robert Bachmann's links&lt;/a&gt;</code>
+
-
* <code>my [http://flickr.com Flickr]:</code>
+
-
** <code>&lt;a class="url" href="http://flickr.com/photos/tantek/"&gt;See my photos&lt;/a&gt;</code>
+
-
** <code>&lt;a rel="me" class="url" href="http://flickr.com/people/tantek/"&gt;Flickr profile&lt;/a&gt;</code>
+
-
* <code>[http://technorati.com/ Technorati]:</code>
+
-
** <code>my &lt;a rel="me" class="url" href="http://technorati.com/profile/tantek/"&gt;Technorati profile&lt;/a&gt;</code>
+
-
* Add more here...
+
-
** ....
+
-
 
+
-
Such explicit user-driven identity consolidation is also a key building block for [[social-network-portability]] that is further explained in the context of [[hcard-xfn-supporting-friends-lists]].
+
-
 
+
-
=== Canonical Profiles on Sites ===
+
-
Sites sometimes have different pages for the "home" page for a person, and that person's user profile page.
+
-
 
+
-
For example Flickr has:
+
-
* your home page is at a URL like: <code>http://flickr.com/photos/</code> followed by your username, e.g.:
+
-
** http://flickr.com/photos/tantek/
+
-
* your profile page is at a URL like: <code>http://flickr.com/people/</code> followed by your username, e.g.:
+
-
** http://flickr.com/people/tantek/
+
-
 
+
-
In addition, sites often have a <em>canonical</em> URL for a person, and several alternate URLs.
+
-
 
+
-
As noted above, links to these URLs inside hCards that represent those people should have classname "url". 
+
-
 
+
-
In addition, such link(s) in hCards to the canonical URL for a person on that site should also have the classname of "uid".  This technique was proposed Ryan King at the first [[events/2007-08-28-social-network-portability-today|Social Network Portability Today lunchtime meetup]].
+
-
 
+
-
Building on the example(s) from the previous section:
+
-
* [http://flickr.com Flickr]:
+
-
** <code>&lt;a class="url" href="http://flickr.com/photos/tantek/"&gt;See my photos&lt;/a&gt;</code>
+
-
** <code>&lt;a rel="me" class="url uid" href="http://flickr.com/people/tantek/"&gt;Flickr profile&lt;/a&gt;</code>
+
-
 
+
-
Such a "url" + "uid" property could also be used by a site as that person's [[OpenID]] URL.
+
-
 
+
-
=== 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.
+
-
 
+
-
=== Lists of Organizations ===
+
-
Similar to [[hcard-examples#References_to_People_in_Blogrolls|lists of people]], lists of organizations (e.g. music bands) should use a list (unordered unless there is a specific reason to order it) with list items and hyperlink to the respective organization home pages.
+
-
 
+
-
E.g. this simple [[POSH]]:
+
-
 
+
-
<pre><nowiki>
+
-
<ul>
+
-
<li>
+
-
  <a href="http://microformats.org/">microformats.org</a>
+
-
</li>
+
-
<li>
+
-
  <a href="http://technorati.com/">Technorati</a>
+
-
</li>
+
-
<li>
+
-
  <a href="http://www.w3.org/">World Wide Web Consortium</a>
+
-
  (W3C)
+
-
  </a>
+
-
</li>
+
-
</ul>
+
-
</nowiki></pre>
+
-
 
+
-
can be easily enhanced with hCard:
+
-
 
+
-
<pre><nowiki>
+
-
<ul>
+
-
<li class="vcard">
+
-
  <a class="fn org url" href="http://microformats.org/">microformats.org</a>
+
-
</li>
+
-
<li class="vcard">
+
-
  <a class="fn org url" href="http://technorati.com/">Technorati</a>
+
-
</li>
+
-
<li class="vcard">
+
-
  <a class="fn org url" href="http://www.w3.org/">World Wide Web Consortium</a>
+
-
  (<span class="nickname">W3C</span>)
+
-
  </a>
+
-
</li>
+
-
</ul>
+
-
</nowiki></pre>
+
== <nowiki>RFC 2426</nowiki> examples in hCard ==
== <nowiki>RFC 2426</nowiki> examples in hCard ==
Line 402: Line 50:
=== 3.1.2 N Type Definition ===
=== 3.1.2 N Type Definition ===
-
==== Example 1 ====
+
==== N Example 1 ====
<pre><nowiki>
<pre><nowiki>
Line 424: Line 72:
Mr. John Quinlan Public, Esq.
Mr. John Quinlan Public, Esq.
-
==== Example 2 ====
+
==== N Example 2 ====
<pre><nowiki>
<pre><nowiki>
Line 451: Line 99:
=== 3.1.3 NICKNAME Type Definition ===
=== 3.1.3 NICKNAME Type Definition ===
-
==== Example 1 ====
+
==== NICKNAME Example 1 ====
<pre><nowiki>
<pre><nowiki>
Line 467: Line 115:
Robbie
Robbie
-
==== Example 2 ====
+
==== NICKNAME Example 2 ====
<pre><nowiki>
<pre><nowiki>
Line 486: Line 134:
=== 3.1.4 PHOTO Type Definition ===
=== 3.1.4 PHOTO Type Definition ===
-
==== Example 1 ====
+
==== PHOTO Example 1 ====
<pre><nowiki>
<pre><nowiki>
PHOTO;VALUE=uri:http://www.abc.com/pub/photos/jqpublic.gif
PHOTO;VALUE=uri:http://www.abc.com/pub/photos/jqpublic.gif
Line 497: Line 145:
</nowiki></pre>
</nowiki></pre>
-
==== Example 2 ====
+
==== PHOTO Example 2 ====
<pre><nowiki>
<pre><nowiki>
PHOTO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
PHOTO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
Line 516: Line 164:
=== 3.1.5 BDAY Type Definition ===
=== 3.1.5 BDAY Type Definition ===
-
==== Example 1 ====
+
==== BDAY Example 1 ====
<pre><nowiki>
<pre><nowiki>
Line 532: Line 180:
<abbr class="bday" title="1996-04-15">April 15, 1996</abbr>
<abbr class="bday" title="1996-04-15">April 15, 1996</abbr>
-
==== Example 2 ====
+
==== BDAY Example 2 ====
<pre><nowiki>
<pre><nowiki>
Line 548: Line 196:
<abbr class="bday" title="1953-10-15T23:10:00Z">Oct 15, 1953</abbr>
<abbr class="bday" title="1953-10-15T23:10:00Z">Oct 15, 1953</abbr>
-
==== Example 3 ====
+
==== BDAY Example 3 ====
<pre><nowiki>
<pre><nowiki>
Line 665: Line 313:
=== 3.3.2 EMAIL Type Definition ===
=== 3.3.2 EMAIL Type Definition ===
-
==== Example 1 ====
+
==== EMAIL Example 1 ====
<pre><nowiki>
<pre><nowiki>
Line 681: Line 329:
[mailto:jqpublic@xyz.dom1.com email jqpublic]
[mailto:jqpublic@xyz.dom1.com email jqpublic]
-
==== Example 2 ====
+
==== EMAIL Example 2 ====
<pre><nowiki>
<pre><nowiki>
Line 697: Line 345:
[mailto:jdoe@isp.net email jdoe]
[mailto:jdoe@isp.net email jdoe]
-
==== Example 3 ====
+
==== EMAIL Example 3 ====
<pre><nowiki>
<pre><nowiki>
Line 734: Line 382:
=== 3.4.1 TZ Type Definition ===
=== 3.4.1 TZ Type Definition ===
-
==== Example 1 ====
+
==== TZ Example 1 ====
<pre><nowiki>
<pre><nowiki>
Line 749: Line 397:
-05:00
-05:00
-
==== Example 2 ====
+
==== TZ Example 2 ====
<pre><nowiki>
<pre><nowiki>
Line 822: Line 470:
=== 3.5.3 LOGO Type Definition ===
=== 3.5.3 LOGO Type Definition ===
-
==== Example 1 ====
+
==== LOGO Example 1 ====
<pre><nowiki>
<pre><nowiki>
Line 839: Line 487:
-
==== Example 2 ====
+
==== LOGO Example 2 ====
<pre><nowiki>
<pre><nowiki>
Line 861: Line 509:
=== 3.5.4 AGENT Type Definition ===
=== 3.5.4 AGENT Type Definition ===
-
==== Example 1 ====
+
==== AGENT Example 1 ====
<pre><nowiki>
<pre><nowiki>
Line 878: Line 526:
JQPUBLIC
JQPUBLIC
-
==== Example 2 ====
+
==== AGENT Example 2 ====
<pre><nowiki>
<pre><nowiki>
Line 889: Line 537:
<pre><nowiki>
<pre><nowiki>
<span class="agent vcard">
<span class="agent vcard">
-
  <a class="email fn n" href="mailto:sthomas@host.com">Susan Thomas</a>,
+
  <a class="email fn" href="mailto:sthomas@host.com">Susan Thomas</a>,
  <span class="tel">+1-919-555-1234</span>
  <span class="tel">+1-919-555-1234</span>
</span>
</span>
Line 898: Line 546:
[mailto:sthomas@host.com Susan Thomas], +1-919-555-1234
[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.
+
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 the implied N rule applies to the given "fn" property.
=== 3.5.5 ORG Type Definition ===
=== 3.5.5 ORG Type Definition ===
Line 922: Line 570:
=== 3.6.1 CATEGORIES Type Definition ===
=== 3.6.1 CATEGORIES Type Definition ===
-
==== Example 1 ====
+
==== CATEGORIES Example 1 ====
<pre><nowiki>
<pre><nowiki>
Line 939: Line 587:
-
==== Example 2 ====
+
==== CATEGORIES Example 2 ====
<pre><nowiki>
<pre><nowiki>
Line 985: Line 633:
=== 3.6.4 REV Type Definition ===
=== 3.6.4 REV Type Definition ===
-
==== Example 1 ====
+
==== REV Example 1 ====
<pre><nowiki>
<pre><nowiki>
Line 1,001: Line 649:
<abbr class="rev" title="1995-10-31T22:27:10Z">Updated: 10/31 10:27p</abbr>
<abbr class="rev" title="1995-10-31T22:27:10Z">Updated: 10/31 10:27p</abbr>
-
==== Example 2 ====
+
==== REV Example 2 ====
<pre><nowiki>
<pre><nowiki>
Line 1,019: Line 667:
=== 3.6.5 SORT-STRING Type Definition ===
=== 3.6.5 SORT-STRING Type Definition ===
-
==== Example 1 ====
+
==== SORT-STRING Example 1 ====
<pre><nowiki>
<pre><nowiki>
Line 1,030: Line 678:
<pre><nowiki>
<pre><nowiki>
-
<span class="n"
+
<span class="n">
  <span class="honorific-prefix">Sir</span>
  <span class="honorific-prefix">Sir</span>
  <span class="fn">
  <span class="fn">
Line 1,049: Line 697:
Sir Rene van der Harten (J.), R.D.O.N.
Sir Rene van der Harten (J.), R.D.O.N.
-
==== Example 2 ====
+
==== SORT-STRING Example 2 ====
<pre><nowiki>
<pre><nowiki>
Line 1,073: Line 721:
Robert Pau Shou Chang
Robert Pau Shou Chang
-
==== Example 3 ====
+
==== SORT-STRING Example 3 ====
<pre><nowiki>
<pre><nowiki>
Line 1,095: Line 743:
Osamu Koura
Osamu Koura
-
==== Example 4 ====
+
==== SORT-STRING Example 4 ====
<pre><nowiki>
<pre><nowiki>
Line 1,123: Line 771:
Oscar del Pozo
Oscar del Pozo
-
==== Example 5 ====
+
==== SORT-STRING Example 5 ====
<pre><nowiki>
<pre><nowiki>
Line 1,147: Line 795:
=== 3.6.6 SOUND Type Definition ===
=== 3.6.6 SOUND Type Definition ===
-
==== Example 1 ====
+
==== SOUND Example 1 ====
<pre><nowiki>
<pre><nowiki>
Line 1,169: Line 817:
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.
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 ====
+
==== SOUND Example 2 ====
<pre><nowiki>
<pre><nowiki>
SOUND;TYPE=BASIC;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
SOUND;TYPE=BASIC;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
Line 1,230: Line 878:
=== 3.7.1 CLASS Type Definition ===
=== 3.7.1 CLASS Type Definition ===
-
==== Example 1 ====
+
==== CLASS Example 1 ====
<pre><nowiki>
<pre><nowiki>
Line 1,246: Line 894:
PUBLIC
PUBLIC
-
==== Example 2 ====
+
==== CLASS Example 2 ====
<pre><nowiki>
<pre><nowiki>
Line 1,262: Line 910:
PRIVATE
PRIVATE
-
==== Example 3 ====
+
==== CLASS Example 3 ====
<pre><nowiki>
<pre><nowiki>
Line 1,464: Line 1,112:
</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>
 
-
    <!-- birthday -->
 
-
    <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="fn 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><span>erred 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
 
-
FN:Fréderic de Villamil
 
-
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 ==
+
:'''This is a sub-page of [[hcard-examples]]'''
-
* [[hcard-examples-issues]]
+
-
{{hcard-related-pages}}
+

Current revision

This is a sub-page of hcard-examples

Contents

RFC 2426 examples in hCard

These are 1:1 hCard examples for each example in RFC2426.

Mark Pilgrim has made these hCard examples available as separate files:

2.4.2 VCARD

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

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

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

this hCard could be displayed as:

Joe Friday
+1-919-555-7878
Area Administrator, Assistant

3.1.1 FN Type Definition

FN:Mr. John Q. Public\, Esq.

this vCard fragment as an hCard fragment:

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

this hCard fragment could be displayed as:

Mr. John Q. Public, Esq.

3.1.2 N Type Definition

N Example 1

N:Public;John;Quinlan;Mr.;Esq.

this vCard fragment as an hCard fragment:

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

this hCard fragment could be displayed as:

Mr. John Quinlan Public, Esq.

N Example 2

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

this vCard fragment as an hCard fragment:

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

this hCard fragment would be displayed as:

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

3.1.3 NICKNAME Type Definition

NICKNAME Example 1

NICKNAME:Robbie

this vCard fragment as an hCard fragment:

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

this hCard fragment could be displayed as:

Robbie

NICKNAME Example 2

NICKNAME:Jim,Jimmie

this vCard fragment as an hCard fragment:

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

this hCard fragment would be displayed as:

Jim, Jimmie

3.1.4 PHOTO Type Definition

PHOTO Example 1

PHOTO;VALUE=uri:http://www.abc.com/pub/photos/jqpublic.gif

this vCard fragment as an hCard fragment:

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

PHOTO Example 2

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

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

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

3.1.5 BDAY Type Definition

BDAY Example 1

BDAY:1996-04-15

this vCard fragment as an hCard fragment:

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

this hCard fragment could be displayed as:

April 15, 1996

BDAY Example 2

BDAY:1953-10-15T23:10:00Z

this vCard fragment as an hCard fragment:

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

this hCard fragment could be displayed as:

Oct 15, 1953

BDAY Example 3

BDAY:1987-09-27T08:30:00-06:00

this vCard fragment as an hCard fragment:

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

this hCard fragment could be displayed as:

Sept 9, 1987

3.2.1 ADR Type Definition

ADR;TYPE=dom,home,postal,parcel:;;123 Main
  Street;Any Town;CA;91921-1234

this vCard fragment as an hCard fragment:

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

this hCard fragment could be displayed as:

US home address, for mail and shipments:

123 Main Street

Any Town, CA, 91921-1234

3.2.2 LABEL Type Definition

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.

this vCard fragment as an hCard fragment:

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

</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 local delivery to my home of mail and packages:

Mr.John Q. Public, Esq.
Mail Drop: TNE QB
123 Main Street
Any Town, CA  91921-1234
U.S.A.

3.3.1 TEL Type Definition

TEL;TYPE=work,voice,pref,msg:+1-213-555-1234

this vCard fragment as an hCard fragment:

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

this hCard fragment could be displayed as:

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

3.3.2 EMAIL Type Definition

EMAIL Example 1

EMAIL;TYPE=internet:jqpublic@xyz.dom1.com

this vCard fragment as an hCard fragment:

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

this hCard fragment could be displayed as:

email jqpublic

EMAIL Example 2

EMAIL;TYPE=internet:jdoe@isp.net

this vCard fragment as an hCard fragment:

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

this hCard fragment could be displayed as:

email jdoe

EMAIL Example 3

EMAIL;TYPE=internet,pref:jane_doe@abc.com

this vCard fragment as an hCard fragment:

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

this hCard fragment could be displayed as:

preferred email for jane_doe

3.3.3 MAILER Type Definition

MAILER:PigeonMail 2.1

this vCard fragment as an hCard fragment:

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

this hCard fragment could be displayed as:

Jane Doe uses PigeonMail 2.1 for email.

3.4.1 TZ Type Definition

TZ Example 1

TZ:-05:00

this vCard fragment as an hCard fragment:

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

this hCard fragment could be displayed as:

-05:00

TZ Example 2

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

this vCard fragment as an hCard fragment:

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

this hCard fragment could be displayed as:

EST

3.4.2 GEO Type Definition

GEO:37.386013;-122.082932

this vCard fragment as an hCard fragment:

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

this hCard fragment could be displayed as:

37.386013, -122.082932

3.5.1 TITLE Type Definition

TITLE:Director\, Research and Development

this vCard fragment as an hCard fragment:

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

this hCard fragment could be displayed as:

Director, Research and Development

3.5.2 ROLE Type Definition

ROLE:Programmer

this vCard fragment as an hCard fragment:

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

this hCard fragment could be displayed as:

Programmer

3.5.3 LOGO Type Definition

LOGO Example 1

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

this vCard fragment as an hCard fragment

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

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

mf-lg-ora.gif


LOGO Example 2

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

this vCard fragment as an hCard fragment

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

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

3.5.4 AGENT Type Definition

AGENT Example 1

AGENT;VALUE=uri:
 CID:JQPUBLIC.part3.960129T083020.xyzMail@host3.com

this vCard fragment as an hCard fragment

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

this hCard fragment could be displayed as:

JQPUBLIC

AGENT Example 2

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

this vCard fragment as an hCard fragment

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

this hCard fragment could be displayed as:

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 the implied N rule applies to the given "fn" property.

3.5.5 ORG Type Definition

ORG:ABC\, Inc.;North American Division;Marketing

this vCard fragment as an hCard fragment:

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

this hCard fragment could be displayed as:

ABC, Inc., North American Division, Marketing

3.6.1 CATEGORIES Type Definition

CATEGORIES Example 1

CATEGORIES:TRAVEL AGENT

this vCard fragment as an hCard fragment:

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

this hCard fragment could be displayed as:

TRAVEL AGENT


CATEGORIES Example 2

CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY

this vCard fragment as an hCard fragment:

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

this hCard fragment would be displayed as:

INTERNET, IETF, INDUSTRY, INFORMATION TECHNOLOGY

3.6.2 NOTE Type Definition

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

this vCard fragment as an hCard fragment:

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

this hCard fragment could be displayed as:

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

3.6.3 PRODID Type Definition

PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN

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

REV Example 1

REV:1995-10-31T22:27:10Z

this vCard fragment as an hCard fragment:

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

this hCard fragment could be displayed as:

Updated: 10/31 10:27p

REV Example 2

REV:1997-11-15

this vCard fragment as an hCard fragment:

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

this hCard fragment could be displayed as:

Updated: November 15

3.6.5 SORT-STRING Type Definition

SORT-STRING Example 1

FN:Rene van der Harten
N:van der Harten;Rene;J.;Sir;R.D.O.N.
SORT-STRING:Harten

this vCard fragment as an hCard fragment:

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

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 DRY principle than vCard.

this hCard fragment could be displayed as:

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

SORT-STRING Example 2

FN:Robert Pau Shou Chang
N:Pau;Shou Chang;Robert
SORT-STRING:Pau

this vCard fragment as an hCard fragment:

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

Note: Not only was the string "Pau" was NOT repeated in the hCard (better 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 element conservation and use only one element for both properties.

this hCard fragment could be displayed as:

Robert Pau Shou Chang

SORT-STRING Example 3

FN:Osamu Koura
N:Koura;Osamu
SORT-STRING:Koura

this vCard fragment as an hCard fragment:

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

Note: This example, in addition to illustrating better support for the DRY principle, also makes use of the Implied "N" Optimization.

this hCard fragment could be displayed as:

Osamu Koura

SORT-STRING Example 4

FN:Oscar del Pozo
N:del Pozo Triscon;Oscar
SORT-STRING:Pozo

this vCard fragment as an hCard fragment:

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

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

SORT-STRING Example 5

FN:Christine d'Aboville
N:d'Aboville;Christine
SORT-STRING:Aboville

this vCard fragment as an hCard fragment:

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

Note: This example re-demonstrates the same hCard advantages/efficiencies demonstrated in example 3 above.

this hCard fragment could be displayed as:

Christine d'Aboville

3.6.6 SOUND Type Definition

SOUND Example 1

SOUND;TYPE=BASIC;VALUE=uri:CID:JOHNQPUBLIC.part8.
 19960229T080000.xyzMail@host1.com

this vCard fragment as an hCard fragment

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

this hCard fragment would probably be displayed as

pronounciation of "JOHN Q PUBLIC"

unless your browser supports the MIME type "audio/basic" (defined in RFC2046 section 4.3) and has some way of retrieving "CID:" urls.

SOUND Example 2

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

this vCard fragment as an hCard fragment

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

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

3.6.7 UID Type Definition

UID:19950401-080045-40000F192713-0052

this vCard fragment as an hCard fragment

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

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

URL:http://www.swbyps.restaurant.french/~chezchic.html

this vCard fragment as an hCard fragment

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

this hCard fragment could be displayed as

Chez Chic


3.7.1 CLASS Type Definition

CLASS Example 1

CLASS:PUBLIC

this vCard fragment as an hCard fragment

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

this hCard fragment could be displayed as

PUBLIC

CLASS Example 2

CLASS:PRIVATE

this vCard fragment as an hCard fragment

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

this hCard fragment could be displayed as

PRIVATE

CLASS Example 3

CLASS:CONFIDENTIAL

this vCard fragment as an hCard fragment

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

this hCard fragment could be displayed as

CONFIDENTIAL

3.7.2 KEY Type Definition

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

this vCard fragment as an hCard fragment

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

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

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

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:

<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><span>erred 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>

this hCards could be displayed as

Frank Dawson

Lotus Development Corporation

work address (mail and packages):

6544 Battleford Drive

Raleigh NC 27613-3502

U.S.A.

+1-919-676-9515 (w, vm)

+1-919-676-9564 (wf)

preferred email, alternate email

Tim Howes

Netscape Communications Corp.

work address:

501 E. Middlefield Rd.

Mountain View, CA 94043

U.S.A.

+1-415-937-3419 (w, vm)

+1-415-528-4164 (wf)


This is a sub-page of hcard-examples
hcard-examples-rfc2426 was last modified: Sunday, April 7th, 2013

Views