hreview-aggregate

<entry-title>hReview-aggregate 0.1</entry-title> This document represents a draft microformat specification. Although drafts are somewhat mature in the development process, the stability of this document cannot be guaranteed, and implementers should be prepared to keep abreast of future developments and changes. Watch this wiki page, or follow discussions on the #microformats IRC channel to stay up-to-date.

hReview-aggregate is a format for embedding review information (of products, services, businesses, etc). Whereas hReview is intended for an individual review, hReview-aggregate is meant for summary information about a collection of user or critic reviews about an item. hReview-aggregate is one of several microformats open standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.

Microformats Draft Specification 2009-11-10

Editor

Kavi Goel, Google

Authors/Contributers (alphabetical)

Tantek Çelik

Othar Hansson, Google

Jay Myers, Best Buy, Co., Inc.

Introduction

Many websites publish reviews using a variety of organization schemes. hReview-aggregate and the similar microformat hReview were designed to enable sharing of review information.

hReview, created in 2006, is well suited to mark up reviews done by individuals on their own websites or for editor's reviews for a new product or service. However, in recent years, there has been an increasing number of sites who aggregate user reviews, either by accepting reviews submitted to their website or by collecting those user reviews from across the web. In these cases, it is often valuable to share not just the individual reviews shown on the webpage, but the consensus opinion derived from those individual reviews.

hReview-aggregate was created to address this need. hReview-aggregate is a standard that can be used to share the number of reviews, average rating, and consensus opinion for a particular product or service. It is meant to complement hReview and reuses hReview properties wherever appropriate. Research and discussion that fed into the design of hReview-aggregate can be found on the aggregate review brainstorming wiki page.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Scope

Collections of reviews consistently share several common aspects. Where possible hReview-aggregate has been based on this common subset.

Out of scope

Portions of reviews that are specific to particular kinds of items have been omitted from hReview-aggregate.

Format

Schema

The hReview-aggregate schema consists of the following:

• hReview-aggregate (hreview-aggregate)
  • item info. required. fn (url || photo ) | hCard (for person or business) | hCalendar (for event) | hProduct (for product)
  • rating. required. fixed point integer [1.0-5.0], with optional alternate worst (default:1.0) and/or best (default:5.0), also fixed point integers, and explicit average.
  • count. required. non-negative integer.
  • summary. optional. text.

Property details

Details of the hReview-aggregate properties:

item:: This required property MUST have at a minimum the name of the entity being reviewed (using the subproperty "fn"), or alternatively have an encapsulated microformat (i.e. hCard for a business or person, hProduct for a product, or hCalendar for an event). If an encapsulated microformat is not used, a URI ("url") for the item and a photo or depiction ("photo") MAY also be provided. Non-URL unique item IDs (e.g. ISBNs, UPCs) MAY be represented as a URN ("url") for the item. Encapsulated microformats must be set on the item itself (e.g. class="item vcard"). However, when using item info subproperties ("fn", "url", "photo"), they must be nested inside the item element.

rating:: The rating is a fixed point integer (one decimal point of precision) from 1.0 to 5.0 inclusive indicating the average rating for the item across all reviews, higher indicating a better rating by default. Optionally a different integral "worst" value and/or "best" value may be specified to indicate a different range (e.g. 6 from 0-10).

count:: This required property is used to specify the total number of reviews for the product or service.

summary:: This optional property can be the title for the review collection or a very short summary of the consensus opinion from the collection.

The item, rating, and summary properties are reused from hReview.

Examples

Basic example

Here is an example showing aggregate review information for a restaurant:

<div>
 <h3>
  <span>Mediterranean Wraps</span>
 </h3>
 <span>Customers flock to this small restaurant for their 
 tasty falafel and shawerma wraps and welcoming staff.</span>
 <span>4.5 out of 5 based on 17 reviews</span>
</div>

Adding hReview-aggregate markup to this is straightforward:

<div class="hreview-aggregate">
 <h3 class="item">
  <span class="fn">Mediterranean Wraps</span>
 </h3>
 <span class="summary">Customers flock to this small restaurant for their 
 tasty falafel and shawerma wraps and welcoming staff.</span>
 <span><span class="rating">4.5</span> out of 5 
 based on <span class="count">17</span> reviews</span>
</div>

Embedded microformat, 10-point rating scale

Often, there is more information available on a page about the item being reviewed than the title. Here is another example of a restaurant review, but with address information present.

<div>
 <div>
  <h3>Mediterranean Wraps</h3>
  <span>433 S California Ave</span>
  <span>Palo Alto, CA
  <span>(650) 321-8189</span>
 </div> 
 <span>Customers flock to this small restaurant for their 
 tasty falafel and shawerma wraps and welcoming staff.</span>
 <span>9.2 out of 10 based on 17 reviews</span>
</div>

And here it is with hReview-aggregate markup, along with an embedded hCard to describe the address and phone information for the restaurant:

<div class="hreview-aggregate">
 <div class="item vcard">
  <h3 class="fn">Mediterranean Wraps</h3>
  <span class="adr">
   <span class="street-address">433 S California Ave</span>
   <span><span class="locality">Palo Alto</span>, <span class="region">CA</span></span>
   <span class="tel">(650) 321-8189</span>
  </span>
 </div> 
 <span class="summary">Customers flock to this small restaurant for their 
 tasty falafel and shawerma wraps and welcoming staff.</span>
 <span class="rating"><span class="average">9.2</span> out of <span class="best">10</span> 
 based on <span class="count">17</span> reviews</span>
</div>

Note that the item and vcard are put next to each other in the same class attribute in order to show that the item being reviewed is described by the embedded hCard.

examples in the wild

This section is informative.

The following sites have implemented hReview-aggregate, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If your site is marked up with hReview aggregate, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page like hreview-aggregate-examples-in-wild.

• Google has implemented support for hReview-aggregate via Rich Snippets.
• STV Local uses hreview-aggregate for business ratings, average prices and contact details with hcard
• Critiki publishes ratings and reviews of Tiki bars, and uses hReview aggregate for average ratings on their pages, e.g. overview of The Tonga Room. (as tweeted by humuhumu 2009-09-21)
• NAPLESPLUS is an example of a website that has implemented hreview-aggregate via Google specs.
• ...

Related Pages

• hReview - microformat for marking up individual reviews
• Aggregate review brainstorming - discussions leading to the creation of hReview-aggregate and ideas for improvement.
• Aggregate review examples