hreview-feedback-fr

Réactions hReview

Ce document est ici pour garder une trace des réaction à propos de hReview, l'un des nombreux Microformats.

gabarit

SVP, utilisez ce format (copiez et collez ceci à la fin de la liste pour ajouter vos problématiques ; remplacez ~~~ par un lien externe si vous préférez) pour rendre compte des problématiques ou réactions :

<div class="vevent">
* {{OpenIssue-fr}} <span class="summary vcard"><span class="dtstart">AAAA-MM-JJ</span> soulevée par <span class="fn">~~~</span></span>
<div class="description">
*# Voici la première problématique/réaction que je rencontre.
*# Voici la seconde problématique/réaction que je rencontre.
</div>
</div>

Réactions

Questions Générales

Voir la page FAQ hReview.

Commentaires Généraux

30 avril 2005 :

Joli travail :-) Quelques 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?)

Voir parseur hcard qui répond à ces questions. -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?):

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

Doesn't RelTag significantly constrain what appears enclosed within the A element? i.e., (from Technorati's tag description:)

 <a href="http://technorati.com/tag/[tagname]" rel="tag">[tagname]</a>

-Jay Fienberg

</nowiki>

Voir la spec. rel-tag. Le dernier segment de l'URL est le nom du tag, pas les contenus de l'élément. La page d'aide Technorati ne fait que fournir un balisage suggéré. Voir la spec pour des détails normatifs. -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. | this page). I've blogged a possible markup for that | here

- JamesStewart

Thus the "description" is optional, and you can provide a URL permalink back to the original. -Tantek

---

J'ai ajouté quelques items à la page FAQ (hReview FAQ) SVP jetez-y un oeil et sentez-vous libre de clarifier et modifier.

-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 experiment to support hCalendar). To that end I was surprised at the specification. I've explained things more fully here

-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 &lt:dl class="hreview">, or each individual item by wrapping the <dt>/<dd> pairs in a <div> (which is the approach I took)?

Follow-up: scratch that last comment: Since I'm using XHTML 1.1,

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: Markup Languages. I will post this URI to del.icio.us tagged as hreview as well.

Douglas Clifton

---

Ne devrait-il pas être mentionné quelque part dans quelle langue la critique est écrite ? Est-ce simplement un glissement de l'esprit, ou une attitude très centrée US ? Je ne pense pas qu'ajouter une info de "language" serait hors sujet, car cela aiderait à éliminer les langues non désirées des requêtes de recherche ; en outre Ce n’est pas parce que mon blog est en anglais, 꼭 英語만 쓰는 것이 아니다… Et si je voulais poster la même critique dans différentes langues ou citer quelque chose dans une autre langue..?

dda

Merci pour ton input. Ceci a été rendu explicite et résolu par hReview 0.2, spécifiquement : hReviews et langue -Tantek

---

Un fragment échantillon de "Critique_Restaurant_Multidimensionnnelle" n'est pas un format valide XML.

original :

 This 
 <a href="http://en.wikipedia.org/wiki/cafe" rel="tag">cafe</a> 

correction :

 This 
 <a href="http://en.wikipedia.org/wiki/cafe" rel="tag">cafe</a> 

YAMAMOTO Yohei

Merci pour le feedback Yamamoto, ceci était mon erreur de typo et l'exemple a été corrigé. - Tantek

---

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).

Dougal Campbell 10:28, 26 Jul 2005 (PDT)

Dougal, ceci a déjà été répondu dans les FAQ il y a un moment comme la première question ! -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.

- Tantek

---

Consider for hReview 0.3:

• make it explicit that a review of an event (see item types list) SHOULD use hCalendar to represent the item, just as a review of a company or person SHOULD use hCard. - Tantek
• now that 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 the "value" construct from hCard (as it is used in "tel" properties for example). E.g.

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

- 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. -- 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 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 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

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:

<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>

Changes to:

<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>

---

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, to enable 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, 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 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 <div class="hreview"> 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

Que penser de baliser les prix, en utilisant la proposition currency ? - 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:

1. hReview Microformat 3D Markup Map for Products
2. hReview Microformat 3D Markup Map for Movies
3. hReview Microformat 3D Markup Map for Restaurants

-- Christopher Schmitt

---

2008-01-20

Item type considered harmful.

Unlike the other parts of the hReview spec, the type 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 principes 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 type 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.

- Andrew

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

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

Andy Mabbett 08:43, 20 Jan 2008 (PST)

Pages en rapport

• hReview
• hReview-aggregate - microformat pour spécifier l'information résumée provenant d'une collection d'avis sur un produit ou service
• hReview creator (feedback) - créer votre propre hReview.
• hReview publication - apprendre comment ajouter du balisage hReview à votre information de contact existante
• hReview brainstorming - idées pour améliorer hReview
• antisèche hReview - propriétés hReview
• hReview exemples dans la jungle - une liste en cours de sites web qui utilisent hReview.
• hReview FAQ - Si vous avez des questions à propos de hReview, regardez ici, et si vous ne trouvez pas de réponses, ajoutez vos questions !
• hReview feedback - Réactions bienvenues !
• hReview implementations - les sites web ou outils qui soit génèrent ou parsent les hReviews.
• hReview problématiques - Ajoutez svp toutes les problématiques avec la spécification sur la page problématiques
• hReview parsage - Détails normatifs sur la manière de parser les hReviews.
• hReview profil - Le profil XMDP pour hReview
• hReview tests - une page wiki avec de véritables hReviews embarquées pour essayer le parsage.
• hReview soutien - encourager les autres à utiliser hReview.
• exemples de critiques
  • hReview exemples
• formats de critiques
• brainstorming critiques - l'endroit où nous avons brainstormé sur les formats de critiques avant d'en venir à hReview.
• currency - proposition pour baliser les montants en argent (par ex. les prix d'items critiqués)
• Aggregate reviews - examples - formats - brainstorming