<p>The microformats community has revisited it’s standard and come up with “<a href="http://microformats.org/wiki/microformats-2">microformats version 2</a>”. At first, I thought why! I don’t like change unless it gives me something worthwhile. After reviewing the work, I think the wholesale change to a new version of microformats is worthwhile because:</p>
<ol>
<li>The authoring patterns have been simplified even more and they are based on real life use cases e.g.: <code><a class="h-card" href="http://glennJones.net">Glenn Jones<a/></code> is a valid microformat</li>
<p><br></p>
<li>microformats 2 addresses one of the biggest problems in maintaining microformats in real sites. The class names are now prefixed i.e. class=”fn” is now class=”p-name”. The prefixes like “h-*” and “p-*” tells you a class is a microformat property and helps make sure classes are not moved or deleted by mistake</li>
<p><br></p>
<li>Like microdata, microformats 2 now has a full specification for a JSON API. This is important as it means the parsers should now have the same output and also browsers could implement this API.</li>
</ol>
<h2></h2>
