View source for hreview-feedback

= hReview Feedback =

This document is for keeping track of feedback about [[hreview|hReview]], one of several MicroFormats.

== Template ==
{{issues-format}}

== Feedback ==
=== General Questions ===
See the [[hreview-faq|hReview FAQ]].

=== General Comments ===

April 30, 2005:

Nice work :-) Some questions:

For the most part, the concept of the format's "fields" translates, in any particular case, to the field name appearing in the class attribute of an element, and the field value appearing in the text of the element. Right?

Can it be generally stated that it doesn't matter which elements these class/fields are attached to? If not, what are the specific constraints?

It'd be useful to outline any cases where:

* fields or values appear in other attributes (e.g., class="type" title="business")

* an element indicated as a field can contain more than text, or a mix of text and other elements (e.g., some of the 1 of 5 type rating span examples)

Also, what is the constraint about class attributes containing multiple values where one is a field name (i.e., I assume you're not supposed to put two field names in the same class--but, what is the extent of the constraint? Can multiple class values be used as long as they don't look like two field names?)

'''See [[hcard-parsing]] which answers these questions. -[http://tantek.com/log/ Tantek]'''


Also ([[rel-tag]] question), does rel-tag support this kind of eleaborate label (where the tag indicated element has more than just a text value that exactly matches the last part of the uri?):

<pre><nowiki>
<li><a href="http://flickr.com/photos/tags/Price" rel="tag">
Price: <abbr class="rating" title="2">$$</abbr>...</a></li>
</nowiki></pre>

Doesn't RelTag significantly constrain what appears enclosed within the A element? i.e., (from Technorati's tag description:)
<pre><nowiki>
 <a href="http://technorati.com/tag/[tagname]" rel="tag">[tagname]</a>
</nowiki></pre>
-[http://icite.net/blog/ Jay Fienberg]
</pre></nowiki>

'''See the [[rel-tag]] spec.  The last segment of the URL is the tagname, not the contents of the element.  The Technorati help page is only providing suggested markup.  See the spec for normative details. -[http://tantek.com/log/ Tantek]'''



----

I don't know how widespread it is to have summaries of a review in one place and then point to them in another, but that's something I do on one of my sites, where reviews are accepted by trackback (eg. [http://grwifi.net/location/Common+Ground+Coffee+Shop | this page]). I've blogged a possible markup for that [http://jystewart.net/process/archives/2005/04/initial-thoughts-on-hreview/ | here]

- JamesStewart


'''Thus the "description" is optional, and you can provide a URL permalink back to the original. -[http://tantek.com/log/ Tantek]'''

----

I've added some items to the  FAQ page ([[hreview-faq|hReview FAQ]]) Please take a look at them and feel free to clarify or modify.

-RyanKing

----

I've been following the evolution of microformats on Technorati with great interest and hReview seems to really break new ground. Reviews represent something big enough that they have their own identity, they can be 'referenced'. In contrast hCard and hCalendar seem to be more of a 'pass-by-value' proposition (I've ammended my SmartTag + AutoLink = SmartLink [http://adriancuthbert.blogspot.com/2005/04/smartlink.html experiment] to support [[hcalendar|hCalendar]]). To that end I was surprised at the specification. I've explained things more fully [http://adriancuthbert.blogspot.com/2005/05/review-of-hreview.html here]

-[http://www.technorati.com/profile/acuth Adrian Cuthbert]

----

Has anyone considered list context? I have adapted my Developer's Resource Index, which is in essence a list of reviews, to use the hReview spec. However, is it appropriate to set the entire list as <code>&lt:dl class="hreview"&gt;</code>, or each individual item by wrapping the <code>&lt;dt&gt;</code>/<code>&lt;dd&gt;</code> pairs in a &lt;div&gt; (which is the approach I took)?

'''Follow-up''': scratch that last comment: Since I'm using XHTML 1.1, <div> is not allowed in this context. Which of course brings me back to the original question. Hmm...

Have a look at an example of the code if you'd like: [http://loadaveragezero.com/app/drx/Data_Formats/Markup_Languages Markup Languages]. I will post this URI to del.icio.us tagged as hreview as well.

[http://loadaveragezero.com/hnav/contact.php Douglas Clifton]

----

Shouldn't it be mentioned somewhere in which language the review is written in? Is it just a slip of the mind, or a very US-centric attitude, dude? I don’t think adding language info would be out of scope, as it would help filter out unwanted languages from search queries; plus, Ce n’est pas parce que mon blog est en anglais, &#44845; &#33521;&#35486;&#47564; &#50416;&#45716; &#44163;&#51060; &#50500;&#45768;&#45796;… What if I wanted to post the same review in different languages, or quote something in another language..?

[http://sungnyemun.org/wordpress/ dda]

'''Thanks for your input.  This was made explicit and resolved by hReview 0.2, specifically: [http://microformats.org/wiki/hreview#Language hReviews and language] -[http://tantek.com/log/ Tantek]'''

----
A sample xhtml fragment of "Multidimensional Restaurant Review" is not valid XML format.

original:
  This <abbr class="type" title="business">
  <a href="http://en.wikipedia.org/wiki/cafe" rel="tag">cafe</abbr></a> 

correct:
  This <abbr class="type" title="business">
  <a href="http://en.wikipedia.org/wiki/cafe" rel="tag">cafe</a></abbr> 

[http://yohei-y.blogspot.com YAMAMOTO Yohei]

'''Thanks for the feedback Yamamoto, that was my typo and the example has been corrected. - [http://tantek.com/ Tantek]'''

----
* 2005-06-21 raised by Hixie
*# ''Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how hReviews must be parsed, how to handle errors, and so forth. Is it defined in terms of the DOM? Is it defined in terms of a serialisation? How do you handle unexpected content or missing content?

----
Should the 'type' field be expanded? What is the proper type for reviewing a movie seen in a cinema? Of the existing values, 'event' would seem to apply best, but it's not completely intuitively obvious, especially since 'product' could also apply.

Compare to reviewing a movie on DVD. One might be tempted to use the 'product' type. But what is really the product here -- the film being viewed, or its packaging? Again, 'product' doesn't seem intuitively obvious, as it would seem to apply to more utilitarian objects, rather than to ephemera like movies or music.

I suggest the following:

'event' should specifically be defined to mean an occurence in a particular time/location frame, experienced in person (live concerts, trade shows, sporting events, etc).

'product' should similarly be narrowed down in some fashion. In some cases, it might be difficult to decide whether one is reviewing a 'business', or their 'product'. And where does the concept of a 'service' fall? These ideas are sometimes closely related, and other times quite separate.

'media' should be added to cover reviews of artistic creations (music, films, literature, art) which may appear in non-unique formats (viewed in person, DVD, CD, TV, radio, magazines, art galleries, etc).


[[User:Dougal Campbell|Dougal Campbell]] 10:28, 26 Jul 2005 (PDT)

'''Dougal, this was already answered in the [[hreview-faq|FAQ]] a while ago as the first question! -[http://tantek.com/log/ Tantek]'''


----

The rating field, at the moment, is mandated to be an integer. Is there a particular reason for this (which seems like an unnecessary restriction)?

- AlfEaton.

'''First, the rating field is based on current actual review/rating data published on the web, which for the most part is integer.  There have been several requests for allowing one decimal digit of precision, since that broader definition would include many more (90%+ at least) reviews on the web, it is being considered for hReview 0.3.'''

'''Second, "unnecessary restriction" is looking at it from the complete wrong perspective. "unnecessary axis of freedom or extensibility" is the thing to avoid, because that is the antithesis of simplicity, and causes more work for everyone involved, testing, developing etc.  Premature generality is a common mistake made by engineers, and microformats explicitly seeks to avoid it.'''

'''- [http://tantek.com/log/ Tantek]'''

----

Consider for hReview 0.3: 

* make it explicit that a review of an event (see item types list) SHOULD use [[hcalendar|hCalendar]] to represent the item, just as a review of a company or person SHOULD use [[hcard|hCard]]. - [http://tantek.com/log/ Tantek]
* now that [[hcard|hCard]], [[hcard-parsing]], and [[hcard-profile]] are solid, change SHOULD to MUST for
** item description of a business MUST use an hCard
** reviewer information MUST be represented by an hCard

2005-10-06 Tantek Çelik and Ian McAllister discussed the above changes for hReview 0.3 and agreed that they should be in hReview 0.3.

* add one decimal digit of precision to ratings per discussion above.  Matt Mullenweg has also asked for this based on his experience at CNET and their reviews.

2005-11-29 Tantek Çelik and John Panzer discussed the above changes for hReview 0.3 and agreed that they should be in hReview 0.3.

2005-12-07 As pointed out by David Janes, there needs to be a more explicit way to markup the best/worst of a rating, and an example provided that does so, e.g.:

I think to convey the scale of an overall rating, we may need to borrow [http://microformats.org/wiki/hcard#Value_excerpting the "value" construct from hCard] (as it is used in "tel" properties for example). E.g.

<pre><nowiki>
<p class="rating">
On Fred's <span class="best">4</a> ICBM scale, I give this a <span 
class="value">2</a>.
</p>
</nowiki></pre>

- Tantek Çelik

2005-12-07 I've made the following assumption from 0.2, which works pretty good and you may consider making more formal: "best"/"worst"/"rating" apply to the entire hReview object, unless they appear inside a rel-tag object, in which case they only appy to that. Since hReview seems designed to apply to one "item" at a time, this seems sufficient. -- [[User:DavidJanes|David Janes]]

----

Some comments:

* ''There is no mention of any sort of credibility attached to a review in this specification. Most review sites today indicate how many users found the review helpful, etc, which I consider critical information to attach any credibility to the review. This can also be considered a review of a review, and allow for embedded hReviews.''
** Response: The URL from which the hReview is obtained can be used to lookup a credibility of that URL/domain/blog as a source in general.  It's not clear this should be in the review itself.
* ''I don't understand why the 'item type' field is restricted. What if I want to write reviews for job desriptions? Is my only option the URL type? ''
** Please see the [[hreview-faq|hReview FAQ]] about using tags for more specific items.
* ''Shouldn't we have the 'origin' field as mandatory? If not specified, this may lead to duplicate reviews on a site that crawls multiple sites which in turn crawl eachother.''
** The permalink field solves this problem.
*''-Sapna''
** - Tantek Çelik

----

2005-10-20 David Sifry suggested adding a license feature so that companies could explicitly state the license/copyright of the review (e.g. CC license, or All Rights Reserved etc.).

* The question is, is such a license feature something that all microformats need? And thus perhaps we need to figure out how to extend / update [[rel-license]] to apply to any microformatted chunk of data - Tantek Çelik

----

2005-11-30 RyanKing wonders whether requiring reviewer might be too much in some cases. For example, he wrote [http://theryanking.com/blog/archives/2005/11/17/spoon-the-warfield/ a review], on his own blog, but had to include his name in the post text.

* Tantek reminds Ryan about the hResume discussion where we figured out how multiple hCards on a page could share a common "fn" at the top of the page by reference.  Note: Tantek needs to add "write hResume draft" to his section on the [[to-do]] page.

----

2006-01-26

[http://microformats.org/discuss/mail/microformats-discuss/2005-July/000409.html Eran Globen noted in July of 2005] that it may be good to allow for rated tags to be specified with the tag inside the rating.  Combined with the "value" technique in hCard, this is quite doable.  The example that Eran gave, modified just a bit to use the "value" technique:

<pre><nowiki>
<ul>
  <li>
    <a href="http://en.wikipedia.org/wiki/Food" rel="tag">Food: 
     <span class="rating">18</span>/<span class="best">30</span></a>;
  </li>
  ...
</ul>
</nowiki></pre>

Changes to:

<pre><nowiki>
<ul>
  <li class="rating">
    <a href="http://en.wikipedia.org/wiki/Food" rel="tag">Food</a>:
    <span class="value">18</span>/<span class="best">30</span>;
  </li>
  ...
</ul>
</nowiki></pre>

------

2006-01-27

In some contexts, it'd be somewhat useful for the author information to be able to be "inherited" from the review's context, e.g. perhaps a series of many, perhaps dozens, of reviews all by the same reviewier, provided together on a list, perhaps on a blog.  This might be good for 0.3.

We thought of something similar for [[hresume|hResume]], to enable [[hcard|hCards]] for each job to share a common "fn" value, derived from the individual's name at the top of the resume.

We could also use such a "sharing of data" concept for [[hatom|hAtom]], so that the authors for entries are by default the authors for the blog, unless otherwise specified. - Tantek

* We have now done this for hReview 0.3 via the object [[include-pattern]]  Thanks.  Tantek

------

2006-02-07

In the extended Crepes on Cole example, the reviewer name is anonymous, but is not so indicated by adding fn to the list of classes on the enclosing element. Is this correct? I don't think so. - Rohit

* This has been corrected in hReview 0.3.  Thanks.  Tantek
------

2006-02-23

What's the rationale for making dtreviewed required? I think (as pointed out earlier) there are vaild cases where it's omitted from the page markup (either because it's inferred from the HTTP Last-Modified date, or because a review date isn't relevant or available).

* This was an unintentional omission from hReview 0.3, and has been corrected. Please take another look. Thanks. Tantek

----

2006-03-06

At [http://postgenomic.com/about_reviews.php postgenomic.com] (an aggregator/analysis engine for life science weblogs), an attempt to get people to add markup to their posts to identify reviews of papers currently recommends using either a) rev="review" on the outgoing link, or b) to enclose the review in &lt;div class="hreview"&gt; and add class="url" to the outgoing link. 

Because of the way the reviews can be structured (generally just free text, without extra citation metadata), the separation between 'item' and 'description' doesn't really fit. Could it be acceptable to just use class="url" on the outgoing link to imply that as the subject of the review, without using either 'item' or 'description'? -- AlfEaton

----

2006-09-20
What about marking up prices, using the [[currency]] proposal? - Andy Mabbett

------
Mahesh - 2007-07-26

What are the optional and what are the required fields


------
2007-11-30

Created three 3D Markup Maps for hReview microformats examples used in the Wiki to better understand the relationship of HTML elements and apply CSS rules: 

# [http://www.christopherschmitt.com/2007/11/29/hreview-microformat-3d-markup-map-for-products/ hReview Microformat 3D Markup Map for Products]
# [http://www.christopherschmitt.com/2007/11/29/hreview-microformat-3d-markup-map-for-movies/ hReview Microformat 3D Markup Map for Movies]
# [http://www.christopherschmitt.com/2007/11/29/hreview-microformat-3d-markup-map-for-restaurants/ hReview Microformat 3D Markup Map for Restaurants]

-- Christopher Schmitt

----
2008-01-20

Item <code>type</code> considered harmful.

Unlike the other parts of the [[hreview]] spec, the <code>type</code> item requires that its contents be particular English language words that are meant for display to the reader of the page (as per the microformats [[principles]] of presentable and parsable). Clearly, this is inappropriate for any page that is not written in English. Defining synonyms for every specified type in every language is not realistic, either. So, we have a problem.

I suggest that the <code>type</code> item be dropped altogether. In reality it is redundant, as the reader of the page should be able to tell what sort of item is being reviewed from the review text itself, grouping of like reviews is possible through the URL item reference or any embedded tags, and it is not clear what computer processing purpose is being served by the level of granularity in the spec. For example, an hReview search for "product" is probably too coarse, potentially grouping together reviews of movies, books, songs, soft drinks, shoes or other products with the same name.

As this part of the spec would appear to have few (if any?) benefits, and a couple of clear problems (i.e. breaks for non English language, need to display redundant information to reader), it does not sit comfortably within the spirit of simplicity or extensibility that microformats promote, and should be removed from future versions of the spec.

- [[User:Andrew|Andrew]]

* This is another case where titles on spans, with a "data" flag, could be applied:

::<nowiki><span class="type" title="data: book">livre</span></nowiki>

:[[User:AndyMabbett|Andy Mabbett]] 08:43, 20 Jan 2008 (PST)

I don't think this is a good application. In this case, the value used by the microformat parser is different to the value that a human viewer of the page sees. Doesn't this violate one of the principles of microformats? Also, what if search engines are optimised for certain types of data - wouldn't this create an incentive for authors to misreport the type?

Can anyone come up with a compelling reason to even have the <code>type</code> item? There seem to be plenty of reasons to drop it.

- [[User:Andrew|Andrew]]

==Related pages==
{{hreview-related-pages}}