Microformats Wiki - User contributions [en]

hproduct

2010-06-17T16:32:48Z

Kavi: /* Schema */

<entry-title>hProduct</entry-title>
{{DraftSpecification}}
__TOC__
hProduct is a microformat suitable for publishing and embedding product data. hProduct is one of several open microformats standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.

==hProduct Microformat Draft Specification==

; Editors/Authors
(alphabetical)
* [[User:PaulLee|Paul Lee]], Google Product Search
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

; Contributors
(alphabetical)
* Craig Cook, [http://focalcurve.com/ Focal Curve]
* Aaron Gustafson, [http://easy-designs.net/ Easy! Designs]

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

== Status ==
Draft, version 0.3.

== Introduction ==
The web is a thriving consumer marketplace with a plethora of manufacturers and vendors scattered across the globe. Sifting through massive amounts of unstructured product data is a difficult task for both browsers and machines alike. The hProduct microformat gives structure to this metadata by providing constructs to identify universal product attributes, plus a mechanism to accomodate the wide variation in product attributes.

The hProduct microformat can assist consumers, manufacturers and retailers in a number of ways. If a browser or application understands that a specific web page contains the hProduct microformat, it can inform and help facilitate the best product choice by the consumer to fulfill their needs. An adopted, open standard will ensure the correct product data is published between manufacturers and retailers, to the benefit of the consumer. Bringing order and structure to product data makes it easy for people and organizations to list the products and services they offer, and easy for web services to consume that product data for analysis and syndication.

=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

=== Inspiration and Acknowledgment ===
Many thanks go out to the contributors who laid the foundation for the current hProduct draft spec.

=== Scope ===
Giving details about a particular product is sometimes very complex as parameters are different for books and CDs than they are for iPods or cars. It should be very easy to mark up an item using hProduct and the syntax should be simple yet flexible enough for more advanced applications.

=== Out of Scope ===
This microformat does not intend to replicate any of the content proposed within [[hListing]] and would defer all money/transactional matters to that microformat. This microformat also does not attempt to specify a product ontology, or category-specific attributes; instead, it aims to create a framework to allow for flexible expression of both.

== Format ==
{{rfc-2119-intro}}

=== In General ===
The hProduct format is based on a set of fields common to numerous ecommerce sites and formats in use today on the web.

=== Schema ===
The hProduct schema consists of the following (see existing class names for reference):

*hproduct
** brand. optional. text. can also use [[hcard|hCard]] for manufacturer.
** category. optional. text. can also use rel-tag. re-used from [[hcard|hCard]].
** price. optional. floating point number. can use currency format.
** description. optional. text. can also include valid HTML markup. re-used from [[hreview|hReview]].
** fn. '''required.''' text. product name or title. re-used from [[hcard|hCard]].
** photo. optional. image element or link. re-used from [[hcard|hCard]].
** url. optional. href. can contain rel-tag rel='product'. re-used from [[hcard|hCard]].
** review. optional. [[hreview|hReview]], or [[hreview-aggregate|hReview-aggregate]].
** listing. optional. [[hlisting|hListing]], or [[aggregate-microformat-template-examples|hListing-aggregate]].
** identifier. optional.
*** type. required. - examples:
**** model
**** mpn
**** upc
**** isbn
**** issn
**** ean
**** jan
**** sn
**** vin
**** sku
*** value. required. - label may be implied

=== Field details ===
Class names <code class="class-name">category</code>, <code class="class-name">fn</code>, <code class="class-name">photo</code>, <code class="class-name">url</code> are reused from [[hcard|hCard]]. <code class="class-name">description</code> is reused from [[hreview|hReview]].

The fields of the hProduct schema represent the following:

*'''<code class="class-name">hproduct::</code>''' Root class name
*'''<code class="class-name">brand::</code>''' the class name brand is used identify brand of the product. {{should}} use [[hcard|hCard]] for manufacturer name. {{must}} be singular.
*'''<code class="class-name">category::</code>''' the class name category identifies product category. {{may}} use [[rel-tag]] microformat. {{may}} be plural to represent multiple categories.
*'''<code class="class-name">price::</code>''' the class name price is used to indicate the price of the product. {{must}} be singular.
*'''<code class="class-name">description::</code>''' the class name description is used to describe the product. {{must}} be singular.
*'''<code class="class-name">fn::</code>''' product text name. {{must}} be singular.
*'''<code class="class-name">photo::</code>''' the class name photo {{may}} be applied to an <img> or <a> element. {{may}} be plural.
*'''<code class="class-name">url::</code>''' the class name url {{should}} refer to the web page associated with product details. {{may}} use [[rel-tag]], rel='product'. {{must}} be singular.
*'''<code class="class-name">review::</code>''' the class name review identifies review(s) for the product. {{should}} use [[hreview|hReview]]. {{may}} be plural.
*'''<code class="class-name">listing::</code>''' the class name listing identifies product listings. {{should}} use [[hlisting|hListing]]. {{may}} be plural.
*'''<code class="class-name">identifier::</code>''' the identifier structure is used to describe product identifiers like Model, UPC or SKU, and is designed to accommodate new or as-yet-unidentified identifiers. {{should}} be singular.
**'''<code class="class-name">type::</code>''' the class name type identifies the identifier type.
**'''<code class="class-name">value::</code>''' label {{may}} be implied

=== Additional Details ===
'''Note:''' If hProduct markup is used in a "standalone" fashion (eg. a manufacturer site that's not commerce enabled, strictly informational), it is assumed that the price attribute represents the manufacturer's suggested retail price. Any transactional (commerce) representation of price should be delegated to [[hlisting|hListing]].

''Internationalization'': Though there are many English-language tokens, they are only used as invisible class-names; user-visible listing information can be completely localized. Note that (X)HTML LANG attribute rules still apply as usual, for multilingual aggregators of hProduct.

=== Relationships with other microformats ===
Products can be complex structures with attributes and features that may fall outside the bounds of the proposed hProduct microformat. Care has been taken to provide just enough attributes to accurately represent products while not overloading the hProduct spec. This means that complete semantic solutions would rely on using hProduct in combination with other microformats to achieve their goals. Through [[hproduct-examples#Coded_examples|examples]] (see also: [[hproduct-recipes|recipes]]) and [[hproduct-examples#Analysis_of_Product.2FCommerce_Sites|analysis]], there are some clear relationships between hProduct and these microformats:

* [[hlisting|hListing]] :: provides additional context to the transaction side of a product, including elements like the transactional price.
* [[hReview|hReview]]/hAggregate(concept) :: research shows that many commerce sites include product reviews, and they are often aggregated to provide overall ratings and reviews on the web. Utilizing these microformats can provide additional data around a product or service.
* [[xoxo|xoxo]] :: to address property-value data that may be necessary for a complete data representation of a product.

Of course, these are just a few of many that could be used with the hProduct microformat.

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hproduct</dt>
<dd>Used to identify and describe metadata universally common to products.</dd>
<dt>brand</dt>
<dd>The brand name of the product.</dd>
<dt>category</dt>
<dd>The product category/ categories the product belongs to.</dd>
<dt>price</dt>
<dd>The price of the product.</dd>
<dt>description</dt>
<dd>The full text representing the written description of the product.</dd>
<dt>fn</dt>
<dd>The common name of the product.</dd>
<dt>photo</dt>
<dd>Accompanying image of the product.</dd>
<dt>url</dt>
<dd>A link to the product details.</dd>
<dt>review</dt>
<dd>A review of the product.</dd>
<dt>listing</dt>
<dd>Listing details of the product.</dd>
<dt>identifier</dt>
<dd>The product identifier like Model, SKU, ISBN, or EAN associated with the product</dd>
</dl>
</dd>
</dl>
</pre>

=== Notes ===
This section is informative.
*...

=== Other examples ===

Please see examples at [[hproduct-examples|hProduct examples]].

== Copyright ==
* [[User:JayMyers|JayMyers]]: I release all of my contributions to the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

== Related ==
* '''hproduct'''
* [[hproduct-issues]]
* [[hproduct-faq]]
* [[hproduct-examples]]
* [[hproduct-recipes]]

* [[product]]
* [[product-examples]]
* [[product-formats]]
* [[product-brainstorming]]

[[Category:Draft Specifications]]
[[Category:hProduct]]

hproduct

2010-06-17T16:30:28Z

Kavi: /* Schema */

<entry-title>hProduct</entry-title>
{{DraftSpecification}}
__TOC__
hProduct is a microformat suitable for publishing and embedding product data. hProduct is one of several open microformats standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.

==hProduct Microformat Draft Specification==

; Editors/Authors
(alphabetical)
* [[User:PaulLee|Paul Lee]], Google Product Search
* [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

; Contributors
(alphabetical)
* Craig Cook, [http://focalcurve.com/ Focal Curve]
* Aaron Gustafson, [http://easy-designs.net/ Easy! Designs]

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

== Status ==
Draft, version 0.3.

== Introduction ==
The web is a thriving consumer marketplace with a plethora of manufacturers and vendors scattered across the globe. Sifting through massive amounts of unstructured product data is a difficult task for both browsers and machines alike. The hProduct microformat gives structure to this metadata by providing constructs to identify universal product attributes, plus a mechanism to accomodate the wide variation in product attributes.

The hProduct microformat can assist consumers, manufacturers and retailers in a number of ways. If a browser or application understands that a specific web page contains the hProduct microformat, it can inform and help facilitate the best product choice by the consumer to fulfill their needs. An adopted, open standard will ensure the correct product data is published between manufacturers and retailers, to the benefit of the consumer. Bringing order and structure to product data makes it easy for people and organizations to list the products and services they offer, and easy for web services to consume that product data for analysis and syndication.

=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

=== Inspiration and Acknowledgment ===
Many thanks go out to the contributors who laid the foundation for the current hProduct draft spec.

=== Scope ===
Giving details about a particular product is sometimes very complex as parameters are different for books and CDs than they are for iPods or cars. It should be very easy to mark up an item using hProduct and the syntax should be simple yet flexible enough for more advanced applications.

=== Out of Scope ===
This microformat does not intend to replicate any of the content proposed within [[hListing]] and would defer all money/transactional matters to that microformat. This microformat also does not attempt to specify a product ontology, or category-specific attributes; instead, it aims to create a framework to allow for flexible expression of both.

== Format ==
{{rfc-2119-intro}}

=== In General ===
The hProduct format is based on a set of fields common to numerous ecommerce sites and formats in use today on the web.

=== Schema ===
The hProduct schema consists of the following (see existing class names for reference):

*hproduct
** brand. optional. text. can also use [[hcard|hCard]] for manufacturer.
** category. optional. text. can also use rel-tag. re-used from [[hcard|hCard]].
** price. optional. floating point number. can use currency format.
** description. optional. text. can also include valid HTML markup. re-used from [[hreview|hReview]].
** fn. '''required.''' text. product name or title. re-used from [[hcard|hCard]].
** photo. optional. image element or link. re-used from [[hcard|hCard]].
** url. optional. href. can contain rel-tag rel='product'. re-used from [[hcard|hCard]].
** review. optional. [[hreview|hReview]], or [[aggregate-microformat-template-examples|hReview-aggregate]].
** listing. optional. [[hlisting|hListing]], or [[hreview-aggregate|hListing-aggregate]].
** identifier. optional.
*** type. required. - examples:
**** model
**** mpn
**** upc
**** isbn
**** issn
**** ean
**** jan
**** sn
**** vin
**** sku
*** value. required. - label may be implied

=== Field details ===
Class names <code class="class-name">category</code>, <code class="class-name">fn</code>, <code class="class-name">photo</code>, <code class="class-name">url</code> are reused from [[hcard|hCard]]. <code class="class-name">description</code> is reused from [[hreview|hReview]].

The fields of the hProduct schema represent the following:

*'''<code class="class-name">hproduct::</code>''' Root class name
*'''<code class="class-name">brand::</code>''' the class name brand is used identify brand of the product. {{should}} use [[hcard|hCard]] for manufacturer name. {{must}} be singular.
*'''<code class="class-name">category::</code>''' the class name category identifies product category. {{may}} use [[rel-tag]] microformat. {{may}} be plural to represent multiple categories.
*'''<code class="class-name">price::</code>''' the class name price is used to indicate the price of the product. {{must}} be singular.
*'''<code class="class-name">description::</code>''' the class name description is used to describe the product. {{must}} be singular.
*'''<code class="class-name">fn::</code>''' product text name. {{must}} be singular.
*'''<code class="class-name">photo::</code>''' the class name photo {{may}} be applied to an <img> or <a> element. {{may}} be plural.
*'''<code class="class-name">url::</code>''' the class name url {{should}} refer to the web page associated with product details. {{may}} use [[rel-tag]], rel='product'. {{must}} be singular.
*'''<code class="class-name">review::</code>''' the class name review identifies review(s) for the product. {{should}} use [[hreview|hReview]]. {{may}} be plural.
*'''<code class="class-name">listing::</code>''' the class name listing identifies product listings. {{should}} use [[hlisting|hListing]]. {{may}} be plural.
*'''<code class="class-name">identifier::</code>''' the identifier structure is used to describe product identifiers like Model, UPC or SKU, and is designed to accommodate new or as-yet-unidentified identifiers. {{should}} be singular.
**'''<code class="class-name">type::</code>''' the class name type identifies the identifier type.
**'''<code class="class-name">value::</code>''' label {{may}} be implied

=== Additional Details ===
'''Note:''' If hProduct markup is used in a "standalone" fashion (eg. a manufacturer site that's not commerce enabled, strictly informational), it is assumed that the price attribute represents the manufacturer's suggested retail price. Any transactional (commerce) representation of price should be delegated to [[hlisting|hListing]].

''Internationalization'': Though there are many English-language tokens, they are only used as invisible class-names; user-visible listing information can be completely localized. Note that (X)HTML LANG attribute rules still apply as usual, for multilingual aggregators of hProduct.

=== Relationships with other microformats ===
Products can be complex structures with attributes and features that may fall outside the bounds of the proposed hProduct microformat. Care has been taken to provide just enough attributes to accurately represent products while not overloading the hProduct spec. This means that complete semantic solutions would rely on using hProduct in combination with other microformats to achieve their goals. Through [[hproduct-examples#Coded_examples|examples]] (see also: [[hproduct-recipes|recipes]]) and [[hproduct-examples#Analysis_of_Product.2FCommerce_Sites|analysis]], there are some clear relationships between hProduct and these microformats:

* [[hlisting|hListing]] :: provides additional context to the transaction side of a product, including elements like the transactional price.
* [[hReview|hReview]]/hAggregate(concept) :: research shows that many commerce sites include product reviews, and they are often aggregated to provide overall ratings and reviews on the web. Utilizing these microformats can provide additional data around a product or service.
* [[xoxo|xoxo]] :: to address property-value data that may be necessary for a complete data representation of a product.

Of course, these are just a few of many that could be used with the hProduct microformat.

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.</p>
<dl>
<dt>hproduct</dt>
<dd>Used to identify and describe metadata universally common to products.</dd>
<dt>brand</dt>
<dd>The brand name of the product.</dd>
<dt>category</dt>
<dd>The product category/ categories the product belongs to.</dd>
<dt>price</dt>
<dd>The price of the product.</dd>
<dt>description</dt>
<dd>The full text representing the written description of the product.</dd>
<dt>fn</dt>
<dd>The common name of the product.</dd>
<dt>photo</dt>
<dd>Accompanying image of the product.</dd>
<dt>url</dt>
<dd>A link to the product details.</dd>
<dt>review</dt>
<dd>A review of the product.</dd>
<dt>listing</dt>
<dd>Listing details of the product.</dd>
<dt>identifier</dt>
<dd>The product identifier like Model, SKU, ISBN, or EAN associated with the product</dd>
</dl>
</dd>
</dl>
</pre>

=== Notes ===
This section is informative.
*...

=== Other examples ===

Please see examples at [[hproduct-examples|hProduct examples]].

== Copyright ==
* [[User:JayMyers|JayMyers]]: I release all of my contributions to the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

== Related ==
* '''hproduct'''
* [[hproduct-issues]]
* [[hproduct-faq]]
* [[hproduct-examples]]
* [[hproduct-recipes]]

* [[product]]
* [[product-examples]]
* [[product-formats]]
* [[product-brainstorming]]

[[Category:Draft Specifications]]
[[Category:hProduct]]

aggregate-review-brainstorming

2009-12-16T06:34:02Z

Kavi:

Ideas for how to support aggregate reviews via microformats.

== Common themes amongst examples (that we might want to support) ==

* Aggregations of reviews always contain these two elements:
** the number of reviewers
** the average rating

''number of reviewers, really? unique people? what if there's more than one rating per person? Number of ratings would be simpler.''

''Google Rich Snippets makes mistake of assuming that number of ratings equals number of reviews, but users may leave rating without leaving review''

''These are good points -- added a separate section below to discuss ratings vs reviews vs reviewers. Note that the first comment referring to the number of "reviewers" caught a typo -- it should be number of reviews, not reviewers. -- Kavi, Nov 2 2009''

* Other elements that occur in the example set include:
** the number of reviews for each rating (i.e. 10 5-star ratings, 7 4-star ratings, etc)
** recurring themes about the entity being reviewed (i.e. "romantic restaurant" or "love the chicken mole").
** who are the reviewers (i.e. "critics" or "users"). Some sites (i.e. Rotten Tomatoes or GameSpot) have multiple sets of aggregate reviews to cover both critics and users.

* In addition, some elements already present in the hReview schema exist in aggregate reviews as well:
** review summary/description
** most recent date reviewed

== Proposal discussed over IRC ==

==== What is the proposal? ====
* Define a new microformat for aggregate reviews (root class name "hreview-aggregate").
* The format will contain only value (the number of reviews) with a new property "count" and embedded [[hReview]] properties that contains details like the average review score, summary, and a reference to the object of the review.

'''This proposal should be written up on a separate page as a microformats draft, e.g. [[hreview-aggregate]].'''

==== Why was this proposal preferred? ====
* Creating a new uF rather than extending hReview doesn't require branching the spec for hReview and provides clean separation in case we want to extend the new format to include other data in the future
* Supporting only the number of reviews (rather than scores per rating, etc) is probably sufficient for 80% of sites with aggregate reviews.

== Other proposals suggested ==

==== 1) Do nothing. Aggregation must be done by the microformats parser ====
* Pros: Doesn't require any change to the existing microformats definitions
* Cons: Very difficult for parsers. Reviews for a single entity are usually not limited to a single web page (there are typically no more than 5-10 reviews per page), so aggregating this data would require the parser to figure out which pages to crawl to assemble the aggregate scores.

==== 2) Extend existing hReview format to include "reviewcount" ====
* Any hReview that contains a reviewcount field (which denotes the number of reviewers) would implicitly refer to an aggregation of reviews. The rating would correspond to the average rating of all individual reviews, summary/description refer to a summary of overall sentiments from the reviews, date refers to the most recent review's date.
* Pros: very simple addition to the existing microformat
* Cons: Mild overloading of what an hReview contains -- a review can now correspond to a single user's review or an aggregation of user reviews.

==== 3) Define a new microformat type for aggregate reviews ====
* This type could contain the staples -- average review score and number of reviewers -- as well as some of the other sometimes-used features listed in the "common themes" section earlier.
* Pros: robust way to mark up many elements of aggregate review information
* Cons: some redundancy with hReview. Extending hReview might be sufficient

==== 4) Do not use hreview classes in hreview-aggregate ====
* This causes a collision when hreview includes an hcard that contains review aggregates per google specification http://www.google.com/support/webmasters/bin/answer.py?answer=146645 . In that case, the hreview has its own rating, and a second rating imported via the include pattern.
Currently Yelp implements review aggregate as an hreview-aggregate block that include the entire hcard inside it, and the aggregate rating. Importing this hcard from an hreview using the include pattern, imports the rating as well.
* review-aggregate can be included INSIDE hcard block, or can surround that block.
* review-aggregate can point to a '''self contained''' hcard (include pattern):
** Without repeating any of the information in the hcard
** Without including empty links, example <code><a class="item include" href="#my_business_hcard"></a></code>
** Without including links with duplicate redundant information that is part of the hcard, example <code><a class="item include make_me_invisible_to_user" href="#my_business_hcard">Business Name</a></code>
** Without adding listing information, such as the type of listing: <code><span class="type">business</span></code>.
** Without using non-semantic HTML, such as object tag.
* An hreview should be able to safely import an hcard that may contain hreview-aggregate '''without name collitions''' especially the rating tag (using include pattern).
* An hreview should be able to safely import an hcard that may contain nested elements of hreview-aggregate, such as count and average rating, '''without name collitions''' (using include pattern). If this is not possible, pages will have to default to non semantic HTML, and markup that contains a lot of hidden content, making them less accessible.

== Reviews vs ratings ==

Note -- this proposal has been incorporated into the hreview-aggregate draft spec version 0.2 in December 2009.

Adoption of hreview-aggregate has been strong, but one issue that arisen is the notion of reviews vs ratings. The original hreview-aggregate spec as described below uses a single property called "count" to specify the total number of reviews for an item that contributed towards an aggregate review. This works well for a site like Yelp, where the aggregate rating is based on the number of individual user reviews.

However, many sites allow users to provide a rating without actually writing a review. So there should be some way of allowing sites to mark up the number of "ratings" (or "votes") separately from the number of "reviews."

A couple examples of sites that have separate rating counts and review counts:
* Urbanspoon: http://www.urbanspoon.com/r/6/88896/restaurant/Patxis-Chicago-Pizza-Palo-Alto
* Download.com: http://download.cnet.com/Mayura-Chess-Board/3000-7562_4-10525218.html
* Longer list of examples is here: [[aggregate-review-examples#Ratings_without_reviews_examples]]

==== Proposed solution ====

* Add a new property called "votes" to hreview-aggregate.
** Pros: it is simple for webmasters to understand and is consistent with the terminology that many sites actually use (for example: Urbanspoon, Download.com, IMDb). It also doesn't change the interpretation for any site that has already implemented the existing hreview-aggregate spec.
** Cons: it's not completely obvious that "count" means "number of reviews" whereas "votes" means "number of ratings."

==== Alternative options ====

* Add nested sub-properties to the "count" property: "reviews" and "votes"
** Pros: terminology is clearer than the proposed solution above. For backwards compatibility, if users don't specify reviews vs votes, assume they meant reviews by default.
** Cons: in practice, adding additional layers of nesting creates more chances for webmasters to make mistakes. More nesting is also more verbose.

Note that we shouldn't remove the ability for people to mark up the actual number of reviews -- for anyone who wants to read reviews, it's very useful to know how many reviews there are on a page even if there are more votes contributing towards an aggregate rating.

== See Also ==
* Aggregate reviews: [[aggregate-review-examples|examples]] - [[aggregate-review-formats|formats]]
* [[hreview-aggregate]]
* [[hreview|hReview]]

hreview-aggregate

2009-12-10T17:23:07Z

Kavi: Added the "votes" property as well as an example showing its use. Updated version number to 0.2

<entry-title>hReview-aggregate 0.2</entry-title>
{{DraftSpecification}}

[[hreview-aggregate|hReview-aggregate]] is a format for embedding review information (of products, services, businesses, etc). Whereas [[hreview|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: [[User:KaviGoel|Kavi Goel]], Google
; Authors/Contributers (alphabetical): [[User:Tantek|Tantek Çelik]]
: Othar Hansson, Google
: [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

== Introduction ==

Many websites publish reviews using a variety of organization schemes. hReview-aggregate and the similar microformat [[hreview|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|aggregate review brainstorming]] wiki page.

{{rfc-2119-intro}}

=== 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 ('''<code>hreview-aggregate</code>''')
** '''<code>item</code>''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' || '''<code>photo</code>''' ) | '''[[hcard|hCard]]''' (for person or business) | '''[[hcalendar|hCalendar]]''' (for event) | '''[[hproduct|hProduct]]''' (for product)
** '''<code>rating</code>'''. required. fixed point integer [1.0-5.0], with optional alternate '''<code>worst</code>''' (default:1.0) and/or '''<code>best</code>''' (default:5.0), also fixed point integers, and explicit '''<code>average</code>'''.
** '''<code>count</code>'''. optional. non-negative integer.
** '''<code>votes</code>'''. optional. non-negative integer. Note that while <code>count</code> and <code>votes</code> are both marked optional, at least one of the two fields must be specified.
** '''<code>summary</code>'''. 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|hCard]] for a business or person, [[hproduct|hProduct]] for a product, or [[hcalendar|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 property is used to specify the total number of reviews for the product or service.

'''votes''':: This property is used to specify the total number of users who have rated the product or service, contributing to the average rating. For some sites, the number of votes is equal to the number of reviews, so <code>count</code> may be used and this property omitted.

'''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 <code>item</code>, <code>rating</code>, and <code>summary</code> properties are reused from [[hreview|hReview]].

== Examples ==

=== Basic example ===

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

<pre><nowiki>
<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>
</nowiki></pre>

Adding hReview-aggregate markup to this is straightforward:

<pre><nowiki>
<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>
</nowiki></pre>

=== 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.

<pre><nowiki>
<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>
</nowiki></pre>

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

<pre><nowiki>
<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>
</nowiki></pre>

Note that the <code>item</code> and <code>vcard</code> 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.

=== Count vs votes ===

In the examples so far, the <code>count</code> property has been used but not <code>votes</code>. <code>votes</code> is useful when users have rated an item without writing full corresponding reviews. Their vote contributed toward the average rating but not towards the number of reviews available.

Consider this example:

<pre><nowiki>
<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 24 ratings.</span>
<span>5 user reviews:</span>
...
</div>
</nowiki></pre>

Here the example is again, with both <code>count</code> and <code>votes</code> specified where appropriate.

<pre><nowiki>
<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="votes">24</span> ratings.</span>
<span><span class="count">5</span> user reviews:</span>
...
</div>
</nowiki></pre>

== 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]].

* [http://www.thesuggestr.com theSUGGESTR.com] has implemented hReview-aggregate for it's business ratings and reviews.
* Google has implemented support for [http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=146645 hReview-aggregate] via [http://googlewebmastercentral.blogspot.com/2009/05/introducing-rich-snippets.html Rich Snippets].
* [http://local.stv.tv/glasgow/place/restaurant-japanese/10320725-wagamama/ STV Local] uses hreview-aggregate for business ratings, average prices and contact details with hcard
* [http://www.critiki.com Critiki] publishes ratings and reviews of Tiki bars, and uses hReview aggregate for average ratings on their pages, e.g. [http://www.critiki.com/cgi-bin/location.cgi?loc_id=162 overview of The Tonga Room]. (as [http://twitter.com/humuhumu/status/4165014155 tweeted by humuhumu] 2009-09-21)
* [http://free.naplesplus.us NAPLESPLUS] is an example of a website that has implemented hreview-aggregate via Google specs.
* ...

== Related Pages ==

* [[hreview|hReview]] - microformat for marking up individual reviews
* [[aggregate-review-brainstorming|Aggregate review brainstorming]] - discussions leading to the creation of hReview-aggregate and ideas for improvement.
* [[aggregate-review-examples|Aggregate review examples]]

[[Category:Draft Specifications]]
[[Category:hReview-aggregate]]

hreview-aggregate

2009-12-10T17:21:02Z

Kavi: /* Examples */

<entry-title>hReview-aggregate 0.1</entry-title>
{{DraftSpecification}}

[[hreview-aggregate|hReview-aggregate]] is a format for embedding review information (of products, services, businesses, etc). Whereas [[hreview|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: [[User:KaviGoel|Kavi Goel]], Google
; Authors/Contributers (alphabetical): [[User:Tantek|Tantek Çelik]]
: Othar Hansson, Google
: [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

== Introduction ==

Many websites publish reviews using a variety of organization schemes. hReview-aggregate and the similar microformat [[hreview|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|aggregate review brainstorming]] wiki page.

{{rfc-2119-intro}}

=== 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 ('''<code>hreview-aggregate</code>''')
** '''<code>item</code>''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' || '''<code>photo</code>''' ) | '''[[hcard|hCard]]''' (for person or business) | '''[[hcalendar|hCalendar]]''' (for event) | '''[[hproduct|hProduct]]''' (for product)
** '''<code>rating</code>'''. required. fixed point integer [1.0-5.0], with optional alternate '''<code>worst</code>''' (default:1.0) and/or '''<code>best</code>''' (default:5.0), also fixed point integers, and explicit '''<code>average</code>'''.
** '''<code>count</code>'''. optional. non-negative integer.
** '''<code>votes</code>'''. optional. non-negative integer. Note that while <code>count</code> and <code>votes</code> are both marked optional, at least one of the two fields must be specified.
** '''<code>summary</code>'''. 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|hCard]] for a business or person, [[hproduct|hProduct]] for a product, or [[hcalendar|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 property is used to specify the total number of reviews for the product or service.

'''votes''':: This property is used to specify the total number of users who have rated the product or service, contributing to the average rating. For some sites, the number of votes is equal to the number of reviews, so <code>count</code> may be used and this property omitted.

'''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 <code>item</code>, <code>rating</code>, and <code>summary</code> properties are reused from [[hreview|hReview]].

== Examples ==

=== Basic example ===

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

<pre><nowiki>
<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>
</nowiki></pre>

Adding hReview-aggregate markup to this is straightforward:

<pre><nowiki>
<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>
</nowiki></pre>

=== 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.

<pre><nowiki>
<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>
</nowiki></pre>

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

<pre><nowiki>
<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>
</nowiki></pre>

Note that the <code>item</code> and <code>vcard</code> 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.

=== Count vs votes ===

In the examples so far, the <code>count</code> property has been used but not <code>votes</code>. <code>votes</code> is useful when users have rated an item without writing full corresponding reviews. Their vote contributed toward the average rating but not towards the number of reviews available.

Consider this example:

<pre><nowiki>
<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 24 ratings.</span>
<span>5 user reviews:</span>
...
</div>
</nowiki></pre>

Here the example is again, with both <code>count</code> and <code>votes</code> specified where appropriate.

<pre><nowiki>
<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="votes">24</span> ratings.</span>
<span><span class="count">5</span> user reviews:</span>
...
</div>
</nowiki></pre>

== 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]].

* [http://www.thesuggestr.com theSUGGESTR.com] has implemented hReview-aggregate for it's business ratings and reviews.
* Google has implemented support for [http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=146645 hReview-aggregate] via [http://googlewebmastercentral.blogspot.com/2009/05/introducing-rich-snippets.html Rich Snippets].
* [http://local.stv.tv/glasgow/place/restaurant-japanese/10320725-wagamama/ STV Local] uses hreview-aggregate for business ratings, average prices and contact details with hcard
* [http://www.critiki.com Critiki] publishes ratings and reviews of Tiki bars, and uses hReview aggregate for average ratings on their pages, e.g. [http://www.critiki.com/cgi-bin/location.cgi?loc_id=162 overview of The Tonga Room]. (as [http://twitter.com/humuhumu/status/4165014155 tweeted by humuhumu] 2009-09-21)
* [http://free.naplesplus.us NAPLESPLUS] is an example of a website that has implemented hreview-aggregate via Google specs.
* ...

== Related Pages ==

* [[hreview|hReview]] - microformat for marking up individual reviews
* [[aggregate-review-brainstorming|Aggregate review brainstorming]] - discussions leading to the creation of hReview-aggregate and ideas for improvement.
* [[aggregate-review-examples|Aggregate review examples]]

[[Category:Draft Specifications]]
[[Category:hReview-aggregate]]

hreview-aggregate

2009-12-10T17:09:00Z

Kavi: /* Format */

<entry-title>hReview-aggregate 0.1</entry-title>
{{DraftSpecification}}

[[hreview-aggregate|hReview-aggregate]] is a format for embedding review information (of products, services, businesses, etc). Whereas [[hreview|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: [[User:KaviGoel|Kavi Goel]], Google
; Authors/Contributers (alphabetical): [[User:Tantek|Tantek Çelik]]
: Othar Hansson, Google
: [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

== Introduction ==

Many websites publish reviews using a variety of organization schemes. hReview-aggregate and the similar microformat [[hreview|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|aggregate review brainstorming]] wiki page.

{{rfc-2119-intro}}

=== 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 ('''<code>hreview-aggregate</code>''')
** '''<code>item</code>''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' || '''<code>photo</code>''' ) | '''[[hcard|hCard]]''' (for person or business) | '''[[hcalendar|hCalendar]]''' (for event) | '''[[hproduct|hProduct]]''' (for product)
** '''<code>rating</code>'''. required. fixed point integer [1.0-5.0], with optional alternate '''<code>worst</code>''' (default:1.0) and/or '''<code>best</code>''' (default:5.0), also fixed point integers, and explicit '''<code>average</code>'''.
** '''<code>count</code>'''. optional. non-negative integer.
** '''<code>votes</code>'''. optional. non-negative integer. Note that while <code>count</code> and <code>votes</code> are both marked optional, at least one of the two fields must be specified.
** '''<code>summary</code>'''. 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|hCard]] for a business or person, [[hproduct|hProduct]] for a product, or [[hcalendar|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 property is used to specify the total number of reviews for the product or service.

'''votes''':: This property is used to specify the total number of users who have rated the product or service, contributing to the average rating. For some sites, the number of votes is equal to the number of reviews, so <code>count</code> may be used and this property omitted.

'''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 <code>item</code>, <code>rating</code>, and <code>summary</code> properties are reused from [[hreview|hReview]].

== Examples ==

=== Basic example ===

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

<pre><nowiki>
<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>
</nowiki></pre>

Adding hReview-aggregate markup to this is straightforward:

<pre><nowiki>
<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>
</nowiki></pre>

=== 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.

<pre><nowiki>
<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>
</nowiki></pre>

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

<pre><nowiki>
<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>
</nowiki></pre>

Note that the <code>item</code> and <code>vcard</code> 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]].

* [http://www.thesuggestr.com theSUGGESTR.com] has implemented hReview-aggregate for it's business ratings and reviews.
* Google has implemented support for [http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=146645 hReview-aggregate] via [http://googlewebmastercentral.blogspot.com/2009/05/introducing-rich-snippets.html Rich Snippets].
* [http://local.stv.tv/glasgow/place/restaurant-japanese/10320725-wagamama/ STV Local] uses hreview-aggregate for business ratings, average prices and contact details with hcard
* [http://www.critiki.com Critiki] publishes ratings and reviews of Tiki bars, and uses hReview aggregate for average ratings on their pages, e.g. [http://www.critiki.com/cgi-bin/location.cgi?loc_id=162 overview of The Tonga Room]. (as [http://twitter.com/humuhumu/status/4165014155 tweeted by humuhumu] 2009-09-21)
* [http://free.naplesplus.us NAPLESPLUS] is an example of a website that has implemented hreview-aggregate via Google specs.
* ...

== Related Pages ==

* [[hreview|hReview]] - microformat for marking up individual reviews
* [[aggregate-review-brainstorming|Aggregate review brainstorming]] - discussions leading to the creation of hReview-aggregate and ideas for improvement.
* [[aggregate-review-examples|Aggregate review examples]]

[[Category:Draft Specifications]]
[[Category:hReview-aggregate]]

aggregate-review-brainstorming

2009-11-23T18:50:13Z

Kavi: /* Reviews vs ratings */

Ideas for how to support aggregate reviews via microformats.

== Common themes amongst examples (that we might want to support) ==

* Aggregations of reviews always contain these two elements:
** the number of reviewers
** the average rating

''number of reviewers, really? unique people? what if there's more than one rating per person? Number of ratings would be simpler.''

''Google Rich Snippets makes mistake of assuming that number of ratings equals number of reviews, but users may leave rating without leaving review''

''These are good points -- added a separate section below to discuss ratings vs reviews vs reviewers. Note that the first comment referring to the number of "reviewers" caught a typo -- it should be number of reviews, not reviewers. -- Kavi, Nov 2 2009''

* Other elements that occur in the example set include:
** the number of reviews for each rating (i.e. 10 5-star ratings, 7 4-star ratings, etc)
** recurring themes about the entity being reviewed (i.e. "romantic restaurant" or "love the chicken mole").
** who are the reviewers (i.e. "critics" or "users"). Some sites (i.e. Rotten Tomatoes or GameSpot) have multiple sets of aggregate reviews to cover both critics and users.

* In addition, some elements already present in the hReview schema exist in aggregate reviews as well:
** review summary/description
** most recent date reviewed

== Proposal discussed over IRC ==

==== What is the proposal? ====
* Define a new microformat for aggregate reviews (root class name "hreview-aggregate").
* The format will contain only value (the number of reviews) with a new property "count" and embedded [[hReview]] properties that contains details like the average review score, summary, and a reference to the object of the review.

'''This proposal should be written up on a separate page as a microformats draft, e.g. [[hreview-aggregate]].'''

==== Why was this proposal preferred? ====
* Creating a new uF rather than extending hReview doesn't require branching the spec for hReview and provides clean separation in case we want to extend the new format to include other data in the future
* Supporting only the number of reviews (rather than scores per rating, etc) is probably sufficient for 80% of sites with aggregate reviews.

== Other proposals suggested ==

==== 1) Do nothing. Aggregation must be done by the microformats parser ====
* Pros: Doesn't require any change to the existing microformats definitions
* Cons: Very difficult for parsers. Reviews for a single entity are usually not limited to a single web page (there are typically no more than 5-10 reviews per page), so aggregating this data would require the parser to figure out which pages to crawl to assemble the aggregate scores.

==== 2) Extend existing hReview format to include "reviewcount" ====
* Any hReview that contains a reviewcount field (which denotes the number of reviewers) would implicitly refer to an aggregation of reviews. The rating would correspond to the average rating of all individual reviews, summary/description refer to a summary of overall sentiments from the reviews, date refers to the most recent review's date.
* Pros: very simple addition to the existing microformat
* Cons: Mild overloading of what an hReview contains -- a review can now correspond to a single user's review or an aggregation of user reviews.

==== 3) Define a new microformat type for aggregate reviews ====
* This type could contain the staples -- average review score and number of reviewers -- as well as some of the other sometimes-used features listed in the "common themes" section earlier.
* Pros: robust way to mark up many elements of aggregate review information
* Cons: some redundancy with hReview. Extending hReview might be sufficient

==== 4) Do not use hreview classes in hreview-aggregate ====
* This causes a collision when hreview includes an hcard that contains review aggregates per google specification http://www.google.com/support/webmasters/bin/answer.py?answer=146645 . In that case, the hreview has its own rating, and a second rating imported via the include pattern.
Currently Yelp implements review aggregate as an hreview-aggregate block that include the entire hcard inside it, and the aggregate rating. Importing this hcard from an hreview using the include pattern, imports the rating as well.
* review-aggregate can be included INSIDE hcard block, or can surround that block.
* review-aggregate can point to a '''self contained''' hcard (include pattern):
** Without repeating any of the information in the hcard
** Without including empty links, example <code><a class="item include" href="#my_business_hcard"></a></code>
** Without including links with duplicate redundant information that is part of the hcard, example <code><a class="item include make_me_invisible_to_user" href="#my_business_hcard">Business Name</a></code>
** Without adding listing information, such as the type of listing: <code><span class="type">business</span></code>.
** Without using non-semantic HTML, such as object tag.
* An hreview should be able to safely import an hcard that may contain hreview-aggregate '''without name collitions''' especially the rating tag (using include pattern).
* An hreview should be able to safely import an hcard that may contain nested elements of hreview-aggregate, such as count and average rating, '''without name collitions''' (using include pattern). If this is not possible, pages will have to default to non semantic HTML, and markup that contains a lot of hidden content, making them less accessible.

== Reviews vs ratings ==

Section added Nov 2009

Adoption of hreview-aggregate has been strong, but one issue that arisen is the notion of reviews vs ratings. The original hreview-aggregate spec as described below uses a single property called "count" to specify the total number of reviews for an item that contributed towards an aggregate review. This works well for a site like Yelp, where the aggregate rating is based on the number of individual user reviews.

However, many sites allow users to provide a rating without actually writing a review. So there should be some way of allowing sites to mark up the number of "ratings" (or "votes") separately from the number of "reviews."

A couple examples of sites that have separate rating counts and review counts:
* Urbanspoon: http://www.urbanspoon.com/r/6/88896/restaurant/Patxis-Chicago-Pizza-Palo-Alto
* Download.com: http://download.cnet.com/Mayura-Chess-Board/3000-7562_4-10525218.html
* Longer list of examples is here: [[aggregate-review-examples#Ratings_without_reviews_examples]]

==== Proposed solution ====

* Add a new property called "votes" to hreview-aggregate.
** Pros: it is simple for webmasters to understand and is consistent with the terminology that many sites actually use (for example: Urbanspoon, Download.com, IMDb). It also doesn't change the interpretation for any site that has already implemented the existing hreview-aggregate spec.
** Cons: it's not completely obvious that "count" means "number of reviews" whereas "votes" means "number of ratings."

==== Alternative options ====

* Add nested sub-properties to the "count" property: "reviews" and "votes"
** Pros: terminology is clearer than the proposed solution above. For backwards compatibility, if users don't specify reviews vs votes, assume they meant reviews by default.
** Cons: in practice, adding additional layers of nesting creates more chances for webmasters to make mistakes. More nesting is also more verbose.

Note that we shouldn't remove the ability for people to mark up the actual number of reviews -- for anyone who wants to read reviews, it's very useful to know how many reviews there are on a page even if there are more votes contributing towards an aggregate rating.

== See Also ==
* Aggregate reviews: [[aggregate-review-examples|examples]] - [[aggregate-review-formats|formats]]
* [[hreview-aggregate]]
* [[hreview|hReview]]

aggregate-review-examples

2009-11-21T02:54:08Z

Kavi: /* Ratings without reviews examples */

== The Problem ==
''There are various services that provide aggregate ratings and reviews on the Web. How should this information be presented in microformat form? hReview is oriented towards individual reviews with ratings; can it also be used for presenting data from aggregate reviews?''
== Participants ==
* John Panzer
* Kavi Goel
* Jay Myers

== Real-World Examples ==
''Links to public web pages, either popular or insightful''

=== Amazon ===
* http://www.amazon.com/gp/product/B001FA1NFA/
* Aggregation of user reviews for a product. Up to 10 reviews per page
* Includes 1-5 stars average rating and the total number of reviews
* Also includes number of reviews for each score (1-5)

=== Bizrate ===
* Aggregation of user reviews for a product. Up to 10 reviews per page
* Includes 1-5 stars average rating and the total number of reviews

=== Citysearch ===
* http://siliconvalley.citysearch.com/profile/11636582/mountain_view_ca/vive_sol.html
* Shows 1-5 stars average rating and the total number of reviews on the "business info" page
* On the "reviews" page, it also includes the number of reviews for each score (1-5) and some themes from the reviews (i.e. "Prompt seating", "Romantic", "Good for groups")

=== CNet Reviews ===
* http://reviews.cnet.com/car-gps-navigation/garmin-nuvi-880/4505-3430_7-32815498.html
* Shows both editors rating (1-5 stars as well as a word describing the rating, i.e. "Excellent") and the average user rating (1-5 stars) and total number of user reviews
* Only shows editor's review and 3 user reviews on first page for a product.
* Clicking through shows 5 reviews per page.

=== Download.com ===
* http://www.download.com/Ad-Aware-2008/3000-8022_4-10045910.html
* Shows both editors rating (1-5 stars) and the average user rating (1-5 stars) and total number of votes
* 5 user reviews shown per page

=== Rotten Tomatoes ===
* http://www.rottentomatoes.com/m/quantum_of_solace/
* Shows percentage of positive reviews from users (in this case, users = movie critics) and number of reviews
* An average rating (between 1 and 10) is also shown, but this data is de-emphasized on the Rotten Tomatoes movies pages.

=== Yelp ===
* http://www.yelp.com/biz/vive-sol-restaurant-mountain-view
* Shows 1-5 stars average rating and the total number of reviews
* Also includes number of reviews for each score (1-5)
* The site highlights recurring themes from reviews (i.e. "The food is delicious - love the chicken mole.") and the number of reviews where such comments were made.

== Ratings without reviews examples ==

This section added Nov 2009.

Some sites allow users to rate an object without providing a written review. These ratings can be numerical ratings (i.e. 1-5 stars) or votes (thumbs up/thumbs down). Aggregate ratings are calculated using all ratings or "votes" though the number of reviews available is smaller. The following are example sites that have separate numbers of user ratings vs full reviews.

=== Download.com ===
* http://www.download.com/Ad-Aware-2008/3000-8022_4-10045910.html
* Download.com explicitly specifies the number of user ratings as well as the number of reviews (though the review count is less prominent). Ratings are on a 5-point scale and Download.com uses the term "votes."

=== Gamespot ===
* http://www.gamespot.com/xbox360/rpg/masseffect/index.html
* Gamespot uses both "reviews" and "votes" in their aggregate reviews. In the Critic Score section, they show the number of reviews, whereas in the User Score section they show "votes." If you click through on the votes link, you can see the number of player reviews (which, as expected, is much lower than the number of player reviews).

=== IGN ===
* http://xbox360.ign.com/objects/718/718963.html
* IGN shows the number of user ratings but not the number of reviews. Ratings are on a 10-point scale, and they use the term "ratings."

=== IMDb ===
* http://www.imdb.com/title/tt0258000/
* IMDb explicilty writes the number of user ratings, provided on a 10-point scale. There are no reviews per se, but user comments on movie pages are often actually reviews. IMDb uses the term "votes."

=== Metromix ===
* http://chicago.metromix.com/restaurants/mexican/rustico-grill-logan-square/1361373/content
* Metromix writes the number of user ratings but not the number of user reviews (though user reviews exist on the page). Ratings are on a 5-point scale, and Metromix uses the term "ratings."

=== Urbanspoon ===
* http://www.urbanspoon.com/r/3/39999/restaurant/West-Village/Spotted-Pig-New-York
* Urbanspoon explicitly writes the number of user ratings as well as the number of reviews (though the review count is less prominent on the page). Urbanspoon uses a binary scale (like it/don't like it) and uses the term "votes."

Overall, "votes" seems to be the most common term used for the number of user ratings when provided without reviews. This is true even when the rating scale is not binary (i.e. 5-point scale or 10-point scale), though the term "ratings" is also used commonly.

== Coded examples ==

(Note: examples may contain additional markup for positioning and presentation purposes to simulate live production markup)

=== aggregate reviews embedded in hproduct block ===
<pre><nowiki>
<div class="hproduct">
<ol class="clearfloat" id="breadcrumbs">
<li><a href="http://www.yoursite.com">Home</a></li>
<li class="category"><a href="http://www.yoursite.com/computers/">Computers</a></li>
<li class="category"><a href="http://www.yoursite.com/computers/networking/">Networking</a></li>
<li class="category"><a href="http://www.yoursite.com/computers/networking/print-servers">Print Servers</a></li>
</ol>
<h1 class="n">NETGEAR 802.11g Wireless USB Print Server with 4-Port Switch</h1>
<div id="topbox">
<div class="rightcol">
<img src="http://images.yoursite.com/images/products/7250/7250707_rb.jpg" alt="Image of NETGEAR WGPS606" class="photo" />
</div>
<div class="leftcol">
<div class="infomain">
<ul>
<li>
<strong>Brand: </strong><span class="brand">NETGEAR</span>
</li>
<li>
<strong>Model: </strong><span class="model">WGPS606</span>
</li>
<li class="identifier">
<span class="type">SKU: </span><span class="value">7250707</span>
</li>
</ul>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://images.yoursite.com/path/to/product" class="url"><img src="http://images.yoursite.com/images/misc/ratings_star_3_5.gif" alt="3.5 out of 5 stars"/></a></span><span class="rating">4.7</span> / <span class="best">5</span> (<span class="num">13</span> reviews)</div>
</div>
</div>
<p class="description">
Share a USB printer with others on your network; up to 54 Mbps; 2 USB ports; wireless Ethernet bridge mode with 4-port switch
</p>
<p>
<span class="availability online">Available online</span>. <span class="shipping">Shipping: Usually leaves our warehouse in 1 business day. <span class="money">Estimated shipping cost: <abbr class="currency" title="USD" lang="en">$</abbr><span class="amount">6.99</span>.</span></span>

</p>
<p>
<span class="availability instore">Available in our stores</span>. Store Pickup: Available at most stores
</p>
<p>
<span class="availability specialorder">Not available for special order</span>.
</p>
</div>
<div class="infoside">
<span class="price regular"><span class="money"><strong>Price: </strong><abbr class="currency" title="USD" lang="en">$</abbr><span class="amount">99.99</span></span></span>
<div>
<a href="http://images.yoursite.com/path/to/buy/product" class="buy"><img src="http://images.yoursite.com/images/btn_add_to_cart.gif" alt="buy this product" /></a>
</div>
</div>
</div>
</div>

</nowiki></pre>

=== hlisting, hproduct, haggregatereview/hreview, xoxo ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/tv-and-video">TV & Video</a></li>
<li class="category"><a href="http://storename.com/televisions">Televisions</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/samsung-ln40a550.jpg" class="photo" alt="picture of samsung ln40a550" />
<div class="fn"><span class="brand">Samsung</span> - 40" 1080p Flat-Panel LCD HDTV</div>
<dl class="identifier">
<dt>Model</dt>
<dd>LN40A550</dd>
<dt>SKU</dt>
<dd>8749465</dd>
</dl>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_3_5.gif" alt="3.5 out of 5 stars"/></a></span><span class="rating">4.7</span> / <span class="best">5</span> (<span class="num">13</span> reviews)</div>
</div>
</div>
<div class="price">$1,099.99</div>
<ol class="xoxo">
<li><h2>Specifications</h2>
<dl>
<dt>Warranty Terms - Parts</dt>
<dd>1 year</dd>
<dt>Warranty Terms - Labor</dt>
<dd>1 year</dd>
<dt>Product Height</dt>
<dd>27" with stand (24-7/10" without)</dd>
<dt>Product Width</dt>
<dd>39-1/5"</dd>
<dt>Product Weight</dt>
<dd>61.5 lbs. with stand (54.5 lbs. without)</dd>
<dt>Product Depth</dt>
<dd>11-4/5" with stand (3-3/5" without)</dd>
<dt>TV Type</dt>
<dd>LCD Flat-Panel</dd>
</dl>
</li>
</div>
</div>
</nowiki></pre>

=== hlisting, hproduct, haudio, haggregatereview/hreview ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct haudio">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/gangsta">Gangsta/Hardcore</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/50cent-curtis.jpg" class="photo" alt="picture of 50 cent" />
<div class="album">Curtis</div>
<div class="contributor"><span class="vcard"><span class=n nickname">50 Cent</span></span></div>
<p>Release date:<abbr class="published" title="2007-09-11">September 11, 2007</abbr></p>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_4_0.gif" alt="4 out of 5 stars"/></a></span><span class="rating">4.0</span> / <span class="best">5</span> Number of reviews:(<span class="num">4</span> reviews)</div>
</div>
<div class="price">$9.99</div>
<a href="add-to-cart-url" rel="payment"><img src="http://storename.com/images/global/add-to-cart.gif" alt="add to cart" /></a>
<h2>Tracks</h2>
<ol>
<li class="item"><span class="position">1</span>.<span class="fn">Intro</span><a href="http://images.storename.com/media/sample/50cent-intro.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">2</span>.<span class="fn">My Gun Go Off</span><a href="http://images.storename.com/media/sample/50cent-gun-go-off.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">3</span>.<span class="fn">Man Down - (censored)</span><a href="http://images.storename.com/media/sample/50cent-man-down.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">4</span>.<span class="fn">I'll Still Kill - (with Akon)</span><a href="http://images.storename.com/media/sample/50cent-ill-still-kill.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">5</span>.<span class="fn">I Get Money</span><a href="http://images.storename.com/media/sample/50cent-i-get-money.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">6</span>.<span class="fn">Come & Go - (with Dr. Dre)</span><a href="http://images.storename.com/media/sample/50cent-come-go.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">7</span>.<span class="fn">Ayo Technology - (with Timbaland/Justin Timberlake)</span><a href="http://images.storename.com/media/sample/50cent-ayo-technology.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">8</span>.<span class="fn">Follow My Lead - (with Robin Thicke)</span><a href="http://images.storename.com/media/sample/50cent-follow-my-lead.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">9</span>.<span class="fn">Movin' on Up</span><a href="http://images.storename.com/media/sample/50cent-movin-on-up.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">10</span>.<span class="fn">Straight to the Bank</span><a href="http://images.storename.com/media/sample/50cent-straight-to-bank.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">11</span>.<span class="fn">Amusement Park</span><a href="http://images.storename.com/media/sample/50cent-amusement-park.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">12</span>.<span class="fn">Fully Loaded Clip</span><a href="http://images.storename.com/media/sample/50cent-fully-loaded-clip.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">13</span>.<span class="fn">Peep Show - (with Eminem)</span><a href="http://images.storename.com/media/sample/50cent-peep-show.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">14</span>.<span class="fn">Fire - (with Young Buck/Nicole Scherzinger)</span><a href="http://images.storename.com/media/sample/50cent-fire.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">15</span>.<span class="fn">All of Me - (with Mary J. Blige)</span><a href="http://images.storename.com/media/sample/50cent-all-of-me.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">16</span>.<span class="fn">Curtis 187</span><a href="http://images.storename.com/media/sample/50cent-curtis-187.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">17</span>.<span class="fn">Touch the Sky - (with Tony Yayo)</span><a href="http://images.storename.com/media/sample/50cent-touch-the-sky.mp3" rel="sample">Listen</a></li>
</ol>
</div>
</div>
</nowiki></pre>

== Existing Practices ==
* ''Summary of common patterns discovered''
* ''Other attempts to solve The Problem''

== Proposal ==
* Early drafts
* ''Link to related pages as they become available''
* I think that this page from email discussion actually is a non-example: http://webcenter.polls.aol.com/poll?view=69043&pollId=69096 ; it's actually aggregate rankings with numerical weightings, which might lead to an interesting hRanking microformat but I think is out of bounds for an 'aggregate review' discussion.
** -brainstorming
** - proposal
** -microformat

== See Also ==
* Aggregation of microformats: [[aggregate-microformat-template-examples|examples]] - [[aggregate-microformat-template-formats|formats]] - [[aggregate-microformat-template-brainstorming|brainstorming]]
* Aggregate review: [[aggregate-review-formats|formats]] - [[aggregate-review-brainstorming|brainstorming]]
* [[hreview-aggregate]]
* [[review-examples]] for examples of individual reviews
* [[hreview|hReview]]
* ''Normative references for tags used''

aggregate-review-examples

2009-11-21T02:51:06Z

Kavi: /* Ratings without reviews examples */

== The Problem ==
''There are various services that provide aggregate ratings and reviews on the Web. How should this information be presented in microformat form? hReview is oriented towards individual reviews with ratings; can it also be used for presenting data from aggregate reviews?''
== Participants ==
* John Panzer
* Kavi Goel
* Jay Myers

== Real-World Examples ==
''Links to public web pages, either popular or insightful''

=== Amazon ===
* http://www.amazon.com/gp/product/B001FA1NFA/
* Aggregation of user reviews for a product. Up to 10 reviews per page
* Includes 1-5 stars average rating and the total number of reviews
* Also includes number of reviews for each score (1-5)

=== Bizrate ===
* Aggregation of user reviews for a product. Up to 10 reviews per page
* Includes 1-5 stars average rating and the total number of reviews

=== Citysearch ===
* http://siliconvalley.citysearch.com/profile/11636582/mountain_view_ca/vive_sol.html
* Shows 1-5 stars average rating and the total number of reviews on the "business info" page
* On the "reviews" page, it also includes the number of reviews for each score (1-5) and some themes from the reviews (i.e. "Prompt seating", "Romantic", "Good for groups")

=== CNet Reviews ===
* http://reviews.cnet.com/car-gps-navigation/garmin-nuvi-880/4505-3430_7-32815498.html
* Shows both editors rating (1-5 stars as well as a word describing the rating, i.e. "Excellent") and the average user rating (1-5 stars) and total number of user reviews
* Only shows editor's review and 3 user reviews on first page for a product.
* Clicking through shows 5 reviews per page.

=== Download.com ===
* http://www.download.com/Ad-Aware-2008/3000-8022_4-10045910.html
* Shows both editors rating (1-5 stars) and the average user rating (1-5 stars) and total number of votes
* 5 user reviews shown per page

=== Rotten Tomatoes ===
* http://www.rottentomatoes.com/m/quantum_of_solace/
* Shows percentage of positive reviews from users (in this case, users = movie critics) and number of reviews
* An average rating (between 1 and 10) is also shown, but this data is de-emphasized on the Rotten Tomatoes movies pages.

=== Yelp ===
* http://www.yelp.com/biz/vive-sol-restaurant-mountain-view
* Shows 1-5 stars average rating and the total number of reviews
* Also includes number of reviews for each score (1-5)
* The site highlights recurring themes from reviews (i.e. "The food is delicious - love the chicken mole.") and the number of reviews where such comments were made.

== Ratings without reviews examples ==

This section added Nov 2009.

Some sites allow users to rate an object without providing a written review. These ratings can be numerical ratings (i.e. 1-5 stars) or votes (thumbs up/thumbs down). Aggregate ratings are calculated using all ratings or "votes" though the number of reviews available is smaller. The following are example sites that have separate numbers of user ratings vs full reviews.

=== Download.com ===
* http://www.download.com/Ad-Aware-2008/3000-8022_4-10045910.html
* Download.com explicitly specifies the number of user ratings as well as the number of reviews (though the review count is less prominent). Ratings are on a 5-point scale and Download.com uses the term "votes."

=== Gamespot ===
* http://www.gamespot.com/xbox360/rpg/masseffect/index.html
* Gamespot uses both "reviews" and "votes" in their aggregate reviews. In the Critic Score section, they show the number of reviews, whereas in the User Score section they show "votes." If you click through on the votes link, you can see the number of player reviews (which, as expected, is much lower than the number of player reviews).

=== IGN ===
* http://xbox360.ign.com/objects/718/718963.html
* IGN shows the number of user ratings but not the number of reviews. Ratings are on a 10-point scale, and they use the term "ratings."

=== IMDb ===
* http://www.imdb.com/title/tt0258000/
* IMDb explicilty writes the number of user ratings, provided on a 10-point scale. There are no reviews per se, but user comments on movie pages are often actually reviews. IMDb uses the term "votes."

=== Metromix ===
* http://chicago.metromix.com/restaurants/mexican/rustico-grill-logan-square/1361373/content
* Metromix writes the number of user ratings but not the number of user reviews (though user reviews exist on the page). Ratings are on a 5-point scale, and Metromix uses the term "ratings."

=== Urbanspoon ===
* http://www.urbanspoon.com/r/3/39999/restaurant/West-Village/Spotted-Pig-New-York
* Urbanspoon explicitly writes the number of user ratings as well as the number of reviews (though the review count is less prominent on the page). Urbanspoon uses a binary scale (like it/don't like it) and uses the term "votes."

== Coded examples ==

(Note: examples may contain additional markup for positioning and presentation purposes to simulate live production markup)

=== aggregate reviews embedded in hproduct block ===
<pre><nowiki>
<div class="hproduct">
<ol class="clearfloat" id="breadcrumbs">
<li><a href="http://www.yoursite.com">Home</a></li>
<li class="category"><a href="http://www.yoursite.com/computers/">Computers</a></li>
<li class="category"><a href="http://www.yoursite.com/computers/networking/">Networking</a></li>
<li class="category"><a href="http://www.yoursite.com/computers/networking/print-servers">Print Servers</a></li>
</ol>
<h1 class="n">NETGEAR 802.11g Wireless USB Print Server with 4-Port Switch</h1>
<div id="topbox">
<div class="rightcol">
<img src="http://images.yoursite.com/images/products/7250/7250707_rb.jpg" alt="Image of NETGEAR WGPS606" class="photo" />
</div>
<div class="leftcol">
<div class="infomain">
<ul>
<li>
<strong>Brand: </strong><span class="brand">NETGEAR</span>
</li>
<li>
<strong>Model: </strong><span class="model">WGPS606</span>
</li>
<li class="identifier">
<span class="type">SKU: </span><span class="value">7250707</span>
</li>
</ul>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://images.yoursite.com/path/to/product" class="url"><img src="http://images.yoursite.com/images/misc/ratings_star_3_5.gif" alt="3.5 out of 5 stars"/></a></span><span class="rating">4.7</span> / <span class="best">5</span> (<span class="num">13</span> reviews)</div>
</div>
</div>
<p class="description">
Share a USB printer with others on your network; up to 54 Mbps; 2 USB ports; wireless Ethernet bridge mode with 4-port switch
</p>
<p>
<span class="availability online">Available online</span>. <span class="shipping">Shipping: Usually leaves our warehouse in 1 business day. <span class="money">Estimated shipping cost: <abbr class="currency" title="USD" lang="en">$</abbr><span class="amount">6.99</span>.</span></span>

</p>
<p>
<span class="availability instore">Available in our stores</span>. Store Pickup: Available at most stores
</p>
<p>
<span class="availability specialorder">Not available for special order</span>.
</p>
</div>
<div class="infoside">
<span class="price regular"><span class="money"><strong>Price: </strong><abbr class="currency" title="USD" lang="en">$</abbr><span class="amount">99.99</span></span></span>
<div>
<a href="http://images.yoursite.com/path/to/buy/product" class="buy"><img src="http://images.yoursite.com/images/btn_add_to_cart.gif" alt="buy this product" /></a>
</div>
</div>
</div>
</div>

</nowiki></pre>

=== hlisting, hproduct, haggregatereview/hreview, xoxo ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/tv-and-video">TV & Video</a></li>
<li class="category"><a href="http://storename.com/televisions">Televisions</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/samsung-ln40a550.jpg" class="photo" alt="picture of samsung ln40a550" />
<div class="fn"><span class="brand">Samsung</span> - 40" 1080p Flat-Panel LCD HDTV</div>
<dl class="identifier">
<dt>Model</dt>
<dd>LN40A550</dd>
<dt>SKU</dt>
<dd>8749465</dd>
</dl>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_3_5.gif" alt="3.5 out of 5 stars"/></a></span><span class="rating">4.7</span> / <span class="best">5</span> (<span class="num">13</span> reviews)</div>
</div>
</div>
<div class="price">$1,099.99</div>
<ol class="xoxo">
<li><h2>Specifications</h2>
<dl>
<dt>Warranty Terms - Parts</dt>
<dd>1 year</dd>
<dt>Warranty Terms - Labor</dt>
<dd>1 year</dd>
<dt>Product Height</dt>
<dd>27" with stand (24-7/10" without)</dd>
<dt>Product Width</dt>
<dd>39-1/5"</dd>
<dt>Product Weight</dt>
<dd>61.5 lbs. with stand (54.5 lbs. without)</dd>
<dt>Product Depth</dt>
<dd>11-4/5" with stand (3-3/5" without)</dd>
<dt>TV Type</dt>
<dd>LCD Flat-Panel</dd>
</dl>
</li>
</div>
</div>
</nowiki></pre>

=== hlisting, hproduct, haudio, haggregatereview/hreview ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct haudio">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/gangsta">Gangsta/Hardcore</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/50cent-curtis.jpg" class="photo" alt="picture of 50 cent" />
<div class="album">Curtis</div>
<div class="contributor"><span class="vcard"><span class=n nickname">50 Cent</span></span></div>
<p>Release date:<abbr class="published" title="2007-09-11">September 11, 2007</abbr></p>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_4_0.gif" alt="4 out of 5 stars"/></a></span><span class="rating">4.0</span> / <span class="best">5</span> Number of reviews:(<span class="num">4</span> reviews)</div>
</div>
<div class="price">$9.99</div>
<a href="add-to-cart-url" rel="payment"><img src="http://storename.com/images/global/add-to-cart.gif" alt="add to cart" /></a>
<h2>Tracks</h2>
<ol>
<li class="item"><span class="position">1</span>.<span class="fn">Intro</span><a href="http://images.storename.com/media/sample/50cent-intro.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">2</span>.<span class="fn">My Gun Go Off</span><a href="http://images.storename.com/media/sample/50cent-gun-go-off.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">3</span>.<span class="fn">Man Down - (censored)</span><a href="http://images.storename.com/media/sample/50cent-man-down.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">4</span>.<span class="fn">I'll Still Kill - (with Akon)</span><a href="http://images.storename.com/media/sample/50cent-ill-still-kill.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">5</span>.<span class="fn">I Get Money</span><a href="http://images.storename.com/media/sample/50cent-i-get-money.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">6</span>.<span class="fn">Come & Go - (with Dr. Dre)</span><a href="http://images.storename.com/media/sample/50cent-come-go.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">7</span>.<span class="fn">Ayo Technology - (with Timbaland/Justin Timberlake)</span><a href="http://images.storename.com/media/sample/50cent-ayo-technology.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">8</span>.<span class="fn">Follow My Lead - (with Robin Thicke)</span><a href="http://images.storename.com/media/sample/50cent-follow-my-lead.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">9</span>.<span class="fn">Movin' on Up</span><a href="http://images.storename.com/media/sample/50cent-movin-on-up.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">10</span>.<span class="fn">Straight to the Bank</span><a href="http://images.storename.com/media/sample/50cent-straight-to-bank.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">11</span>.<span class="fn">Amusement Park</span><a href="http://images.storename.com/media/sample/50cent-amusement-park.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">12</span>.<span class="fn">Fully Loaded Clip</span><a href="http://images.storename.com/media/sample/50cent-fully-loaded-clip.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">13</span>.<span class="fn">Peep Show - (with Eminem)</span><a href="http://images.storename.com/media/sample/50cent-peep-show.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">14</span>.<span class="fn">Fire - (with Young Buck/Nicole Scherzinger)</span><a href="http://images.storename.com/media/sample/50cent-fire.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">15</span>.<span class="fn">All of Me - (with Mary J. Blige)</span><a href="http://images.storename.com/media/sample/50cent-all-of-me.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">16</span>.<span class="fn">Curtis 187</span><a href="http://images.storename.com/media/sample/50cent-curtis-187.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">17</span>.<span class="fn">Touch the Sky - (with Tony Yayo)</span><a href="http://images.storename.com/media/sample/50cent-touch-the-sky.mp3" rel="sample">Listen</a></li>
</ol>
</div>
</div>
</nowiki></pre>

== Existing Practices ==
* ''Summary of common patterns discovered''
* ''Other attempts to solve The Problem''

== Proposal ==
* Early drafts
* ''Link to related pages as they become available''
* I think that this page from email discussion actually is a non-example: http://webcenter.polls.aol.com/poll?view=69043&pollId=69096 ; it's actually aggregate rankings with numerical weightings, which might lead to an interesting hRanking microformat but I think is out of bounds for an 'aggregate review' discussion.
** -brainstorming
** - proposal
** -microformat

== See Also ==
* Aggregation of microformats: [[aggregate-microformat-template-examples|examples]] - [[aggregate-microformat-template-formats|formats]] - [[aggregate-microformat-template-brainstorming|brainstorming]]
* Aggregate review: [[aggregate-review-formats|formats]] - [[aggregate-review-brainstorming|brainstorming]]
* [[hreview-aggregate]]
* [[review-examples]] for examples of individual reviews
* [[hreview|hReview]]
* ''Normative references for tags used''

aggregate-review-examples

2009-11-21T02:20:29Z

Kavi:

== The Problem ==
''There are various services that provide aggregate ratings and reviews on the Web. How should this information be presented in microformat form? hReview is oriented towards individual reviews with ratings; can it also be used for presenting data from aggregate reviews?''
== Participants ==
* John Panzer
* Kavi Goel
* Jay Myers

== Real-World Examples ==
''Links to public web pages, either popular or insightful''

=== Amazon ===
* http://www.amazon.com/gp/product/B001FA1NFA/
* Aggregation of user reviews for a product. Up to 10 reviews per page
* Includes 1-5 stars average rating and the total number of reviews
* Also includes number of reviews for each score (1-5)

=== Bizrate ===
* Aggregation of user reviews for a product. Up to 10 reviews per page
* Includes 1-5 stars average rating and the total number of reviews

=== Citysearch ===
* http://siliconvalley.citysearch.com/profile/11636582/mountain_view_ca/vive_sol.html
* Shows 1-5 stars average rating and the total number of reviews on the "business info" page
* On the "reviews" page, it also includes the number of reviews for each score (1-5) and some themes from the reviews (i.e. "Prompt seating", "Romantic", "Good for groups")

=== CNet Reviews ===
* http://reviews.cnet.com/car-gps-navigation/garmin-nuvi-880/4505-3430_7-32815498.html
* Shows both editors rating (1-5 stars as well as a word describing the rating, i.e. "Excellent") and the average user rating (1-5 stars) and total number of user reviews
* Only shows editor's review and 3 user reviews on first page for a product.
* Clicking through shows 5 reviews per page.

=== Download.com ===
* http://www.download.com/Ad-Aware-2008/3000-8022_4-10045910.html
* Shows both editors rating (1-5 stars) and the average user rating (1-5 stars) and total number of votes
* 5 user reviews shown per page

=== Rotten Tomatoes ===
* http://www.rottentomatoes.com/m/quantum_of_solace/
* Shows percentage of positive reviews from users (in this case, users = movie critics) and number of reviews
* An average rating (between 1 and 10) is also shown, but this data is de-emphasized on the Rotten Tomatoes movies pages.

=== Yelp ===
* http://www.yelp.com/biz/vive-sol-restaurant-mountain-view
* Shows 1-5 stars average rating and the total number of reviews
* Also includes number of reviews for each score (1-5)
* The site highlights recurring themes from reviews (i.e. "The food is delicious - love the chicken mole.") and the number of reviews where such comments were made.

== Ratings without reviews examples ==

This section added Nov 2009.

Some sites allow users to rate an object without providing a written review. These ratings can be numerical ratings (i.e. 1-5 stars) or votes (thumbs up/thumbs down). Aggregate ratings are calculated using all ratings or "votes" though the number of reviews available is smaller. The following are example sites that have separate numbers of user ratings vs full reviews.

=== Download.com ===
* http://www.download.com/Ad-Aware-2008/3000-8022_4-10045910.html
* Download.com explicitly specifies the number of user ratings as well as the number of reviews (though the review count is less prominent). Ratings are on a 5-point scale and Download.com uses the term "votes."

=== IMDb ===
* http://www.imdb.com/title/tt0258000/
* IMDb explicilty writes the number of user ratings, provided on a 10-point scale. There are no reviews per se, but user comments on movie pages are often actually reviews. IMDb uses the term "votes."

=== Metromix ===
* http://chicago.metromix.com/restaurants/mexican/rustico-grill-logan-square/1361373/content
* Metromix writes the number of user ratings but not the number of user reviews (though user reviews exist on the page). Ratings are on a 5-point scale, and Metromix uses the term "ratings."

=== Urbanspoon ===
* http://www.urbanspoon.com/r/3/39999/restaurant/West-Village/Spotted-Pig-New-York
* Urbanspoon explicitly writes the number of user ratings as well as the number of reviews (though the review count is less prominent on the page). Urbanspoon uses the term "votes" and votes are binary (like it/don't like it).

== Coded examples ==

(Note: examples may contain additional markup for positioning and presentation purposes to simulate live production markup)

=== aggregate reviews embedded in hproduct block ===
<pre><nowiki>
<div class="hproduct">
<ol class="clearfloat" id="breadcrumbs">
<li><a href="http://www.yoursite.com">Home</a></li>
<li class="category"><a href="http://www.yoursite.com/computers/">Computers</a></li>
<li class="category"><a href="http://www.yoursite.com/computers/networking/">Networking</a></li>
<li class="category"><a href="http://www.yoursite.com/computers/networking/print-servers">Print Servers</a></li>
</ol>
<h1 class="n">NETGEAR 802.11g Wireless USB Print Server with 4-Port Switch</h1>
<div id="topbox">
<div class="rightcol">
<img src="http://images.yoursite.com/images/products/7250/7250707_rb.jpg" alt="Image of NETGEAR WGPS606" class="photo" />
</div>
<div class="leftcol">
<div class="infomain">
<ul>
<li>
<strong>Brand: </strong><span class="brand">NETGEAR</span>
</li>
<li>
<strong>Model: </strong><span class="model">WGPS606</span>
</li>
<li class="identifier">
<span class="type">SKU: </span><span class="value">7250707</span>
</li>
</ul>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://images.yoursite.com/path/to/product" class="url"><img src="http://images.yoursite.com/images/misc/ratings_star_3_5.gif" alt="3.5 out of 5 stars"/></a></span><span class="rating">4.7</span> / <span class="best">5</span> (<span class="num">13</span> reviews)</div>
</div>
</div>
<p class="description">
Share a USB printer with others on your network; up to 54 Mbps; 2 USB ports; wireless Ethernet bridge mode with 4-port switch
</p>
<p>
<span class="availability online">Available online</span>. <span class="shipping">Shipping: Usually leaves our warehouse in 1 business day. <span class="money">Estimated shipping cost: <abbr class="currency" title="USD" lang="en">$</abbr><span class="amount">6.99</span>.</span></span>

</p>
<p>
<span class="availability instore">Available in our stores</span>. Store Pickup: Available at most stores
</p>
<p>
<span class="availability specialorder">Not available for special order</span>.
</p>
</div>
<div class="infoside">
<span class="price regular"><span class="money"><strong>Price: </strong><abbr class="currency" title="USD" lang="en">$</abbr><span class="amount">99.99</span></span></span>
<div>
<a href="http://images.yoursite.com/path/to/buy/product" class="buy"><img src="http://images.yoursite.com/images/btn_add_to_cart.gif" alt="buy this product" /></a>
</div>
</div>
</div>
</div>

</nowiki></pre>

=== hlisting, hproduct, haggregatereview/hreview, xoxo ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/tv-and-video">TV & Video</a></li>
<li class="category"><a href="http://storename.com/televisions">Televisions</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/samsung-ln40a550.jpg" class="photo" alt="picture of samsung ln40a550" />
<div class="fn"><span class="brand">Samsung</span> - 40" 1080p Flat-Panel LCD HDTV</div>
<dl class="identifier">
<dt>Model</dt>
<dd>LN40A550</dd>
<dt>SKU</dt>
<dd>8749465</dd>
</dl>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_3_5.gif" alt="3.5 out of 5 stars"/></a></span><span class="rating">4.7</span> / <span class="best">5</span> (<span class="num">13</span> reviews)</div>
</div>
</div>
<div class="price">$1,099.99</div>
<ol class="xoxo">
<li><h2>Specifications</h2>
<dl>
<dt>Warranty Terms - Parts</dt>
<dd>1 year</dd>
<dt>Warranty Terms - Labor</dt>
<dd>1 year</dd>
<dt>Product Height</dt>
<dd>27" with stand (24-7/10" without)</dd>
<dt>Product Width</dt>
<dd>39-1/5"</dd>
<dt>Product Weight</dt>
<dd>61.5 lbs. with stand (54.5 lbs. without)</dd>
<dt>Product Depth</dt>
<dd>11-4/5" with stand (3-3/5" without)</dd>
<dt>TV Type</dt>
<dd>LCD Flat-Panel</dd>
</dl>
</li>
</div>
</div>
</nowiki></pre>

=== hlisting, hproduct, haudio, haggregatereview/hreview ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct haudio">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/gangsta">Gangsta/Hardcore</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/50cent-curtis.jpg" class="photo" alt="picture of 50 cent" />
<div class="album">Curtis</div>
<div class="contributor"><span class="vcard"><span class=n nickname">50 Cent</span></span></div>
<p>Release date:<abbr class="published" title="2007-09-11">September 11, 2007</abbr></p>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_4_0.gif" alt="4 out of 5 stars"/></a></span><span class="rating">4.0</span> / <span class="best">5</span> Number of reviews:(<span class="num">4</span> reviews)</div>
</div>
<div class="price">$9.99</div>
<a href="add-to-cart-url" rel="payment"><img src="http://storename.com/images/global/add-to-cart.gif" alt="add to cart" /></a>
<h2>Tracks</h2>
<ol>
<li class="item"><span class="position">1</span>.<span class="fn">Intro</span><a href="http://images.storename.com/media/sample/50cent-intro.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">2</span>.<span class="fn">My Gun Go Off</span><a href="http://images.storename.com/media/sample/50cent-gun-go-off.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">3</span>.<span class="fn">Man Down - (censored)</span><a href="http://images.storename.com/media/sample/50cent-man-down.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">4</span>.<span class="fn">I'll Still Kill - (with Akon)</span><a href="http://images.storename.com/media/sample/50cent-ill-still-kill.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">5</span>.<span class="fn">I Get Money</span><a href="http://images.storename.com/media/sample/50cent-i-get-money.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">6</span>.<span class="fn">Come & Go - (with Dr. Dre)</span><a href="http://images.storename.com/media/sample/50cent-come-go.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">7</span>.<span class="fn">Ayo Technology - (with Timbaland/Justin Timberlake)</span><a href="http://images.storename.com/media/sample/50cent-ayo-technology.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">8</span>.<span class="fn">Follow My Lead - (with Robin Thicke)</span><a href="http://images.storename.com/media/sample/50cent-follow-my-lead.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">9</span>.<span class="fn">Movin' on Up</span><a href="http://images.storename.com/media/sample/50cent-movin-on-up.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">10</span>.<span class="fn">Straight to the Bank</span><a href="http://images.storename.com/media/sample/50cent-straight-to-bank.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">11</span>.<span class="fn">Amusement Park</span><a href="http://images.storename.com/media/sample/50cent-amusement-park.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">12</span>.<span class="fn">Fully Loaded Clip</span><a href="http://images.storename.com/media/sample/50cent-fully-loaded-clip.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">13</span>.<span class="fn">Peep Show - (with Eminem)</span><a href="http://images.storename.com/media/sample/50cent-peep-show.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">14</span>.<span class="fn">Fire - (with Young Buck/Nicole Scherzinger)</span><a href="http://images.storename.com/media/sample/50cent-fire.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">15</span>.<span class="fn">All of Me - (with Mary J. Blige)</span><a href="http://images.storename.com/media/sample/50cent-all-of-me.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">16</span>.<span class="fn">Curtis 187</span><a href="http://images.storename.com/media/sample/50cent-curtis-187.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">17</span>.<span class="fn">Touch the Sky - (with Tony Yayo)</span><a href="http://images.storename.com/media/sample/50cent-touch-the-sky.mp3" rel="sample">Listen</a></li>
</ol>
</div>
</div>
</nowiki></pre>

== Existing Practices ==
* ''Summary of common patterns discovered''
* ''Other attempts to solve The Problem''

== Proposal ==
* Early drafts
* ''Link to related pages as they become available''
* I think that this page from email discussion actually is a non-example: http://webcenter.polls.aol.com/poll?view=69043&pollId=69096 ; it's actually aggregate rankings with numerical weightings, which might lead to an interesting hRanking microformat but I think is out of bounds for an 'aggregate review' discussion.
** -brainstorming
** - proposal
** -microformat

== See Also ==
* Aggregation of microformats: [[aggregate-microformat-template-examples|examples]] - [[aggregate-microformat-template-formats|formats]] - [[aggregate-microformat-template-brainstorming|brainstorming]]
* Aggregate review: [[aggregate-review-formats|formats]] - [[aggregate-review-brainstorming|brainstorming]]
* [[hreview-aggregate]]
* [[review-examples]] for examples of individual reviews
* [[hreview|hReview]]
* ''Normative references for tags used''

hreview-aggregate

2009-11-11T05:53:03Z

Kavi: /* Examples */

<entry-title>hReview-aggregate 0.1</entry-title>
{{DraftSpecification}}

[[hreview-aggregate|hReview-aggregate]] is a format for embedding review information (of products, services, businesses, etc). Whereas [[hreview|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: [[User:KaviGoel|Kavi Goel]], Google
; Authors/Contributers (alphabetical): [[User:Tantek|Tantek Çelik]]
: Othar Hansson, Google
: [[User:JayMyers|Jay Myers]], [http://www.bestbuy.com/ Best Buy, Co., Inc.]

== Introduction ==

Many websites publish reviews using a variety of organization schemes. hReview-aggregate and the similar microformat [[hreview|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|aggregate review brainstorming]] wiki page.

{{rfc-2119-intro}}

=== 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 ('''<code>hreview-aggregate</code>''')
** '''<code>item</code>''' info. required. '''<code>fn</code>''' ('''<code>url</code>''' || '''<code>photo</code>''' ) | '''[[hcard|hCard]]''' (for person or business) | '''[[hcalendar|hCalendar]]''' (for event) | '''[[hproduct|hProduct]]''' (for product)
** '''<code>rating</code>'''. required. fixed point integer [1.0-5.0], with optional alternate '''<code>worst</code>''' (default:1.0) and/or '''<code>best</code>''' (default:5.0), also fixed point integers, and explicit '''<code>average</code>'''.
** '''<code>count</code>'''. required. non-negative integer.
** '''<code>summary</code>'''. 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|hCard]] for a business or person, [[hproduct|hProduct]] for a product, or [[hcalendar|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 <code>item</code>, <code>rating</code>, and <code>summary</code> properties are reused from [[hreview|hReview]].

== Examples ==

=== Basic example ===

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

<pre><nowiki>
<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>
</nowiki></pre>

Adding hReview-aggregate markup to this is straightforward:

<pre><nowiki>
<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>
</nowiki></pre>

=== 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.

<pre><nowiki>
<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>
</nowiki></pre>

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

<pre><nowiki>
<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>
</nowiki></pre>

Note that the <code>item</code> and <code>vcard</code> 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 [http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=146645 hReview-aggregate] via [http://googlewebmastercentral.blogspot.com/2009/05/introducing-rich-snippets.html Rich Snippets].
* [http://local.stv.tv/glasgow/place/restaurant-japanese/10320725-wagamama/ STV Local] uses hreview-aggregate for business ratings, average prices and contact details with hcard
* [http://www.critiki.com Critiki] publishes ratings and reviews of Tiki bars, and uses hReview aggregate for average ratings on their pages, e.g. [http://www.critiki.com/cgi-bin/location.cgi?loc_id=162 overview of The Tonga Room]. (as [http://twitter.com/humuhumu/status/4165014155 tweeted by humuhumu] 2009-09-21)
* [http://free.naplesplus.us NAPLESPLUS] is an example of a website that has implemented hreview-aggregate via Google specs.
* ...

== Related Pages ==

* [[hreview|hReview]] - microformat for marking up individual reviews
* [[aggregate-review-brainstorming|Aggregate review brainstorming]] - discussions leading to the creation of hReview-aggregate and ideas for improvement.
* [[aggregate-review-examples|Aggregate review examples]]

[[Category:Draft Specifications]]
[[Category:hReview-aggregate]]

hreview-aggregate

2009-11-11T05:04:08Z

Kavi: /* examples in the wild */

hreview-aggregate

2009-11-11T05:01:54Z

Kavi:

Template:hreview-related-pages

2009-11-11T05:00:43Z

Kavi:

* [[hreview]]
* [[hreview-aggregate|hReview-aggregate]] - microformat for specifying summary information from a collection of reviews about a product or service
* [http://microformats.org/code/hreview/creator hReview creator] ([[hreview-creator-feedback|feedback]]) - create your own hReview.
* [[hreview-authoring|hReview authoring]] - learn how to add hReview mark-up to your existing contact info.
* [[hreview-brainstorming|hReview brainstorming]] - thoughts for improving hReview.
* [[hreview-cheatsheet|hReview cheatsheet]] - hCard properties.
* [[hreview-examples-in-wild|hReview examples in the wild]] - an on-going list of websites which use hReview.
* [[hreview-faq|hReview FAQ]] - If you have any questions about hReview, check here, and if you don't find answers, add your questions!
* [[hreview-feedback|hReview feedback]] - Feedback is encouraged!
* [[hreview-implementations|hReview implementations]] - websites or tools which either generate or parse hReviews.
* [[hreview-issues|hReview issues]] - Please add any issues with the specification to the issues page.
* [[hreview-parsing|hReview parsing]] - Normatively details of how to parse hReviews.
* [[hreview-profile|hReview profile]] - The XMDP profile for hReview.
* [[hreview-tests|hReview tests]] - a wiki page with actual embedded hReviews to try parsing.
* [[advocacy#hReview|hReview advocacy]] - encourage others to use hReview.
* [[review-examples]]
** [[hreview-examples]]
* [[review-formats]]
* [[review-brainstorming]] - where we brainstormed about review formats before coming up with hReview.
* [[currency]] - proposal for marking up amounts of money (e.g. prices of reviewed items).
* Aggregate reviews - [[aggregate-review-examples|examples]] - [[aggregate-review-formats|formats]] - [[aggregate-review-brainstorming|brainstorming]]

hreview-aggregate

2009-11-11T04:42:35Z

Kavi: /* Introduction */

hreview-aggregate

2009-11-11T04:41:20Z

Kavi: /* Format */

hreview-aggregate

2009-11-11T04:40:53Z

Kavi: /* Format */

hreview-aggregate

2009-11-11T00:57:58Z

Kavi:

hreview-aggregate

2009-11-11T00:36:20Z

Kavi:

aggregate-review-brainstorming

2009-11-03T00:28:56Z

Kavi:

Ideas for how to support aggregate reviews via microformats.

== Common themes amongst examples (that we might want to support) ==

* Aggregations of reviews always contain these two elements:
** the number of reviewers
** the average rating

''number of reviewers, really? unique people? what if there's more than one rating per person? Number of ratings would be simpler.''

''Google Rich Snippets makes mistake of assuming that number of ratings equals number of reviews, but users may leave rating without leaving review''

''These are good points -- added a separate section below to discuss ratings vs reviews vs reviewers. Note that the first comment referring to the number of "reviewers" caught a typo -- it should be number of reviews, not reviewers. -- Kavi, Nov 2 2009''

* Other elements that occur in the example set include:
** the number of reviews for each rating (i.e. 10 5-star ratings, 7 4-star ratings, etc)
** recurring themes about the entity being reviewed (i.e. "romantic restaurant" or "love the chicken mole").
** who are the reviewers (i.e. "critics" or "users"). Some sites (i.e. Rotten Tomatoes or GameSpot) have multiple sets of aggregate reviews to cover both critics and users.

* In addition, some elements already present in the hReview schema exist in aggregate reviews as well:
** review summary/description
** most recent date reviewed

== Proposal discussed over IRC ==

==== What is the proposal? ====
* Define a new microformat for aggregate reviews (root class name "hreview-aggregate").
* The format will contain only value (the number of reviews) with a new property "count" and embedded [[hReview]] properties that contains details like the average review score, summary, and a reference to the object of the review.

'''This proposal should be written up on a separate page as a microformats draft, e.g. [[hreview-aggregate]].'''

==== Why was this proposal preferred? ====
* Creating a new uF rather than extending hReview doesn't require branching the spec for hReview and provides clean separation in case we want to extend the new format to include other data in the future
* Supporting only the number of reviews (rather than scores per rating, etc) is probably sufficient for 80% of sites with aggregate reviews.

== Other proposals suggested ==

==== 1) Do nothing. Aggregation must be done by the microformats parser ====
* Pros: Doesn't require any change to the existing microformats definitions
* Cons: Very difficult for parsers. Reviews for a single entity are usually not limited to a single web page (there are typically no more than 5-10 reviews per page), so aggregating this data would require the parser to figure out which pages to crawl to assemble the aggregate scores.

==== 2) Extend existing hReview format to include "reviewcount" ====
* Any hReview that contains a reviewcount field (which denotes the number of reviewers) would implicitly refer to an aggregation of reviews. The rating would correspond to the average rating of all individual reviews, summary/description refer to a summary of overall sentiments from the reviews, date refers to the most recent review's date.
* Pros: very simple addition to the existing microformat
* Cons: Mild overloading of what an hReview contains -- a review can now correspond to a single user's review or an aggregation of user reviews.

==== 3) Define a new microformat type for aggregate reviews ====
* This type could contain the staples -- average review score and number of reviewers -- as well as some of the other sometimes-used features listed in the "common themes" section earlier.
* Pros: robust way to mark up many elements of aggregate review information
* Cons: some redundancy with hReview. Extending hReview might be sufficient

==== 4) Do not use hreview classes in hreview-aggregate ====
* This causes a collision when hreview includes an hcard that contains review aggregates per google specification http://www.google.com/support/webmasters/bin/answer.py?answer=146645 . In that case, the hreview has its own rating, and a second rating imported via the include pattern.
Currently Yelp implements review aggregate as an hreview-aggregate block that include the entire hcard inside it, and the aggregate rating. Importing this hcard from an hreview using the include pattern, imports the rating as well.
* review-aggregate can be included INSIDE hcard block, or can surround that block.
* review-aggregate can point to a '''self contained''' hcard (include pattern):
** Without repeating any of the information in the hcard
** Without including empty links, example <code><a class="item include" href="#my_business_hcard"></a></code>
** Without including links with duplicate redundant information that is part of the hcard, example <code><a class="item include make_me_invisible_to_user" href="#my_business_hcard">Business Name</a></code>
** Without adding listing information, such as the type of listing: <code><span class="type">business</span></code>.
** Without using non-semantic HTML, such as object tag.
* An hreview should be able to safely import an hcard that may contain hreview-aggregate '''without name collitions''' especially the rating tag (using include pattern).
* An hreview should be able to safely import an hcard that may contain nested elements of hreview-aggregate, such as count and average rating, '''without name collitions''' (using include pattern). If this is not possible, pages will have to default to non semantic HTML, and markup that contains a lot of hidden content, making them less accessible.

== Reviews vs ratings ==

Section added Nov 2009

Adoption of hreview-aggregate has been strong, but one issue that arisen is the notion of reviews vs ratings. The original hreview-aggregate spec as described below uses a single property called "count" to specify the total number of reviews for an item that contributed towards an aggregate review. This works well for a site like Yelp, where the aggregate rating is based on the number of individual user reviews.

However, many sites allow users to provide a rating without actually writing a review. So there should be some way of allowing sites to mark up the number of "ratings" (or "votes") separately from the number of "reviews."

A couple examples of sites that have separate rating counts and review counts:
* Urbanspoon: http://www.urbanspoon.com/r/6/88896/restaurant/Patxis-Chicago-Pizza-Palo-Alto
* Download.com: http://download.cnet.com/Mayura-Chess-Board/3000-7562_4-10525218.html

==== Proposed solution ====

* Add a new property called "votes" to hreview-aggregate.
** Pros: it is simple for webmasters to understand and is consistent with the terminology that many sites actually use (for example: Urbanspoon, Download.com, IMDb). It also doesn't change the interpretation for any site that has already implemented the existing hreview-aggregate spec.
** Cons: it's not completely obvious that "count" means "number of reviews" whereas "votes" means "number of ratings."

==== Alternative options ====

* Add nested sub-properties to the "count" property: "reviews" and "votes"
** Pros: terminology is clearer than the proposed solution above. For backwards compatibility, if users don't specify reviews vs votes, assume they meant reviews by default.
** Cons: in practice, adding additional layers of nesting creates more chances for webmasters to make mistakes. More nesting is also more verbose.

Note that we shouldn't remove the ability for people to mark up the actual number of reviews -- for anyone who wants to read reviews, it's very useful to know how many reviews there are on a page even if there are more votes contributing towards an aggregate rating.

== See Also ==
* Aggregate reviews: [[aggregate-review-examples|examples]] - [[aggregate-review-formats|formats]]
* [[hreview-aggregate]]
* [[hreview|hReview]]

hlisting-brainstorming

2009-07-06T20:00:59Z

Kavi: /* Items changed: */

<h1>listing microformat brainstorming </h1>
This is brainstorming for a [[hlisting]] microformat per the [[process]].

{{TOC-right}}

=== Revised Base Schema Elements (proposed, revised by [[User:JayMyers|Jay Myers]] 16:55, 29 Jun 2009 (UTC)) ===

*hListing (hlisting)
** listing action. optional. one or more tags, suggested set: sell | rent | trade | meet | announce | offer | wanted | event | service
** '''lister.''' required. hCard | (fn || email || url || tel).
** dtlisted. optional. ISO8601 absolute date time.
** dtexpired. optional. ISO8601 absolute date time.
** price. optional. text. [should include a floating-point number with optional ISO currency codes] - see the currency proposal
** item info. optional. (fn || url || photo || geo || adr) | hCard (for person or business).
** summary. optional. text.
** '''description.''' required. text with optional valid XHTML markup.
** item tags. optional. keywords or phrases describing the item being offered, using rel-tag
** permalink. optional.
** availability. optional. text.
** condition. optional. text. examples: 'new', 'used', 'refurbished'.
** shipping. optional. text. text describing shipping and fulfillment

==== Notes ====

Please see [[hlisting-examples|hListing examples page]] for analysis of 80/20 use case for new attributes availability, condition and shipping. I believe condition should still be considered even though it misses the 80/20 use case mark (71.2% based on current analysis) as it is included in most product-specific data submission services (e.g., Yahoo Product Submit, Google Base).

----

=== Revised Base Schema Elements (proposed) ===

*hListing (hlisting)
** listing action. optional. one or more tags, suggested set: sell | rent | trade | meet | announce | offer | wanted | event | service
** lister. optional. hCard | (fn || email || url || tel).
** dtlisted. optional. ISO8601 absolute date time.
** dtexpired. optional. ISO8601 absolute date time.
** price. optional. text. [should include a floating-point number with optional ISO currency codes] - see the currency proposal
** item info. optional. (fn || url || photo || [[geo]] || [[adr]]) | [[hcard|hCard]] (for person or business).
** summary. optional. text.
** '''description'''. required. text with optional valid XHTML markup.
** item tags. optional. keywords or phrases describing the item being offered, using rel-tag
** permalink. optional.
** availability. optional. text.
** condition. optional. text. examples: 'new', 'used', 'refurbished'.
** shipping. optional. text. text describing shipping and fulfillment

==== Items removed ====
* version. optional. text.

<div class=discussion>
* +1 I'm tending to agree with the removal of version, as in practice it has not been necessary for either [[hReview]] or [[hListing]].[[User:Tantek|Tantek]] 17:45, 16 April 2009 (UTC)
</div>

* item info. optional. (fn || url || photo || geo || adr) | hCard (for person or business).

<div class=discussion>
* Removal of <code>item</code> seems to be a mistake, as that is used to indicate the item itself being listed. E.g., a nested <code>hProduct</code> would be <code><p class='item hproduct'></p></code>. Removal appears to leave no way to include ''what'' is being listed. --[[User:BenWard|BenWard]] 17:38, 16 April 2009 (UTC)
** +1 completely agreed with Ben Ward's point. Wide use of [[hReview]] in the [[hreview-examples-in-wild|wild]] has shown that having an explicit "item" is both necessary and works in practice. [[User:Tantek|Tantek]] 17:40, 16 April 2009 (UTC)
* Indeed it was a mistake... left it out of my edits. Replaced. [[User:JayMyers|JayMyers]] 21:04, 22 April 2009 (UTC)
</div>

==== Items added ====
<div class=discussion>
* Each of the following should cite the analysis made of real world examples that demonstrates the 80%+ use case need, otherwise, they should not be added. [[User:Tantek|Tantek]] 17:45, 16 April 2009 (UTC)
</div>

* availability. optional. text.
* condition. optional. text. examples: 'new', 'used', 'refurbished'.
* shipping. optional. text. text describing shipping and fulfillment

==== Items changed: ====
* listing action => optional. if omitted, action assumed to be sell
* lister => optional. if omitted, the buyer/seller is assumed to be the site where the microformat exists
<div class=discussion>
* In that case, an algorithm should be provided for how to determine the hCard for the lister, if no explicit lister is given. [[User:Tantek|Tantek]] 17:45, 16 April 2009 (UTC)
* Isn't the instruction above ("buyer/seller is assumed to be the site where the microformat exists" itself an algorithm? So, if Target.com has an item for sale and lister isn't specified, you use the domain of the web page containing the markup to identify the seller as "target.com" --Kavi, 6 July 2009
</div>

User:KaviGoel

2009-06-25T21:53:48Z

Kavi: New page: Kavi Goel is a product manager at Google.

Kavi Goel is a product manager at Google.

events/2009-06-26-microformats-4th-bday

2009-06-25T21:50:44Z

Kavi: /* regrets */

<entry-title>microformats.org 4th birthday party!</entry-title>

Celebrate the 4th birthday of http://microformats.org! One of several microformats [[events]].

If you'd like to help out with or attend the party, please add your name below.

[[#attending|RSVP]] <strong>required</strong> for venue capacity tracking.

<div class="event-page vevent" id="party">
== overview ==
;When
:<span class="dtstart"><span class="value">2009</span>-<span class="value">06</span>-<span class="value">26</span> a<span class="value" style="text-transform:lowercase">T</span> <span class="value">19</span class="value">:<span class="value">00</span><span style="display:none">:<span class="value">00</span></span></span> to <span class="dtend"><span class="value">2009</span>-<span class="value">06</span>-<span class="value">26</span> a<span class="value" style="text-transform:lowercase">T</span> <span class="value">22</span>:<span class="value">00</span><span style="display:none">:<span class="value">00</span></span></span>
;Where
:<span class="location vcard"><span class="fn org">[http://www.yelp.com/biz/b-restaurant-and-bar-san-francisco B Restaurant and Bar]</span>, <span class="adr"><span class="street-address">720 Howard Street</span>, <span class="extended-address">Yerba Buena Upper Terrace</span>, <span class="locality">San Francisco</span>, <span class="region">CA</span> <span class="postal-code">94103</span> <span class="country-name">USA</span></span></span>
;What
:<span class="summary">microformats.org 4th birthday party!</span>
;Web
:<span class="url">http://microformats.org/wiki/events/2009-06-26-microformats-4th-bday</span>
;Donation
:Donation requested at the door: sliding scale $5-$20.
</div> 

'''[http://feeds.technorati.com/events/microformats.org/wiki/events/2009-06-26-microformats-4th-bday%23party Add this event to your calendar]''' [http://feeds.technorati.com/events/microformats.org/wiki/events/2009-06-26-microformats-4th-bday%23party http://www.boogdesign.com/images/buttons/microformat_hcalendar.png]

== sponsors ==
Please sign up to sponsor the microformats.org 4th birthday party!

* [http://objectadjective.com Object Adjective] is a proud sponsor of this event.
* [http://www.ribbit.com/ Ribbit] is proud to sponsor the party
* [http://spinn3r.com Spinn3r] is a proud sponsor of the party
* ...

== planners ==
This section is for organizing a party for the upcoming 4th birthday of http://microformats.org.

I'm donating my time before the event to help plan and make the party happen!
* [[User:Tantek|Tantek Çelik]] - coordinating, sponsors
* [[User:Rohit|Rohit Khare]] - sponsors
* [[User:Kevin_Marks|Kevin Marks]] - sponsors
* [[User:BenWard|Ben Ward]] - tshirts, sponsors
* [[User:Pseudowish|Lauren Scime]] - design / venue / sponsors / publicity
* [[User:Repeatpenguin|Jeremy Anderson]] - will be assisting Lauren w/ above.

We need:
* a volunteer coordinator. someone to coordinate the volunteers listed below.
* [[stickers]] - Lauren is on it
** 500 rounded square 2" stickers w/logo on black background have come in the mail
* tshirts - Ben is on it

== volunteers ==
Sign up to be a volunteer!
We need volunteers to check people in at the door, take donations, hand out stickers, t-shirts etc.
* [[User:Richardault|Richard Ault]] - Checking names and taking donations for at least first hour. Need to find money box. Also need more volunteers to do same.
* ...

== donations ==
* Donation requested at the door: sliding scale $5-$20. $10 or more gets you a t-shirt (may have to order them on demand and hand out at the next dinner depending on whether t-shirts arrive or not).
* Donations go towards the party and [[events/2009-07-18-dev-camp|microformatsDevCamp]] this summer.
* Spinn3r would be willing to donate/sponsor some...

== attending ==
I'm going to show up and help celebrate so I'm signing up here with my name linked to my user page (or personal web site).
# [[User:Tantek|Tantek Çelik]]
# [[User:Kevin_Marks|Kevin Marks]]
# [[User:BenWard|Ben Ward]]
# [[User:Pseudowish|Lauren Scime]]
# [[User:Repeatpenguin|Jeremy Anderson]]
# [[User:Richardault|Richard Ault]]
# [[User:KevinBurton|Kevin Burton]] of [http://spinn3r.com Spinn3r] - I will be by for an hour or so... Spinn3r's 3.0 launch dinn3r is that evening too.
# [[User:Singpolyma|Singpolyma]]
# [http://brynnevans.com Brynn Evans]
# [http://factoryjoe.com Chris Messina]
# [http://lizdunn.com Liz Dunn]
# [http://www.myspace.com/ciberch Monica Keller]
# ...

== regrets ==
I'd love to be there but can't. Happy 4th birthday from afar!
* [[User:Rohit|Rohit Khare]]
* [[User:Cindyli|Cindy Li]]
* [[User:Tonystubblebine|Tony Stubblebine]]
* [[User:Anildash|Anildash]] 20:07, 24 June 2009 (UTC)
* [[User:NiallKennedy|Niall Kennedy]] - in Los Angeles
* [[User:KaviGoel|Kavi Goel]]
* ...

== location ==
* [http://www.yelp.com/biz/b-restaurant-and-bar-san-francisco B Restaurant and Bar] - June 26th, 2009 at 7pm
** Will have hors d'oeuvres and about 50-60 drink tix to hand out to people at the door. Attendees can buy drinks at cash bar after drink tix are used.

== date ==
* 2009-06-26 Friday

== Promotional Graphics ==
* Banners & Images of Various Sizes: Promote Microformats 4 Year Birthday Party!
** [http://anendlessarray.com/microformats/88x31.jpg 88x31px]
** [http://anendlessarray.com/microformats/120x240.jpg 120x240px]
** [http://anendlessarray.com/microformats/125x125.jpg 125x125px]
** [http://anendlessarray.com/microformats/200x100.jpg 200x100px]
** [http://anendlessarray.com/microformats/200x200.jpg 200x200px]
** [http://anendlessarray.com/microformats/250x250.jpg 250x250px]
** [http://anendlessarray.com/microformats/300x225.jpg 300x225px]
** [http://anendlessarray.com/microformats/468x60.jpg 468x468px]
** [http://anendlessarray.com/microformats/160x600.jpg 160x600px]
** [http://anendlessarray.com/microformats/728x90.jpg 728x90px]
** [http://anendlessarray.com/microformats/728x90-pink.jpg 728x90px w/Pink]

* Note: If you are DYING to have a different size than the ones up here I can either send you the photoshop file or make you a custom one - Just send a request to lauren@objectadjective.com or find pseudowish on the [[IRC]]

== Related Pages==
{{events-related-pages}}

search-engines

2009-05-18T16:41:17Z

Kavi: /* web search */

<h1>search engines</h1>
{{TOC-right}}
Search engine [[implementations]] that index microformats across the web (i.e. not just on their own site). Alphabetical within status/stability.

== web search ==
General web search. Search engines that index websites in general using microformats.
* [http://google.com/ Google search] supports [[rel-nofollow]], [[hCard]], [[hReview]], [[hreview-aggregate|hReview aggregate]], [[hProduct]] (since 2009-05 for [http://www.google.com/support/webmasters/bin/answer.py?answer=99170 rich snippets]) in main search. Through additional interfaces:
** [http://www.google.com/advanced_search Google Advanced Search - Usage rights] supports [[rel-license]] (since 2005(?) citation needed)
** [http://code.google.com/apis/socialgraph/ Google Social Graph API] supports [[XFN]] (launched 2008 February). See "[http://socialgraph-resources.googlecode.com/svn/trunk/samples/findyours.html Google Social Graph API How are your sites connected?]".
* [http://search.yahoo.com Yahoo search] supports [[rel-nofollow]]. Through additional interfaces:
** [http://search.yahoo.com/cc Yahoo Creative Commons search] supports [[rel-license]]
** [http://developer.yahoo.com/search/boss/ Yahoo Search BOSS]
*** [http://www.bosshacks.com/build-semantic-search-boss.html Build a semantic Search Engine with BOSS] documents how to use Yahoo's BOSS API to access Yahoo Search Monkey which supports the [[hAtom]], [[hCalendar]], [[hCard]], [[hReview]], [[XFN]], [[geo]], [[rel-tag]], [[adr]] microformats.
** [http://developer.yahoo.net/blog/archives/2008/06/monkey_microformat.html Yahoo Search Monkey] ([[hCard]], [[hCalendar]], [[hReview]], [[hAtom]], others) - launched 2008 May
*** [http://search.yahoo.com/search?p=searchmonkeyid%3Acom.yahoo.uf.hcard search Yahoo for hCards]
*** [http://search.yahoo.com/search?p=searchmonkeyid%3Acom.yahoo.uf.hcalendar search Yahoo for hCalendar events]
*** [http://search.yahoo.com/search?p=searchmonkeyid%3Acom.yahoo.uf.hreview search Yahoo for hReviews]
*** [http://search.yahoo.com/search?p=searchmonkeyid%3Acom.yahoo.uf.hatom search Yahoo for hAtom]
*** [http://search.yahoo.com/search?p=searchmonkeyid%3Acom.yahoo.uf.xfn search Yahoo for XFN]

Editor note: Google and Yahoo search engines could probably use their own pages with implementation details and links to additional resources.

== blog search ==
Search blog posts and blogs in general. Search engines that specifically index blogs, blog posts, and other realtime sources on the web using microformats.
* [http://www.icerocket.com IceRocket] through additional interfaces
** [http://www.icerocket.com/tags IceRocket Tag search] support [[rel-tag]] (to search for [http://www.icerocket.com/c?p=tags blog posts tagged with rel-tag]).
* [http://technorati.com Technorati] ([[rel-nofollow]])
** [http://technorati.com/tags/ Technorati Tag Search] supports [[rel-tag]] (to search for blog posts tagged with rel-tag).

== prototype or alpha ==
=== socialsearchme ===
* [http://scrape.singpolyma.net/profile/ singpolyma social web search] ([[xfn]], [[hCard]]) part of the [http://code.google.com/p/diso/ diso] project.
** memorable URL: http://socialsearchme.com/
** e.g. try a [http://scrape.singpolyma.net/profile/?q=Jeremy search for Jeremy]
** 2008-08-19 [http://singpolyma.net/2008/08/diso-gets-search/ DiSo Gets Search] - blog post announcing it!
==== to do ====
* both <code>socialsearchme.com/?q=b</code> and <code>socialsearchme.com/b</code> should redirect/retrieve <code>scrape.singpolyma.net/profile/?q=b</code>.

=== Technorati Kitchen ===
* [http://kitchen.technorati.com Technorati Kitchen]
** [http://kitchen.technorati.com/contacts/search/ Technorati contacts search] ([[hCard]])
** [http://kitchen.technorati.com/events/search/ Technorati events search] ([[hCalendar]])

=== VIREL ===
* [http://virel.de/ VIREL] indexes both [[hCard]] and [[hCalendar]] and provides a user interface (pop-up menu) to choose between searching contacts or events.
** 2008-09-09 Tag Edge: [http://tagedge.com/2008/09/09/virel-microformats-search-engine/ Virel: Microformats Search Engine]

== search results in microformats ==
Search engines that publish microformats in their results (but may not necessarily be indexing microformats).
=== Karniyarik ===
* [http://www.karniyarik.com Karniyarik] Vertical Search Engine for Online Products ([http://www.karniyarik.com/karniyarik-web Stealth Beta]). Karniyarik's search results lists products and their vendors, which are marked up with [[hCard]] (e.g. [http://www.karniyarik.com/search.jsp?query=bebek+bezi search results for bebek bezi - diapers]). In addition, Karniyarik's [http://www.karniyarik.com/aboutus.jsp about page] is marked up with hCard.

== related ==
* [[implementations]]

implementations

2009-05-18T16:40:34Z

Kavi: /* Google Search */

<entry-title>Microformats Implementations</entry-title>
{{TOC-right}}
This page lists the applications, plugins, sample code, services, tools that produce or consume microformats.

== help improve this page ==
This is only a partial list. If you know other services or tools for or supporting microformats, please add them to this page, link to their [[implementors]], and list what specific microformats they support.

When you find an implementation:
# Make sure that it is an implementation, rather an publishing example (e.g. [[hcard-examples-in-wild|hCard examples in the wild]], [[hcalendar-examples-in-wild|hCalendar examples]], et.c).
# Note the name of the ''tool or service'' and the name of the ''developer(s)'' who built it.
# Add a third level heading with the name of the tool/service to the Applications / Plugins / Services / Tools section below, sorted alphabetically by name of tool/service. e.g. <p><kbd><nowiki>=== Name of Tool ===</nowiki></kbd></p>
# Add a top level list item just below the heading with an external link to the tool/service, along with a link to evidence of their support for microformats, and mention (and locally link) each microformat that is supported. E.g. <p><kbd>* Link to tool/service, link to their blog post announcing support for e.g. <nowiki>[[hCard]] and [[hReview]]</nowiki></kbd></p>
# Add a nested list item and local to wiki hyperlink the Name of Developer to a fragment identifier in the [[implementors]] page, e.g. Apple Computer would be linked like this: <p><kbd><nowiki>** by [[implementors#Apple_Computer|Apple Computer]]</nowiki></kbd></p>
# Check to see if there is an entry for the developer in the [[implementors|list of implementors]], if not add them there. Add a link to the developer's home page followed by "has implemented microformats in:".
# In the entry for the developer, add a list item and local to wiki hyperlink the Name of Tool to a fragment identifier in this page, e.g. X2V would be linked like this: <p><kbd><nowiki>* [[implementations#X2V|X2V]]</nowiki></kbd></p>
# Save the page and make sure that each fragment ID local hyperlink when clicked scrolls you to the right spot (for the developer, and for the tool). Make any fix-up edits as necessary. That's it!

=== Implementation Details ===
If there are implementation details worth noting, add them them as nested list items under the item for the implementation itself. If the details subsection grows too big for a specific implementation, feel free to move the details to their own page and leave a link in place on the implementations page.

== Reporting Bugs ==
Similar to implementation details, in short, [[put-it-on-the-wiki]]. In particular, add bug reports, with URL(s) to a valid demonstrative test case(s) of course, to the listing of an implementation on this page, OR on the specific implementations wiki page (e.g. [[hcard-implementations]]). Please describe why you think it is a bug (user interface, cosmetic, violates a spec page, e.g. for problems parsing hCards, reference which part of [[hcard-parsing]] the implementation appears to not be following).

If you have a sense of urgency for getting that particular bug fixed in that implementation, you may email [http://microformats.org/discuss/ microformats-dev] with the URL of that implementation on the wiki page, and *summarize* the bug (the full description being on the wiki page instead).

== Formats ==
Most microformat specifications have an "implementations" section, e.g.:
*[[rel-tag#Implementations|rel-tag implementations]]
*[[vote-links#Implementations|vote-link implementations]]
*[[xoxo#Implementations|XOXO implementations]]

In addition, some microformat specifications have separate implementation pages:
*[[hcalendar-implementations|hCalendar implementations]]
*[[hcard-implementations|hCard Implementations]]
*[[xfn-implementations|XFN implementations]]

== Applications / Plugins / Services / Tools ==
This is an alphabetical listing of all applications, plugins (grouped with their app/tool), services and tools that implement microformats, along with the list of microformats that are supported, and the company and/or developers responsible for it.

As a user, the implementations listed below will automatically help you use microformats and help your data portability and interoperability with other apps and services.

Please help complete this list! If you know of additional apps/plugins/services/tools that support microformats, please add them!

Note: this section is only for listing specific ''implementations''. The list of ''implementors'' is in the [[implementors#Companies / Developers / Organizations|Companies / Developers / Organizations]] section on the [[implementors]] page.

Alphabetically:

=== .Mac Webmail ===
* The [http://www.mac.com/webmail .Mac Webmail] ''service'' now [http://factoryjoe.com/blog/2006/10/28/apple-embraces-microformats-in-new-mac-webmail/ supports hcard].
** by [[implementors#Apple_Computer|Apple Computer]]

=== AlchemyPoint ===
* [http://www.orch8.net/ AlchemyPoint] is a structured web / mashup platform that supports parsing hCard, rel-tag and other microformats.
** by [[implementors#Orchestr8|Orchestr8]]

=== Backnetwork ===
* [http://backnetwork.com/ Backnetwork] is a community networking tool for events that supports [[hCard]], [[hCalendar]], and [[XFN]].
** by [[implementors#Glenn_Jones|Glenn Jones]] of [[implementors#Madgex|Madgex]].

=== Blinksale ===
* [http://blinksale.com Blinksale] uses [[hcard|hCard]] standard throughout for people and companies.

=== BlogMatrix ===
* [http://www.blogmatrix.com BlogMatrix] - user information marked as [[hcard|hCard]], tag directories in [[xfolk]]/[[rel-tag]], enclosures are marked as [[rel-enclosure]].
** by [[implementors#David_Janes|David Janes]]

=== Blogmarks.net ===
* [http://www.blogmarks.net Blogmarks.net] publish user bookmarks in [[xfolk]]/[[rel-tag]].

=== Bugzilla ===

* [http://www.bugzilla.org/ Bugzilla] [http://www.bugzilla.org/status/2007-08-23.html 3.1.1] includes some microformats on show_bug.cgi and a few other places.

=== cmSiteNavigation ===
* [http://www.christophm.de/software/firefox/cmSiteNavigation/ cmSiteNavigation] extension for Firefox make use of links marked with a [[existing-rel-values|"rel" value]], and parses additional link types also.
** This seems to use rel values defined in the HTML 4 spec, not microformats. This is more of a [[posh|POSH]] implementation than a [[microformats]] implementation.

=== Community Server ===
* [http://communityserver.org Community Server] supports tagging posts with [[rel-tag]], implements [[rel-nofollow]] on links in comments, and allows users to create link lists using [http://gmpg.org/xfn/ XFN].

=== Conferenceer ===
* Built for SXSW 2007, [http://sxsw07.conferenceer.com/ Conferenceer] supports hcalendar and hcard.

=== Citycita===
* [http://www.citycita.org Citycita] supports [[hCal|hCal]] in all event pages for local social groups.
** by [[implementors#Rubio_Jamin|Rubio Jamin]]

=== Cork'd ===
* [http://corkd.com Cork'd] supports [[hcard|hCard]] for user profiles, [[hreview|hReview]] for wine reviews, along with [[rel-tag]] for tagging wines as announced in [http://www.simplebits.com/notebook/2006/06/10/wineformats.html Pairing Wine and Microformats]
** by [[implementors#Dan_Cederhold|Dan Cederholm]]

=== Delicious Generation ===
* [http://deliciousgeneration.com/ Delicious Generation] supports [[hCal|hCal]] for the event and [[hcard|hCard]] for sponsors and people.
** by [[implementors#Chris_Messina|Chris Messina]]

=== Digg ===
* [http://digg.com/ Digg] supports [[hcard|hCards]] for profiles and rel-me for identity consolidation (though they currently mix rel-nofollow with rel-me, negating these links).

=== Dreamweaver ===
==== Microformats Extensions ====
* [http://www.webstandards.org/action/dwtf/microformats Dreamweaver Microformats Extensions] ([http://allinthehead.com/beta/microformats.mxp.zip download]) support authoring [[hcard|hCard]], [[hcalendar|hCalendar]], [http://gmpg.org/xfn XFN], [[rel-tag]], [[rel-license]] as [http://allinthehead.com/retro/282/microformats-in-dreamweaver announced by Drew]
** by [[implementors#Drew_Mclellan|Drew McLellan]]

=== Drupal ===
==== Upcoming module for Drupal ====
* [http://hybernaut.com/upcoming-module Drupal Upcoming.org syndication module] emits [[hcalendar|hCalendar]]
** by [[implementors#Brian_Del_Vecchio|Brian Del Vecchio]]

=== Eventful ===
* [http://eventful.com Eventful] supports [[hcalendar|hCalendar]] for over 1,000,000 event listings and [[hcard|hCard]] for venues.

=== Facebook ===
* [http://facebook.com/ Facebook] supports [[hcard|hCard]] for some public profiles '''(example needed)'''.
* There is also an [http://www.facebook.com/apps/application.php?id=2400943827&ref=s hCard application] (a plug-in) for Facebook users.
* Note also the [http://www.facebook.com/group.php?gid=2374732285 microformats group], which Facebook users who support microformats can join.

=== Ficlets ===
* [http://ficlets.com Ficlets] supports [[hcard]] for author data and [[hatom]] for stories and lists of stories.
** [http://sixtwothree.org Jason Garber] and [http://lawver.net Kevin Lawver] for [http://aol.com AOL]

=== Firefox ===
* See [[firefox-extensions]]

=== Flickr People ===
* [http://flickr.com/ Flickr]'s profiles on its people pages supports both [[hcard|hCard]] and [http://gmpg.org/xfn XFN].
** by [[implementors#Cal_Henderson|Cal Henderson]]
**[http://flickr.com/people/tantek example]

=== Flickr Photos ===
* [http://flickr.com/map/ Flickr's geo tagged photos] are marked up with the [[geo]] microformat.

=== Flock Web Browser ===
* The [http://flock.com Flock web browser] supports the [[rel-tag]] microformat.
** by [[implementors#Flock|Flock]]

=== Google Search ===
* Consumes microformats via rich snippets: [[search engines | wiki page]], [http://www.google.com/support/webmasters/bin/answer.py?answer=99170 rich snippets docs]
* supports [[rel-nofollow]]
** by [[implementors#Google|Google]]

=== Google Blogger ===
* [http://blogger.com/ Blogger] supports [[hatom|hAtom]] (citation to blog post needed - 2007)
** by [[implementors#Google|Google]]

=== Google Creative Commons Search ===
* [http://www.google.com/webhp?as_rights=(cc_publicdomain%7Ccc_attribute%7Ccc_sharealike%7Ccc_noncommercial%7Ccc_nonderived) Google Creative Commons Search] - supports [[rel-license]]
** by [[implementors#Google|Google]]

=== Google Maps ===
* [http://maps.google.com/ Google Maps] supports [[hcard|hCard]] (see [http://googlemapsapi.blogspot.com/2007/06/microformats-in-google-maps.html 2007-06-31 announcement by Google])
* Google maps also allows reviewers and map creators to [http://maps.google.com/maps/me attach a public profile], which includes hCard and rel="me' XFN markup. See [http://google-latlong.blogspot.com/2007/10/put-yourself-on-map.html 2007-10-17 announcement]. Sample profile: [http://maps.google.com/maps/user?uid=109581870574956225297 Kevin Marks].
** by [[implementors#Google|Google]]
**Unfortunately, [http://microformats.org/discuss/mail/microformats-discuss/2007-July/010311.html Google Map's implementation is broken]. [http://microformats.org/discuss/mail/microformats-discuss/2007-August/010457.html Google are aware; a fix is awaited].
** Also, there is no hCard nor any XFN rel values on the [http://maps.google.com/maps/user?uid=109581870574956225297 sample profile] itself, it appears to include a [http://maps.google.com/maps/c/widgets/ProfileViewer?js=RAW&maximize=true&hide=false&width=40&noTitle=true&theme=theme_2&service=local&uid=109581870574956225297&height=0&background=transparent&serverbased=true&border=NONE&eventCallback=ParentStub1192999211538&zx=dc574o15j0wrv frame] which then has an hCard and rel="me" to the user's blog.

=== Gravatar Commenters as hCards ===
* [http://thedredge.org Andy Hume] added code to his blogging software to automatically mark-up the names and URLs of commenters on his blog with [[hcard|hCard]].
** by [[implementors#Andy_Hume|Andy Hume]]
** Andy - any chance of open sourcing your code to turn Gravatars into hCards?

=== Greasemonkey ===
* [http://greasemonkey.makedatamakesense.com/google_hcalendar/ Google hCalendar] - Adds hCalendar data to Google Calendar.
* [http://www.nickpeters.net/?p=35 Social xFolk] - Adds xFolk links to social bookmarking sites del.icio.us and ma.gnolia.
* [http://monkeyformats.org/ Monkeyformats] - a collection of GreaseMonkey scripts that add actual hCard and hCalendar microformat markup to several international phone directories.

=== hCalendar creator ===
* [http://microformats.org/code/hcalendar/creator hCalendar creator] (originally [http://theryanking.com/microformats/hcalendar-creator.html published by Ryan King]) is a javascript form for creating [[hcalendar|hCalendar]] events.
** by [[implementors#Ryan_King|Ryan King]]

=== hCard to Gmail Service ===
* [http://jkg3.com/Journal/81/bookmarklet hCard to gmail] is a bookmarklet / service which will convert hCard formatted data to the .CSV file for importing to gmail.
** by [[implementors#Jamie_Knight|Jamie Knight]]

=== hCard creator ===
* The open source [http://microformats.org/code/hcard/creator hCard creator] (originally [http://tantek.com/microformats/hcard-creator.html published by Tantek]) is a very simple, yet illustrative, open source user interface / form / script which creates an [[hcard|hCard]] in real-time as you type in a set of contact information.
** by [[implementors#Tantek_Çelik|Tantek Çelik]]

=== Helios Calendar ===
* [http://www.helioscalendar.com/ Helios Calendar] is a commercial PHP script for event publishing that [http://www.helioscalendar.com/index.php?com=features&d=1 supports hCalendar and hCard].
** by [[implementors#Refresh Web Development|Refresh Web Development]]

=== hKit Microformats Toolkit for PHP5 ===
* [http://hkit.googlecode.com/ hKit Microformats Toolkit for PHP5] as [http://allinthehead.com/retro/291/hkit-microformats-toolkit-for-php announced by Drew McLellan]. See also [[hkit|hKit on this wiki]].

=== hReview creator ===
* [http://microformats.org/code/hcalendar/creator hReview creator] (originally [http://theryanking.com/microformats/hreview-creator.html published by Ryan King]) is a javascript form for creating [[hreview|hReviews]].
** by [[implementors#Ryan_King|Ryan King]]

=== iChat buddy list to hCards ===
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards.
** by [[implementors#Tantek_Çelik|Tantek Çelik]]

=== Internet Explorer ===
* See [[internet-explorer-extensions]]

=== JobiJoba ===
* [http://www.jobijoba.com JobiJoba : moteur de recherche emploi] parses and supports [[hCard|hCard]] and [[rel-tag|rel-tag]] for over 40,000 job listings.

=== JSCalendar ===
* [http://web.mit.edu/glasser/www/JSCalendar/ JSCalendar] parses [[hcalendar|hCalendar]] and produces a displayable HTML table/CSS-based calendar.

=== Konqueror ===
* [http://www.konqueror.org/ Konqueror] - [http://flickr.com/photos/factoryjoe/68755089/ supports] [[hcard|hCard]]

=== Last.fm ===
* [http://last.fm Last.fm] - [http://factoryjoe.com/blog/2006/10/31/lastfm-adds-support-for-hcalendar/ Last.fm supports] [[hcalendar|hCalendar]]

=== LinkedIn ===
* [http://www.linkedin.com LinkedIn] - LinkedIn includes [[hcard|hCard]] and [[xfn|XFN]] on contacts, [[hresume|hResume]] for public profiles and [[hreview|hReview]] on service provider recommendations

=== Live Clipboard ===
* [http://spaces.live.com/editorial/rayozzie/demo/liveclip/liveclipsample/techPreview.html Live Clipboard Technical Introduction]
* [http://spaces.live.com/editorial/rayozzie/demo/liveclip/liveclipsample/clipboardexample.html Live Clipboard Example]

=== LiveJournal ===
* [http://www.livejournal.com LiveJournal]
** supports tagging posts with [[rel-tag]]
** supports [[hcard-supporting-user-profiles|hCard user profiles]] and [[XFN]] ([http://community.livejournal.com/lj_releases/24768.html 2007-09-27 release #15]).
** by [[implementors#Six Apart|Six Apart]] (at the time of implementation)

=== LJFind ===
* [http://www.ljfind.com LJ-Find] - LJFind supports tagging posts with [[rel-tag]].

=== LouderVoice ===
* [http://www.loudervoice.com Publishes and aggregates hreview content] - The LouderVoice site provides a variety of tools to publish hreview to blogs and it also aggregates hreview content from any registered RSS Feed so that users can search/rate/collect distributed reviews.

=== Ma.gnolia ===
* [http://ma.gnolia.com Ma.gnolia] has wide [http://wiki.ma.gnolia.com/Ma.gnolia_Feeds_Guide#Microformats support for a variety of microformats] including [[rel-tag]], [[xfolk]], [[hreview]], [[xfn]] and [[hcard]].

=== Mash Maker ===
* [http://mashmaker.intel.com/ Intel Mash Maker] supports microformats as of 2007-11-15 (see [http://softwareblogs.intel.com/2007/11/15/bookmarks-microformats-and-bug-fixes/ announcing blog post])
** by [[implementors#Intel|Intel]]

=== Maxthon ===
[http://maxthon.com Maxthon] is a browser for Microsoft Windows that uses the Trident rendering engine and provides additional user interface. Maxthon has built and published a plugin for their browser that recognizes microformats in web pages and allows users to take action with them, similar to Operator for [[Firefox]].
* [http://forum.maxthon.com/index.php?showtopic=65408 Microformats Button Version 1.0.0 Release Candidate 1]
** Description: "Microformats Button extracts Microformats from websites and allows you to export the data to vCard, vCalendar, Google Maps, Yahoo Maps and other sites."

=== Microformat Base ===
* [http://randomchaos.com/microformats/base/ Microformat Base]
** by [[implementors#Scott Reynen|Scott Reynen]]

=== Microformat Bookmarklet Overlay ===
* [http://leftlogic.com/info/articles/microformats_bookmarklet Microformats Bookmarklet] for Safari, Firefox and Camino, supports [[hcard|hCard]] and [[hcalendar|hCalendar]] and allows the user to import individual microformats on the fly.
** by [[implementors#Remy_Sharp|Remy Sharp]]

=== Microformat Parser for Ruby ===
* [http://blog.labnotes.org/2005/11/20/microformat-parser-for-ruby/ Microformat Parser for Ruby]
** by [[implementors#Assaf Arkin|Assaf Arkin]]

=== Movable Type ===
* [http://movabletype.org Movable Type] (MT) open source blogging software supports:
** [[XFN]] [[rel-me]] "other profiles" UI, and [[hAtom]] activity streams (as of MT v4.1 - see [http://www.sixapart.com/about/news/2008/01/time_for_action.html announcement] and [http://www.movabletype.org/2008/01/building_action_streams.html technical details].)
** by [[implementors#Six Apart|Six Apart]]
See also [[movable-type]].

=== MyMap.yam.com ===
* support [[geo]] microformat in the POI page. example: [http://mymap.yam.com/place/point/charleschuang/6695/ a book store in Tamsui].

=== National eXtension Initiative ===
* [http://www.extension.org/ eXtension Home] - content marked-up with [[hatom|hAtom]] and events marked-up as [[hcalendar|hCalendar]] entries.
** by [[implementors#James E. Robinson, III|James E. Robinson, III]]

=== Nature Network Boston ===
* [http://network.nature.com/boston/ Nature Network Boston], a social networking community for scientists, supports [[reltag|rel-tag]], [[hcard|hCard]] for user profiles and [[hcalendar|hCalendar]] for marking up events across the site.
** by [[implementors#Nature Publishing Group|Nature Publishing Group]]

=== Nature Protocols ===
* [http://www.nature.com/nprot/ Nature Protocols], a forum for scientists to upload and comment on protocols, supports [[hcard|hCard]] and [[XOXO]].
** by [[implementors#Nature Publishing Group|Nature Publishing Group]]

=== NetNewsWire ===
*[http://www.newsgator.com/Individuals/NetNewsWire/ NetNewsWire] is an easy-to-use RSS and Atom reader for your Mac. NetNewsWire 3.0 detects, extracts and converts hcard and hcalendar data from feed entries.
** by [[implementors#NewsGator|NewsGator]]

=== Netscape Navigator ===
* Version 9.0+ supports [[Firefox extensions]], e.g. [[Operator]]:
** [http://notizblog.org/2007/10/21/operator-unter-navigator-90/ Operator unter Navigator 9.0]

=== Nutch ===
* [http://www.mail-archive.com/nutch-dev@lucene.apache.org/msg01295.html rel-nofollow support added]
* [http://www.mail-archive.com/nutch-commits@lucene.apache.org/msg01014.html rel-tag support checked in]

=== ODEO ===
* [http://odeo.com/ ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html noted] that they support microformats: [[rel-tag]], [[rel-enclosure]], [http://gmpg.org/xfn XFN].

=== Optimus ===
*[http://microformatique.com/optimus/ Optimus]. Output formats: XML, JSON, JSON-P.

=== phpMicroformats ===
* [http://enarion.net/phpmicroformats/ phpMicroformats] is a PHP class library that generates microformat entries for [[hcalendar|hCalendar]] and [[hcard|hCard]]. It is released under GPL.

=== Portable Social Network Profile Parser ===
* [http://lab.backnetwork.com/ufXtract-psn/ Portable Social Network Profile Parser] implements parsing of [[hCard]], [[XFN]], and in particular [[rel-me]] for [[identity-consolidation]] for [[social-network-portability]].
** by [[implementors#Glenn_Jones|Glenn Jones]] of [[implementors#Madgex|Madgex]].

=== PostNuke ===
''[http://www.postnuke.com PostNuke] is an Application Framework/Content Management Systeme''
* [http://www.pagesetter.net/index.php?module=pagesetter&func=viewpub&tid=4&pid=96 hCards4Pagesetter] - hCards Publication Type for the PostNuke module "Pagesetter"
* [http://www.pagesetter.net/index.php?module=pagesetter&func=viewpub&tid=4&pid=97 hCalendar4Pagesetter] - hCalendar Publication Type for the PostNuke module "Pagesetter"
* [http://www.pagesetter.net/index.php?module=pagesetter&func=viewpub&tid=4&pid=98 hReview4Pagesetter] - hReview Publication Type for the PostNuke module "Pagesetter"
* [http://noc.postnuke.com/frs/?group_id=256&release_id=477 Blogroll] - XFN Block/Modul
* [http://noc.postnuke.com/frs/?group_id=256&release_id=628 nofollow] - nofollow Hook

=== Pownce ===
*[http://pownce/ Optimus]. Output formats: XML, JSON, JSON-P.

=== Profiler ===
* [http://microformat.makedatamakesense.com/profiler/ Profiler] works as a proxy service adding microformat profiles to documents that appear to contain microformats.

=== Realcom HAKONE for Notes ===
* [http://www.realcom.co.jp/en/hakone2.html HAKONE for Notes] - supports [[hCard|hCard]]
** by [[implementors#Realcom|Realcom]]

=== Realcom KnowledgeMarket ===
* [http://www.realcom.co.jp/en/enterprisesuite2.html KnowledgeMarket] - supports [[hCard|hCard]]
** by [[implementors#Realcom|Realcom]]

=== RFC2629.xslt ===
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate [[hcard|hCard]] information ([http://ietf.org/rfc/rfc2629 RFC2629] in an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])

=== Salesforce ===
* [http://salesforce.com Salesforce] [http://flickr.com/photos/kingsleyj/175689109/ supports] [[hcard|hCard]]
** by [http://flickr.com/people/kingsleyj/ Kingsley Joseph]
==== Spanning Salesforce ====
* [http://spanningsalesforce.com/ Spanning Salesforce] supports [[hcalendar|hCalendar]].

=== Sivitools ===
<blockquote>
Sivitols is a Java library for microformats. Currently only the xFolk RC1 standard is implemented, but additional microformat support is planned. This library is being written and maintained for a tag sharing project undertaken by Video Vertigo.
</blockquote>
[http://blog.blip.tv/blog/microformats/ Annoucement], [http://pokkari.com/microformat/javadoc/ Docs]

=== Safari Microformats plugin ===
<blockquote>
The Safari Microformats plugin notifies you when the author of the website has published Microformats and allows you to easily import hCards and hCalendars in Address Book and iCal. This plugin was inspired by the idea and mockup of Jon Hicks.
</blockquote>
[http://www.zappatic.net/safarimicroformats/ Safari Microformats Plugin]
* Note - the latest version, 3.1, currently only works w/Mac OS 10.5 (Leopard)

=== SPRACI ===
* [http://www.spraci.com SPRACI] - nightlife/events - [[hcalendar|hCalendar]] published in events listings, aggregator can read hCalendar

=== stuckUnstuck ===
* [http://stuckunstuck.com stuckUnstuck] supports [[hcard|hCard]] and [[hatom|hatom]].

<div id="cognition">
=== Swignition ===
* [http://buzzword.org.uk/swignition/ Swignition] is a Perl framework and script (usable online via CGI, and downloadable for local use) that supports:
** [[hatom|hAtom]]
** [[haudio|hAudio]]
** [[User:TobyInk/hcalendar-1.1|hCalendar]]
** [[hcard|hCard]], [[adr]], [[geo]], [[jCard]], [[xfn|XFN]] (1.0 and 1.1) and [http://xen.adactio.com XEN]
** [[hresume|hResume]]
** [[hreview|hReview]]
** [[rel-tag]], [[rel-enclosure]] and [[rel-license]]
** [[figure]]
** [[measure]]
** [[species]]
** [[xfolk|xFolk]]
** [[xoxo|XOXO]]
** several non-microformat semantic HTML techniques, including GRDDL, RDFa, eRDF and COinS.
** by [[implementors#Toby_Inkster|Toby Inkster]]
</div>

=== Technorati Contacts Feed Service ===
* [http://feeds.technorati.com/contacts/ Technorati Contacts Feed Service] is a deployment of [[implementations#X2V|X2V]] to convert [[hcard|hCards]] to vCard (.vcf) format.
** by [[implementors#Technorati|Technorati]]

=== Technorati Events Feed Service ===
* [http://feeds.technorati.com/events/ Technorati Events Feed Service] is a deployment of [[implementations#X2V|X2V]] to convert [[hcalendar|hCalendar]] events to iCalendar (.ics) format.
** by [[implementors#Technorati|Technorati]]

=== Technorati Microformats Search ===
* Technorati [http://kitchen.technorati.com/search/ Microformats Search]. Search for contacts ([[hcard|hCard]]), events ([[hcalendar|hCalendar]]), or reviews ([[hreview|hReview]]) published on blogs and other web sites.
** by [[implementors#Ryan_King|Ryan King]]
** first version (2006 May) by [[implementors#Tantek_Çelik|Tantek Çelik]], [[implementors#Ryan_King|Ryan King]], [[implementors#Kevin_Marks|Kevin Marks]], [[implementors#Josh_Smith|Josh Smith]]

=== Technorati Search ===
* [http://technorati.com/ Technorati] [http://technorati.com/search Search] supports and handles both [[vote-links]] and [[rel-nofollow]] for indicating whether a link should have any/positive/negative weighting towards the destination.
** by [http://technorati.com/about/staff.html Technorati Staff]

=== Technorati Tags ===
* [http://technorati.com/tags/ Technorati Tags] pages aggregate blog posts tagged with the [[rel-tag]] open tagging standard, in addition to recent tagged photos and links.

=== Textpattern ===
==== Microformats Plugin ====
* [http://placenamehere.com/TXP/pnh_mf/ Textpattern Microformats Plugin] supports authoring [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [http://gmpg.org/xfn XFN], [[rel-tag]], [[rel-license]] in the [http://www.textpattern.com/ Textpattern] CMS/blogging tool
** by [http://placenamehere.com/ Chris Casciano]

=== Tomota ===
* The [http://www.tomota.de Tomota] allows import, export and conversion from and to hcards.
** by [[implementors#RalfEngels|Ralf Engels]]

=== Transformr ===
* [http://code.google.com/p/transformr/ Transformr] Is a microformats transformation toolkit. Transformr is also available as a [http://transformr.co.uk/ webservice]
** by [[implementors#Martin_McEvoy|Martin McEvoy]]

=== TYPO3 ===
* [http://www.typo3.com TYPO3]
==== Getting Started =====
* [http://typo3.org TYPO3 Developer Ressource]
* [http://www.acqal.com/a/article/getting-help-with-typo3-98.html Getting Help With TYPO3]
==== tt_address extension====
* [http://typo3.org/extensions/repository/view/tt_address/2.0.1/ tt_address] - hCard support with the tt_address extension version 2.0.0
** by [[implementors#Ingo_Renner|Ingo Renner]]
==== TIMTAB extension====
* [http://typo3.org/extensions/repository/view/timtab/0.5.11/ TIMTAB] - XFN support for blogrolls with the TIMTAB weblog extension for TYPO3
** by [[implementors#Ingo_Renner|Ingo Renner]]

=== Tweeterboard ===
* Tweeterboard supports [hcard|hCard]], and [http://gmpg.org/xfn XFN] on profile pages ([http://tweeterboard.com/user/missrogue example]).

=== Twitter ===

* [http://twitter.com Twitter] [http://twitter.com/al3x/statuses/53982402 supports] [[hatom|hAtom]], [[hcard|hCard]], and [http://gmpg.org/xfn XFN].
** hCards for groups are marked up with "fn" not "fn org". See, for example, [http://twitter.com/microformats microformats on Twitter]
** Improper address mark-up (no child properties; though this may be all that can be achieved, if the user enters a value like "Birmingham, England")
** Uses <code>class="label"</code> for non-hCard purpose.

=== ufXtract ===
* [http://lab.backnetwork.com/ufXtract/ ufXtract] implements [[parsing]] of microformats such as [[hCard]] and [[XFN]].
** by [[implementors#Glenn_Jones|Glenn Jones]] of [[implementors#Madgex|Madgex]]. See [http://www.glennjones.net/Post/831/ufXtractmicroformatsparser.htm blog post announcement].

=== Upcoming.org ===
* [http://upcoming.org Upcoming.org] - hCalendar support in events listings and individual events.
** by [[implementors#Andy_Baio|Andy Baio]], [[implementors#Leonard_Lin|Leonard Lin]], [[implementors#Gordon_Luk|Gordon Luk]]

=== vCardExplorer ===
* [http://vcardexplorer.corefault.de/ vCardExplorer for MacOSX] - browses local vcards and converts hcards from URLs.

=== VIREL Microformats Search Engine===
* [http://www.virel.de/ microformats search engine] - website friendly crawler. searches for public informations embedded as microformats in web pages.

=== WindowsLiveWriter ===
* [[implementors#Microsoft|Microsoft's]] WindowsLiveWriter (WLW) [http://gallery.live.com/liveItemDetail.aspx?li=9751e563-1408-4fc3-8028-bd4351edb1fb&l=8 event plugin] supports [[hcalendar|hCalendar]].

=== WordPress ===
*See [[wordpress|WordPress]].

=== X2V ===
* Brian Suda has created several XSLT files to extract microformats from HTML. From that the [http://suda.co.uk/projects/X2V/ X2V] webservice/favelet emerged. The XSLT and favelet extracts [[hcard|hCard]] and to produces .vcf (vCard) files and [[hcalendar|hCalendar]] to produce .ics (iCal) files. Also in the labs is a universal XMDP validator and a site-wide search spider that recognizes 'no-follow', 'license' and other microformats so they can be used in a more semantic way when displaying search results.
** by [[implementors#Brian_Suda|Brian Suda]]

=== XWiki ===
* [http://xwiki.org XWiki] (as of [http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWiki10Beta5 version 10Beta5]) publishes the user profiles using [[hcard | hCard]], the events in the calendar application using [[hCalendar | hCalendar]], the blog entries using [[hAtom | hAtom]] and homepage links using [[rel-home | rel-home]].

=== xfn-spider ===

* [http://sphinx.net.ru/hg/xfn-spider xfn-spider] — simple crawler extracting microformats with XSLT ([http://sphinx.net.ru/blog/entry/simple-microformat-xslt-extraction/ Original article in Russian] circa summer 2007) and exporting information to OPML feedlist, tag cloud etc.

* See [http://services.alphaworks.ibm.com/manyeyes/view/SNnqRHsOtha6i5-m6iGTH2- XFN visualization] example at IBM's Many Eyes made using data extracted with xfn-spider

=== Yahoo Creative Commons Search ===
* [http://search.yahoo.com/cc/ Yahoo Creative Commons Search] - supports [[rel-license]] specifically to search for Creative Commons licensed content.

=== Yahoo Local ===
* [http://local.yahoo.com Yahoo local] supports [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]].

=== Yahoo Tech ===
* [http://tech.yahoo.com Yahoo! Tech] supports [[hreview|hReview]].

=== Yahoo UK Movies ===
* [http://movies.yahoo.co.uk Yahoo! UK Movies] supports [[hreview|hReview]].
** by Mark Norman Francis

=== Yalwa - Local directory ===
* [http://www.yalwa.com/ Yalwa - Local Directory] supports [[hreview|hReview]].
Example: [http://wiesbaden.yalwa.de/ID_102318221/Yalwa-GmbH.html Yalwa Listing]

=== Yedda ===
* [http://yedda.com Yedda] supports [[hcard|hCard]] for exposing users information, [[hatom|hAtom]] for exposing data that is already exposed via feeds (like list of questions and answers) and [[rel-tag|rel-tag]] for every tag used to tag questions and users.

== Validators ==

See [[debugging-tools]].

==Search engines==
See [[search-engines]]

== Companies / Developers / Organizations ==
See [[implementors]]

The following have been moved from the sections above due to problems, stated below:

=== Web Essentials ===
* [http://we05.com/ Web Essentials] - supports [[hcard|hCard]] and [[hcalendar|hCalendar]], e.g. in their [http://we05.com/presenters.cfm list of presenters] and [http://we05.com/program.cfm program schedule].
** John McKerrell tried to look at the site on 24th October 2006 but could not access the site, server didn't seem to be up.
** As of 2008-02-22, domain is expired. [[User:AndyMabbett|Andy Mabbett]] 05:12, 22 Feb 2008 (PST)

== Other ==
Some notes on initial thoughts around [[implementation-guidelines|Guidelines and Strategies for Implementing Microformats]]

implementations

2009-05-18T16:39:55Z

Kavi: /* Google Search */

<entry-title>Microformats Implementations</entry-title>
{{TOC-right}}
This page lists the applications, plugins, sample code, services, tools that produce or consume microformats.

== help improve this page ==
This is only a partial list. If you know other services or tools for or supporting microformats, please add them to this page, link to their [[implementors]], and list what specific microformats they support.

When you find an implementation:
# Make sure that it is an implementation, rather an publishing example (e.g. [[hcard-examples-in-wild|hCard examples in the wild]], [[hcalendar-examples-in-wild|hCalendar examples]], et.c).
# Note the name of the ''tool or service'' and the name of the ''developer(s)'' who built it.
# Add a third level heading with the name of the tool/service to the Applications / Plugins / Services / Tools section below, sorted alphabetically by name of tool/service. e.g. <p><kbd><nowiki>=== Name of Tool ===</nowiki></kbd></p>
# Add a top level list item just below the heading with an external link to the tool/service, along with a link to evidence of their support for microformats, and mention (and locally link) each microformat that is supported. E.g. <p><kbd>* Link to tool/service, link to their blog post announcing support for e.g. <nowiki>[[hCard]] and [[hReview]]</nowiki></kbd></p>
# Add a nested list item and local to wiki hyperlink the Name of Developer to a fragment identifier in the [[implementors]] page, e.g. Apple Computer would be linked like this: <p><kbd><nowiki>** by [[implementors#Apple_Computer|Apple Computer]]</nowiki></kbd></p>
# Check to see if there is an entry for the developer in the [[implementors|list of implementors]], if not add them there. Add a link to the developer's home page followed by "has implemented microformats in:".
# In the entry for the developer, add a list item and local to wiki hyperlink the Name of Tool to a fragment identifier in this page, e.g. X2V would be linked like this: <p><kbd><nowiki>* [[implementations#X2V|X2V]]</nowiki></kbd></p>
# Save the page and make sure that each fragment ID local hyperlink when clicked scrolls you to the right spot (for the developer, and for the tool). Make any fix-up edits as necessary. That's it!

=== Implementation Details ===
If there are implementation details worth noting, add them them as nested list items under the item for the implementation itself. If the details subsection grows too big for a specific implementation, feel free to move the details to their own page and leave a link in place on the implementations page.

== Reporting Bugs ==
Similar to implementation details, in short, [[put-it-on-the-wiki]]. In particular, add bug reports, with URL(s) to a valid demonstrative test case(s) of course, to the listing of an implementation on this page, OR on the specific implementations wiki page (e.g. [[hcard-implementations]]). Please describe why you think it is a bug (user interface, cosmetic, violates a spec page, e.g. for problems parsing hCards, reference which part of [[hcard-parsing]] the implementation appears to not be following).

If you have a sense of urgency for getting that particular bug fixed in that implementation, you may email [http://microformats.org/discuss/ microformats-dev] with the URL of that implementation on the wiki page, and *summarize* the bug (the full description being on the wiki page instead).

== Formats ==
Most microformat specifications have an "implementations" section, e.g.:
*[[rel-tag#Implementations|rel-tag implementations]]
*[[vote-links#Implementations|vote-link implementations]]
*[[xoxo#Implementations|XOXO implementations]]

In addition, some microformat specifications have separate implementation pages:
*[[hcalendar-implementations|hCalendar implementations]]
*[[hcard-implementations|hCard Implementations]]
*[[xfn-implementations|XFN implementations]]

== Applications / Plugins / Services / Tools ==
This is an alphabetical listing of all applications, plugins (grouped with their app/tool), services and tools that implement microformats, along with the list of microformats that are supported, and the company and/or developers responsible for it.

As a user, the implementations listed below will automatically help you use microformats and help your data portability and interoperability with other apps and services.

Please help complete this list! If you know of additional apps/plugins/services/tools that support microformats, please add them!

Note: this section is only for listing specific ''implementations''. The list of ''implementors'' is in the [[implementors#Companies / Developers / Organizations|Companies / Developers / Organizations]] section on the [[implementors]] page.

Alphabetically:

=== .Mac Webmail ===
* The [http://www.mac.com/webmail .Mac Webmail] ''service'' now [http://factoryjoe.com/blog/2006/10/28/apple-embraces-microformats-in-new-mac-webmail/ supports hcard].
** by [[implementors#Apple_Computer|Apple Computer]]

=== AlchemyPoint ===
* [http://www.orch8.net/ AlchemyPoint] is a structured web / mashup platform that supports parsing hCard, rel-tag and other microformats.
** by [[implementors#Orchestr8|Orchestr8]]

=== Backnetwork ===
* [http://backnetwork.com/ Backnetwork] is a community networking tool for events that supports [[hCard]], [[hCalendar]], and [[XFN]].
** by [[implementors#Glenn_Jones|Glenn Jones]] of [[implementors#Madgex|Madgex]].

=== Blinksale ===
* [http://blinksale.com Blinksale] uses [[hcard|hCard]] standard throughout for people and companies.

=== BlogMatrix ===
* [http://www.blogmatrix.com BlogMatrix] - user information marked as [[hcard|hCard]], tag directories in [[xfolk]]/[[rel-tag]], enclosures are marked as [[rel-enclosure]].
** by [[implementors#David_Janes|David Janes]]

=== Blogmarks.net ===
* [http://www.blogmarks.net Blogmarks.net] publish user bookmarks in [[xfolk]]/[[rel-tag]].

=== Bugzilla ===

* [http://www.bugzilla.org/ Bugzilla] [http://www.bugzilla.org/status/2007-08-23.html 3.1.1] includes some microformats on show_bug.cgi and a few other places.

=== cmSiteNavigation ===
* [http://www.christophm.de/software/firefox/cmSiteNavigation/ cmSiteNavigation] extension for Firefox make use of links marked with a [[existing-rel-values|"rel" value]], and parses additional link types also.
** This seems to use rel values defined in the HTML 4 spec, not microformats. This is more of a [[posh|POSH]] implementation than a [[microformats]] implementation.

=== Community Server ===
* [http://communityserver.org Community Server] supports tagging posts with [[rel-tag]], implements [[rel-nofollow]] on links in comments, and allows users to create link lists using [http://gmpg.org/xfn/ XFN].

=== Conferenceer ===
* Built for SXSW 2007, [http://sxsw07.conferenceer.com/ Conferenceer] supports hcalendar and hcard.

=== Citycita===
* [http://www.citycita.org Citycita] supports [[hCal|hCal]] in all event pages for local social groups.
** by [[implementors#Rubio_Jamin|Rubio Jamin]]

=== Cork'd ===
* [http://corkd.com Cork'd] supports [[hcard|hCard]] for user profiles, [[hreview|hReview]] for wine reviews, along with [[rel-tag]] for tagging wines as announced in [http://www.simplebits.com/notebook/2006/06/10/wineformats.html Pairing Wine and Microformats]
** by [[implementors#Dan_Cederhold|Dan Cederholm]]

=== Delicious Generation ===
* [http://deliciousgeneration.com/ Delicious Generation] supports [[hCal|hCal]] for the event and [[hcard|hCard]] for sponsors and people.
** by [[implementors#Chris_Messina|Chris Messina]]

=== Digg ===
* [http://digg.com/ Digg] supports [[hcard|hCards]] for profiles and rel-me for identity consolidation (though they currently mix rel-nofollow with rel-me, negating these links).

=== Dreamweaver ===
==== Microformats Extensions ====
* [http://www.webstandards.org/action/dwtf/microformats Dreamweaver Microformats Extensions] ([http://allinthehead.com/beta/microformats.mxp.zip download]) support authoring [[hcard|hCard]], [[hcalendar|hCalendar]], [http://gmpg.org/xfn XFN], [[rel-tag]], [[rel-license]] as [http://allinthehead.com/retro/282/microformats-in-dreamweaver announced by Drew]
** by [[implementors#Drew_Mclellan|Drew McLellan]]

=== Drupal ===
==== Upcoming module for Drupal ====
* [http://hybernaut.com/upcoming-module Drupal Upcoming.org syndication module] emits [[hcalendar|hCalendar]]
** by [[implementors#Brian_Del_Vecchio|Brian Del Vecchio]]

=== Eventful ===
* [http://eventful.com Eventful] supports [[hcalendar|hCalendar]] for over 1,000,000 event listings and [[hcard|hCard]] for venues.

=== Facebook ===
* [http://facebook.com/ Facebook] supports [[hcard|hCard]] for some public profiles '''(example needed)'''.
* There is also an [http://www.facebook.com/apps/application.php?id=2400943827&ref=s hCard application] (a plug-in) for Facebook users.
* Note also the [http://www.facebook.com/group.php?gid=2374732285 microformats group], which Facebook users who support microformats can join.

=== Ficlets ===
* [http://ficlets.com Ficlets] supports [[hcard]] for author data and [[hatom]] for stories and lists of stories.
** [http://sixtwothree.org Jason Garber] and [http://lawver.net Kevin Lawver] for [http://aol.com AOL]

=== Firefox ===
* See [[firefox-extensions]]

=== Flickr People ===
* [http://flickr.com/ Flickr]'s profiles on its people pages supports both [[hcard|hCard]] and [http://gmpg.org/xfn XFN].
** by [[implementors#Cal_Henderson|Cal Henderson]]
**[http://flickr.com/people/tantek example]

=== Flickr Photos ===
* [http://flickr.com/map/ Flickr's geo tagged photos] are marked up with the [[geo]] microformat.

=== Flock Web Browser ===
* The [http://flock.com Flock web browser] supports the [[rel-tag]] microformat.
** by [[implementors#Flock|Flock]]

=== Google Search ===
* [http://google.com/ Google Search] - supports [[rel-nofollow]]
* Consumes microformats via rich snippets: [[search engines | wiki page]], [http://www.google.com/support/webmasters/bin/answer.py?answer=99170 rich snippets docs]
** by [[implementors#Google|Google]]

=== Google Blogger ===
* [http://blogger.com/ Blogger] supports [[hatom|hAtom]] (citation to blog post needed - 2007)
** by [[implementors#Google|Google]]

=== Google Creative Commons Search ===
* [http://www.google.com/webhp?as_rights=(cc_publicdomain%7Ccc_attribute%7Ccc_sharealike%7Ccc_noncommercial%7Ccc_nonderived) Google Creative Commons Search] - supports [[rel-license]]
** by [[implementors#Google|Google]]

=== Google Maps ===
* [http://maps.google.com/ Google Maps] supports [[hcard|hCard]] (see [http://googlemapsapi.blogspot.com/2007/06/microformats-in-google-maps.html 2007-06-31 announcement by Google])
* Google maps also allows reviewers and map creators to [http://maps.google.com/maps/me attach a public profile], which includes hCard and rel="me' XFN markup. See [http://google-latlong.blogspot.com/2007/10/put-yourself-on-map.html 2007-10-17 announcement]. Sample profile: [http://maps.google.com/maps/user?uid=109581870574956225297 Kevin Marks].
** by [[implementors#Google|Google]]
**Unfortunately, [http://microformats.org/discuss/mail/microformats-discuss/2007-July/010311.html Google Map's implementation is broken]. [http://microformats.org/discuss/mail/microformats-discuss/2007-August/010457.html Google are aware; a fix is awaited].
** Also, there is no hCard nor any XFN rel values on the [http://maps.google.com/maps/user?uid=109581870574956225297 sample profile] itself, it appears to include a [http://maps.google.com/maps/c/widgets/ProfileViewer?js=RAW&maximize=true&hide=false&width=40&noTitle=true&theme=theme_2&service=local&uid=109581870574956225297&height=0&background=transparent&serverbased=true&border=NONE&eventCallback=ParentStub1192999211538&zx=dc574o15j0wrv frame] which then has an hCard and rel="me" to the user's blog.

=== Gravatar Commenters as hCards ===
* [http://thedredge.org Andy Hume] added code to his blogging software to automatically mark-up the names and URLs of commenters on his blog with [[hcard|hCard]].
** by [[implementors#Andy_Hume|Andy Hume]]
** Andy - any chance of open sourcing your code to turn Gravatars into hCards?

=== Greasemonkey ===
* [http://greasemonkey.makedatamakesense.com/google_hcalendar/ Google hCalendar] - Adds hCalendar data to Google Calendar.
* [http://www.nickpeters.net/?p=35 Social xFolk] - Adds xFolk links to social bookmarking sites del.icio.us and ma.gnolia.
* [http://monkeyformats.org/ Monkeyformats] - a collection of GreaseMonkey scripts that add actual hCard and hCalendar microformat markup to several international phone directories.

=== hCalendar creator ===
* [http://microformats.org/code/hcalendar/creator hCalendar creator] (originally [http://theryanking.com/microformats/hcalendar-creator.html published by Ryan King]) is a javascript form for creating [[hcalendar|hCalendar]] events.
** by [[implementors#Ryan_King|Ryan King]]

=== hCard to Gmail Service ===
* [http://jkg3.com/Journal/81/bookmarklet hCard to gmail] is a bookmarklet / service which will convert hCard formatted data to the .CSV file for importing to gmail.
** by [[implementors#Jamie_Knight|Jamie Knight]]

=== hCard creator ===
* The open source [http://microformats.org/code/hcard/creator hCard creator] (originally [http://tantek.com/microformats/hcard-creator.html published by Tantek]) is a very simple, yet illustrative, open source user interface / form / script which creates an [[hcard|hCard]] in real-time as you type in a set of contact information.
** by [[implementors#Tantek_Çelik|Tantek Çelik]]

=== Helios Calendar ===
* [http://www.helioscalendar.com/ Helios Calendar] is a commercial PHP script for event publishing that [http://www.helioscalendar.com/index.php?com=features&d=1 supports hCalendar and hCard].
** by [[implementors#Refresh Web Development|Refresh Web Development]]

=== hKit Microformats Toolkit for PHP5 ===
* [http://hkit.googlecode.com/ hKit Microformats Toolkit for PHP5] as [http://allinthehead.com/retro/291/hkit-microformats-toolkit-for-php announced by Drew McLellan]. See also [[hkit|hKit on this wiki]].

=== hReview creator ===
* [http://microformats.org/code/hcalendar/creator hReview creator] (originally [http://theryanking.com/microformats/hreview-creator.html published by Ryan King]) is a javascript form for creating [[hreview|hReviews]].
** by [[implementors#Ryan_King|Ryan King]]

=== iChat buddy list to hCards ===
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards.
** by [[implementors#Tantek_Çelik|Tantek Çelik]]

=== Internet Explorer ===
* See [[internet-explorer-extensions]]

=== JobiJoba ===
* [http://www.jobijoba.com JobiJoba : moteur de recherche emploi] parses and supports [[hCard|hCard]] and [[rel-tag|rel-tag]] for over 40,000 job listings.

=== JSCalendar ===
* [http://web.mit.edu/glasser/www/JSCalendar/ JSCalendar] parses [[hcalendar|hCalendar]] and produces a displayable HTML table/CSS-based calendar.

=== Konqueror ===
* [http://www.konqueror.org/ Konqueror] - [http://flickr.com/photos/factoryjoe/68755089/ supports] [[hcard|hCard]]

=== Last.fm ===
* [http://last.fm Last.fm] - [http://factoryjoe.com/blog/2006/10/31/lastfm-adds-support-for-hcalendar/ Last.fm supports] [[hcalendar|hCalendar]]

=== LinkedIn ===
* [http://www.linkedin.com LinkedIn] - LinkedIn includes [[hcard|hCard]] and [[xfn|XFN]] on contacts, [[hresume|hResume]] for public profiles and [[hreview|hReview]] on service provider recommendations

=== Live Clipboard ===
* [http://spaces.live.com/editorial/rayozzie/demo/liveclip/liveclipsample/techPreview.html Live Clipboard Technical Introduction]
* [http://spaces.live.com/editorial/rayozzie/demo/liveclip/liveclipsample/clipboardexample.html Live Clipboard Example]

=== LiveJournal ===
* [http://www.livejournal.com LiveJournal]
** supports tagging posts with [[rel-tag]]
** supports [[hcard-supporting-user-profiles|hCard user profiles]] and [[XFN]] ([http://community.livejournal.com/lj_releases/24768.html 2007-09-27 release #15]).
** by [[implementors#Six Apart|Six Apart]] (at the time of implementation)

=== LJFind ===
* [http://www.ljfind.com LJ-Find] - LJFind supports tagging posts with [[rel-tag]].

=== LouderVoice ===
* [http://www.loudervoice.com Publishes and aggregates hreview content] - The LouderVoice site provides a variety of tools to publish hreview to blogs and it also aggregates hreview content from any registered RSS Feed so that users can search/rate/collect distributed reviews.

=== Ma.gnolia ===
* [http://ma.gnolia.com Ma.gnolia] has wide [http://wiki.ma.gnolia.com/Ma.gnolia_Feeds_Guide#Microformats support for a variety of microformats] including [[rel-tag]], [[xfolk]], [[hreview]], [[xfn]] and [[hcard]].

=== Mash Maker ===
* [http://mashmaker.intel.com/ Intel Mash Maker] supports microformats as of 2007-11-15 (see [http://softwareblogs.intel.com/2007/11/15/bookmarks-microformats-and-bug-fixes/ announcing blog post])
** by [[implementors#Intel|Intel]]

=== Maxthon ===
[http://maxthon.com Maxthon] is a browser for Microsoft Windows that uses the Trident rendering engine and provides additional user interface. Maxthon has built and published a plugin for their browser that recognizes microformats in web pages and allows users to take action with them, similar to Operator for [[Firefox]].
* [http://forum.maxthon.com/index.php?showtopic=65408 Microformats Button Version 1.0.0 Release Candidate 1]
** Description: "Microformats Button extracts Microformats from websites and allows you to export the data to vCard, vCalendar, Google Maps, Yahoo Maps and other sites."

=== Microformat Base ===
* [http://randomchaos.com/microformats/base/ Microformat Base]
** by [[implementors#Scott Reynen|Scott Reynen]]

=== Microformat Bookmarklet Overlay ===
* [http://leftlogic.com/info/articles/microformats_bookmarklet Microformats Bookmarklet] for Safari, Firefox and Camino, supports [[hcard|hCard]] and [[hcalendar|hCalendar]] and allows the user to import individual microformats on the fly.
** by [[implementors#Remy_Sharp|Remy Sharp]]

=== Microformat Parser for Ruby ===
* [http://blog.labnotes.org/2005/11/20/microformat-parser-for-ruby/ Microformat Parser for Ruby]
** by [[implementors#Assaf Arkin|Assaf Arkin]]

=== Movable Type ===
* [http://movabletype.org Movable Type] (MT) open source blogging software supports:
** [[XFN]] [[rel-me]] "other profiles" UI, and [[hAtom]] activity streams (as of MT v4.1 - see [http://www.sixapart.com/about/news/2008/01/time_for_action.html announcement] and [http://www.movabletype.org/2008/01/building_action_streams.html technical details].)
** by [[implementors#Six Apart|Six Apart]]
See also [[movable-type]].

=== MyMap.yam.com ===
* support [[geo]] microformat in the POI page. example: [http://mymap.yam.com/place/point/charleschuang/6695/ a book store in Tamsui].

=== National eXtension Initiative ===
* [http://www.extension.org/ eXtension Home] - content marked-up with [[hatom|hAtom]] and events marked-up as [[hcalendar|hCalendar]] entries.
** by [[implementors#James E. Robinson, III|James E. Robinson, III]]

=== Nature Network Boston ===
* [http://network.nature.com/boston/ Nature Network Boston], a social networking community for scientists, supports [[reltag|rel-tag]], [[hcard|hCard]] for user profiles and [[hcalendar|hCalendar]] for marking up events across the site.
** by [[implementors#Nature Publishing Group|Nature Publishing Group]]

=== Nature Protocols ===
* [http://www.nature.com/nprot/ Nature Protocols], a forum for scientists to upload and comment on protocols, supports [[hcard|hCard]] and [[XOXO]].
** by [[implementors#Nature Publishing Group|Nature Publishing Group]]

=== NetNewsWire ===
*[http://www.newsgator.com/Individuals/NetNewsWire/ NetNewsWire] is an easy-to-use RSS and Atom reader for your Mac. NetNewsWire 3.0 detects, extracts and converts hcard and hcalendar data from feed entries.
** by [[implementors#NewsGator|NewsGator]]

=== Netscape Navigator ===
* Version 9.0+ supports [[Firefox extensions]], e.g. [[Operator]]:
** [http://notizblog.org/2007/10/21/operator-unter-navigator-90/ Operator unter Navigator 9.0]

=== Nutch ===
* [http://www.mail-archive.com/nutch-dev@lucene.apache.org/msg01295.html rel-nofollow support added]
* [http://www.mail-archive.com/nutch-commits@lucene.apache.org/msg01014.html rel-tag support checked in]

=== ODEO ===
* [http://odeo.com/ ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html noted] that they support microformats: [[rel-tag]], [[rel-enclosure]], [http://gmpg.org/xfn XFN].

=== Optimus ===
*[http://microformatique.com/optimus/ Optimus]. Output formats: XML, JSON, JSON-P.

=== phpMicroformats ===
* [http://enarion.net/phpmicroformats/ phpMicroformats] is a PHP class library that generates microformat entries for [[hcalendar|hCalendar]] and [[hcard|hCard]]. It is released under GPL.

=== Portable Social Network Profile Parser ===
* [http://lab.backnetwork.com/ufXtract-psn/ Portable Social Network Profile Parser] implements parsing of [[hCard]], [[XFN]], and in particular [[rel-me]] for [[identity-consolidation]] for [[social-network-portability]].
** by [[implementors#Glenn_Jones|Glenn Jones]] of [[implementors#Madgex|Madgex]].

=== PostNuke ===
''[http://www.postnuke.com PostNuke] is an Application Framework/Content Management Systeme''
* [http://www.pagesetter.net/index.php?module=pagesetter&func=viewpub&tid=4&pid=96 hCards4Pagesetter] - hCards Publication Type for the PostNuke module "Pagesetter"
* [http://www.pagesetter.net/index.php?module=pagesetter&func=viewpub&tid=4&pid=97 hCalendar4Pagesetter] - hCalendar Publication Type for the PostNuke module "Pagesetter"
* [http://www.pagesetter.net/index.php?module=pagesetter&func=viewpub&tid=4&pid=98 hReview4Pagesetter] - hReview Publication Type for the PostNuke module "Pagesetter"
* [http://noc.postnuke.com/frs/?group_id=256&release_id=477 Blogroll] - XFN Block/Modul
* [http://noc.postnuke.com/frs/?group_id=256&release_id=628 nofollow] - nofollow Hook

=== Pownce ===
*[http://pownce/ Optimus]. Output formats: XML, JSON, JSON-P.

=== Profiler ===
* [http://microformat.makedatamakesense.com/profiler/ Profiler] works as a proxy service adding microformat profiles to documents that appear to contain microformats.

=== Realcom HAKONE for Notes ===
* [http://www.realcom.co.jp/en/hakone2.html HAKONE for Notes] - supports [[hCard|hCard]]
** by [[implementors#Realcom|Realcom]]

=== Realcom KnowledgeMarket ===
* [http://www.realcom.co.jp/en/enterprisesuite2.html KnowledgeMarket] - supports [[hCard|hCard]]
** by [[implementors#Realcom|Realcom]]

=== RFC2629.xslt ===
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate [[hcard|hCard]] information ([http://ietf.org/rfc/rfc2629 RFC2629] in an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])

=== Salesforce ===
* [http://salesforce.com Salesforce] [http://flickr.com/photos/kingsleyj/175689109/ supports] [[hcard|hCard]]
** by [http://flickr.com/people/kingsleyj/ Kingsley Joseph]
==== Spanning Salesforce ====
* [http://spanningsalesforce.com/ Spanning Salesforce] supports [[hcalendar|hCalendar]].

=== Sivitools ===
<blockquote>
Sivitols is a Java library for microformats. Currently only the xFolk RC1 standard is implemented, but additional microformat support is planned. This library is being written and maintained for a tag sharing project undertaken by Video Vertigo.
</blockquote>
[http://blog.blip.tv/blog/microformats/ Annoucement], [http://pokkari.com/microformat/javadoc/ Docs]

=== Safari Microformats plugin ===
<blockquote>
The Safari Microformats plugin notifies you when the author of the website has published Microformats and allows you to easily import hCards and hCalendars in Address Book and iCal. This plugin was inspired by the idea and mockup of Jon Hicks.
</blockquote>
[http://www.zappatic.net/safarimicroformats/ Safari Microformats Plugin]
* Note - the latest version, 3.1, currently only works w/Mac OS 10.5 (Leopard)

=== SPRACI ===
* [http://www.spraci.com SPRACI] - nightlife/events - [[hcalendar|hCalendar]] published in events listings, aggregator can read hCalendar

=== stuckUnstuck ===
* [http://stuckunstuck.com stuckUnstuck] supports [[hcard|hCard]] and [[hatom|hatom]].

<div id="cognition">
=== Swignition ===
* [http://buzzword.org.uk/swignition/ Swignition] is a Perl framework and script (usable online via CGI, and downloadable for local use) that supports:
** [[hatom|hAtom]]
** [[haudio|hAudio]]
** [[User:TobyInk/hcalendar-1.1|hCalendar]]
** [[hcard|hCard]], [[adr]], [[geo]], [[jCard]], [[xfn|XFN]] (1.0 and 1.1) and [http://xen.adactio.com XEN]
** [[hresume|hResume]]
** [[hreview|hReview]]
** [[rel-tag]], [[rel-enclosure]] and [[rel-license]]
** [[figure]]
** [[measure]]
** [[species]]
** [[xfolk|xFolk]]
** [[xoxo|XOXO]]
** several non-microformat semantic HTML techniques, including GRDDL, RDFa, eRDF and COinS.
** by [[implementors#Toby_Inkster|Toby Inkster]]
</div>

=== Technorati Contacts Feed Service ===
* [http://feeds.technorati.com/contacts/ Technorati Contacts Feed Service] is a deployment of [[implementations#X2V|X2V]] to convert [[hcard|hCards]] to vCard (.vcf) format.
** by [[implementors#Technorati|Technorati]]

=== Technorati Events Feed Service ===
* [http://feeds.technorati.com/events/ Technorati Events Feed Service] is a deployment of [[implementations#X2V|X2V]] to convert [[hcalendar|hCalendar]] events to iCalendar (.ics) format.
** by [[implementors#Technorati|Technorati]]

=== Technorati Microformats Search ===
* Technorati [http://kitchen.technorati.com/search/ Microformats Search]. Search for contacts ([[hcard|hCard]]), events ([[hcalendar|hCalendar]]), or reviews ([[hreview|hReview]]) published on blogs and other web sites.
** by [[implementors#Ryan_King|Ryan King]]
** first version (2006 May) by [[implementors#Tantek_Çelik|Tantek Çelik]], [[implementors#Ryan_King|Ryan King]], [[implementors#Kevin_Marks|Kevin Marks]], [[implementors#Josh_Smith|Josh Smith]]

=== Technorati Search ===
* [http://technorati.com/ Technorati] [http://technorati.com/search Search] supports and handles both [[vote-links]] and [[rel-nofollow]] for indicating whether a link should have any/positive/negative weighting towards the destination.
** by [http://technorati.com/about/staff.html Technorati Staff]

=== Technorati Tags ===
* [http://technorati.com/tags/ Technorati Tags] pages aggregate blog posts tagged with the [[rel-tag]] open tagging standard, in addition to recent tagged photos and links.

=== Textpattern ===
==== Microformats Plugin ====
* [http://placenamehere.com/TXP/pnh_mf/ Textpattern Microformats Plugin] supports authoring [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [http://gmpg.org/xfn XFN], [[rel-tag]], [[rel-license]] in the [http://www.textpattern.com/ Textpattern] CMS/blogging tool
** by [http://placenamehere.com/ Chris Casciano]

=== Tomota ===
* The [http://www.tomota.de Tomota] allows import, export and conversion from and to hcards.
** by [[implementors#RalfEngels|Ralf Engels]]

=== Transformr ===
* [http://code.google.com/p/transformr/ Transformr] Is a microformats transformation toolkit. Transformr is also available as a [http://transformr.co.uk/ webservice]
** by [[implementors#Martin_McEvoy|Martin McEvoy]]

=== TYPO3 ===
* [http://www.typo3.com TYPO3]
==== Getting Started =====
* [http://typo3.org TYPO3 Developer Ressource]
* [http://www.acqal.com/a/article/getting-help-with-typo3-98.html Getting Help With TYPO3]
==== tt_address extension====
* [http://typo3.org/extensions/repository/view/tt_address/2.0.1/ tt_address] - hCard support with the tt_address extension version 2.0.0
** by [[implementors#Ingo_Renner|Ingo Renner]]
==== TIMTAB extension====
* [http://typo3.org/extensions/repository/view/timtab/0.5.11/ TIMTAB] - XFN support for blogrolls with the TIMTAB weblog extension for TYPO3
** by [[implementors#Ingo_Renner|Ingo Renner]]

=== Tweeterboard ===
* Tweeterboard supports [hcard|hCard]], and [http://gmpg.org/xfn XFN] on profile pages ([http://tweeterboard.com/user/missrogue example]).

=== Twitter ===

* [http://twitter.com Twitter] [http://twitter.com/al3x/statuses/53982402 supports] [[hatom|hAtom]], [[hcard|hCard]], and [http://gmpg.org/xfn XFN].
** hCards for groups are marked up with "fn" not "fn org". See, for example, [http://twitter.com/microformats microformats on Twitter]
** Improper address mark-up (no child properties; though this may be all that can be achieved, if the user enters a value like "Birmingham, England")
** Uses <code>class="label"</code> for non-hCard purpose.

=== ufXtract ===
* [http://lab.backnetwork.com/ufXtract/ ufXtract] implements [[parsing]] of microformats such as [[hCard]] and [[XFN]].
** by [[implementors#Glenn_Jones|Glenn Jones]] of [[implementors#Madgex|Madgex]]. See [http://www.glennjones.net/Post/831/ufXtractmicroformatsparser.htm blog post announcement].

=== Upcoming.org ===
* [http://upcoming.org Upcoming.org] - hCalendar support in events listings and individual events.
** by [[implementors#Andy_Baio|Andy Baio]], [[implementors#Leonard_Lin|Leonard Lin]], [[implementors#Gordon_Luk|Gordon Luk]]

=== vCardExplorer ===
* [http://vcardexplorer.corefault.de/ vCardExplorer for MacOSX] - browses local vcards and converts hcards from URLs.

=== VIREL Microformats Search Engine===
* [http://www.virel.de/ microformats search engine] - website friendly crawler. searches for public informations embedded as microformats in web pages.

=== WindowsLiveWriter ===
* [[implementors#Microsoft|Microsoft's]] WindowsLiveWriter (WLW) [http://gallery.live.com/liveItemDetail.aspx?li=9751e563-1408-4fc3-8028-bd4351edb1fb&l=8 event plugin] supports [[hcalendar|hCalendar]].

=== WordPress ===
*See [[wordpress|WordPress]].

=== X2V ===
* Brian Suda has created several XSLT files to extract microformats from HTML. From that the [http://suda.co.uk/projects/X2V/ X2V] webservice/favelet emerged. The XSLT and favelet extracts [[hcard|hCard]] and to produces .vcf (vCard) files and [[hcalendar|hCalendar]] to produce .ics (iCal) files. Also in the labs is a universal XMDP validator and a site-wide search spider that recognizes 'no-follow', 'license' and other microformats so they can be used in a more semantic way when displaying search results.
** by [[implementors#Brian_Suda|Brian Suda]]

=== XWiki ===
* [http://xwiki.org XWiki] (as of [http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWiki10Beta5 version 10Beta5]) publishes the user profiles using [[hcard | hCard]], the events in the calendar application using [[hCalendar | hCalendar]], the blog entries using [[hAtom | hAtom]] and homepage links using [[rel-home | rel-home]].

=== xfn-spider ===

* [http://sphinx.net.ru/hg/xfn-spider xfn-spider] — simple crawler extracting microformats with XSLT ([http://sphinx.net.ru/blog/entry/simple-microformat-xslt-extraction/ Original article in Russian] circa summer 2007) and exporting information to OPML feedlist, tag cloud etc.

* See [http://services.alphaworks.ibm.com/manyeyes/view/SNnqRHsOtha6i5-m6iGTH2- XFN visualization] example at IBM's Many Eyes made using data extracted with xfn-spider

=== Yahoo Creative Commons Search ===
* [http://search.yahoo.com/cc/ Yahoo Creative Commons Search] - supports [[rel-license]] specifically to search for Creative Commons licensed content.

=== Yahoo Local ===
* [http://local.yahoo.com Yahoo local] supports [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]].

=== Yahoo Tech ===
* [http://tech.yahoo.com Yahoo! Tech] supports [[hreview|hReview]].

=== Yahoo UK Movies ===
* [http://movies.yahoo.co.uk Yahoo! UK Movies] supports [[hreview|hReview]].
** by Mark Norman Francis

=== Yalwa - Local directory ===
* [http://www.yalwa.com/ Yalwa - Local Directory] supports [[hreview|hReview]].
Example: [http://wiesbaden.yalwa.de/ID_102318221/Yalwa-GmbH.html Yalwa Listing]

=== Yedda ===
* [http://yedda.com Yedda] supports [[hcard|hCard]] for exposing users information, [[hatom|hAtom]] for exposing data that is already exposed via feeds (like list of questions and answers) and [[rel-tag|rel-tag]] for every tag used to tag questions and users.

== Validators ==

See [[debugging-tools]].

==Search engines==
See [[search-engines]]

== Companies / Developers / Organizations ==
See [[implementors]]

The following have been moved from the sections above due to problems, stated below:

=== Web Essentials ===
* [http://we05.com/ Web Essentials] - supports [[hcard|hCard]] and [[hcalendar|hCalendar]], e.g. in their [http://we05.com/presenters.cfm list of presenters] and [http://we05.com/program.cfm program schedule].
** John McKerrell tried to look at the site on 24th October 2006 but could not access the site, server didn't seem to be up.
** As of 2008-02-22, domain is expired. [[User:AndyMabbett|Andy Mabbett]] 05:12, 22 Feb 2008 (PST)

== Other ==
Some notes on initial thoughts around [[implementation-guidelines|Guidelines and Strategies for Implementing Microformats]]

search-engines

2009-05-18T16:33:11Z

Kavi:

<h1>search engines</h1>
{{TOC-right}}
Search engine [[implementations]] that index microformats across the web (i.e. not just on their own site). Alphabetical within status/stability.

== web search ==
General web search. Search engines that index websites in general using microformats.
* [http://google.com/ Google search] supports [[rel-nofollow]], [[hCard]], [[hReview]], [[hreview-aggregate|hReview aggregate]], [[hProduct]] (since 2009-05 for [[http://www.google.com/support/webmasters/bin/answer.py?answer=99170 rich snippets]]) in main search. Through additional interfaces:
** [http://www.google.com/advanced_search Google Advanced Search - Usage rights] supports [[rel-license]] (since 2005(?) citation needed)
** [http://code.google.com/apis/socialgraph/ Google Social Graph API] supports [[XFN]] (launched 2008 February). See "[http://socialgraph-resources.googlecode.com/svn/trunk/samples/findyours.html Google Social Graph API How are your sites connected?]".
* [http://search.yahoo.com Yahoo search] supports [[rel-nofollow]]. Through additional interfaces:
** [http://search.yahoo.com/cc Yahoo Creative Commons search] supports [[rel-license]]
** [http://developer.yahoo.com/search/boss/ Yahoo Search BOSS]
*** [http://www.bosshacks.com/build-semantic-search-boss.html Build a semantic Search Engine with BOSS] documents how to use Yahoo's BOSS API to access Yahoo Search Monkey which supports the [[hAtom]], [[hCalendar]], [[hCard]], [[hReview]], [[XFN]], [[geo]], [[rel-tag]], [[adr]] microformats.
** [http://developer.yahoo.net/blog/archives/2008/06/monkey_microformat.html Yahoo Search Monkey] ([[hCard]], [[hCalendar]], [[hReview]], [[hAtom]], others) - launched 2008 May
*** [http://search.yahoo.com/search?p=searchmonkeyid%3Acom.yahoo.uf.hcard search Yahoo for hCards]
*** [http://search.yahoo.com/search?p=searchmonkeyid%3Acom.yahoo.uf.hcalendar search Yahoo for hCalendar events]
*** [http://search.yahoo.com/search?p=searchmonkeyid%3Acom.yahoo.uf.hreview search Yahoo for hReviews]
*** [http://search.yahoo.com/search?p=searchmonkeyid%3Acom.yahoo.uf.hatom search Yahoo for hAtom]
*** [http://search.yahoo.com/search?p=searchmonkeyid%3Acom.yahoo.uf.xfn search Yahoo for XFN]

Editor note: Google and Yahoo search engines could probably use their own pages with implementation details and links to additional resources.

== blog search ==
Search blog posts and blogs in general. Search engines that specifically index blogs, blog posts, and other realtime sources on the web using microformats.
* [http://www.icerocket.com IceRocket] through additional interfaces
** [http://www.icerocket.com/tags IceRocket Tag search] support [[rel-tag]] (to search for [http://www.icerocket.com/c?p=tags blog posts tagged with rel-tag]).
* [http://technorati.com Technorati] ([[rel-nofollow]])
** [http://technorati.com/tags/ Technorati Tag Search] supports [[rel-tag]] (to search for blog posts tagged with rel-tag).

== prototype or alpha ==
=== socialsearchme ===
* [http://scrape.singpolyma.net/profile/ singpolyma social web search] ([[xfn]], [[hCard]]) part of the [http://code.google.com/p/diso/ diso] project.
** memorable URL: http://socialsearchme.com/
** e.g. try a [http://scrape.singpolyma.net/profile/?q=Jeremy search for Jeremy]
** 2008-08-19 [http://singpolyma.net/2008/08/diso-gets-search/ DiSo Gets Search] - blog post announcing it!
==== to do ====
* both <code>socialsearchme.com/?q=b</code> and <code>socialsearchme.com/b</code> should redirect/retrieve <code>scrape.singpolyma.net/profile/?q=b</code>.

=== Technorati Kitchen ===
* [http://kitchen.technorati.com Technorati Kitchen]
** [http://kitchen.technorati.com/contacts/search/ Technorati contacts search] ([[hCard]])
** [http://kitchen.technorati.com/events/search/ Technorati events search] ([[hCalendar]])

=== VIREL ===
* [http://virel.de/ VIREL] indexes both [[hCard]] and [[hCalendar]] and provides a user interface (pop-up menu) to choose between searching contacts or events.
** 2008-09-09 Tag Edge: [http://tagedge.com/2008/09/09/virel-microformats-search-engine/ Virel: Microformats Search Engine]

== search results in microformats ==
Search engines that publish microformats in their results (but may not necessarily be indexing microformats).
=== Karniyarik ===
* [http://www.karniyarik.com Karniyarik] Vertical Search Engine for Online Products ([http://www.karniyarik.com/karniyarik-web Stealth Beta]). Karniyarik's search results lists products and their vendors, which are marked up with [[hCard]] (e.g. [http://www.karniyarik.com/search.jsp?query=bebek+bezi search results for bebek bezi - diapers]). In addition, Karniyarik's [http://www.karniyarik.com/aboutus.jsp about page] is marked up with hCard.

== related ==
* [[implementations]]

search-engines

2009-05-18T16:31:55Z

Kavi:

<h1>search engines</h1>
{{TOC-right}}
Search engine [[implementations]] that index microformats across the web (i.e. not just on their own site). Alphabetical within status/stability.

== web search ==
General web search. Search engines that index websites in general using microformats.
* [http://google.com/ Google search] supports [[rel-nofollow]], [[hCard]], [[hReview]], [[hreview-aggregate|hReview aggregate]], [[hProduct]] (since 2009-05 for [[http://www.google.com/support/webmasters/bin/answer.py?answer=99170|rich snippets]]) in main search. Through additional interfaces:
** [http://www.google.com/advanced_search Google Advanced Search - Usage rights] supports [[rel-license]] (since 2005(?) citation needed)
** [http://code.google.com/apis/socialgraph/ Google Social Graph API] supports [[XFN]] (launched 2008 February). See "[http://socialgraph-resources.googlecode.com/svn/trunk/samples/findyours.html Google Social Graph API How are your sites connected?]".
* [http://search.yahoo.com Yahoo search] supports [[rel-nofollow]]. Through additional interfaces:
** [http://search.yahoo.com/cc Yahoo Creative Commons search] supports [[rel-license]]
** [http://developer.yahoo.com/search/boss/ Yahoo Search BOSS]
*** [http://www.bosshacks.com/build-semantic-search-boss.html Build a semantic Search Engine with BOSS] documents how to use Yahoo's BOSS API to access Yahoo Search Monkey which supports the [[hAtom]], [[hCalendar]], [[hCard]], [[hReview]], [[XFN]], [[geo]], [[rel-tag]], [[adr]] microformats.
** [http://developer.yahoo.net/blog/archives/2008/06/monkey_microformat.html Yahoo Search Monkey] ([[hCard]], [[hCalendar]], [[hReview]], [[hAtom]], others) - launched 2008 May
*** [http://search.yahoo.com/search?p=searchmonkeyid%3Acom.yahoo.uf.hcard search Yahoo for hCards]
*** [http://search.yahoo.com/search?p=searchmonkeyid%3Acom.yahoo.uf.hcalendar search Yahoo for hCalendar events]
*** [http://search.yahoo.com/search?p=searchmonkeyid%3Acom.yahoo.uf.hreview search Yahoo for hReviews]
*** [http://search.yahoo.com/search?p=searchmonkeyid%3Acom.yahoo.uf.hatom search Yahoo for hAtom]
*** [http://search.yahoo.com/search?p=searchmonkeyid%3Acom.yahoo.uf.xfn search Yahoo for XFN]

Editor note: Google and Yahoo search engines could probably use their own pages with implementation details and links to additional resources.

== blog search ==
Search blog posts and blogs in general. Search engines that specifically index blogs, blog posts, and other realtime sources on the web using microformats.
* [http://www.icerocket.com IceRocket] through additional interfaces
** [http://www.icerocket.com/tags IceRocket Tag search] support [[rel-tag]] (to search for [http://www.icerocket.com/c?p=tags blog posts tagged with rel-tag]).
* [http://technorati.com Technorati] ([[rel-nofollow]])
** [http://technorati.com/tags/ Technorati Tag Search] supports [[rel-tag]] (to search for blog posts tagged with rel-tag).

== prototype or alpha ==
=== socialsearchme ===
* [http://scrape.singpolyma.net/profile/ singpolyma social web search] ([[xfn]], [[hCard]]) part of the [http://code.google.com/p/diso/ diso] project.
** memorable URL: http://socialsearchme.com/
** e.g. try a [http://scrape.singpolyma.net/profile/?q=Jeremy search for Jeremy]
** 2008-08-19 [http://singpolyma.net/2008/08/diso-gets-search/ DiSo Gets Search] - blog post announcing it!
==== to do ====
* both <code>socialsearchme.com/?q=b</code> and <code>socialsearchme.com/b</code> should redirect/retrieve <code>scrape.singpolyma.net/profile/?q=b</code>.

=== Technorati Kitchen ===
* [http://kitchen.technorati.com Technorati Kitchen]
** [http://kitchen.technorati.com/contacts/search/ Technorati contacts search] ([[hCard]])
** [http://kitchen.technorati.com/events/search/ Technorati events search] ([[hCalendar]])

=== VIREL ===
* [http://virel.de/ VIREL] indexes both [[hCard]] and [[hCalendar]] and provides a user interface (pop-up menu) to choose between searching contacts or events.
** 2008-09-09 Tag Edge: [http://tagedge.com/2008/09/09/virel-microformats-search-engine/ Virel: Microformats Search Engine]

== search results in microformats ==
Search engines that publish microformats in their results (but may not necessarily be indexing microformats).
=== Karniyarik ===
* [http://www.karniyarik.com Karniyarik] Vertical Search Engine for Online Products ([http://www.karniyarik.com/karniyarik-web Stealth Beta]). Karniyarik's search results lists products and their vendors, which are marked up with [[hCard]] (e.g. [http://www.karniyarik.com/search.jsp?query=bebek+bezi search results for bebek bezi - diapers]). In addition, Karniyarik's [http://www.karniyarik.com/aboutus.jsp about page] is marked up with hCard.

== related ==
* [[implementations]]

aggregate-microformat-template-brainstorming

2009-04-24T04:27:11Z

Kavi: /* Example: aggregate review on Yelp */

= 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 ==

* The number of microformats being summarized is important in every example aggregation (i.e. 23 reviews, 50 products, 14 events, 6 recipes)
* For ratings, the average rating score is important
* In the Yelp example, sample descriptions are also included
* For prices, the range (low and high price) are relevant
* For message board posts, the most recent post date is relevant

== Proposal ==

Here is a proposed template for defining aggregate microformats:

* For any microformat "hX" there is a corresponding aggregate microformat that follows a consistent naming convention. For example, an aggregate hReview could be "hReview-aggregate" and an aggregate hAtom could be "hAtom-aggregate."
* The aggregate microformat "hX-aggregate" contains all of the same attributes as the original microformat "hX".
* Each attribute borrowed from "hX" can also take on some sub-attributes -- min, max, average, or sample. So an average rating would be class="rating average", a lowest price would be class="price min", a most recent blog post date would be class="updated max" (where max here is interpreted as the latest date), and a sample summary from a review would be class="summary sample".
* Aggregate microformats contain an additional attribute that isn't imported from "hX" -- for purposes of discussion, let's call this "count." It contains the number of objects that are being summarized.
* 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: hypothetical aggregate review on Yelp ====
URL: http://www.yelp.com/biz/vive-sol-restaurant-mountain-view

<pre><nowiki>
<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>
</nowiki></pre>

== See also ==

* Aggregation of microformats: [[aggregate-microformat-template-examples|examples]] - [[aggregate-microformat-template-formats|formats]]
* Aggregate review: [[aggregate-review-examples|examples]] - [[aggregate-review-formats|formats]] - [[aggregate-review-brainstorming|brainstorming]]

aggregate-microformat-template-brainstorming

2009-04-10T21:57:06Z

Kavi:

= 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 ==

* The number of microformats being summarized is important in every example aggregation (i.e. 23 reviews, 50 products, 14 events, 6 recipes)
* For ratings, the average rating score is important
* In the Yelp example, sample descriptions are also included
* For prices, the range (low and high price) are relevant
* For message board posts, the most recent post date is relevant

== Proposal ==

Here is a proposed template for defining aggregate microformats:

* For any microformat "hX" there is a corresponding aggregate microformat that follows a consistent naming convention. For example, an aggregate hReview could be "hReview-aggregate" and an aggregate hAtom could be "hAtom-aggregate."
* The aggregate microformat "hX-aggregate" contains all of the same attributes as the original microformat "hX".
* Each attribute borrowed from "hX" can also take on some sub-attributes -- min, max, average, or sample. So an average rating would be class="rating average", a lowest price would be class="price min", a most recent blog post date would be class="updated max" (where max here is interpreted as the latest date), and a sample summary from a review would be class="summary sample".
* Aggregate microformats contain an additional attribute that isn't imported from "hX" -- for purposes of discussion, let's call this "count." It contains the number of objects that are being summarized.
* 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 ====
URL: http://www.yelp.com/biz/vive-sol-restaurant-mountain-view

<pre><nowiki>
<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.
</div>
</nowiki></pre>

== See also ==

* Aggregation of microformats: [[aggregate-microformat-template-examples|examples]] - [[aggregate-microformat-template-formats|formats]]
* Aggregate review: [[aggregate-review-examples|examples]] - [[aggregate-review-formats|formats]] - [[aggregate-review-brainstorming|brainstorming]]

aggregate-microformat-template-examples

2009-04-10T21:53:53Z

Kavi: /* Real-World Examples */

= Aggregate microformats: examples =

== The Problem ==

Many pages on the web contain or reference aggregates or summaries of other data: a summary of 173 reviews for a business, a summary of 25 running shoes for sale, a summary of a discussion with 501 individual posts. Often the summary data is as important or more important than the individual pieces of data being summarized, so we would like to have a way to mark them up using microformats.

We tried to solve this for the case of review summaries (i.e. 35 reviews, average rating is 4.5 stars), but then realized that our approach applied to similar problems of aggregating other kinds of microformat data. The problem is to come up with a simple "pattern" or "template" that can be used to annotate aggregate information about pages that contain or reference multiple microformat instances.

== Participants ==
* Othar Hansson
* Kavi Goel

== Real-World Examples ==

=== Aggregate reviews (aggregate hReview) ===
Showing aggregate review information for products or businesses is very common on the web. hReview is designed to annotate a single user's review but not summarize a collection of user reviews.

* Amazon
** http://www.amazon.com/gp/product/B001FA1NFA/
** Aggregation of user reviews for a product. Up to 10 reviews per page
** Includes 1-5 stars average rating and the total number of reviews
** Also includes number of reviews for each score (1-5)

* Yelp
** http://www.yelp.com/biz/vive-sol-restaurant-mountain-view
** Shows 1-5 stars average rating and the total number of reviews
** Also includes number of reviews for each score (1-5)
** The site highlights recurring themes from reviews (i.e. "The food is delicious - love the chicken mole.") and the number of reviews where such comments were made.

For a longer list of aggregate review examples, see [[aggregate-review-examples]].

=== Summary of discussion boards (aggregate hAtom) ===

* BBC News
** http://newsforums.bbc.co.uk/nol/thread.jspa?forumID=6305&edition=2&ttl=20090406181909
** Shows the total number of comments posted and the date of the most recent post.

* AARP discussion board
** http://www.aarp.org/community/groups/searchGroups.bt?orderBy=1&categoryId=43
** Shows the total number of comments posted and the date of the most recent post.

=== Lists of product offers (aggregate hListing?) ===

Another common occurrence on the web is to have many offers for a product from different sellers. Shopping aggregators like Amazon, Nextag, Pricegrabber, etc all do this. Solving this problem also requires some rationalization of hListing and hProduct, but in any case aggregations of offers examples are as follows.

* Amazon
** http://www.amazon.com/Sony-BDP-S550-1080p-Blu-ray-Player/dp/B001FN3ZRQ
** Many aggregations on this page (aggregations of reviews and sellers)
** The "15 used & new from $254.12" shows the number of sellers and the low price amongst those offers

* CNET Reviews
** http://reviews.cnet.com/1770-5_7-0.html?query=monitor&tag=srch
** Shows price range (low and high price) and number of sellers for the Samsung SyncMaster T220.

* Pricegrabber
** http://clothing.pricegrabber.com/mens-athletic-shoes/Nike-Shox-Experience-Men-Running-Shoes/m83885830.html
** Shows the lowest priced offer and the number of offers

=== Summaries that only contain a count ===

For many search results pages (or category pages showing a list of items), just knowing the number of results is valuable.

* Recipes on Food Network
** http://www.foodnetwork.com/search/tortilla+soup/results.do?fnSearchType=recipe
** 102 recipes (aggregate hRecipe)
* People with the name "Kevin Marks" on Facebook
** http://www.facebook.com/s.php?q=kevin+marks&n=-1&k=400000000010&sf=r&init=q&sid=f88be874d43681c8bfd0d98fe3c47634
** 414 people (aggregate hCard)
* Concerts on Pollstar
** http://www.pollstar.com/resultsArtist.aspx?ID=74518&SortBy=Date&SearchBy=bob%20dylan
** 12 upcoming Bob Dylan concerts (aggregate hCalendar)

== See also ==

* Aggregation of microformats: [[aggregate-microformat-template-formats|formats]] - [[aggregate-microformat-template-brainstorming|brainstorming]]

* Aggregate reviews: [[aggregate-review-examples|examples]] - [[aggregate-review-formats|formats]] - [[aggregate-review-brainstorming|brainstorming]]

aggregate-microformat-template-examples

2009-04-10T21:53:39Z

Kavi: /* Real-World Examples */

aggregate-microformat-template-examples

2009-04-10T21:51:46Z

Kavi:

= Aggregate microformats: examples =

== The Problem ==

Many pages on the web contain or reference aggregates or summaries of other data: a summary of 173 reviews for a business, a summary of 25 running shoes for sale, a summary of a discussion with 501 individual posts. Often the summary data is as important or more important than the individual pieces of data being summarized, so we would like to have a way to mark them up using microformats.

We tried to solve this for the case of review summaries (i.e. 35 reviews, average rating is 4.5 stars), but then realized that our approach applied to similar problems of aggregating other kinds of microformat data. The problem is to come up with a simple "pattern" or "template" that can be used to annotate aggregate information about pages that contain or reference multiple microformat instances.

== Participants ==
* Othar Hansson
* Kavi Goel

== Real-World Examples ==

=== Aggregate reviews (aggregate hReview) ===
Showing aggregate review information for products or businesses is very common on the web. hReview is designed to annotate a single user's review but not summarize a collection of user reviews.

* Amazon
** http://www.amazon.com/gp/product/B001FA1NFA/
** Aggregation of user reviews for a product. Up to 10 reviews per page
** Includes 1-5 stars average rating and the total number of reviews
** Also includes number of reviews for each score (1-5)

* Yelp
** http://www.yelp.com/biz/vive-sol-restaurant-mountain-view
** Shows 1-5 stars average rating and the total number of reviews
** Also includes number of reviews for each score (1-5)
** The site highlights recurring themes from reviews (i.e. "The food is delicious - love the chicken mole.") and the number of reviews where such comments were made.

For a longer list of aggregate review examples, see [[aggregate-review-examples]].

=== Summary of discussion boards (aggregate hAtom) ===

* BBC News
** http://newsforums.bbc.co.uk/nol/thread.jspa?forumID=6305&edition=2&ttl=20090406181909
** Shows the total number of comments posted and the date of the most recent post.

* AARP discussion board
** http://www.aarp.org/community/groups/searchGroups.bt?orderBy=1&categoryId=43
** Shows the total number of comments posted and the date of the most recent post.

=== Lists of product offers (aggregate hListing?) ===

Another common occurrence on the web is to have many offers for a product from different sellers. Shopping aggregators like Amazon, Nextag, Pricegrabber, etc all do this. Solving this problem also requires some rationalization of hListing and hProduct, but in any case aggregations of offers examples are as follows.

* Amazon
** http://www.amazon.com/Sony-BDP-S550-1080p-Blu-ray-Player/dp/B001FN3ZRQ
** Many aggregations on this page (aggregations of reviews and sellers)
** The "15 used & new from $254.12" shows the number of sellers and the low price amongst those offers

* CNET Reviews
** http://reviews.cnet.com/1770-5_7-0.html?query=monitor&tag=srch
** Shows price range (low and high price) and number of sellers for the Samsung SyncMaster T220.

* Pricegrabber
** http://clothing.pricegrabber.com/mens-athletic-shoes/Nike-Shox-Experience-Men-Running-Shoes/m83885830.html
** Shows the lowest priced offer and the number of offers

=== Summary info for lists of products (aggregate hProduct) ===

* BuyFineArt.com
** http://www.buy-fineart.com/pricerange.asp?f=50&t=99
** Shows price range and total count of products in the category

=== Summaries that only contain a count ===

For many search results pages (or category pages showing a list of items), just knowing the number of results is valuable.

* Recipes on Food Network
** http://www.foodnetwork.com/search/tortilla+soup/results.do?fnSearchType=recipe
** 102 recipes (aggregate hRecipe)
* People with the name "Kevin Marks" on Facebook
** http://www.facebook.com/s.php?q=kevin+marks&n=-1&k=400000000010&sf=r&init=q&sid=f88be874d43681c8bfd0d98fe3c47634
** 414 people (aggregate hCard)
* Concerts on Pollstar
** http://www.pollstar.com/resultsArtist.aspx?ID=74518&SortBy=Date&SearchBy=bob%20dylan
** 12 upcoming Bob Dylan concerts (aggregate hCalendar)

== See also ==

* Aggregation of microformats: [[aggregate-microformat-template-formats|formats]] - [[aggregate-microformat-template-brainstorming|brainstorming]]

* Aggregate reviews: [[aggregate-review-examples|examples]] - [[aggregate-review-formats|formats]] - [[aggregate-review-brainstorming|brainstorming]]

aggregate-microformat-template-brainstorming

2009-04-09T08:08:48Z

Kavi: /* Proposal */

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 ==

* The number of microformats being summarized is important in every example aggregation (i.e. 23 reviews, 50 products, 14 events, 6 recipes)
* For ratings, the average rating score is important
* In the Yelp example, sample descriptions are also included
* For prices, the range (low and high price) are relevant
* For message board posts, the most recent post date is relevant

== Proposal ==

Here is a proposed template for defining aggregate microformats:

* For any microformat "hX" there is a corresponding aggregate microformat that follows a consistent naming convention. For example, an aggregate hReview could be "hReview-aggregate" and an aggregate hAtom could be "hAtom-aggregate."
* The aggregate microformat "hX-aggregate" contains all of the same attributes as the original microformat "hX".
* Each attribute borrowed from "hX" can also take on some sub-attributes -- min, max, average, or sample. So an average rating would be class="rating average", a lowest price would be class="price min", a most recent blog post date would be class="updated max" (where max here is interpreted as the latest date), and a sample summary from a review would be class="summary sample".
* Aggregate microformats contain an additional attribute that isn't imported from "hX" -- for purposes of discussion, let's call this "count." It contains the number of objects that are being summarized.
* 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 ====
URL: http://www.yelp.com/biz/vive-sol-restaurant-mountain-view

<pre><nowiki>
<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.
</div>
</nowiki></pre>

== See also ==

* Aggregation of microformats: [[aggregate-microformat-template-examples|examples]] - [[aggregate-microformat-template-formats|formats]]
* Aggregate review: [[aggregate-review-examples|examples]] - [[aggregate-review-formats|formats]] - [[aggregate-review-brainstorming|brainstorming]]

aggregate-microformat-template-brainstorming

2009-04-09T08:03:36Z

Kavi:

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 ==

* The number of microformats being summarized is important in every example aggregation (i.e. 23 reviews, 50 products, 14 events, 6 recipes)
* For ratings, the average rating score is important
* In the Yelp example, sample descriptions are also included
* For prices, the range (low and high price) are relevant
* For message board posts, the most recent post date is relevant

== Proposal ==

Here is a proposed template for defining aggregate microformats:

* For any microformat "hX" there is a corresponding aggregate microformat that follows a consistent naming convention. For example, an aggregate hReview could be "hReview-aggregate" and an aggregate hAtom could be "hAtom-aggregate."
* The aggregate microformat contains all of the same attributes as the original microformat.
* Each attribute from the existing microformat can also take on some sub-attributes -- min, max, average, or sample. So an average rating would be class="rating average", a lowest price would be class="price min", a most recent blog post date would be class="updated max" (where max here is interpreted as the latest date), and a sample summary from a review would be class="summary sample".
* Aggregate microformats contain an additional attribute that isn't imported from the original microformat -- for purposes of discussion, let's call this "count." It contains the number of objects that are being summarized.
* 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 there are often highlighted instances on summary pages. Amazon shows the most popular reviews on the first page for a product and shopping aggregator sites usually show the best deal first in a list of offers.

==== Example: aggregate review on Yelp ====
URL: http://www.yelp.com/biz/vive-sol-restaurant-mountain-view

<pre><nowiki>
<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.
</div>
</nowiki></pre>

== See also ==

* Aggregation of microformats: [[aggregate-microformat-template-examples|examples]] - [[aggregate-microformat-template-formats|formats]]
* Aggregate review: [[aggregate-review-examples|examples]] - [[aggregate-review-formats|formats]] - [[aggregate-review-brainstorming|brainstorming]]

aggregate-microformat-template-brainstorming

2009-04-09T08:02:48Z

Kavi: /* Example: aggregate review on Yelp */

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 ==

* The number of microformats being summarized is important in every example aggregation (i.e. 23 reviews, 50 products, 14 events, 6 recipes)
* For ratings, the average rating score is important
* In the Yelp example, sample descriptions are also included
* For prices, the range (low and high price) are relevant
* For message board posts, the most recent post date is relevant

== Proposal ==

Here is a proposed template for defining aggregate microformats:

* For any microformat "hX" there is a corresponding aggregate microformat that follows a consistent naming convention. For example, an aggregate hReview could be "hReview-aggregate" and an aggregate hAtom could be "hAtom-aggregate."
* The aggregate microformat contains all of the same attributes as the original microformat.
* Each attribute from the existing microformat can also take on some sub-attributes -- min, max, average, or sample. So an average rating would be class="rating average", a lowest price would be class="price min", a most recent blog post date would be class="updated max" (where max here is interpreted as the latest date), and a sample summary from a review would be class="summary sample".
* Aggregate microformats contain an additional attribute that isn't imported from the original microformat -- for purposes of discussion, let's call this "count." It contains the number of objects that are being summarized.
* 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 there are often highlighted instances on summary pages. Amazon shows the most popular reviews on the first page for a product and shopping aggregator sites usually show the best deal first in a list of offers.

==== Example: aggregate review on Yelp ====
URL: http://www.yelp.com/biz/vive-sol-restaurant-mountain-view

<pre><nowiki>
<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.
</div>
</nowiki></pre>

== See also ==

* Aggregation of microformats: [[aggregate-microformat-template-examples|examples]] - [[aggregate-microformat-template-formats|formats]]
* Aggregate review: [[aggregate-review-examples|examples]] - [[aggregate-review-formats|formats]] - [[aggregate-review-brainstorming|brainstorming]]

aggregate-microformat-template-brainstorming

2009-04-09T08:01:40Z

Kavi:

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 ==

* The number of microformats being summarized is important in every example aggregation (i.e. 23 reviews, 50 products, 14 events, 6 recipes)
* For ratings, the average rating score is important
* In the Yelp example, sample descriptions are also included
* For prices, the range (low and high price) are relevant
* For message board posts, the most recent post date is relevant

== Proposal ==

Here is a proposed template for defining aggregate microformats:

* For any microformat "hX" there is a corresponding aggregate microformat that follows a consistent naming convention. For example, an aggregate hReview could be "hReview-aggregate" and an aggregate hAtom could be "hAtom-aggregate."
* The aggregate microformat contains all of the same attributes as the original microformat.
* Each attribute from the existing microformat can also take on some sub-attributes -- min, max, average, or sample. So an average rating would be class="rating average", a lowest price would be class="price min", a most recent blog post date would be class="updated max" (where max here is interpreted as the latest date), and a sample summary from a review would be class="summary sample".
* Aggregate microformats contain an additional attribute that isn't imported from the original microformat -- for purposes of discussion, let's call this "count." It contains the number of objects that are being summarized.
* 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 there are often highlighted instances on summary pages. Amazon shows the most popular reviews on the first page for a product and shopping aggregator sites usually show the best deal first in a list of offers.

=== Example: aggregate review on Yelp ===

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

<pre><nowiki>
<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.
</div>
</nowiki></pre>

== See also ==

* Aggregation of microformats: [[aggregate-microformat-template-examples|examples]] - [[aggregate-microformat-template-formats|formats]]
* Aggregate review: [[aggregate-review-examples|examples]] - [[aggregate-review-formats|formats]] - [[aggregate-review-brainstorming|brainstorming]]

aggregate-microformat-template-examples

2009-04-09T07:54:12Z

Kavi:

== The Problem ==

Many pages on the web contain or reference aggregates or summaries of other data: a summary of 173 reviews for a business, a summary of 25 running shoes for sale, a summary of a discussion with 501 individual posts. Often the summary data is as important or more important than the individual pieces of data being summarized, so we would like to have a way to mark them up using microformats.

We tried to solve this for the case of review summaries (i.e. 35 reviews, average rating is 4.5 stars), but then realized that our approach applied to similar problems of aggregating other kinds of microformat data. The problem is to come up with a simple "pattern" or "template" that can be used to annotate aggregate information about pages that contain or reference multiple microformat instances.

== Participants ==
* Othar Hansson
* Kavi Goel

== Real-World Examples ==

=== Aggregate reviews (aggregate hReview) ===
Showing aggregate review information for products or businesses is very common on the web. hReview is designed to annotate a single user's review but not summarize a collection of user reviews.

* Amazon
** http://www.amazon.com/gp/product/B001FA1NFA/
** Aggregation of user reviews for a product. Up to 10 reviews per page
** Includes 1-5 stars average rating and the total number of reviews
** Also includes number of reviews for each score (1-5)

* Yelp
** http://www.yelp.com/biz/vive-sol-restaurant-mountain-view
** Shows 1-5 stars average rating and the total number of reviews
** Also includes number of reviews for each score (1-5)
** The site highlights recurring themes from reviews (i.e. "The food is delicious - love the chicken mole.") and the number of reviews where such comments were made.

For a longer list of aggregate review examples, see [[aggregate-review-examples]].

=== Summary of discussion boards (aggregate hAtom) ===

* BBC News
** http://newsforums.bbc.co.uk/nol/thread.jspa?forumID=6305&edition=2&ttl=20090406181909
** Shows the total number of comments posted and the date of the most recent post.

* AARP discussion board
** http://www.aarp.org/community/groups/searchGroups.bt?orderBy=1&categoryId=43
** Shows the total number of comments posted and the date of the most recent post.

=== Lists of product offers (aggregate hListing?) ===

Another common occurrence on the web is to have many offers for a product from different sellers. Shopping aggregators like Amazon, Nextag, Pricegrabber, etc all do this. Solving this problem also requires some rationalization of hListing and hProduct, but in any case aggregations of offers examples are as follows.

* Amazon
** http://www.amazon.com/Sony-BDP-S550-1080p-Blu-ray-Player/dp/B001FN3ZRQ
** Many aggregations on this page (aggregations of reviews and sellers)
** The "15 used & new from $254.12" shows the number of sellers and the low price amongst those offers

* CNET Reviews
** http://reviews.cnet.com/1770-5_7-0.html?query=monitor&tag=srch
** Shows price range (low and high price) and number of sellers for the Samsung SyncMaster T220.

* Pricegrabber
** http://clothing.pricegrabber.com/mens-athletic-shoes/Nike-Shox-Experience-Men-Running-Shoes/m83885830.html
** Shows the lowest priced offer and the number of offers

=== Summary info for lists of products (aggregate hProduct) ===

* BuyFineArt.com
** http://www.buy-fineart.com/pricerange.asp?f=50&t=99
** Shows price range and total count of products in the category

=== Summaries that only contain a count ===

For many search results pages (or category pages showing a list of items), just knowing the number of results is valuable.

* Recipes on Food Network
** http://www.foodnetwork.com/search/tortilla+soup/results.do?fnSearchType=recipe
** 102 recipes (aggregate hRecipe)
* People with the name "Kevin Marks" on Facebook
** http://www.facebook.com/s.php?q=kevin+marks&n=-1&k=400000000010&sf=r&init=q&sid=f88be874d43681c8bfd0d98fe3c47634
** 414 people (aggregate hCard)
* Concerts on Pollstar
** http://www.pollstar.com/resultsArtist.aspx?ID=74518&SortBy=Date&SearchBy=bob%20dylan
** 12 upcoming Bob Dylan concerts (aggregate hCalendar)

== See also ==

* Aggregation of microformats: [[aggregate-microformat-template-formats|formats]] - [[aggregate-microformat-template-brainstorming|brainstorming]]

* Aggregate reviews: [[aggregate-review-examples|examples]] - [[aggregate-review-formats|formats]] - [[aggregate-review-brainstorming|brainstorming]]

aggregate-microformat-template-examples

2009-04-09T07:38:58Z

Kavi:

== The Problem ==

Many pages on the web contain or reference aggregates or summaries of other data: a summary of 173 reviews for a business, a summary of 25 running shoes for sale, a summary of a discussion with 501 individual posts. Naturally, the summary data is the best summary of the page itself and why a user should visit it.

We tried to solve this for the case of review summaries, but then realized that our approach applied to similar problems of aggregating other kinds of microformat data. The problem is to come up with a simple "pattern" or "template" that can be used to annotate aggregate information about pages that contain or reference multiple microformat instances.

== Participants ==
* Othar Hansson
* Kavi Goel

== Real-World Examples ==

=== Aggregate reviews (aggregate hReview) ===
Showing aggregate review information for products or businesses is very common on the web. hReview is designed to annotate a single user's review but not summarize a collection of user reviews.

* Amazon
** http://www.amazon.com/gp/product/B001FA1NFA/
** Aggregation of user reviews for a product. Up to 10 reviews per page
** Includes 1-5 stars average rating and the total number of reviews
** Also includes number of reviews for each score (1-5)

* Yelp
** http://www.yelp.com/biz/vive-sol-restaurant-mountain-view
** Shows 1-5 stars average rating and the total number of reviews
** Also includes number of reviews for each score (1-5)
** The site highlights recurring themes from reviews (i.e. "The food is delicious - love the chicken mole.") and the number of reviews where such comments were made.

For a longer list of aggregate review examples, see [[aggregate-review-examples]].

=== Summary of discussion boards (aggregate hAtom) ===

* BBC News
** http://newsforums.bbc.co.uk/nol/thread.jspa?forumID=6305&edition=2&ttl=20090406181909
** Shows the total number of comments posted and the date of the most recent post.

* AARP discussion board
** http://www.aarp.org/community/groups/searchGroups.bt?orderBy=1&categoryId=43
** Shows the total number of comments posted and the date of the most recent post.

=== Lists of product offers (aggregate hListing?) ===

Another common occurrence on the web is to have many offers for a product from different sellers. Shopping aggregators like Amazon, Nextag, Pricegrabber, etc all do this. Solving this problem also requires some rationalization of hListing and hProduct, but in any case aggregations of offers examples are as follows.

* Amazon
** http://www.amazon.com/Sony-BDP-S550-1080p-Blu-ray-Player/dp/B001FN3ZRQ
** Many aggregations on this page (aggregations of reviews and sellers)
** The "15 used & new from $254.12" shows the number of sellers and the low price amongst those offers

* CNET Reviews
** http://reviews.cnet.com/1770-5_7-0.html?query=monitor&tag=srch
** Shows price range (low and high price) and number of sellers for the Samsung SyncMaster T220.

* Pricegrabber
** http://clothing.pricegrabber.com/mens-athletic-shoes/Nike-Shox-Experience-Men-Running-Shoes/m83885830.html
** Shows the lowest priced offer and the number of offers

=== Summary info for lists of products (aggregate hProduct) ===

* BuyFineArt.com
** http://www.buy-fineart.com/pricerange.asp?f=50&t=99
** Shows price range and total count of products in the category

=== Summaries that only contain a count ===

For many search results pages (or category pages showing a list of items), just knowing the number of results is valuable.

* Recipes on Food Network
** http://www.foodnetwork.com/search/tortilla+soup/results.do?fnSearchType=recipe
** 102 recipes (aggregate hRecipe)
* People with the name "Kevin Marks" on Facebook
** http://www.facebook.com/s.php?q=kevin+marks&n=-1&k=400000000010&sf=r&init=q&sid=f88be874d43681c8bfd0d98fe3c47634
** 414 people (aggregate hCard)
* Concerts on Pollstar
** http://www.pollstar.com/resultsArtist.aspx?ID=74518&SortBy=Date&SearchBy=bob%20dylan
** 12 upcoming Bob Dylan concerts (aggregate hCalendar)

== See also ==

* Aggregation of microformats: [[aggregate-microformat-template-formats|formats]] - [[aggregate-microformat-template-brainstorming|brainstorming]]

* Aggregate reviews: [[aggregate-review-examples|examples]] - [[aggregate-review-formats|formats]] - [[aggregate-review-brainstorming|brainstorming]]

aggregate-microformat-template-formats

2009-04-09T07:38:19Z

Kavi:

Nor prior work identified in this space. For a list of sites that have done some work related to markup of aggregate review information, see [[aggregate-review-formats]].

== See also ==

* Aggregation of microformats: [[aggregate-microformat-template-examples|examples]] - [[aggregate-microformat-template-brainstorming|brainstorming]]

* Aggregate reviews: [[aggregate-review-examples|examples]] - [[aggregate-review-formats|formats]] - [[aggregate-review-brainstorming|brainstorming]]

aggregate-microformat-template-formats

2009-04-09T07:36:49Z

Kavi: New page: Nor prior work identified in this space. For a list of sites that have done some work related to markup of aggregate review information, see aggregate-review-formats.

Nor prior work identified in this space. For a list of sites that have done some work related to markup of aggregate review information, see [[aggregate-review-formats]].

aggregate-microformat-template-brainstorming

2009-04-09T07:34:00Z

Kavi: New page: 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...

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.

== Types of information that appear in the examples ==

* The number of microformats being summarized is important in every example aggregation (i.e. 23 reviews, 50 products, 14 events, 6 recipes)
* For ratings, the average rating score is important
* In the Yelp example, sample descriptions are also included
* For prices, the range (low and high price) are relevant
* For message board posts, the most recent post date is relevant

== 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.

== Proposal ==

Here is a proposed template for defining aggregate microformats:

* Any existing microformat has a corresponding aggregate microformat that follows a consistent naming convention. For example, an aggregate hReview could be "hReview-aggregate" and an aggregate hAtom could be "hAtom-aggregate."
* The aggregate microformat contains all of the same attributes as the original microformat.
* Each attribute from the existing microformat can also take on some sub-attributes -- min, max, average, or sample. So an average rating would be class="rating average", a lowest price would be class="price min", a most recent blog post date would be class="updated max" (where max here is interpreted as the latest date), and a sample summary from a review would be class="summary sample".
* Aggregate microformats contain an additional attribute that isn't imported from the original microformat -- for purposes of discussion, let's call this "count." It contains the number of objects that are being summarized.
* 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 there are often highlighted instances on summary pages. Amazon shows the most popular reviews on the first page for a product and shopping aggregator sites usually show the best deal first in a list of offers.

== See also ==

* Aggregation of microformats: [[aggregate-microformat-template-examples|examples]] - [[aggregate-microformat-template-formats|formats]]
* Aggregate review: [[aggregate-review-examples|examples]] - [[aggregate-review-formats|formats]] - [[aggregate-review-brainstorming|brainstorming]]

aggregate-microformat-template-examples

2009-04-09T06:33:07Z

Kavi: /* Participants */

== The Problem ==

Many pages on the web contain or reference aggregates or summaries of other data: a summary of 173 reviews for a business, a summary of 25 running shoes for sale, a summary of a discussion with 501 individual posts. Naturally, the summary data is the best summary of the page itself and why a user should visit it.

We tried to solve this for the case of review summaries, but then realized that our approach applied to similar problems of aggregating other kinds of microformat data. The problem is to come up with a simple "pattern" or "template" that can be used to annotate aggregate information about pages that contain or reference multiple microformat instances.

== Participants ==
* Othar Hansson
* Kavi Goel

== Real-World Examples ==

=== Aggregate reviews (aggregate hReview) ===
Showing aggregate review information for products or businesses is very common on the web. hReview is designed to annotate a single user's review but not summarize a collection of user reviews.

* Amazon
** http://www.amazon.com/gp/product/B001FA1NFA/
** Aggregation of user reviews for a product. Up to 10 reviews per page
** Includes 1-5 stars average rating and the total number of reviews
** Also includes number of reviews for each score (1-5)

* Yelp
** http://www.yelp.com/biz/vive-sol-restaurant-mountain-view
** Shows 1-5 stars average rating and the total number of reviews
** Also includes number of reviews for each score (1-5)
** The site highlights recurring themes from reviews (i.e. "The food is delicious - love the chicken mole.") and the number of reviews where such comments were made.

For a longer list of aggregate review examples, see [[aggregate-review-examples]].

=== Summary of discussion boards (aggregate hAtom) ===

* BBC News
** http://newsforums.bbc.co.uk/nol/thread.jspa?forumID=6305&edition=2&ttl=20090406181909
** Shows the total number of comments posted and the date of the most recent post.

* AARP discussion board
** http://www.aarp.org/community/groups/searchGroups.bt?orderBy=1&categoryId=43
** Shows the total number of comments posted and the date of the most recent post.

=== Lists of product offers (aggregate hListing?) ===

Another common occurrence on the web is to have many offers for a product from different sellers. Shopping aggregators like Amazon, Nextag, Pricegrabber, etc all do this. Solving this problem also requires some rationalization of hListing and hProduct, but in any case aggregations of offers examples are as follows.

* Amazon
** http://www.amazon.com/Sony-BDP-S550-1080p-Blu-ray-Player/dp/B001FN3ZRQ
** Many aggregations on this page (aggregations of reviews and sellers)
** The "15 used & new from $254.12" shows the number of sellers and the low price amongst those offers

* CNET Reviews
** http://reviews.cnet.com/1770-5_7-0.html?query=monitor&tag=srch
** Shows price range (low and high price) and number of sellers for the Samsung SyncMaster T220.

* Pricegrabber
** http://clothing.pricegrabber.com/mens-athletic-shoes/Nike-Shox-Experience-Men-Running-Shoes/m83885830.html
** Shows the lowest priced offer and the number of offers

=== Summary info for lists of products (aggregate hProduct) ===

* BuyFineArt.com
** http://www.buy-fineart.com/pricerange.asp?f=50&t=99
** Shows price range and total count of products in the category

=== Summaries that only contain a count ===

For many search results pages (or category pages showing a list of items), just knowing the number of results is valuable.

* Recipes on Food Network
** http://www.foodnetwork.com/search/tortilla+soup/results.do?fnSearchType=recipe
** 102 recipes (aggregate hRecipe)
* People with the name "Kevin Marks" on Facebook
** http://www.facebook.com/s.php?q=kevin+marks&n=-1&k=400000000010&sf=r&init=q&sid=f88be874d43681c8bfd0d98fe3c47634
** 414 people (aggregate hCard)
* Concerts on Pollstar
** http://www.pollstar.com/resultsArtist.aspx?ID=74518&SortBy=Date&SearchBy=bob%20dylan
** 12 upcoming Bob Dylan concerts (aggregate hCalendar)

== See also ==

* Aggregation of microformats: [[aggregate-microformat-template-formats|formats]] - [[aggregate-microformat-template-brainstorming|brainstorming]]

* Aggregate reviews: [[aggregate-review-examples|examples]] - [[aggregate-review-formats|formats]] - [[aggregate-review-brainstorming|brainstorming]]

aggregate-microformat-template-examples

2009-04-07T20:01:47Z

Kavi: /* Lists of product offers (aggregate hListing?) */

== The Problem ==

Many pages on the web contain or reference aggregates or summaries of other data: a summary of 173 reviews for a business, a summary of 25 running shoes for sale, a summary of a discussion with 501 individual posts. Naturally, the summary data is the best summary of the page itself and why a user should visit it.

We tried to solve this for the case of review summaries, but then realized that our approach applied to similar problems of aggregating other kinds of microformat data. The problem is to come up with a simple "pattern" or "template" that can be used to annotate aggregate information about pages that contain or reference multiple microformat instances.

== Participants ==
* Othar Hansson
* Kavi Goel
* Jay Myers

== Real-World Examples ==

=== Aggregate reviews (aggregate hReview) ===
Showing aggregate review information for products or businesses is very common on the web. hReview is designed to annotate a single user's review but not summarize a collection of user reviews.

* Amazon
** http://www.amazon.com/gp/product/B001FA1NFA/
** Aggregation of user reviews for a product. Up to 10 reviews per page
** Includes 1-5 stars average rating and the total number of reviews
** Also includes number of reviews for each score (1-5)

* Yelp
** http://www.yelp.com/biz/vive-sol-restaurant-mountain-view
** Shows 1-5 stars average rating and the total number of reviews
** Also includes number of reviews for each score (1-5)
** The site highlights recurring themes from reviews (i.e. "The food is delicious - love the chicken mole.") and the number of reviews where such comments were made.

For a longer list of aggregate review examples, see [[aggregate-review-examples]].

=== Summary of discussion boards (aggregate hAtom) ===

* BBC News
** http://newsforums.bbc.co.uk/nol/thread.jspa?forumID=6305&edition=2&ttl=20090406181909
** Shows the total number of comments posted and the date of the most recent post.

* AARP discussion board
** http://www.aarp.org/community/groups/searchGroups.bt?orderBy=1&categoryId=43
** Shows the total number of comments posted and the date of the most recent post.

=== Lists of product offers (aggregate hListing?) ===

Another common occurrence on the web is to have many offers for a product from different sellers. Shopping aggregators like Amazon, Nextag, Pricegrabber, etc all do this. Solving this problem also requires some rationalization of hListing and hProduct, but in any case aggregations of offers examples are as follows.

* Amazon
** http://www.amazon.com/Sony-BDP-S550-1080p-Blu-ray-Player/dp/B001FN3ZRQ
** Many aggregations on this page (aggregations of reviews and sellers)
** The "15 used & new from $254.12" shows the number of sellers and the low price amongst those offers

* CNET Reviews
** http://reviews.cnet.com/1770-5_7-0.html?query=monitor&tag=srch
** Shows price range (low and high price) and number of sellers for the Samsung SyncMaster T220.

* Pricegrabber
** http://clothing.pricegrabber.com/mens-athletic-shoes/Nike-Shox-Experience-Men-Running-Shoes/m83885830.html
** Shows the lowest priced offer and the number of offers

=== Summary info for lists of products (aggregate hProduct) ===

* BuyFineArt.com
** http://www.buy-fineart.com/pricerange.asp?f=50&t=99
** Shows price range and total count of products in the category

=== Summaries that only contain a count ===

For many search results pages (or category pages showing a list of items), just knowing the number of results is valuable.

* Recipes on Food Network
** http://www.foodnetwork.com/search/tortilla+soup/results.do?fnSearchType=recipe
** 102 recipes (aggregate hRecipe)
* People with the name "Kevin Marks" on Facebook
** http://www.facebook.com/s.php?q=kevin+marks&n=-1&k=400000000010&sf=r&init=q&sid=f88be874d43681c8bfd0d98fe3c47634
** 414 people (aggregate hCard)
* Concerts on Pollstar
** http://www.pollstar.com/resultsArtist.aspx?ID=74518&SortBy=Date&SearchBy=bob%20dylan
** 12 upcoming Bob Dylan concerts (aggregate hCalendar)

== See also ==

* Aggregation of microformats: [[aggregate-microformat-template-formats|formats]] - [[aggregate-microformat-template-brainstorming|brainstorming]]

* Aggregate reviews: [[aggregate-review-examples|examples]] - [[aggregate-review-formats|formats]] - [[aggregate-review-brainstorming|brainstorming]]

aggregate-microformat-template-examples

2009-04-06T18:47:53Z

Kavi:

== The Problem ==

Many pages on the web contain or reference aggregates or summaries of other data: a summary of 173 reviews for a business, a summary of 25 running shoes for sale, a summary of a discussion with 501 individual posts. Naturally, the summary data is the best summary of the page itself and why a user should visit it.

We tried to solve this for the case of review summaries, but then realized that our approach applied to similar problems of aggregating other kinds of microformat data. The problem is to come up with a simple "pattern" or "template" that can be used to annotate aggregate information about pages that contain or reference multiple microformat instances.

== Participants ==
* Othar Hansson
* Kavi Goel
* Jay Myers

== Real-World Examples ==

=== Aggregate reviews (aggregate hReview) ===
Showing aggregate review information for products or businesses is very common on the web. hReview is designed to annotate a single user's review but not summarize a collection of user reviews.

* Amazon
** http://www.amazon.com/gp/product/B001FA1NFA/
** Aggregation of user reviews for a product. Up to 10 reviews per page
** Includes 1-5 stars average rating and the total number of reviews
** Also includes number of reviews for each score (1-5)

* Yelp
** http://www.yelp.com/biz/vive-sol-restaurant-mountain-view
** Shows 1-5 stars average rating and the total number of reviews
** Also includes number of reviews for each score (1-5)
** The site highlights recurring themes from reviews (i.e. "The food is delicious - love the chicken mole.") and the number of reviews where such comments were made.

For a longer list of aggregate review examples, see [[aggregate-review-examples]].

=== Summary of discussion boards (aggregate hAtom) ===

* BBC News
** http://newsforums.bbc.co.uk/nol/thread.jspa?forumID=6305&edition=2&ttl=20090406181909
** Shows the total number of comments posted and the date of the most recent post.

* AARP discussion board
** http://www.aarp.org/community/groups/searchGroups.bt?orderBy=1&categoryId=43
** Shows the total number of comments posted and the date of the most recent post.

=== Lists of product offers (aggregate hListing?) ===

Another common occurrence on the web is to have many offers for a product from different sellers. Shopping aggregators like Amazon, Nextag, Pricegrabber, etc all do this. Solving this problem also requires some rationalization of hListing and hProduct, but in any case aggregations of offers examples are as follows.

* Amazon
** http://www.amazon.com/Sony-BDP-S550-1080p-Blu-ray-Player/dp/B001FN3ZRQ/ref=pd_bbs_sr_3?ie=UTF8&s=electronics&qid=1239042485&sr=8-3
** Many aggregations on this page (aggregations of reviews and sellers)
** The "15 used & new from $254.12" shows the number of sellers and the low price amongst those offers

* CNET Reviews
** http://reviews.cnet.com/1770-5_7-0.html?query=monitor&tag=srch
** Shows price range (low and high price) and number of sellers for the Samsung SyncMaster T220.

* Pricegrabber
** http://clothing.pricegrabber.com/mens-athletic-shoes/Nike-Shox-Experience-Men-Running-Shoes/m83885830.html
** Shows the lowest priced offer and the number of offers

=== Summary info for lists of products (aggregate hProduct) ===

* BuyFineArt.com
** http://www.buy-fineart.com/pricerange.asp?f=50&t=99
** Shows price range and total count of products in the category

=== Summaries that only contain a count ===

For many search results pages (or category pages showing a list of items), just knowing the number of results is valuable.

* Recipes on Food Network
** http://www.foodnetwork.com/search/tortilla+soup/results.do?fnSearchType=recipe
** 102 recipes (aggregate hRecipe)
* People with the name "Kevin Marks" on Facebook
** http://www.facebook.com/s.php?q=kevin+marks&n=-1&k=400000000010&sf=r&init=q&sid=f88be874d43681c8bfd0d98fe3c47634
** 414 people (aggregate hCard)
* Concerts on Pollstar
** http://www.pollstar.com/resultsArtist.aspx?ID=74518&SortBy=Date&SearchBy=bob%20dylan
** 12 upcoming Bob Dylan concerts (aggregate hCalendar)

== See also ==

* Aggregation of microformats: [[aggregate-microformat-template-formats|formats]] - [[aggregate-microformat-template-brainstorming|brainstorming]]

* Aggregate reviews: [[aggregate-review-examples|examples]] - [[aggregate-review-formats|formats]] - [[aggregate-review-brainstorming|brainstorming]]

aggregate-microformat-template-examples

2009-04-06T18:46:56Z

Kavi:

== The Problem ==

Many pages on the web contain or reference aggregates or summaries of other data: a summary of 173 reviews for a business, a summary of 25 running shoes for sale, a summary of a discussion with 501 individual posts. Naturally, the summary data is the best summary of the page itself and why a user should visit it.

We tried to solve this for the case of review summaries, but then realized that our approach applied to similar problems of aggregating other kinds of microformat data. The problem is to come up with a simple "pattern" or "template" that can be used to annotate aggregate information about pages that contain or reference multiple microformat instances.

== Participants ==
* Othar Hansson
* Kavi Goel
* Jay Myers

== Real-World Examples ==

=== Aggregate reviews (aggregate hReview) ===
Showing aggregate review information for products or businesses is very common on the web. hReview is designed to annotate a single user's review but not summarize a collection of user reviews.

* Amazon
** http://www.amazon.com/gp/product/B001FA1NFA/
** Aggregation of user reviews for a product. Up to 10 reviews per page
** Includes 1-5 stars average rating and the total number of reviews
** Also includes number of reviews for each score (1-5)

* Yelp
** http://www.yelp.com/biz/vive-sol-restaurant-mountain-view
** Shows 1-5 stars average rating and the total number of reviews
** Also includes number of reviews for each score (1-5)
** The site highlights recurring themes from reviews (i.e. "The food is delicious - love the chicken mole.") and the number of reviews where such comments were made.

For a longer list of aggregate review examples, see [[aggregate-review-examples]].

=== Summary of discussion boards (aggregate hAtom) ===

* BBC News
** http://newsforums.bbc.co.uk/nol/thread.jspa?forumID=6305&edition=2&ttl=20090406181909
** Shows the total number of comments posted and the date of the most recent post.

* AARP discussion board
** http://www.aarp.org/community/groups/searchGroups.bt?orderBy=1&categoryId=43
** Shows the total number of comments posted and the date of the most recent post.

=== Lists of product offers (aggregate hListing?) ===

Another common occurrence on the web is to have many offers for a product from different sellers. Shopping aggregators like Amazon, Nextag, Pricegrabber, etc all do this. Solving this problem also requires some rationalization of hListing and hProduct, but in any case aggregations of offers examples are as follows.

* Amazon
** http://www.amazon.com/Sony-BDP-S550-1080p-Blu-ray-Player/dp/B001FN3ZRQ/ref=pd_bbs_sr_3?ie=UTF8&s=electronics&qid=1239042485&sr=8-3
** Many aggregations on this page (aggregations of reviews and sellers)
** The "15 used & new from $254.12" shows the number of sellers and the low price amongst those offers

* CNET Reviews
** http://reviews.cnet.com/1770-5_7-0.html?query=monitor&tag=srch
** Shows price range (low and high price) and number of sellers for the Samsung SyncMaster T220.

* Pricegrabber
** http://clothing.pricegrabber.com/mens-athletic-shoes/Nike-Shox-Experience-Men-Running-Shoes/m83885830.html
** Shows the lowest priced offer and the number of offers

=== Summary info for lists of products (aggregate hProduct) ===

* BuyFineArt.com
** http://www.buy-fineart.com/pricerange.asp?f=50&t=99
** Shows price range and total count of products in the category

=== Summaries that only contain a count ===

For many search results pages (or category pages showing a list of items), just knowing the number of results is valuable.

* Recipes on Food Network
** http://www.foodnetwork.com/search/tortilla+soup/results.do?fnSearchType=recipe
** 102 recipes (aggregate hRecipe)
* People with the name "Kevin Marks" on Facebook
** http://www.facebook.com/s.php?q=kevin+marks&n=-1&k=400000000010&sf=r&init=q&sid=f88be874d43681c8bfd0d98fe3c47634
** 414 people (aggregate hCard)
* Concerts on Pollstar
** http://www.pollstar.com/resultsArtist.aspx?ID=74518&SortBy=Date&SearchBy=bob%20dylan
** 12 upcoming Bob Dylan concerts (aggregate hCalendar)

== See also ==

* Aggregate reviews: [[aggregate-review-examples|examples]] - [[aggregate-review-formats|formats]] - [[aggregate-review-brainstorming|brainstorming]]

aggregate-microformat-template-examples

2009-04-06T18:45:19Z

Kavi: New page: == The Problem == Many pages on the web contain or reference aggregates or summaries of other data: a summary of 173 reviews for a business, a summary of 25 running shoes for sale, a summ...

== The Problem ==

Many pages on the web contain or reference aggregates or summaries of other data: a summary of 173 reviews for a business, a summary of 25 running shoes for sale, a summary of a discussion with 501 individual posts. Naturally, the summary data is the best summary of the page itself and why a user should visit it.

We tried to solve this for the case of review summaries, but then realized that our approach applied to similar problems of aggregating other kinds of microformat data. The problem is to come up with a simple "pattern" or "template" that can be used to annotate aggregate information about pages that contain or reference multiple microformat instances.

== Participants ==
* Othar Hansson
* Kavi Goel
* Jay Myers

== Real-World Examples ==

=== Aggregate reviews (aggregate hReview) ===
Showing aggregate review information for products or businesses is very common on the web. hReview is designed to annotate a single user's review but not summarize a collection of user reviews.

* Amazon
** http://www.amazon.com/gp/product/B001FA1NFA/
** Aggregation of user reviews for a product. Up to 10 reviews per page
** Includes 1-5 stars average rating and the total number of reviews
** Also includes number of reviews for each score (1-5)

* Yelp
** http://www.yelp.com/biz/vive-sol-restaurant-mountain-view
** Shows 1-5 stars average rating and the total number of reviews
** Also includes number of reviews for each score (1-5)
** The site highlights recurring themes from reviews (i.e. "The food is delicious - love the chicken mole.") and the number of reviews where such comments were made.

For a longer list of aggregate review examples, see [[aggregate-review-examples]].

=== Summary of discussion boards (aggregate hAtom) ===

* BBC News
** http://newsforums.bbc.co.uk/nol/thread.jspa?forumID=6305&edition=2&ttl=20090406181909
** Shows the total number of comments posted and the date of the most recent post.

* AARP discussion board
** http://www.aarp.org/community/groups/searchGroups.bt?orderBy=1&categoryId=43
** Shows the total number of comments posted and the date of the most recent post.

=== Lists of product offers (aggregate hListing?) ===

Another common occurrence on the web is to have many offers for a product from different sellers. Shopping aggregators like Amazon, Nextag, Pricegrabber, etc all do this. Solving this problem also requires some rationalization of hListing and hProduct, but in any case aggregations of offers examples are as follows.

* Amazon
** http://www.amazon.com/Sony-BDP-S550-1080p-Blu-ray-Player/dp/B001FN3ZRQ/ref=pd_bbs_sr_3?ie=UTF8&s=electronics&qid=1239042485&sr=8-3
** Many aggregations on this page (aggregations of reviews and sellers)
** The "15 used & new from $254.12" shows the number of sellers and the low price amongst those offers

* CNET Reviews
** http://reviews.cnet.com/1770-5_7-0.html?query=monitor&tag=srch
** Shows price range (low and high price) and number of sellers for the Samsung SyncMaster T220.

* Pricegrabber
** http://clothing.pricegrabber.com/mens-athletic-shoes/Nike-Shox-Experience-Men-Running-Shoes/m83885830.html
** Shows the lowest priced offer and the number of offers

=== Summary info for lists of products (aggregate hProduct) ===

* BuyFineArt.com
** http://www.buy-fineart.com/pricerange.asp?f=50&t=99
** Shows price range and total count of products in the category

=== Summaries that only contain a count ===

For many search results pages (or category pages showing a list of items), just knowing the number of results is valuable.

* Recipes on Food Network
** http://www.foodnetwork.com/search/tortilla+soup/results.do?fnSearchType=recipe
** 102 recipes (aggregate hRecipe)
* People with the name "Kevin Marks" on Facebook
** http://www.facebook.com/s.php?q=kevin+marks&n=-1&k=400000000010&sf=r&init=q&sid=f88be874d43681c8bfd0d98fe3c47634
** 414 people (aggregate hCard)
* Concerts on Pollstar
** http://www.pollstar.com/resultsArtist.aspx?ID=74518&SortBy=Date&SearchBy=bob%20dylan
** 12 upcoming Bob Dylan concerts (aggregate hCalendar)

aggregate-review-examples

2009-04-06T17:38:31Z

Kavi:

== The Problem ==
''There are various services that provide aggregate ratings and reviews on the Web. How should this information be presented in microformat form? hReview is oriented towards individual reviews with ratings; can it also be used for presenting data from aggregate reviews?''
== Participants ==
* John Panzer
* Kavi Goel
* Jay Myers

== Real-World Examples ==
''Links to public web pages, either popular or insightful''

=== Amazon ===
* http://www.amazon.com/gp/product/B001FA1NFA/
* Aggregation of user reviews for a product. Up to 10 reviews per page
* Includes 1-5 stars average rating and the total number of reviews
* Also includes number of reviews for each score (1-5)

=== Bizrate ===
* Aggregation of user reviews for a product. Up to 10 reviews per page
* Includes 1-5 stars average rating and the total number of reviews

=== Citysearch ===
* http://siliconvalley.citysearch.com/profile/11636582/mountain_view_ca/vive_sol.html
* Shows 1-5 stars average rating and the total number of reviews on the "business info" page
* On the "reviews" page, it also includes the number of reviews for each score (1-5) and some themes from the reviews (i.e. "Prompt seating", "Romantic", "Good for groups")

=== CNet Reviews ===
* http://reviews.cnet.com/car-gps-navigation/garmin-nuvi-880/4505-3430_7-32815498.html
* Shows both editors rating (1-5 stars as well as a word describing the rating, i.e. "Excellent") and the average user rating (1-5 stars) and total number of user reviews
* Only shows editor's review and 3 user reviews on first page for a product.
* Clicking through shows 5 reviews per page.

=== Download.com ===
* http://www.download.com/Ad-Aware-2008/3000-8022_4-10045910.html
* Shows both editors rating (1-5 stars) and the average user rating (1-5 stars) and total number of votes
* 5 user reviews shown per page

=== Rotten Tomatoes ===
* http://www.rottentomatoes.com/m/quantum_of_solace/
* Shows percentage of positive reviews from users (in this case, users = movie critics) and number of reviews
* An average rating (between 1 and 10) is also shown, but this data is de-emphasized on the Rotten Tomatoes movies pages.

=== Yelp ===
* http://www.yelp.com/biz/vive-sol-restaurant-mountain-view
* Shows 1-5 stars average rating and the total number of reviews
* Also includes number of reviews for each score (1-5)
* The site highlights recurring themes from reviews (i.e. "The food is delicious - love the chicken mole.") and the number of reviews where such comments were made.

== Coded examples ==

(Note: examples may contain additional markup for positioning and presentation purposes to simulate live production markup)

=== aggregate reviews embedded in hproduct block ===
<pre><nowiki>
<div class="hproduct">
<ol class="clearfloat" id="breadcrumbs">
<li><a href="http://www.yoursite.com">Home</a></li>
<li class="category"><a href="http://www.yoursite.com/computers/">Computers</a></li>
<li class="category"><a href="http://www.yoursite.com/computers/networking/">Networking</a></li>
<li class="category"><a href="http://www.yoursite.com/computers/networking/print-servers">Print Servers</a></li>
</ol>
<h1 class="n">NETGEAR 802.11g Wireless USB Print Server with 4-Port Switch</h1>
<div id="topbox">
<div class="rightcol">
<img src="http://images.yoursite.com/images/products/7250/7250707_rb.jpg" alt="Image of NETGEAR WGPS606" class="photo" />
</div>
<div class="leftcol">
<div class="infomain">
<ul>
<li>
<strong>Brand: </strong><span class="brand">NETGEAR</span>
</li>
<li>
<strong>Model: </strong><span class="model">WGPS606</span>
</li>
<li class="identifier">
<span class="type">SKU: </span><span class="value">7250707</span>
</li>
</ul>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://images.yoursite.com/path/to/product" class="url"><img src="http://images.yoursite.com/images/misc/ratings_star_3_5.gif" alt="3.5 out of 5 stars"/></a></span><span class="rating">4.7</span> / <span class="best">5</span> (<span class="num">13</span> reviews)</div>
</div>
</div>
<p class="description">
Share a USB printer with others on your network; up to 54 Mbps; 2 USB ports; wireless Ethernet bridge mode with 4-port switch
</p>
<p>
<span class="availability online">Available online</span>. <span class="shipping">Shipping: Usually leaves our warehouse in 1 business day. <span class="money">Estimated shipping cost: <abbr class="currency" title="USD" lang="en">$</abbr><span class="amount">6.99</span>.</span></span>

</p>
<p>
<span class="availability instore">Available in our stores</span>. Store Pickup: Available at most stores
</p>
<p>
<span class="availability specialorder">Not available for special order</span>.
</p>
</div>
<div class="infoside">
<span class="price regular"><span class="money"><strong>Price: </strong><abbr class="currency" title="USD" lang="en">$</abbr><span class="amount">99.99</span></span></span>
<div>
<a href="http://images.yoursite.com/path/to/buy/product" class="buy"><img src="http://images.yoursite.com/images/btn_add_to_cart.gif" alt="buy this product" /></a>
</div>
</div>
</div>
</div>

</nowiki></pre>

=== hlisting, hproduct, haggregatereview/hreview, xoxo ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/tv-and-video">TV & Video</a></li>
<li class="category"><a href="http://storename.com/televisions">Televisions</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/samsung-ln40a550.jpg" class="photo" alt="picture of samsung ln40a550" />
<div class="fn"><span class="brand">Samsung</span> - 40" 1080p Flat-Panel LCD HDTV</div>
<dl class="identifier">
<dt>Model</dt>
<dd>LN40A550</dd>
<dt>SKU</dt>
<dd>8749465</dd>
</dl>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_3_5.gif" alt="3.5 out of 5 stars"/></a></span><span class="rating">4.7</span> / <span class="best">5</span> (<span class="num">13</span> reviews)</div>
</div>
</div>
<div class="price">$1,099.99</div>
<ol class="xoxo">
<li><h2>Specifications</h2>
<dl>
<dt>Warranty Terms - Parts</dt>
<dd>1 year</dd>
<dt>Warranty Terms - Labor</dt>
<dd>1 year</dd>
<dt>Product Height</dt>
<dd>27" with stand (24-7/10" without)</dd>
<dt>Product Width</dt>
<dd>39-1/5"</dd>
<dt>Product Weight</dt>
<dd>61.5 lbs. with stand (54.5 lbs. without)</dd>
<dt>Product Depth</dt>
<dd>11-4/5" with stand (3-3/5" without)</dd>
<dt>TV Type</dt>
<dd>LCD Flat-Panel</dd>
</dl>
</li>
</div>
</div>
</nowiki></pre>

=== hlisting, hproduct, haudio, haggregatereview/hreview ===

<pre><nowiki>
<div class="hlisting">
<div class="hproduct haudio">
<ol>
<li class="lister"><a href="http://storename.com">Store name</a></li>
<li class="category"><a href="http://storename.com/gangsta">Gangsta/Hardcore</a></li>
<li>Product Info</li>
</ol>
<img src="http://images.storename.com/products/50cent-curtis.jpg" class="photo" alt="picture of 50 cent" />
<div class="album">Curtis</div>
<div class="contributor"><span class="vcard"><span class=n nickname">50 Cent</span></span></div>
<p>Release date:<abbr class="published" title="2007-09-11">September 11, 2007</abbr></p>
<div class="haggregatereview">
<div class="hreview">
<span class="fn"><a href="http://storename.com/path/to/product" class="url"><img src="http://images.storename.com/images/misc/ratings_star_4_0.gif" alt="4 out of 5 stars"/></a></span><span class="rating">4.0</span> / <span class="best">5</span> Number of reviews:(<span class="num">4</span> reviews)</div>
</div>
<div class="price">$9.99</div>
<a href="add-to-cart-url" rel="payment"><img src="http://storename.com/images/global/add-to-cart.gif" alt="add to cart" /></a>
<h2>Tracks</h2>
<ol>
<li class="item"><span class="position">1</span>.<span class="fn">Intro</span><a href="http://images.storename.com/media/sample/50cent-intro.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">2</span>.<span class="fn">My Gun Go Off</span><a href="http://images.storename.com/media/sample/50cent-gun-go-off.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">3</span>.<span class="fn">Man Down - (censored)</span><a href="http://images.storename.com/media/sample/50cent-man-down.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">4</span>.<span class="fn">I'll Still Kill - (with Akon)</span><a href="http://images.storename.com/media/sample/50cent-ill-still-kill.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">5</span>.<span class="fn">I Get Money</span><a href="http://images.storename.com/media/sample/50cent-i-get-money.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">6</span>.<span class="fn">Come & Go - (with Dr. Dre)</span><a href="http://images.storename.com/media/sample/50cent-come-go.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">7</span>.<span class="fn">Ayo Technology - (with Timbaland/Justin Timberlake)</span><a href="http://images.storename.com/media/sample/50cent-ayo-technology.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">8</span>.<span class="fn">Follow My Lead - (with Robin Thicke)</span><a href="http://images.storename.com/media/sample/50cent-follow-my-lead.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">9</span>.<span class="fn">Movin' on Up</span><a href="http://images.storename.com/media/sample/50cent-movin-on-up.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">10</span>.<span class="fn">Straight to the Bank</span><a href="http://images.storename.com/media/sample/50cent-straight-to-bank.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">11</span>.<span class="fn">Amusement Park</span><a href="http://images.storename.com/media/sample/50cent-amusement-park.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">12</span>.<span class="fn">Fully Loaded Clip</span><a href="http://images.storename.com/media/sample/50cent-fully-loaded-clip.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">13</span>.<span class="fn">Peep Show - (with Eminem)</span><a href="http://images.storename.com/media/sample/50cent-peep-show.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">14</span>.<span class="fn">Fire - (with Young Buck/Nicole Scherzinger)</span><a href="http://images.storename.com/media/sample/50cent-fire.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">15</span>.<span class="fn">All of Me - (with Mary J. Blige)</span><a href="http://images.storename.com/media/sample/50cent-all-of-me.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">16</span>.<span class="fn">Curtis 187</span><a href="http://images.storename.com/media/sample/50cent-curtis-187.mp3" rel="sample">Listen</a></li>
<li class="item"><span class="position">17</span>.<span class="fn">Touch the Sky - (with Tony Yayo)</span><a href="http://images.storename.com/media/sample/50cent-touch-the-sky.mp3" rel="sample">Listen</a></li>
</ol>
</div>
</div>
</nowiki></pre>

== Existing Practices ==
* ''Summary of common patterns discovered''
* ''Other attempts to solve The Problem''
== Proposal ==
* Early drafts
* ''Link to related pages as they become available''
* I think that this page from email discussion actually is a non-example: http://webcenter.polls.aol.com/poll?view=69043&pollId=69096 ; it's actually aggregate rankings with numerical weightings, which might lead to an interesting hRanking microformat but I think is out of bounds for an 'aggregate review' discussion.
** -brainstorming
** - proposal
** -microformat
== See Also ==
* Aggregation of microformats: [[aggregate-microformat-template-examples|examples]] - [[aggregate-microformat-template-formats|formats]] - [[aggregate-microformat-template-brainstorming|brainstorming]]
* Aggregate review: [[aggregate-review-formats|formats]] - [[aggregate-review-brainstorming|brainstorming]]
* [[review-examples]] for examples of individual reviews
* [[hreview|hReview]]
* ''Normative references for tags used''

aggregate-review-brainstorming

2009-02-09T18:51:57Z

Kavi:

Ideas for how to support aggregate reviews via microformats.

== Common themes amongst examples (that we might want to support) ==

* Aggregations of reviews always contain these two elements:
** the number of reviewers
** the average rating

* Other elements that occur in the example set include:
** the number of reviews for each rating (i.e. 10 5-star ratings, 7 4-star ratings, etc)
** recurring themes about the entity being reviewed (i.e. "romantic restaurant" or "love the chicken mole").
** who are the reviewers (i.e. "critics" or "users"). Some sites (i.e. Rotten Tomatoes or GameSpot) have multiple sets of aggregate reviews to cover both critics and users.

* In addition, some elements already present in the hReview schema exist in aggregate reviews as well:
** review summary/description
** most recent date reviewed

== Proposal discussed over IRC ==

==== What is the proposal? ====
* Define a new microformat for aggregate reviews.
* The format will contain only value (the number of reviews) and an embedded hReview that contains details like the average review score, summary, and a reference to the object of the review.

==== Why was this proposal preferred? ====
* Creating a new uF rather than extending hReview doesn't require branching the spec for hReview and provides clean separation in case we want to extend the new format to include other data in the future
* Supporting only the number of reviews (rather than scores per rating, etc) is probably sufficient for 80% of sites with aggregate reviews.

== All proposals suggested ==

==== 1) Do nothing. Aggregation must be done by the microformats parser ====
* Pros: Doesn't require any change to the existing microformats definitions
* Cons: Very difficult for parsers. Reviews for a single entity are usually not limited to a single web page (there are typically no more than 5-10 reviews per page), so aggregating this data would require the parser to figure out which pages to crawl to assemble the aggregate scores.

==== 2) Extend existing hReview format to include "reviewcount" ====
* Any hReview that contains a reviewcount field (which denotes the number of reviewers) would implicitly refer to an aggregation of reviews. The rating would correspond to the average rating of all individual reviews, summary/description refer to a summary of overall sentiments from the reviews, date refers to the most recent review's date.
* Pros: very simple addition to the existing microformat
* Cons: Mild overloading of what an hReview contains -- a review can now correspond to a single user's review or an aggregation of user reviews.

==== 3) Define a new microformat type for aggregate reviews ====
* This type could contain the staples -- average review score and number of reviewers -- as well as some of the other sometimes-used features listed in the "common themes" section earlier.
* Pros: robust way to mark up many elements of aggregate review information
* Cons: some redundancy with hReview. Extending hReview might be sufficient

== See Also ==
* Aggregate reviews: [[aggregate-review-examples|examples]] - [[aggregate-review-formats|formats]]
* [[hreview|hReview]]

aggregate-review-brainstorming

2009-01-12T23:12:05Z

Kavi: /* Discussion */

Ideas for how to support aggregate reviews via microformats.

== Common themes amongst examples (that we might want to support) ==

* Aggregations of reviews always contain these two elements:
** the number of reviewers
** the average rating

* Other elements that occur in the example set include:
** the number of reviews for each rating (i.e. 10 5-star ratings, 7 4-star ratings, etc)
** recurring themes about the entity being reviewed (i.e. "romantic restaurant" or "love the chicken mole").
** who are the reviewers (i.e. "critics" or "users"). Some sites (i.e. Rotten Tomatoes or GameSpot) have multiple sets of aggregate reviews to cover both critics and users.

* In addition, some elements already present in the hReview schema exist in aggregate reviews as well:
** review summary/description
** most recent date reviewed

== Proposals ==

==== 1) Do nothing. Aggregation must be done by the microformats parser ====
* Pros: Doesn't require any change to the existing microformats definitions
* Cons: Very difficult for parsers. Reviews for a single entity are usually not limited to a single web page (there are typically no more than 5-10 reviews per page), so aggregating this data would require the parser to figure out which pages to crawl to assemble the aggregate scores.

==== 2) Extend existing hReview format to include "reviewcount" ====
* Any hReview that contains a reviewcount field (which denotes the number of reviewers) would implicitly refer to an aggregation of reviews. The rating would correspond to the average rating of all individual reviews, summary/description refer to a summary of overall sentiments from the reviews, date refers to the most recent review's date.
* Pros: very simple addition to the existing microformat
* Cons: Mild overloading of what an hReview contains -- a review can now correspond to a single user's review or an aggregation of user reviews.

==== 3) Define a new microformat type for aggregate reviews ====
* This type could contain the staples -- average review score and number of reviewers -- as well as some of the other sometimes-used features listed in the "common themes" section earlier.
* Pros: robust way to mark up many elements of aggregate review information
* Cons: some redundancy with hReview. Extending hReview might be sufficient

== Discussion ==

* Kavi: option #2 seems simple and covers the 80% case well for supporting aggregate reviews.

== See Also ==
* Aggregate reviews: [[aggregate-review-examples|examples]] - [[aggregate-review-formats|formats]]
* [[hreview|hReview]]