pageoneresults - 9:06 pm on Feb 26, 2010 (gmt 0)
Should Microformats markup be added to a product listing page listing 20 different products, or a product detail page listing only 1 product?
Anywhere that product data may appear is a prime candidate for Microformats. Think of it this way, you have the existing HTML elements which help define a page or section it, semantically speaking that is. Then along comes Microformats which allows you to further refine the data within those elements, hence the term Microformats.
If I had an existing ecommerce platform, I'd be reworking the templates this weekend to include the hProduct and hReview Microformats if your site qualifies.
We do not currently display this information, unless the product is part of a review.
I can understand why they chose the Reviews to be at the top of the list for testing. It all ties in with everything they've been doing from Local to Social. If you've got a shop that does ecommerce with product reviews, you've got another set of semantic properties to work with and, there are a bunch of them, hCard being just one of them for the representations of people, companies, organizations, and places.
tedster mentions reserving class names which I would like to reiterate. You SHOULD make sure that your existing class names do not interfere with the Microformats Property List.
hCard Property List
Even if your ecommerce site does not support reviews, I'd make the leap and start implementing hProducts as soon as possible. Not to mention hCard where applicable. If you have hReviews setup, you may even want to use hCard for the Authors. ;)
The [Microformats.org...] website provides all the information you need. You'll also find Google referencing Microformats consistently throughout their documentation.
Google Webmaster Central - Help us make the web better: An update on Rich Snippets
Monday, October 26, 2009 - [GoogleWebmasterCentral.Blogspot.com...]
Tags: Microformats, vCard, hCard, hProduct, hReview, hCalendar