Difference between revisions of "representative-hcard-authoring"

From Microformats Wiki
representative-hcard-authoring
Jump to navigation Jump to search
(needs update for microformats2)
m (Replace <entry-title> with {{DISPLAYTITLE:}})
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
<entry-title>representative hCard authoring</entry-title>
+
{{DISPLAYTITLE:representative hCard authoring}}
  
----
+
{{latest|representative-h-card-authoring}}
NEEDS UPDATE for [[microformats2]] [[h-card]].
 
----
 
  
 
To publish a [[representative hCard]] on a page, in addition to properly following [[hcard-authoring]] instructions, you need to do at least one of two of the following (you can do both).
 
To publish a [[representative hCard]] on a page, in addition to properly following [[hcard-authoring]] instructions, you need to do at least one of two of the following (you can do both).

Latest revision as of 16:32, 18 July 2020


See latest version: representative h-card authoring

To publish a representative hCard on a page, in addition to properly following hCard authoring tips instructions, you need to do at least one of two of the following (you can do both).

1. hyperlink to the page itself, perhaps around your icon or name (or both), and use both the "uid" and "url" class names in the class attribute on the hyperlink. e.g.:

<span class="vcard">
 <a href="http://tantek.com/" class="url uid fn">Tantek Çelik</a>
</span>

2. markup your links to other profiles with both rel="me" and the "url" class name. e.g.:

<span class="vcard">
 <span class="fn">Tantek Çelik</span> 
 (<a href="http://twitter.com/t" rel="me" class="url">my Twitter</a>)
</span>

Or better yet do both:

<span class="vcard">
 <a href="http://tantek.com/" class="url uid fn">Tantek Çelik</a>
 (<a href="http://twitter.com/t" rel="me" class="url">my Twitter</a>)
</span>

which has the following advantages over either individual example above:

  • a richer, more semantic hCard (e.g. providing two URLs for the person rather than just one)
  • works with both hCard-only parsers/crawlers and XFN-only parsers/crawlers

see also