hreview-feedback-fr - Revision history

Brian: Reverted edits by TrsitCnada (Talk) to last version by ChristopheDucamp

2008-12-20T22:40:10Z

Reverted edits by TrsitCnada (Talk) to last version by ChristopheDucamp

← Older revision		Revision as of 22:40, 20 December 2008
Line 1:		Line 1:
	~~acgetgetcaou~~		<h1> Réactions hReview </h1>
	<h1> ~~RÃ©actions~~ hReview </h1>
	{{TOC-right}}		{{TOC-right}}
	Ce document est ici pour garder une trace des ~~rÃ©action Ã~~ propos de [[hreview-fr\|hReview]], l'un des nombreux Microformats.		Ce document est ici pour garder une trace des réaction à propos de [[hreview-fr\|hReview]], l'un des nombreux Microformats.

	== gabarit ==		== gabarit ==
	{{issues-format-fr}}		{{issues-format-fr}}

	== ~~RÃ©actions~~ ==		== Réactions ==
	=== Questions ~~GÃ©nÃ©rales~~ ===		=== Questions Générales ===
	Voir la page [[hreview-faq-fr\|FAQ hReview]].		Voir la page [[hreview-faq-fr\|FAQ hReview]].

	=== Commentaires ~~GÃ©nÃ©raux~~ ===		=== Commentaires Généraux ===

	30 avril 2005 :		30 avril 2005 :
Line 29:		Line 28:
	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?)		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 [[hcard-parsing-fr\|parseur hcard]] qui ~~rÃ©pond Ã~~ ces questions. -[http://tantek.com/log/ Tantek]'''		'''Voir [[hcard-parsing-fr\|parseur hcard]] qui répond à ces questions. -[http://tantek.com/log/ Tantek]'''


Line 46:		Line 45:
	</pre></nowiki>		</pre></nowiki>

	'''Voir la spec. [[rel-tag-fr\|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. -[http://tantek.com/log/ Tantek]'''		'''Voir la spec. [[rel-tag-fr\|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. -[http://tantek.com/log/ Tantek]'''


Line 61:		Line 60:
	----		----

	J'ai ~~ajoutÃ©~~ quelques items Ã la page FAQ ([[hreview-faq-fr\|hReview FAQ]]) SVP jetez-y un oeil et sentez-vous libre de clarifier et modifier.		J'ai ajouté quelques items à la page FAQ ([[hreview-faq-fr\|hReview FAQ]]) SVP jetez-y un oeil et sentez-vous libre de clarifier et modifier.

	-RyanKing		-RyanKing
Line 83:		Line 82:
	----		----

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

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

	'''Merci pour ton input. Ceci a ~~Ã©tÃ©~~ rendu explicite et ~~rÃ©solu~~ par hReview 0.2, ~~spÃ©cifiquement~~ : [http://microformats.org/wiki/hreview#Langue hReviews et langue] -[http://tantek.com/log/ Tantek]'''		'''Merci pour ton input. Ceci a été rendu explicite et résolu par hReview 0.2, spécifiquement : [http://microformats.org/wiki/hreview#Langue hReviews et langue] -[http://tantek.com/log/ Tantek]'''

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

	original :		original :
Line 102:		Line 101:
	[http://yohei-y.blogspot.com YAMAMOTO Yohei]		[http://yohei-y.blogspot.com YAMAMOTO Yohei]

	'''Merci pour le feedback Yamamoto, ceci ~~Ã©tait~~ mon erreur de typo et l'exemple a ~~Ã©tÃ© corrigÃ©~~. - [http://tantek.com/ Tantek]'''		'''Merci pour le feedback Yamamoto, ceci était mon erreur de typo et l'exemple a été corrigé. - [http://tantek.com/ Tantek]'''

	----		----
Line 120:		Line 119:
	[[User:Dougal Campbell\|Dougal Campbell]] 10:28, 26 Jul 2005 (PDT)		[[User:Dougal Campbell\|Dougal Campbell]] 10:28, 26 Jul 2005 (PDT)

	'''Dougal, ceci a ~~dÃ©jÃ Ã©tÃ© rÃ©pondu~~ dans les [[hreview-faq-fr\|FAQ]] il y a un moment comme la ~~premiÃ¨re~~ question ! -[http://tantek.com/log/ Tantek]'''		'''Dougal, ceci a déjà été répondu dans les [[hreview-faq-fr\|FAQ]] il y a un moment comme la première question ! -[http://tantek.com/log/ Tantek]'''


Line 144:		Line 143:
	** reviewer information MUST be represented by 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.		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.		* 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-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.:		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.:
Line 161:		Line 160:
	</nowiki></pre>		</nowiki></pre>

	- Tantek ~~Ãelik~~		- 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]]		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]]
Line 176:		Line 175:
	** The permalink field solves this problem.		** The permalink field solves this problem.
	*''-Sapna''		*''-Sapna''
	** - Tantek ~~Ãelik~~		** - Tantek Çelik

	----		----
Line 182:		Line 181:
	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.).		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~~		* 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

	----		----

TrsitCnada: tamoncor

2008-12-20T06:52:35Z

tamoncor

← Older revision		Revision as of 06:52, 20 December 2008
Line 1:		Line 1:
	<h1> ~~Réactions~~ hReview </h1>		acgetgetcaou
			<h1> RÃ©actions hReview </h1>
	{{TOC-right}}		{{TOC-right}}
	Ce document est ici pour garder une trace des ~~réaction à~~ propos de [[hreview-fr\|hReview]], l'un des nombreux Microformats.		Ce document est ici pour garder une trace des rÃ©action Ã propos de [[hreview-fr\|hReview]], l'un des nombreux Microformats.

	== gabarit ==		== gabarit ==
	{{issues-format-fr}}		{{issues-format-fr}}

	== ~~Réactions~~ ==		== RÃ©actions ==
	=== Questions ~~Générales~~ ===		=== Questions GÃ©nÃ©rales ===
	Voir la page [[hreview-faq-fr\|FAQ hReview]].		Voir la page [[hreview-faq-fr\|FAQ hReview]].

	=== Commentaires ~~Généraux~~ ===		=== Commentaires GÃ©nÃ©raux ===

	30 avril 2005 :		30 avril 2005 :
Line 28:		Line 29:
	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?)		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 [[hcard-parsing-fr\|parseur hcard]] qui ~~répond à~~ ces questions. -[http://tantek.com/log/ Tantek]'''		'''Voir [[hcard-parsing-fr\|parseur hcard]] qui rÃ©pond Ã ces questions. -[http://tantek.com/log/ Tantek]'''


Line 45:		Line 46:
	</pre></nowiki>		</pre></nowiki>

	'''Voir la spec. [[rel-tag-fr\|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. -[http://tantek.com/log/ Tantek]'''		'''Voir la spec. [[rel-tag-fr\|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. -[http://tantek.com/log/ Tantek]'''


Line 60:		Line 61:
	----		----

	J'ai ~~ajouté~~ quelques items à la page FAQ ([[hreview-faq-fr\|hReview FAQ]]) SVP jetez-y un oeil et sentez-vous libre de clarifier et modifier.		J'ai ajoutÃ© quelques items Ã la page FAQ ([[hreview-faq-fr\|hReview FAQ]]) SVP jetez-y un oeil et sentez-vous libre de clarifier et modifier.

	-RyanKing		-RyanKing
Line 82:		Line 83:
	----		----

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

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

	'''Merci pour ton input. Ceci a ~~été~~ rendu explicite et ~~résolu~~ par hReview 0.2, ~~spécifiquement~~ : [http://microformats.org/wiki/hreview#Langue hReviews et langue] -[http://tantek.com/log/ Tantek]'''		'''Merci pour ton input. Ceci a Ã©tÃ© rendu explicite et rÃ©solu par hReview 0.2, spÃ©cifiquement : [http://microformats.org/wiki/hreview#Langue hReviews et langue] -[http://tantek.com/log/ Tantek]'''

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

	original :		original :
Line 101:		Line 102:
	[http://yohei-y.blogspot.com YAMAMOTO Yohei]		[http://yohei-y.blogspot.com YAMAMOTO Yohei]

	'''Merci pour le feedback Yamamoto, ceci ~~était~~ mon erreur de typo et l'exemple a ~~été corrigé~~. - [http://tantek.com/ Tantek]'''		'''Merci pour le feedback Yamamoto, ceci Ã©tait mon erreur de typo et l'exemple a Ã©tÃ© corrigÃ©. - [http://tantek.com/ Tantek]'''

	----		----
Line 119:		Line 120:
	[[User:Dougal Campbell\|Dougal Campbell]] 10:28, 26 Jul 2005 (PDT)		[[User:Dougal Campbell\|Dougal Campbell]] 10:28, 26 Jul 2005 (PDT)

	'''Dougal, ceci a ~~déjà été répondu~~ dans les [[hreview-faq-fr\|FAQ]] il y a un moment comme la ~~première~~ question ! -[http://tantek.com/log/ Tantek]'''		'''Dougal, ceci a dÃ©jÃ Ã©tÃ© rÃ©pondu dans les [[hreview-faq-fr\|FAQ]] il y a un moment comme la premiÃ¨re question ! -[http://tantek.com/log/ Tantek]'''


Line 143:		Line 144:
	** reviewer information MUST be represented by 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.		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.		* 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-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.:		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.:
Line 160:		Line 161:
	</nowiki></pre>		</nowiki></pre>

	- Tantek ~~Çelik~~		- 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]]		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]]
Line 175:		Line 176:
	** The permalink field solves this problem.		** The permalink field solves this problem.
	*''-Sapna''		*''-Sapna''
	** - Tantek ~~Çelik~~		** - Tantek Ãelik

	----		----
Line 181:		Line 182:
	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.).		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~~		* 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

	----		----

ChristopheDucamp at 07:28, 27 January 2008

2008-01-27T07:28:16Z

← Older revision		Revision as of 07:28, 27 January 2008
Line 1:		Line 1:
	= Réactions hReview =		<h1> Réactions hReview </h1>
			{{TOC-right}}
	Ce document est ici pour garder une trace des réaction à propos de [[hreview-fr\|hReview]], l'un des nombreux Microformats.		Ce document est ici pour garder une trace des réaction à propos de [[hreview-fr\|hReview]], l'un des nombreux Microformats.

ChristopheDucamp: [fr:sync'd with english version-to be translated]

2008-01-27T07:27:40Z

[fr:sync'd with english version-to be translated]

@@ Line 1: / Line 1: @@
 = Réactions hReview =
-Ce document est ici pour garder une trace des réaction à propos de [[hreview-fr|hReview]], l'un des nombreux Microformats
+== gabarit ==
 == Réactions ==
@@ Line 254: / Line 256: @@
 Que penser de baliser les prix, en utilisant la proposition [[currency-fr|currency]] ? - Andy Mabbett
 ==Pages en rapport ==
 {{hreview-related-pages-fr}}

ChristopheDucamp: reintegration currency -> will be reintegrated in template hreview-related-pages... sorry Andy

2006-12-26T22:58:10Z

reintegration currency -> will be reintegrated in template hreview-related-pages... sorry Andy

← Older revision		Revision as of 22:58, 26 December 2006
Line 248:		Line 248:

	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		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-fr\|currency]] ? - Andy Mabbett


			==Pages en rapport ==
			{{hreview-related-pages-fr}}

ChristopheDucamp: [fr: this page will be translated later - localization of links]

2006-07-22T06:58:05Z

[fr: this page will be translated later - localization of links]

New page

= Réactions hReview =

Ce document est ici pour garder une trace des réaction à propos de [[hreview-fr|hReview]], l'un des nombreux Microformats

== Réactions ==
=== Questions Générales ===
Voir la page [[hreview-faq-fr|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 [[hcard-parsing-fr|parseur hcard]] qui répond à ces questions. -[http://tantek.com/log/ Tantek]'''

Also ([[rel-tag-fr|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>

'''Voir la spec. [[rel-tag-fr|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. -[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]'''

----

J'ai ajouté quelques items à la page FAQ ([[hreview-faq-fr|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 [http://adriancuthbert.blogspot.com/2005/04/smartlink.html experiment] to support [[hcalendar-fr|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"></code>, or each individual item by wrapping the <code><dt></code>/<code><dd></code> pairs in a <div> (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]

----

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

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

'''Merci pour ton input. Ceci a été rendu explicite et résolu par hReview 0.2, spécifiquement : [http://microformats.org/wiki/hreview#Langue hReviews et langue] -[http://tantek.com/log/ Tantek]'''

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

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

correction :
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]

'''Merci pour le feedback Yamamoto, ceci était mon erreur de typo et l'exemple a été corrigé. - [http://tantek.com/ 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).

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

'''Dougal, ceci a déjà été répondu dans les [[hreview-faq-fr|FAQ]] il y a un moment comme la première 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-fr|hCalendar]] to represent the item, just as a review of a company or person SHOULD use [[hcard-fr|hCard]]. - [http://tantek.com/log/ Tantek]
* now that [[hcard-fr|hCard]], [[hcard-parsing-fr|hcard-parsing]], and [[hcard-profile-fr|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-fr|hResume]], to enable [[hcard-fr|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-fr|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-fr|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 <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