aggregate-review-brainstorming

(Difference between revisions)

Jump to: navigation, search
(note specifically other proposals, and that chosen/consensus proposal should be written up as a draft.)
(Other proposals suggested)
Line 45: Line 45:
* Cons: some redundancy with hReview. Extending hReview might be sufficient
* 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>&lt;a class="item include" href="#my_business_hcard"&gt;&lt;/a&gt;</code>
 +
** Without including links with duplicate redundant information that is part of the hcard, example <code>&lt;a class="item include make_me_invisible_to_user" href="#my_business_hcard"&gt;Business Name&lt;/a&gt;</code>
 +
** Without adding listing information, such as the type of listing: <code>&lt;span class="type"&gt;business&lt;/span&gt;</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.
 +
* 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'''. 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.
== See Also ==
== See Also ==

Revision as of 06:36, 2 June 2009

Ideas for how to support aggregate reviews via microformats.


Contents

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

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