Microformats Wiki - User contributions [en]

cheat-sheet

2006-11-21T20:10:58Z

Dougal Campbell:

implementations

2006-05-11T16:05:10Z

Dougal Campbell: /* WordPress */

=Microformats Implementors And Implementations=

This page lists the companies, applications, services, and sample code which support microformats, along with the developers responsible for doing so that have chosen to be listed. This is only a partial list. If you know other companies implementing microformats, please add them and list their services and what specific microformats they support.

__TOC__

== Formats ==

Most microformat specifications have an "implementations" section, e.g.:
* [http://microformats.org/wiki/hcalendar#Implementations hCalendar], [http://microformats.org/wiki/hcard#Implementations hCard], [http://microformats.org/wiki/rel-tag#Implementations rel-tag], [http://microformats.org/wiki/vote-links#Implementations vote-links], [http://microformats.org/wiki/xoxo#Implementations XOXO] etc.

In addition, some microformat specifications have separate implementation pages:
* [[xfn-implementations]]

== Companies / Organizations / Authors / Services ==

=== Avon ===
* [http://avon.com/ Avon] - publishes all 40,000+ Avon representatives' contact info with the [[hcard|hCard]] microformat.

=== BlogMatrix ===
* [http://www.blogmatrix.com BlogMatrix] - user information marked as [[hcard|hCard]], tag directories in [[xfolk]]/[[rel-tag]], enclosures are marked as [[rel-enclosure]].
* developers
** [http://blogmatrix.blogmatrix.com David Janes]

=== Drupal ===
* [http://hybernaut.com/upcoming-module Drupal Upcoming.org syndication module] emits [[hcalendar|hCalendar]]
* developers:
** [http://hybernaut.com/ Brian Del Vecchio]

=== EVDB ===
* [http://evdb.com EVDB] supports [[hcalendar|hCalendar]] for over 100,000 event listings and [[hcard|hCard]] for venues.

=== Flock ===
* [http://flock.com Flock] browser supports the [[rel-tag]] microformat.
* [http://flock.com/about Flock About] page supports [[hcard|hCard]] microformat.

=== Google ===
* [http://google.com/ Google] - supports [[rel-nofollow]]
* [http://www.google.com/webhp?as_rights=(cc_publicdomain%7Ccc_attribute%7Ccc_sharealike%7Ccc_noncommercial%7Ccc_nonderived) Google Creative Commons Search] - supports [[rel-license]]

=== Ice Rocket ===
* [http://icerocket.com] - [http://blogs.icerocket.com/tag/ supports] [[rel-tag]]

=== Iowa Military Veterans Band ===
* [http://www.iowamilitaryveteransband.com/members/ Iowa Military Veterans Band]

=== Karova ===
* [http://www.karova.com/ Karova] [http://www.karova.com/article.aspx?id=4 supports microformats]

=== Konqueror ===
* [http://www.konqueror.org/ Konqueror] - [http://flickr.com/photos/factoryjoe/68755089/ supports] [[hcard|hCard]]

=== Laughing Squid ===
* The [http://laughingsquid.com/squidlist/calendar/ Laughing Squid Calendar] events listings support [[hcalendar|hCalendar]].

=== LiveJournal ===
* [http://www.livejournal.com LiveJournal] - LiveJournal supports tagging posts with [[rel-tag]].

=== LJFind ===
* [http://www.ljfind.com LJ-Find] - LJFind supports tagging posts with [[rel-tag]].

=== ODEO ===
* [http://odeo.com/ ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html noted] that they support microformats: [[rel-tag]], [[rel-enclosure]], [http://gmpg.org/xfn XFN].

=== Sunnyvale House Concerts ===
* [http://concerts.shrub.ca/shows Sunnyvale House Concerts] supports [[hcard|hCard]] and [[hcalendar|hCalendar]].

=== Technorati ===
* [http://technorati.com/ Technorati] supports and handles both [[vote-links]] and [[rel-nofollow]] for indicating whether a link should have any/positive/negative weighting towards the destination.
* [http://technorati.com/tag/ Technorati Tags index] - an index of blog posts tagged with the [[rel-tag]] open tagging standard.
* [http://tantek.com/microformats/hcard-creator.html hCard creator] - contributed to [http://microformats.org/code/hcard/creator microformats.org as open source]. This is a very simple, yet illustrative, open source user interface / form / script which creates an hCard in real-time as you type in a set of contact information.
* [http://theryanking.com/microformats/hcalendar-creator.html hCalendar creator] - contributed to [http://microformats.org/code/hcalendar/creator microformats.org as open source]. Similar, but for hCalendar.
* [http://theryanking.com/microformats/hreview-creator.html hReview creator] - contributed to [http://microformats.org/code/hreview/creator microformats.org as open source]. Similar, but for hReview.
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards.
* [http://technorati.com/ Technorati] publishes its own contact information as [[hcard|hCard]]s: [http://technorati.com/about/ About page] lists their Media Contact, and their [http://technorati.com/press/ Press page] also lists their Press Contact, both as inline hCards.
* developers:
** [http://epeus.blogspot.com/ Kevin Marks]
** [http://theryanking.com Ryan King]
** [http://tantek.com/log/ Tantek Çelik]

=== Upcoming.org ===
* [http://upcoming.org Upcoming.org] - hCalendar support in events listings and individual events.

=== University of Bath ===
* [http://www.bath.ac.uk/ University of Bath] [http://www.bath.ac.uk/contact/ Person Finder] supports [[hcard|hCard]]

=== Web Essentials ===
* [http://we05.com/ Web Essentials] - supports [[hcard|hCard]] and [[hcalendar|hCalendar]], e.g. in their [http://we05.com/presenters.cfm list of presenters] and [http://we05.com/program.cfm program schedule].

=== WordPress ===
* [http://wordpress.org WordPress] supports [http://gmpg.org/xfn/ XFN] blogrolls through a very nice built-in user interface. (cf. [[xfn-implementations]])

=== Yahoo ===
* [http://search.yahoo.com/cc/ Yahoo Creative Commons Search] - supports [[rel-license]] specifically to search for Creative Commons licensed content.

=== suda.co.uk ===
[http://suda.co.uk/ brian suda] has created several XSLT files to extract microformats from HTML. From that the [http://suda.co.uk/projects/X2V/ X2V] webservice/favelet emerged. The XSLT and favelet extracts [[hcard|hCard]] and to produces .vcf (vCard) files and [[hcalendar|hCalendar]] to produce .ics (iCal) files. Also in the labs is a universal XMDP validator and a site-wide search spider that recognizes 'no-follow', 'license' and other microformats so they can be used in a more semantic way when displaying search results.

=== other ===
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate hCard information ([http://ietf.org/rfc/rfc2629 RFC2629] is an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])
* [http://thedredge.org Andy Hume] uses the hcard format to mark-up the names and URLs of commentors on his blog.
* [http://web.mit.edu/glasser/www/JSCalendar/ JSCalendar] parses hCalendar and produces a displayable HTML table/CSS-based calendar.

== Tools, Plugins, Projects ==
=== Firefox ===
* [[greasemonkey]] scripts for Firefox
=== Nutch ===
* [http://www.mail-archive.com/nutch-dev@lucene.apache.org/msg01295.html rel-nofollow support added]
* [http://www.mail-archive.com/nutch-commits@lucene.apache.org/msg01014.html rel-tag support checked in]

==general info==
Some notes on initial thoughts around [[implementation-guidelines|Guidelines and Strategies for Implementing Microformats]]

xfn-implementations

2006-05-11T16:00:00Z

Dougal Campbell: /* XFN Implementations */

= XFN Implementations =

In addition to the [http://gmpg.org/xfn/tools XFN Tools] page, here are a few more more recent implementations:

The following implementations have been developed which either generate or parse [http://gmpg.org/xfn XFN relationship links]. If you have an XFN implementation, feel free to add it to the top of this list.

* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of XFN links from within Dreamweaver 8.

* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding XFN and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].

* [http://wiki.www.videntity.org/wiki/Social_Networking_Unlimited Videntity supports XFN].

* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] <code>rel="contact"</code> for a user's contacts on their profile page.

* [http://icite.net/develop/software.html#ll4blojsom LL4blojsom] is the LinkList plugin for the [http://blojsom.sf.net blojsom] blog engine. blojsom, written in Java, is the open source application behind the Tiger Weblog Server that is part of OS X server. The LL4blojsom plugin is used for creating XFN blogrolls.

* [http://tagalag.com Tagalag] Tagalag [http://tagalag.com/tools.html#xfn supports] a partial XFN vocabulary.

* [http://www.zachinglis.com/projects/xfn-rel-creator/ XFN rel Creator] This script replaces any links within the designated tags and replaces them with a visual representation of the links. Default set as abbrevations but with CSS it is easy to replace them for images.

* [http://www.wordpress.org/ WordPress] has XFN support built-in to its Link Manager function, which is used for generating blogrolls. When in the administrative interface, choose the Links top-level menu item, then choose Add Link. The link form lets you choose which XFN properties you wish the link to have. When displaying the links on the site via any of the standard WordPress template tags, it will automatically format it with the appropriate tags in the rel attribute. (based on [http://gmpg.org/xfn/creator XFN Creator])

== See Also ==

* [http://www.centralityjournal.com/archives/xfn_bottomup_social_networks.html XFN:bottom-up Social Networks by Stowe Boyd]
* [[xfn-wants]]

hreview-feedback

2005-07-26T17:28:48Z

Dougal Campbell: /* hReview Feedback */

= hReview Feedback =

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

== Feedback ==
=== General Questions ===
See the [[hReviewFAQ]].

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

Also ([[RelTag]] question), does RelTag 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>
----

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

----

I've added some items to the FAQ page ([[hReviewFAQ]]) 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]]). 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]

----

Shouldn't it be mentioned somewhere in which language the review is written in? Is it just a slip of the mind, or a very US-centric attitude, dude? I don’t think adding language info would be out of scope, as it would help filter out unwanted languages from search queries; plus, Ce n’est pas parce que mon blog est en anglais, 꼭 英語만 쓰는 것이 아니다… What if I wanted to post the same review in different languages, or quote something in another language..?

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

----
A sample xhtml fragment of "Multidimensional Restaurant Review" is not valid XML format.

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

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

Thanks for the feedback Yamamoto, that was my typo and the example has been corrected. - [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)
----

media-metadata-examples

2005-07-26T16:56:21Z

Dougal Campbell: /* Offline Media */

This is an exploratory page to be used for storage of various multimedia metadata profiles currently in use around the web. As this is a very, very early exploration, we should include as many types of multimedia as possible in the opening discussion - but please be sure to place your profiles in the correct portion of this page.

= Purpose of this exploration (or : The Problem) =

The purpose of the studies on this page is to determine the feasibility and demand for a flexible, semantic markup format for providing metadata alongside linked multimedia files. Typically, this metadata is stored within the header of the media file itself - which has massive implications for any application where metadata is to be indexed, searched, or made externally accessible. Of course, even if you could easily access the correct portions of a media file remotely, you'd still have to cope with a multitude of open and proprietary metadata formats, each with it's own distinct fieldset, nomenclature and storage method.

This study aims to make a start at solving this problem.

== Contributors ==

These folks have contributed real-world examples and research to this document, and are interested in helping with a solution.

* Christopher Allen
* Dougal Campbell
* Dr. Ernie
* Rohit Khare
* Ryan King
* Kevin Marks
* Danski

If you contribute new real-world examples or research, and wish to help with a solution, please add your name as well.

= Examples =

== Still image ==

* [http://www.exif.org/Exif2-2.PDF EXIF]
* [http://www.tasi.ac.uk/2000/09/rdfmeta/ RDF for self-describing images]
* [http://archive.dstc.edu.au/RDU/staff/jane-hunter/PNG/paper.html An Indexing and Querying System for Online Images Based on the PNG Format and Embedded Metadata]
* [http://www.w3.org/TR/photo-rdf/ Describing and retrieving photos using RDF and HTTP]

== Audio ==

* [http://www.id3.org/ ID3v2]

* iTunes
** Album : String
** Artist : String
** Beats Per Minute : Number
** Bit Rate : Number
** Comment : Blob
** Composer : String
** Genre : String or Foreign ID
** Disc Number : Number
** Kind : Proprietary - could be implimented as MIME type
** My Rating : Number < 5
** Sample Rate : Number
** Size : Number
** Time : Number
** Track Number : Number
** Year : Number
**Additional metadata used internally by the application : Date Added (Timestamp), Date Modified (Timestamp), Equalizer (foreign ID), Play Count (Number), Grouping (Internal)
**Noteable absences : Tags, [[rel-license|License]], Copyright year. Also note common complaints about [http://www.everything2.com/index.pl?node_id=1707402 ID3 and classical music].

== Podcasts ==

* '''iTunes podcast:''' http://phobos.apple.com/static/podcast_specifications.pdf
(HTML version of spec: [http://labs.commerce.net/~rohit/How%20To%20Publish%20a%20Podcast%20on%20iTunes%20Music%20Store.html local archive], [http://labs.commerce.net/~rohit/iTunesRSS.html updated version from Apple Chapter Tool Beta docs], [http://phobos.apple.com/static/iTunesRSS.html online copy at Apple])

iTunes release 4.9 was widely heralded as an advance for mainstream acceptance of podcasting. However, while some advocates resist even the fragment of a trademarked name in the label for the phenomenon, the use of "itunes:" in the namespace is one of many design decisions in Apple's original specification that became focal points of debate. While Apple has a tradition of working on breakthrough features very quietly, they have been open to public input after its initial release. Many [http://daringfireball.net/2005/07/podcast_pocket other bloggers] have [http://usefulinc.com/edd/blog/contents/2005/06/28-rss-apple-itunes/read chronicled] [http://www.intertwingly.net/blog/2005/07/05/Insensitive-iTunes some of the feedback], as well as some [http://tantek.com/log/2005/07.html#d10t0130 face-to-face discussions].

A mailing list may be coming soon...

* '''Media RSS:''' http://search.yahoo.com/mrss

Media RSS has [http://www.ysearchblog.com/archives/000111.html been in the works longer], but doesn't have the overnight-adoption advantage of iTunes. However, it has a much broader ambit, including [http://www.ysearchblog.com/archives/000060.html video]; and a much broader [http://groups.yahoo.com/group/rss-media/ community of interest].

=== A Podcasting Microformat? ===

The best starting point for understanding these two proposals is [http://www.w3.org/2005/07/media-and-rss W3C's summary table, by Karl Dubost].

There are (at least) two paths to consider when 'porting' these proposals into Microformats:
# '''Standalone.''' What is the most straightforward rendering of each proposal into XHTML? This keeps the interests of the developers of ''consuming'' applications foremost: how can the migration be made as painless as possible?
# '''Refactored.''' Given the existing core of Microformats, what is the minimal (!) necessary to add on to RelLicense, RelTag, hReview, and so forth? This favors (we'd hope) content ''publishing'' applications: how can the marginal migration costs of adding media be made as painless as possible.

Mapping the existing specs requires understanding the data definitions set forth in each specification, and finding the optimal equivalents (where available). The following is a partial summary of one possible mapping:

{| border="1" cellpadding="5" cellspacing="0" style="border:1px solid grey;"
|+ Comparing existing proposals
! Aspect !! Apple !! Yahoo! !! Microformat?
|-
| '''Categorization'''
|| <itunes:category> <br> <itunes:keywords>
|| <media:category>
|| [[rel-tag | RelTag]]
|-
| '''Rating''' || <itunes:explicit>|| <media:adult> || [[hreview |hReview]]
|-
| '''Description''' ||<itunes:subtitle> <br> <itunes:summary>|| <media:text> || XHTML (e.g. < blockquote > )
|-
| '''Authorship'''
|| <itunes:author> <br> <itunes:owner> <br> <itunes:name> <br> <itunes:email>
|| <media:credit>
|| <cite> <br> [[hcard|hCard]]
|-
| '''Metadata''' || <itunes:duration> <br> <itunes:image>|| <media:thumbnail> <br> <media:hash> <br>
<media:content
url="http://www.foo.com/movie.mov"
fileSize="12216320"
type="video/quicktime"
isDefault="true"
expression="full"
bitrate="128"
framerate="25"
duration="185"
height="200"
width="300" />
|| ''needs a new microformat'' <br> e.g., <dt> <dd>
|-
| '''Licensing''' || <itunes:block> <br> <copyright> <br> <link>|| Not explicitly mentioned || [[rel-license | RelLicense]]
|-
|}

== Video ==
* [http://www.exif.org/Exif2-2.PDF EXIF] - (Yes, the spec deals with video taken by still cameras. -- RyanKing)
* [http://www.chiariglione.org/mpeg/standards/mpeg-7/mpeg-7.htm MPEG-7] - MPEG-7, formally named "Multimedia Content Description Interface", is a standard for describing the multimedia content data that supports some degree of interpretation of the information meaning, which can be passed onto, or accessed by, a device or a computer code. (Very powerful, but you have to pay for documentation -- [[User:ChristopherA|ChristopherA]] 01:53, 29 Jun 2005 (PDT))
* [http://www.w3.org/AudioVideo/ SMIL] - Synchronized Multimedia Integration Language (SMIL, pronounced "smile") enables simple authoring of interactive audiovisual presentations. (Not exactly video, but has a lot of useful video-related features in it. -- [[User:ChristopherA|ChristopherA]] 01:55, 29 Jun 2005 (PDT))

== Interactive ==
* [http://www.w3.org/Graphics/SVG/ SVG]
* [http://www.w3.org/AudioVideo/ SMIL]
* QTVR?

== Offline Media ==
(I'm not sure if you want to open the scope up this much.)

=== Printed Publications (books/magazines) ===
* [http://amazon.com/ Amazon]

=== Movies ===
* [http://imdb.com/ IMDB]
* [http://amazon.com/ Amazon]

=== Music ===
* [http://freedb.org/ FreeDB]
* [http://musicbrainz.org/ MusicBrainz]
* [http://amazon.com/ Amazon]

media-metadata-examples

2005-07-13T20:20:17Z

Dougal Campbell:

media-metadata-examples

2005-07-13T20:19:36Z

Dougal Campbell: /* Interactive */

media-metadata-examples

2005-07-13T19:37:25Z

Dougal Campbell: rdfpic

media-metadata-examples

2005-07-13T19:34:45Z

Dougal Campbell: embedded metadata paper

media-metadata-examples

2005-07-13T19:29:14Z

Dougal Campbell: rdfmeta

hreview

2005-07-12T19:34:31Z

Dougal Campbell: /* Human vs. Machine Readable */

= hReview 0.2 =

hReview is a simple, open, distributed reviews format suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. hReview is one of several [[microformats]] open standards.

__TOC__

== Draft Specification 2005-06-07 ==

=== Editor ===
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]

=== Authors ===
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]
* [http://360.yahoo.com/alidiabali Ali Diab],[http://yahoo.com Yahoo! Inc.]
* [http://spaces.msn.com/members/ianmcallister/ Ian McAllister], [http://microsoft.com/ Microsoft Corporation]
* [http://journals.aol.com/panzerjohn/abstractioneer John Panzer], [http://www.aol.com America Online, Inc.]
* [http://ifindkarma.com/blog Adam Rifkin], [http://labs.commerce.net/ CommerceNet Labs]
* [http://sippey.typepad.com/ Michael Sippey], [http://sixapart.com Six Apart, Ltd.]

== Introduction ==
Numerous web sites publish reviews using a broad variety of schema for all sorts of things from products (movies, music, books), to businesses (restaurants, hotels, stores), to events (concerts, theatre), to people (artists, leaders, celebrities), to places (landmarks, parks), to online resources (web pages, files), to reviews of reviews themselves.

In order to enable and encourage the sharing, distribution, syndication, and aggregation, of reviews, the authors propose the hReview MicroFormat, an open standard for distributed reviews. The authors have researched numerous earlier attempts at ReviewsFormats, and have designed hReview around a simple minimal schema for reviews. Feedback is encouraged on the ["hReviewFeedback"] page.

=== Working Name ===
The name "hReview" is a working name for this microformat. The name was suggested as it shares much with the hCard and hCalendar microformats, despite not having an IETF RFC to reference for a normative schema.

=== Copyright ===
{{MicroformatCopyrightStatement2005}}

=== Patents ===
{{MicroFormatPatentStatement}}

=== Inspiration and Acknowledgments ===
Thanks to everyone who responded to the open call for implementor participation for hReview. The authors in particular wish to thank the following individuals for their constructive input and feedback: [http://www.richardault.com/ Richard Ault], [http://dannyayers.com Danny Ayers], [http://www.vertexdev.com/~jeff/ Jeffrey Barr],[http://adriancuthbert.blogspot.com/ Adrian Cuthbert],[http://jason.defillippo.com/ Jason DeFillippo], [http://www.hybernaut.com/bdv Brian Del Vecchio], Scott Derringer, [http://budgibson.com/home/ Bud Gibson], [http://joi.ito.com/ Joi Ito], [http://www.kanai.net/weblog/ Gen Kanai],[http://niallkennedy.com/ Niall Kennedy], [http://labs.commerce.net/wiki/index.php/Rohit_Khare Rohit Khare], [http://theryanking.com/ Ryan King], [http://www.jluster.org/ Jonas Luster], [http://epeus.blogspot.com/ Kevin Marks], [http://www.powazek.com/ Derek Powazek], [http://www.judysbook.com/ Jeff Rodenburg], [http://sifry.com/alerts/ David Sifry], [http://jystewart.net/ James Stewart], [http://kung-foo.tv/ Adriaan Tijsseling], [http://www.flashenabled.com/ Phillip Torrone], Thai Tran, [http://w6daily.winn.com/ Phillip Winn], [http://yohei-y.blogspot.com YAMAMOTO Yohei].

=== Scope ===
Reviews consistently share several common fields. Where possible hReview has been based on this minimal common subset.

==== Out of scope ====
Fields that are type-specific have been omitted from hReview. It is important that hReview be kept simple and minimal from the start. Additional features can be added as deemed necessary by practical implementation experience.

The concept of a "universal object identifier", that is, how to identify the same object/item/product across different shopping sites, though something very useful to have, is outside the scope of this format.

== Semantic XHTML Design Principles ==
{{SemanticXHTMLDesignPrinciples}}

== Format ==
=== In General ===
The hReview format is based on a set of fields common to numerous review sites and formats in use today on the web. Where possible field names have been chosen based on those defined by the related [[hcard|hCard]] and [[hcalendar|hCalendar]] standards.

=== Schema ===
The hReview schema consists of the following:

* hReview
** version. optional. text.
** summary. optional. text.
** item type. optional. product | business | event | person | place | website | url.
** item info. required. (fn || url || photo ) | [[hcard|hCard]] (for person or business).
** reviewer. required. [[hcard|hCard]] | fn | email | url.
** dtreviewed. required. ISO8601 absolute date time.
** rating. optional. integer [1-5], with optional alternate worst (default:1) and/or best (default:5), also integers.
** description. optional. text with optional valid XHTML markup.
** tags. optional. keywords or phrases, using RelTag, each with optional rating.
** permalink. optional.

=== Field details ===
The fields of the hReview schema represent the following:

'''version''':: This optional field permits hReview publishers to specify a particular version of hReview that their content uses. By omitting this field, the publisher is stating that implementations may interpret the hReviews according to any version of the hReview specification v0.2 or later. In practice the authors of this specification are comitted to maintaining backward compatibility with content produced using earlier versions of the specification. This field is syntax compatible with, and thus reuses the semantics of "VERSION" as defined in vCard RFC2426 section "3.6.9 VERSION Type Definition". The value of this field for this specification is "0.2".

'''summary''':: This optional field serves as a title for the review itself.

'''item type''':: This optional field "type" provides the type of the item being reviewed, one of the following: product, business, event, person, place, website, url.

'''item info''':: This required field MUST have at a minimum the name ("fn" - the formatted text corresponding to the name) of the item , SHOULD provide at least one URI ("url") for the item, and MAY provide at least one URL to a photo or depiction ("photo") of the item. For items of type person or business, the item info (fn, url, photo) SHOULD be encapsulated in an [[hcard|hCard]]. Unique item IDs (e.g. ISBNs, UPCs) MAY be represented as a URN ("url") for the item.

'''reviewer''':: The person who authored the review. An hCard representing the reviewer SHOULD be provided with full name and URL. Alternatively, just a name, email address, or URL to the person MAY be provided. To specify more than one of those, encapsulate them in an hCard. For anonymous reviews, use "anonymous" (without quotes) for the full name of the reviewer.

'''dtreviewed''':: This required field MUST provide an ISO8601 absolute date time of when the review was written or otherwise authored. This field SHOULD use UTC, but MAY use the time zone offset syntax.

'''rating''':: The rating is an integer from 1 to 5 inclusive indicating a rating for the item, higher indicating a better rating. Optionally a different integral "worst" value and/or "best" value MAY be specified (e.g. 6 from 0-10).

'''description''':: This optional field contains the full text representing the written opinion of the reviewer. The field MAY include valid XHTML markup (e.g. paragraphs). User agents SHOULD preserve any markup. Multiple descriptions or section descriptions (e.g. pros and cons, plusses and minusses) SHOULD be included in the description field.

'''tags''':: Tags are represented using a list of keywords or phrases (using the [[reltag|RelTag]] microformat for each individual keyword or phrase tag) that the reviewer associates with the item. The reviewer MAY optionally provide a tag-specific rating inside each [[reltag|RelTag]], e.g. ambience:5. Tag-specific ratings by default use the same range as an overall rating for the item if present, and MAY also have a custom worst...best range specified. Authors MAY enclose all tags for a review inside an element with a specific classname, e.g. "categories" (from vCard RFC2426 and iCalendar RFC2445), but are not required to do so.

'''permalink''':: This optional field is a URL for the hReview. In addition to using the <code><a href></code> tag for this field, the attribute <code>rel="self bookmark"</code> MUST be used to indicate that the hyperlink is a permalink for the review itself. If the hyperlink already contains a <code>rel</code> attribute, then the values <code>self</code> and <code>bookmark</code> MUST be included among the space-separated set of values in the attribute. Indexers MAY treat the permalink of a review as a unique ID in order to identify and collate the same review from multiple sources (such as indexing a page multiple times). The permalink MAY also be used to indicate or imply the origin of the review. Authors MAY use the classname of "permalink" on the element representing the permalink, but are not required to do so.

The following field names have been reused from the [[hcard|hCard]] and [[hcalendar|hCalendar]] microformats: <code>version, summary, fn, url, email, photo, description, categories</code>. In addition, items and reviewers described by hCards MAY contain any hCard field.

=== More Semantic Equivalents ===

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For any "url", use <code><a class="url" href="...">...</a></code> inside the element with class="hreview" in hReview.
* Similarly, any "email", use <code><nowiki><a class="email" href="mailto:...">...</a></nowiki></code>
* And for "photo", use <code><img class="photo" src="..." alt="Photo of ..." /></code>

* Ratings are often presented either as a set of images or characters, e.g. "***". For these, the <code><abbr></code> element is particularly useful, as such characters are an abbreviation for the precise rating, e.g. <code><abbr class="rating" title="3">***</abbr></code>. This is further explored in the next section.

==== Language ====
* To explicitly convey the natural language that an hReview is written in, use the standard (X)HTML 'lang' attribute on the element with class="hreview", e.g. <code><div class="hreview" lang="en"> ... </div></code> If portions of an hReview (e.g. the item name) are in a different language, use the 'lang' attribute on those portions.
* hReview processors which need to handle the language of reviews MUST process the standard (X)HTML 'lang' attribute as specified.

=== Human vs. Machine Readable ===
If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

Similarly, if an <code><img /></code> element is used for one or more properties, it MUST be treated as follows:

# For the "photo" property and any other property that takes a URL as its value, the <code>src="..."</code> attribute provides the property value.
# For other properties, the <code><img /></code> element's '<code>alt</code>' attribute is the value of the property.

=== Notes ===
This section is informative.

* By marking up a review with the hReview microformat, the expectation is communicated that the review MAY be indexed. This has no impact on the copyright of the review itself.
* The enumerated list of item types is under development and may be extended.
* Each type may have custom hReview fields that follow the common set.
* Additional details about a particular item should be specified with the rest of the item's info at the URL provided for the item.
* Most rating systems use the range 1 to 5, and most of those represent the rating as a number of stars. Sites may use whatever graphic they wish to represent the rating.

== Examples ==
Here are a few examples of reviews from current web sites, and how they could be easily enhanced to support the hReview structured review microformat.

=== Restaurant reviews ===

Here is an example of a simple online restaurant review:

<code><pre><nowiki>
<div>
<span>5 stars out of 5 stars</span>
<h4>Crepes on Cole is awesome</h4>
<span>Reviewer: <span>Tantek</span> - April 18, 2005</span>
<blockquote><p>
Crepes on Cole is one of the best little creperies in San Francisco.
Excellent food and service. Plenty of tables in a variety of sizes
for parties large and small. Window seating makes for excellent
people watching to/from the N-Judah which stops right outside.
I've had many fun social gatherings here, as well as gotten
plenty of work done thanks to neighborhood WiFi.
</p></blockquote>
<p>Visit date: <span>April 2005</span></p>
<p>Food eaten: <span>Florentine crepe</span></p>
</div>
</nowiki></pre></code>

Adding hReview to this review is quite simple:

<code><pre><nowiki>
<div class="hreview">
<span><span class="rating">5</span> out of 5 stars</span>
<h4 class="summary"><span class="item fn">Crepes on Cole</span> is awesome</h4>
<span>Reviewer: <span class="reviewer fn">Tantek</span> -
<abbr class="dtreview" title="20050418T2300-0700">April 18, 2005</abbr></span>
<blockquote class="description"><p>
Crepes on Cole is one of the best little creperies in San Francisco.
Excellent food and service. Plenty of tables in a variety of sizes
for parties large and small. Window seating makes for excellent
people watching to/from the N-Judah which stops right outside.
I've had many fun social gatherings here, as well as gotten
plenty of work done thanks to neighborhood WiFi.
</p></blockquote>
<p>Visit date: <span>April 2005</span></p>
<p>Food eaten: <span>Florentine crepe</span></p>
</div>
</nowiki></pre></code>

Note that some of the properties of this sample review are not captured by hReview (visit date, food eaten). This is deliberate per the scope of keeping hReview minimal and simple.

This sample hReview could be rendered like this:

5 stars out of 5 stars<br />
'''Crepes on Cole is awesome'''<br />
Reviewer: Tantek - April 18, 2005<br />

<blockquote>Crepes on Cole is one of the best little creperies in San Francisco. Excellent food and service. Plenty of tables in a variety of sizes for parties large and small. Window seating makes for excellent people watching to/from the N-Judah which stops right outside. I've had many fun social gatherings here, as well as gotten plenty of work done thanks to neighborhood wifi.</blockquote>

Visit date: April 2005<br />
Food eaten: Florentine crepe<br />

==== Multidimensional Restaurant Review ====
Some restaurant reviews indicate ratings for different aspects of the restaurant. Such details are represented in hReview using tagged ratings. In addition, note the inline tags inside the description of this review.

Here is one such review in text format:

Cafe Borrone

1010 El Camino Real, Menlo Park, CA 94025, +1-650-327-0830;
cafeborrone.com

Food: 18/30; Ambience: 19/30; Service: 15/30; Price: $$...

This cafe is a welcoming oasis on the Peninsula. It even has a fountain
outside which cloaks the nearby sounds of El Camino traffic. Next door to a
superb indy bookstore, Cafe Borrone is an ideal spot to grab a coffee or a
snack to accompany a newly purchased book or imported periodical. Soups and
sandwich specials rotate daily. The corn chowder with croutons and big
chunks of cheese goes especially well with a freshly toasted mini-baguette.
Evenings are often crowded and may require sharing a table with a perfect
stranger. Espresso afficionados will appreciate the Illy coffee. Noise
levels can vary from peaceful in the late mornings to nearly overwhelming on
jazz band nights.

As an hReview:

<code><pre><nowiki>
<div class="hreview">
<div class="item vcard">
<div class="fn org summary">Cafe Borrone</div>
<span class="adr">
<span class="street-address">1010 El Camino Real</span>,
<span class="locality">San Francisco</span>,
<span class="region">CA</span>
<span class="postal-code">94025</span>,
</span>
<span class="tel"><span class="voice work">+1-650-327-0830</span></span>;
<a class="url" href="http://cafeborrone.com">cafeborrone.com</a>
</div>
<ul class="categories">
<li><a href="http://en.wikipedia.org/wiki/Food" rel="tag">
Food: <span class="rating">18</span>/<span class="best">30</span></a>;</li>
<li><a href="http://flickr.com/photos/tags/Ambience" rel="tag">
Ambience: <span class="rating">19</span>/<span class="best">30</span></a>;</li>
<li><a href="http://en.wikipedia.org/wiki/Service" rel="tag">
Service: <span class="rating">15</span>/<span class="best">30</span></a>;</li>
<li><a href="http://en.wikipedia.org/wiki/Price" rel="tag">
Price: <abbr class="rating" title="2">$$</abbr>...</a></li>
</ul>
<blockquote class="description"><p>
This <abbr class="type" title="business">
<a href="http://en.wikipedia.org/wiki/cafe" rel="tag">cafe</a></abbr>
is a welcoming oasis on the Peninsula.
It even has a fountain outside which nearly eliminates
the sounds of El Camino traffic. Next door to a superb indy bookstore,
Cafe Borrone is an ideal spot to grab a
<a href="http://en.wikipedia.org/wiki/coffee" rel="tag">coffee</a>
or a meal to accompany a newly purchased book or imported periodical.
<a href="http://technorati.com/tag/soup" rel="tag">Soups</a> and
<a href="http://technorati.com/tag/sandwich" rel="tag">sandwich</a>
specials rotate daily. The corn chowder with croutons and big chunks of cheese
goes especially well with a freshly toasted mini-baguette. Evenings are
often crowded and may require sharing a table with a perfect stranger.
<a href="http://flickr.com/photos/tags/espresso" rel="tag">Espresso</a>
afficionados will appreciate the
<a href="http://en.wikipedia.org/wiki/Illy" rel="tag">Illy</a> coffee.
Noise levels can vary from peaceful in the late mornings to nearly overwhelming on
<a href="http://en.wikipedia.org/wiki/jazz" rel="tag">jazz</a> band nights.
</p></blockquote>
Review (<a href="http://developers.technorati.com/wiki/hReview">
hReview v<span class="version">0.2</span></a>)
by <span class="reviewer">anonymous</span>,
<abbr class="dtreviewed" title="20050428T2130-0700">April 28th, 2005</abbr>.
</div>
</nowiki></pre></code>

With an accompanying CSS style sheet like:

<code><pre><nowiki>
a.url { display:block }
ul.categories { margin:1em 0; padding:0 }
.categories li { display:inline }
</nowiki></pre></code>

This hReview could be presented similar to the original text:

Cafe Borrone<br />
1010 El Camino Real, Menlo Park, CA 94025, +1-650-327-0830;<br />
[http://cafeborrone.com/ cafeborrone.com]<br />
<br />
[http://en.wikipedia.org/wiki/Food Food: 18/30];
[http://flickr.com/photos/tags/Ambience Ambience: 19/30];
[http://en.wikipedia.org/wiki/Service Service: 15/30];
[http://en.wikipedia.org/wiki/Price Price: $$...]<br />

<blockquote>This [http://en.wikipedia.org/wiki/cafe cafe] is a welcoming oasis on the Peninsula. It even has a fountain outside which cloaks the nearby sounds of El Camino traffic. Next door to a superb indy bookstore, Cafe Borrone is an ideal spot to grab a [http://en.wikipedia.org/wiki/coffee coffee] or a snack to accompany a newly purchased book or imported periodical. [http://technorati.com/tag/soup Soups] and [http://technorati.com/tag/sandwich sandwich] specials rotate daily. The corn chowder with croutons and big chunks of cheese goes especially well with a freshly toasted mini-baguette. Evenings are often crowded and may require sharing a table with a perfect stranger. [http://flickr.com/photos/tags/espresso Espresso] afficionados will appreciate the [http://en.wikipedia.org/wiki/Illy Illy] coffee. Noise levels can vary from peaceful in the late mornings to nearly overwhelming on [http://en.wikipedia.org/wiki/jazz jazz] band nights.</blockquote>

Review ([http://microformats.org/wiki/hreview hReview v0.2]) by anonymous, April 28th, 2005.

=== Product review ===
Here is an example of a product review:

<code><pre><nowiki>
<div>
<a href="http://www.amazon.com/exec/obidos/ASIN/B000089CJI/">
<img src="http://images.amazon.com/images/P/B000089CJI.01._SCTHUMBZZZ_.jpg"
alt="Album cover photo: The Postal Service: Give Up." />
The Postal Service: Give Up</a>
<blockquote><p>
"The people thought they were just being rewarded for treating others
as they like to be treated, for obeying stop signs and curing diseases,
for mailing letters with the address of the sender... Don't wake me,
I plan on sleeping in..."
</p><p>
"Nothing Better" is a great track on this album, too...
</p></blockquote>
(*****)
</div>
</nowiki></pre></code>

Adding hReview to this review is also quite simple, but in this case requires a few more elements for the rating and reviewer which are required by hReview:

<code><pre><nowiki>
<div class="hreview">
<a class="item url" href="http://www.amazon.com/exec/obidos/ASIN/B000089CJI/">
<img src="http://images.amazon.com/images/P/B000089CJI.01._SCTHUMBZZZ_.jpg"
alt="Album cover photo: The Postal Service: Give Up. "
class="photo" />
<span class="fn">The Postal Service: Give Up</span></a>
<blockquote class="description"><p>
"The people thought they were just being rewarded for treating others
as they like to be treated, for obeying stop signs and curing diseases,
for mailing letters with the address of the sender... Don't wake me,
I plan on sleeping in..."
</p><p>
"Nothing Better" is a great track on this album, too...
</p></blockquote>
(<abbr class="rating" title="5">*****</abbr>)
<p class="reviewer vcard">Review by
<a class="url fn" href="http://ifindkarma.com/blog/">Adam Rifkin</a>,
<abbr class="dtreviewed" title="200502">February 2005</abbr>
</p>
</div>
</nowiki></pre></code>

And this hReview might be presented like this:

[Album cover photo: ]
[The Postal Service:]
[ Give Up ]

The Postal Service: Give Up

<blockquote>"The people thought they were just being rewarded for treating others as they like to be treated, for obeying stop signs and curing diseases, for mailing letters with the address of the sender... Don't wake me, I plan on sleeping in..."</blockquote>

<blockquote>"Nothing Better" is a great track on this album, too... </blockquote>

(*****)

Review by Adam Rifkin, February 2005.

=== Movie Review ===
Finally, here is an example of a movie review.

<code><pre><nowiki>
<div>
<span>anonymous, April 18th, 2005</span>
<div>
<a lang="zh" href="http://www.imdb.com/title/tt0299977/">
Ying Xiong (<span lang="en">HERO</span>)
</a>
</div>
<div>Rating: 4 out of 5</div>
<blockquote><p>
This movie has great visuals and music.
</p></blockquote>
</div>
</nowiki></pre></code>

With hReview:

<code><pre><nowiki>
<div class="hreview">
<span class="reviewer">
<span class="fn">anonymous</span>,
<abbr class="dtreviewed" title="20050418">April 18th, 2005</abbr>
</span>
<div class="item">
<a lang="zh" class="url fn" href="http://www.imdb.com/title/tt0299977/">
Ying Xiong (<span lang="en">HERO</span>)
</a>
</div>
<div>Rating: <span class="rating">4</span> out of 5</div>
<blockquote class="description"><p>
This movie has great music and visuals.
</p></blockquote>
</div>
</nowiki></pre></code>

Which could be presented like this:

anonymous, April 18th, 2005<br />
Ying Xiong (HERO)<br />
Rating: 4 out of 5<br />

This movie has great music and visuals.

== Examples in the wild ==
This section is '''informative'''.

The following sites have published hReviews, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If you publish hReviews on your own page, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

* [http://www.dinnerbuzz.com/ Dinnerbuzz] is a great site for posting tagged reviews of restaurants, and they publish and summarize all their reviews in hReview!
* [http://soldierant.net/ Bryce Glass] posted an [http://soldierant.net/archives/2005/06/product_review.html hReview of the Uniden ELBT 595 Bluetooth Cordless Phone].
* dda posted an [http://sungnyemun.org/wordpress/?p=20 hReview of hReview] :)
* An [http://tbp.xomerang.com/?p=3 hReview of Caffè Camardo coffee].
* [http://loadaveragezero.com/hnav/contact.php Douglas Clifton] posted [http://loadaveragezero.com/#May-12-2005 comments] regarding adapting his list of 400+ [http://loadaveragezero.com/app/drx/Data_Formats/Metadata Developer Resources] as a format for testing hReview.
* [http://www.oliverbrown.me.uk/ Oliver Brown] [http://www.oliverbrown.me.uk/2005/05/09/sitereviewsorg-supports-hreview-i-think/ has announced] that his [http://en-us.sitereviews.org/ SiteReviews.org] (which reviews websites) publishes its reviews using hReview, e.g. here is the [http://en-us.sitereviews.org/review-photomatt.net review on SiteReviews.org for photomatt.net].
* [http://www.myelin.co.nz/post/ Phillip Pearson] is publishing hReviews in the [http://coffee.gen.nz/rss/reviews RSS feed of cafe reviews] on his [http://coffee.gen.nz/ kiwi coffee review site], which of course has the reviews in HTML with embedded hReview markup as well.
* [http://station11.net/ticker/ Kjell] is publishing his link blog as a [http://station11.net/ticker/ list of hReviews].
* [http://epeus.blogspot.com/ Kevin Marks] has [http://epeus.blogspot.com/2005_04_01_epeus_archive.html#111484565269684374 published two hReviews] and used unicode "star" characters for his ratings!
* JamesStewart is publishing hReviews in the location pages at his [http://grwifi.net Grand Rapids WiFi site].
* [http://soldierant.net/ Soldier Ant] has [http://soldierant.net/archives/2005/06/product_review.html reviewed a cordless phone].

== Implementations ==
This section is '''informative'''.

The following implementations have been developed which either generate or parse hReviews. If you have an hReview implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

* [http://sungnyemun.org/wordpress/?p=22 hReview plugin for WordPress]
* [http://theryanking.com/ Ryan King] has an [http://theryanking.com/microformats/hreview-creator.html hReview Creator].

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[hcalendar|hCalendar]]
* [[reltag|RelTag]]
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]
* [http://www.ietf.org/rfc/rfc3986.txt RFC3986]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.ietf.org/rfc/rfc3667.txt RFC3667]
* [http://www.ietf.org/rfc/rfc3668.txt RFC3668]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other reviews efforts. See [[reviews-formats]].
* Contributed from http://developers.technorati.com/wiki/hReview.

==== Similar Work ====
* [[xoxo]]

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

=== Changes from v0.1 ===
The following changes have been made in hReview v0.2:
# '''version'''. Added optional "version" field.
# '''language'''. Made explicit the reuse of (X)HTML 'lang' attribute to convey natural language information.
# '''tags requirement removed'''. Removed requirement of classname "tags" for the tags field, and thus removed the requirement to have an explicit tags field at all, permitting tags anywhere inside the hReview, e.g. inside the description.
# '''permalink requirement removed'''. Removed requirement of classname "permalink", as it is unnecessary, given that the permalink field explicitly requires a hyperlink with rel values of "self" and "bookmark".
# Updated examples accordingly.

== Discussions ==

* Feedback is encouraged on the [[hreview-feedback]] page.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

=== Q&A ===
* If you have any questions about hReview, check the [[hreview-faq|hReview FAQ]], and if you don't find answers, add your questions to the end!

=== Issues ===
* Please add any issues with the specification to the separate [[hreview-issues|hReview issues]] document.

User:Dougal Campbell

2005-06-21T18:56:10Z

Dougal Campbell:

Name: Ernest MacDougal Campbell III<br>
Location: Canton, Georgia USA<br>
Occupation: Web Developer<br>
Homepage: [http://dougal.gunters.org/ geek ramblings]<br>
Projects: [http://wordpress.org/ WordPress], [http://pingomatic.com/ Ping-O-Matic]

Yeah, yeah. I need a real bio here. I'll get around to that in my [http://info.astrian.net/jargon/terms/c/copious_free_time.html Copious Free Time].

Talk:hreview

2005-06-21T18:54:18Z

Dougal Campbell:

Some of the values for the 'type' field could use some more details, and some specific examples might be useful. In particular, I wonder about the 'product' type. If you are reviewing a book, a movie on DVD (or in a theater, for that matter), or a music CD, should you use the product type? Or since you're typically reviewing the content, and not the literal, physical product, should you just not specify a type? Or should there be a 'media' type?

Also, what is the difference between the 'website' and 'url' type?

--[[User:Dougal Campbell|Dougal Campbell]] 11:54, 21 Jun 2005 (PDT)