aggregate-review-brainstorming

(Difference between revisions)

Jump to: navigation, search
(Common themes amongst examples (that we might want to support))
(3) Define a new microformat type for aggregate reviews)
Line 31: Line 31:
* 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.
* 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
* Pros: robust way to mark up many elements of aggregate review information
-
* Cons: some redundancy with hReview. Extending hReview might be simpler and sufficient
+
* Cons: some redundancy with hReview. Extending hReview might be sufficient
-
 
+
== Discussion ==
== Discussion ==

Revision as of 03:17, 23 December 2008

Ideas for how to support aggregate reviews via microformats.


Contents

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

Proposals

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

Discussion

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

Views