<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://microformats.org/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Dmitry+Baranovskiy</id>
	<title>Microformats Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://microformats.org/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Dmitry+Baranovskiy"/>
	<link rel="alternate" type="text/html" href="https://microformats.org/wiki/Special:Contributions/Dmitry_Baranovskiy"/>
	<updated>2026-05-14T05:40:10Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.38.4</generator>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=Acid_Test&amp;diff=26778</id>
		<title>Acid Test</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=Acid_Test&amp;diff=26778"/>
		<updated>2008-04-16T07:09:36Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==ACID Test for Parsers==&lt;br /&gt;
This is not really ACID test, but it sounds good. Basically test should run across as many as possible edge cases in microformats’ parsing. So far cases I found are:&lt;br /&gt;
* include pattern&lt;br /&gt;
* include inside include&lt;br /&gt;
* nested µf (agent as vcard inside vcard)&lt;br /&gt;
* multiple eleemtns of the same type&lt;br /&gt;
* “value” container&lt;br /&gt;
* correct work with abbr and img tags&lt;br /&gt;
* tel with type, but without value elements&lt;br /&gt;
* tel with type, without valu, but with “include”&lt;br /&gt;
* value as an ul element&lt;br /&gt;
* “headers” pattern&lt;br /&gt;
* “headers” with nested include&lt;br /&gt;
&lt;br /&gt;
That’s it so far. You could test your parsers over there: [http://microformatique.com/optimus/test.html]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This thing is under development and will be updated.&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=Acid_Test&amp;diff=26777</id>
		<title>Acid Test</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=Acid_Test&amp;diff=26777"/>
		<updated>2008-04-16T07:07:35Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This is not really ACID test, but it sounds good. Basically test should run across as many as possible edge cases in microformats’ parsing. So far cases I found are:&lt;br /&gt;
* include pattern&lt;br /&gt;
* include inside include&lt;br /&gt;
* nested µf (agent as vcard inside vcard)&lt;br /&gt;
* multiple eleemtns of the same type&lt;br /&gt;
* “value” container&lt;br /&gt;
* correct work with abbr and img tags&lt;br /&gt;
* tel with type, but without value elements&lt;br /&gt;
* tel with type, without valu, but with “include”&lt;br /&gt;
* value as an ul element&lt;br /&gt;
* “headers” pattern&lt;br /&gt;
* “headers” with nested include&lt;br /&gt;
&lt;br /&gt;
That’s it so far. You could test your parsers over there: [http://microformatique.com/optimus/test.html]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This thing is under development and will be updated.&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=parsing&amp;diff=27823</id>
		<title>parsing</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=parsing&amp;diff=27823"/>
		<updated>2008-04-16T06:25:30Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: /* Links */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Parsing =&lt;br /&gt;
This is a braindump, this page will need cleaning-up, take everything with a grain of salt at the moment.&lt;br /&gt;
&lt;br /&gt;
For now, start with reading [[hcard-parsing]] as that has more detail and has been more throughly reviewed and implemented.&lt;br /&gt;
&lt;br /&gt;
== By Element ==&lt;br /&gt;
This is a matrix of element and type. This should be describe under what circumstances each value and where that value comes from. The list of elements has been taken from http://www.w3.org/TR/html4/index/elements.html&lt;br /&gt;
&lt;br /&gt;
See [[semantic xhtml]] for a definitive list of elements.&lt;br /&gt;
&lt;br /&gt;
=== data types ===&lt;br /&gt;
(this probably needs a better name) There are two types in microformats, protocol types and strings. Strings could be integers, such as ratings, strings, such as a note, or datetimes, such as dtstart. Protocol types are UIDs, URLs, email addresses, (sometimes Telephones and faxes)&lt;br /&gt;
&lt;br /&gt;
If there is a comma list, then this is in order of availability. For instance, the ABBR element is @title,node-value. IF the @title is present then it is used, if not the stack is popped and node-value is looked at, if there is no node-value, then the value is NULL.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table border=&amp;quot;1&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;protocol&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;string&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;A&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;@href,node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;ABBR&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;@title,node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;@title,node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;ACRONYM&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;@title,node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;@title,node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;ADDRESS&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;APPLET&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;???&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;???(node-value)&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;AREA&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;@href,node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;B&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;BASE (valid?)&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;@href&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;BASEFONT (valid?)&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;BDO (valid?)&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;BIG&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;BLOCKQUOTE&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;@cite?,node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;BODY&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;BR (valid?)&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;BUTTON&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;@value?&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;@value?&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;CAPTION&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;CENTER&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;CITE&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;CODE&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;COL&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;COLGROUP&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;DD&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;DEL&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;@cite,node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;DFN&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;DIR&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;DIV&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;DL&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;DT&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;EM&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;FIELDSET&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;FONT&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;FORM&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;@action?,node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;FRAME&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;@src?,node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;FRAMESET&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;H1&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;H2&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;H3&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;H4&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;H5&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;H6&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;HEAD (valid?)&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;HR (valid?)&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;HTML (valid?)&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;I&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;IFRAME&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;@src?&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;IMG&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;@src&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;@alt&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;INPUT&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;@value?&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;@value?&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;INS&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;@cite,node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;ISINDEX (valid?)&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;KBD&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;LABEL&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;LEGEND&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;LI&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;LINK (valid?)&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;MAP&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;MENU (valid?)&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;META (valid?)&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;NOFRAMES&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;NOSCRIPT&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;OBJECT&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;@data,node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;OL&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;OPTGROUP (valid?)&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;OPTION&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;P&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;PARAM (?)&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;PRE&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;Q&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;S&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;SAMP&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;SCRIPT&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;SELECT (valid?)&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;SMALL&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;SPAN&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;STRIKE&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;STRONG&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;STYLE (valid?)&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;SUB&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;SUP&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;TABLE(valid?)&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;TBODY&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;TD&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;TEXTAREA&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;TFOOT&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;TH&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;THEAD&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;TITLE&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;TR&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;TT&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;U&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;UL&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;VAR&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;td&amp;gt;node-value&amp;lt;/td&amp;gt;&lt;br /&gt;
&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
* [http://www.xml.com/pub/a/2007/09/04/parsing-microformats.html XML.com Parsing microformats]&lt;br /&gt;
* [[Acid Test]]&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=User:Dmitry_Baranovskiy&amp;diff=32285</id>
		<title>User:Dmitry Baranovskiy</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=User:Dmitry_Baranovskiy&amp;diff=32285"/>
		<updated>2007-07-18T01:59:18Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Dmitry Baranovskiy&lt;br /&gt;
&lt;br /&gt;
[http://dmitry.baranovskiy.com Dmitry Baranovskiy’s Web Log]&lt;br /&gt;
&lt;br /&gt;
{{public-domain-release}}&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=events&amp;diff=14844</id>
		<title>events</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=events&amp;diff=14844"/>
		<updated>2007-03-27T00:58:01Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: /* Recent */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
=Microformats related events=&lt;br /&gt;
&lt;br /&gt;
Please add any microformats related events (specifically, events where there will be talks on microformats) you find here, and we'll add them to the [[hcalendar|hCalendar]] on the [http://microformats.org home page]. Please also create a page for each specific event, where you can list URLs for the event, event details, create an &amp;quot;Attending&amp;quot; section, link to photos afterwards, etc. (See [[events/2006-03-01-w3c-plenary-microformats|Microformats panel at W3C Plenary Day]] for a decent example to mimic/copy-paste). Thanks! -[http://tantek.com/ Tantek]&lt;br /&gt;
&lt;br /&gt;
If you can (or can ask the organisers to kindly-) use microformats (especially [[hCalendar]] and [[hCard]]) on the event's web pages, so much the better!&lt;br /&gt;
&lt;br /&gt;
There is a separate wiki page for details of [[presentations]].&lt;br /&gt;
&lt;br /&gt;
Patterns:&lt;br /&gt;
* YYYY-MM-DD: &amp;lt;nowiki&amp;gt;[[events/YYYY-MM-DD-event-session-title|Event Session Title]]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
* YYYY-MM-DD - YYYY-MM-DD: &amp;lt;nowiki&amp;gt;[[events/YYYY-MM-DD-event-session-title|Event Session Title]]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming ==&lt;br /&gt;
&amp;lt;!-- Please try to keep to neutral tense (e.g &amp;quot;Bill Smith on microformats&amp;quot; not &amp;quot;Bill Smith will talk about Microformats&amp;quot;), where possible, for convenience when moving to the historical section of this page. Please also include as many details about the event as possible, including precise start end times, room number, etc. Ideally details should be moved to the (events/..) wiki page for the event itself, but at least include the information here to start with. Thank you. --&amp;gt;&lt;br /&gt;
* 2007-03-20: [http://upcoming.org/event/161681/ Semantic London], a social gathering for people interested in microformats, SemWeb etc.&lt;br /&gt;
* 2007-03-23 [[events/2007-03-23-stanford|Microformats at Stanford]]&lt;br /&gt;
* 2007-04-16 [[events/2007-04-15-Web2Expo|Microformats for Web Services and Portable Content]] by Kevin Lawver at[http://www.web2expo.com/cs/webex2007/view/e_sess/11831 Web 2.0 Expo] in San Francisco.&lt;br /&gt;
* 2007-04-17 [[events/2007-04-15-Web2Expo|Microformats: Much more than just promise]] by John Allsopp, at [http://www.web2expo.com/cs/webex2007/view/e_sess/11831 Web 2.0 Expo] in San Francisco.&lt;br /&gt;
* 2007-04-18 [[events/2007-04-18-Web2ExpoDinner|Microformats Dinner]] following [http://www.web2expo.com/cs/webex2007/view/e_sess/11831 Web 2.0 Expo] in San Francisco.&lt;br /&gt;
* 2007-04-30 - 2007-05-02 [http://visitmix.com/ Mix07 Conference]: Microformats: Data Formats That Put Humans First. The Venetian, Las Vegas, NV&lt;br /&gt;
* 2007-05-16 [[events/2007-05-16-XTech|Microformats: the nanotechnology of the semantic web]] at the [http://2007.xtech.org/ XTech 2007] conference in Paris.&lt;br /&gt;
* …&lt;br /&gt;
&lt;br /&gt;
== Recent ==&lt;br /&gt;
&amp;lt;!-- Please change to past tense, and reverse the date-order, when moving events to this section. Thank you.--&amp;gt;&lt;br /&gt;
* 2007-03-22 [http://www.webdu.com.au/go/session/microformats--hidden-treasures Microformats—the hidden treasure] by Dmitry Baranovskiy at the [http://www.webdu.com.au/ webDU 2007] conference in Sydney, Australia. [http://dmitry.baranovskiy.com/microformats-webdu.pdf Presentation slides (PDF 5.1 Mb)]&lt;br /&gt;
* 2007-03-12: [[events/2007-03-12-sxsw-growth-evolution-of|The Growth and Evolution of Microformats]] at [http://2007.sxsw.com/interactive South by Southwest Interactive Festival] 2007 3/10-13. See also [http://2007.sxsw.com/interactive/programming/panels/ confirmed SXSWi 2007 panels].&lt;br /&gt;
* 2007-02-17 - 2007-02-18: Various microformateers were in attendance at [http://barcamp.org/BarCampLondon2 BarCampLondon] so various microformat related sessions featured. [[events/2007-02-17-barcamplondon2|Microformats at BarCampLondon]]&lt;br /&gt;
* 2007-02-07: [[events/2007-02-07-web-directions-north|microformats presentations at Web Directions North]] - 11:45am-12:45pm &amp;quot;Microformats - The Big Picture&amp;quot; with Tantek Çelik in ballroom I , 1:45pm-3:45pm: &amp;quot;Microformats - more than just promise&amp;quot; with John Allsopp and Dan Cederholm in ballroom II.&lt;br /&gt;
* 2007-02-03: [http://barcamp.org/BarCampBank3 how could we use microformats in banks ] - proposal from Christophe Ducamp (3pm-4pm) - Atelier BnpParibas 29 rue la Pérouse 75116 Paris - France (Métro Etoile)&lt;br /&gt;
* 2007-01-27: [[events/2007-01-la-get-together|Los Angeles Microformats Get Together]]&lt;br /&gt;
* 2007-01-18: [[events/2007-01-18-sf-microformats-dinner|San Francisco Microformats Dinner]] 6pm-? @ Nova on 2nd street. Details inside.&lt;br /&gt;
* 2007-01-03: [http://eventful.com/events/E0-001-002386631-6 Lancement du projet 'Cette Semaine en MicroFormats'] in Paris, France.&lt;br /&gt;
&lt;br /&gt;
==2006==&lt;br /&gt;
See [[events-2006]]&lt;br /&gt;
&lt;br /&gt;
== Quicktime Broadcaster Notes ==&lt;br /&gt;
&lt;br /&gt;
For setting up a mac laptop with an iSight and QT Broadcaster in order to publish live audio/video from events.&lt;br /&gt;
&lt;br /&gt;
# Make sure you have the necessary equipment and software installed&lt;br /&gt;
#* A Macintosh running OSX 10.3.9 or later&lt;br /&gt;
#* Quicktime 7 - get it from http://www.apple.com/quicktime/&lt;br /&gt;
#* Quicktime Broadcaster - get it from http://www.apple.com/quicktime/broadcaster/&lt;br /&gt;
#* An iSight or digital video camera with firewire connection&lt;br /&gt;
# Get a broadcast template document from someone (see KevinMarks for example)&lt;br /&gt;
# Open that, then change the info in the 'Network' pane that has his name etc in it.&lt;br /&gt;
# Check the video and audio panes are using your iSight&lt;br /&gt;
# Another tip is that the standalone thingy for the iSight can be more useful than the screen-top one if you have a desk, as that way it picks up less typing noise and wobbles&lt;br /&gt;
# I find plugging in headphones is a good idea, as you can then monitor and not get howlround&lt;br /&gt;
&lt;br /&gt;
http://microformats.org/media/broadcast.mov&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=events&amp;diff=14833</id>
		<title>events</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=events&amp;diff=14833"/>
		<updated>2007-03-27T00:54:28Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: /* Upcoming */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
=Microformats related events=&lt;br /&gt;
&lt;br /&gt;
Please add any microformats related events (specifically, events where there will be talks on microformats) you find here, and we'll add them to the [[hcalendar|hCalendar]] on the [http://microformats.org home page]. Please also create a page for each specific event, where you can list URLs for the event, event details, create an &amp;quot;Attending&amp;quot; section, link to photos afterwards, etc. (See [[events/2006-03-01-w3c-plenary-microformats|Microformats panel at W3C Plenary Day]] for a decent example to mimic/copy-paste). Thanks! -[http://tantek.com/ Tantek]&lt;br /&gt;
&lt;br /&gt;
If you can (or can ask the organisers to kindly-) use microformats (especially [[hCalendar]] and [[hCard]]) on the event's web pages, so much the better!&lt;br /&gt;
&lt;br /&gt;
There is a separate wiki page for details of [[presentations]].&lt;br /&gt;
&lt;br /&gt;
Patterns:&lt;br /&gt;
* YYYY-MM-DD: &amp;lt;nowiki&amp;gt;[[events/YYYY-MM-DD-event-session-title|Event Session Title]]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
* YYYY-MM-DD - YYYY-MM-DD: &amp;lt;nowiki&amp;gt;[[events/YYYY-MM-DD-event-session-title|Event Session Title]]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming ==&lt;br /&gt;
&amp;lt;!-- Please try to keep to neutral tense (e.g &amp;quot;Bill Smith on microformats&amp;quot; not &amp;quot;Bill Smith will talk about Microformats&amp;quot;), where possible, for convenience when moving to the historical section of this page. Please also include as many details about the event as possible, including precise start end times, room number, etc. Ideally details should be moved to the (events/..) wiki page for the event itself, but at least include the information here to start with. Thank you. --&amp;gt;&lt;br /&gt;
* 2007-03-20: [http://upcoming.org/event/161681/ Semantic London], a social gathering for people interested in microformats, SemWeb etc.&lt;br /&gt;
* 2007-03-23 [[events/2007-03-23-stanford|Microformats at Stanford]]&lt;br /&gt;
* 2007-04-16 [[events/2007-04-15-Web2Expo|Microformats for Web Services and Portable Content]] by Kevin Lawver at[http://www.web2expo.com/cs/webex2007/view/e_sess/11831 Web 2.0 Expo] in San Francisco.&lt;br /&gt;
* 2007-04-17 [[events/2007-04-15-Web2Expo|Microformats: Much more than just promise]] by John Allsopp, at [http://www.web2expo.com/cs/webex2007/view/e_sess/11831 Web 2.0 Expo] in San Francisco.&lt;br /&gt;
* 2007-04-18 [[events/2007-04-18-Web2ExpoDinner|Microformats Dinner]] following [http://www.web2expo.com/cs/webex2007/view/e_sess/11831 Web 2.0 Expo] in San Francisco.&lt;br /&gt;
* 2007-04-30 - 2007-05-02 [http://visitmix.com/ Mix07 Conference]: Microformats: Data Formats That Put Humans First. The Venetian, Las Vegas, NV&lt;br /&gt;
* 2007-05-16 [[events/2007-05-16-XTech|Microformats: the nanotechnology of the semantic web]] at the [http://2007.xtech.org/ XTech 2007] conference in Paris.&lt;br /&gt;
* …&lt;br /&gt;
&lt;br /&gt;
== Recent ==&lt;br /&gt;
&amp;lt;!-- Please change to past tense, and reverse the date-order, when moving events to this section. Thank you.--&amp;gt;&lt;br /&gt;
* 2007-03-12: [[events/2007-03-12-sxsw-growth-evolution-of|The Growth and Evolution of Microformats]] at [http://2007.sxsw.com/interactive South by Southwest Interactive Festival] 2007 3/10-13. See also [http://2007.sxsw.com/interactive/programming/panels/ confirmed SXSWi 2007 panels].&lt;br /&gt;
* 2007-02-17 - 2007-02-18: Various microformateers were in attendance at [http://barcamp.org/BarCampLondon2 BarCampLondon] so various microformat related sessions featured. [[events/2007-02-17-barcamplondon2|Microformats at BarCampLondon]]&lt;br /&gt;
* 2007-02-07: [[events/2007-02-07-web-directions-north|microformats presentations at Web Directions North]] - 11:45am-12:45pm &amp;quot;Microformats - The Big Picture&amp;quot; with Tantek Çelik in ballroom I , 1:45pm-3:45pm: &amp;quot;Microformats - more than just promise&amp;quot; with John Allsopp and Dan Cederholm in ballroom II.&lt;br /&gt;
* 2007-02-03: [http://barcamp.org/BarCampBank3 how could we use microformats in banks ] - proposal from Christophe Ducamp (3pm-4pm) - Atelier BnpParibas 29 rue la Pérouse 75116 Paris - France (Métro Etoile)&lt;br /&gt;
* 2007-01-27: [[events/2007-01-la-get-together|Los Angeles Microformats Get Together]]&lt;br /&gt;
* 2007-01-18: [[events/2007-01-18-sf-microformats-dinner|San Francisco Microformats Dinner]] 6pm-? @ Nova on 2nd street. Details inside.&lt;br /&gt;
* 2007-01-03: [http://eventful.com/events/E0-001-002386631-6 Lancement du projet 'Cette Semaine en MicroFormats'] in Paris, France.&lt;br /&gt;
&lt;br /&gt;
==2006==&lt;br /&gt;
See [[events-2006]]&lt;br /&gt;
&lt;br /&gt;
== Quicktime Broadcaster Notes ==&lt;br /&gt;
&lt;br /&gt;
For setting up a mac laptop with an iSight and QT Broadcaster in order to publish live audio/video from events.&lt;br /&gt;
&lt;br /&gt;
# Make sure you have the necessary equipment and software installed&lt;br /&gt;
#* A Macintosh running OSX 10.3.9 or later&lt;br /&gt;
#* Quicktime 7 - get it from http://www.apple.com/quicktime/&lt;br /&gt;
#* Quicktime Broadcaster - get it from http://www.apple.com/quicktime/broadcaster/&lt;br /&gt;
#* An iSight or digital video camera with firewire connection&lt;br /&gt;
# Get a broadcast template document from someone (see KevinMarks for example)&lt;br /&gt;
# Open that, then change the info in the 'Network' pane that has his name etc in it.&lt;br /&gt;
# Check the video and audio panes are using your iSight&lt;br /&gt;
# Another tip is that the standalone thingy for the iSight can be more useful than the screen-top one if you have a desk, as that way it picks up less typing noise and wobbles&lt;br /&gt;
# I find plugging in headphones is a good idea, as you can then monitor and not get howlround&lt;br /&gt;
&lt;br /&gt;
http://microformats.org/media/broadcast.mov&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=presentations&amp;diff=14632</id>
		<title>presentations</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=presentations&amp;diff=14632"/>
		<updated>2007-03-18T23:41:41Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: /* 2007 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt; microformats presentations &amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page lists various presentations, sessions, papers and posters which have provided explanations and discusions of both [[microformats]] in general, and specific microformats.  Check out microformats [[events]] for upcoming presentations. See also microformats [[podcasts]] and [[screencasts]] for audio/video presentations and discussions.&lt;br /&gt;
&lt;br /&gt;
Most recent presentations/sessions listed first.&lt;br /&gt;
&lt;br /&gt;
== 2007 ==&lt;br /&gt;
* 2007-03-22 [http://www.webdu.com.au/go/session/microformats--hidden-treasures Microformats—the hidden treasure] by Dmitry Baranovskiy at the [http://www.webdu.com.au/ webDU 2007] conference in Sydney, Australia, 3:00pm–4:00pm&lt;br /&gt;
* 2007-02-19, [http://www.glennjones.net/Post/825/DestroyingWalledGardens-MicroformatssyndicationandAPI%e2%80%99s.htm Destroying Walled Gardens - Microformats syndication and API’s] at [http://barcamp.org/BarCampLondon2 BarCamp London 2], UK by Glenn Jones&lt;br /&gt;
* 2007-02-07, [http://north.webdirections.org Web Directions North 2007], [http://north.webdirections.org/detail/venue/ Renaissance Vancouver Hotel Harbourside], 1133 West Hastings Street, Vancouver, British Columbia, V6E3T3, Canada&lt;br /&gt;
** [[events/2007-02-07-web-directions-north|Microformats at Web Directions North 2007]], 11:45am-12:45pm, 1:45pm-3:45pm&lt;br /&gt;
*** Tantek Çelik (Technorati) - &amp;quot;[http://tantek.com/presentations/2007/02/microformats/ Microformats — The Big Picture]&amp;quot;&lt;br /&gt;
*** John Allsopp (Westciv) - &amp;quot;[http://north.webdirections.org/presentations/MicroformatsForDevelopers.pdf Microformats For Developers]&amp;quot;&lt;br /&gt;
*** Dan Cederholm (Simplebits) - &amp;quot;[http://north.webdirections.org/presentations/MicroformatsForDesigners.pdf Microformats For Designers]&amp;quot;&lt;br /&gt;
* 2007-02-03 [http://www.glennjones.net/Post/823/Microformats%2ctheAK-47oftheweb-WebDD.htm Microformats HTML to API] at [http://www.webdd.org.uk/ WebDD], Reading UK by Glenn Jones&lt;br /&gt;
&lt;br /&gt;
== 2006 ==&lt;br /&gt;
* 2006-11-24, Taichi Kaminogoya presented to [http://2xup.org/log/2006/11/27-2219 microformats に触れてみよう] at [http://www.asahi-net.or.jp/~eb2m-mrt/kaihatsu9.html XML Developers' Day #9], Tokyo, JAPAN.&lt;br /&gt;
* October 28th, [http://www.keepthebyte.ch/2006/10/microformats-speech-at-barcamp-zurich.html Microformats Speech at Barcamp Zurich]&lt;br /&gt;
* October 10th, Taichi Kaminogoya presented to [http://2xup.org/log/2006/10/10-1800 microformatsがもたらすドキドキする未来] at [http://lp1.cssnite.jp/ CSS Nite LP Disk 1], Tokyo, JAPAN.&lt;br /&gt;
* September 28th, [http://www.webdirections.org/microformats/ Microformats] at Web Directions South, Sydney Australia by John Allsopp. [http://www.webdirections.org/microformats/ slides, podcast, live blogging transcript all online now]&lt;br /&gt;
* September 27th, [http://tantek.com/presentations/2006/09/microformats-intro/ Microformats Intro] at New Context 2006, Radisson Miyako Hotel, Minato-ku, Tokyo, JAPAN.  See also [http://flickr.com/photos/tags/microformatsnewcontext2006 photos].&lt;br /&gt;
* September 16th, [http://fredericdevillamil.com/presentations/2006/que-sont-les-microformats/index.html Introducing Microformats for resume publishing] in French by Frederic de Villamil at Barcamp Paris 4. Location: 43 rue d'Aboukir, 75002 Paris France&lt;br /&gt;
* September 13th, [http://tantek.com/presentations/2006/09/microformats-practices/ Microformats Practices] at [[events/2006-09-13-future-of-web-apps-microformats|Future of Web Apps]] in San Francisco.  Location: Palace of Fine Arts Theatre, Lyon Street, San Francisco CA 94123.&lt;br /&gt;
* August 26th, Tantek Çelik led the [http://barcamp.org/BarCampStanfordMicroformats BarCampStanfordMicroformats] discussion at room 426, Margaret Jacks Hall, Stanford, CA 94305.  There is an [http://barcamp.org/f/MF-barcamp_08_26_2006.ogg Ogg recording of the session].&lt;br /&gt;
* July 11th, [http://tantek.com/presentations/2006/07/what-are-microformats/ What are microformats?] at [[events/2006-07-11-an-event-apart-microformats|An Event Apart in New York City]]&lt;br /&gt;
* July 6th, [http://yatil.de/webmontag/ka0706/ Mikroformate Erweiterte Semantik von HTML-Dokumenten] (Präsentation von Eric Eggert) Web mondays presentation in german - translation is available here&lt;br /&gt;
* June 15th, Phil Wilson presented to the [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/ Institutional Web Management Workshop]&lt;br /&gt;
* June 8, Pete Prodoehl presented [http://rasterweb.net/raster/presentations/microformats-20060608/ Microformats] to the Milwaukee Web Design Meetup Group&lt;br /&gt;
* May 30, [http://netsquared.org NetSquared] [http://netsquared.org/conference/ Conference], 4:15pm-5:10pm: : [http://netsquared.org/conference/conference-sessions/Mashups A web more woven - the alchemy and practicalities of Mashups].  Tantek Çelik, Taylor McKnight and Chris Messina will discuss the core utility of microformats to publish and share data for/with mashups and other applications.  Location:  Jordan room, Cisco Systems' Vineyard Conference Center, 260 E. Tasman Drive, San Jose, CA.&lt;br /&gt;
* May 25, Brian Suda and Ryan King presented [http://theryanking.com/presentations/2006/www/ Practical Microformats] at WWW 2006 ([http://www.molly.com Molly Holzschlag] was orginally scheduled to give this talk, we filled in at the last minute with our slides from XTech)&lt;br /&gt;
* May 24, Kevin Lawver presented [http://presentations.lawver.net/standards/a_microformat_and_proposal_for/ A Microformat and Proposal For Interoperable Widgets]&lt;br /&gt;
* May 18, [http://xtech06.usefulinc.com/schedule/paper/148 The Intelligent Design of Microformats] by Ryan King at XTech 2006. ([http://theryanking.com/presentations/2006/xtech/talk/ slides]).&lt;br /&gt;
* May 16, [http://thebigjc.org/articles/2006/05/16/is-web-2-0-changing-the-software-industry Is Web 2.0 Changing the Software Industry?] by Chris Messina at [http://meshconference.com Mesh Conference]&lt;br /&gt;
* May 16, [http://theryanking.com/presentations/2006/xtech/tutorial/ Microformats from the Ground Up] by Brian Suda and Ryan King @ XTech 2006&lt;br /&gt;
* April 25, At [http://barcamp.org/TorCampDemoCamp5 DemoCamp #5 in Toronto], [http://blog.davidjanes.com David Janes] demonstrated [http://www.blogmatrix.com/ BlogMatrix] his platform for publish which supports microformats. (see [http://accordionguy.blogware.com/blog/_archives/2006/4/26/1913279.html  Accordionguy blogpost]).&lt;br /&gt;
* April 23, [http://jazkarta.com/presentations/microformats.pdf/view Microformats and the Future of Syndication] by Nate Aune, AdaptiveWave (CM Pros Summit, San Francisco, CA)&lt;br /&gt;
* April 22, Intro to Microformats, [http://barcamp.pbwiki.com/BarCampBangalore Barcamp Bangalore], Bangalore, India, (photos [http://flickr.com/photos/abgpt/133393564/ 1], [http://flickr.com/photos/abgpt/133393545/ 2], [http://flickr.com/photos/abgpt/133393626/ 3])&lt;br /&gt;
* March 16, [http://ono.cdlib.org/archives/shimenawa/000219.html Reading 2.0] (see [http://radar.oreilly.com/archives/2006/03/link_list_reading_20_1.html Tim O'Reilly's notes]), San Francisco, CA&lt;br /&gt;
** Building with MicroFormats, [http://www.chaddickerson.com/blog/2006/03/17/reading-20-and-microformats/ Chad Dickerson], Yahoo &lt;br /&gt;
* March 13, SXSW Interactive, Room 17AB, Austin Convention Center, Austin, TX&lt;br /&gt;
** [[events/2006-03-13-sxsw-microformats|Microformats: Evolving the Web]], 11:30am-12:30pm &lt;br /&gt;
* March 11, SXSW Interactive, Room 17AB, Austin Convention Center, Austin, TX&lt;br /&gt;
** [http://tantek.com/presentations/2006/03/building-blocks Creating Building Blocks For Independents], 5pm-6pm&lt;br /&gt;
** [http://flickr.com/photos/tags/microformatssxsw photos]&lt;br /&gt;
* March 7, O'Reilly Emerging Technologies (ETech) Conference, Manchester Grand Hyatt, Ballroom, San Diego, CA&lt;br /&gt;
** [[events/2006-03-07-etech-microformats|Microformats intro and lightning demos at O'Reilly ETech conf.]], 5:30pm-6:15pm &lt;br /&gt;
** [http://flickr.com/photos/tags/microformatsetech photos]&lt;br /&gt;
* March 1, W3C Technical Plenary Day, Hotel Sofitel Cannes Mandelieu Royal Casino, main auditorium, 605 avenuedu Général de Gaulle, BP 49, MANDELIEU LA NAPOULE CEDEX, 06212 MANDELIEU LA NAPOULE, FRANCE&lt;br /&gt;
** [[events/2006-03-01-w3c-plenary-microformats|Microformats panel at W3C Technical Plenary Day]], 10:30am-11:30am&lt;br /&gt;
*** Ian Hickson (Google) - &amp;quot;A billion documents and no semantics anywhere&amp;quot; (NEED LINK TO SLIDES OR STUDY)&lt;br /&gt;
*** Tantek Çelik (Technorati) - &amp;quot;[http://tantek.com/presentations/2006/03/what-are-microformats/ What are microformats?]&amp;quot;&lt;br /&gt;
*** Håkon Wium Lie (Opera) - &amp;quot;Cascading Markup Languages — boom!&amp;quot; (NEED LINK TO SLIDES)&lt;br /&gt;
*** Rohit Khare (CommerceNet) - &amp;quot;[http://labs.commerce.net/~rohit/Angstro-W3C-TP/ Where Angle Brackets Fear to Tread]&amp;quot;&lt;br /&gt;
*** Dan Connolly (W3C) - &amp;quot;[http://www.w3.org/2003/g/talk62/slides Microformats for practical Semantic Web deployment]&amp;quot;&lt;br /&gt;
*** Q&amp;amp;A&lt;br /&gt;
**** &amp;quot;I'm very excited about '''microformats'''. What I really want is to get all the data out of databases and expressed as part of the Semantic Web.&amp;quot; - Tim Berners-Lee. ('''emphasis''' added)&lt;br /&gt;
** &amp;quot;Services and the Web&amp;quot; by Mark Nottingham (Yahoo), 12:05pm-12:10pm.&lt;br /&gt;
*** Request to W3T/W3M: Go After The &amp;quot;Real&amp;quot; Web: Apache, PHP, Mozilla, Intermediaries and Caches, '''Microformats''', JSON... ('''emphasis''' added)&lt;br /&gt;
** Attendees voted the &amp;quot;Microformats&amp;quot; session the best session of the Plenary Day. 6:17pm.&lt;br /&gt;
* February 24, Yahoo Speakers Series, Yahoo Mission College Campus, 2nd floor conference room, 2821 Mission College Blvd., Santa Clara, CA 95054&lt;br /&gt;
** [http://tantek.com/presentations/2006/02/microformats-evolution/ Microformats: Evolving the Web]&lt;br /&gt;
* January 18, Apple Web Publishers internal meeting, Apple Computer, Star Trek conference room, 1 Infinite Loop, Cupertino, CA 95014, 12-1:40pm&lt;br /&gt;
** [http://tantek.com/presentations/2006/01/microformats-evolution/ Microformats: Evolving the Web]&lt;br /&gt;
* January 10, SD Forum Emerging Technologies SIG, Room H1, Cubberley Community Center, Palo Alto, CA, 7-9pm&lt;br /&gt;
** Ryan King's presentation, Ernie Prabhakar's presentation, Rohit Khare's presentation&lt;br /&gt;
** Microformats panel: Ryan King, Ernie Prabhakar, Rohit Khare, Tantek Çelik, Kevin Marks&lt;br /&gt;
&lt;br /&gt;
== 2005 ==&lt;br /&gt;
* December 15, Syndicate Conference, San Francisco, CA&lt;br /&gt;
** [http://tantek.com/presentations/2005/12/syndicate-microformats/ Microformats - Emerging syndication types]&lt;br /&gt;
* November 26, [http://barcamp.org/index.cgi?TorCamp TorCamp], Teehan+Lax, 460 Richmond St. W, Toronto, ON, CA&lt;br /&gt;
** [http://www.davidjanes.com/docs/2005.11.25%20Microformats%20Presentation.ppt powerpoints] (sorry)&lt;br /&gt;
** [http://blog.davidjanes.com/mtarchives/2005_12.html#003467 photo]&lt;br /&gt;
* November 12, THINK Conference, Santa Cruz room, Chaminade hotel, Santa Cruz, CA, USA&lt;br /&gt;
** [[presentation-think-2005-11-12]]&lt;br /&gt;
* November 10, (location unknown), by Kevin Yank of SitePoint Pty. Ltd.&lt;br /&gt;
** [http://www.sitepoint.com/examples/innovation-on-standards/ Innovating on top of standards - Not around them]&lt;br /&gt;
* October 5, [http://web2con.com Web 2.0 Conference], Olympic Room, Argent Hotel, San Francisco, CA, USA&lt;br /&gt;
** [http://tantek.com/presentations/2005/10/microformats-examples/ Microformats Examples]&lt;br /&gt;
* October 4, [http://osafoundation.org/ OSAF], San Francisco, CA, USA&lt;br /&gt;
** [http://tantek.com/presentations/2005/10/microformats-evolution/ Microformats: Evolving the Web]&lt;br /&gt;
* September 30, [http://we05.com/ Web Essentials 05], Guthrie auditorium, University of Technology, Sydney, Australia&lt;br /&gt;
** [http://tantek.com/presentations/2005/09/microformats-evolution/ Microformats: Evolving the Web] ([http://we05.com/podcast/mp3/we05-14-tantek-celik2.mp3 MP3 - incomplete])&lt;br /&gt;
* September 29, [http://we05.com/ Web Essentials 05], Guthrie auditorium, University of Technology, Sydney, Australia&lt;br /&gt;
** [http://tantek.com/presentations/2005/09/elements-of-xhtml/ The Elements of Meaningful XHTML] ([http://we05.com/podcast/mp3/we05-2-tantek-celik.mp3 MP3])&lt;br /&gt;
* September 25, [http://webzine2005.com/ Webzine 2005], Valhalla Room, Swedish American Hall, San Francisco, CA, USA&lt;br /&gt;
** [http://theryanking.com/presentations/2005/webzine/ Microformats @ Webzine 2005]&lt;br /&gt;
* September 21, Web Intelligence Conference, Compiegne, France &lt;br /&gt;
** [http://moloko.itc.it/paoloblog/presentations/presentation_wi05/presentation_wi05.html Page-reRank: using trusted links to re-rank authority] ([http://sra.itc.it/people/massa/publications/wi05_page_rerank_massa_hayes.pdf paper]) - A discussion of using [[vote-links]] to improve [http://www-db.stanford.edu/~backrub/google.html PageRank]&lt;br /&gt;
* June 20: Supernova 2005 ([http://supernova2005.com/ Supernova2005 site]), Microformats [http://supernova2005.com/workshops.htm Workshop], Wharton West, Suite 500, San Francisco, CA, USA&lt;br /&gt;
** &amp;quot;[http://tantek.com/presentations/2005/06/what-are-microformats/ What are Microformats?]&amp;quot;&lt;br /&gt;
** &amp;quot;[http://homepage.mac.com/kevinmarks/supernovatags.html A microformat for tags]&amp;quot;&lt;br /&gt;
** [http://wiki.commerce.net/wiki/ZCommerceWS#Microformats commercenet wiki page on the workshop] ([http://labs.commerce.net/wiki/index.php/ZCommerceWS#Microformats 2])&lt;br /&gt;
* May 14: Fourteenth International World Wide Web Conference ([http://www2005.org/ WWW2005]), 2005, Microformats Dev-Day Track, Makuhari Messe Room 303, Chiba, JAPAN&lt;br /&gt;
** &amp;quot;[http://tantek.com/presentations/2005/05/what-are-microformats/ What are Microformats?]&amp;quot; - Tantek Çelik &lt;br /&gt;
** &amp;quot;[http://westciv.com/WWW2005/linkmf.html Link Microformats]&amp;quot; - John Allsopp&lt;br /&gt;
** &amp;quot;[http://complexspiral.com/events/archive/2005/www2005/potential.html The Potential of Microformats]&amp;quot; - Eric Meyer&lt;br /&gt;
** &amp;quot;Distributed Social Networks (XFN Implementations)&amp;quot;&lt;br /&gt;
*** Demonstrations of [http://wordpress.org WordPress] &amp;amp; [http://metafilter.com Metafilter]'s builtin XFN support, and XFN search engines [http://rubhub.com/ RubHub] &amp;amp; [http://xhtmlfriends.net/ xhtmlfriends.net].&lt;br /&gt;
** &amp;quot;[http://tantek.com/presentations/2005/05/hcard-hcalendar/ People and Events (hCard &amp;amp; hCalendar)]&amp;quot; - Tantek Çelik&lt;br /&gt;
** &amp;quot;[http://cnlabs.commerce.net/~rohit/hReview-in-Review/ hReview in Review]&amp;quot; - Rohit Khare&lt;br /&gt;
** &amp;quot;Bibliographies (hBib)&amp;quot; - notes captured: [[hbib-discussion-2005-05-14|hBib Discussion 2005-05-14]]&lt;br /&gt;
** &amp;quot;[http://westciv.com/WWW2005/xml2mf.html a more meaningful web with microformats]&amp;quot;&lt;br /&gt;
** &amp;quot;Semantic Web and Microformats&amp;quot; panel, Room 201&lt;br /&gt;
&lt;br /&gt;
* March 15: &amp;quot;[http://tantek.com/presentations/2005/03/decentralizednetworks/ Decentralized Social Networks]&amp;quot;, South by South West Conference (SXSW) 2005, Austin Convention Center Room 17AB, Austin TX&lt;br /&gt;
&lt;br /&gt;
* March 14: &amp;quot;[http://2005.sxsw.com/interactive/conference/panels/?action=show&amp;amp;id=IAP0060 How to Trick-Out Your Blog]&amp;quot;, South by South West Conference (SXSW) 2005, Austin Convention Center Room 16B, Austin TX&lt;br /&gt;
&lt;br /&gt;
* March 13&lt;br /&gt;
** &amp;quot;[http://complexspiral.com/events/archive/2005/sxsw/ Emergent Semantics]&amp;quot;, South by South West Conference (SXSW) 2005, Austin Convention Center Room 15, Austin TX&lt;br /&gt;
** &amp;quot;[http://tantek.com/presentations/2005/03/leveragingtags.html Leveraging Tags]&amp;quot;, as part of the &amp;quot;How to Leverage Solipsism&amp;quot; panel, South by South West Conference (SXSW) 2005, Austin Convention Center Room 18A, Austin TX&lt;br /&gt;
** &amp;quot;[http://tantek.com/presentations/2005/03/elementsofxhtml/ The Elements of Meaningful XHTML]&amp;quot;, South by South West Conference (SXSW) 2005, Austin Convention Center Room 16B, Austin TX&lt;br /&gt;
&lt;br /&gt;
* January 21: [http://tantek.com/presentations/2005/01/attentionxml.html Attention.xml Technology Overview], private presentation, Yahoo! campus, Santa Clara, CA&lt;br /&gt;
&lt;br /&gt;
== 2004 ==&lt;br /&gt;
&lt;br /&gt;
* September 28: &amp;quot;[http://tantek.com/presentations/20040928sdforumws/semantic-xhtml.html Semantic XHTML: Can your website be your API? - Using semantic XHTML to show what you mean]&amp;quot;, SD Forum Web Services SIG, eBay's Silicon Valley Conference Center 2161 North First Street San Jose, CA 95131&lt;br /&gt;
&lt;br /&gt;
* September 12: &amp;quot;[http://wiki.oreillynet.com/foocamp04/index.cgi?MVCeqXHTMLCSSJS Model+View+Controller = XHTML+CSS+JS]&amp;quot;, O'Reilly Media Foo Camp 2004, O'Reilly Campus, Wallcreeper room, Sebastopol CA&lt;br /&gt;
&lt;br /&gt;
* September 11: &amp;quot;[http://wiki.oreillynet.com/foocamp04/index.cgi?AttentionXML Attention.XML]&amp;quot;, O'Reilly Media Foo Camp 2004, O'Reilly Campus, Appaloosa room, Sebastopol CA&lt;br /&gt;
&lt;br /&gt;
* September 10: &amp;quot;[http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats Simple Semantic Formats]&amp;quot;, O'Reilly Media Foo Camp 2004, O'Reilly Campus, Camel room, Sebastopol CA&lt;br /&gt;
&lt;br /&gt;
* March 15: &amp;quot;[http://tantek.com/presentations/2004sxsw/xfn.html Ridiculously Easy Social Software]&amp;quot;, South by South West Conference (SXSW) 2004, Austin Convention Center Room 17B, Austin TX&lt;br /&gt;
&lt;br /&gt;
* February 11th: &amp;quot;[http://www.tantek.com/presentations/2004etech/realworldsemanticspres.html real world semantics]&amp;quot;, O'Reilly Emerging Technology Conference (ETech) 2004 Westin Horton Plaza, San Diego, CA.  This presentation was the first public discussion and introduction of the terms &amp;quot;microformat&amp;quot; and &amp;quot;lowercase semantic web&amp;quot;.  Reprised as a five-minute lightning talk at [http://wiki.oreillynet.com/etech/index.cgi?ConCon ConCon], Rx Gallery, San Francisco CA (16 February 2004).&lt;br /&gt;
&lt;br /&gt;
This page was contributed from [http://developers.technorati.com/wiki/MicroFormatsPresentations the Technorati developers wiki].&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=events&amp;diff=14492</id>
		<title>events</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=events&amp;diff=14492"/>
		<updated>2007-03-18T23:38:34Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: /* Upcoming */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
=Microformats related events=&lt;br /&gt;
&lt;br /&gt;
Please add any microformats related events (specifically, events where there will be talks on microformats) you find here, and we'll add them to the [[hcalendar|hCalendar]] on the [http://microformats.org home page]. Please also create a page for each specific event, where you can list URLs for the event, event details, create an &amp;quot;Attending&amp;quot; section, link to photos afterwards, etc. (See [[events/2006-03-01-w3c-plenary-microformats|Microformats panel at W3C Plenary Day]] for a decent example to mimic/copy-paste). Thanks! -[http://tantek.com/ Tantek]&lt;br /&gt;
&lt;br /&gt;
If you can (or can ask the organisers to kindly-) use microformats (especially [[hCalendar]] and [[hCard]]) on the event's web pages, so much the better!&lt;br /&gt;
&lt;br /&gt;
There is a separate wiki page for details of [[presentations]].&lt;br /&gt;
&lt;br /&gt;
Patterns:&lt;br /&gt;
* YYYY-MM-DD: &amp;lt;nowiki&amp;gt;[[events/YYYY-MM-DD-event-session-title|Event Session Title]]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
* YYYY-MM-DD - YYYY-MM-DD: &amp;lt;nowiki&amp;gt;[[events/YYYY-MM-DD-event-session-title|Event Session Title]]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming ==&lt;br /&gt;
&amp;lt;!-- Please try to keep to neutral tense (e.g &amp;quot;Bill Smith on microformats&amp;quot; not &amp;quot;Bill Smith will talk about Microformats&amp;quot;), where possible, for convenience when moving to the historical section of this page. Please also include as many details about the event as possible, including precise start end times, room number, etc. Ideally details should be moved to the (events/..) wiki page for the event itself, but at least include the information here to start with. Thank you. --&amp;gt;&lt;br /&gt;
* 2007-03-20: [http://upcoming.org/event/161681/ Semantic London], a social gathering for people interested in microformats, SemWeb etc.&lt;br /&gt;
* 2007-03-22 [http://www.webdu.com.au/go/session/microformats--hidden-treasures Microformats—the hidden treasure] by Dmitry Baranovskiy at the [http://www.webdu.com.au/ webDU 2007] conference in Sydney, Australia &lt;br /&gt;
* 2007-04-16 [[events/2007-04-15-Web2Expo|Microformats for Web Services and Portable Content]] by Kevin Lawver at[http://www.web2expo.com/cs/webex2007/view/e_sess/11831 Web 2.0 Expo] in San Francisco.&lt;br /&gt;
* 2007-04-17 [[events/2007-04-15-Web2Expo|Microformats: Much more than just promise]] by John Allsopp, at [http://www.web2expo.com/cs/webex2007/view/e_sess/11831 Web 2.0 Expo] in San Francisco.&lt;br /&gt;
* 2007-04-18 [[events/2007-04-18-Web2ExpoDinner|Microformats Dinner]] following [http://www.web2expo.com/cs/webex2007/view/e_sess/11831 Web 2.0 Expo] in San Francisco.&lt;br /&gt;
* 2007-05-16 [[events/2007-05-16-XTech|Microformats: the nanotechnology of the semantic web]] at the [http://2007.xtech.org/ XTech 2007] conference in Paris.&lt;br /&gt;
* …&lt;br /&gt;
&lt;br /&gt;
== Recent ==&lt;br /&gt;
&amp;lt;!-- Please change to past tense, and reverse the date-order, when moving events to this section. Thank you.--&amp;gt;&lt;br /&gt;
* 2007-03-12: [[events/2007-03-12-sxsw-growth-evolution-of|The Growth and Evolution of Microformats]] at [http://2007.sxsw.com/interactive South by Southwest Interactive Festival] 2007 3/10-13. See also [http://2007.sxsw.com/interactive/programming/panels/ confirmed SXSWi 2007 panels].&lt;br /&gt;
* 2007-02-17 - 2007-02-18: Various microformateers were in attendance at [http://barcamp.org/BarCampLondon2 BarCampLondon] so various microformat related sessions featured. [[events/2007-02-17-barcamplondon2|Microformats at BarCampLondon]]&lt;br /&gt;
* 2007-02-07: [[events/2007-02-07-web-directions-north|microformats presentations at Web Directions North]] - 11:45am-12:45pm &amp;quot;Microformats - The Big Picture&amp;quot; with Tantek Çelik in ballroom I , 1:45pm-3:45pm: &amp;quot;Microformats - more than just promise&amp;quot; with John Allsopp and Dan Cederholm in ballroom II.&lt;br /&gt;
* 2007-02-03: [http://barcamp.org/BarCampBank3 how could we use microformats in banks ] - proposal from Christophe Ducamp (3pm-4pm) - Atelier BnpParibas 29 rue la Pérouse 75116 Paris - France (Métro Etoile)&lt;br /&gt;
* 2007-01-27: [[events/2007-01-la-get-together|Los Angeles Microformats Get Together]]&lt;br /&gt;
* 2007-01-18: [[events/2007-01-18-sf-microformats-dinner|San Francisco Microformats Dinner]] 6pm-? @ Nova on 2nd street. Details inside.&lt;br /&gt;
* 2007-01-03: [http://eventful.com/events/E0-001-002386631-6 Lancement du projet 'Cette Semaine en MicroFormats'] in Paris, France.&lt;br /&gt;
&lt;br /&gt;
==2006==&lt;br /&gt;
See [[events-2006]]&lt;br /&gt;
&lt;br /&gt;
== Quicktime Broadcaster Notes ==&lt;br /&gt;
&lt;br /&gt;
For setting up a mac laptop with an iSight and QT Broadcaster in order to publish live audio/video from events.&lt;br /&gt;
&lt;br /&gt;
# Make sure you have the necessary equipment and software installed&lt;br /&gt;
#* A Macintosh running OSX 10.3.9 or later&lt;br /&gt;
#* Quicktime 7 - get it from http://www.apple.com/quicktime/&lt;br /&gt;
#* Quicktime Broadcaster - get it from http://www.apple.com/quicktime/broadcaster/&lt;br /&gt;
#* An iSight or digital video camera with firewire connection&lt;br /&gt;
# Get a broadcast template document from someone (see KevinMarks for example)&lt;br /&gt;
# Open that, then change the info in the 'Network' pane that has his name etc in it.&lt;br /&gt;
# Check the video and audio panes are using your iSight&lt;br /&gt;
# Another tip is that the standalone thingy for the iSight can be more useful than the screen-top one if you have a desk, as that way it picks up less typing noise and wobbles&lt;br /&gt;
# I find plugging in headphones is a good idea, as you can then monitor and not get howlround&lt;br /&gt;
&lt;br /&gt;
http://microformats.org/media/broadcast.mov&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=events&amp;diff=14374</id>
		<title>events</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=events&amp;diff=14374"/>
		<updated>2007-03-18T23:35:37Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: /* Upcoming */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
=Microformats related events=&lt;br /&gt;
&lt;br /&gt;
Please add any microformats related events (specifically, events where there will be talks on microformats) you find here, and we'll add them to the [[hcalendar|hCalendar]] on the [http://microformats.org home page]. Please also create a page for each specific event, where you can list URLs for the event, event details, create an &amp;quot;Attending&amp;quot; section, link to photos afterwards, etc. (See [[events/2006-03-01-w3c-plenary-microformats|Microformats panel at W3C Plenary Day]] for a decent example to mimic/copy-paste). Thanks! -[http://tantek.com/ Tantek]&lt;br /&gt;
&lt;br /&gt;
If you can (or can ask the organisers to kindly-) use microformats (especially [[hCalendar]] and [[hCard]]) on the event's web pages, so much the better!&lt;br /&gt;
&lt;br /&gt;
There is a separate wiki page for details of [[presentations]].&lt;br /&gt;
&lt;br /&gt;
Patterns:&lt;br /&gt;
* YYYY-MM-DD: &amp;lt;nowiki&amp;gt;[[events/YYYY-MM-DD-event-session-title|Event Session Title]]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
* YYYY-MM-DD - YYYY-MM-DD: &amp;lt;nowiki&amp;gt;[[events/YYYY-MM-DD-event-session-title|Event Session Title]]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming ==&lt;br /&gt;
&amp;lt;!-- Please try to keep to neutral tense (e.g &amp;quot;Bill Smith on microformats&amp;quot; not &amp;quot;Bill Smith will talk about Microformats&amp;quot;), where possible, for convenience when moving to the historical section of this page. Please also include as many details about the event as possible, including precise start end times, room number, etc. Ideally details should be moved to the (events/..) wiki page for the event itself, but at least include the information here to start with. Thank you. --&amp;gt;&lt;br /&gt;
* 2007-03-20: [http://upcoming.org/event/161681/ Semantic London], a social gathering for people interested in microformats, SemWeb etc.&lt;br /&gt;
* 2007-03-22 [[events/2007-03-22-webDU|Microformats—the hidden treasure]] by Dmitry Baranovskiy at the[http://www.webdu.com.au/ webDU 2007] conference in Sydney, Australia &lt;br /&gt;
* 2007-04-16 [[events/2007-04-15-Web2Expo|Microformats for Web Services and Portable Content]] by Kevin Lawver at[http://www.web2expo.com/cs/webex2007/view/e_sess/11831 Web 2.0 Expo] in San Francisco.&lt;br /&gt;
* 2007-04-17 [[events/2007-04-15-Web2Expo|Microformats: Much more than just promise]] by John Allsopp, at [http://www.web2expo.com/cs/webex2007/view/e_sess/11831 Web 2.0 Expo] in San Francisco.&lt;br /&gt;
* 2007-04-18 [[events/2007-04-18-Web2ExpoDinner|Microformats Dinner]] following [http://www.web2expo.com/cs/webex2007/view/e_sess/11831 Web 2.0 Expo] in San Francisco.&lt;br /&gt;
* 2007-05-16 [[events/2007-05-16-XTech|Microformats: the nanotechnology of the semantic web]] at the [http://2007.xtech.org/ XTech 2007] conference in Paris.&lt;br /&gt;
* …&lt;br /&gt;
&lt;br /&gt;
== Recent ==&lt;br /&gt;
&amp;lt;!-- Please change to past tense, and reverse the date-order, when moving events to this section. Thank you.--&amp;gt;&lt;br /&gt;
* 2007-03-12: [[events/2007-03-12-sxsw-growth-evolution-of|The Growth and Evolution of Microformats]] at [http://2007.sxsw.com/interactive South by Southwest Interactive Festival] 2007 3/10-13. See also [http://2007.sxsw.com/interactive/programming/panels/ confirmed SXSWi 2007 panels].&lt;br /&gt;
* 2007-02-17 - 2007-02-18: Various microformateers were in attendance at [http://barcamp.org/BarCampLondon2 BarCampLondon] so various microformat related sessions featured. [[events/2007-02-17-barcamplondon2|Microformats at BarCampLondon]]&lt;br /&gt;
* 2007-02-07: [[events/2007-02-07-web-directions-north|microformats presentations at Web Directions North]] - 11:45am-12:45pm &amp;quot;Microformats - The Big Picture&amp;quot; with Tantek Çelik in ballroom I , 1:45pm-3:45pm: &amp;quot;Microformats - more than just promise&amp;quot; with John Allsopp and Dan Cederholm in ballroom II.&lt;br /&gt;
* 2007-02-03: [http://barcamp.org/BarCampBank3 how could we use microformats in banks ] - proposal from Christophe Ducamp (3pm-4pm) - Atelier BnpParibas 29 rue la Pérouse 75116 Paris - France (Métro Etoile)&lt;br /&gt;
* 2007-01-27: [[events/2007-01-la-get-together|Los Angeles Microformats Get Together]]&lt;br /&gt;
* 2007-01-18: [[events/2007-01-18-sf-microformats-dinner|San Francisco Microformats Dinner]] 6pm-? @ Nova on 2nd street. Details inside.&lt;br /&gt;
* 2007-01-03: [http://eventful.com/events/E0-001-002386631-6 Lancement du projet 'Cette Semaine en MicroFormats'] in Paris, France.&lt;br /&gt;
&lt;br /&gt;
==2006==&lt;br /&gt;
See [[events-2006]]&lt;br /&gt;
&lt;br /&gt;
== Quicktime Broadcaster Notes ==&lt;br /&gt;
&lt;br /&gt;
For setting up a mac laptop with an iSight and QT Broadcaster in order to publish live audio/video from events.&lt;br /&gt;
&lt;br /&gt;
# Make sure you have the necessary equipment and software installed&lt;br /&gt;
#* A Macintosh running OSX 10.3.9 or later&lt;br /&gt;
#* Quicktime 7 - get it from http://www.apple.com/quicktime/&lt;br /&gt;
#* Quicktime Broadcaster - get it from http://www.apple.com/quicktime/broadcaster/&lt;br /&gt;
#* An iSight or digital video camera with firewire connection&lt;br /&gt;
# Get a broadcast template document from someone (see KevinMarks for example)&lt;br /&gt;
# Open that, then change the info in the 'Network' pane that has his name etc in it.&lt;br /&gt;
# Check the video and audio panes are using your iSight&lt;br /&gt;
# Another tip is that the standalone thingy for the iSight can be more useful than the screen-top one if you have a desk, as that way it picks up less typing noise and wobbles&lt;br /&gt;
# I find plugging in headphones is a good idea, as you can then monitor and not get howlround&lt;br /&gt;
&lt;br /&gt;
http://microformats.org/media/broadcast.mov&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=events&amp;diff=14373</id>
		<title>events</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=events&amp;diff=14373"/>
		<updated>2007-03-18T23:35:14Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: /* Upcoming */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
=Microformats related events=&lt;br /&gt;
&lt;br /&gt;
Please add any microformats related events (specifically, events where there will be talks on microformats) you find here, and we'll add them to the [[hcalendar|hCalendar]] on the [http://microformats.org home page]. Please also create a page for each specific event, where you can list URLs for the event, event details, create an &amp;quot;Attending&amp;quot; section, link to photos afterwards, etc. (See [[events/2006-03-01-w3c-plenary-microformats|Microformats panel at W3C Plenary Day]] for a decent example to mimic/copy-paste). Thanks! -[http://tantek.com/ Tantek]&lt;br /&gt;
&lt;br /&gt;
If you can (or can ask the organisers to kindly-) use microformats (especially [[hCalendar]] and [[hCard]]) on the event's web pages, so much the better!&lt;br /&gt;
&lt;br /&gt;
There is a separate wiki page for details of [[presentations]].&lt;br /&gt;
&lt;br /&gt;
Patterns:&lt;br /&gt;
* YYYY-MM-DD: &amp;lt;nowiki&amp;gt;[[events/YYYY-MM-DD-event-session-title|Event Session Title]]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
* YYYY-MM-DD - YYYY-MM-DD: &amp;lt;nowiki&amp;gt;[[events/YYYY-MM-DD-event-session-title|Event Session Title]]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Upcoming ==&lt;br /&gt;
&amp;lt;!-- Please try to keep to neutral tense (e.g &amp;quot;Bill Smith on microformats&amp;quot; not &amp;quot;Bill Smith will talk about Microformats&amp;quot;), where possible, for convenience when moving to the historical section of this page. Please also include as many details about the event as possible, including precise start end times, room number, etc. Ideally details should be moved to the (events/..) wiki page for the event itself, but at least include the information here to start with. Thank you. --&amp;gt;&lt;br /&gt;
* 2007-03-20: [http://upcoming.org/event/161681/ Semantic London], a social gathering for people interested in microformats, SemWeb etc.&lt;br /&gt;
* 2007-03-22 [[events/2007-03-22-webDU|Microformats—the hidden trasure]] by Dmitry Baranovskiy at the[http://www.webdu.com.au/ webDU 2007] conference in Sydney, Australia &lt;br /&gt;
* 2007-04-16 [[events/2007-04-15-Web2Expo|Microformats for Web Services and Portable Content]] by Kevin Lawver at[http://www.web2expo.com/cs/webex2007/view/e_sess/11831 Web 2.0 Expo] in San Francisco.&lt;br /&gt;
* 2007-04-17 [[events/2007-04-15-Web2Expo|Microformats: Much more than just promise]] by John Allsopp, at [http://www.web2expo.com/cs/webex2007/view/e_sess/11831 Web 2.0 Expo] in San Francisco.&lt;br /&gt;
* 2007-04-18 [[events/2007-04-18-Web2ExpoDinner|Microformats Dinner]] following [http://www.web2expo.com/cs/webex2007/view/e_sess/11831 Web 2.0 Expo] in San Francisco.&lt;br /&gt;
* 2007-05-16 [[events/2007-05-16-XTech|Microformats: the nanotechnology of the semantic web]] at the [http://2007.xtech.org/ XTech 2007] conference in Paris.&lt;br /&gt;
* …&lt;br /&gt;
&lt;br /&gt;
== Recent ==&lt;br /&gt;
&amp;lt;!-- Please change to past tense, and reverse the date-order, when moving events to this section. Thank you.--&amp;gt;&lt;br /&gt;
* 2007-03-12: [[events/2007-03-12-sxsw-growth-evolution-of|The Growth and Evolution of Microformats]] at [http://2007.sxsw.com/interactive South by Southwest Interactive Festival] 2007 3/10-13. See also [http://2007.sxsw.com/interactive/programming/panels/ confirmed SXSWi 2007 panels].&lt;br /&gt;
* 2007-02-17 - 2007-02-18: Various microformateers were in attendance at [http://barcamp.org/BarCampLondon2 BarCampLondon] so various microformat related sessions featured. [[events/2007-02-17-barcamplondon2|Microformats at BarCampLondon]]&lt;br /&gt;
* 2007-02-07: [[events/2007-02-07-web-directions-north|microformats presentations at Web Directions North]] - 11:45am-12:45pm &amp;quot;Microformats - The Big Picture&amp;quot; with Tantek Çelik in ballroom I , 1:45pm-3:45pm: &amp;quot;Microformats - more than just promise&amp;quot; with John Allsopp and Dan Cederholm in ballroom II.&lt;br /&gt;
* 2007-02-03: [http://barcamp.org/BarCampBank3 how could we use microformats in banks ] - proposal from Christophe Ducamp (3pm-4pm) - Atelier BnpParibas 29 rue la Pérouse 75116 Paris - France (Métro Etoile)&lt;br /&gt;
* 2007-01-27: [[events/2007-01-la-get-together|Los Angeles Microformats Get Together]]&lt;br /&gt;
* 2007-01-18: [[events/2007-01-18-sf-microformats-dinner|San Francisco Microformats Dinner]] 6pm-? @ Nova on 2nd street. Details inside.&lt;br /&gt;
* 2007-01-03: [http://eventful.com/events/E0-001-002386631-6 Lancement du projet 'Cette Semaine en MicroFormats'] in Paris, France.&lt;br /&gt;
&lt;br /&gt;
==2006==&lt;br /&gt;
See [[events-2006]]&lt;br /&gt;
&lt;br /&gt;
== Quicktime Broadcaster Notes ==&lt;br /&gt;
&lt;br /&gt;
For setting up a mac laptop with an iSight and QT Broadcaster in order to publish live audio/video from events.&lt;br /&gt;
&lt;br /&gt;
# Make sure you have the necessary equipment and software installed&lt;br /&gt;
#* A Macintosh running OSX 10.3.9 or later&lt;br /&gt;
#* Quicktime 7 - get it from http://www.apple.com/quicktime/&lt;br /&gt;
#* Quicktime Broadcaster - get it from http://www.apple.com/quicktime/broadcaster/&lt;br /&gt;
#* An iSight or digital video camera with firewire connection&lt;br /&gt;
# Get a broadcast template document from someone (see KevinMarks for example)&lt;br /&gt;
# Open that, then change the info in the 'Network' pane that has his name etc in it.&lt;br /&gt;
# Check the video and audio panes are using your iSight&lt;br /&gt;
# Another tip is that the standalone thingy for the iSight can be more useful than the screen-top one if you have a desk, as that way it picks up less typing noise and wobbles&lt;br /&gt;
# I find plugging in headphones is a good idea, as you can then monitor and not get howlround&lt;br /&gt;
&lt;br /&gt;
http://microformats.org/media/broadcast.mov&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hcalendar-schedule-creator-feedback&amp;diff=32639</id>
		<title>hcalendar-schedule-creator-feedback</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hcalendar-schedule-creator-feedback&amp;diff=32639"/>
		<updated>2007-01-04T01:06:36Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: Conference Schedule Creator Feedback&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt;Conference Schedule Creator Feedback&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page is for collecting bugs, suggested fixes, and feature requests for the [http://dmitry.baranovskiy.com/work/csc/ Conference Schedule Creator]&lt;br /&gt;
&lt;br /&gt;
Please list your name, and indicate ''which'' version (even just a date and time helps) of the creator that you are providing feedback on.  Thanks!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Bug Reports ==&lt;br /&gt;
=== REGRESSIONS ===&lt;br /&gt;
Regressions are the worst kind of bug, and the top priority to fix. If you find problems in the creator that were not there in a previous version, please enter them here.&lt;br /&gt;
* bug #1 reported by Someone at 2006-07-20'&lt;br /&gt;
** clarification: &amp;quot;…&amp;quot;&lt;br /&gt;
* bug #2 reported by Someone at 2006-07-20'&lt;br /&gt;
** clarification: &amp;quot;…&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Bugs in new features ===&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
== Suggested Tweaks and Fixes ==&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Feature Requests ==&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
* [[hcalendar|hCalendar specification]]&lt;br /&gt;
* [[hcalendar-feedback|hCalendar feedback]]&lt;br /&gt;
* [[hcard-creator-feedback|hCard creator feedback]]&lt;br /&gt;
* [[hreview-creator-feedback|hReview creator feedback]]&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=Template:hcalendar-related-pages&amp;diff=12111</id>
		<title>Template:hcalendar-related-pages</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=Template:hcalendar-related-pages&amp;diff=12111"/>
		<updated>2007-01-04T01:02:17Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* [[hcalendar|hCalendar]]&lt;br /&gt;
* [[hcalendar-cheatsheet|hCalendar cheatsheet]]  - hCalendar properties&lt;br /&gt;
* [http://microformats.org/code/hcalendar/creator hCalendar creator] ([[hcalendar-creator-feedback|hCalendar feedback]]) - create your own hCalendar events.&lt;br /&gt;
* [http://dmitry.baranovskiy.com/work/csc/ Conference Schedule Creator] ([[hcalendar-schedule-creator-feedback|Conference Schedule Creator feedback]]) - create your conference schedule with hCalendar events.&lt;br /&gt;
* [[hcalendar-authoring|hCalendar authoring]] - learn how to add hCalendar markup to your existing events.&lt;br /&gt;
* [[hcalendar-examples-in-wild|hCalendar examples in the wild]] - an on-going list of websites which use hCalendars.&lt;br /&gt;
* [[hcalendar-implementations|hCalendar implementations]] - websites or tools which either generate or parse hCalendars&lt;br /&gt;
* [[hcalendar-intro]] ''draft'' '''plain English''' introduction (for use in evangelism)&lt;br /&gt;
* [[hcalendar-faq|hCalendar FAQ]] - If you have any questions about hCalendar, check here, and if you don't find answers, add your questions!&lt;br /&gt;
* [[hcalendar-parsing|hCalendar parsing]] - normative details of how to parse hCalendar.&lt;br /&gt;
* [[hcalendar-profile|hCalendar profile]] - the XMDP profile for hCalendar&lt;br /&gt;
* [[hcalendar-tests|hCalendar tests]] - a wiki page with actual embedded hCalendar events to try parsing.&lt;br /&gt;
* [[icalendar-implementations|iCalendar implementations]]&lt;br /&gt;
&lt;br /&gt;
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.&lt;br /&gt;
&lt;br /&gt;
* [[hcalendar-brainstorming|hCalendar Brainstorming]] - brainstorms and other explorations relating to hCard&lt;br /&gt;
* [[hcalendar-issues|hCalendar issues]] - issues with the specification&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=to-do&amp;diff=12173</id>
		<title>to-do</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=to-do&amp;diff=12173"/>
		<updated>2007-01-04T00:58:38Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: /* help implementers */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt;To Do&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page is for posting [[microformats]] related shared to do items.  If you want to use this page for your microformats related to-do items, create a section with your name on it.  The reason we are keeping these all on the same page is to make it easier to tell when people are working on similar things, and to make it more obvious when people help out with other people's tasks.  In theory this probably won't scale, but let's first see how it does in practice. :) - [http://tantek.com Tantek]&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Lazyweb ==&lt;br /&gt;
&lt;br /&gt;
Just some nice things, feel free to do any of these.&lt;br /&gt;
&lt;br /&gt;
=== for all microformats ===&lt;br /&gt;
* quick and easy &amp;quot;how to&amp;quot; pages for each microformat. [[use]] is a good overall start.&lt;br /&gt;
* brief summary statements for each microformat that explain why it matters, what does it accomplish for the publisher.&lt;br /&gt;
* write up [http://microformats.org/discuss/ mailing-list] questions and answers in the appropriate [[faq]] pages.&lt;br /&gt;
* validators.  See the hReview section below as there has been a request for an hReview validator in particular. See [http://norman.walsh.name/2006/04/13/validatingMicroformats Norman Walsh's blog post &amp;quot;Validating microformats&amp;quot;] for some valuable analysis and validation pseudo-code (prose description), which are useful steps towards building microformat validators.&lt;br /&gt;
* Create a microformat (based on hCalendar?) for marking up the opening hours of stores and restaurants. Some people seem to believe hCalenders repeating event support isn't good enough for this and needs to be amended first.&lt;br /&gt;
&lt;br /&gt;
=== hReview ===&lt;br /&gt;
* [[hreview|hReview]] support in Ecto (hey Adriaan!), requested by Andy Smith&lt;br /&gt;
* an [[hreview|hReview]] validator.&lt;br /&gt;
* a semantic, clean css star rating picker (e.g. a UI widget to rate from 1-5 stars)&lt;br /&gt;
** both [http://komodomedia.com/blog/index.php/2005/08/24/creating-a-star-rater-using-css/ this] and [http://factorycity.net/demos/drupal/rating/default.html this] have some flaws. Ask [[User:RyanKing|Ryan King]] for an explanation.&lt;br /&gt;
&lt;br /&gt;
=== hCard ===&lt;br /&gt;
* microformatted versions of conference pages&lt;br /&gt;
** Do a revision of the [http://conferences.oreillynet.com/etel2006/ ETel] [http://conferences.oreillynet.com/pub/w/44/speakers.html speaker's page] with all the speakers marked up with [[hcard|hCard]] and links to &amp;quot;Add hCards to Address Book&amp;quot; etc., similar to the [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 speakers page which Tantek did a revision of last fall].&lt;br /&gt;
* vcard to hcard converter&lt;br /&gt;
** would be nice to have a web upload UI that would take one or more vCards from apple's address book and give them back to you as hCards&lt;br /&gt;
** [[User:RobertBachmann | RobertBachmann]] suggests starting points:&lt;br /&gt;
*** For Ruby: http://vpim.rubyforge.org/ &lt;br /&gt;
*** For C: http://freshmeat.net/projects/libvc/&lt;br /&gt;
*** For Python: http://www.nongnu.org/python-pdi/&lt;br /&gt;
*** For PHP: http://pear.php.net/package/Contact_Vcard_Parse/&lt;br /&gt;
* add export support for microformats to [http://www.turingart.com/abForWeb_lan__en.htm AB to Web]&lt;br /&gt;
* A mash-up with google maps that will take any url with a hcard (or hcard's) and map the location(s) on a map (similar to [http://austin.adactio.com/ austin.adactio.com])&lt;br /&gt;
&lt;br /&gt;
=== hCalendar/hCard/hReview editor ===&lt;br /&gt;
* onblur in the URL field (e.g. on hCalendar), goes out and tries to retrieve an object of same time (e.g. an hCalendar vevent) from that URL and uses it to autofill the form, same thing if the creator is loaded with that URL prefilled (e.g. due to a ?url=http://example.com/ in the URL that loads the creator).&lt;br /&gt;
&lt;br /&gt;
=== WordPress patches for microformats ===&lt;br /&gt;
* submit patches for WordPress code/templates for microformats improvement&lt;br /&gt;
** &amp;amp;lt;address class=&amp;quot;vcard&amp;quot;&amp;amp;gt; improvement in post author publication (e.g. home page of http://microformats.org/ )&lt;br /&gt;
* Wordpress plugin for microformats, specifically hReview and hCalendar&lt;br /&gt;
** See [http://www.surfarama.com/index.php?p=227 lazyweb request]&lt;br /&gt;
&lt;br /&gt;
=== Yahoo Open Source Library Patches ===&lt;br /&gt;
&lt;br /&gt;
Several of these could very much be improved with a little microformats markup.  Do we just make patches and submit them?  Contact Nate Koechley at Yahoo (see Tantek for contact info) to follow-up.&lt;br /&gt;
&lt;br /&gt;
* [http://developer.yahoo.net/yui/ Yahoo! User Interface Library]&lt;br /&gt;
* [http://developer.yahoo.net/ypatterns/ Yahoo! Design Patterns Library]&lt;br /&gt;
* [http://www.yuiblog.com Yahoo! User Interface Blog]&lt;br /&gt;
&lt;br /&gt;
=== Drupal patches for microformats ===&lt;br /&gt;
* [http://groups.drupal.org/microformats-in-drupal Microformat Module for Drupal] A group discussing ways to implement microformats in Drupal.  Currently looking to support hAtom, hCard and hCalendar to start with.  Contact digitalspaghetti at gmail dot com if you are interested in contributing to the project.&lt;br /&gt;
&lt;br /&gt;
=== Adding Microformats to Existing Pages ===&lt;br /&gt;
&lt;br /&gt;
* See [[advocacy#Adding_Microformats_to_Existing_Sites|advocacy: Adding microformats to existing sites]].&lt;br /&gt;
&lt;br /&gt;
===Geotagging on Wikipedia===&lt;br /&gt;
Somebody familiar with the &amp;quot;geo&amp;quot; microformat might want to add details, and a link to the relevant page on this Wiki, to the [http://en.wikipedia.org/wiki/Geotagging Wikipedia page on Geotagging]. [[User:AndyMabbett|Andy Mabbett]]&lt;br /&gt;
&lt;br /&gt;
===rel-tagging on Wikipedia===&lt;br /&gt;
Somebody familiar with the &amp;quot;rel-tag&amp;quot; microformat might want to add details, and a link to the relevant page on this Wiki, to the [http://en.wikipedia.org/wiki/Tag_%28metadata%29 Wikipedia page on tagging]. [[User:AndyMabbett|Andy Mabbett]] 14:07, 3 Jan 2007 (PST)&lt;br /&gt;
&lt;br /&gt;
== Tantek ==&lt;br /&gt;
&lt;br /&gt;
I'm keeping a few microformats related to-do items here both for my own convenience, and for folks looking to help out with small tasks.  If so, just create a new section with your name, and and maybe copy the item there, and put your name next to the item in my list.  We'll figure this out as we go along.  Thanks,  [http://tantek.com Tantek].&lt;br /&gt;
&lt;br /&gt;
=== overall priority ordering ===&lt;br /&gt;
# Protect the community from threats (wiki damage, mailing list pain or noise), repair damage, add measures to reduce future damage&lt;br /&gt;
# Help publishers with established microformats: [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]&lt;br /&gt;
# Help implementers with established microformats&lt;br /&gt;
# Wiki cleanup/gardening for existing established microformats&lt;br /&gt;
# Site usability&lt;br /&gt;
# Iterate on existing established microformats, resolve issues/feedback etc.&lt;br /&gt;
# Community dynamics, [[process]] and [[principles]] improvements to help guide new microformats developments&lt;br /&gt;
# Emerging in-demand microformats: [[hlisting|hListing]], [[citation]] using abovementioned process and principles improvements.&lt;br /&gt;
# New microformat requests&lt;br /&gt;
# Other&lt;br /&gt;
&lt;br /&gt;
=== protect the community ===&lt;br /&gt;
* Analyze [[Special:Recentchanges]] and [http://microformats.org/discuss mailing-lists] and:&lt;br /&gt;
** add to [[mailing-lists]] policies/guidelines accordingly.&lt;br /&gt;
** privately email violaters kindly asking them to improve their behavior&lt;br /&gt;
** work with admins on next steps for individuals negatively impacting the community&lt;br /&gt;
** recognize noisy/distracting threads on the email list, document responses/answers to such subjects on the appropriate page(s) on the wiki, and reply to those threads with the URLs to the documentation on the wiki. Putting the responses/answers on the wiki helps by hopefully providing preemptive answers to some who might reraise the subjects on the list in the future, and helps the community quickly terminate such threads by using the answers on the wiki.&lt;br /&gt;
&lt;br /&gt;
=== help publishers ===&lt;br /&gt;
* (: [[advocacy]] - add pages/sites that could use microformats, update them with sample markup, find contacts for those pages to get them updated, and send requests to update their sites with microformats including sample markup.&lt;br /&gt;
&lt;br /&gt;
==== *-authoring microformats wiki pages ====&lt;br /&gt;
* Add some tips to [[hcard-authoring]]&lt;br /&gt;
** a tutorial on creating an hCard for your site&lt;br /&gt;
** specific instructions for common blogging platforms&lt;br /&gt;
** instructions for more properties (match at least the set that is in the [http://microformats.org/code/hcard/creator hCard creator])&lt;br /&gt;
* Create [[hreview-authoring]] - a tutorial on how to blog reviews so that they'll be aggregated.&lt;br /&gt;
&lt;br /&gt;
* *-authoring for all microformats: [[hcalendar-authoring]], [[hreview-authoring]], [[xfolk-authoring]], [[hatom-authoring]]&lt;br /&gt;
&lt;br /&gt;
==== help with microformat examples in the wild ====&lt;br /&gt;
Go over all &amp;quot;common&amp;quot; pages (both logged out and logged in states) of the following sites which have some microformats already, and verify each page is as microformatted as it can be with high fidelity [[hcalendar|hCalendar]] and [[hcard|hCard]] etc.  Document full support of each implementation's microformats on the implementations page (perhaps create a separate page for each implementation, e.g. [[flickr]], [[upcoming]], [[eventful]] etc.) Document any exceptions as needed.  In no particular order:&lt;br /&gt;
* Flickr.com (3.5m hCards)&lt;br /&gt;
* Upcoming.org (100k hCalendar events, 100k hCard venues)&lt;br /&gt;
** home page&lt;br /&gt;
* Eventful.com (100k hCalendar events, 100k hCard venues)&lt;br /&gt;
* Yahoo! Tech (300k products with hReviews)&lt;br /&gt;
* JudysBook.com (???k hReviews)&lt;br /&gt;
* ... lots more, get from &amp;quot;Implementations&amp;quot; and &amp;quot;Examples in the Wild&amp;quot; sections of specs.&lt;br /&gt;
&lt;br /&gt;
=== help implementers ===&lt;br /&gt;
* wordpress improvements&lt;br /&gt;
** WP admin for new profiles&lt;br /&gt;
*** should simply read blog URL&lt;br /&gt;
*** look for hcards and parse them&lt;br /&gt;
* [http://gmpg.org/xfn/creator XFN Creator] localizations&lt;br /&gt;
** Get someone to verify the [http://gmpg.org/xfn/creator-ru XFN Creator Russian localization].&lt;br /&gt;
** Add it to the [http://gmpg.org/xfn/tools XFN Tools] page.&lt;br /&gt;
** Add rel=&amp;quot;alternate&amp;quot; href=&amp;quot;creator-ru&amp;quot; &amp;amp;lt;link&amp;amp;gt;s to the other XFN Creators.&lt;br /&gt;
* Conference Schedule Creator&lt;br /&gt;
** We need to ASAP build a simple conference schedule creator (and editor?) that builds upon the hCalendar creator. We should make it *trivial* for conference organizers to build/edit/publish an [[hcalendar|hCalendar]] schedule for their conference, including auto-generated &amp;quot;Subscribe...&amp;quot; link which produces the proper &amp;quot;webcal:...&amp;quot; link with X2V.  Note: see the &amp;quot;axis&amp;quot; and &amp;quot;header&amp;quot; attributes in HTML4, specifically in the section on Tables. (Done. Feedback wanted. [http://dmitry.baranovskiy.com/work/csc/ Conference Schedule Creator])&lt;br /&gt;
&lt;br /&gt;
=== wiki cleanup ===&lt;br /&gt;
==== for all microformat specs ====&lt;br /&gt;
* modularize any specs which are &amp;gt; 30K in order to avoid loss/corruption like [http://microformats.org/wiki?title=Special:Contributions&amp;amp;target=Evan Evan's 14 June edits] to [[hcard|hCard]], [[rel-tag]], and [[xoxo|XOXO]].&lt;br /&gt;
** [[hcard|hCard]] -&lt;br /&gt;
*** [[hcard-examples-in-the-wild]] group/sort by individuals,  organizations, and hosting sites. Consider moving largest subsection to its own page as well.&lt;br /&gt;
** [[rel-tag]]&lt;br /&gt;
** [[xoxo]]&lt;br /&gt;
&lt;br /&gt;
==== update specification section organization ====&lt;br /&gt;
In particular, the introduction/boilerplate/headers.  [[hresume|hResume]] has an experimental abbreviated intro/headers section, and links to more details further below, based on some ideas that Ryan King and I had for improving the readability of the microformats specifications. [[hreview|hReview]] has some similar improvements, but different.  We need to:&lt;br /&gt;
# Figure out if the new intro/headers structure in [[hresume|hResume]] and/or [[hreview|hReview]] is an improvement, and if it could be better.  Perhaps figure out the requirements for an intro/header section&lt;br /&gt;
#* Shorter tends to be better&lt;br /&gt;
#* Must be comprehensive enough to &amp;quot;print and read&amp;quot;&lt;br /&gt;
#* Must detail authorship/editorship&lt;br /&gt;
#* Must detail copyright/patent statements&lt;br /&gt;
# Write up a template - make it self-documenting per the requirements&lt;br /&gt;
# Update existing specifications with the new intro/headers structure.&lt;br /&gt;
## [[hcard|hCard]]&lt;br /&gt;
## [[hcalendar|hCalendar]]&lt;br /&gt;
## [[hreview|hReview]]&lt;br /&gt;
&lt;br /&gt;
==== reorganizing Implementations sections ====&lt;br /&gt;
* sort implementations by authoring/creating/publishing, browsing/viewing, converting/importing, indexing/searching.&lt;br /&gt;
&lt;br /&gt;
Hmmm... I like: '''A'''uthoring, '''B'''rowsing, '''C'''onverting, '''I'''ndexing, '''L'''ibraries (for developers), and '''P'''otential (for open source projects we want to add support to).  Anybody have alternative suggestions for this vocabulary?  I don't have a particularly strong preference so I'm going to go with these four until I find examples that don't fit, or someone suggests something better.&lt;br /&gt;
&lt;br /&gt;
See: [http://microformats.org/wiki/hcalendar#Implementations hCalendar Implementations] for a first attempt at this.  Assuming folks like that, we can go ahead with categorizing the implementations sections of other microformats specifications.&lt;br /&gt;
&lt;br /&gt;
* [[hcard-implementations]] - organize by same subsections as [[hcalendar-implementations]].&lt;br /&gt;
&lt;br /&gt;
==== reorg Examples in the Wild sections ====&lt;br /&gt;
* include more *key* details per example, e.g. precise or estimates of counts for services&lt;br /&gt;
* collate/sort examples in the wild by &lt;br /&gt;
** hosting services - where users/people actively contribute to the growth (e.g. Flickr profile hCards)&lt;br /&gt;
** publishing services - where lots of data is published from some datasource/database (e.g. Yahoo! Local)&lt;br /&gt;
** companies/groups/organizations member pages (and their own) - pages for a group's site where they list members or employees (e.g. Technorati staff page)&lt;br /&gt;
** individiual companies/organizations contact info pages&lt;br /&gt;
** individual people's contact info pages&lt;br /&gt;
* of course at some point this won't scale, but that will be a very good problem to have, and by then I'm sure we'll have services to point to that provide queries and search results for all this data.&lt;br /&gt;
&lt;br /&gt;
=== site usability ===&lt;br /&gt;
* figure out how to get wordpress to autopost blog posts to the microformats-announce list&lt;br /&gt;
** ideally use the from address of the author of the blog post&lt;br /&gt;
** maybe photomatt knows how to do this.&lt;br /&gt;
&lt;br /&gt;
=== iterate on current microformats ===&lt;br /&gt;
==== [[hcard|hCard]] ====&lt;br /&gt;
* [[hcard-examples]]&lt;br /&gt;
** add examples of [[hcard|hCard]]s with work telephone, mailing address etc.&lt;br /&gt;
** add examples of marking up an organization vs. a person, then link to it from [http://microformats.org/wiki/hcard#Organization_Contact_Info hCard spec section on Organization Contact Info].&lt;br /&gt;
** add example of organization-name and organization-unit usage.&lt;br /&gt;
* Examples in the wild - need to create a new page for them!&lt;br /&gt;
** Group examples in the wild according to:&lt;br /&gt;
*** Individuals - one card per person, perhaps sort alphabetically&lt;br /&gt;
*** Organizations - one card per organization, alphabetical again&lt;br /&gt;
*** Institutions (which list more than one person), with a count estimating the # of hCards, e.g. 40k for Avon. Also indicate complexity of information supplied, eg. just name+number vs. complete details&lt;br /&gt;
*** Online Profiles (which host profiles for more than one person) with a count estimating the # of hCards, e.g. 3.5m for Flickr.com&lt;br /&gt;
*** Online Venues (which provide listings for businesses or organizations) with a count estimating the # of venues, e.g. ~10k for Upcoming.org&lt;br /&gt;
*** Speakers Listings (lists of speakers on conference sites) with a count estimating the # of speakers, e.g. ~300 for SXSW 2006.&lt;br /&gt;
** help dglazkov markup: http://glazkov.com/blog/archive/2003/12/17/147.aspx&lt;br /&gt;
&lt;br /&gt;
==== [[hcalendar|hCalendar]] ====&lt;br /&gt;
* re-add a list of properties per the [[hcard#Property_List|hCard property list]].&lt;br /&gt;
* formalize [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]&lt;br /&gt;
* flesh out [[hcalendar-examples]] and do a once over on markup/presentation of what RFC2445 examples would look like&lt;br /&gt;
* need spec details and then [[hcalendar-examples]] of multi-instance [[hcalendar|hCalendar]] events&lt;br /&gt;
* need spec details and then [[hcalendar-examples]] of repeating events&lt;br /&gt;
* add explicit explanation and examples for LOCATION [[hcard|hCards]] and ATTENDEE [[hcard|hCards]], perhaps on a separate [[hcalendar-examples]] page.&lt;br /&gt;
* need to resolve all outstanding [[hcalendar-issues]] to-do items.&lt;br /&gt;
* create [[hcalendar-profile]] and have folks verify it.  note that it will likely need reconciliation with the [[hcard-profile]], especially since [[hcalendar|hCalendar]] normatively depends on [[hcard|hCard]].  Probably makes sense to have a combined profile which hCalendar would use.&lt;br /&gt;
&lt;br /&gt;
==== [[hreview|hReview]] ====&lt;br /&gt;
* Write hReview 0.3 XMDP profile, and reconcile with [[hcalendar-profile]] and [[hcard-profile]].  Makes sense to have a combined profile of all three for hReview, since hReview normatively depends on hCard and hCalendar.&lt;br /&gt;
&lt;br /&gt;
==== summary Examples in the Wild page ====&lt;br /&gt;
* need to create a summary / overall [[examples-in-the-wild]] page &lt;br /&gt;
** parallel the summary/overall [[implementations]] page.&lt;br /&gt;
** use newly reoganized content from the above &amp;quot;reoganizing Examples in the Wild&amp;quot; task&lt;br /&gt;
&lt;br /&gt;
==== parsing ====&lt;br /&gt;
* *-parsing for all microformats: [[hcalendar-parsing]], [[hreview-parsing]], [[xfolk-parsing]], [[hatom-parsing]]&lt;br /&gt;
&lt;br /&gt;
=== introduction / community ===&lt;br /&gt;
* microformats-discuss&lt;br /&gt;
** introductory email template for new subscribers needs to direct people to [[process]] and [[how-to-play]]&lt;br /&gt;
* Need to add more to the [[naming-principles]], to cover in particular:&lt;br /&gt;
** avoid using the same name to mean two things&lt;br /&gt;
** avoid using two names to mean the same thing&lt;br /&gt;
** seek to keep the microformats vocabulary minimal, memorable, and usable.&lt;br /&gt;
* update and add details/simplifications to [[process]] given the past several months of experience. in particular:&lt;br /&gt;
** clarify requirement (MUST rather than SHOULD) of *-examples, *-formats, before any *-brainstorming.  &lt;br /&gt;
** Add details of encouragement to experiment with simple semantic class names from *-brainstorming proposals to gain real world experience with real world content.&lt;br /&gt;
** note SHOULD prerequisite of use of all relevant microformats on real world web pages, along with documenting such use in respective &amp;quot;Examples in the Wild&amp;quot; sections, before proposing any new microformats.&lt;br /&gt;
&lt;br /&gt;
==== principles and process ====&lt;br /&gt;
Create the following pages and document/fill them with content from other pages, email lists, and [[presentations]].&lt;br /&gt;
* [[principles]] - mostly [[microformats#the_microformats_principles|documented in the microformats]] page.&lt;br /&gt;
* clearer statement of both copyright and patents both in specific specs and in general&lt;br /&gt;
&lt;br /&gt;
==== profiles ====&lt;br /&gt;
* update XMDP with new required features:&lt;br /&gt;
** ability for one profile to include/import another (rel=&amp;quot;import&amp;quot; ?)&lt;br /&gt;
** ability to reference an XMDP via rel=&amp;quot;profile&amp;quot; (similar to XHTML2 rel value by same name)&lt;br /&gt;
** ability/suggestion to reference an XMDP using &amp;amp;lt;a href&amp;amp;gt; in addition to &amp;amp;lt;link&amp;amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== community mark ====&lt;br /&gt;
* Can we make &amp;quot;microformat&amp;quot; and &amp;quot;microformats&amp;quot; into [http://factoryjoe.com/blog/2006/01/14/the-case-for-community-marks/ Community Marks]?&lt;br /&gt;
&lt;br /&gt;
==== document issue resolutions ====&lt;br /&gt;
* Prefixing has already been considered and rejected for microformats in general.  Note [[naming-conventions]], limited vocabulary, and exceptions made for [[hatom|hAtom]] and how we went about doing so.&lt;br /&gt;
&lt;br /&gt;
=== emerging microformats ===&lt;br /&gt;
* [[citation]]&lt;br /&gt;
* [[hlisting|hListing]]&lt;br /&gt;
* [[media-info]]&lt;br /&gt;
* [[licensing]]&lt;br /&gt;
&lt;br /&gt;
=== new microformat requests ===&lt;br /&gt;
* expense reports (really just a list of &amp;quot;expense&amp;quot; items), [http://flickr.com/photos/edyson/56774178/ requested by ED], should look at UBL as a pre-existing format&lt;br /&gt;
* photo-notes microformat&lt;br /&gt;
** clean up Subethaedit notes from working session with Greg Elin, Ryan King, Kevin Marks, Suw Charman and email to folks and figure out next steps&lt;br /&gt;
** iterate on [[photo-note-examples]] and start [[photo-note-formats]] and [[photo-note-brainstorming]].&lt;br /&gt;
&lt;br /&gt;
=== other ===&lt;br /&gt;
* Add XPath equivalents where appropriate in [[hcard-parsing]]&lt;br /&gt;
&lt;br /&gt;
==Ryan==&lt;br /&gt;
=== wiki cleanup ===&lt;br /&gt;
* possibly move dead proposals off of homepage?&lt;br /&gt;
&lt;br /&gt;
=== hCalendar/hCard/hReview creator improvements ===&lt;br /&gt;
* get all creators working in IE/Win, IE/Mac, Safari/OSX.3&lt;br /&gt;
&lt;br /&gt;
=== other ===&lt;br /&gt;
* add an example of how to use DURATION in hcalendar see http://www.policyawareweb.org/2005/ftf2/paw-mtg#item15) -&amp;gt; verify http://svn.lifelint.com/hcalendar_tests/calendar-todo-multiple-attendees-and-alarm.xml&lt;br /&gt;
&lt;br /&gt;
=== rel-payment ===&lt;br /&gt;
* update rel-payment to reference the IANA registry [http://www1.ietf.org/mail-archive/web/ietf-announce/current/msg02055.html]&lt;br /&gt;
&lt;br /&gt;
=== hcalendar ===&lt;br /&gt;
* make sure we explicitly disallow 'vjournal'&lt;br /&gt;
&lt;br /&gt;
== Dimitri Glazkov ==&lt;br /&gt;
&lt;br /&gt;
* Figure out REST/Microformats thing&lt;br /&gt;
* Work on result set idea&lt;br /&gt;
* Implement h-creators using Web Forms 2.0&lt;br /&gt;
&lt;br /&gt;
== Chris Messina ==&lt;br /&gt;
&lt;br /&gt;
=== General ===&lt;br /&gt;
&lt;br /&gt;
* Work on a microformat for play-lists (is it just a XOXO ordererd list of play-items?)&lt;br /&gt;
* Work on a microformat for play-item (take a look at [[media-info-examples]])&lt;br /&gt;
* Work on microformats tutorial for designers&lt;br /&gt;
* Add support for OpenID to micformats wiki&lt;br /&gt;
&lt;br /&gt;
=== Campaigns ===&lt;br /&gt;
&lt;br /&gt;
* Get Blogger to support hAtom and hCard&lt;br /&gt;
* &amp;lt;strike&amp;gt;Get LinkedIn to support hCard, hResume, hCalendar&amp;lt;/strike&amp;gt; and XFN&lt;br /&gt;
* Get XING to support &amp;lt;strike&amp;gt;hCard&amp;lt;/strike&amp;gt;, hCalendar, hResume and XFN&lt;br /&gt;
* Get Digg to support microformats.&lt;br /&gt;
&lt;br /&gt;
=== Wishlist ===&lt;br /&gt;
&lt;br /&gt;
* Microformat for &amp;quot;buyable items&amp;quot; (see [[listing-examples]] and related documents)&lt;br /&gt;
* Location MF -- right click &amp;quot;map this&amp;quot; (see [[geo]] and [[adr]])&lt;br /&gt;
* Better hCard support in the browser -- right click &amp;quot;IM this person...&amp;quot;, &amp;quot;Add to contacts&amp;quot; (see [http://factoryjoe.com/blog/2006/03/20/flocktails-for-flock/  Flocktails])&lt;br /&gt;
* Better hCal support -- support many views of same hCal data on one page using XSLT&lt;br /&gt;
* We need something that a designer/web programmer can come to and leave w/ 2 examples of each microformat that they can apply right away... a &amp;quot;microformats styleguide for designers&amp;quot;, if you will.&lt;br /&gt;
* invoicing microformat&lt;br /&gt;
* better microformats wiki theme&lt;br /&gt;
&lt;br /&gt;
== Robert Bachmann ==&lt;br /&gt;
&lt;br /&gt;
=== hCard Creator ===&lt;br /&gt;
* [http://microformats.org/code/hcard/creator hCard creator] - add features/fields&lt;br /&gt;
** aim / instant messaging contact info, using the techniques documented in [[hcard-examples#New_Types_of_Contact_Info|hCard Examples: New Types of Contact Info]]&lt;br /&gt;
*** consider a popup menu for the IM service (AIM|Yahoo|...), and a field next to it for the IM id.&lt;br /&gt;
&lt;br /&gt;
=== hAtom2Atom ===&lt;br /&gt;
&lt;br /&gt;
Some ideas for features which could be implemented :&lt;br /&gt;
&lt;br /&gt;
(If you are interested in one of this features, add &amp;quot;&amp;lt;i&amp;gt;+1 Your Name&amp;lt;/i&amp;gt;&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
Join all hfeed's inside a page (or a fragment thereof) into one feed using [http://greenbytes.de/tech/webdav/rfc4287.html#element.source atom:source] semantics.&lt;br /&gt;
&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;&lt;br /&gt;
Extraction of &amp;lt;code&amp;gt;atom:content&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;atom:summary&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;atom:title&amp;lt;/code&amp;gt;:&lt;br /&gt;
* &amp;lt;code&amp;gt;atom:content&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;atom:summary&amp;lt;/code&amp;gt; as HTML &lt;br /&gt;
* &amp;lt;code&amp;gt;atom:content&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;atom:summary&amp;lt;/code&amp;gt; as plain-text&lt;br /&gt;
* &amp;lt;code&amp;gt;atom:title&amp;lt;/code&amp;gt; as XHTML&lt;br /&gt;
* &amp;lt;code&amp;gt;atom:title&amp;lt;/code&amp;gt; as HTML&lt;br /&gt;
&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Support for other XSLT engines:&lt;br /&gt;
* MSXML&lt;br /&gt;
* .Net System.Xml&lt;br /&gt;
* Sablotron&lt;br /&gt;
* Oracle XSLT&lt;br /&gt;
* XT&lt;br /&gt;
* hAtom2Atom written using XSL 2.0?&lt;br /&gt;
** Do you think this would be useful? I have created a barebones version, doesn't yet take in all the parsing rules yet, but I'd be happy to share.  Moving to XSL 2.0 does make things a bit cleaner and more efficient. - Matt Dertinger.&lt;br /&gt;
&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Support for other output formats: (hAtom2&amp;lt;i&amp;gt;xyz&amp;lt;/i&amp;gt;.xsl)&lt;br /&gt;
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl]) -- &amp;lt;i&amp;gt;+1 Matt Dertinger&amp;lt;/i&amp;gt;&lt;br /&gt;
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt]) -- &amp;lt;i&amp;gt;+1 Matt Dertinger&amp;lt;/i&amp;gt;&lt;br /&gt;
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])-- &amp;lt;i&amp;gt;+1 Matt Dertinger&amp;lt;/i&amp;gt;&lt;br /&gt;
* JSON?&lt;br /&gt;
** Does it make sense to consider a canonical representation of microformats (either case by case, or in general) in JSON?  E.g. so that a JSON API that returned contact information could return an hCard-equivalent chunk of JSON. - Tantek.&lt;br /&gt;
&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
([[User:Singpolyma|singpolyma]] 01:02, 9 May 2006 (PDT) -- Not XSLT, but see http://xoxotools.ning.com/hatom2rss.php for hatom to RSS2.0 conversion)&lt;br /&gt;
&lt;br /&gt;
== Brian Suda ==&lt;br /&gt;
=== Citation Microformats ===&lt;br /&gt;
* Add all my notes to the Wiki&lt;br /&gt;
* Start the process of naming the properties using existing names&lt;br /&gt;
&lt;br /&gt;
=== X2V ===&lt;br /&gt;
Make changes and update site (almost stable)&lt;br /&gt;
Get ATTENDEE and other strange attributes working&lt;br /&gt;
==== WARNINGS and ERROR ====&lt;br /&gt;
work on the warnings and error output for the pre-check in X2V&lt;br /&gt;
&lt;br /&gt;
=== FAQ ===&lt;br /&gt;
* clean-up the MF FAQs&lt;br /&gt;
* clean-up FAQs from the major microformats&lt;br /&gt;
* pull Questions from the mailing list and document them to the FAQs and example&lt;br /&gt;
&lt;br /&gt;
== Mark Rickerby ==&lt;br /&gt;
&lt;br /&gt;
=== Current Tasks ===&lt;br /&gt;
&lt;br /&gt;
* Follow up on usability review&lt;br /&gt;
** Edits to homepage feature box text &lt;br /&gt;
** Draft of [[getting-started]] page&lt;br /&gt;
* Review content for new pages - [[start-simple]], [[modularity]], [[reuse]], [[humans-first]]&lt;br /&gt;
* xoxo datatype examples&lt;br /&gt;
** test case lists&lt;br /&gt;
** transmitting key/value lists&lt;br /&gt;
* practical feedback on hresume&lt;br /&gt;
&lt;br /&gt;
=== Wishlist ===&lt;br /&gt;
&lt;br /&gt;
* hmmm&lt;br /&gt;
&lt;br /&gt;
== Ernest Prabhakar ==&lt;br /&gt;
=== Wiki-Thon Proposal ===&lt;br /&gt;
Set aside several hours (probably a Friday night US PST) for focused work on the Wiki, including both physical (e.g., a room in the Bay Area) and virtual (IRC/iChat) participants.&lt;br /&gt;
&lt;br /&gt;
==== Goals ====&lt;br /&gt;
# Improve understanding of what needs to be done for Wiki&lt;br /&gt;
#* IMHO - this should be done here, in [[to-do]] incrementally. -Tantek&lt;br /&gt;
# Tackle larger projects (~1-2 hours) than people usually have time for&lt;br /&gt;
#* I'd like to see these projects *documented* first on [[to-do]] before we spend 1-2 hours of a bunch of folk's collective time to go through them. -Tantek&lt;br /&gt;
# Motivate community to have fun with otherwise tedious &amp;quot;housecleaning&amp;quot; chores&lt;br /&gt;
&lt;br /&gt;
==== Agenda (Wishlist) ====&lt;br /&gt;
In parallel:&lt;br /&gt;
* Coalesce/prioritize existing To-Do items (above)&lt;br /&gt;
* Review/revise desired pathways for:&lt;br /&gt;
** New users learning about microformats&lt;br /&gt;
*** e.g., intro, about, explore, tutorials, etc.&lt;br /&gt;
*** cf. [http://www.rubyonrails.com/ Rails] front page&lt;br /&gt;
****Get Excited (Why, background, motivation)&lt;br /&gt;
****Get Started (What, downloads, getting started)&lt;br /&gt;
****Get Better (How, tutorials, )&lt;br /&gt;
****Get Involved (Who)&lt;br /&gt;
** Microformat lifecycle&lt;br /&gt;
*** e.g., research-&amp;gt;brainstorm-&amp;gt;proposal-&amp;gt;spec-&amp;gt;maintain&lt;br /&gt;
*** see http://theryanking.com/microformats/method.txt --[[User:RyanKing|RyanKing]] 15:35, 22 Feb 2006 (PST)&lt;br /&gt;
*** ensure information easy to find, follow, and up-to-date&lt;br /&gt;
* Review existing specs for completeness and consistency&lt;br /&gt;
* Identify areas of 'bitrot' or 'hole-filling'&lt;br /&gt;
* Do it!&lt;br /&gt;
&lt;br /&gt;
== Dan Connolly ==&lt;br /&gt;
&lt;br /&gt;
[[User:DanC|DanC]] hopes to sync up on these tasks in [[irc]] roughly&lt;br /&gt;
weekly, during Wednesday afternoon (Chicago time) &amp;quot;office hours&amp;quot;. See also my [http://esw.w3.org/topic/DanConnolly esw todo list and someday pile].&lt;br /&gt;
&lt;br /&gt;
* from SxSW in Austin&lt;br /&gt;
** build a combined hcalendar/hcard profile; resolve issues in [[profile-uris]].&lt;br /&gt;
*** with XSLT transformation to RDF&lt;br /&gt;
** finish [[hcard-tests]]&lt;br /&gt;
*** figure out [[include-pattern]] boundaries&lt;br /&gt;
&lt;br /&gt;
* Medium term&lt;br /&gt;
** sync [[hcalendar-tests]] and [http://www.w3.org/2002/12/cal/ RDF calendar] tests and CALSIFY&lt;br /&gt;
*** reconsider RDF calendar naming conventions&lt;br /&gt;
** update my CV/resume using [[hResume]] and [[citation-formats]]&lt;br /&gt;
*** get an answer from the CALSIFY WG re [http://lists.w3.org/Archives/Public/www-rdf-calendar/2006Apr/0006.html dtstart and date vs datetime ] 21 Apr 2006&lt;br /&gt;
*** refine [[hatom]] so that it's suitable for the workflow around the W3C homepage.&lt;br /&gt;
&lt;br /&gt;
* from WWW2006&lt;br /&gt;
** follow up on GRDDL as escape valve for microformats proposals, much like CSS was an escape valve for HTML tag proposals.&lt;br /&gt;
&lt;br /&gt;
* Someday pile&lt;br /&gt;
** set up a timezone registry based on wikipedia and semantic mediawiki. As discussed in [[datetime-design-pattern]], iCalendar's by-value timezone passing is broken. see [http://lists.w3.org/Archives/Public/www-rdf-calendar/2006Apr/0002.html reconsidering timezones in light of hCalendar and CALSIFY] and [http://dig.csail.mit.edu/breadcrumbs/node/91 Toward Semantic Web data from Wikipedia]&lt;br /&gt;
** noodle on a playlist format and some of the media RSS stuff like [[media-info-brainstorming]],  [[media-metadata-examples]] (re playlists: XSPF, SMIL, RDF, and microformats 9 Sep 2005)&lt;br /&gt;
** check out that hReview bug stuff...&lt;br /&gt;
** noodle on [[meeting-minutes-brainstorming]] and [http://esw.w3.org/topic/MeetingRecords MeetingRecords in the esw wiki].&lt;br /&gt;
** noodle on clipboard scenarios, esp how RDFa works in the general case but isn't as author-friendly as domain-specific syntaxes.&lt;br /&gt;
&lt;br /&gt;
[[User:DanC|DanC]] 15:39, 31 May 2006 (PDT)&lt;br /&gt;
&lt;br /&gt;
== Chris Casciano ==&lt;br /&gt;
&lt;br /&gt;
[[User:ChrisCasciano|ChrisCasciano]] &lt;br /&gt;
&lt;br /&gt;
* get around to updating [[hatom-issues]] with some multi feed rules/exceptions.&lt;br /&gt;
* &amp;lt;del&amp;gt;Update textpattern plugin with simple hreview support and get a new release out&amp;lt;/del&amp;gt;&lt;br /&gt;
* Redesign placenamehere.com and include hatom&lt;br /&gt;
* Follow up with technorati folks on pingerati reviews getting lost (note: this will require publishing more reviews and theen watching them through the update process)&lt;br /&gt;
* &amp;lt;del&amp;gt;prototype a NetNewsWire microformat extractor (CSS+AppleScript)&amp;lt;/del&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Drew McLellan ==&lt;br /&gt;
&lt;br /&gt;
[[User:DrewMcLellan|DrewMcLellan]] &lt;br /&gt;
&lt;br /&gt;
* Build an hReview profile for [http://allinthehead.com/hkit/ hKit] and test&lt;br /&gt;
* Update the [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver extensions] to mirror recent changes in the online builders&lt;br /&gt;
* &amp;lt;del&amp;gt;Publish an hCard to JSON service on [http://tools.microformatic.com/ tools.microformatic.com] using hKit.&amp;lt;/del&amp;gt;&lt;br /&gt;
* Further develop blog comment form hCard collection ideas.&lt;br /&gt;
* Version of hReview creator using hKit to import business details from an hCard&lt;br /&gt;
&lt;br /&gt;
== Christophe Ducamp (french localization) ==&lt;br /&gt;
&lt;br /&gt;
[[Christophe Ducamp]]&lt;br /&gt;
* translate red links on [[Main_Page-fr]]&lt;br /&gt;
* localize a [http://www.elanceur.org/microformats/index.html french version] of the official website &lt;br /&gt;
** ask authorization to the authors&lt;br /&gt;
** migration could be done on any collaborative CMS&lt;br /&gt;
** test a cocomment system (based on local-wiki)&lt;br /&gt;
** complete with original links &lt;br /&gt;
* find experts for peer-reviewing&lt;br /&gt;
* update [http://fr.wikipedia.org/wiki/Microformats French-wikipedia:Microformats] via cowriting [http://fr.wikipedia.org/wiki/Discuter:Microformats on discussion page] (directly originated from the english article) + french examples to be found + local resources.&lt;br /&gt;
&lt;br /&gt;
== Frances Berriman ==&lt;br /&gt;
&lt;br /&gt;
[[User:Phae|Frances Berriman]]&lt;br /&gt;
&lt;br /&gt;
* Work on styles for [[zen-garden]] project.&lt;br /&gt;
* Style HTML cheatsheet to match Brian Suda's PDF.&lt;br /&gt;
* Write simplified help/implementation documents (how tos) for all finalised Microformats.&lt;br /&gt;
* Re-organise general FAQ and simplify&lt;br /&gt;
** (Feel free to add suggested tasks to my list below:)&lt;br /&gt;
*** Help converge on organization efforts ~bewest :-)&lt;br /&gt;
&lt;br /&gt;
== Ben West (bewest) ==&lt;br /&gt;
&lt;br /&gt;
[[User:BenWest|bewest]]&lt;br /&gt;
* fight spam&lt;br /&gt;
* help tend wiki&lt;br /&gt;
&lt;br /&gt;
=== Vocabulary ===&lt;br /&gt;
A lot of knowledge work is about maintaining sets of vocabulary. Now that the vocabulary is emerging, it may be time start making sure everyone is &amp;quot;on the same page,&amp;quot; especially since some of the language is highly symbolic.&lt;br /&gt;
Terms:&lt;br /&gt;
* &amp;quot;boil the ocean&amp;quot; A huge task.  &amp;quot;A phrase used in the industry to describe an attempt at something that is way too ambitious. For example, &amp;quot;They're trying to get their site launched by COMDEX. They could easier boil the ocean.&amp;quot; from &amp;lt;http://www.netlingo.com/right.cfm?term=boil%20the%20ocean&amp;gt;&lt;br /&gt;
* microformats: more than one microformat&lt;br /&gt;
* microformat: see my definition on http://microformats.org/wiki/what-are-microformats#BenWest&lt;br /&gt;
* data fidelity: the extent to which a data format might be considered lossy. eg HTML is often seen as a lossy format because the information parsed out of a resource may not fully match the information orginally encoded. Non-lossy formats have a very high data fidelity, while lossy formats have low data fidelity. Microformats seek to increase data fidelity of html.&lt;br /&gt;
* market: the locus of economic forces&lt;br /&gt;
&lt;br /&gt;
: See [[glossary]]. [[User:AndyMabbett|Andy Mabbett]] 13:57, 7 Dec 2006 (PST)&lt;br /&gt;
&lt;br /&gt;
=== Creators ===&lt;br /&gt;
_Concession_: my plans involve reuse of code, which would involve non-compatible changes with the current inline model.  This is a nice feature, so maybe I should be branching instead.&lt;br /&gt;
* &amp;lt;strike&amp;gt;Start hatom creator.&amp;lt;/strike&amp;gt; http://dichotomize.com/uf/hatom/creator.html&lt;br /&gt;
* Code Reuse. These creators are downright handy, and I’ve reimplemented the vcard one on my own site. Instead, let’s make these widgetized. Let’s decide on a more or less canonical html structure and create some javascript that will create the desired microformat. Something as easy to use as new Microformat.hCard($('mycontainer')); would be awesome. Right now, if someone makes an improvement to the hCard creator, the other creators don’t get the benefit. Spec this out!&lt;br /&gt;
* About Section. Is there an official creator page? If so, let’s point to that. The about paragraph is getting longer and longer with phrases like “which is based on…” repeated over and over.&lt;br /&gt;
* Default all dates to “right now”. Provide an easy to use calendar type widget to change dates.&lt;br /&gt;
* hAtom creator: Add multiple. It’d be nice to add an arbitrary number of entries.&lt;br /&gt;
* hAtom creator: Optional feed enclosure. Check box to wrap the entry/entries in an hfeed.&lt;br /&gt;
* Edit URI: Allow someone to enter a URI and edit whatever microformat is found on the page.&lt;br /&gt;
* Optionals. If the format requires, say, a vcard, the creator can defer to an external URI or can trust the user to fill it in later.&lt;br /&gt;
* Common stylesheet. I suppose this goes with the reuseable code idea… we have many great coders, we should be reusing eachothers’ work.&lt;br /&gt;
* Use Amazon's ECS to pull in information about products when there is an ASIN in the item URI.&lt;br /&gt;
&lt;br /&gt;
=== Information Architecture ===&lt;br /&gt;
'''Help Welcomed! Please leave your name'''&lt;br /&gt;
Add complaints to [[wiki-feedback]]!&lt;br /&gt;
Helping to make the wiki easier to use.  I'd like to see the main page more towards a format like http://simile.mit.edu/solvent/ with the big questions right out front:&lt;br /&gt;
* What Is This?&lt;br /&gt;
* What can I do here?&lt;br /&gt;
* Is there a demo?&lt;br /&gt;
* Where can I learn more?&lt;br /&gt;
I'd like to change the front page to this kind of design.&lt;br /&gt;
==== Support Pages ====&lt;br /&gt;
There are several categories of things in the wiki.  Can we enumerate them?&lt;br /&gt;
* About the Community&lt;br /&gt;
** Where to find information.&lt;br /&gt;
** Who are the stake holders?&lt;br /&gt;
** FAQs&lt;br /&gt;
* Web/Architectural Philosophy&lt;br /&gt;
** Community Principles&lt;br /&gt;
** Why are we doing this?&lt;br /&gt;
** XML and Namespaces&lt;br /&gt;
** Semantic XHTML&lt;br /&gt;
** Common Misconceptions&lt;br /&gt;
** Concession and Disposition of Criticism&lt;br /&gt;
** FAQs&lt;br /&gt;
* Specs&lt;br /&gt;
** Examples&lt;br /&gt;
** Discussion&lt;br /&gt;
** Exploration&lt;br /&gt;
** Use Cases&lt;br /&gt;
** Implementations&lt;br /&gt;
** The spec itself.&lt;br /&gt;
&lt;br /&gt;
* Tips and Tricks for Authoring ([[User:BenWest|BenWest]] 15:00, 9 Dec 2006 (PST))&lt;br /&gt;
** how to author semantic html&lt;br /&gt;
** choosing class names&lt;br /&gt;
** using HTML's general extension mechanisms&lt;br /&gt;
** advocating use&lt;br /&gt;
** collaborating/reusing HTML&lt;br /&gt;
** debugging HTML: use pastebin, separate out the relevant bits.&lt;br /&gt;
** getting help from the community&lt;br /&gt;
** applying Microformats.&lt;br /&gt;
&lt;br /&gt;
Can others agree and or refine this list?  Should I take it to the -discuss list?  How do we create consensus on how the wiki should be organized in order to make it more usable? And how can we turn that consensus into actionable changes?&lt;br /&gt;
&lt;br /&gt;
The wiki should also capture wisdom that stems from discussions that don't produce microformats.  For example, Chris Messina suggests a &amp;quot;Best Of&amp;quot; page suitable for capturing this kind of wisdom.  I think we can think of a given microformat as being at a place in a spectrum that ranges from &amp;quot;not yet thought of&amp;quot;, to &amp;quot;interesting but needs work,&amp;quot; or even &amp;quot;rejected&amp;quot;, and of course including all the stages familiar to the microformats processes (eg examples, brainstorming, etc...).&lt;br /&gt;
If there were such a page would it:&lt;br /&gt;
* Belong to a microformat? (eg hcard-bestof)&lt;br /&gt;
* or to the global namespace? (eg /wiki/wisdom/foobar-format)&lt;br /&gt;
(I think Chris Messina suggests that it belongs to a given microformat, but then how do we collect wisdom from non-microformats?)&lt;br /&gt;
&lt;br /&gt;
Considering that the wiki page named with the microformat (i.e. /wiki/hcard) is the one that people will mostly likely look to first for learning about a particular format, I'd think it'd make more sense and create a more welcoming feel to convert these pages to an intro page introducing the format for the beginner and linking to resources like tutorials and creators. Spec pages would then be relocated to wiki/*-spec -- [[User:Cgriego|Cgriego]] 13:25, 16 Oct 2006 (PDT)&lt;br /&gt;
&lt;br /&gt;
====Mike Schinkel's Comments====&lt;br /&gt;
&lt;br /&gt;
My suggestion on the list was for us to use a convention that the entry page (i.e.&lt;br /&gt;
http://microformats.org/wiki/hcard) would be an index into a list of&lt;br /&gt;
(psuedo) standardized sub pages so that it would be very people to &lt;br /&gt;
find what is important to them. For example, is a list of potential sub pages:&lt;br /&gt;
&lt;br /&gt;
* Microformat&lt;br /&gt;
** Specification&lt;br /&gt;
** Tutorial&lt;br /&gt;
** Examples&lt;br /&gt;
** Use cases&lt;br /&gt;
** Reference&lt;br /&gt;
** Discussion&lt;br /&gt;
** Brainstorming (might be combined w/Discussion)&lt;br /&gt;
** Implementations&lt;br /&gt;
** Related Pages&lt;br /&gt;
** Further Reading&lt;br /&gt;
** All (Uses Mediawiki's &amp;quot;includes&amp;quot; to create a page including all sub pages; very useful for printing &amp;amp; reading offline)&lt;br /&gt;
&lt;br /&gt;
These pages would be located respectively at&lt;br /&gt;
&lt;br /&gt;
* http://microformats.org/wiki/hcard/&lt;br /&gt;
** http://microformats.org/wiki/hcard/Specification&lt;br /&gt;
** http://microformats.org/wiki/hcard/Tutorial&lt;br /&gt;
** http://microformats.org/wiki/hcard/Examples&lt;br /&gt;
** http://microformats.org/wiki/hcard/Use_cases&lt;br /&gt;
** http://microformats.org/wiki/hcard/Reference&lt;br /&gt;
** http://microformats.org/wiki/hcard/Discussion&lt;br /&gt;
** http://microformats.org/wiki/hcard/Brainstorming&lt;br /&gt;
** http://microformats.org/wiki/hcard/Implementations&lt;br /&gt;
** http://microformats.org/wiki/hcard/Related_Pages&lt;br /&gt;
** http://microformats.org/wiki/hcard/Further_Reading&lt;br /&gt;
** http://microformats.org/wiki/hcard/All&lt;br /&gt;
&lt;br /&gt;
Please note I am suggesting an architecture not a specific list of sub pages. The list of sub pages should be defined by both reviewing existing information during site reorganization, and then via discussion on the list in an attempt to discover and extract which sub pages are needed for most/all microformats.&lt;br /&gt;
&lt;br /&gt;
'''NOTE''': This differs from above in that the spec if not viewed as a top level structure but instead the microformat itself and the spec would be under the microformat.  In this context &amp;quot;microformat&amp;quot; is a more abstract concept and &amp;quot;spec&amp;quot; is a more concrete thing. Another way to think about it would be that each microformat would have it's own mini home page and then things like &amp;quot;spec&amp;quot; are the pages listed on its home page.&lt;br /&gt;
&lt;br /&gt;
== Matt Dertinger (Thewhoo) ==&lt;br /&gt;
&lt;br /&gt;
[[User:Thewhoo]]&lt;br /&gt;
&lt;br /&gt;
=== hAtom2Atom ===&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Support for other XSLT engines:&lt;br /&gt;
* hAtom2Atom written using XSL 2.0&lt;br /&gt;
&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Support for other output formats: (hAtom2&amp;lt;i&amp;gt;xyz&amp;lt;/i&amp;gt;.xsl)&lt;br /&gt;
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl])&lt;br /&gt;
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt])&lt;br /&gt;
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])&lt;br /&gt;
&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Microformats Proposals ===&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;rel=&amp;quot;disclaimer&amp;quot;:&lt;br /&gt;
* Purpose: to create a semantic linkage (relationship) between a foot-note or end-note marker and the actual location of the text that the marker refers to.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;rel=&amp;quot;external&amp;quot;:&lt;br /&gt;
* Purpose: to formalize what is already in existence in the wild. The use of rel=&amp;quot;external&amp;quot; to refer to a document that is external or outside of the current domain.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Henri Bergius ==&lt;br /&gt;
&lt;br /&gt;
[[User:HenriBergius|Henri Bergius]]&lt;br /&gt;
&lt;br /&gt;
* Add hKit support for automatically populating contact details into [http://www.openpsa.org/version2/openpsa/contacts.html OpenPsa Contacts] CRM&lt;br /&gt;
* Implement Tail scripts for adding things into Midgard&lt;br /&gt;
&lt;br /&gt;
== Justin Thorp ==&lt;br /&gt;
* Start researching examples for a To-do microformat&lt;br /&gt;
&lt;br /&gt;
== [[User:MarkLentczner|Mark Lentczner]] ==&lt;br /&gt;
&lt;br /&gt;
* Get Second Life's event web pages to have proper event microformats data&lt;br /&gt;
** Add [[hcard|hCard]] to profile pages&lt;br /&gt;
** Add [[hcalendar|hCalendar]] to events listings&lt;br /&gt;
* Start pinging pingerati.net/ping/$url when pages are updated&lt;br /&gt;
* Collaborate on designing how to integrate microformats, metadata and objects in [http://secondlife.com/ Second Life].&lt;br /&gt;
&lt;br /&gt;
== New Person 1 ==&lt;br /&gt;
&lt;br /&gt;
etc.&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=User:Dmitry_Baranovskiy&amp;diff=18469</id>
		<title>User:Dmitry Baranovskiy</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=User:Dmitry_Baranovskiy&amp;diff=18469"/>
		<updated>2006-10-03T07:15:03Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Dmitry Baranovskiy&lt;br /&gt;
&lt;br /&gt;
[http://dmitry.baranovskiy.com My Blog]&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=tagcloud-brainstorming&amp;diff=12016</id>
		<title>tagcloud-brainstorming</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=tagcloud-brainstorming&amp;diff=12016"/>
		<updated>2006-09-26T03:51:40Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This is for brainstorming ideas around '''tagcloud''' formats&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[tagcloud-examples]]&lt;br /&gt;
==First pass analysis==&lt;br /&gt;
From a visual and logical perspective, tagclouds have a reasonably small number of common components, and largely all focus on the same problem. They are typically&lt;br /&gt;
&lt;br /&gt;
* an alphabetically ordered list of links to a tag space — occasionally the order is by popularity. &lt;br /&gt;
* the links are usually single words&lt;br /&gt;
&lt;br /&gt;
While it is possible to imagine other ways of representing tags, like most recent, using a tag cloud, in the examples considered all show popularity, albeit over different time scales. Typically the times scales are&lt;br /&gt;
&lt;br /&gt;
* most commonly, all time popularity&lt;br /&gt;
* less frequently popularity over the last week and&lt;br /&gt;
* popularity ver the last 24 hours&lt;br /&gt;
&lt;br /&gt;
On the ground, things become more complicated.&lt;br /&gt;
===the root elements===&lt;br /&gt;
Typically, but nopt always, there is a root element, with a class or id value.&lt;br /&gt;
Root elements include the following elements&lt;br /&gt;
&lt;br /&gt;
* p&lt;br /&gt;
* div&lt;br /&gt;
* ul&lt;br /&gt;
* td&lt;br /&gt;
&lt;br /&gt;
And are given the following class and/or id values&lt;br /&gt;
&lt;br /&gt;
* class=&amp;amp;#8221;heatmap&amp;amp;#8221; id=&amp;amp;#8221;smallheatmap&amp;amp;#8221;&lt;br /&gt;
* class=&amp;amp;#8221;heatmap&amp;amp;#8221; id=&amp;amp;#8221;bigheatmap&amp;amp;#8221;&lt;br /&gt;
* id=&amp;amp;#8221;TagCloud&amp;amp;#8221;&lt;br /&gt;
* id=recently&lt;br /&gt;
* class=&amp;amp;#8221;frontpageheatmap&amp;amp;#8221;&lt;br /&gt;
* class=&amp;amp;#8221;alphacloud&amp;amp;#8221;&lt;br /&gt;
* class=&amp;amp;#8221;freqcloud&amp;amp;#8221;&lt;br /&gt;
* class=&amp;amp;#8221;zoomclouds&amp;amp;#8221;&lt;br /&gt;
* id=&amp;amp;#8221;tagcloud24Display&amp;amp;#8221; class=&amp;amp;#8221;tagcloud&amp;amp;#8221;&lt;br /&gt;
* id=&amp;amp;#8221;tagcloudWeekDisplay&amp;amp;#8221; class=&amp;amp;#8221;tagcloud&amp;amp;#8221;&lt;br /&gt;
* id=&amp;amp;#8221;tagcloudDisplay&amp;amp;#8221; class=&amp;amp;#8221;tagcloud&amp;amp;#8221;&lt;br /&gt;
* class=&amp;amp;#8221;hTagcloud&amp;amp;#8221;&lt;br /&gt;
&lt;br /&gt;
Clearly there is some consensus. Cloud is the most common part of the identifying values, with tagcloud in whole or part reasonably common. But, do heatmaps constitute a specific subset of tagclouds? Do we really have two kinds of seemingly similar entities — tagclouds and heatmaps? Or areall tagclouds heatmaps?&lt;br /&gt;
A  class or id name for the root element of a tagcloud is required. We are proposing hTagcloud, as the general term for these entities is &amp;amp;#8220;tagcloud&amp;amp;#8221; and by analogy with hCard etc. Class rather than id would seem to make the most sense, as often more than one tagcloud appears on a page. &lt;br /&gt;
===The tags themselves===&lt;br /&gt;
Some of the clouds are marked up as lists:&lt;br /&gt;
&lt;br /&gt;
* technorati&lt;br /&gt;
* webconnections&lt;br /&gt;
&lt;br /&gt;
Some of them are marked up as links without any other intervening markup&lt;br /&gt;
&lt;br /&gt;
* flickrs tagcloud (but not heat maps!)&lt;br /&gt;
* BBPress&lt;br /&gt;
* del.icio.us&lt;br /&gt;
* squidoo&lt;br /&gt;
&lt;br /&gt;
Zoomclouds wrap the links in a spam with a class value.&lt;br /&gt;
====Marking up &amp;amp;#8220;weight&amp;amp;#8221;====&lt;br /&gt;
Probably the trickiest issue is how popularity &amp;amp;#8220;weight&amp;amp;#8221; is marked up.&lt;br /&gt;
Several sites use inline CSS, with font-size values including&lt;br /&gt;
&lt;br /&gt;
* flickr&lt;br /&gt;
* BBPress&lt;br /&gt;
* squidoo&lt;br /&gt;
&lt;br /&gt;
This is hardly to be considered semantic markup.&lt;br /&gt;
Other sites use class values&lt;br /&gt;
&lt;br /&gt;
* del.icio.us&lt;br /&gt;
* zoomclouds&lt;br /&gt;
* web connections&lt;br /&gt;
&lt;br /&gt;
Probably the most immediately obvious mechanism for marking up tag weights. Class is used in ways similar to this all the time. But we should perhaps be less hasty than this. What exactly is class for? Our old friend the  [http://www.w3.org/TR/html4/struct/global.html#h-7.4.3 HTML 4.01 spec]  says of class&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&lt;br /&gt;
The class attribute has several roles in HTML: &amp;amp;#8230; For general purpose processing by user agents.&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
Does giving an tag a class value to represent its popularity constitute using class for &amp;amp;#8220;general purpose processing&amp;amp;#8221;? The definition is sufficiently vague as to seemingly preclude nothing that would loosely be associated with data processing. But it might be suggested that class is for element identification (the class attribute definition is actually found in the specification subsection titled &amp;amp;#8220;Element identifiers&amp;amp;#8221;), not for containing actual data, which arguably relative popularity is. Perhaps one way of addressing this is by semantically naming the class values in a relative way, for example &amp;amp;#8220;popular&amp;amp;#8221;, &amp;amp;#8220;v-popular&amp;amp;#8221;, &amp;amp;#8220;vv-popular&amp;amp;#8221;. In this context, tags would &amp;amp;#8220;belong to a class&amp;amp;#8221; based on popularity. But, it&amp;amp;#8217;s not the tag which belongs to a class, rather the element which has the tag as its value which is assigned a class in this way.&lt;br /&gt;
You might be able to see why I suggested that the obvious use of class might be a bit hasty.&lt;br /&gt;
Two unique examples stand out. In addition to using inline CSS, BBPress also adds a title value relative to weight. The more popular a tag, the higher the value of the title value. While this may seem perverse, it&amp;amp;#8217;s at least arguably correct. The [http://www.w3.org/TR/html4/struct/global.html#h-7.4.3 HTML 4.01 spec] says of title This attribute offers advisory information about the element for which it is set. As to whether the popularity of a tag constitutes &amp;amp;#8220;advisory information&amp;amp;#8221; is a matter for discussion.&lt;br /&gt;
Technorati uses nested em elements to indicate weight. This is very clever, IMO, but I suspect, and a quick straw poll with some pretty savvy developers suggests, that it is perhaps not overly humanly friendly at least from a publisher&amp;amp;#8217;s point of view.&lt;br /&gt;
Precisely how best to markup the weight of a tag would seem to me to be the outstanding issue to resolve in developing a tagcloud microformat.&lt;br /&gt;
==Next steps==&lt;br /&gt;
Ok, looking over our microformats process checklist:  we&amp;amp;#8217;ve seen there is a problem to solve, and we&amp;amp;#8217;ve done some research into the curent ways in which the problem is being solved. What&amp;amp;#8217;s next?  [http://microformats.org/wiki/process Microformats.org has this to say about creating a new microformat ]&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&lt;br /&gt;
&amp;lt;strong&amp;gt;[http://microformats.org/wiki/process#Propose_a_Microformat DON&amp;amp;#8217;T!!!]&amp;lt;/strong&amp;gt;&lt;br /&gt;
There are other things to try before developing a microformat. First, ask yourself these questions:&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
# Is there a standard element in XHTML that would work?&lt;br /&gt;
# Is there a compound of XHTML elements that would work?&lt;br /&gt;
# Ok, if the answer to the above two is &amp;amp;#8216;no,&amp;amp;#8217; we can talk about a microformat.&lt;br /&gt;
&lt;br /&gt;
So&lt;br /&gt;
&lt;br /&gt;
1. Is there a standard XHTML element which would work?&amp;lt;br /&amp;gt; I really don&amp;amp;#8217;t think so. &lt;br /&gt;
&lt;br /&gt;
2. Is there a compound of XHTML elements that would work?&amp;lt;br /&amp;gt;&lt;br /&gt;
I think that we can get a fair way to solving this problem by using a number of standard HTML components. In essence, a tagcloud is just a list of links. It&amp;amp;#8217;s ordered usually alphabetically, but in the case of del.icio.us, by frequency as well. Often too, the list is labeled with a heading, and some kind of explanation.&lt;br /&gt;
==Issues to resolve==&lt;br /&gt;
A number of issues emerge even before we get to the more thorny ones outlined above.&lt;br /&gt;
Should a tagcloud microformat mandate the use of lists, or any type of particular element? Typically, microformats focus on the use of class values, and other attribute values. However, some focus in element types too — for example XOXO.&lt;br /&gt;
Should the issue of different types of tagcloud (all time popularity, time scoped popularity) as found in these real world examples be accommodated in a hTagcloud? &lt;br /&gt;
The web connections tagcloud markup deals with this issue like this&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;amp;lt;div class=&amp;quot;hTagcloud&amp;quot;&amp;amp;gt;&lt;br /&gt;
	&amp;amp;lt;ul class=&amp;quot;popularity&amp;quot;&amp;amp;gt;&lt;br /&gt;
		&amp;amp;lt;li class=&amp;quot;weight1&amp;quot;&amp;amp;gt;&amp;amp;lt;a href=&amp;quot;/tags/Access+Testing&amp;quot;&amp;amp;gt;Access Testing&amp;amp;lt;/a&amp;amp;gt;&amp;amp;lt;/li&amp;amp;gt;&lt;br /&gt;
		&amp;amp;lt;li class=&amp;quot;weight1&amp;quot;&amp;amp;gt;&amp;amp;lt;a href=&amp;quot;/tags/McFarlane+Prize&amp;quot;&amp;amp;gt;McFarlane Prize&amp;amp;lt;/a&amp;amp;gt;&amp;amp;lt;/li&amp;amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
This would conform with microformats patterns, where the root element has a single identifying class or id value. &lt;br /&gt;
Squidoo on the other hand, marks this up by using both an id and class value on its &amp;amp;#8220;root&amp;amp;#8221; tagcloud element  &lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;amp;lt;div id=&amp;quot;tagcloud24Display&amp;quot; class=&amp;quot;tagcloud&amp;quot;&amp;amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
So, again, we can find in these real world examples that there is a need to differentiate different kinds of tagcloud.&lt;br /&gt;
The web connections approach uses the semantic appropriateness of the list, coupled with a containing root div element to provide a mechanism for doing this conformant with current microformats patterns.&lt;br /&gt;
The really significant issue, as outline above is just how to correctly use the mechanisms for HTML to markup the weight of fonts?&lt;br /&gt;
==Toward a proposal for hTagcloud==&lt;br /&gt;
OK, I&amp;amp;#8217;ve followed the process for considering whether a tagcloud microformat makes sense. i think given the widespread use of this pattern, at some significant sites and in some significant applications, that at least the proposal of this microformat makes sense. Where do we go now?&lt;br /&gt;
[http://microformats.org/wiki/process#Propose_a_Microformat Are there any well established, interoperable implemented standards we can look at which address this problem?]. To the best of my knowledge, no.&lt;br /&gt;
Next the proposal procedure asks us to ensure that it is[http://microformats.org/wiki/process#Propose_a_Microformat designed for humans first and machines second]. Let&amp;amp;#8217;s keep that in mind with the following .01 draft proposal.&lt;br /&gt;
In conjunction with this, the process asks&lt;br /&gt;
&lt;br /&gt;
* If I looked at this microformat in a browser that didn&amp;amp;#8217;t support CSS or had CSS turned off, would it still be human-readable?&lt;br /&gt;
* Are this format&amp;amp;#8217;s elements stylable with CSS?&lt;br /&gt;
&lt;br /&gt;
We&amp;amp;#8217;ll address these in a moment as well.&lt;br /&gt;
==.01 hTagcloud proposal==&lt;br /&gt;
Based on the above discussion, here is a very first stab at an hTagcloud microformat proposal. Some of it is contingent on the resolution of the issues outlined above and summarized below.&lt;br /&gt;
# hTagclouds have a root element with a class value of hTagcloud&lt;br /&gt;
# this root element contains a list element, with an optional class value which identifies the nature of the tagcloud — is it historically popular? is it popularity within the last 24hours, is it popularity within the last 7 days. These are the three common kinds of popularity in the real world examples shown. Should other reasonably common kinds of cloud be found in the wild, these can be added to the list&lt;br /&gt;
# This list may also optionally have a class value to indicate the order — alphabetical or by frequency (is this really required?)&lt;br /&gt;
# tags are link elements, with an href value of the tagspace which the tagcloud represents&lt;br /&gt;
# popularity or &amp;amp;#8220;weight&amp;amp;#8221; is conveyed with class values. There are 5 class values, ranging from &amp;amp;#8220;popular&amp;amp;#8221; to &amp;amp;#8220;vvvv-popular&amp;amp;#8221;. Some tag clouds have many more levels than this, but around 5 is a common number of weights. Many more than 5 becomes difficylt to convey meaningfully via style. &amp;amp;#8220;Popular&amp;amp;#8221; is the &amp;amp;#8220;lowest&amp;amp;#8221; value, because in any non trivial tagging system, the number of tags in the system vastly exceeds the tags displayed in the tagcloud. All tags in a tagcloud are at least popular. That&amp;amp;#8217;s why the values don&amp;amp;#8217;t start with vv-unpopular, and range to vv-popular, by analogy with CSS named font sizes. As per the discussion on class values for marking up tag weight above, popularity has been chosen above terms like &amp;amp;#8220;weight&amp;amp;#8221; so that the tags belong to a class based on popularity, rather than using class to carry with it more data about the content of the element. The use of class in this way is familar to a significant number of developers, and makes for easily stylable tagclouds.&lt;br /&gt;
# The use of the &amp;amp;#8220;title&amp;amp;#8221; has been excluded for the following reasons&lt;br /&gt;
## it&amp;amp;#8217;s an atypical use of title&lt;br /&gt;
## elements marked up with title could only be styled using CSS with attribute selectors, which are both largely unused by developers, and not supported in the majority of browsers people use (in the sense that the majority of web users are using a browser which does not support this selector, therefore in effect these elements aren&amp;amp;#8217;t stylable at present with CSS, and so developers would be unlikely to adopt this practice for this practical reason)&lt;br /&gt;
# The use of nested ems has been not adopted for this draft because of its novelty, and the fussiness of coding it could quite possibly preclude the adoption of hTagcloud. This is based on a straw poll of some very proficient developers. While it is a very clever use of HTML, it might also be argued that the existence of the em element for [http://www.w3.org/TR/html4/struct/text.html#h-9.2.1 Indicat{ing} emphasis] and additionally the strong element for [http://www.w3.org/TR/html4/struct/text.html#h-9.2.1 Indicat{ing} stronger emphasis] suggests that the use of multiply nested em elements does not indicate greater emphasis than a single unnested em element. Otherwise strong would be redundant, as equivalent to &amp;amp;lt;em&amp;amp;gt;&amp;amp;lt;em&amp;amp;gt;&lt;br /&gt;
Of course, this is a .01 specification, and has been explicitly drafted to put the issues on the table for discussion at this early stage, while also moving the proposal forward by making concrete suggestions.&lt;br /&gt;
==an example hTagcloud==&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;amp;lt;div class=&amp;quot;hTagcloud&amp;quot;&amp;amp;gt;&lt;br /&gt;
	&amp;amp;lt;ul class=&amp;quot;popularity&amp;quot;&amp;amp;gt;&lt;br /&gt;
		&amp;amp;lt;li class=&amp;quot;vvvv-popular&amp;quot;&amp;amp;gt;&amp;amp;lt;a href=&amp;quot;/tags/Web+Standards+Group&amp;quot;&amp;amp;gt;Web Standards Group&amp;amp;lt;/a&amp;amp;gt;&amp;amp;lt;/li&amp;amp;gt;&lt;br /&gt;
		&amp;amp;lt;li class=&amp;quot;vvv-popular&amp;quot;&amp;amp;gt;&amp;amp;lt;a href=&amp;quot;/tags/accessibility&amp;quot;&amp;amp;gt;accessibility&amp;amp;lt;/a&amp;amp;gt;&amp;amp;lt;/li&amp;amp;gt;&lt;br /&gt;
		&amp;amp;lt;li class=&amp;quot;popular&amp;quot;&amp;amp;gt;&amp;amp;lt;a href=&amp;quot;/tags/beta+tester&amp;quot;&amp;amp;gt;beta tester&amp;amp;lt;/a&amp;amp;gt;&amp;amp;lt;/li&amp;amp;gt;&lt;br /&gt;
		&amp;amp;lt;li class=&amp;quot;vvv-popular&amp;quot;&amp;amp;gt;&amp;amp;lt;a href=&amp;quot;/tags/css&amp;quot;&amp;amp;gt;css&amp;amp;lt;/a&amp;amp;gt;&amp;amp;lt;/li&amp;amp;gt;&lt;br /&gt;
		&amp;amp;lt;li class=&amp;quot;v-popular&amp;quot;&amp;amp;gt;&amp;amp;lt;a href=&amp;quot;/tags/ex-coder&amp;quot;&amp;amp;gt;ex-coder&amp;amp;lt;/a&amp;amp;gt;&amp;amp;lt;/li&amp;amp;gt;&lt;br /&gt;
		&amp;amp;lt;li class=&amp;quot;vv-popular&amp;quot;&amp;amp;gt;&amp;amp;lt;a href=&amp;quot;/tags/usability&amp;quot;&amp;amp;gt;usability&amp;amp;lt;/a&amp;amp;gt;&amp;amp;lt;/li&amp;amp;gt;&lt;br /&gt;
		&amp;amp;lt;li class=&amp;quot;vvvv-popular&amp;quot;&amp;amp;gt;&amp;amp;lt;a href=&amp;quot;/tags/wsg&amp;quot;&amp;amp;gt;wsg&amp;amp;lt;/a&amp;amp;gt;&amp;amp;lt;/li&amp;amp;gt;&lt;br /&gt;
 	&amp;amp;lt;/ul&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;/div&amp;amp;gt;&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=tagcloud-examples&amp;diff=32254</id>
		<title>tagcloud-examples</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=tagcloud-examples&amp;diff=32254"/>
		<updated>2006-09-26T03:34:19Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This is a page for '''Tagcloud''' examples&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[tagcloud-brainstorming]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Site Name: flickr==&lt;br /&gt;
===url===&lt;br /&gt;
http://flickr.com/photos/tags/&lt;br /&gt;
===Tag cloud models===&lt;br /&gt;
Flickr has both their main tagcloud, which models the relative popularity of tags historically, that is, how often a tag has been used in total, as well as smaller “hot tags” tag clouds, which reflect the most popular tags in a shorter period of time, a day and week respectively.&lt;br /&gt;
===Screenshots===&lt;br /&gt;
[http://microformatique.com/images/hTagcloud/flickrmain.gif http://microformatique.com/images/hTagcloud/flickrmain.gif]&lt;br /&gt;
&lt;br /&gt;
[http://microformatique.com/images/hTagcloud/flickrhot24.gif http://microformatique.com/images/hTagcloud/flickrhot24.gif]&lt;br /&gt;
&lt;br /&gt;
[http://microformatique.com/images/hTagcloud/flickrhotweek.gif http://microformatique.com/images/hTagcloud/flickrhotweek.gif]&lt;br /&gt;
===Code conventions===&lt;br /&gt;
The hot tags code looks like this&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;amp;lt;table id=&amp;quot;Recently&amp;quot;&amp;amp;gt;&lt;br /&gt;
	&amp;amp;lt;tr&amp;amp;gt;&lt;br /&gt;
		&amp;amp;lt;td&amp;amp;gt;&lt;br /&gt;
			&amp;amp;lt;p&amp;amp;gt;&amp;amp;lt;b&amp;amp;gt;In the last 24 hours&amp;amp;lt;/b&amp;amp;gt;&amp;amp;lt;br /&amp;amp;gt;&lt;br /&gt;
			&amp;amp;lt;b&amp;amp;gt;&amp;amp;lt;a href=&amp;quot;/photos/tags/pics2006/&amp;quot;&amp;amp;gt;pics2006&amp;amp;lt;/a&amp;amp;gt;,&amp;amp;nbsp;&amp;amp;lt;/b&amp;amp;gt;&lt;br /&gt;
			&amp;amp;lt;b&amp;amp;gt;&amp;amp;lt;a href=&amp;quot;/photos/tags/ubicomp2006/&amp;quot;&amp;amp;gt;ubicomp2006&amp;amp;lt;/a&amp;amp;gt;,&amp;amp;nbsp;&amp;amp;lt;/b&amp;amp;gt;&lt;br /&gt;
			...&lt;br /&gt;
		&amp;amp;lt;/p&amp;amp;gt;&lt;br /&gt;
		&amp;amp;lt;/td&amp;amp;gt;&lt;br /&gt;
		&amp;amp;lt;td&amp;amp;gt;&lt;br /&gt;
			&amp;amp;lt;p&amp;amp;gt;&amp;amp;lt;b&amp;amp;gt;Over the last week&amp;amp;lt;/b&amp;amp;gt;&amp;amp;lt;br /&amp;amp;gt;&lt;br /&gt;
			&amp;amp;lt;b&amp;amp;gt;&amp;amp;lt;a href=&amp;quot;/photos/tags/itunes7/&amp;quot;&amp;amp;gt;itunes7&amp;amp;lt;/a&amp;amp;gt;,&amp;amp;nbsp;&amp;amp;lt;/b&amp;amp;gt;&lt;br /&gt;
			&amp;amp;lt;b&amp;amp;gt;&amp;amp;lt;a href=&amp;quot;/photos/tags/futureofwebappssf06/&amp;quot;&amp;amp;gt;futureofwebappssf06&amp;amp;lt;/a&amp;amp;gt;,&amp;amp;nbsp;&amp;amp;lt;/b&amp;amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Flickrs main tagcloud looks like this in HTML&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;amp;lt;p id=&amp;quot;TagCloud&amp;quot;&amp;amp;gt;&lt;br /&gt;
	&amp;amp;nbsp;&amp;amp;lt;a href=&amp;quot;/photos/tags/06/&amp;quot; style=&amp;quot;font-size: 12px;&amp;quot;&amp;amp;gt;06&amp;amp;lt;/a&amp;amp;gt;&amp;amp;nbsp;&lt;br /&gt;
	&amp;amp;nbsp;&amp;amp;lt;a href=&amp;quot;/photos/tags/amsterdam/&amp;quot; style=&amp;quot;font-size: 15px;&amp;quot;&amp;amp;gt;amsterdam&amp;amp;lt;/a&amp;amp;gt;&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
===Notes===&lt;br /&gt;
# The hot tags are simply cells in a table with the id &amp;amp;#8220;recently&amp;amp;#8221;&lt;br /&gt;
# The tagcloud proper is a p with the id of &amp;amp;#8220;tagcloud&amp;amp;#8221; — which would allow only a single tagcloud per page&lt;br /&gt;
# that the links are simply links — despite this being a list of words, ordered alphabetically&lt;br /&gt;
# that the rank or weight or popularity of the tag is visually created using inline style and font-size&lt;br /&gt;
# There are at least a dozen different levels of popularity, difficult to determine without tedious work, as these are reflected in font-sizes in pixels.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Site Name: Technorati==&lt;br /&gt;
===url===&lt;br /&gt;
http://technorati.com/tags&lt;br /&gt;
===Tag cloud models===&lt;br /&gt;
This page shows two tag clouds, called &amp;amp;#8220;heat maps&amp;amp;#8221; — one for the most popular tags in the last hour, and one for the 100 historically most popular tags.&lt;br /&gt;
===Screenshots===&lt;br /&gt;
[http://microformatique.com/images/hTagcloud/technloratimain.gif http://microformatique.com/images/hTagcloud/technloratimain.gif]&lt;br /&gt;
&lt;br /&gt;
[http://microformatique.com/images/hTagcloud/technloratihot1hr.gif http://microformatique.com/images/hTagcloud/technloratihot1hr.gif]&lt;br /&gt;
===Code conventions===&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;amp;lt;ul class=&amp;quot;heatmap&amp;quot; id=&amp;quot;smallheatmap&amp;quot;&amp;amp;gt;&lt;br /&gt;
	&amp;amp;lt;li&amp;amp;gt;&amp;amp;lt;em&amp;amp;gt;&amp;amp;lt;em&amp;amp;gt;&amp;amp;lt;em&amp;amp;gt;&amp;amp;lt;em&amp;amp;gt;&amp;amp;lt;em&amp;amp;gt;&amp;amp;lt;a href=&amp;quot;/tag/Advertising&amp;quot;&amp;amp;gt;Advertising&amp;amp;lt;/a&amp;amp;gt;&lt;br /&gt;
	&amp;amp;lt;/em&amp;amp;gt;&amp;amp;lt;/em&amp;amp;gt;&amp;amp;lt;/em&amp;amp;gt;&amp;amp;lt;/em&amp;amp;gt;&amp;amp;lt;/em&amp;amp;gt;&amp;amp;lt;/li&amp;amp;gt; &amp;amp;lt;li&amp;amp;gt;&amp;amp;lt;em&amp;amp;gt;&amp;amp;lt;em&amp;amp;gt;&lt;br /&gt;
	&amp;amp;lt;em&amp;amp;gt;&amp;amp;lt;a href=&amp;quot;/tag/Blogroll&amp;quot;&amp;amp;gt;Blogroll&amp;amp;lt;/a&amp;amp;gt;&amp;amp;lt;/em&amp;amp;gt;&amp;amp;lt;/em&amp;amp;gt;&amp;amp;lt;/em&amp;amp;gt;&amp;amp;lt;/li&amp;amp;gt; &amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;amp;lt;ul class=&amp;quot;heatmap&amp;quot; id=&amp;quot;bigheatmap&amp;quot;&amp;amp;gt;&lt;br /&gt;
	&amp;amp;lt;li&amp;amp;gt;&amp;amp;lt;em&amp;amp;gt;&amp;amp;lt;em&amp;amp;gt;&amp;amp;lt;em&amp;amp;gt;&amp;amp;lt;a href=&amp;quot;/tag/Allgemein&amp;quot;&amp;amp;gt;Allgemein&amp;amp;lt;/a&amp;amp;gt;&lt;br /&gt;
	&amp;amp;lt;/em&amp;amp;gt;&amp;amp;lt;/em&amp;amp;gt;&amp;amp;lt;/em&amp;amp;gt;&amp;amp;lt;/li&amp;amp;gt; &amp;lt;/pre&amp;gt;&lt;br /&gt;
===Notes===&lt;br /&gt;
&lt;br /&gt;
# each tagcloud is of class &amp;amp;#8220;heatmap&amp;amp;#8221;, but are differentiated by the ids &amp;amp;#8220;smallheatmap&amp;amp;#8221; (hot tags of the last hour) and largeheatmap (historically popular tags)&lt;br /&gt;
# tags are an unordered list&lt;br /&gt;
# Innovatively, and very cleverly, nested em elements provide the &amp;amp;#8220;weight&amp;amp;#8221; or &amp;amp;#8220;importance&amp;amp;#8221; of a tag.&lt;br /&gt;
# It&amp;amp;#8217;s not easy to determine how many levels of tag weight there are, as I&amp;amp;#8217;m too lazy to count nested em elements :-) &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Site Name: BBpress==&lt;br /&gt;
===url===&lt;br /&gt;
http://support.westciv.com&lt;br /&gt;
This is an example standard BBPress install. The PHP has been edited to make the font-sizing em based, and to constrain the font sizing to an upper and lower limit. This is done in the PHP.&lt;br /&gt;
===Tag cloud models===&lt;br /&gt;
As far as I can determine, the tagcloud shows the historically most popular tags, but given its labeling as &amp;amp;#8220;Hot tags&amp;amp;#8221; it may reflect the recent popularity of the the tags.&lt;br /&gt;
===Screenshots===&lt;br /&gt;
[http://microformatique.com/images/hTagcloud/bbpress.gif http://microformatique.com/images/hTagcloud/bbpress.gif]&lt;br /&gt;
===Code conventions===&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;amp;lt;p class=&amp;quot;frontpageheatmap&amp;quot;&amp;amp;gt;&lt;br /&gt;
	&amp;amp;lt;a href='http://support.westciv.com/tags.php?tag=bbedit' title='2 topics'&lt;br /&gt;
	style='font-size: 1.2em;'&amp;amp;gt;BBEdit&amp;amp;lt;/a&amp;amp;gt;&lt;br /&gt;
	&amp;amp;lt;a href='http://support.westciv.com/tags.php?tag=case_sensitive' title='1 topics'&lt;br /&gt;
	style='font-size: 0.9em;'&amp;amp;gt;case_sensitive&amp;amp;lt;/a&amp;amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
===Notes===&lt;br /&gt;
&lt;br /&gt;
# the cloud is a paragraph of class &amp;amp;#8220;frontpageheatmap&amp;amp;#8221;&lt;br /&gt;
# tags are just links, not in a list&lt;br /&gt;
# the relative rank of a tag is shown by inline style, but also indicated by the title attribute on the link element. e.g. title=&amp;amp;#8221;1 topics&amp;amp;#8221;, title=&amp;amp;#8221;3 topics&amp;amp;#8221;&lt;br /&gt;
# It&amp;amp;#8217;s unclear from the example how many levels of tag weight or rank there are&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Site Name: del.icio.us==&lt;br /&gt;
===url===&lt;br /&gt;
http://del.icio.us/tag/&lt;br /&gt;
===Tag cloud models===&lt;br /&gt;
The tag cloud shows a list of the most popular tags, presumably over time.&lt;br /&gt;
===Screenshots===&lt;br /&gt;
[http://microformatique.com/images/hTagcloud/deli.icio.us.gif http://microformatique.com/images/hTagcloud/deli.icio.us.gif]&lt;br /&gt;
===Code conventions===&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;amp;lt;div class=&amp;quot;alphacloud&amp;quot;&amp;amp;gt;&lt;br /&gt;
		&amp;amp;lt;a href=&amp;quot;/tag/.net&amp;quot; class=&amp;quot;lr s2;&amp;quot;&amp;amp;gt;.net&amp;amp;lt;/a&amp;amp;gt;&lt;br /&gt;
		&amp;amp;lt;a href=&amp;quot;/tag/advertising&amp;quot; class=&amp;quot;lb s1&amp;quot;&amp;amp;gt;advertising&amp;amp;lt;/a&amp;amp;gt;&lt;br /&gt;
		&amp;amp;lt;a href=&amp;quot;/tag/ajax&amp;quot; class=&amp;quot; s5&amp;quot;&amp;amp;gt;ajax&amp;amp;lt;/a&amp;amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
When the tags are chosen to be shown as a list in order of frequency, rather than alphabeticcally, the class name is &amp;amp;#8220;freqcloud&amp;amp;#8221;&lt;br /&gt;
===Notes===&lt;br /&gt;
&lt;br /&gt;
# There are two kinds of cloud — an alphacloud which orders tags alpahbetically, and a freqcloud, which orders them by popularity&lt;br /&gt;
# The links are not in a list&lt;br /&gt;
# There is a root element with a class value, variously &amp;amp;#8220;alphacloud&amp;amp;#8221; and &amp;amp;#8220;freqcloud&amp;amp;#8221;&lt;br /&gt;
# The weight of a tag is given by a class value — s1 though s5, giving 5 levels of weight&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Site Name: Zoomclouds==&lt;br /&gt;
===url===&lt;br /&gt;
http://zoomclouds.com/cloud/ZC_Blom/&lt;br /&gt;
===Tag cloud models===&lt;br /&gt;
Like most tag clouds, zoomclouds models the historical popularity of a tag.&lt;br /&gt;
===Screenshots===&lt;br /&gt;
Zoomclouds, more than most, utlize CSS to style their clouds.&lt;br /&gt;
[http://microformatique.com/images/hTagcloud/zoomclouds.gif http://microformatique.com/images/hTagcloud/zoomclouds.gif]&lt;br /&gt;
===Code conventions===&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;amp;lt;div class=&amp;quot;zoomclouds&amp;quot;&amp;amp;gt;&lt;br /&gt;
	&amp;amp;lt;span class=&amp;quot;tag2&amp;quot;&amp;amp;gt;&amp;amp;lt;a href=&amp;quot;http://www.zoomclouds.com/tag/ZC_Blom/asian+stocks&amp;quot;&lt;br /&gt;
	onmouseout=&amp;quot;zoomclouds_cs()&amp;quot; style=&amp;quot;font-size: 12px;&amp;quot;&amp;amp;gt;asian stocks&amp;amp;lt;/a&amp;amp;gt;&amp;amp;lt;/span&amp;amp;gt;&lt;br /&gt;
	&amp;amp;lt;span class=&amp;quot;zoomcloudswg&amp;quot;&amp;amp;gt;(39)&amp;amp;lt;/span&amp;amp;gt;&lt;br /&gt;
	&amp;amp;lt;span class=&amp;quot;tag1&amp;quot;&amp;amp;gt;&amp;amp;lt;a href=&amp;quot;http://www.zoomclouds.com/tag/ZC_Blom/analysts&amp;quot;&lt;br /&gt;
	style=&amp;quot;font-size: 9px;&amp;quot;&amp;amp;gt;analysts&amp;amp;lt;/a&amp;amp;gt;&amp;amp;lt;/span&amp;amp;gt;&lt;br /&gt;
	&amp;amp;lt;span class=&amp;quot;zoomcloudswg&amp;quot;&amp;amp;gt;(23)&amp;amp;lt;/span&amp;amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
# the root element is a div with a class value of &amp;amp;#8220;zoomclouds&amp;amp;#8221;&lt;br /&gt;
# the count of the tag is added as content after the tag name, with a class of zoomcloudswg.&lt;br /&gt;
# the weight of the tag is given by a font-size value, but also with a clas value of tagN, where N is an integer of 1–4 (at least in the example cited)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Site Name: Squidoo==&lt;br /&gt;
===url===&lt;br /&gt;
http://www.squidoo.com/browse/tag_cloud&lt;br /&gt;
===Tag cloud models===&lt;br /&gt;
Squidoo has three kinds of tag cloud — all ranking popularity. Hot tags, are those which are popular in the last 24 hours, recent tags are popular in the last week, and all time tags are the most popular tags over the life of squidoo&lt;br /&gt;
===Screenshots===&lt;br /&gt;
[http://microformatique.com/images/hTagcloud/squiddweek.gif http://microformatique.com/images/hTagcloud/squiddweek.gif]&lt;br /&gt;
&lt;br /&gt;
[http://microformatique.com/images/hTagcloud/squidall.gif http://microformatique.com/images/hTagcloud/squidall.gif]&lt;br /&gt;
&lt;br /&gt;
[http://microformatique.com/images/hTagcloud/squidoo24.gif http://microformatique.com/images/hTagcloud/squidoo24.gif]&lt;br /&gt;
===Code conventions===&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;amp;lt;div id=&amp;quot;tagcloud24Display&amp;quot; class=&amp;quot;tagcloud&amp;quot;&amp;amp;gt;&lt;br /&gt;
			&amp;amp;lt;a href=&amp;quot;http://www.squidoo.com/tags/advertising&amp;quot; style=&amp;quot;font-size:1em&amp;quot;&amp;amp;gt;advertising&amp;amp;lt;/a&amp;amp;gt;&lt;br /&gt;
			&amp;amp;lt;a href=&amp;quot;http://www.squidoo.com/tags/art&amp;quot; style=&amp;quot;font-size:1.8em&amp;quot;&amp;amp;gt;art&amp;amp;lt;/a&amp;amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;amp;lt;div id=&amp;quot;tagcloudWeekDisplay&amp;quot; class=&amp;quot;tagcloud&amp;quot;&amp;amp;gt;&lt;br /&gt;
			&amp;amp;lt;a href=&amp;quot;http://www.squidoo.com/tags/advertising&amp;quot; style=&amp;quot;font-size:.8em&amp;quot;&amp;amp;gt;advertising&amp;amp;lt;/a&amp;amp;gt;&lt;br /&gt;
			&amp;amp;lt;a href=&amp;quot;http://www.squidoo.com/tags/art&amp;quot; style=&amp;quot;font-size:2em&amp;quot;&amp;amp;gt;art&amp;amp;lt;/a&amp;amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;amp;lt;div id=&amp;quot;tagcloudDisplay&amp;quot; class=&amp;quot;tagcloud&amp;quot;&amp;amp;gt;&lt;br /&gt;
			&amp;amp;lt;a href=&amp;quot;http://www.squidoo.com/tags/advertising&amp;quot; style=&amp;quot;font-size:1.5em&amp;quot;&amp;amp;gt;advertising&amp;amp;lt;/a&amp;amp;gt;&lt;br /&gt;
			&amp;amp;lt;a href=&amp;quot;http://www.squidoo.com/tags/art&amp;quot; style=&amp;quot;font-size:2.2em&amp;quot;&amp;amp;gt;art&amp;amp;lt;/a&amp;amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
===Notes===&lt;br /&gt;
&lt;br /&gt;
# tag clouds all are divs with a class value of tagcloud&lt;br /&gt;
# the three are differentiated by id values, &amp;amp;#8220;tagcloud24Display&amp;amp;#8221;, &amp;amp;#8220;tagcloudWeekDisplay&amp;amp;#8221;, &amp;amp;#8220;tagcloudDisplay&amp;amp;#8221;&lt;br /&gt;
# weight is indicated by inline CSS &amp;amp;#8220;font-size&amp;amp;#8221; values&lt;br /&gt;
# there appear to be quite a significant number different weights, as indicated by different font-size values&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Site Name: Web Connections==&lt;br /&gt;
===url===&lt;br /&gt;
http://connections.webdirections.org&lt;br /&gt;
===Tag cloud models===&lt;br /&gt;
The tag cloud represents the popularity of tags historically&lt;br /&gt;
===Screenshots===&lt;br /&gt;
[http://microformatique.com/images/hTagcloud/webconnections.gif http://microformatique.com/images/hTagcloud/webconnections.gif]&lt;br /&gt;
===Code conventions===&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;amp;lt;div class=&amp;quot;hTagcloud&amp;quot;&amp;amp;gt;&lt;br /&gt;
	&amp;amp;lt;ul class=&amp;quot;popularity&amp;quot;&amp;amp;gt;&lt;br /&gt;
		&amp;amp;lt;li class=&amp;quot;weight1&amp;quot;&amp;amp;gt;&amp;amp;lt;a href=&amp;quot;/tags/Access+Testing&amp;quot;&amp;amp;gt;Access Testing&amp;amp;lt;/a&amp;amp;gt;&amp;amp;lt;/li&amp;amp;gt;&lt;br /&gt;
		&amp;amp;lt;li class=&amp;quot;weight1&amp;quot;&amp;amp;gt;&amp;amp;lt;a href=&amp;quot;/tags/McFarlane+Prize&amp;quot;&amp;amp;gt;McFarlane Prize&amp;amp;lt;/a&amp;amp;gt;&amp;amp;lt;/li&amp;amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
===Notes===&lt;br /&gt;
&lt;br /&gt;
# The root element is a div of class &amp;amp;#8220;hTagcloud&amp;amp;#8221;. Web connections front end developer Cameron Adams and I came up with this as a very early implementation of a potential proposal for a tagcloud microformat, and chose the name by analogy with hCard, etc.&lt;br /&gt;
# this contains an unordered list of class &amp;amp;#8220;popularity&amp;amp;#8221;. This allows for the extension to other class values for different kinds of cloud&lt;br /&gt;
# each tag is a list item, with a class value of &amp;amp;#8220;weightN&amp;amp;#8221; where n is an integer value of 1–5&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=icons&amp;diff=9875</id>
		<title>icons</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=icons&amp;diff=9875"/>
		<updated>2006-09-14T03:37:53Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt; Icons &amp;lt;/h1&amp;gt;&lt;br /&gt;
These icons can be used to depict various microformats in webpages or on the desktop.&lt;br /&gt;
&lt;br /&gt;
== Creators ==&lt;br /&gt;
* [http://factoryjoe.com/blog Chris Messina]&lt;br /&gt;
* [http://dmitry.baranovskiy.com Dmitry Baranovskiy]&lt;br /&gt;
&lt;br /&gt;
=== Copyright ===&lt;br /&gt;
Unless otherwise noted, these icons are licensed under the [http://creativecommons.org/licenses/by-sa/2.5/ Creative Commons Attribution-ShareAlike 2.5 license].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Icons ==&lt;br /&gt;
&lt;br /&gt;
=== Mac ===&lt;br /&gt;
[http://factoryjoe.com/blog/wp-content/uploads/2006/08/mf-icons.zip http://factoryjoe.com/blog/wp-content/uploads/2006/08/mf-icons-preview.png]&lt;br /&gt;
&lt;br /&gt;
These [http://factoryjoe.com/blog/wp-content/uploads/2006/08/mf-icons.zip icons] can be used for folders or files on your Mac. You can use a tool like [http://iconfactory.com/software/pixadex Pixadex] for managing and applying them.&lt;br /&gt;
&lt;br /&gt;
Created by [http://factoryjoe.com/blog Chris Messina]&lt;br /&gt;
=== PDF &amp;amp; SVG ===&lt;br /&gt;
[http://dmitry.baranovskiy.com/res/mf-logo.pdf http://dmitry.baranovskiy.com/i/pdffile.png] [http://dmitry.baranovskiy.com/res/mf-logo.svg http://dmitry.baranovskiy.com/i/svgfile.png]&lt;br /&gt;
&lt;br /&gt;
This logo looks pretty much as first icon of Chris’ set. You could open it in any bitmap or vector editing tools, such as Adobe Photoshop or Adobe Illustrator.&lt;br /&gt;
&lt;br /&gt;
Created by [http://dmitry.baranovskiy.com Dmitry Baranovskiy]&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=icons&amp;diff=8505</id>
		<title>icons</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=icons&amp;diff=8505"/>
		<updated>2006-09-14T00:31:16Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt; Icons &amp;lt;/h1&amp;gt;&lt;br /&gt;
These icons can be used to depict various microformats in webpages or on the desktop.&lt;br /&gt;
&lt;br /&gt;
== Creators ==&lt;br /&gt;
* [http://factoryjoe.com/blog Chris Messina]&lt;br /&gt;
* [http://dmitry.baranovskiy.com Dmitry Baranovskiy]&lt;br /&gt;
&lt;br /&gt;
=== Copyright ===&lt;br /&gt;
Unless otherwise noted, these icons are licensed under the [http://creativecommons.org/licenses/by-sa/2.5/ Creative Commons Attribution-ShareAlike 2.5 license].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Icons ==&lt;br /&gt;
&lt;br /&gt;
=== Mac ===&lt;br /&gt;
[http://factoryjoe.com/blog/wp-content/uploads/2006/08/mf-icons.zip http://factoryjoe.com/blog/wp-content/uploads/2006/08/mf-icons-preview.png]&lt;br /&gt;
&lt;br /&gt;
These [http://factoryjoe.com/blog/wp-content/uploads/2006/08/mf-icons.zip icons] can be used for folders or files on your Mac. You can use a tool like [http://iconfactory.com/software/pixadex Pixadex] for managing and applying them.&lt;br /&gt;
&lt;br /&gt;
Created by [http://factoryjoe.com/blog Chris Messina]&lt;br /&gt;
=== PDF ===&lt;br /&gt;
[http://dmitry.baranovskiy.com/res/mf-logo.pdf http://dmitry.baranovskiy.com/i/pdffile.png]&lt;br /&gt;
&lt;br /&gt;
This logo looks pretty much as first icon of Chris’ set. You could open it in any bitmap or vector editing tools, such as Adobe Photoshop or Adobe Illustrator.&lt;br /&gt;
&lt;br /&gt;
Created by [http://dmitry.baranovskiy.com Dmitry Baranovskiy]&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hcalendar-creator-issues&amp;diff=7552</id>
		<title>hcalendar-creator-issues</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hcalendar-creator-issues&amp;diff=7552"/>
		<updated>2006-07-20T01:04:52Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: /* Bug Reports */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt;hCalendar creator feedback&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page is for collecting bugs, suggested fixes, and feature requests for the [[hcalendar|hCalendar]] [http://microformats.org/code/hcalendar/creator creator]&lt;br /&gt;
&lt;br /&gt;
Please list your name, and indicate ''which'' version (even just a date and time helps) of the creator that you are providing feedback on.  Thanks!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Bug Reports ==&lt;br /&gt;
* dtend has format &amp;quot;2006620&amp;quot;, should be &amp;quot;20060620&amp;quot; ''reported by Dmitry Baranovskiy at 2006-07-20''&lt;br /&gt;
&lt;br /&gt;
== Suggested Tweaks and Fixes ==&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Feature Requests ==&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
* [[hcalendar|hCalendar specification]]&lt;br /&gt;
* [[hcalendar-feedback|hCalendar feedback]]&lt;br /&gt;
* [[hcard-creator-feedback|hCard creator feedback]]&lt;br /&gt;
* [[hreview-creator-feedback|hReview creator feedback]]&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hcard-creator-issues&amp;diff=7705</id>
		<title>hcard-creator-issues</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hcard-creator-issues&amp;diff=7705"/>
		<updated>2006-07-20T01:04:42Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: /* Bug Reports */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt;hCard creator feedback&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page is for collecting bugs, suggested fixes, and feature requests for the [[hcard|hCard]] [http://microformats.org/code/hcard/creator creator]&lt;br /&gt;
&lt;br /&gt;
Please list your name, and indicate ''which'' version (even just a date and time helps) of the creator that you are providing feedback on.  Thanks!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Bug Reports ==&lt;br /&gt;
* AIM screenname &amp;amp; YIM screenname overlap each other in Safari ver. 2.0.4 (419.3) (on the last WebKit it looks Ok, but still gap between these two labels is too small) ''reported by Dmitry Baranovskiy at 2006-07-20''&lt;br /&gt;
&lt;br /&gt;
== Suggested Tweaks and Fixes ==&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Feature Requests ==&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
* [[hcard|hCard specification]]&lt;br /&gt;
* [[hcard-feedback|hCard feedback]]&lt;br /&gt;
* [[hcalendar-creator-feedback|hCalendar creator feedback]]&lt;br /&gt;
* [[hreview-creator-feedback|hReview creator feedback]]&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hreview-creator-issues&amp;diff=7704</id>
		<title>hreview-creator-issues</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hreview-creator-issues&amp;diff=7704"/>
		<updated>2006-07-20T01:03:42Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: /* Suggested Tweaks and Fixes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt;hReview creator feedback&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page is for collecting bugs, suggested fixes, and feature requests for the [[hreview|hReview]] [http://microformats.org/code/hreview/creator creator]&lt;br /&gt;
&lt;br /&gt;
Please list your name, and indicate ''which'' version (even just a date and time helps) of the creator that you are providing feedback on.  Thanks!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Bug Reports ==&lt;br /&gt;
* word &amp;quot;date*&amp;quot; in &amp;quot;review date*&amp;quot; jumps on the next row and moves &amp;quot;reviewer*&amp;quot; down in Safari (var. 2.0.4 (419.3)). It looks like &amp;quot;review&amp;quot; is label for date, &amp;quot;date*&amp;quot; is label for text field and &amp;quot;reviewer*&amp;quot; is label for empty row. The same bug in the latest WebKit. ''reported by Dmitry Baranovskiy at 2006-07-20''&lt;br /&gt;
* I didn't noticed value of url field in generated code. ''reported by Dmitry Baranovskiy at 2006-07-20''&lt;br /&gt;
&lt;br /&gt;
== Suggested Tweaks and Fixes ==&lt;br /&gt;
*  Should &amp;quot;photo&amp;quot; be inside an &amp;quot;item&amp;quot; as well as &amp;quot;fn&amp;quot; and &amp;quot;url&amp;quot;? ''reported by Dmitry Baranovskiy at 2006-07-20''&lt;br /&gt;
&lt;br /&gt;
== Feature Requests ==&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
* [[hreview |hReview specification]]&lt;br /&gt;
* [[hreview-feedback|hReview feedback]]&lt;br /&gt;
* [[hcard-creator-feedback|hCard creator feedback]]&lt;br /&gt;
* [[hcalendar-creator-feedback|hCalendar creator feedback]]&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hreview-creator-issues&amp;diff=7548</id>
		<title>hreview-creator-issues</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hreview-creator-issues&amp;diff=7548"/>
		<updated>2006-07-20T01:02:31Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: /* Bug Reports */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt;hReview creator feedback&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page is for collecting bugs, suggested fixes, and feature requests for the [[hreview|hReview]] [http://microformats.org/code/hreview/creator creator]&lt;br /&gt;
&lt;br /&gt;
Please list your name, and indicate ''which'' version (even just a date and time helps) of the creator that you are providing feedback on.  Thanks!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Bug Reports ==&lt;br /&gt;
* word &amp;quot;date*&amp;quot; in &amp;quot;review date*&amp;quot; jumps on the next row and moves &amp;quot;reviewer*&amp;quot; down in Safari (var. 2.0.4 (419.3)). It looks like &amp;quot;review&amp;quot; is label for date, &amp;quot;date*&amp;quot; is label for text field and &amp;quot;reviewer*&amp;quot; is label for empty row. The same bug in the latest WebKit. ''reported by Dmitry Baranovskiy at 2006-07-20''&lt;br /&gt;
* I didn't noticed value of url field in generated code. ''reported by Dmitry Baranovskiy at 2006-07-20''&lt;br /&gt;
&lt;br /&gt;
== Suggested Tweaks and Fixes ==&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Feature Requests ==&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
* [[hreview |hReview specification]]&lt;br /&gt;
* [[hreview-feedback|hReview feedback]]&lt;br /&gt;
* [[hcard-creator-feedback|hCard creator feedback]]&lt;br /&gt;
* [[hcalendar-creator-feedback|hCalendar creator feedback]]&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hcalendar-creator-issues&amp;diff=7550</id>
		<title>hcalendar-creator-issues</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hcalendar-creator-issues&amp;diff=7550"/>
		<updated>2006-07-20T00:59:43Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: /* Bug Reports */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt;hCalendar creator feedback&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page is for collecting bugs, suggested fixes, and feature requests for the [[hcalendar|hCalendar]] [http://microformats.org/code/hcalendar/creator creator]&lt;br /&gt;
&lt;br /&gt;
Please list your name, and indicate ''which'' version (even just a date and time helps) of the creator that you are providing feedback on.  Thanks!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Bug Reports ==&lt;br /&gt;
* dtend has format &amp;quot;2006620&amp;quot;, should be &amp;quot;20060620&amp;quot; ''reported by Dmitry Baranovskiy at 2006-07-20''&lt;br /&gt;
&lt;br /&gt;
== Suggested Tweaks and Fixes ==&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Feature Requests ==&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
* [[hcalendar|hCalendar specification]]&lt;br /&gt;
* [[hcalendar-feedback|hCalendar feedback]]&lt;br /&gt;
* [[hcard-creator-feedback|hCard creator feedback]]&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hcard-creator-issues&amp;diff=7549</id>
		<title>hcard-creator-issues</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hcard-creator-issues&amp;diff=7549"/>
		<updated>2006-07-20T00:59:26Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: /* Bug Reports */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt;hCard creator feedback&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page is for collecting bugs, suggested fixes, and feature requests for the [[hcard|hCard]] [http://microformats.org/code/hcard/creator creator]&lt;br /&gt;
&lt;br /&gt;
Please list your name, and indicate ''which'' version (even just a date and time helps) of the creator that you are providing feedback on.  Thanks!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Bug Reports ==&lt;br /&gt;
* AIM screenname &amp;amp; YIM screenname overlap each other in Safari ver. 2.0.4 (419.3) (on the last WebKit it looks Ok, but still gap between these two labels is too small) ''reported by Dmitry Baranovskiy at 2006-07-20''&lt;br /&gt;
&lt;br /&gt;
== Suggested Tweaks and Fixes ==&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Feature Requests ==&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
* [[hcard|hCard specification]]&lt;br /&gt;
* [[hcard-feedback|hCard feedback]]&lt;br /&gt;
* [[hcalendar-creator-feedback|hCalendar creator feedback]]&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hreview-creator-issues&amp;diff=7547</id>
		<title>hreview-creator-issues</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hreview-creator-issues&amp;diff=7547"/>
		<updated>2006-07-20T00:57:00Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt;hReview creator feedback&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page is for collecting bugs, suggested fixes, and feature requests for the [[hreview|hReview]] [http://microformats.org/code/hreview/creator creator]&lt;br /&gt;
&lt;br /&gt;
Please list your name, and indicate ''which'' version (even just a date and time helps) of the creator that you are providing feedback on.  Thanks!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Bug Reports ==&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Suggested Tweaks and Fixes ==&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Feature Requests ==&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
* [[hreview |hReview specification]]&lt;br /&gt;
* [[hreview-feedback|hReview feedback]]&lt;br /&gt;
* [[hcard-creator-feedback|hCard creator feedback]]&lt;br /&gt;
* [[hcalendar-creator-feedback|hCalendar creator feedback]]&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hreview&amp;diff=7747</id>
		<title>hreview</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hreview&amp;diff=7747"/>
		<updated>2006-07-20T00:53:05Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: /* Implementations */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt; hReview 0.3 &amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[hreview|hReview]] is a simple, open, distributed format, suitable for embedding reviews (of products, services, businesses, events, etc.) in (X)HTML, Atom, RSS, and arbitrary XML. hReview is one of several [[microformats]] open standards.&lt;br /&gt;
&lt;br /&gt;
Want to get started with writing an [[hreview|hReview]]?  Use the [http://microformats.org/code/hreview/creator hReview creator] to write a review and publish it.&lt;br /&gt;
&lt;br /&gt;
== Microformats Draft Specification 2006-02-22 ==&lt;br /&gt;
&lt;br /&gt;
; Editor: [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]&lt;br /&gt;
; Authors: [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]&lt;br /&gt;
: [http://360.yahoo.com/alidiabali Ali Diab],[http://yahoo.com Yahoo! Inc.]&lt;br /&gt;
: [http://spaces.msn.com/members/ianmcallister/ Ian McAllister], [http://microsoft.com/ Microsoft Corporation]&lt;br /&gt;
: [http://journals.aol.com/panzerjohn/abstractioneer John Panzer], [http://www.aol.com America Online, Inc.]&lt;br /&gt;
: [http://ifindkarma.com/blog Adam Rifkin], [http://labs.commerce.net/ CommerceNet Labs]&lt;br /&gt;
: [http://sippey.typepad.com/ Michael Sippey], [http://sixapart.com Six Apart, Ltd.]&lt;br /&gt;
&lt;br /&gt;
Microformats [http://microformats.org/wiki/hreview#Copyright copyright] and [http://microformats.org/wiki/hreview#Patents patents] statements apply.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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 both numerous [[review-examples]] in the wild and earlier attempts at [[review-formats]], and have designed hReview around a simple minimal schema for reviews.  Feedback is encouraged on the [[hreview-feedback|hReview feedback]] page.&lt;br /&gt;
&lt;br /&gt;
=== Inspiration and Acknowledgments ===&lt;br /&gt;
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], Mark Nottingham, [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].&lt;br /&gt;
&lt;br /&gt;
=== Scope ===&lt;br /&gt;
Reviews consistently share several common fields.  Where possible hReview has been based on this minimal common subset.&lt;br /&gt;
&lt;br /&gt;
==== Out of scope ====&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The concept of a &amp;quot;universal object identifier&amp;quot;, 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.&lt;br /&gt;
&lt;br /&gt;
== Semantic XHTML Design Principles ==&lt;br /&gt;
{{semantic-xhtml-design-principles}}&lt;br /&gt;
&lt;br /&gt;
== Format ==&lt;br /&gt;
=== In General ===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Schema ===&lt;br /&gt;
The hReview schema consists of the following:&lt;br /&gt;
&lt;br /&gt;
* hReview ('''&amp;lt;code&amp;gt;hreview&amp;lt;/code&amp;gt;''')&lt;br /&gt;
** '''&amp;lt;code&amp;gt;version&amp;lt;/code&amp;gt;'''. optional. text.&lt;br /&gt;
** '''&amp;lt;code&amp;gt;summary&amp;lt;/code&amp;gt;'''. optional. text.&lt;br /&gt;
** item '''&amp;lt;code&amp;gt;type&amp;lt;/code&amp;gt;'''. optional. product | business | event | person | place | website | url.&lt;br /&gt;
** '''&amp;lt;code&amp;gt;item&amp;lt;/code&amp;gt;''' info. required. ('''&amp;lt;code&amp;gt;fn&amp;lt;/code&amp;gt;''' || '''&amp;lt;code&amp;gt;url&amp;lt;/code&amp;gt;''' || '''&amp;lt;code&amp;gt;photo&amp;lt;/code&amp;gt;''' ) | '''[[hcard|hCard]]''' (for person or business) | '''[[hcalendar|hCalendar]]''' (for event)&lt;br /&gt;
** '''&amp;lt;code&amp;gt;reviewer&amp;lt;/code&amp;gt;'''. optional. '''[[hcard|hCard]]'''.&lt;br /&gt;
** '''&amp;lt;code&amp;gt;dtreviewed&amp;lt;/code&amp;gt;'''. optional. ISO8601 absolute date time.&lt;br /&gt;
** '''&amp;lt;code&amp;gt;rating&amp;lt;/code&amp;gt;'''. optional. fixed point integer [1.0-5.0], with optional alternate '''&amp;lt;code&amp;gt;worst&amp;lt;/code&amp;gt;''' (default:1.0) and/or '''&amp;lt;code&amp;gt;best&amp;lt;/code&amp;gt;''' (default:5.0), also fixed point integers, and explicit '''&amp;lt;code&amp;gt;value&amp;lt;/code&amp;gt;'''.&lt;br /&gt;
** '''&amp;lt;code&amp;gt;description&amp;lt;/code&amp;gt;'''. optional. text with optional valid XHTML markup.&lt;br /&gt;
** tags. optional. keywords or phrases, using '''[[rel-tag]]''', each with optional rating.&lt;br /&gt;
** permalink. optional, using '''[[rel-bookmark]]''' and '''[[rel-self]]'''.&lt;br /&gt;
** license. optional, using '''[[rel-license]]'''.&lt;br /&gt;
&lt;br /&gt;
=== Field details ===&lt;br /&gt;
The fields of the hReview schema represent the following:&lt;br /&gt;
&lt;br /&gt;
'''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 &amp;quot;VERSION&amp;quot; as defined in vCard RFC2426 section &amp;quot;3.6.9 VERSION Type Definition&amp;quot;.  The value of this field for this specification is &amp;quot;0.3&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''summary''':: This optional field serves as a title for the review itself.&lt;br /&gt;
&lt;br /&gt;
'''item type''':: This optional field &amp;quot;type&amp;quot; provides the type of the item being reviewed, one of the following: product, business, event, person, place, website, url.  If omitted, then in some cases the item type may be inferred.  If the item is also an [[hcard|hCard]], then the item type is a &amp;quot;business&amp;quot; or a &amp;quot;person&amp;quot; based upon which of those the hCard represents.  If the item is also an [[hcalendar|hCalendar]] event, then the item type is an &amp;quot;event&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''item info''':: This required field MUST have at a minimum the name (&amp;quot;fn&amp;quot; - the formatted text corresponding to the name) of ''the'' item (an hReview describes only one item), SHOULD provide at least one URI (&amp;quot;url&amp;quot;) for the item, and MAY provide at least one URL to a photo or depiction (&amp;quot;photo&amp;quot;) of the item.  For items of type person or business, the item info (fn, url, photo) MUST be encapsulated in an [[hcard|hCard]].  For items of type event, the item info SHOULD be encapsulated in an [[hcalendar|hCalendar]] &amp;quot;vevent&amp;quot;.  Unique item IDs (e.g. ISBNs, UPCs) MAY be represented as a URN (&amp;quot;url&amp;quot;) for the item.&lt;br /&gt;
&lt;br /&gt;
'''reviewer''':: The optional field specifies the person who authored the review.  If the reviewer is specified, an hCard representing the reviewer MUST be provided.  For anonymous reviews, use &amp;quot;anonymous&amp;quot; (without quotes) for the full name of the reviewer.  If no &amp;quot;reviewer&amp;quot; is found inside the hReview, parsers should look outside the hReview, in the context of the page, for the &amp;quot;reviewer&amp;quot;. If there is no &amp;quot;reviewer&amp;quot; outside either, then parsers should use the author defined by the containing document language, e.g. for (X)HTML documents, the &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;address&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; contact info for the page (which is ideally marked up as an [[hcard|hCard]] as well), for Atom 1.0 the &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;entry&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;author&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; if present and if not the &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;feed&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;author&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;, for RSS the &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;author&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; inside the containing &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;item&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; element.&lt;br /&gt;
&lt;br /&gt;
'''dtreviewed''':: This optional field when present 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.  If dtreviewed is absent from the hReview, then look outside the hReview, in the surrounding context.  If the context is an [[hatom|hAtom]] entry, use its &amp;quot;published&amp;quot; (or &amp;quot;updated&amp;quot; if that is missing) datetime as the dtreviewed, if not present on the entry, use the &amp;quot;published&amp;quot; (or &amp;quot;updated&amp;quot; if that is missing) of the feed.  Otherwise use the creation date (or modified date if that is missing) information according to the containing document language (e.g. &amp;quot;published&amp;quot;/&amp;quot;updated&amp;quot; similarly for Atom feeds), then protocol (e.g. HTTP Last-Modified, or file system last modified datetime) as the dtreviewed.&lt;br /&gt;
&lt;br /&gt;
'''rating''':: The rating is a fixed point integer (one decimal point of precision) from 1.0 to 5.0 inclusive indicating a rating for the item, higher indicating a better rating by default. Optionally a different integral &amp;quot;worst&amp;quot; value and/or &amp;quot;best&amp;quot; value MAY be specified (e.g. 6 from 0-10).  The &amp;quot;best&amp;quot; value may be numerically smaller than the &amp;quot;worst&amp;quot; value.&lt;br /&gt;
&lt;br /&gt;
'''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.&lt;br /&gt;
&lt;br /&gt;
'''tags''':: Tags are represented using a list of keywords or phrases (using the [[rel-tag]] 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 [[rel-tag]], 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 also invert this structure for the same semantic if it is more convenient for their markup, that is, place the [[rel-tag]] inside a rating to indicate a rated tag.  Note: rated tags should ideally use a tag space that explains what the ratings for that tag mean. E.g. Food:18/30 should link to a tags space for Food that explains what an 18 out of 30 means for the Food tag.&lt;br /&gt;
&lt;br /&gt;
'''permalink''':: This optional field is a URL for the hReview.  In addition to using the &amp;lt;code&amp;gt;&amp;lt;a href&amp;gt;&amp;lt;/code&amp;gt; tag for this field, the attribute &amp;lt;code&amp;gt;rel=&amp;quot;self bookmark&amp;quot;&amp;lt;/code&amp;gt; MUST be used to indicate that the hyperlink is a permalink for the review itself.  If the hyperlink already contains a &amp;lt;code&amp;gt;rel&amp;lt;/code&amp;gt; attribute, then the values &amp;lt;code&amp;gt;self&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;bookmark&amp;lt;/code&amp;gt; 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 &amp;quot;permalink&amp;quot; on the element representing the permalink, but are not required to do so.&lt;br /&gt;
&lt;br /&gt;
The following field names have been reused from the [[hcard|hCard]] and [[hcalendar|hCalendar]] microformats: &amp;lt;code&amp;gt;version, summary, fn, url, email, photo, description, categories&amp;lt;/code&amp;gt;.  In addition, items and reviewers described by hCards MAY contain any hCard field.  The rel value &amp;quot;self&amp;quot; has been reused from the [http://atompub.org/2005/07/11/draft-ietf-atompub-format-10.html Atom 1.0 specification].&lt;br /&gt;
&lt;br /&gt;
'''license''':: This optional field links to the license under which the contents of the hReview itself is licensed, using the '''[[rel-license]]''' microformat.&lt;br /&gt;
&lt;br /&gt;
=== More Semantic Equivalents ===&lt;br /&gt;
&lt;br /&gt;
For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.: &lt;br /&gt;
&lt;br /&gt;
* For any &amp;quot;url&amp;quot;, use &amp;lt;code&amp;gt;&amp;lt;a class=&amp;quot;url&amp;quot; href=&amp;quot;...&amp;quot;&amp;gt;...&amp;lt;/a&amp;gt;&amp;lt;/code&amp;gt; inside the element with the class name 'hreview' in hReview. &lt;br /&gt;
* Similarly, any &amp;quot;email&amp;quot;, use &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;a class=&amp;quot;email&amp;quot; href=&amp;quot;mailto:...&amp;quot;&amp;gt;...&amp;lt;/a&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; &lt;br /&gt;
* And for &amp;quot;photo&amp;quot;, use &amp;lt;code&amp;gt;&amp;lt;img class=&amp;quot;photo&amp;quot; src=&amp;quot;...&amp;quot; alt=&amp;quot;Photo of ...&amp;quot; /&amp;gt;&amp;lt;/code&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Ratings are often presented either as a set of images or characters, e.g. &amp;quot;***&amp;quot;.  For these, the &amp;lt;code&amp;gt;&amp;amp;lt;abbr&amp;amp;gt;&amp;lt;/code&amp;gt; element is particularly useful, as such characters are an abbreviation for the precise rating, e.g. &amp;lt;code&amp;gt;&amp;amp;lt;abbr class=&amp;quot;rating&amp;quot; title=&amp;quot;3&amp;quot;&amp;amp;gt;***&amp;amp;lt;/abbr&amp;amp;gt;&amp;lt;/code&amp;gt;.  This is further explored in the next section.&lt;br /&gt;
&lt;br /&gt;
==== Language ====&lt;br /&gt;
* To explicitly convey the natural language that an hReview is written in, use the standard (X)HTML 'lang' attribute on the element with class=&amp;quot;hreview&amp;quot;, e.g. &amp;lt;code&amp;gt;&amp;amp;lt;div class=&amp;quot;hreview&amp;quot; lang=&amp;quot;en&amp;quot;&amp;amp;gt; ... &amp;amp;lt;/div&amp;amp;gt;&amp;lt;/code&amp;gt; If portions of an hReview (e.g. the item name) are in a different language, use the 'lang' attribute on those portions.&lt;br /&gt;
* hReview processors which need to handle the language of reviews MUST process the standard (X)HTML 'lang' attribute as specified.&lt;br /&gt;
&lt;br /&gt;
=== Human vs. Machine Readable ===&lt;br /&gt;
If an &amp;lt;code&amp;gt;&amp;amp;lt;abbr&amp;gt;&amp;lt;/code&amp;gt; element is used for a property, then its '&amp;lt;code&amp;gt;title&amp;lt;/code&amp;gt;' 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. &lt;br /&gt;
&lt;br /&gt;
Similarly, if an &amp;lt;code&amp;gt;&amp;lt;img /&amp;gt;&amp;lt;/code&amp;gt; element is used for one or more properties, it MUST be treated as follows: &lt;br /&gt;
&lt;br /&gt;
# For the &amp;quot;photo&amp;quot; property and any other property that takes a URL as its value, the &amp;lt;code&amp;gt;src=&amp;quot;...&amp;quot;&amp;lt;/code&amp;gt; attribute provides the property value. &lt;br /&gt;
# For other properties, the &amp;lt;code&amp;gt;&amp;lt;img /&amp;gt;&amp;lt;/code&amp;gt; element's '&amp;lt;code&amp;gt;alt&amp;lt;/code&amp;gt;' attribute is the value of the property.&lt;br /&gt;
&lt;br /&gt;
=== Object Includes ===&lt;br /&gt;
&lt;br /&gt;
hReview 0.3 includes support for the object [[include-pattern]].&lt;br /&gt;
&lt;br /&gt;
Often a single page lists an item, and then several reviews for that item.  In order to avoid having to repeat the item info for each review of the item, the first review should be marked up as an hReview, with a unique &amp;quot;id&amp;quot; attribute on the item info, and then following reviews should use the object [[include-pattern]] to include the item info from the first review.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Notes ===&lt;br /&gt;
This section is informative.&lt;br /&gt;
&lt;br /&gt;
* 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 which the publisher may explicitly specify using [[rel-license]] as specified above.&lt;br /&gt;
* The enumerated list of item types is under development and may be extended.&lt;br /&gt;
* Each type may have custom hReview fields that follow the common set.&lt;br /&gt;
* Additional details about a particular item should be specified with the rest of the item's info at the URL provided for the item.&lt;br /&gt;
* Most rating systems use the range 1.0 to 5.0, and most of those represent the rating as a number (and possibly half) of stars.  Sites may use whatever graphic they wish to represent the rating.&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
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.  &lt;br /&gt;
&lt;br /&gt;
Want to get started with writing an [[hreview|hReview]]?  Use the [http://microformats.org/code/hreview/creator hReview creator] to write a review and publish it on your blog.&lt;br /&gt;
&lt;br /&gt;
=== Restaurant reviews ===&lt;br /&gt;
&lt;br /&gt;
Here is an example of a simple online restaurant review:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;div&amp;gt;&lt;br /&gt;
 &amp;lt;span&amp;gt;5 stars out of 5 stars&amp;lt;/span&amp;gt;&lt;br /&gt;
 &amp;lt;h4&amp;gt;Crepes on Cole is awesome&amp;lt;/h4&amp;gt;&lt;br /&gt;
 &amp;lt;span&amp;gt;Reviewer: &amp;lt;span&amp;gt;Tantek&amp;lt;/span&amp;gt; - April 18, 2005&amp;lt;/span&amp;gt;&lt;br /&gt;
 &amp;lt;blockquote&amp;gt;&amp;lt;p&amp;gt;&lt;br /&gt;
  Crepes on Cole is one of the best little creperies in San Francisco. &lt;br /&gt;
  Excellent food and service. Plenty of tables in a variety of sizes &lt;br /&gt;
  for parties large and small.  Window seating makes for excellent &lt;br /&gt;
  people watching to/from the N-Judah which stops right outside.  &lt;br /&gt;
  I've had many fun social gatherings here, as well as gotten &lt;br /&gt;
  plenty of work done thanks to neighborhood WiFi.&lt;br /&gt;
 &amp;lt;/p&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
 &amp;lt;p&amp;gt;Visit date: &amp;lt;span&amp;gt;April 2005&amp;lt;/span&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
 &amp;lt;p&amp;gt;Food eaten: &amp;lt;span&amp;gt;Florentine crepe&amp;lt;/span&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Adding hReview to this review is quite simple:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;hreview&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;span&amp;gt;&amp;lt;span class=&amp;quot;rating&amp;quot;&amp;gt;5&amp;lt;/span&amp;gt; out of 5 stars&amp;lt;/span&amp;gt;&lt;br /&gt;
 &amp;lt;h4 class=&amp;quot;summary&amp;quot;&amp;gt;Crepes on Cole is awesome&amp;lt;/h4&amp;gt;&lt;br /&gt;
 &amp;lt;span class=&amp;quot;reviewer vcard&amp;quot;&amp;gt;Reviewer: &amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;Tantek&amp;lt;/span&amp;gt; - &lt;br /&gt;
 &amp;lt;abbr class=&amp;quot;dtreviewed&amp;quot; title=&amp;quot;20050418T2300-0700&amp;quot;&amp;gt;April 18, 2005&amp;lt;/abbr&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
 &amp;lt;div class=&amp;quot;description item vcard&amp;quot;&amp;gt;&amp;lt;p&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;fn org&amp;quot;&amp;gt;Crepes on Cole&amp;lt;/span&amp;gt; is one of the best little &lt;br /&gt;
  creperies in &amp;lt;span class=&amp;quot;adr&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;locality&amp;quot;&amp;gt;San Francisco&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;.&lt;br /&gt;
  Excellent food and service. Plenty of tables in a variety of sizes &lt;br /&gt;
  for parties large and small.  Window seating makes for excellent &lt;br /&gt;
  people watching to/from the N-Judah which stops right outside.  &lt;br /&gt;
  I've had many fun social gatherings here, as well as gotten &lt;br /&gt;
  plenty of work done thanks to neighborhood WiFi.&lt;br /&gt;
 &amp;lt;/p&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
 &amp;lt;p&amp;gt;Visit date: &amp;lt;span&amp;gt;April 2005&amp;lt;/span&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
 &amp;lt;p&amp;gt;Food eaten: &amp;lt;span&amp;gt;Florentine crepe&amp;lt;/span&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
This sample hReview could be rendered like this:&lt;br /&gt;
&lt;br /&gt;
5 stars out of 5 stars&amp;lt;br /&amp;gt;&lt;br /&gt;
'''Crepes on Cole is awesome'''&amp;lt;br /&amp;gt;&lt;br /&gt;
Reviewer: Tantek - April 18, 2005&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Visit date: April 2005&amp;lt;br /&amp;gt;&lt;br /&gt;
Food eaten: Florentine crepe&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Multidimensional Restaurant Review ====&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Here is one such review in text format:&lt;br /&gt;
&lt;br /&gt;
 Cafe Borrone&lt;br /&gt;
 &lt;br /&gt;
 1010 El Camino Real, Menlo Park, CA 94025, +1-650-327-0830;&lt;br /&gt;
 cafeborrone.com&lt;br /&gt;
 &lt;br /&gt;
 Food: 18/30; Ambience: 19/30; Service: 15/30; Price: $$...&lt;br /&gt;
 &lt;br /&gt;
 This cafe is a welcoming oasis on the Peninsula.  It even has a fountain&lt;br /&gt;
 outside which cloaks the nearby sounds of El Camino traffic.  Next door to a  &lt;br /&gt;
 superb indy bookstore, Cafe Borrone is an ideal spot to grab a coffee or a &lt;br /&gt;
 snack to accompany a newly purchased book or imported periodical.  Soups and &lt;br /&gt;
 sandwich specials rotate daily.  The corn chowder with croutons and big &lt;br /&gt;
 chunks of cheese goes especially well with a freshly toasted mini-baguette.  &lt;br /&gt;
 Evenings are often crowded and may require sharing a table with a perfect &lt;br /&gt;
 stranger.  Espresso afficionados will appreciate the Illy coffee.  Noise &lt;br /&gt;
 levels can vary from peaceful in the late mornings to nearly overwhelming on &lt;br /&gt;
 jazz band nights.&lt;br /&gt;
&lt;br /&gt;
As an hReview:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;hreview&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;div class=&amp;quot;item vcard&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;div class=&amp;quot;fn org summary&amp;quot;&amp;gt;Cafe Borrone&amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;adr&amp;quot;&amp;gt;&lt;br /&gt;
   &amp;lt;span class=&amp;quot;street-address&amp;quot;&amp;gt;1010 El Camino Real&amp;lt;/span&amp;gt;,&lt;br /&gt;
   &amp;lt;span class=&amp;quot;locality&amp;quot;&amp;gt;Menlo Park&amp;lt;/span&amp;gt;,&lt;br /&gt;
   &amp;lt;span class=&amp;quot;region&amp;quot;&amp;gt;CA&amp;lt;/span&amp;gt;&lt;br /&gt;
   &amp;lt;span class=&amp;quot;postal-code&amp;quot;&amp;gt;94025&amp;lt;/span&amp;gt;,&lt;br /&gt;
  &amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;+1-650-327-0830&amp;lt;/span&amp;gt;;&lt;br /&gt;
  &amp;lt;a class=&amp;quot;url&amp;quot; href=&amp;quot;http://cafeborrone.com&amp;quot;&amp;gt;cafeborrone.com&amp;lt;/a&amp;gt;&lt;br /&gt;
 &amp;lt;/div&amp;gt;&lt;br /&gt;
 &amp;lt;ul class=&amp;quot;categories&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;li class=&amp;quot;rating&amp;quot;&amp;gt;&amp;lt;a href=&amp;quot;http://en.wikipedia.org/wiki/Food&amp;quot; rel=&amp;quot;tag&amp;quot;&amp;gt;&lt;br /&gt;
   Food: &amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt;18&amp;lt;/span&amp;gt;/&amp;lt;span class=&amp;quot;best&amp;quot;&amp;gt;30&amp;lt;/span&amp;gt;&amp;lt;/a&amp;gt;;&amp;lt;/li&amp;gt;&lt;br /&gt;
  &amp;lt;li class=&amp;quot;rating&amp;quot;&amp;gt;&amp;lt;a href=&amp;quot;http://flickr.com/photos/tags/Ambience&amp;quot; rel=&amp;quot;tag&amp;quot;&amp;gt;&lt;br /&gt;
   Ambience: &amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt;19&amp;lt;/span&amp;gt;/&amp;lt;span class=&amp;quot;best&amp;quot;&amp;gt;30&amp;lt;/span&amp;gt;&amp;lt;/a&amp;gt;;&amp;lt;/li&amp;gt;&lt;br /&gt;
  &amp;lt;li class=&amp;quot;rating&amp;quot;&amp;gt;&amp;lt;a href=&amp;quot;http://en.wikipedia.org/wiki/Service&amp;quot; rel=&amp;quot;tag&amp;quot;&amp;gt;&lt;br /&gt;
   Service: &amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt;15&amp;lt;/span&amp;gt;/&amp;lt;span class=&amp;quot;best&amp;quot;&amp;gt;30&amp;lt;/span&amp;gt;&amp;lt;/a&amp;gt;;&amp;lt;/li&amp;gt;&lt;br /&gt;
  &amp;lt;li class=&amp;quot;rating&amp;quot;&amp;gt;&amp;lt;a href=&amp;quot;http://en.wikipedia.org/wiki/Price&amp;quot; rel=&amp;quot;tag&amp;quot;&amp;gt;&lt;br /&gt;
   Price: &amp;lt;abbr class=&amp;quot;value&amp;quot; title=&amp;quot;2&amp;quot;&amp;gt;$$&amp;lt;/abbr&amp;gt;...&amp;lt;/a&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
 &amp;lt;/ul&amp;gt;&lt;br /&gt;
 &amp;lt;div class=&amp;quot;description&amp;quot;&amp;gt;&amp;lt;p&amp;gt;&lt;br /&gt;
  This &amp;lt;abbr class=&amp;quot;type&amp;quot; title=&amp;quot;business&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;a href=&amp;quot;http://en.wikipedia.org/wiki/cafe&amp;quot; rel=&amp;quot;tag&amp;quot;&amp;gt;cafe&amp;lt;/a&amp;gt;&amp;lt;/abbr&amp;gt; &lt;br /&gt;
  is a welcoming oasis on the Peninsula.  &lt;br /&gt;
  It even has a fountain outside which nearly eliminates &lt;br /&gt;
  the sounds of El Camino traffic.  Next door to a superb indy bookstore, &lt;br /&gt;
  Cafe Borrone is an ideal spot to grab a &lt;br /&gt;
  &amp;lt;a href=&amp;quot;http://en.wikipedia.org/wiki/coffee&amp;quot; rel=&amp;quot;tag&amp;quot;&amp;gt;coffee&amp;lt;/a&amp;gt; &lt;br /&gt;
  or a meal to accompany a newly purchased book or imported periodical.  &lt;br /&gt;
  &amp;lt;a href=&amp;quot;http://technorati.com/tag/soup&amp;quot; rel=&amp;quot;tag&amp;quot;&amp;gt;Soups&amp;lt;/a&amp;gt; and &lt;br /&gt;
  &amp;lt;a href=&amp;quot;http://technorati.com/tag/sandwich&amp;quot; rel=&amp;quot;tag&amp;quot;&amp;gt;sandwich&amp;lt;/a&amp;gt; &lt;br /&gt;
  specials rotate daily.  The corn chowder with croutons and big chunks of cheese &lt;br /&gt;
  goes especially well with a freshly toasted mini-baguette.  Evenings are &lt;br /&gt;
  often crowded and may require sharing a table with a perfect stranger. &lt;br /&gt;
  &amp;lt;a href=&amp;quot;http://flickr.com/photos/tags/espresso&amp;quot; rel=&amp;quot;tag&amp;quot;&amp;gt;Espresso&amp;lt;/a&amp;gt; &lt;br /&gt;
  afficionados will appreciate the &lt;br /&gt;
  &amp;lt;a href=&amp;quot;http://en.wikipedia.org/wiki/Illy&amp;quot; rel=&amp;quot;tag&amp;quot;&amp;gt;Illy&amp;lt;/a&amp;gt; coffee.  &lt;br /&gt;
  Noise levels can vary from peaceful in the late mornings to nearly overwhelming on &lt;br /&gt;
  &amp;lt;a href=&amp;quot;http://en.wikipedia.org/wiki/jazz&amp;quot; rel=&amp;quot;tag&amp;quot;&amp;gt;jazz&amp;lt;/a&amp;gt; band nights.&lt;br /&gt;
 &amp;lt;/p&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
 Review (&amp;lt;a href=&amp;quot;http://microformats.org/wiki/hreview&amp;quot;&amp;gt; &lt;br /&gt;
  hReview v&amp;lt;span class=&amp;quot;version&amp;quot;&amp;gt;0.3&amp;lt;/span&amp;gt;&amp;lt;/a&amp;gt;)&lt;br /&gt;
 by &amp;lt;span class=&amp;quot;reviewer vcard&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;anonymous&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;, &lt;br /&gt;
 &amp;lt;abbr class=&amp;quot;dtreviewed&amp;quot; title=&amp;quot;20050428T2130-0700&amp;quot;&amp;gt;April 28th, 2005&amp;lt;/abbr&amp;gt;.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With an accompanying CSS style sheet like:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
a.url { display:block }&lt;br /&gt;
ul.categories { margin:1em 0; padding:0 }&lt;br /&gt;
.categories li { display:inline }&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This hReview could be presented similar to the original text:&lt;br /&gt;
&lt;br /&gt;
Cafe Borrone&amp;lt;br /&amp;gt;&lt;br /&gt;
1010 El Camino Real, Menlo Park, CA 94025, +1-650-327-0830;&amp;lt;br /&amp;gt;&lt;br /&gt;
[http://cafeborrone.com/ cafeborrone.com]&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
[http://en.wikipedia.org/wiki/Food Food: 18/30];&lt;br /&gt;
[http://flickr.com/photos/tags/Ambience Ambience: 19/30];&lt;br /&gt;
[http://en.wikipedia.org/wiki/Service Service: 15/30];&lt;br /&gt;
[http://en.wikipedia.org/wiki/Price Price: $$...]&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Review ([http://microformats.org/wiki/hreview hReview v0.3]) by anonymous, April 28th, 2005.&lt;br /&gt;
&lt;br /&gt;
=== Product review ===&lt;br /&gt;
Here is an example of a product review:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;div&amp;gt;&lt;br /&gt;
 &amp;lt;a href=&amp;quot;http://www.amazon.com/exec/obidos/ASIN/B000089CJI/&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;img src=&amp;quot;http://images.amazon.com/images/P/B000089CJI.01._SCTHUMBZZZ_.jpg&amp;quot; &lt;br /&gt;
              alt=&amp;quot;Album cover photo: The Postal Service: Give Up.&amp;quot; /&amp;gt;&lt;br /&gt;
 The Postal Service: Give Up&amp;lt;/a&amp;gt;&lt;br /&gt;
 &amp;lt;blockquote&amp;gt;&amp;lt;p&amp;gt;&lt;br /&gt;
   &amp;quot;The people thought they were just being rewarded for treating others &lt;br /&gt;
    as they like to be treated, for obeying stop signs and curing diseases, &lt;br /&gt;
    for mailing letters with the address of the sender... Don't wake me, &lt;br /&gt;
    I plan on sleeping in...&amp;quot;&lt;br /&gt;
   &amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;&lt;br /&gt;
   &amp;quot;Nothing Better&amp;quot; is a great track on this album, too... &lt;br /&gt;
 &amp;lt;/p&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
 (*****)&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;hreview&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;a class=&amp;quot;item url&amp;quot; href=&amp;quot;http://www.amazon.com/exec/obidos/ASIN/B000089CJI/&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;img src=&amp;quot;http://images.amazon.com/images/P/B000089CJI.01._SCTHUMBZZZ_.jpg&amp;quot; &lt;br /&gt;
       alt=&amp;quot;Album cover photo: The Postal Service: Give Up. &amp;quot; &lt;br /&gt;
       class=&amp;quot;photo&amp;quot; /&amp;gt;&lt;br /&gt;
 &amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;The Postal Service: Give Up&amp;lt;/span&amp;gt;&amp;lt;/a&amp;gt;&lt;br /&gt;
 &amp;lt;div class=&amp;quot;description&amp;quot;&amp;gt;&amp;lt;p&amp;gt;&lt;br /&gt;
    &amp;quot;The people thought they were just being rewarded for treating others &lt;br /&gt;
     as they like to be treated, for obeying stop signs and curing diseases, &lt;br /&gt;
     for mailing letters with the address of the sender... Don't wake me, &lt;br /&gt;
     I plan on sleeping in...&amp;quot;&lt;br /&gt;
   &amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;&lt;br /&gt;
   &amp;quot;Nothing Better&amp;quot; is a great track on this album, too... &lt;br /&gt;
 &amp;lt;/p&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
 (&amp;lt;abbr class=&amp;quot;rating&amp;quot; title=&amp;quot;5&amp;quot;&amp;gt;*****&amp;lt;/abbr&amp;gt;)&lt;br /&gt;
 &amp;lt;p class=&amp;quot;reviewer vcard&amp;quot;&amp;gt;Review by &lt;br /&gt;
  &amp;lt;a class=&amp;quot;url fn&amp;quot; href=&amp;quot;http://ifindkarma.com/blog/&amp;quot;&amp;gt;Adam Rifkin&amp;lt;/a&amp;gt;, &lt;br /&gt;
  &amp;lt;abbr class=&amp;quot;dtreviewed&amp;quot; title=&amp;quot;200502&amp;quot;&amp;gt;February 2005&amp;lt;/abbr&amp;gt;&lt;br /&gt;
 &amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And this hReview might be presented like this:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[Album cover photo: ]&lt;br /&gt;
[The Postal Service:]&lt;br /&gt;
[      Give Up      ]&lt;br /&gt;
&lt;br /&gt;
The Postal Service: Give Up&lt;br /&gt;
&lt;br /&gt;
&amp;quot;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...&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Nothing Better&amp;quot; is a great track on this album, too...&lt;br /&gt;
&lt;br /&gt;
(*****)&lt;br /&gt;
&lt;br /&gt;
Review by Adam Rifkin, February 2005.&lt;br /&gt;
&lt;br /&gt;
=== Movie Review ===&lt;br /&gt;
Finally, here is an example of a movie review.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;div&amp;gt;&lt;br /&gt;
 &amp;lt;span&amp;gt;anonymous, April 18th, 2005&amp;lt;/span&amp;gt;&lt;br /&gt;
 &amp;lt;div&amp;gt;&lt;br /&gt;
  &amp;lt;a lang=&amp;quot;zh&amp;quot; href=&amp;quot;http://www.imdb.com/title/tt0299977/&amp;quot;&amp;gt;&lt;br /&gt;
  Ying Xiong (&amp;lt;span lang=&amp;quot;en&amp;quot;&amp;gt;HERO&amp;lt;/span&amp;gt;)&lt;br /&gt;
  &amp;lt;/a&amp;gt;&lt;br /&gt;
 &amp;lt;/div&amp;gt;&lt;br /&gt;
 &amp;lt;div&amp;gt;Rating: 4 out of 5&amp;lt;/div&amp;gt;&lt;br /&gt;
 &amp;lt;blockquote&amp;gt;&amp;lt;p&amp;gt;&lt;br /&gt;
  This movie has great visuals and music.&lt;br /&gt;
 &amp;lt;/p&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With hReview:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;hreview&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;span class=&amp;quot;reviewer vcard&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;anonymous&amp;lt;/span&amp;gt;, &lt;br /&gt;
  &amp;lt;abbr class=&amp;quot;dtreviewed&amp;quot; title=&amp;quot;20050418&amp;quot;&amp;gt;April 18th, 2005&amp;lt;/abbr&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&lt;br /&gt;
 &amp;lt;div class=&amp;quot;item&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;a lang=&amp;quot;zh&amp;quot; class=&amp;quot;url fn&amp;quot; href=&amp;quot;http://www.imdb.com/title/tt0299977/&amp;quot;&amp;gt;&lt;br /&gt;
  Ying Xiong (&amp;lt;span lang=&amp;quot;en&amp;quot;&amp;gt;HERO&amp;lt;/span&amp;gt;)&lt;br /&gt;
  &amp;lt;/a&amp;gt;&lt;br /&gt;
 &amp;lt;/div&amp;gt;&lt;br /&gt;
 &amp;lt;div&amp;gt;Rating: &amp;lt;span class=&amp;quot;rating&amp;quot;&amp;gt;4&amp;lt;/span&amp;gt; out of 5&amp;lt;/div&amp;gt;&lt;br /&gt;
 &amp;lt;div class=&amp;quot;description&amp;quot;&amp;gt;&amp;lt;p&amp;gt;&lt;br /&gt;
  This movie has great music and visuals.&lt;br /&gt;
 &amp;lt;/p&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Which could be presented like this:&lt;br /&gt;
&lt;br /&gt;
anonymous, April 18th, 2005&amp;lt;br /&amp;gt;&lt;br /&gt;
Ying Xiong (HERO)&amp;lt;br /&amp;gt;&lt;br /&gt;
Rating: 4 out of 5&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This movie has great music and visuals.&lt;br /&gt;
&lt;br /&gt;
== Examples in the wild ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
The following sites have published hReviews, and thus are a great place to start for anyone looking for examples &amp;quot;in the wild&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
Want to get started with writing an [[hreview|hReview]]?  Use the [http://microformats.org/code/hreview/creator hReview creator] to write a review and publish it on your blog.&lt;br /&gt;
* [http://local.yahoo.com Yahoo Local] now supports hReviews for all the user feedback and ratings about places in their search results&lt;br /&gt;
*[http://corkd.com/ Cork'd] is a community site for reviewing and sharing wine.  Member-created &amp;quot;Tasting Notes&amp;quot; are published using hReview.&lt;br /&gt;
*[[User:ChrisCasciano]] has started using hReview in his blog postings including these reviews of [http://chunkysoup.net/article/211/TechnoratisNewToys Pingerati and Technorati Microformat Search].&lt;br /&gt;
*[http://www.judysbook.com/ Judy's Book] is a local reviews community.  All reviews are published in hReview format, and all business listings and members (review authors) in the hCard format.&lt;br /&gt;
*[http://www.judysbook.com/ Judy's Book] is a local reviews community.  All reviews are published in hReview format, and all business listings and members (review authors) in the hCard format.&lt;br /&gt;
* [http://tech.yahoo.com/ Yahoo! Tech] has launched with hReview markup on all their reviews! Hat tips: [http://nerddawg.blogspot.com/2006/05/hreview-microformat-on-yahoo-tech.html Ashish Shetty] and [http://jeremy.zawodny.com/blog/archives/006729.html Jeremy Zawodny] both via [http://www.moskalyuk.com/blog/yahoo-tech-tip-of-the-day/1058 Alex Moskalyuk].  [http://jeremy.zawodny.com/blog/archives/006729.html#comment-27779 Alex says]: &amp;quot;when we launched, the press reported on 300,000 tech products in our database. Some popular items, like [http://tech.yahoo.com/pr/apple-ipod-video-30gb-black-mp3-player/1992981873 this Apple iPod], have over 200 reviews.&amp;quot;&lt;br /&gt;
* [http://3spots.blogspot.com/2006/05/social-bookmarking-smarking.html 3spots: Social + bookMARKING = Smarking] has an hReview of [http://smarking.com/ Smarking.com] (a social bookmarking service) which marks up their tagged links with [[xfolk|xFolk]].&lt;br /&gt;
*[http://www.pacificspirit.com Dave Orchard] provides hreview marked [http://www.pacificspirit.com/Restaurants-Vancouver.html Vancouver Restaurant reviews]&lt;br /&gt;
*[http://3spots.blogspot.com/2006/04/what-is-wikio-definitely-web-20-but.html hReview of Wikio]&lt;br /&gt;
*[http://jg.typepad.com/ciel/ Joan] has published [http://jg.typepad.com/ciel/2006/02/daniel_bouluds_.html an hReview of Garçon]&lt;br /&gt;
*[http://zipingo.typepad.com/ Zipingo Team Blog], a collaborative blog by the Zipingo Product Development Team at Intuit, used the hReview format to tag [http://zipingo.typepad.com/my_weblog/2005/12/finding_an_elec.html the backstory] of a review on a San Mateo electrician, written by one of the Zipingo team members ZipingoJim. Jim's post also links to his review on [http://www.zipingo.com Zipingo], a consumer opinion site.&lt;br /&gt;
* [http://mincedmedia.blogspot.com/ Minced Media], a media blog by author/writer [http://www.kimbayne.com Kim M. Bayne], used the hReview format to tag her rant about [http://mincedmedia.blogspot.com/2005/09/old-yeller.html customer service]. Future reviews of business and media will contain hReview.&lt;br /&gt;
* [http://ukfilmreview.blogspot.com/ UK Film Review] a new blog using hReview format to review Films and DVD releases in the UK&lt;br /&gt;
* [http://www.debaser.it/ DeBaser.it] publishes music reviews (in Italian) supporting hReview.&lt;br /&gt;
* [http://blog.ftwr.co.uk/ Peter Westwood] posted an [http://blog.ftwr.co.uk/archives/2006/01/05/the-fox-inn/ hReview of The Fox Inn]&lt;br /&gt;
* [http://www.livejournal.com/users/danieljohn/ Daniel John] provides a [http://www.livejournal.com/users/danieljohn/58674.html scathing hReview of CIBC].&lt;br /&gt;
* [http://uk.movies.yahoo.com/movie-reviews/ Yahoo UK Movie Reviews] now supports hReview on all (&amp;gt;2000) reviews, e.g. [http://uk.movies.yahoo.com/h/Harry-Potter-and-the-Goblet-of-Fire/review-41195.html Harry Potter and the Goblet of Fire Review]&lt;br /&gt;
* [http://adam.typepad.com/impossiblethings/ Adam Hertz] wrote hReviews of [http://adam.typepad.com/impossiblethings/2005/11/soluna.html Soluna] and [http://adam.typepad.com/impossiblethings/2006/05/cafe_gibraltar.html Cafe Gibraltar]&lt;br /&gt;
* [http://www.mattmcalister.com/blog/ Matt McAllister] wrote an [http://www.mattmcalister.com/blog/_archives/2005/11/16/1408893.html hReview of the TV show: &amp;quot;The Office&amp;quot;]&lt;br /&gt;
* [http://www.bmannconsulting.com/blog/bmann/ Boris Mann] wrote an [http://www.bmannconsulting.com/blog/bmann/doubletake-best-panorama-stitch-tool-for-mac-os-x hReview of DoubleTake, a panorama stitch tool for Mac OS X]&lt;br /&gt;
* [http://blog.ftwr.co.uk/ Peter Westwood] has written an [http://blog.ftwr.co.uk/archives/2005/10/03/blubeckers-hampton-court/ hReview of Blubeckers Hampton Court] and an [http://blog.ftwr.co.uk/archives/2006/01/05/the-fox-inn/ hReview of The Fox Inn Bucks Green, West Sussex]&lt;br /&gt;
* [http://dougal.gunters.org/blog/ Dougal] has published an [http://dougal.gunters.org/blog/2005/08/03/french-vanilla-latte hReview of Wolfgang Puck’s Gourmet French Vanilla Latte].&lt;br /&gt;
* [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!&lt;br /&gt;
* [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].&lt;br /&gt;
* dda posted an [http://sungnyemun.org/wordpress/?p=20 hReview of hReview] :) &lt;br /&gt;
* An [http://tbp.xomerang.com/?p=3 hReview of Caffè Camardo coffee].&lt;br /&gt;
* [http://loadaveragezero.com/hnav/contact.php Douglas Clifton] posted [http://loadaveragezero.com/#May-12-2005 comments] regarding adapting his list of ~800 [http://loadaveragezero.com/app/drx Developer Resources] as a format for evaluating hReview.&lt;br /&gt;
* [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].&lt;br /&gt;
* [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.&lt;br /&gt;
* [http://station11.net/ticker/ Kjell] is publishing his link blog as a [http://station11.net/ticker/ list of hReviews].&lt;br /&gt;
* [http://epeus.blogspot.com/ Kevin Marks] has [http://epeus.blogspot.com/2005_04_01_epeus_archive.html#111484565269684374 published two hReviews] and used unicode &amp;quot;star&amp;quot; characters for his ratings!&lt;br /&gt;
* JamesStewart is publishing hReviews in the location pages at his [http://grwifi.net Grand Rapids WiFi site].&lt;br /&gt;
* [http://soldierant.net/ Soldier Ant] has [http://soldierant.net/archives/2005/06/product_review.html reviewed a cordless phone].&lt;br /&gt;
* [http://www.happenchance.co.uk/ Paul Livingstone] uses hreview to voice his opinion on [http://www.happenchance.co.uk/archives/2005/07/war_of_the_worl.php books], [http://www.happenchance.co.uk/archives/2005/03/im_going_to_fin.php movies] and [http://www.happenchance.co.uk/archives/2005/05/eels_carling_ac.php music].&lt;br /&gt;
* [http://www.stuffandnonsense.co.uk/ Andy Clarke] uses hReview for his [http://www.stuffandnonsense.co.uk/general/recommended-reading.html recommended reading list].&lt;br /&gt;
* [http://www.tjameswhite.com/blog Tim White] has begun implementing hReviews at [http://reviews.gale.com at work].&lt;br /&gt;
* [http://nachlin.com/ Jim Nachlin] has added hReview publishing to the CMS he uses to publish  [http://daysofleisure.com/writing his blog].&lt;br /&gt;
* [http://whumpdotcom.livejournal.com/236856.html Bill Humphries] has reviewed the book &amp;quot;A Brother's Price&amp;quot; on his LiveJournal.&lt;br /&gt;
* [http://www.thinkvitamin.com/ Vitamin] uses hReview on it's [http://www.thinkvitamin.com/reviews/ reviews] section (e.g. a [http://www.thinkvitamin.com/reviews/webapps/fluxiom/ review of Fluxiom]).&lt;br /&gt;
* [http://www.openguides.org/ OpenGuides] has support for the hReview microformat in svn, and for now you can see it in action on the [http://cotswolds.openguides.org/ Cotswolds OpenGuide].&lt;br /&gt;
* [http://paulgoscicki.com Paul Goscicki] is publishing his [http://paulgoscicki.com/#wp_movie_ratings movie ratings] using hReview.&lt;br /&gt;
* [http://www.liptrot.org Adam Liptrot] publishes movie reviews using hReview and hCard. See article at [http://www.liptrot.org/journal/entries/movies_and_microformats/ Movies and Microformats].&lt;br /&gt;
&lt;br /&gt;
== Implementations ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Textpattern plug-in : [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hReview and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].&lt;br /&gt;
* [http://kitchen.technorati.com/search Technorati Microformats Search] indexes [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] as [http://tantek.com/log/2006/05.html#d31t1802 announced by Tantek]. &lt;br /&gt;
* [http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar&lt;br /&gt;
* [http://www.reevoo.com/blogs/bengriffiths/ Revieworld CTO Ben Griffiths] has announced that they have built support into [http://www.reevoo.com/ Reevoo] to [http://www.reevoo.com/blogs/bengriffiths/2006/02/01/join-the-reevolution/ aggregate reviews of products that are published on blogs using hReview] ([http://opensource.reevoo.com/2006/03/08/release-uformats-12/ open source parser for Ruby])&lt;br /&gt;
* [http://brain.lionsden.com/ Leo Cerebellum Annotare] notes that [http://brain.lionsden.com/?p=229 ReviewZilla Alpha 2 includes MicroFormat hReview markup]&lt;br /&gt;
* [http://blog.codeeg.com/ Calvin Yu] has written a  [http://blog.codeeg.com/2006/01/28/using-microformats-to-plot-my-favorite-places/ web service that will allow you plot and describe places on a Yahoo Map easily] using [[hreview|hReview]] and [[geo]].&lt;br /&gt;
* [http://blog.codeeg.com/tails-firefox-extension/ Tails is a Firefox Extension] that will display the presence of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage.&lt;br /&gt;
* [http://kritx.com Kritx] is a site that indexes hReviews and other reviews on the Web.&lt;br /&gt;
* [http://www.goodpic.com/mt/aws/index_us.html Goodpic] has written:&lt;br /&gt;
** [http://www.goodpic.com/mt/aws/index_us.html hReview creator for Amazon.com products]&lt;br /&gt;
** [http://www.goodpic.com/mt/aws/index_uk.html hReview creator for Amazon.co.uk products]&lt;br /&gt;
** [http://www.goodpic.com/mt/aws/index_uk.html hReview creator for Amazon.co.jp products]&lt;br /&gt;
** be sure to choose the &amp;quot;hRview&amp;quot; tab from among the choices on the page that says &amp;quot;You can choose from more than 30 designs, please click the tab to select categories.&amp;quot;&lt;br /&gt;
* See the microformats.org [http://microformats.org/code/hreview/creator hReview creator] ([[hreview-creator-feedback|feedback]])&lt;br /&gt;
* [http://www.eigaseikatu.com/ Eigaseikatu], one of the largest movie community sites in Japan, provides [http://www.eigaseikatu.com/hreview/ hReview creator] for movie review.&lt;br /&gt;
* [http://sungnyemun.org/wordpress/?p=22 hReview plugin for WordPress]&lt;br /&gt;
* [http://paulgoscicki.com/projects/wp-movie-ratings/ WP Movie Ratings] is a [http://wordpress.org WordPress] plugin made by [http://paulgoscicki.com Paul Goscicki] which lets you rate (and review) movies and publish those ratings as hReviews.&lt;br /&gt;
* [http://theryanking.com/ Ryan King] has an [http://theryanking.com/microformats/hreview-creator.html hReview Creator] ([[hreview-creator-feedback|feedback]]).&lt;br /&gt;
* [http://rvu.ning.com/ Rvu] is a [http://ning.com Ning] app that lets you write reviews of reviews and publishes them in hReview&lt;br /&gt;
* [http://randomchaos.com/microformats/base/ Microformat Base] is an open-source PHP microformat aggregation crawler, currently recognizing hreview, hcalendar, and hcard.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
=== Normative References ===&lt;br /&gt;
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]&lt;br /&gt;
* [http://gmpg.org/xmdp/ XMDP]&lt;br /&gt;
* [[hcard|hCard]]&lt;br /&gt;
* [[hcalendar|hCalendar]]&lt;br /&gt;
* [[rel-tag]]&lt;br /&gt;
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]&lt;br /&gt;
* [http://www.ietf.org/rfc/rfc3986.txt RFC3986]&lt;br /&gt;
* [http://www.ietf.org/rfc/rfc4287.txt RFC4287] (Atom 1.0)&lt;br /&gt;
&lt;br /&gt;
=== Informative References ===&lt;br /&gt;
* [http://www.w3.org/TR/REC-CSS1 CSS1]&lt;br /&gt;
* ISO.8601.1988&lt;br /&gt;
** International Organization for Standardization, &amp;quot;Data elements and interchange formats - Information interchange - Representation of dates and times&amp;quot;, ISO Standard 8601, June 1988.&lt;br /&gt;
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]&lt;br /&gt;
* [http://www.ietf.org/rfc/rfc3667.txt RFC3667]&lt;br /&gt;
* [http://www.ietf.org/rfc/rfc3668.txt RFC3668]&lt;br /&gt;
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]&lt;br /&gt;
* [http://local.yahoo.com/details?id=21359628 Crepes on Cole reviews on Yahoo! Local]&lt;br /&gt;
* Other reviews efforts. See [[reviews-formats]].&lt;br /&gt;
* Contributed from http://developers.technorati.com/wiki/hReview.&lt;br /&gt;
&lt;br /&gt;
==== Similar Work ====&lt;br /&gt;
* [[hlisting-proposal|hListing]]&lt;br /&gt;
* [[xoxo|XOXO]]&lt;br /&gt;
&lt;br /&gt;
=== Copyright ===&lt;br /&gt;
{{MicroformatCopyrightStatement2005}}&lt;br /&gt;
&lt;br /&gt;
=== Patents ===&lt;br /&gt;
{{MicroFormatPatentStatement}}&lt;br /&gt;
&lt;br /&gt;
== Work in progress ==&lt;br /&gt;
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. &lt;br /&gt;
&lt;br /&gt;
=== Changes from v0.2 ===&lt;br /&gt;
The following changes have been made in hReview v0.3 over [[hreview-v0.2|hReview v0.2]]:&lt;br /&gt;
&lt;br /&gt;
Normative changes:&lt;br /&gt;
# MUST (instead of SHOULD) use [[hcard|hCard]] for the item description of a business or person&lt;br /&gt;
# &amp;quot;reviewer&amp;quot; changes&lt;br /&gt;
## Made reviewer *optional* per feedback from Ryan King and Mark Nottingham&lt;br /&gt;
## If reviewer is absent from the hReview, then look outside the hReview, in the context of the page, for the reviewer.  If there is no &amp;quot;reviewer&amp;quot; outside either, then use the author information according to the containing document language (e.g. &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;address&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; for (X)HTML pages) as the reviewer.&lt;br /&gt;
## MUST (instead of SHOULD) use [[hcard|hCard]] to represent reviewer information&lt;br /&gt;
# &amp;quot;dtreviewed&amp;quot; changes&lt;br /&gt;
## Made dtreviewed *optional* per feedback from Ryan King and Mark Nottingham&lt;br /&gt;
## If dtreviewed is absent from the hReview, then look outside the hReview, in the surrounding context.  If the context is an [[hatom|hAtom]] entry, use its &amp;quot;published&amp;quot; (or &amp;quot;updated&amp;quot; if that is missing) datetime as the dtreviewed, if not present on the entry, use the &amp;quot;published&amp;quot; (or &amp;quot;updated&amp;quot; if that is missing) of the feed.  Otherwise use the information according to the containing document language (e.g. &amp;quot;published&amp;quot;/&amp;quot;updated&amp;quot; similarly for Atom feeds), then protocol (e.g. HTTP Last-Modified, or file system last modified datetime).&lt;br /&gt;
# SHOULD use [[hcalendar|hCalendar]] to represent an item of 'type' 'event'&lt;br /&gt;
# Added one decimal digit of precision to ratings' numerical values based on publisher experience.&lt;br /&gt;
# Use [http://microformats.org/wiki/hcard#Value_excerpting the &amp;quot;value&amp;quot; construct from hCard] (as it is used in &amp;quot;tel&amp;quot; properties for example) to more explicitly markup the rating value when also providing (marking up) the best/worst of a rating.&lt;br /&gt;
# Added [[rel-license]] to indicate the license of the hReview as a whole.&lt;br /&gt;
# Permit tags inside ratings to denote rated tags, the same as ratings inside tags per suggestion from Eran Globen.&lt;br /&gt;
# Add [[include-pattern]] support to allow multiple reviews for the same item to not repeat the item info.&lt;br /&gt;
&lt;br /&gt;
Informative changes (several, but in particular):&lt;br /&gt;
# Note that scalar/rated tags would ideally use a tag space that explain the ratings for that tag.  E.g. to explain what Food:18/30 means.&lt;br /&gt;
# Updated examples accordingly.&lt;br /&gt;
&lt;br /&gt;
== Discussions ==&lt;br /&gt;
* Feedback is encouraged on the [[hreview-feedback]] page.&lt;br /&gt;
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].&lt;br /&gt;
&lt;br /&gt;
=== Q&amp;amp;A ===&lt;br /&gt;
* 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!&lt;br /&gt;
&lt;br /&gt;
=== Issues ===&lt;br /&gt;
* Please add any issues with the specification to the separate [[hreview-issues|hReview issues]] document.&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hcalendar-creator-issues&amp;diff=7546</id>
		<title>hcalendar-creator-issues</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hcalendar-creator-issues&amp;diff=7546"/>
		<updated>2006-07-20T00:46:17Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: /* Bug Reports */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt;hCalendar creator feedback&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page is for collecting bugs, suggested fixes, and feature requests for the [[hcalendar|hCalendar]] [http://microformats.org/code/hcalendar/creator creator]&lt;br /&gt;
&lt;br /&gt;
Please list your name, and indicate ''which'' version (even just a date and time helps) of the creator that you are providing feedback on.  Thanks!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Bug Reports ==&lt;br /&gt;
* dtend has format &amp;quot;2006620&amp;quot;, should be &amp;quot;20060620&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Suggested Tweaks and Fixes ==&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Feature Requests ==&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
* [[hcalendar|hCalendar specification]]&lt;br /&gt;
* [[hcalendar-feedback|hCalendar feedback]]&lt;br /&gt;
* [[hcard-creator-feedback|hCard creator feedback]]&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hcalendar-creator-issues&amp;diff=7543</id>
		<title>hcalendar-creator-issues</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hcalendar-creator-issues&amp;diff=7543"/>
		<updated>2006-07-20T00:46:06Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: /* Bug Reports */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt;hCalendar creator feedback&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page is for collecting bugs, suggested fixes, and feature requests for the [[hcalendar|hCalendar]] [http://microformats.org/code/hcalendar/creator creator]&lt;br /&gt;
&lt;br /&gt;
Please list your name, and indicate ''which'' version (even just a date and time helps) of the creator that you are providing feedback on.  Thanks!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Bug Reports ==&lt;br /&gt;
* dtend has fromat &amp;quot;2006620&amp;quot;, should be &amp;quot;20060620&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Suggested Tweaks and Fixes ==&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Feature Requests ==&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
* [[hcalendar|hCalendar specification]]&lt;br /&gt;
* [[hcalendar-feedback|hCalendar feedback]]&lt;br /&gt;
* [[hcard-creator-feedback|hCard creator feedback]]&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
	<entry>
		<id>https://microformats.org/wiki/index.php?title=hcard-creator-issues&amp;diff=7545</id>
		<title>hcard-creator-issues</title>
		<link rel="alternate" type="text/html" href="https://microformats.org/wiki/index.php?title=hcard-creator-issues&amp;diff=7545"/>
		<updated>2006-07-20T00:42:30Z</updated>

		<summary type="html">&lt;p&gt;Dmitry Baranovskiy: /* Bug Reports */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt;hCard creator feedback&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page is for collecting bugs, suggested fixes, and feature requests for the [[hcard|hCard]] [http://microformats.org/code/hcard/creator creator]&lt;br /&gt;
&lt;br /&gt;
Please list your name, and indicate ''which'' version (even just a date and time helps) of the creator that you are providing feedback on.  Thanks!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Bug Reports ==&lt;br /&gt;
* AIM screenname &amp;amp; YIM screenname overlap each other in Safari ver. 2.0.4 (419.3) (on the last WebKit it looks Ok, but still gap between these two labels is too small)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Suggested Tweaks and Fixes ==&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Feature Requests ==&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
* [[hcard|hCard specification]]&lt;br /&gt;
* [[hcard-feedback|hCard feedback]]&lt;br /&gt;
* [[hcalendar-creator-feedback|hCalendar creator feedback]]&lt;/div&gt;</summary>
		<author><name>Dmitry Baranovskiy</name></author>
	</entry>
</feed>