hreview-feedback

2007-06-14T00:46:16Z

ZabPe5:

= hReview Feedback =

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

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

Microformats Wiki - User contributions [en]

hreview-feedback