aggregate-microformat-template-brainstorming

(Difference between revisions)

Jump to: navigation, search
m
Current revision (04:27, 24 April 2009) (view source)
(Example: aggregate review on Yelp)
 
Line 32: Line 32:
* Aggregate microformats can optionally contain one or more sample instances of the microformats that are being aggregated. So an hReview-aggregate could contain sample hReviews. The reason for this is that sites often highlight specific instances of "hX" on their summary pages. Amazon shows the most popular reviews on the first page for a product. Shopping aggregator sites usually show the best deals first in a list of offers.
* Aggregate microformats can optionally contain one or more sample instances of the microformats that are being aggregated. So an hReview-aggregate could contain sample hReviews. The reason for this is that sites often highlight specific instances of "hX" on their summary pages. Amazon shows the most popular reviews on the first page for a product. Shopping aggregator sites usually show the best deals first in a list of offers.
-
==== Example: aggregate review on Yelp ====
+
==== Example: hypothetical aggregate review on Yelp ====
URL: http://www.yelp.com/biz/vive-sol-restaurant-mountain-view
URL: http://www.yelp.com/biz/vive-sol-restaurant-mountain-view
Line 38: Line 38:
<div class="hReview-aggregate">
<div class="hReview-aggregate">
  <span class="fn">Vive Sol Restaurant</span>
  <span class="fn">Vive Sol Restaurant</span>
-
  <span class="rating average">4</span> star rating  
+
  <div class="rating"><span class="average">4</span></div> star rating  
  based on <span class="count">180</span> reviews.
  based on <span class="count">180</span> reviews.
</div>
</div>

Current revision

Contents

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


Proposal

Here is a proposed template for defining aggregate microformats:

Example: hypothetical aggregate review on Yelp

URL: http://www.yelp.com/biz/vive-sol-restaurant-mountain-view

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

See also

aggregate-microformat-template-brainstorming was last modified: Friday, April 24th, 2009

Views