hcard-implied: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
No edit summary
 
(bypass redirects)
Line 29: Line 29:
Which amounts to an almost 500% increase in code. For two words and a <abbr>URL</abbr>.
Which amounts to an almost 500% increase in code. For two words and a <abbr>URL</abbr>.


* For more examples, see [[implied-hcard-examples]]
* For more examples, see [[hcard-implied-examples]]
* For ideas refer to [[implied-hcard-brainstorming]]
* For ideas refer to [[hcard-implied-brainstorming]]

Revision as of 21:38, 8 December 2006

Implied hCard

Implied hCards attempt to streamline creation and markup for simple hCards by assuming information from common design patterns.

Authors

Why?

As microformats grow and emerge, the barrier to entry for writing them increases. Already, compound microformats such as hAtom, hResume and hReview are comprised of data from hCard, hCal, and rel-tag, and writing to the former requires knowledge of the latter even if the constructs used are quite simple. In addition, adding microformats to a Web page often requires adding a significant amount of tags to code, which often have to be added (time-consumingly) by hand. For example:

<a href="http://www.example.com/">John Doe</a>

quickly becomes:

<span class="vcard">
<a class="url fn n" href="http://www.example.com/">
<span class="given-name">John</span>
<span class="family-name">
<span class="sort-string">D</span>oe
</span>
</a>
</span>

Which amounts to an almost 500% increase in code. For two words and a URL.