I believe your hReview Plugin does have a small bug. In all the examples I can find (see below), the fn of the reviewed item should be inside the item level (a bit like fn should be inside a vcard, not at the same level):

So:

<p class="item"span class="fn">Something</span></p>

is fine, whereas:

<p class="item fn">Something</p>
is not. Combining this with the url data is most useful, giving:

<p class="item"><a class="fn url" href="http://www.aes.id.au/?page_id=28" rel="nofollow">hReview WordPress Plugin</a></p>

Without this tweak, the Operator plugin does not successfully detect the plugin (except in debug mode).

The examples where fn is inside item:

http://microformats.org/wiki/hreview#Restaurant_reviews
http://www.golfdigest.com/courses/places/2483
http://www.novedge.com/review/1978/

Actually, the http://microformats.org/wiki/hreview-profile sums it up nicely. fn is a sub-property of item.

I did ponder what to do about the review type field. Personally, I find it a bit annoying, and I’ve considered removing it from the plugin. However, I think I followed the approach used by the hReview Creator page (http://microformats.org/code/hreview/creator) which used the style attribute to prevent it displaying. However, since it’s invisible, I could position it before the summary so that people like yourself could change the CSS and have it display as they wish.

The other optional things I generally left out to keep the user interface and code simpler. For example, on my own site, I have an hCard on every page anyway, and so I didn’t need to add support for another hCard within each review. I suspect most blogs will also take this approach, unless they have multiple authors contributing to the blog.

FYI, the Tails Export plugin for Firefox (https://addons.mozilla.org/en-US/firefox/addon/2240) supports hReview.