representative-h-card-authoring: Difference between revisions
Jump to navigation
Jump to search
GRegorLove (talk | contribs) (h-card-specific version) |
GRegorLove (talk | contribs) (remove XFN parser claim; if you have citations otherwise, please update) |
||
Line 22: | Line 22: | ||
which has the following advantages over either individual example above: | which has the following advantages over either individual example above: | ||
* a richer, more semantic h-card (e.g. providing two URLs for the person rather than just one) | * a richer, more semantic [[h-card]] (e.g. providing two URLs for the person rather than just one) | ||
== see also == | == see also == | ||
{{representative-hcard-related-pages}} | {{representative-hcard-related-pages}} |
Revision as of 22:29, 20 July 2018
<entry-title>representative h-card authoring</entry-title>
To publish a representative h-card on a page, in addition to properly following h-card-authoring 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 u-url
and u-uid
class names in the class attribute on the hyperlink. e.g.:
<span class="h-card">
<a href="http://tantek.com/" class="u-url u-uid">Tantek Çelik</a>
</span>
2. markup your links to other profiles with both rel="me"
and the u-url
class name. e.g.:
<span class="h-card">
<span class="p-name">Tantek Çelik</span>
(<a href="http://twitter.com/t" rel="me" class="u-url">my Twitter</a>)
</span>
Or better yet do both:
<span class="h-card">
<a href="http://tantek.com/" class="u-url u-uid">Tantek Çelik</a>
(<a href="http://twitter.com/t" rel="me" class="u-url">my Twitter</a>)
</span>
which has the following advantages over either individual example above:
- a richer, more semantic h-card (e.g. providing two URLs for the person rather than just one)