hreview-issues
hReview issues
These are externally raised issues about hReview with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec. Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — Tantek
See related hcalendar-issues and hcard-issues.
Template
Please use this format (copy and paste this to the end of the list to add your issues):
- YYYY-MM-DD raised by YOURNAME.
- Issue 1: Here is the first issue I have.
- Issue 2: Here is the second issue I have.
rel="self"
2005-01-04 by David Janes:
Atom defines rel="self" here
- The value "self" signifies that the IRI in the value of the href attribute identifies a resource equivalent to the containing element.
HTML rel="boomark" here
- Refers to a bookmark. A bookmark is a link to a key entry point within an extended document. The title attribute may be used, for example, to label the bookmark. Note that several bookmarks may be defined in each document.
Since we're using "bookmark" to mean the entry point to the hReview, isn't the "self" redundant or overly subtle?
default lower bound
- YYYY-MM-DD????? raised by Scott Reynen
- Why is the default lower bound 1 when the real world examples almost all have a lower bound of 0?
- REJECTED INVALID ASSUMPTION. Most real-world examples have a lower bound of 1, not 0.
- Why is the default lower bound 1 when the real world examples almost all have a lower bound of 0?
default range
- 2006-02-23 raised by Andy Mabbett
- Not all marks give ratings "out of five". The value should be a percentage. Zero should be allowed.
- REJECTED IGNORES RESEARCH. Most real-world examples have a range of 1.0-5.0 not a percentage. You may set the "best" bound to 100 explicitly, and the "worst" bound to 0 explicitly per the spec if necessary.
- "most" != "all"; indeed, the page you cite has examples of "1-10" and "0-100%". I never claimed that many examples use percentages, but I'm sure a mathematician would explain that values in the range "1-5" may be expressed as percentages.
- REJECTED RTFM. Most examples are what the defaults are based on. Please re-read both the spec and the previous resolution, 1-10 is allowed (you have to explicitly set "best" to 10), and so is 0-100 (you have to explicitly set "worst" to 0 and "best" to 100).
- Not all marks give ratings "out of five". The value should be a percentage. Zero should be allowed.
Specification Clarifications
- 2006-02-01 raised by Tantek.
- The spec needs to clarify that there is only one "item" per "hreview".
- ACCEPTED. Resolved in hReview 0.3.
- The spec needs to clarify that there is only one "item" per "hreview".
Multilinguism
- 2006-03-22 raised by Fil
- the reviewer spec can't say For anonymous reviews, use "anonymous" (without quotes) for the full name of the reviewer. as this word ("anonymous") is going to be apparent on the page, and is not multilingual (and even in English someone might want to use another word, like "an anonymous coward")
Price
- 2006-04-04 raised by Evan.
- It doesn't seem possible to give an approximate, average, or absolute price of the product or service in question. Examples: for a piece of software, the suggested retail price. For a restaurant, average price of an entree, or a price range. Prices should almost definitely have a currency marker and an amount. Suggestion: <span class="price"><abbr class="currency" title="Canadian dollars">$</abbr><span class="amount">10.99</span></span>. For a range, <span class="pricerange"><span class="price"> ... </span> to <span class="price"> ... </span></span>.