Microformats Wiki - User contributions [en]

hcard-examples-rfc2426

2005-09-07T16:08:53Z

Bryan: /* Example 2 */

= hCard examples =

Example [[hcard|hCards]].

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

== RFC 2426 examples in hCard ==

* In the process of creating 1:1 hCard examples for each example in [http://www.ietf.org/rfc/rfc2426.txt RFC 2426].

=== 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] 
+1-919-555-7878 
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>
Mr. John Q. Public, Esq.
</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>

Mr.
John
Quinlan
Public,
Esq.

</nowiki></pre>

with singular class names instead of plural
(see Issue 1 in [[hcard-parsing]]).

<pre><nowiki>

Mr.
John
Quinlan
Public,
Esq.

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

Dr.
John
<ul class="additional-names">
<li>Philip</li>
<li>Paul</li>
</ul>
Stevenson,
<ul class="honorific-suffixes">
<li>Jr.</li>
<li>M.D.</li>
<li>A.C.P.</li>
</ul>

</nowiki></pre>

and with this CSS2(.1) style sheet:

<pre><nowiki>
.n ul,.n li { display:inline; list-style:none }
.honorific-suffixes li:before {
content:", "; margin-left:-.7ex;
}
</nowiki></pre>

In a CSS2(.1) compliant browser, this hCard fragment would be displayed as:

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

In a CSS1 compliant browser (lacking some CSS2 features), this hCard fragment would be displayed as:

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

Note the lack of commas, which we are unable to insert inbetween the items on the list (since no character data is allowed directly inside the <ul>), and the lack of CSS2(.1) generated content support means the style rule that inserts them doesn't take effect either.

However, with singular class names instead of plural
(see Issue 1 in [[hcard-parsing]]).

<pre><nowiki>

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

</nowiki></pre>

without any special style sheet, this hCard fragment would be displayed as:

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

This is another good reason to go with singular class names.

=== 3.1.3 NICKNAME Type Definition ===

==== Example 1 ====

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

this vCard fragment as an hCard fragment:

<pre><nowiki>
Robbie
</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>
<ul class="nickname"><li>Jim</li><li>Jimmie</li></ul>
</nowiki></pre>

and with this CSS2(.1) style sheet:

<pre><nowiki>
ul.nickname,.nickname li { display:inline; list-style:none }
.nickname li:before {
content:", "; margin-left:-.7ex;
}
.nickname li:first-child:before {
content:""; margin-left: 0;
}
</nowiki></pre>

In a CSS2(.1) compliant browser, this hCard fragment would be displayed as:

Jim, Jimmie

In a CSS1 compliant browser (lacking some CSS2 features), this hCard fragment would be displayed as:

Jim Jimmie

Note the lack of a comma, which we are unable to insert inbetween the item(s) on the list (since no character data is allowed directly inside the <ul>), and the lack of CSS2(.1) generated content support means the style rule that inserts them doesn't take effect either.

The class name "nickname" is already singular, and if we simply treat it as such per issue 1 in [[hcard-parsing]], we can encode this hCard fragment as:

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

without any special style sheet, this hCard fragment would be displayed as:

Jim, Jimmie

This is another good reason to go with singular class names, or in this case, a singular interpretation of the class name.

=== 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>
home 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>
Any Town, CA,
91921-1234
</div>
</nowiki></pre>

this hCard fragment could be displayed as:

<div class="adr">
<abbr class="type" title="dom">US</abbr>
home 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>
Any Town, CA,
91921-1234
</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>

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

</nowiki></pre>

this hCard fragment could be displayed as:

<abbr class="type" title="pref">my</abbr>
work
<abbr class="type" title="voice">phone,</abbr>
<abbr class="type" title="msg">with voicemail:</abbr>
+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 PigeonMail 2.1 for email.
</nowiki></pre>

this hCard fragment could be displayed as:

Jane Doe uses PigeonMail 2.1 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>
-05:00
</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>

37.386013,
-122.082932

</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>
Director, Research and Development
</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>
Programmer
</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>

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

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

ABC, Inc.,
North American Division,
Marketing,

</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>
TRAVEL AGENT
</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>
<ul class="categories">
<li>INTERNET</li>
<li>IETF</li>
<li>INDUSTRY</li>
<li>INFORMATION TECHNOLOGY</li>
</ul>
</nowiki></pre>

this hCard fragment could be displayed as:

* INTERNET
* IETF
* INDUSTRY
* INFORMATION TECHNOLOGY

and with this CSS2(.1) style sheet:

<pre><nowiki>
ul.categories,.categories li { display:inline; list-style:none }
.categories li:before {
content:", "; margin-left:-.7ex;
}
.categories li:first-child:before {
content:""; margin-left: 0;
}
</nowiki></pre>

in a CSS2(.1) compliant browser, this hCard fragment would be displayed as:

INTERNET, IETF, INDUSTRY, INFORMATION TECHNOLOGY

In a CSS1 compliant browser (lacking some CSS2 features), this hCard fragment would be displayed as:

INTERNET IETF INDUSTRY INFORMATION TECHNOLOGY

Note the lack of commas, which we are unable to insert inbetween the item(s) on the list (since no character data is allowed directly inside the <code><ul></code>), and the lack of CSS2(.1) generated content support means the style rule that inserts them doesn't take effect either. Note also that "INFORMATION TECHNOLOGY" appears to be two categories (INFORMATION and TECHNOLOGY) since it is only separated from other categories uing a space.

But with singular class names instead of plural (see Issue 1 in [[hcard-parsing]]).

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

without any special style sheet, this hCard fragment would be displayed as:

INTERNET, IETF, INDUSTRY, INFORMATION TECHNOLOGY

This is another good reason to go with singular class names.

=== 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>
This fax number is operational 0800 to 1715 EST, Mon-Fri.
</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>
Sir

Rene

van der Harten


(J.),
R.D.O.N.

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

Note 2: With singular class names instead of plural (see Issue 1 in [[hcard-parsing]]), "honorific-prefixes" would be "honorific-prefix", "honorific-suffixes" would be "honorific-suffix", and "additional-names" would be "additional-name".

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>

Robert
Pau
Shou Chang

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

Note 2: With singular class names instead of plural (see Issue 1 in [[hcard-parsing]]), "additional-names" would be "additional-name".

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>

Osamu Koura

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


Oscar
del Pozo


del Pozo Triscon


</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:Chistine d'Aboville
N:d'Aboville;Christine
SORT-STRING:Aboville
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>

Chistine d'Aboville

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

Chistine d'Aboville

== Other ==

* See [[hcard-brainstorming]] for more examples (which may eventually be moved here) and analysis.

buttons

2005-09-04T22:33:38Z

Bryan:

buttons

2005-09-04T22:33:16Z

Bryan:

buttons

2005-09-04T22:33:01Z

Bryan: /* badges */

buttons

2005-09-04T22:14:09Z

Bryan: /* badges */

buttons

2005-09-04T22:13:48Z

Bryan: /* badges */

= Microformats buttons =

There have been requests for buttons for various microformats. Either badges, or buttons that do something with the specific microformats. This page keeps a list of buttons, and requests as well. - [http://tantek.com/log/ Tantek]

== badges ==

* [[hcard|hCard]]
** http://www.crowley.nl/images/hcard.png
** http://rbach.priv.at/Misc/Volatile/hCard.gif
** <a style="font: 9px Geneva, Verdana, sans-serif; padding: 1px 1em 1px 0;
border: 1px solid black; background: #888; color: #FFF; text-decoration: none;" class="hcard-badge" href="" title="">>>> hCard</a>

== requests ==

* logos and buttons for all microformats

User:Bryan

2005-08-19T19:09:03Z

Bryan:

Bryan J Busch

[http://www.re-run.com re-run]

User:Bryan

2005-08-19T19:08:52Z

Bryan:

Bryan J Busch
[http://www.re-run.com re-run]

blog-post-brainstorming

2005-08-17T19:23:58Z

Bryan:

==Obstacles==

===Header Tag for Entry Title?===
--[[User:Bryan|Bryan]] 14:55, 14 Aug 2005 (PDT)

Many weblog CMSes allow for concurrent publishing of entries in the following ways:

* multiple entries on a page (an "Index," monthly archive, category archive, etc. see [http://re-run.com/category/creative/comedy/ Example])
* one entry on a page (see [http://re-run.com/2005/02/11/nickels-worth-of-free-advice/ Example])

Early attempts at [[blog-post-formats]] have set the title of the blog post to use the h3 tag.

At least where individual entry pages are concerned (and possible including indexes and archives), I recommend using h1 for the entry title, given that the entry is by far the most important chunk of information on the page, and it's what we'd want search engines to recognize as such. In the case where the h1 was used for the site title, fears about "losing" this information should be allayed by simply including the site name in the title tag, after the title of the article / entry / post.

==See Also==
* [[blog-post-formats]]

blog-post-brainstorming

2005-08-17T19:23:50Z

Bryan:

blog-post-brainstorming

2005-08-17T19:23:40Z

Bryan:

blog-post-brainstorming

2005-08-14T22:05:20Z

Bryan: /* Header Tag for Entry Title? */

blog-post-brainstorming

2005-08-14T21:55:47Z

Bryan: /* Header Tag for Entry Title? */

blog-post-brainstorming

2005-08-14T21:54:38Z

Bryan:

==Obstacles==

===Header Tag for Entry Title?===

Many weblog CMSes allow for concurrent publishing of entries in the following ways:

* multiple entries on a page (an "Index," monthly archive, category archive, etc. see [http://re-run.com/category/creative/comedy/ Example])
* one entry on a page (see [http://re-run.com/2005/02/11/nickels-worth-of-free-advice/ Example])

Early attempts at [[blog-post-formats]] have set the title of the blog post to use the h3 tag.

At least where individual entry pages are concerned (and possible including indexes and archives), I recommend using h1 for the entry title, given that the entry is by far the most important chunk of information on the page.