Revision as of 21:57, 10 April 2009 by Kavi (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)

Jump to: navigation, search


Aggregate microformats: brainstorming

Ideas/proposal for how to mark up aggregate or summary information about a collection of related microformats (i.e. aggregation of user reviews, summary of product offers, summary of posts on a message board, etc).

Since summary information can be relevant for many different types of microformats, it seems useful to design a system of marking up aggregate/summary information that generalizes to any existing or future microformat.

Why do we need to mark this information up at all?

Why can't the parser reconstruct the aggregate information by reading each individual microformat?

Although doing so is possible in some cases, in real-life scenarios it is often infeasible (or at a minimum much less efficient) to reconstruct aggregate info rather than reading the summary data written on the page directly, since the content being aggregated can be voluminous and spread across many web pages.

Types of information that appear in the examples


Here is a proposed template for defining aggregate microformats:

Example: aggregate review on Yelp


<div class="hReview-aggregate">
 <span class="fn">Vive Sol Restaurant</span>
 <span class="rating average">4</span> star rating 
 based on <span class="count">180</span> reviews.

See also

aggregate-microformat-template-brainstorming was last modified: Wednesday, December 31st, 1969