aggregate-review-brainstorming

(Difference between revisions)

Jump to: navigation, search
(4) Do not use hreview classes in hreview-aggregate)
(discussion)
Line 7: Line 7:
** the number of reviewers
** the number of reviewers
** the average rating
** 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''
* Other elements that occur in the example set include:
* Other elements that occur in the example set include:

Revision as of 16:57, 7 September 2009

Ideas for how to support aggregate reviews via microformats.


Contents

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

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

Proposal discussed over IRC

What is the proposal?

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

Why was this proposal preferred?

Other proposals suggested

1) Do nothing. Aggregation must be done by the microformats parser

2) Extend existing hReview format to include "reviewcount"

3) Define a new microformat type for aggregate reviews

4) Do not use hreview classes in hreview-aggregate

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.

See Also

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

Views