<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://microformats.org/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Alik</id>
	<title>Microformats Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://microformats.org/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Alik"/>
	<link rel="alternate" type="text/html" href="http://microformats.org/wiki/Special:Contributions/Alik"/>
	<updated>2026-05-08T05:33:16Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.38.4</generator>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=rel-tag&amp;diff=43053</id>
		<title>rel-tag</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=rel-tag&amp;diff=43053"/>
		<updated>2010-09-05T21:05:25Z</updated>

		<summary type="html">&lt;p&gt;Alik: Quotes&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;entry-title&amp;gt;rel=&amp;quot;tag&amp;quot;&amp;lt;/entry-title&amp;gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
== Draft Specification 2005-01-10 ==&lt;br /&gt;
; Editors/Authors&lt;br /&gt;
:[http://tantek.com/ Tantek Çelik]&lt;br /&gt;
:[http://epeus.blogspot.com/ Kevin Marks]&lt;br /&gt;
&lt;br /&gt;
;Concept&lt;br /&gt;
:[http://powazek.com/ Derek Powazek]&lt;br /&gt;
&lt;br /&gt;
;short URL&lt;br /&gt;
:http://tr.im/reltag&lt;br /&gt;
&lt;br /&gt;
=== Copyright ===&lt;br /&gt;
{{MicroFormatCopyrightStatement2004}}&lt;br /&gt;
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.&lt;br /&gt;
* [[User:Kevin Marks|Kevin Marks]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.&lt;br /&gt;
** When all authors/editors have done so, we can remove the MicroFormatCopyrightStatement template reference and replace it with the MicroFormatPublicDomainContributionStatement.&lt;br /&gt;
&lt;br /&gt;
=== Patents ===&lt;br /&gt;
{{MicroFormatPatentStatement}}&lt;br /&gt;
&lt;br /&gt;
== Abstract ==&lt;br /&gt;
[[Rel-Tag]] is one of several [[MicroFormats]].  By adding &amp;lt;code&amp;gt;rel=&amp;amp;quot;tag&amp;amp;quot;&amp;lt;/code&amp;gt; to a hyperlink, a page indicates that the destination of that hyperlink is an author-designated &amp;amp;quot;tag&amp;amp;quot; (or keyword/subject) for the current page. Note that a tag may just refer to a major portion of the current page (i.e. a blog post). e.g. by placing this link on a page,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&amp;lt;a href=&amp;quot;http://technorati.com/tag/tech&amp;quot; rel=&amp;quot;tag&amp;quot;&amp;gt;tech&amp;lt;/a&amp;gt;&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
the author indicates that the page (or some portion of the page) has the tag &amp;amp;quot;tech&amp;amp;quot;.&lt;br /&gt;
&lt;br /&gt;
The linked page SHOULD exist, and it is the linked page, rather than the link text, that defines the tag. The last path component of the URL&lt;br /&gt;
is the text of the tag, so &lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&amp;lt;a href=&amp;quot;http://technorati.com/tag/tech&amp;quot; rel=&amp;quot;tag&amp;quot;&amp;gt;fish&amp;lt;/a&amp;gt;&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
would indicate the tag &amp;amp;quot;tech&amp;amp;quot; rather than &amp;amp;quot;fish&amp;amp;quot;.&lt;br /&gt;
&lt;br /&gt;
== Scope ==&lt;br /&gt;
rel=&amp;amp;quot;tag&amp;amp;quot; is specifically designed for &amp;amp;quot;tagging&amp;amp;quot; content, typically web pages (or portions thereof, like blog posts).&lt;br /&gt;
&lt;br /&gt;
rel=&amp;amp;quot;tag&amp;amp;quot; is NOT designed for &amp;amp;quot;tagging&amp;amp;quot; arbitrary URLs or external content.  There is demand for a general decentralized syntax for tagging URLs external to the current page, but this is not meant for that.  See [[xfolk|xFolk]] and [[hreview|hReview]] for ways to tag arbitrary URLs.&lt;br /&gt;
&lt;br /&gt;
If you need to define tags as part of a more specialized format,  rel=&amp;amp;quot;tag&amp;amp;quot; is the recommended way to do so, and [[xfolk|xFolk]], [[hreview|hReview]], [[hcard |hCard]], [[hcalendar|hCalendar]] and [[hrecipe|hRecipe]] all do this.&lt;br /&gt;
&lt;br /&gt;
== XMDP profile ==&lt;br /&gt;
See [[rel-tag-profile]].&lt;br /&gt;
&lt;br /&gt;
== Tag Spaces ==&lt;br /&gt;
&lt;br /&gt;
Tags are embedded in HTTP URIs in a well-defined manner so that the tag embedded in an HTTP URI can be mechanically extracted from that URI. Specifically, the last segment of the path portion of the URI (after the final &amp;quot;/&amp;quot; character) contains the tag value. For example, the URI &amp;lt;source lang=html4strict&amp;gt;http://www.example.com/tags/foo&amp;lt;/source&amp;gt; contains the tag &amp;amp;quot;foo&amp;amp;quot;. &lt;br /&gt;
&lt;br /&gt;
Thus, for the purposes of comparing two HTTP URIs as tags, the last segment of the path portion should be extracted and only that value (that value of the tag) should be compared.&lt;br /&gt;
&lt;br /&gt;
''Need more formal language about comparison and extraction process.''&lt;br /&gt;
&lt;br /&gt;
The destination of a rel=&amp;amp;quot;tag&amp;amp;quot; hyperlink is required to be a tag space (a place that collates or defines tags), where the last segment of the path of the URL is the tag, e.g. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;http://technorati.com/tag/tech &amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
is a URL for the tag &amp;amp;quot;tech&amp;amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Tags may only be placed in the URL path, and only in the last segment of the path.  Tags may not be placed in query parameters or fragment identifiers.  e.g.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;http://technorati.com/tag/tech?tag=fish#emu &amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
is still a URL for the tag &amp;amp;quot;tech&amp;amp;quot;, not &amp;amp;quot;fish&amp;amp;quot; or &amp;amp;quot;emu&amp;amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Since the only part of a tag space URL of which any structure is required is the last path segment, a tag space URL can be hosted at any domain.  Authors may choose to link to a tag at a particular tag space in order to provide a specific meaning.  E.g. a tag for technology could link to:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;  http://en.wikipedia.org/wiki/Technology &amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Trailing slashes in tag URLs are ignored, that is:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;  http://technorati.com/tag/Technology/ &amp;lt;/source&amp;gt;&lt;br /&gt;
as a rel-tag URL is treated as:&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;  http://technorati.com/tag/Technology &amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Encoding issues ==&lt;br /&gt;
Spaces can be encoded either as &amp;lt;code&amp;gt;+&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;%20&amp;lt;/code&amp;gt;. Unicode characters are encoded as specified in [http://www.ietf.org/rfc/rfc3986.txt &amp;lt;nowiki&amp;gt;RFC 3986&amp;lt;/nowiki&amp;gt;]. For example:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&amp;lt;a href=&amp;quot;http://technorati.com/tag/Sant%C3%A9+et+bien-%C3%AAtre&amp;quot; rel=&amp;quot;tag&amp;quot;&amp;gt;Santé et bien-être&amp;lt;/a&amp;gt; &amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note that if using Wikipedia as a tagspace, as discussed above, you should use &amp;lt;code&amp;gt;%20&amp;lt;/code&amp;gt; as they remap '+' to &amp;lt;code&amp;gt;%2B&amp;lt;/code&amp;gt;, causing  a page with a plus sign in the title (which usually does not exist) to appear.&lt;br /&gt;
&lt;br /&gt;
== Tags Are Visible Metadata ==&lt;br /&gt;
&amp;lt;code&amp;gt;rel=&amp;amp;quot;tag&amp;amp;quot;&amp;lt;/code&amp;gt; hyperlinks are intended to be visible links on pages and posts.  This is in stark contrast to meta keywords (which were invisible and typically never revealed to readers), and thus is at least somewhat more resilient to the problems which plagued meta keywords.&lt;br /&gt;
&lt;br /&gt;
Making tag hyperlinks visible has the additional benefit of making it more obvious to readers if a page is abusing tag links, and thus providing more peer pressure for better behavior.  It also makes it more obvious to authors, who may not always be aware what invisible metadata is being generated on their behalf.&lt;br /&gt;
&lt;br /&gt;
As a result the invisible tag link syntax variant: &amp;lt;code&amp;gt;&amp;lt;link rel=&amp;amp;quot;tag&amp;amp;quot; href=&amp;amp;quot;...&amp;amp;quot; /&amp;gt;&amp;lt;/code&amp;gt; SHOULD NOT be supported by implementations.&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 implemented rel-tag, 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 your site is marked up with rel-tag, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page like [[rel-tag-examples-in-wild]].&amp;lt;span id=&amp;quot;Examples_in_the_Wild&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
* [http://en.newsgrail.com/ Newsgrail] uses rel-tag for an implementation of structured sematic tagging by [http://opencalais.com/ OpenCalais].&lt;br /&gt;
* [http://davidswain.co.uk Actor David Swain] uses rel-tag on all &amp;quot;tag&amp;quot; links on his site each pointing to its own tag-space.&lt;br /&gt;
* [http://beeets.com beeets] is a tag-based event search engine that uses rel-tag on all &amp;quot;tag&amp;quot; links, each pointing to its own tag-space.&lt;br /&gt;
* [http://www.beginrunning.com/ Begin Running] uses rel-tag on pages containing tagged content.&lt;br /&gt;
* [http://laibcoms.asia/blog/ Snow World] uses rel-tag on all &amp;quot;tag&amp;quot; links.  As is built in [http://b2evolution.net b2evolution].&lt;br /&gt;
* [http://gameshogun.ws/ gameshogun™] uses rel-tag on all &amp;quot;tag&amp;quot; links.  A [http://b2evolution.net b2evolution] implementation.&lt;br /&gt;
* [http://huffduffer.com/ Huffduffer] uses rel-tag on every page, pointing to its own tag space e.g. http://huffduffer.com/tags/microformats&lt;br /&gt;
* [http://www.pantrymothtrap.com/ Pantry Moth Traps] implements the rel-tag in articles where an authoritative source is known.  (for example in the article [http://www.pantrymothtrap.com/MothTrapsPick.html Moth Trap Picks] the tag [http://www.cleanertoday.com/tag/moth%20trap Moth Trap])&lt;br /&gt;
* [http://www.hightechcville.com/ HighTechCville] uses rel-tag on all the pages listing tagged content for [http://www.hightechcville.com/people people], [http://www.hightechcville.com/organizations organizations] and [http://www.hightechcville.com/events events] related to high tech in Charlottesville, VA.&lt;br /&gt;
* [http://skateboardspot.info skateboardspot.info] uses rel-tag in spotguide entries which are added to the site and categorized by the users (for example: [http://skateboardspot.info/cat/spotguide/action/view/id/1 “El Toro High School” spotguide entry]).&lt;br /&gt;
* [http://www.idoneos.com Idoneos.com] uses rel-tag for conceptual links to its own tag space, a collection of 'concepts' (mostly spanish).&lt;br /&gt;
* [http://www.professionalontheweb.com Professional On The Web]  uses rel-tag for user entered tags which categorize web professionals and freelancers.&lt;br /&gt;
* [https://www.coderesort.com/p/epicode/wiki/CloudCuckoo CloudCuckoo] (secure site but open to all) an [http://www.episerver.com EPiServer] module distributed free by [http://www.interakting.co.uk Interakting], generates tag clouds with rel-tag links.&lt;br /&gt;
* [http://www.lifetime.com Lifetime.com] uses rel- and rev-tags in all content pages.&lt;br /&gt;
* [http://www.my-warehouse.de the my-Warehouse shopsystem] implements rel-tags in box headings and categories links.&lt;br /&gt;
* Joseph Bergantine uses tags to categorize [http://bergantinedesign.us/wallpaper/ wallpapers] and [http://bergantinedesign.us/blog/my-name-is-rachel-corrie blog posts]&lt;br /&gt;
* [http://www.codesignville.com Codesignville] uses rel-tag to indicate content categories.&lt;br /&gt;
* [http://www.bossalive.com BossaLive] uses rel-tag for tagging music. Publishes rel-tags for album, artist and genre.&lt;br /&gt;
** Also uses [[hcard|hCard]] on user profile pages.&lt;br /&gt;
* [http://www.qmpeople.com/ qmpeople] Uses rel-tag for translated tags into english, french and italian to meet new friends in different countries.&lt;br /&gt;
* [http://www.keevu.com Keevu.com] uses rel-tag to indicate content categories on most pages, like [http://www.keevu.com/venues venues]&lt;br /&gt;
* [http://www.amazingincredible.com Amazing Incredible] uses rel-tag on content pages&lt;br /&gt;
* [http://www.auctionlink.com.au AuctionLink] uses rel-tag on [http://www.auctionlink.com.au/TagList/Auctioneers/ Auction Sales Listings] tags.&lt;br /&gt;
** Could also use [[hcard|hCard]], e.g. on [http://www.auctionlink.com.au/Auctioneers/Auctioneer/Bonhams_Goodman_1/] [[User:AndyMabbett|Andy Mabbett]]&lt;br /&gt;
* Christian Hess uses rel-tag on his [http://www.hess-cr.com homepage blog] and several other pages of his site.&lt;br /&gt;
* [http://spacedust.atspace.com/ Spacedust] uses rel-tag to mark up gallery pages.&lt;br /&gt;
* [http://my.opera.com/dstorey/blog/ My Opera] uses rel-tag for tags on all user's blog entries.&lt;br /&gt;
* [http://dev.opera.com/articles/view/making-wii-friendly-pages/ Dev Opera] uses rel-tag on all article tags.&lt;br /&gt;
* [http://www.international.unt.edu UNT International] uses rel-tag to indicate content categories on most pages&lt;br /&gt;
* [http://yedda.com Yedda] - Yedda publishes rel-tags for all of the tags the people entered on themselves as well as on all tags entered on questions asked on Yedda.&lt;br /&gt;
* [http://www.lingr.com Lingr] publishes rel-tags for all user entered tags.&lt;br /&gt;
* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] rel-tags for user entered tags.&lt;br /&gt;
* [http://eventful.com Eventful] publishes rel-tags for user entered tags.&lt;br /&gt;
* [http://spinn3r.com Spinn3r] implements rel-tag as well as RSS and Atom subject and categories.&lt;br /&gt;
* [http://www.weboffate.com Web of Fate] publishes rel-tags for future predictions.&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 rel-tag links. If you have a rel-tag 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 like [[rel-tag-implementations]].&lt;br /&gt;
&lt;br /&gt;
* [http://b2evolution.net b2evolution] A blog platform which generates rel-tag for all tags on blog posts (starting from v3.x).&lt;br /&gt;
* [http://www.textcube.org Textcube.org] makes a blogging tool, Textcube which generates rel-tag for tags on blog posts.&lt;br /&gt;
* [http://hashtags.org/ HashTags] tags Twitter posts, converting &amp;quot;#example&amp;quot; into a tag of &amp;quot;example&amp;quot;&lt;br /&gt;
* [http://ikiwiki.info ikiwiki] generates rel-tag for all tagged pages (as of version 2.6)&lt;br /&gt;
* [http://www.hubtag.com HubTag] helps users find a unique tag across the web for their event - eg. JohnAndBettysWeddingWimbledonMarch07&lt;br /&gt;
* [http://www.necctar.com Necctar] is a search engine exclusively based on tag microformat parsing and processing. Necctar uses tags entered by bloggers to index the world wide web&lt;br /&gt;
* Nutch has a [[rel-tag]] parser [http://www.mail-archive.com/nutch-commits@lucene.apache.org/msg01014.html committed to their svn repository].&lt;br /&gt;
* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables rel-tagging from within Dreamweaver 8.&lt;br /&gt;
* [http://scooch.gr0w.com/ Scooch] slide show creator allows authors to generate rel-tags and group slide shows by rel-tag via a list or cloud with tag usage count.&lt;br /&gt;
* The Freetag plugin for the [http://www.s9y.org Serendipity] blog software supports rel-tags on a per-entry basis, as well as inside of its tag clouds.  (The Freetag plugin is available inside of SPARTACUS)&lt;br /&gt;
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding rel-tags and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].&lt;br /&gt;
* [http://www.rainskit.com/blog/493/trutags-a-tagging-plugin-for-textpattern tru_tags] is a plugin for [http://textpattern.com/ Textpattern] that supports rel-tagging blog posts via the Keywords field.&lt;br /&gt;
* [http://news.livejournal.com/86492.html?thread=24881884 LiveJournal] - see also [http://www.livejournal.com/support/faq.bml?cat=tags their FAQ regarding their tags support]&lt;br /&gt;
* [http://trac.labnotes.org/cgi-bin/trac.cgi/wiki/TagsLinks TagsLinks] Turn each tag into links that let you find related content on tagging services.&lt;br /&gt;
* [http://www.octofinder.com OctoFinder] uses rel-tag for all live news tag clouds.&lt;br /&gt;
* [http://dev.wp-plugins.org/wiki/BunnysTechnoratiTags Tag plugin for WordPress]&lt;br /&gt;
** Note that some sites using WordPress (http://microformatique.com/ for instance) are getting incorrect tags. The tag is ?cat=12 instead of the actual tag value.&lt;br /&gt;
* [http://noone.org/blog/tags/Tagging Tag plugin for Blosxom]&lt;br /&gt;
* Technorati first implemented rel-tag in its [http://technorati.com/tag/ Technorati Tags] service. Technorati indexes rel-tag tags.&lt;br /&gt;
* [http://consumingexperience.blogspot.com/2005/12/updated-multiple-word-technorati-tag.html Greasemonkey script for Firefox that generates tags for Blogger]&lt;br /&gt;
* [http://tools.microformatic.com/help/xhtml/rel-lint/ rel-lint] is a validation tool by [[User:DrewMcLellan|Drew McLellan]] that will validate existence of rel-tag attributes.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
=== Normative References ===&lt;br /&gt;
* [http://www.w3.org/TR/REC-html40/ HTML 4]&lt;br /&gt;
* [http://www.w3.org/TR/xhtml1/ XHTML 1]&lt;br /&gt;
* [http://gmpg.org/xmdp/ XMDP]&lt;br /&gt;
* RFC 3986 specifies URL syntax.  Section 3.3 specifies URL paths and path segments.&lt;br /&gt;
&lt;br /&gt;
=== Informative References ===&lt;br /&gt;
* [[hreview|hReview]] uses rel-tag for tags and scalar tags&lt;br /&gt;
* [[xfolk|xFolk]] uses rel-tag to build a distributed remote resource tagging construct&lt;br /&gt;
* [http://developers.technorati.com/wiki/attentionxml Attention.XML] uses rel-tag for reader tagging of pages, posts, feeds&lt;br /&gt;
* [[hcard|hCard]] can use rel-tag for categories&lt;br /&gt;
* [[hcalendar|hCalendar]] can use rel-tag for categories&lt;br /&gt;
* [http://technorati.com/help/tags.html Using Technorati Tags]&lt;br /&gt;
* Contributed from http://developers.technorati.com/wiki/RelTag&lt;br /&gt;
* [http://microformatique.com/?p=61 Know your rel-tag] at microformatique.com&lt;br /&gt;
&lt;br /&gt;
== Discussions ==&lt;br /&gt;
* Feedback is encouraged on the [[rel-tag-feedback]] page.&lt;br /&gt;
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].&lt;br /&gt;
* History: [http://www.powazek.com/2005/07/000532.html How Tags Happened at Technorati] by [http://www.powazek.com/ Derek Powazek]&lt;br /&gt;
&lt;br /&gt;
=== Q&amp;amp;A ===&lt;br /&gt;
* If you have any questions about rel-tag, check the [[rel-faq|rel FAQ]] first for general rel attribute questions, then check the [[rel-tag-faq|rel-tag FAQ]], and then if you don't find answers, ask your question on the [http://microformats.org/discuss microformats-discuss] mailing list.&lt;br /&gt;
&lt;br /&gt;
==Related pages==&lt;br /&gt;
{{rel-tag-related-pages}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Specifications]]&lt;br /&gt;
[[Category:rel-tag]]&lt;/div&gt;</summary>
		<author><name>Alik</name></author>
	</entry>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=vote-links&amp;diff=43052</id>
		<title>vote-links</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=vote-links&amp;diff=43052"/>
		<updated>2010-09-05T21:02:22Z</updated>

		<summary type="html">&lt;p&gt;Alik: /* Specification */ Quotes&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;entry-title&amp;gt;Vote Links&amp;lt;/entry-title&amp;gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
== Specification 2005 ==&lt;br /&gt;
=== Editor ===&lt;br /&gt;
* [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc.], formerly of [http://microsoft.com/ Microsoft Corporation])&lt;br /&gt;
&lt;br /&gt;
=== Concept ===&lt;br /&gt;
* [http://epeus.blogspot.com/ Kevin Marks] ([http://technorati.com Technorati, Inc.])&lt;br /&gt;
&lt;br /&gt;
=== Authors ===&lt;br /&gt;
* [http://epeus.blogspot.com/ Kevin Marks] ([http://technorati.com Technorati, Inc])&lt;br /&gt;
* [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc])&lt;br /&gt;
&lt;br /&gt;
=== Copyright ===&lt;br /&gt;
{{MicroFormatPublicDomainContributionStatement}}&lt;br /&gt;
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.&lt;br /&gt;
* [[User:Kevin_Marks|Kevin Marks]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.&lt;br /&gt;
&lt;br /&gt;
=== Patents ===&lt;br /&gt;
{{MicroFormatPatentStatement}}&lt;br /&gt;
&lt;br /&gt;
=== Inspiration and Acknowledgments ===&lt;br /&gt;
Thanks to everyone who has given feedback on VoteLinks.  Thanks especially to EtanWexler, who provided the first really good documentation that VoteLinks should be using 'rev' instead of 'rel' (see [[VoteLinksFAQ]]), and John Allsopp who similarly challenged the use of 'rel', and helped co-author the [[RelFAQ]] exploring questions and issues about the use of the HTML4 'rel', 'rev' attributes and linktypes in general.&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
Indexing and tracking applications treat all links as endorsements, or expressions of support. This is a problem, as we need to link to those we disagree with as well, to discuss why.&lt;br /&gt;
&lt;br /&gt;
== Specification ==&lt;br /&gt;
VoteLinks is an [[elemental-microformat|elemental microformat]], one of several [[microformats|microformat]] open standards.&lt;br /&gt;
We propose a set of three new values for the rev attribute of the &amp;lt;a&amp;gt; (hyperlink) tag in HTML.&lt;br /&gt;
&lt;br /&gt;
The new values are &amp;amp;quot;vote-for&amp;amp;quot; &amp;amp;quot;vote-abstain&amp;amp;quot; or &amp;amp;quot;vote-against&amp;amp;quot;, which are mutually exclusive, and represent agreement, abstention or indifference, and disagreement respectively.&lt;br /&gt;
&lt;br /&gt;
A link without an explicit vote 'rev' value is deemed to have value &amp;amp;quot;vote-for&amp;amp;quot; or &amp;amp;quot;vote-abstain&amp;amp;quot;, depending on the application.&lt;br /&gt;
&lt;br /&gt;
Additional human-readable commentary can be added using the existing 'title' attribute, which most browsers show as a rollover.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
 &amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;a rev=&amp;quot;vote-for&amp;quot; href=&amp;quot;http://example.com/cheesevote&amp;quot;  &lt;br /&gt;
   title=&amp;quot;Melt the cheese!&amp;quot;&amp;gt;Do it!&amp;lt;/a&amp;gt;&lt;br /&gt;
&amp;lt;a rev=&amp;quot;vote-against&amp;quot; href=&amp;quot;http://example.com/cheesevote&amp;quot;  &lt;br /&gt;
   title=&amp;quot;Don't melt the cheese!&amp;quot;&amp;gt;Don't do it!&amp;lt;/a&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Deprecated: Using 'rel' for VoteLinks ===&lt;br /&gt;
A previous draft of the specification used the 'rel' attribute instead of the 'rev' attribute.  Analysis and feedback has demonstrated this to have been inappropriate use of the 'rel' attribute, when the 'rev' attribute was much more important.  See the [[RelFAQ]] for more details.&lt;br /&gt;
&lt;br /&gt;
Implementations MAY support links with the VoteLinks values in the 'rel' attribute for backward compatibility with any existing VoteLinks content.&lt;br /&gt;
&lt;br /&gt;
Authors MUST NOT use 'rel' for VoteLinks values.&lt;br /&gt;
&lt;br /&gt;
== XMDP profile ==&lt;br /&gt;
The following is an [http://gmpg.org/xmdp/ XMDP] profile for the [[vote-links]] specification.&lt;br /&gt;
&lt;br /&gt;
=== URLs ===&lt;br /&gt;
This profile is hosted as a separate XMDP file on microformats.org:&lt;br /&gt;
* http://microformats.org/profile/vote-links&lt;br /&gt;
* shortURL: http://ufs.cc/x/vote-links&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
Profiles are referenced in (X)HTML files in the &amp;amp;lt;HEAD&amp;amp;gt; tag, e.g.:&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;head profile='http://microformats.org/profile/vote-links'&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Profile ===&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;dl class=&amp;quot;profile&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;dt id=&amp;quot;rev&amp;quot;&amp;gt;rev&amp;lt;/dt&amp;gt;&lt;br /&gt;
 &amp;lt;dd&amp;gt;&amp;lt;p&amp;gt;&lt;br /&gt;
   &amp;lt;a rel=&amp;quot;help&amp;quot; href=&amp;quot;http://www.w3.org/TR/html401/struct/links.html#adef-rev&amp;quot;&amp;gt;&lt;br /&gt;
     HTML4 definition of the 'rev' attribute.&amp;lt;/a&amp;gt;  &lt;br /&gt;
   Here are additional values as defined in the&lt;br /&gt;
   &amp;lt;a rel=&amp;quot;help start&amp;quot; href=&amp;quot;http://microformats.org/wiki/vote-links&amp;quot;&amp;gt;&lt;br /&gt;
   vote-links specification&amp;lt;/a&amp;gt; &lt;br /&gt;
   .&amp;lt;/p&amp;gt;&lt;br /&gt;
  &amp;lt;dl&amp;gt;&lt;br /&gt;
   &amp;lt;dt id=&amp;quot;vote-for&amp;quot;&amp;gt;vote-for&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;Indicates agreement with or recommendation for the referred resource.&amp;lt;/dd&amp;gt;&lt;br /&gt;
   &amp;lt;dt id=&amp;quot;vote-abstain&amp;quot;&amp;gt;vote-abstain&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;Indicates abstention or indifference for the referred resource.&amp;lt;/dd&amp;gt;&lt;br /&gt;
   &amp;lt;dt id=&amp;quot;vote-against&amp;quot;&amp;gt;vote-against&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;Indicates disagreement with or recommendation against the referred resource.&amp;lt;/dd&amp;gt;&lt;br /&gt;
  &amp;lt;/dl&amp;gt;&lt;br /&gt;
 &amp;lt;/dd&amp;gt;&lt;br /&gt;
&amp;lt;/dl&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Implementations ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
* Following a [http://jyte.com/cl/jyte-should-integrate-microformats-votelinks vote-links claim] [http://jyte.com/profile/brianellin.com Brian Ellin] implemented vote-links on [http://jyte.com Jyte] within less than 30 minutes.&lt;br /&gt;
* [http://moloko.itc.it/paoloblog/ Paolo Massa] created [http://moloko.itc.it/paoloblog/semantic_links/ SemanticLinks], a small Firefox extension that shows vote-for, vote-against links information. (Note the download links for SemanticLinks have been removed by the author.)&lt;br /&gt;
* Wordpress VoteBack (vote-link aware pingback and trackback) plugin is in testing at [http://redmonk.net/archives/2006/12/21/voteback/ VoteBack] ([[User:SteveIvy|Steve Ivy]]) - looking for testers!&lt;br /&gt;
* [http://folksr.de/ Folksr.de] - using VoteLinks to vote on the World Cup 2006&lt;br /&gt;
* [http://www.weboffate.com/ Web of Fate] - has VoteLinks for future predictions&lt;br /&gt;
== Examples in the wild ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
The following sites have implemented VoteLinks , 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 your site marked up with VoteLinks, 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;
&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
          Add new items to the top of the list&lt;br /&gt;
&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
* [http://www.likeorhate.com/ LikeOrHate] uses Vote-Links all over the site, to rate anything, items, comments, users. Valid votes are Like, Hate, Whatever (&amp;quot;vote-for&amp;quot;, &amp;quot;vote-against&amp;quot;, &amp;quot;vote-abstain&amp;quot;). CSS is used to &amp;quot;check&amp;quot; votes so logged users can remember them later.&lt;br /&gt;
* [http://www.weboffate.com/ Web of Fate] Web of Fate uses Vote-Links for prediction probability scoring. Users can vote Agree, Disagree, Witness (&amp;quot;vote-for&amp;quot;, &amp;quot;vote-against&amp;quot;, &amp;quot;vote-abstain&amp;quot;)&lt;br /&gt;
* [http://tommorris.org/blog/ Tom Morris] has vote links on del.icio.us links (based on tags &amp;quot;vote-for&amp;quot;, &amp;quot;vote-against&amp;quot; and &amp;quot;vote-abstain&amp;quot;).&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
          Add new items to the top of the list&lt;br /&gt;
&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
=== Normative References ===&lt;br /&gt;
* [http://gmpg.org/xmdp/ XMDP]&lt;br /&gt;
&lt;br /&gt;
=== Informative References ===&lt;br /&gt;
* [http://www.artweb-design.de/articles/2006/06/05/distributed-votings-using-microformats Distributed votings using microformats] from Artweb Design&lt;br /&gt;
* [http://24ways.org/2006/boost-your-hyperlink-power Boost Your Hyperlink Power] - Jeremy Keith, using CSS to surface vote information&lt;br /&gt;
&lt;br /&gt;
== Related Work ==&lt;br /&gt;
* [[xoxo]]&lt;br /&gt;
* [http://gmpg.org/xfn/ XFN]&lt;br /&gt;
* [http://developers.technorati.com/wiki/attentionxml Attention.xml]&lt;br /&gt;
* [[rellicense]]&lt;br /&gt;
* [[reltag]]&lt;br /&gt;
* [[relnofollow]]&lt;br /&gt;
&lt;br /&gt;
== FAQ ==&lt;br /&gt;
* See [[vote-links-faq]] and the broader [[rel-faq]].&lt;br /&gt;
* See also [[vote-links-issues]] for issues which have been raised with the votelinks [[microformat]].&lt;br /&gt;
&lt;br /&gt;
[[Category:Specifications]]&lt;br /&gt;
[[Category:vote-links]]&lt;/div&gt;</summary>
		<author><name>Alik</name></author>
	</entry>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=vote-links&amp;diff=43051</id>
		<title>vote-links</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=vote-links&amp;diff=43051"/>
		<updated>2010-09-05T20:58:54Z</updated>

		<summary type="html">&lt;p&gt;Alik: Syntax highlighting&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;entry-title&amp;gt;Vote Links&amp;lt;/entry-title&amp;gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
== Specification 2005 ==&lt;br /&gt;
=== Editor ===&lt;br /&gt;
* [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc.], formerly of [http://microsoft.com/ Microsoft Corporation])&lt;br /&gt;
&lt;br /&gt;
=== Concept ===&lt;br /&gt;
* [http://epeus.blogspot.com/ Kevin Marks] ([http://technorati.com Technorati, Inc.])&lt;br /&gt;
&lt;br /&gt;
=== Authors ===&lt;br /&gt;
* [http://epeus.blogspot.com/ Kevin Marks] ([http://technorati.com Technorati, Inc])&lt;br /&gt;
* [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc])&lt;br /&gt;
&lt;br /&gt;
=== Copyright ===&lt;br /&gt;
{{MicroFormatPublicDomainContributionStatement}}&lt;br /&gt;
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.&lt;br /&gt;
* [[User:Kevin_Marks|Kevin Marks]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.&lt;br /&gt;
&lt;br /&gt;
=== Patents ===&lt;br /&gt;
{{MicroFormatPatentStatement}}&lt;br /&gt;
&lt;br /&gt;
=== Inspiration and Acknowledgments ===&lt;br /&gt;
Thanks to everyone who has given feedback on VoteLinks.  Thanks especially to EtanWexler, who provided the first really good documentation that VoteLinks should be using 'rev' instead of 'rel' (see [[VoteLinksFAQ]]), and John Allsopp who similarly challenged the use of 'rel', and helped co-author the [[RelFAQ]] exploring questions and issues about the use of the HTML4 'rel', 'rev' attributes and linktypes in general.&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
Indexing and tracking applications treat all links as endorsements, or expressions of support. This is a problem, as we need to link to those we disagree with as well, to discuss why.&lt;br /&gt;
&lt;br /&gt;
== Specification ==&lt;br /&gt;
VoteLinks is an [[elemental-microformat|elemental microformat]], one of several [[microformats|microformat]] open standards.&lt;br /&gt;
We propose a set of three new values for the rev attribute of the &amp;lt;a&amp;gt; (hyperlink) tag in HTML.&lt;br /&gt;
&lt;br /&gt;
The new values are &amp;amp;quot;vote-for&amp;amp;quot; &amp;amp;quot;vote-abstain&amp;amp;quot; or &amp;amp;quot;vote-against&amp;amp;quot;, which are mutually exclusive, and represent agreement, abstention or indifference, and disagreement respectively.&lt;br /&gt;
&lt;br /&gt;
A link without an explicit vote 'rev' value is deemed to have value &amp;amp;quot;vote-for&amp;amp;quot; or &amp;amp;quot;vote-abstain&amp;amp;quot;, depending on the application.&lt;br /&gt;
&lt;br /&gt;
Additional human-readable commentary can be added using the existing 'title' attribute, which most browsers show as a rollover.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
 &amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;a rev=&amp;amp;quot;vote-for&amp;amp;quot; href=&amp;amp;quot;http://example.com/cheesevote&amp;amp;quot;  &lt;br /&gt;
   title=&amp;amp;quot;Melt the cheese!&amp;amp;quot;&amp;gt;Do it!&amp;lt;/a&amp;gt;&lt;br /&gt;
&amp;lt;a rev=&amp;amp;quot;vote-against&amp;amp;quot; href=&amp;amp;quot;http://example.com/cheesevote&amp;amp;quot;  &lt;br /&gt;
   title=&amp;amp;quot;Don't melt the cheese!&amp;amp;quot;&amp;gt;Don't do it!&amp;lt;/a&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Deprecated: Using 'rel' for VoteLinks ===&lt;br /&gt;
A previous draft of the specification used the 'rel' attribute instead of the 'rev' attribute.  Analysis and feedback has demonstrated this to have been inappropriate use of the 'rel' attribute, when the 'rev' attribute was much more important.  See the [[RelFAQ]] for more details.&lt;br /&gt;
&lt;br /&gt;
Implementations MAY support links with the VoteLinks values in the 'rel' attribute for backward compatibility with any existing VoteLinks content.&lt;br /&gt;
&lt;br /&gt;
Authors MUST NOT use 'rel' for VoteLinks values.&lt;br /&gt;
&lt;br /&gt;
== XMDP profile ==&lt;br /&gt;
The following is an [http://gmpg.org/xmdp/ XMDP] profile for the [[vote-links]] specification.&lt;br /&gt;
&lt;br /&gt;
=== URLs ===&lt;br /&gt;
This profile is hosted as a separate XMDP file on microformats.org:&lt;br /&gt;
* http://microformats.org/profile/vote-links&lt;br /&gt;
* shortURL: http://ufs.cc/x/vote-links&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
Profiles are referenced in (X)HTML files in the &amp;amp;lt;HEAD&amp;amp;gt; tag, e.g.:&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;head profile='http://microformats.org/profile/vote-links'&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Profile ===&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;dl class=&amp;quot;profile&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;dt id=&amp;quot;rev&amp;quot;&amp;gt;rev&amp;lt;/dt&amp;gt;&lt;br /&gt;
 &amp;lt;dd&amp;gt;&amp;lt;p&amp;gt;&lt;br /&gt;
   &amp;lt;a rel=&amp;quot;help&amp;quot; href=&amp;quot;http://www.w3.org/TR/html401/struct/links.html#adef-rev&amp;quot;&amp;gt;&lt;br /&gt;
     HTML4 definition of the 'rev' attribute.&amp;lt;/a&amp;gt;  &lt;br /&gt;
   Here are additional values as defined in the&lt;br /&gt;
   &amp;lt;a rel=&amp;quot;help start&amp;quot; href=&amp;quot;http://microformats.org/wiki/vote-links&amp;quot;&amp;gt;&lt;br /&gt;
   vote-links specification&amp;lt;/a&amp;gt; &lt;br /&gt;
   .&amp;lt;/p&amp;gt;&lt;br /&gt;
  &amp;lt;dl&amp;gt;&lt;br /&gt;
   &amp;lt;dt id=&amp;quot;vote-for&amp;quot;&amp;gt;vote-for&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;Indicates agreement with or recommendation for the referred resource.&amp;lt;/dd&amp;gt;&lt;br /&gt;
   &amp;lt;dt id=&amp;quot;vote-abstain&amp;quot;&amp;gt;vote-abstain&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;Indicates abstention or indifference for the referred resource.&amp;lt;/dd&amp;gt;&lt;br /&gt;
   &amp;lt;dt id=&amp;quot;vote-against&amp;quot;&amp;gt;vote-against&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;Indicates disagreement with or recommendation against the referred resource.&amp;lt;/dd&amp;gt;&lt;br /&gt;
  &amp;lt;/dl&amp;gt;&lt;br /&gt;
 &amp;lt;/dd&amp;gt;&lt;br /&gt;
&amp;lt;/dl&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Implementations ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
* Following a [http://jyte.com/cl/jyte-should-integrate-microformats-votelinks vote-links claim] [http://jyte.com/profile/brianellin.com Brian Ellin] implemented vote-links on [http://jyte.com Jyte] within less than 30 minutes.&lt;br /&gt;
* [http://moloko.itc.it/paoloblog/ Paolo Massa] created [http://moloko.itc.it/paoloblog/semantic_links/ SemanticLinks], a small Firefox extension that shows vote-for, vote-against links information. (Note the download links for SemanticLinks have been removed by the author.)&lt;br /&gt;
* Wordpress VoteBack (vote-link aware pingback and trackback) plugin is in testing at [http://redmonk.net/archives/2006/12/21/voteback/ VoteBack] ([[User:SteveIvy|Steve Ivy]]) - looking for testers!&lt;br /&gt;
* [http://folksr.de/ Folksr.de] - using VoteLinks to vote on the World Cup 2006&lt;br /&gt;
* [http://www.weboffate.com/ Web of Fate] - has VoteLinks for future predictions&lt;br /&gt;
== Examples in the wild ==&lt;br /&gt;
This section is '''informative'''.&lt;br /&gt;
&lt;br /&gt;
The following sites have implemented VoteLinks , 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 your site marked up with VoteLinks, 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;
&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
          Add new items to the top of the list&lt;br /&gt;
&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
* [http://www.likeorhate.com/ LikeOrHate] uses Vote-Links all over the site, to rate anything, items, comments, users. Valid votes are Like, Hate, Whatever (&amp;quot;vote-for&amp;quot;, &amp;quot;vote-against&amp;quot;, &amp;quot;vote-abstain&amp;quot;). CSS is used to &amp;quot;check&amp;quot; votes so logged users can remember them later.&lt;br /&gt;
* [http://www.weboffate.com/ Web of Fate] Web of Fate uses Vote-Links for prediction probability scoring. Users can vote Agree, Disagree, Witness (&amp;quot;vote-for&amp;quot;, &amp;quot;vote-against&amp;quot;, &amp;quot;vote-abstain&amp;quot;)&lt;br /&gt;
* [http://tommorris.org/blog/ Tom Morris] has vote links on del.icio.us links (based on tags &amp;quot;vote-for&amp;quot;, &amp;quot;vote-against&amp;quot; and &amp;quot;vote-abstain&amp;quot;).&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
          Add new items to the top of the list&lt;br /&gt;
&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
=== Normative References ===&lt;br /&gt;
* [http://gmpg.org/xmdp/ XMDP]&lt;br /&gt;
&lt;br /&gt;
=== Informative References ===&lt;br /&gt;
* [http://www.artweb-design.de/articles/2006/06/05/distributed-votings-using-microformats Distributed votings using microformats] from Artweb Design&lt;br /&gt;
* [http://24ways.org/2006/boost-your-hyperlink-power Boost Your Hyperlink Power] - Jeremy Keith, using CSS to surface vote information&lt;br /&gt;
&lt;br /&gt;
== Related Work ==&lt;br /&gt;
* [[xoxo]]&lt;br /&gt;
* [http://gmpg.org/xfn/ XFN]&lt;br /&gt;
* [http://developers.technorati.com/wiki/attentionxml Attention.xml]&lt;br /&gt;
* [[rellicense]]&lt;br /&gt;
* [[reltag]]&lt;br /&gt;
* [[relnofollow]]&lt;br /&gt;
&lt;br /&gt;
== FAQ ==&lt;br /&gt;
* See [[vote-links-faq]] and the broader [[rel-faq]].&lt;br /&gt;
* See also [[vote-links-issues]] for issues which have been raised with the votelinks [[microformat]].&lt;br /&gt;
&lt;br /&gt;
[[Category:Specifications]]&lt;br /&gt;
[[Category:vote-links]]&lt;/div&gt;</summary>
		<author><name>Alik</name></author>
	</entry>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=rel-tag&amp;diff=43050</id>
		<title>rel-tag</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=rel-tag&amp;diff=43050"/>
		<updated>2010-09-05T20:58:24Z</updated>

		<summary type="html">&lt;p&gt;Alik: Syntax highlighting&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;entry-title&amp;gt;rel=&amp;quot;tag&amp;quot;&amp;lt;/entry-title&amp;gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
== Draft Specification 2005-01-10 ==&lt;br /&gt;
; Editors/Authors&lt;br /&gt;
:[http://tantek.com/ Tantek Çelik]&lt;br /&gt;
:[http://epeus.blogspot.com/ Kevin Marks]&lt;br /&gt;
&lt;br /&gt;
;Concept&lt;br /&gt;
:[http://powazek.com/ Derek Powazek]&lt;br /&gt;
&lt;br /&gt;
;short URL&lt;br /&gt;
:http://tr.im/reltag&lt;br /&gt;
&lt;br /&gt;
=== Copyright ===&lt;br /&gt;
{{MicroFormatCopyrightStatement2004}}&lt;br /&gt;
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.&lt;br /&gt;
* [[User:Kevin Marks|Kevin Marks]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.&lt;br /&gt;
** When all authors/editors have done so, we can remove the MicroFormatCopyrightStatement template reference and replace it with the MicroFormatPublicDomainContributionStatement.&lt;br /&gt;
&lt;br /&gt;
=== Patents ===&lt;br /&gt;
{{MicroFormatPatentStatement}}&lt;br /&gt;
&lt;br /&gt;
== Abstract ==&lt;br /&gt;
[[Rel-Tag]] is one of several [[MicroFormats]].  By adding &amp;lt;code&amp;gt;rel=&amp;amp;quot;tag&amp;amp;quot;&amp;lt;/code&amp;gt; to a hyperlink, a page indicates that the destination of that hyperlink is an author-designated &amp;amp;quot;tag&amp;amp;quot; (or keyword/subject) for the current page. Note that a tag may just refer to a major portion of the current page (i.e. a blog post). e.g. by placing this link on a page,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&amp;lt;a href=&amp;amp;quot;http://technorati.com/tag/tech&amp;amp;quot; rel=&amp;amp;quot;tag&amp;amp;quot;&amp;gt;tech&amp;lt;/a&amp;gt;&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
the author indicates that the page (or some portion of the page) has the tag &amp;amp;quot;tech&amp;amp;quot;.&lt;br /&gt;
&lt;br /&gt;
The linked page SHOULD exist, and it is the linked page, rather than the link text, that defines the tag. The last path component of the URL&lt;br /&gt;
is the text of the tag, so &lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&amp;lt;a href=&amp;amp;quot;http://technorati.com/tag/tech&amp;amp;quot; rel=&amp;amp;quot;tag&amp;amp;quot;&amp;gt;fish&amp;lt;/a&amp;gt;&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
would indicate the tag &amp;amp;quot;tech&amp;amp;quot; rather than &amp;amp;quot;fish&amp;amp;quot;.&lt;br /&gt;
&lt;br /&gt;
== Scope ==&lt;br /&gt;
rel=&amp;amp;quot;tag&amp;amp;quot; is specifically designed for &amp;amp;quot;tagging&amp;amp;quot; content, typically web pages (or portions thereof, like blog posts).&lt;br /&gt;
&lt;br /&gt;
rel=&amp;amp;quot;tag&amp;amp;quot; is NOT designed for &amp;amp;quot;tagging&amp;amp;quot; arbitrary URLs or external content.  There is demand for a general decentralized syntax for tagging URLs external to the current page, but this is not meant for that.  See [[xfolk|xFolk]] and [[hreview|hReview]] for ways to tag arbitrary URLs.&lt;br /&gt;
&lt;br /&gt;
If you need to define tags as part of a more specialized format,  rel=&amp;amp;quot;tag&amp;amp;quot; is the recommended way to do so, and [[xfolk|xFolk]], [[hreview|hReview]], [[hcard |hCard]], [[hcalendar|hCalendar]] and [[hrecipe|hRecipe]] all do this.&lt;br /&gt;
&lt;br /&gt;
== XMDP profile ==&lt;br /&gt;
See [[rel-tag-profile]].&lt;br /&gt;
&lt;br /&gt;
== Tag Spaces ==&lt;br /&gt;
&lt;br /&gt;
Tags are embedded in HTTP URIs in a well-defined manner so that the tag embedded in an HTTP URI can be mechanically extracted from that URI. Specifically, the last segment of the path portion of the URI (after the final &amp;quot;/&amp;quot; character) contains the tag value. For example, the URI &amp;lt;source lang=html4strict&amp;gt;http://www.example.com/tags/foo&amp;lt;/source&amp;gt; contains the tag &amp;amp;quot;foo&amp;amp;quot;. &lt;br /&gt;
&lt;br /&gt;
Thus, for the purposes of comparing two HTTP URIs as tags, the last segment of the path portion should be extracted and only that value (that value of the tag) should be compared.&lt;br /&gt;
&lt;br /&gt;
''Need more formal language about comparison and extraction process.''&lt;br /&gt;
&lt;br /&gt;
The destination of a rel=&amp;amp;quot;tag&amp;amp;quot; hyperlink is required to be a tag space (a place that collates or defines tags), where the last segment of the path of the URL is the tag, e.g. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;http://technorati.com/tag/tech &amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
is a URL for the tag &amp;amp;quot;tech&amp;amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Tags may only be placed in the URL path, and only in the last segment of the path.  Tags may not be placed in query parameters or fragment identifiers.  e.g.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;http://technorati.com/tag/tech?tag=fish#emu &amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
is still a URL for the tag &amp;amp;quot;tech&amp;amp;quot;, not &amp;amp;quot;fish&amp;amp;quot; or &amp;amp;quot;emu&amp;amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Since the only part of a tag space URL of which any structure is required is the last path segment, a tag space URL can be hosted at any domain.  Authors may choose to link to a tag at a particular tag space in order to provide a specific meaning.  E.g. a tag for technology could link to:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;  http://en.wikipedia.org/wiki/Technology &amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Trailing slashes in tag URLs are ignored, that is:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;  http://technorati.com/tag/Technology/ &amp;lt;/source&amp;gt;&lt;br /&gt;
as a rel-tag URL is treated as:&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;  http://technorati.com/tag/Technology &amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Encoding issues ==&lt;br /&gt;
Spaces can be encoded either as &amp;lt;code&amp;gt;+&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;%20&amp;lt;/code&amp;gt;. Unicode characters are encoded as specified in [http://www.ietf.org/rfc/rfc3986.txt &amp;lt;nowiki&amp;gt;RFC 3986&amp;lt;/nowiki&amp;gt;]. For example:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&amp;lt;a href=&amp;amp;quot;http://technorati.com/tag/Sant%C3%A9+et+bien-%C3%AAtre&amp;amp;quot; rel=&amp;amp;quot;tag&amp;amp;quot;&amp;gt;Santé et bien-être&amp;lt;/a&amp;gt; &amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note that if using Wikipedia as a tagspace, as discussed above, you should use &amp;lt;code&amp;gt;%20&amp;lt;/code&amp;gt; as they remap '+' to &amp;lt;code&amp;gt;%2B&amp;lt;/code&amp;gt;, causing  a page with a plus sign in the title (which usually does not exist) to appear.&lt;br /&gt;
&lt;br /&gt;
== Tags Are Visible Metadata ==&lt;br /&gt;
&amp;lt;code&amp;gt;rel=&amp;amp;quot;tag&amp;amp;quot;&amp;lt;/code&amp;gt; hyperlinks are intended to be visible links on pages and posts.  This is in stark contrast to meta keywords (which were invisible and typically never revealed to readers), and thus is at least somewhat more resilient to the problems which plagued meta keywords.&lt;br /&gt;
&lt;br /&gt;
Making tag hyperlinks visible has the additional benefit of making it more obvious to readers if a page is abusing tag links, and thus providing more peer pressure for better behavior.  It also makes it more obvious to authors, who may not always be aware what invisible metadata is being generated on their behalf.&lt;br /&gt;
&lt;br /&gt;
As a result the invisible tag link syntax variant: &amp;lt;code&amp;gt;&amp;lt;link rel=&amp;amp;quot;tag&amp;amp;quot; href=&amp;amp;quot;...&amp;amp;quot; /&amp;gt;&amp;lt;/code&amp;gt; SHOULD NOT be supported by implementations.&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 implemented rel-tag, 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 your site is marked up with rel-tag, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page like [[rel-tag-examples-in-wild]].&amp;lt;span id=&amp;quot;Examples_in_the_Wild&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
* [http://en.newsgrail.com/ Newsgrail] uses rel-tag for an implementation of structured sematic tagging by [http://opencalais.com/ OpenCalais].&lt;br /&gt;
* [http://davidswain.co.uk Actor David Swain] uses rel-tag on all &amp;quot;tag&amp;quot; links on his site each pointing to its own tag-space.&lt;br /&gt;
* [http://beeets.com beeets] is a tag-based event search engine that uses rel-tag on all &amp;quot;tag&amp;quot; links, each pointing to its own tag-space.&lt;br /&gt;
* [http://www.beginrunning.com/ Begin Running] uses rel-tag on pages containing tagged content.&lt;br /&gt;
* [http://laibcoms.asia/blog/ Snow World] uses rel-tag on all &amp;quot;tag&amp;quot; links.  As is built in [http://b2evolution.net b2evolution].&lt;br /&gt;
* [http://gameshogun.ws/ gameshogun™] uses rel-tag on all &amp;quot;tag&amp;quot; links.  A [http://b2evolution.net b2evolution] implementation.&lt;br /&gt;
* [http://huffduffer.com/ Huffduffer] uses rel-tag on every page, pointing to its own tag space e.g. http://huffduffer.com/tags/microformats&lt;br /&gt;
* [http://www.pantrymothtrap.com/ Pantry Moth Traps] implements the rel-tag in articles where an authoritative source is known.  (for example in the article [http://www.pantrymothtrap.com/MothTrapsPick.html Moth Trap Picks] the tag [http://www.cleanertoday.com/tag/moth%20trap Moth Trap])&lt;br /&gt;
* [http://www.hightechcville.com/ HighTechCville] uses rel-tag on all the pages listing tagged content for [http://www.hightechcville.com/people people], [http://www.hightechcville.com/organizations organizations] and [http://www.hightechcville.com/events events] related to high tech in Charlottesville, VA.&lt;br /&gt;
* [http://skateboardspot.info skateboardspot.info] uses rel-tag in spotguide entries which are added to the site and categorized by the users (for example: [http://skateboardspot.info/cat/spotguide/action/view/id/1 “El Toro High School” spotguide entry]).&lt;br /&gt;
* [http://www.idoneos.com Idoneos.com] uses rel-tag for conceptual links to its own tag space, a collection of 'concepts' (mostly spanish).&lt;br /&gt;
* [http://www.professionalontheweb.com Professional On The Web]  uses rel-tag for user entered tags which categorize web professionals and freelancers.&lt;br /&gt;
* [https://www.coderesort.com/p/epicode/wiki/CloudCuckoo CloudCuckoo] (secure site but open to all) an [http://www.episerver.com EPiServer] module distributed free by [http://www.interakting.co.uk Interakting], generates tag clouds with rel-tag links.&lt;br /&gt;
* [http://www.lifetime.com Lifetime.com] uses rel- and rev-tags in all content pages.&lt;br /&gt;
* [http://www.my-warehouse.de the my-Warehouse shopsystem] implements rel-tags in box headings and categories links.&lt;br /&gt;
* Joseph Bergantine uses tags to categorize [http://bergantinedesign.us/wallpaper/ wallpapers] and [http://bergantinedesign.us/blog/my-name-is-rachel-corrie blog posts]&lt;br /&gt;
* [http://www.codesignville.com Codesignville] uses rel-tag to indicate content categories.&lt;br /&gt;
* [http://www.bossalive.com BossaLive] uses rel-tag for tagging music. Publishes rel-tags for album, artist and genre.&lt;br /&gt;
** Also uses [[hcard|hCard]] on user profile pages.&lt;br /&gt;
* [http://www.qmpeople.com/ qmpeople] Uses rel-tag for translated tags into english, french and italian to meet new friends in different countries.&lt;br /&gt;
* [http://www.keevu.com Keevu.com] uses rel-tag to indicate content categories on most pages, like [http://www.keevu.com/venues venues]&lt;br /&gt;
* [http://www.amazingincredible.com Amazing Incredible] uses rel-tag on content pages&lt;br /&gt;
* [http://www.auctionlink.com.au AuctionLink] uses rel-tag on [http://www.auctionlink.com.au/TagList/Auctioneers/ Auction Sales Listings] tags.&lt;br /&gt;
** Could also use [[hcard|hCard]], e.g. on [http://www.auctionlink.com.au/Auctioneers/Auctioneer/Bonhams_Goodman_1/] [[User:AndyMabbett|Andy Mabbett]]&lt;br /&gt;
* Christian Hess uses rel-tag on his [http://www.hess-cr.com homepage blog] and several other pages of his site.&lt;br /&gt;
* [http://spacedust.atspace.com/ Spacedust] uses rel-tag to mark up gallery pages.&lt;br /&gt;
* [http://my.opera.com/dstorey/blog/ My Opera] uses rel-tag for tags on all user's blog entries.&lt;br /&gt;
* [http://dev.opera.com/articles/view/making-wii-friendly-pages/ Dev Opera] uses rel-tag on all article tags.&lt;br /&gt;
* [http://www.international.unt.edu UNT International] uses rel-tag to indicate content categories on most pages&lt;br /&gt;
* [http://yedda.com Yedda] - Yedda publishes rel-tags for all of the tags the people entered on themselves as well as on all tags entered on questions asked on Yedda.&lt;br /&gt;
* [http://www.lingr.com Lingr] publishes rel-tags for all user entered tags.&lt;br /&gt;
* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] rel-tags for user entered tags.&lt;br /&gt;
* [http://eventful.com Eventful] publishes rel-tags for user entered tags.&lt;br /&gt;
* [http://spinn3r.com Spinn3r] implements rel-tag as well as RSS and Atom subject and categories.&lt;br /&gt;
* [http://www.weboffate.com Web of Fate] publishes rel-tags for future predictions.&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 rel-tag links. If you have a rel-tag 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 like [[rel-tag-implementations]].&lt;br /&gt;
&lt;br /&gt;
* [http://b2evolution.net b2evolution] A blog platform which generates rel-tag for all tags on blog posts (starting from v3.x).&lt;br /&gt;
* [http://www.textcube.org Textcube.org] makes a blogging tool, Textcube which generates rel-tag for tags on blog posts.&lt;br /&gt;
* [http://hashtags.org/ HashTags] tags Twitter posts, converting &amp;quot;#example&amp;quot; into a tag of &amp;quot;example&amp;quot;&lt;br /&gt;
* [http://ikiwiki.info ikiwiki] generates rel-tag for all tagged pages (as of version 2.6)&lt;br /&gt;
* [http://www.hubtag.com HubTag] helps users find a unique tag across the web for their event - eg. JohnAndBettysWeddingWimbledonMarch07&lt;br /&gt;
* [http://www.necctar.com Necctar] is a search engine exclusively based on tag microformat parsing and processing. Necctar uses tags entered by bloggers to index the world wide web&lt;br /&gt;
* Nutch has a [[rel-tag]] parser [http://www.mail-archive.com/nutch-commits@lucene.apache.org/msg01014.html committed to their svn repository].&lt;br /&gt;
* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables rel-tagging from within Dreamweaver 8.&lt;br /&gt;
* [http://scooch.gr0w.com/ Scooch] slide show creator allows authors to generate rel-tags and group slide shows by rel-tag via a list or cloud with tag usage count.&lt;br /&gt;
* The Freetag plugin for the [http://www.s9y.org Serendipity] blog software supports rel-tags on a per-entry basis, as well as inside of its tag clouds.  (The Freetag plugin is available inside of SPARTACUS)&lt;br /&gt;
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding rel-tags and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].&lt;br /&gt;
* [http://www.rainskit.com/blog/493/trutags-a-tagging-plugin-for-textpattern tru_tags] is a plugin for [http://textpattern.com/ Textpattern] that supports rel-tagging blog posts via the Keywords field.&lt;br /&gt;
* [http://news.livejournal.com/86492.html?thread=24881884 LiveJournal] - see also [http://www.livejournal.com/support/faq.bml?cat=tags their FAQ regarding their tags support]&lt;br /&gt;
* [http://trac.labnotes.org/cgi-bin/trac.cgi/wiki/TagsLinks TagsLinks] Turn each tag into links that let you find related content on tagging services.&lt;br /&gt;
* [http://www.octofinder.com OctoFinder] uses rel-tag for all live news tag clouds.&lt;br /&gt;
* [http://dev.wp-plugins.org/wiki/BunnysTechnoratiTags Tag plugin for WordPress]&lt;br /&gt;
** Note that some sites using WordPress (http://microformatique.com/ for instance) are getting incorrect tags. The tag is ?cat=12 instead of the actual tag value.&lt;br /&gt;
* [http://noone.org/blog/tags/Tagging Tag plugin for Blosxom]&lt;br /&gt;
* Technorati first implemented rel-tag in its [http://technorati.com/tag/ Technorati Tags] service. Technorati indexes rel-tag tags.&lt;br /&gt;
* [http://consumingexperience.blogspot.com/2005/12/updated-multiple-word-technorati-tag.html Greasemonkey script for Firefox that generates tags for Blogger]&lt;br /&gt;
* [http://tools.microformatic.com/help/xhtml/rel-lint/ rel-lint] is a validation tool by [[User:DrewMcLellan|Drew McLellan]] that will validate existence of rel-tag attributes.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
=== Normative References ===&lt;br /&gt;
* [http://www.w3.org/TR/REC-html40/ HTML 4]&lt;br /&gt;
* [http://www.w3.org/TR/xhtml1/ XHTML 1]&lt;br /&gt;
* [http://gmpg.org/xmdp/ XMDP]&lt;br /&gt;
* RFC 3986 specifies URL syntax.  Section 3.3 specifies URL paths and path segments.&lt;br /&gt;
&lt;br /&gt;
=== Informative References ===&lt;br /&gt;
* [[hreview|hReview]] uses rel-tag for tags and scalar tags&lt;br /&gt;
* [[xfolk|xFolk]] uses rel-tag to build a distributed remote resource tagging construct&lt;br /&gt;
* [http://developers.technorati.com/wiki/attentionxml Attention.XML] uses rel-tag for reader tagging of pages, posts, feeds&lt;br /&gt;
* [[hcard|hCard]] can use rel-tag for categories&lt;br /&gt;
* [[hcalendar|hCalendar]] can use rel-tag for categories&lt;br /&gt;
* [http://technorati.com/help/tags.html Using Technorati Tags]&lt;br /&gt;
* Contributed from http://developers.technorati.com/wiki/RelTag&lt;br /&gt;
* [http://microformatique.com/?p=61 Know your rel-tag] at microformatique.com&lt;br /&gt;
&lt;br /&gt;
== Discussions ==&lt;br /&gt;
* Feedback is encouraged on the [[rel-tag-feedback]] page.&lt;br /&gt;
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].&lt;br /&gt;
* History: [http://www.powazek.com/2005/07/000532.html How Tags Happened at Technorati] by [http://www.powazek.com/ Derek Powazek]&lt;br /&gt;
&lt;br /&gt;
=== Q&amp;amp;A ===&lt;br /&gt;
* If you have any questions about rel-tag, check the [[rel-faq|rel FAQ]] first for general rel attribute questions, then check the [[rel-tag-faq|rel-tag FAQ]], and then if you don't find answers, ask your question on the [http://microformats.org/discuss microformats-discuss] mailing list.&lt;br /&gt;
&lt;br /&gt;
==Related pages==&lt;br /&gt;
{{rel-tag-related-pages}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Specifications]]&lt;br /&gt;
[[Category:rel-tag]]&lt;/div&gt;</summary>
		<author><name>Alik</name></author>
	</entry>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=rel-license&amp;diff=43049</id>
		<title>rel-license</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=rel-license&amp;diff=43049"/>
		<updated>2010-09-05T20:57:11Z</updated>

		<summary type="html">&lt;p&gt;Alik: Syntax highlighting&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;entry-title&amp;gt;rel=&amp;quot;license&amp;quot;&amp;lt;/entry-title&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p class=&amp;quot;entry-summary&amp;quot;&amp;gt;Rel-License is a simple, open, format for indicating content licenses which is  embedable in HTML or XHTML, Atom, RSS, and arbitrary XML. Rel-License is one of several [[microformats|microformat]] open standards.&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Specification 2005-02-06 ==&lt;br /&gt;
=== Author ===&lt;br /&gt;
[http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc.], formerly of [http://microsoft.com/ Microsoft Corporation])&lt;br /&gt;
&lt;br /&gt;
=== Copyright ===&lt;br /&gt;
Per the public domain release on [[User:Tantek|my user page]], this specification is released into the public domain.&lt;br /&gt;
&lt;br /&gt;
{{MicroFormatPublicDomainContributionStatement}}&lt;br /&gt;
&lt;br /&gt;
=== Patents ===&lt;br /&gt;
{{MicroFormatPatentStatement}}&lt;br /&gt;
&lt;br /&gt;
== Abstract ==&lt;br /&gt;
Rel-License is one of several microformats.  By adding &amp;lt;code&amp;gt;rel=&amp;quot;license&amp;quot;&amp;lt;/code&amp;gt; to a hyperlink, a page indicates that the destination of that hyperlink is a license for the current page. E.g. with the following hyperlink:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;a href=&amp;quot;http://creativecommons.org/licenses/by/2.0/&amp;quot; rel=&amp;quot;license&amp;quot;&amp;gt;cc by 2.0&amp;lt;/a&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
the author indicates that the page is licensed under a Creative Commons 2.0 Attribution Required license.&lt;br /&gt;
&lt;br /&gt;
== Multiple Licenses ==&lt;br /&gt;
Multiple such rel=&amp;quot;license&amp;quot; hyperlinks indicate that the page is available under any of the referred licenses.  E.g. the following hyperlinks could be used to declare that a page is available under either a Creative Commons 2.0 Attribution Required license or the Apache 2.0 license:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&amp;lt;a href=&amp;quot;http://creativecommons.org/licenses/by/2.0/&amp;quot; rel=&amp;quot;license&amp;quot;&amp;gt;cc by 2.0&amp;lt;/a&amp;gt;&lt;br /&gt;
&amp;lt;a href=&amp;quot;http://www.apache.org/licenses/LICENSE-2.0&amp;quot; rel=&amp;quot;license&amp;quot;&amp;gt;Apache 2.0&amp;lt;/a&amp;gt;&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== XMDP profile ==&lt;br /&gt;
The following is an [http://gmpg.org/xmdp/ XMDP] profile for the [[rel-license]] specification.&lt;br /&gt;
&lt;br /&gt;
=== URLs ===&lt;br /&gt;
This profile is hosted as a separate XMDP file on microformats.org:&lt;br /&gt;
* http://microformats.org/profile/rel-license&lt;br /&gt;
* shortURL: http://ufs.cc/x/rel-license&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
Profiles are referenced in (X)HTML files in the &amp;amp;lt;HEAD&amp;amp;gt; tag, e.g.:&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;head profile='http://microformats.org/profile/rel-license'&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Profile ===&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;dl class=&amp;quot;profile&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;dt id=&amp;quot;rel&amp;quot;&amp;gt;rel&amp;lt;/dt&amp;gt;&lt;br /&gt;
 &amp;lt;dd&amp;gt;&amp;lt;p&amp;gt;&lt;br /&gt;
   &amp;lt;a rel=&amp;quot;help&amp;quot; href=&amp;quot;http://www.w3.org/TR/html401/struct/links.html#adef-rel&amp;quot;&amp;gt;&lt;br /&gt;
     HTML4 definition of the 'rel' attribute.&amp;lt;/a&amp;gt;  &lt;br /&gt;
   Here is an additional value as defined in the&lt;br /&gt;
   &amp;lt;a rel=&amp;quot;help start&amp;quot; href=&amp;quot;http://microformats.org/wiki/rel-license&amp;quot;&amp;gt;&lt;br /&gt;
   rel-license specification&amp;lt;/a&amp;gt; &lt;br /&gt;
   .&amp;lt;/p&amp;gt;&lt;br /&gt;
  &amp;lt;dl&amp;gt;&lt;br /&gt;
   &amp;lt;dt id=&amp;quot;license&amp;quot;&amp;gt;license&amp;lt;/dt&amp;gt;&lt;br /&gt;
   &amp;lt;dd&amp;gt;Indicates that the referred resource is a license for the referring page.&amp;lt;/dd&amp;gt;&lt;br /&gt;
  &amp;lt;/dl&amp;gt;&lt;br /&gt;
 &amp;lt;/dd&amp;gt;&lt;br /&gt;
&amp;lt;/dl&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Implementations ==&lt;br /&gt;
* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of rel-license links from within Dreamweaver 8. Includes (cc) defaults.&lt;br /&gt;
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding rel license and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].&lt;br /&gt;
* [http://creativecommons.org/license/ Creative Commons (cc) license chooser]&lt;br /&gt;
* [http://search.yahoo.com/cc Yahoo! (cc) search] (appears to pick up link-rel in a but not link elements)&lt;br /&gt;
* [http://www.google.com/support/bin/answer.py?answer=29508 Google &amp;quot;Usage Rights&amp;quot; search] (also appears to pick up link-rel in a but not link elements)&lt;br /&gt;
&lt;br /&gt;
== List of Licenses ==&lt;br /&gt;
&lt;br /&gt;
* [http://creativecommons.org CC]&lt;br /&gt;
* [http://www.opensource.org/licenses/ Open Source Initiative] licenses -- mostly software-focused&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
=== Normative References ===&lt;br /&gt;
* [http://gmpg.org/xmdp/ XMDP]&lt;br /&gt;
&lt;br /&gt;
=== Informative References ===&lt;br /&gt;
* 20040211 rel=&amp;quot;license&amp;quot; first proposed in presentation [http://tantek.com/presentations/2004etech/realworldsemanticspres.html real world semantics] at 2004 O'Reilly Emerging Technologies Conference, San Diego, CA, USA.&lt;br /&gt;
* 20040225 [http://tantek.com/log/2004/02.html#d25t1805 Thorough discussion of rel=&amp;quot;license&amp;quot;] including advantages and presentation possibilities. &lt;br /&gt;
* [http://creativecommons.org/licenses/by/2.0/ Creative Commons 2.0 By (Attribution Required) license]&lt;br /&gt;
* [http://www.apache.org/licenses/LICENSE-2.0 Apache 2.0 license]&lt;br /&gt;
* Contributed from http://developers.technorati.com/wiki/RelLicense&lt;br /&gt;
* [http://microformatique.com/?p=60 Know your rel-license at Microformatique]&lt;br /&gt;
&lt;br /&gt;
== see also ==&lt;br /&gt;
* [[rel-license-issues]] - issues which have been raised with this microformat.&lt;br /&gt;
* [[rel-faq]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Specifications]]&lt;br /&gt;
[[Category:rel-license]]&lt;/div&gt;</summary>
		<author><name>Alik</name></author>
	</entry>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=include-pattern&amp;diff=43048</id>
		<title>include-pattern</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=include-pattern&amp;diff=43048"/>
		<updated>2010-09-05T20:54:40Z</updated>

		<summary type="html">&lt;p&gt;Alik: Unicode&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt;Include Pattern&amp;lt;/h1&amp;gt;&lt;br /&gt;
{{TOC-right}}&lt;br /&gt;
The include pattern is a microformat design pattern, providing a mechanism to include a portion of data from one area of a page into another area of the same page, allowing the data to be reused by multiple microformats, independent of content order, without repeating all the information. The following is documentation for re-use of the pattern in other microformats, and for publishers working with it.&lt;br /&gt;
&lt;br /&gt;
;Editors: Tantek Çelik&lt;br /&gt;
: Ben Ward&lt;br /&gt;
&lt;br /&gt;
== background ==&lt;br /&gt;
&lt;br /&gt;
[[hresume|hResume]] needed the ability to include a name from one hCard at the top of a resume — the person's contact details — into the separate hCards used in the same person's employment history. Repeating name information would not have matched the existing publishing practices used in Resumes and Curriculum Vitæ, would be inconvenient to publishers, and irritating to consumers. The include pattern is a mechanism to reference data from the same page, avoiding repetition, or duplicate visible information.&lt;br /&gt;
&lt;br /&gt;
== scope ==&lt;br /&gt;
&lt;br /&gt;
The include pattern is strictly limited to the scope of the current page. It cannot be used to include content from other URLs.&lt;br /&gt;
&lt;br /&gt;
== quick reference==&lt;br /&gt;
&lt;br /&gt;
The include-pattern is a mechanism to include content from one microformat into another microformat elsewhere in the same document, using hyperlinks or &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt;. For example:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&amp;lt;a class=&amp;quot;include&amp;quot; href=&amp;quot;#author&amp;quot;&amp;gt;James Levine&amp;lt;/a&amp;gt;&amp;lt;/source&amp;gt;&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&amp;lt;object class=&amp;quot;include&amp;quot; data=&amp;quot;#author&amp;quot;&amp;gt;&amp;lt;/object&amp;gt;&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In specifications which cite the include-pattern, either of the above code snippets {{must}} cause a microformats parser to replace the &amp;lt;code&amp;gt;A&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt; element with class name &amp;quot;include&amp;quot; with the content fragment with ID &amp;quot;author&amp;quot;. Full examples follow.&lt;br /&gt;
&lt;br /&gt;
== in general==&lt;br /&gt;
&lt;br /&gt;
To reference includes, use an include element with class name &amp;quot;include&amp;quot; and a document fragment identifier. The content to be included should have an ID attribute set, and that ID should be referenced from the HREF or DATA attribute at the point of inclusion.&lt;br /&gt;
&lt;br /&gt;
The include element with class name &amp;quot;include&amp;quot; indicates a reference to a sub-tree elsewhere in the document which {{must}} be included in-place by microformat parsers. That is, the element with class &amp;quot;include&amp;quot; is _replaced_ in the DOM by the referenced sub-tree. Note that this means all other class names on the include element are discarded. Microformat class names should be included on the target of the include, not on the include element itself.&lt;br /&gt;
&lt;br /&gt;
To prevent infinite loops, if a class=&amp;quot;include&amp;quot; refers to itself or to an ancestor in the parse tree, then it is ignored and has no effect on the parser.&lt;br /&gt;
&lt;br /&gt;
Per the [[include-pattern#Scope|scope]], the &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt; 'data' attribute and hyperlink 'href' attribute {{must}} be local ID references when used as include pattern instances. External references (requiring a consuming application to load an external resource) are not supported by this method.&lt;br /&gt;
&lt;br /&gt;
There are two HTML elements available to reference includes, hyperlink/Anchor and &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt;. They are documented below.&lt;br /&gt;
&lt;br /&gt;
These methods of property indirection via a hyperlink element can apply to any/all properties in class-based microformats, but should only be used where a microformat explicitly states that the include-pattern is a dependency. For example, [[XOXO]] does not reference the include-pattern at this time, so sub-trees cannot be included by reference in XOXO. [[hResume]] and [[hReview]] do reference the include pattern.&lt;br /&gt;
&lt;br /&gt;
=== Hyperlink ===&lt;br /&gt;
&lt;br /&gt;
The recommended way to reference includes within microformats is to use a hyperlink.&lt;br /&gt;
&lt;br /&gt;
==== Hyperlink example====&lt;br /&gt;
&lt;br /&gt;
Here is an [[hcard|hCard]] for a bar, included at the top of a reviews page, shown here as a verbose hCard.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;vcard&amp;quot; id=&amp;quot;bricklayers-card&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;div class=&amp;quot;fn org&amp;quot;&amp;gt;The Bricklayers Arms&amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;div class=&amp;quot;adr&amp;quot;&amp;gt;&lt;br /&gt;
     &amp;lt;span class=&amp;quot;street-address&amp;quot;&amp;gt;31 Gresse Street&amp;lt;/span&amp;gt;,&lt;br /&gt;
     &amp;lt;span class=&amp;quot;locality&amp;quot;&amp;gt;Fitzrovia&amp;lt;/span&amp;gt;&lt;br /&gt;
     &amp;lt;span class=&amp;quot;region&amp;quot;&amp;gt;London&amp;lt;/span&amp;gt;&lt;br /&gt;
     &amp;lt;span class=&amp;quot;postal-code&amp;quot;&amp;gt;W1T 1QS&amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Elsewhere on the page, a number of reviews reference the hcard in the item property. Rather than repeat all the verbose detail, only the name is reprinted and the detailed hcard referenced using the include-pattern.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;hreview&amp;quot;&amp;gt;&lt;br /&gt;
   &amp;lt;h1 class=&amp;quot;summary&amp;quot;&amp;gt;A great venue for monthly gatherings!&amp;lt;/h1&amp;gt;&lt;br /&gt;
   &amp;lt;div class=&amp;quot;item&amp;quot;&amp;gt;&amp;lt;a class=&amp;quot;include&amp;quot; href=&amp;quot;#bricklayers-card&amp;quot;&amp;gt;The Bricklayers Arms&amp;lt;/a&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
   &amp;lt;p class=&amp;quot;description&amp;quot;&amp;gt;Wonderful pub, cheap beer, open fire to warm mince pies at Christmas.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hreview&amp;quot;&amp;gt;&lt;br /&gt;
   &amp;lt;h1 class=&amp;quot;summary&amp;quot;&amp;gt;Takes a while to thin out, but!&amp;lt;/h1&amp;gt;&lt;br /&gt;
   &amp;lt;div class=&amp;quot;item&amp;quot;&amp;gt;&amp;lt;a class=&amp;quot;include&amp;quot; href=&amp;quot;#bricklayers-card&amp;quot;&amp;gt;The Bricklayers Arms&amp;lt;/a&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
   &amp;lt;p class=&amp;quot;rating&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt;5&amp;lt;/span&amp;gt;/&amp;lt;span class=&amp;quot;best&amp;quot;&amp;gt;5&amp;lt;/span&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Note that you {{must}} include content within the anchor element. See the notes and issues below.&lt;br /&gt;
&lt;br /&gt;
A microformat parser {{must}} treat each review as follows, with the hyperlink include element completely replaced (including inner-text) by the sub-tree that was referenced:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;hreview&amp;quot;&amp;gt;&lt;br /&gt;
   &amp;lt;h1 class=&amp;quot;summary&amp;quot;&amp;gt;A great venue for monthly gatherings!&amp;lt;/h1&amp;gt;&lt;br /&gt;
   &amp;lt;div class=&amp;quot;item&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;div class=&amp;quot;vcard&amp;quot; id=&amp;quot;bricklayers-card&amp;quot;&amp;gt;&lt;br /&gt;
        &amp;lt;div class=&amp;quot;fn org&amp;quot;&amp;gt;The Bricklayers Arms&amp;lt;/div&amp;gt;&lt;br /&gt;
        &amp;lt;div class=&amp;quot;adr&amp;quot;&amp;gt;&lt;br /&gt;
           &amp;lt;span class=&amp;quot;street-address&amp;quot;&amp;gt;31 Gresse Street&amp;lt;/span&amp;gt;,&lt;br /&gt;
           &amp;lt;span class=&amp;quot;locality&amp;quot;&amp;gt;Fitzrovia&amp;lt;/span&amp;gt;&lt;br /&gt;
           &amp;lt;span class=&amp;quot;region&amp;quot;&amp;gt;London&amp;lt;/span&amp;gt;&lt;br /&gt;
           &amp;lt;span class=&amp;quot;postal-code&amp;quot;&amp;gt;W1T 1QS&amp;lt;/span&amp;gt;&lt;br /&gt;
        &amp;lt;/div&amp;gt;&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
   &amp;lt;/div&amp;gt;&lt;br /&gt;
   &amp;lt;p class=&amp;quot;description&amp;quot;&amp;gt;Wonderful pub, cheap beer, open fire to warm mince pies at Christmas.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/source&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== notes and issues ====&lt;br /&gt;
&lt;br /&gt;
Note: The &amp;lt;code&amp;gt;id&amp;lt;/code&amp;gt; attribute value in the example &amp;quot;bricklayers-card&amp;quot; was chosen for demonstration purposes. The text of the value has no semantic per the include-pattern other than to connect the source of the include to the destination. Authors {{should}} use good [[POSH]] techniques to choose &amp;lt;code&amp;gt;id&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;class&amp;lt;/code&amp;gt; names.&lt;br /&gt;
&lt;br /&gt;
Authors {{must}} supply content text for the hyperlink itself. This can require repeating a small piece of information (such as a person's name in an hcard), or including generic text as appropriate to the context of the page. &lt;br /&gt;
&lt;br /&gt;
===== accessibility =====&lt;br /&gt;
&lt;br /&gt;
* Testing indicates that the only way to guarantee accessibility of hyperlinks to users of assistive technology (such as screen readers) is to include inner-text. [http://yuiblog.com/blog/2008/01/23/empty-links/ See: Empty Links and Screen Readers]&lt;br /&gt;
* You {{must}} include inner-text in the hyperlink element.&lt;br /&gt;
* You MAY enhance the rendered user experience (depending on the context of your page) by hiding the include element using CSS &amp;lt;code&amp;gt;display: none&amp;lt;/code&amp;gt;&lt;br /&gt;
* Where you wish to hide the content of the include element, you {{should not}} hide the include element using a CSS negative margin offset as the hidden link will remain in the tab order of the document. Use &amp;lt;code&amp;gt;display: none&amp;lt;/code&amp;gt; instead.&lt;br /&gt;
&lt;br /&gt;
Where a publishing constraint prevents putting content within the include-pattern, you {{must}} use the &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt; element pattern instead of a hyperlink.&lt;br /&gt;
&lt;br /&gt;
=== Object ===&lt;br /&gt;
&lt;br /&gt;
The Object Include Pattern is semantically superior to the Hyperlink Include; it is being used to embed content into the page. The &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt; element based include was the original developed include pattern. However, there are some browser compatibility issues that can affect some implementation scenarios and thus the above Hyperlink Include Pattern is preferred.&lt;br /&gt;
&lt;br /&gt;
==== Object example ====&lt;br /&gt;
&lt;br /&gt;
The [[hcard|hCard]] from the beginning of a resumé describes the person who's resumé it is:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;fn n&amp;quot; id=&amp;quot;james-hcard-name&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;span class=&amp;quot;given-name&amp;quot;&amp;gt;James&amp;lt;/span&amp;gt; &amp;lt;span class=&amp;quot;family-name&amp;quot;&amp;gt;Levine&amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Elsewhere on the page, a second hCard, with employer information, re-uses the &amp;quot;fn n&amp;quot; content from the first hCard:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;object class=&amp;quot;include&amp;quot; data=&amp;quot;#james-hcard-name&amp;quot;&amp;gt;&amp;lt;/object&amp;gt;&lt;br /&gt;
 &amp;lt;span class=&amp;quot;org&amp;quot;&amp;gt;SimplyHired&amp;lt;/span&amp;gt;&lt;br /&gt;
 &amp;lt;span class=&amp;quot;title&amp;quot;&amp;gt;Microformat Brainstormer&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt; &lt;br /&gt;
&lt;br /&gt;
A microformat parser {{must}} treat the second hCard as follows, with the &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt; include element completely replaced by the sub-tree that it referenced:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;fn n&amp;quot; id=&amp;quot;james-hcard-name&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;span class=&amp;quot;given-name&amp;quot;&amp;gt;James&amp;lt;/span&amp;gt; &amp;lt;span class=&amp;quot;family-name&amp;quot;&amp;gt;Levine&amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;org&amp;quot;&amp;gt;SimplyHired&amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;title&amp;quot;&amp;gt;Microformat Brainstormer&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This method of hCard property indirection via an object element can apply to any/all properties in class-based microformats.&lt;br /&gt;
&lt;br /&gt;
=== notes and issues===&lt;br /&gt;
&lt;br /&gt;
* Unlike the hyperlink pattern, the &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt; is not believed to cause problems in assistive technology when fallback text is absent. ('''research needed''')&lt;br /&gt;
* Apple's Safari 1.x browser has some rendering issues with this use of &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt;: Publishers {{should}} style a width and height of &amp;quot;0&amp;quot; for the include elements to resolve this ('''clarification of issue needed''').&lt;br /&gt;
* Bugs have been reported in some web browsers (Internet Explorer, Safari, Firefox) that &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt; elements referencing fragments of the same document erroneously cause the browser to make additional HTTP requests ('''version(s) affected needed'''). For scenarios where HTTP requests are a performance issue, publishers {{should}} use the hyperlink pattern instead.&lt;br /&gt;
* Versions of Microsoft Internet Explorer with ActiveX controls disabled will throw a warning prompt upon finding an &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt; element ('''version(s) affected needed''').&lt;br /&gt;
&lt;br /&gt;
== acknowledgements ==&lt;br /&gt;
&lt;br /&gt;
Thanks to discussions and brainstorms with a bunch of folks: [http://theryanking.com/ Ryan King], James Levine, the whole crowd at the [http://mashupcamp.com/index.cgi?HAtomFinalization Microformats specifications working session] at MashupCamp, [http://suda.co.uk/ Brian Suda], [http://randomchaos.com/ Scott Reynen], [http://allinthehead.com/ Drew McLellan]. Thanks to [http://www.isolani.co.uk/ Mike Davies] for accessibility research.&lt;br /&gt;
&lt;br /&gt;
== specifications using ==&lt;br /&gt;
* [[hresume|hResume]]&lt;br /&gt;
* [[hreview|hReview]]&lt;br /&gt;
&lt;br /&gt;
=== considering ===&lt;br /&gt;
All class-based microformats {{should}} consider using and explicitly normatively stating support for the include pattern.&lt;br /&gt;
* [[hatom|hAtom]]&lt;br /&gt;
* [[hcalendar|hCalendar]]&lt;br /&gt;
* [[hcard|hCard]]&lt;br /&gt;
&lt;br /&gt;
== implementations ==&lt;br /&gt;
* X2V implements the [[include-pattern]] when parsing [[hcard|hCards]] and [[hcalendar|hCalendars]] for both object.include and a.include.&lt;br /&gt;
&lt;br /&gt;
== references ==&lt;br /&gt;
&lt;br /&gt;
=== normative ===&lt;br /&gt;
* HTML 4.01&lt;br /&gt;
&lt;br /&gt;
=== informative ===&lt;br /&gt;
* [[hcard|hCard]]&lt;br /&gt;
* [[hresume|hResume]]&lt;br /&gt;
* XHTML 1.0&lt;br /&gt;
&lt;br /&gt;
== related pages==&lt;br /&gt;
{{include-pattern-related-pages}}&lt;br /&gt;
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].&lt;/div&gt;</summary>
		<author><name>Alik</name></author>
	</entry>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=hresume&amp;diff=43047</id>
		<title>hresume</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=hresume&amp;diff=43047"/>
		<updated>2010-09-05T20:52:52Z</updated>

		<summary type="html">&lt;p&gt;Alik: Unicode&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;entry-title&amp;gt;hResume&amp;lt;/entry-title&amp;gt;&lt;br /&gt;
{{DraftSpecification}}&lt;br /&gt;
__TOC__&lt;br /&gt;
hResume is a microformat for publishing resumes and CVs. hResume is one of several open microformat standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.&lt;br /&gt;
&lt;br /&gt;
Want to get started with writing an hResume? Use the [http://hresume.weblogswork.com/hresumecreator/ hResume Creator] to create your hResume and publish it, or follow the hResume authoring tips to add hResume markup to your web page or blog. &lt;br /&gt;
&lt;br /&gt;
==Microformats Draft Specification==&lt;br /&gt;
&lt;br /&gt;
; Editor/Author: [http://theryanking.com Ryan King]&lt;br /&gt;
; Acknowledgments: See [http://microformats.org/wiki/hresume#Acknowledgements  acknowledgments].&lt;br /&gt;
&lt;br /&gt;
Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.&lt;br /&gt;
&lt;br /&gt;
{{rfc-2119-intro}}&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
Draft, version 0.1.&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
=== Semantic XHTML Design Principles ===&lt;br /&gt;
{{SemanticXHTMLDesignPrinciples}}&lt;br /&gt;
&lt;br /&gt;
== Format ==&lt;br /&gt;
=== In General ===&lt;br /&gt;
The hResume format is based on a set of fields common to numerous resumes published today on the web.  Where possible field names have been chosen and reused from preexisting microformats.&lt;br /&gt;
&lt;br /&gt;
=== Schema ===&lt;br /&gt;
The hResume schema consists of the following:&lt;br /&gt;
&lt;br /&gt;
* hResume&lt;br /&gt;
** summary. optional. text.&lt;br /&gt;
** contact info. required. {{must}} use [[hcard|hCard]]; {{should}} use &amp;lt;code class=&amp;quot;element&amp;quot;&amp;gt;&amp;amp;lt;address&amp;amp;gt;&amp;lt;/code&amp;gt; + [[hcard|hCard]].&lt;br /&gt;
** experience. optional. One or more [[hcalendar]] events with the class name '&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;experience&amp;lt;/code&amp;gt;', with an embedded [[hcard|hCard]] indicating the job title, name of company, address of company etc.&lt;br /&gt;
** education. optional One or more [[hcalendar]] events with the class name '&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;education&amp;lt;/code&amp;gt;', with an embedded [[hcard|hCard]] indicating the name of school, address of school etc.&lt;br /&gt;
** skills. optional. phrases or keywords using the [[rel-tag]] microformat with the class name '&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;skill&amp;lt;/code&amp;gt;'.&lt;br /&gt;
** affiliations. optional. the class name &amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;affiliation&amp;lt;/code&amp;gt; along with an [[hcard]] of the organization&lt;br /&gt;
** publications. optional. One or more citations. Use cite tag.&lt;br /&gt;
&lt;br /&gt;
=== Field details ===&lt;br /&gt;
The fields of the hResume schema represent the following:&lt;br /&gt;
&lt;br /&gt;
* '''&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;hresume&amp;lt;/code&amp;gt;''':: root class name&lt;br /&gt;
* '''&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;summary&amp;lt;/code&amp;gt;''':: The class name &amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;summary&amp;lt;/code&amp;gt; is used to mark up an overview of qualifications and objectives.&lt;br /&gt;
* '''contact''':: Current contact info in an [[hCard]]; {{should}} use &amp;lt;code class=&amp;quot;element&amp;quot;&amp;gt;&amp;amp;lt;address&amp;amp;gt;&amp;lt;/code&amp;gt; with [[hCard]] when possible.&lt;br /&gt;
* '''&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;education&amp;lt;/code&amp;gt;''':: the class name '&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;education&amp;lt;/code&amp;gt;' is applied to an [[hcalendar]] event.&lt;br /&gt;
* '''&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;experience&amp;lt;/code&amp;gt;''':: the class name '&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;experience&amp;lt;/code&amp;gt;' is applied to an [[hcalendar]] event. Job titles/positions should use an [[hCard]].&lt;br /&gt;
* '''&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;skill&amp;lt;/code&amp;gt;''':: An hResume may be tagged using the [[rel-tag]] microformat and the '&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;skill&amp;lt;/code&amp;gt;' class name.&lt;br /&gt;
* '''&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;affiliation&amp;lt;/code&amp;gt;''':: The class name &amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;affiliation&amp;lt;/code&amp;gt; is used along with an [[hcard]] of the organization&lt;br /&gt;
* '''publications''':: just use &amp;lt;code class=&amp;quot;element&amp;quot;&amp;gt;&amp;amp;lt;cite&amp;amp;gt;&amp;lt;/code&amp;gt;.  When there is a [[citation]] microformat, then that can be used in combination with the cite element to further markup the components of the citation.&lt;br /&gt;
&lt;br /&gt;
=== XMDP Profile ===&lt;br /&gt;
* [[hresume-profile]] (@TODO)&lt;br /&gt;
&lt;br /&gt;
=== Notes ===&lt;br /&gt;
This section is informative.&lt;br /&gt;
&lt;br /&gt;
*...&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
=== Summary ===&lt;br /&gt;
An example summary:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;p class=&amp;quot;summary&amp;quot;&amp;gt;&lt;br /&gt;
  I have 10 years experience with all Web 2.0 technologies– I've been working with Ajax since 1996, &lt;br /&gt;
  designing with pastels while others will still using tiled background images and frames...&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Contact ===&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;address class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;Pedro Sanchez&amp;lt;/span&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;123 Fake St.&amp;lt;/span&amp;gt;&lt;br /&gt;
    &amp;lt;span class=&amp;quot;locality&amp;quot;&amp;gt;Preston&amp;lt;/span&amp;gt;, &amp;lt;span class=&amp;quot;region&amp;quot;&amp;gt;Idaho&amp;lt;/span&amp;gt; &amp;lt;span class=&amp;quot;postal-code&amp;quot;&amp;gt;83263&amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;span&amp;gt;Email: &amp;lt;a class=&amp;quot;email&amp;quot; href=&amp;quot;mailto:joe@example.com&amp;quot;&amp;gt;pedro@vote-for-pedro.com&amp;lt;/a&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;span&amp;gt;Homepage: &amp;lt;a class=&amp;quot;url&amp;quot; href=&amp;quot;http://vote-for-pedro.com/&amp;quot;&amp;gt;vote-for-pedro.com&amp;lt;/a&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;span&amp;gt;Phone: &amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;+01.208.555.4567&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/address&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Education ===&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;ol class=&amp;quot;vcalendar&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;li class=&amp;quot;education vevent&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;a class=&amp;quot;url summary&amp;quot; href=&amp;quot;http://example.edu/&amp;quot;&amp;gt;Preston High School&amp;lt;/a&amp;gt;&lt;br /&gt;
    (&amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;2001-01-24&amp;quot;&amp;gt;2001&amp;lt;/abbr&amp;gt; - &amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;2005-05-25&amp;quot;&amp;gt;2005&amp;lt;/abbr&amp;gt;)&lt;br /&gt;
  &amp;lt;/li&amp;gt;&lt;br /&gt;
  ...&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Experience ===&lt;br /&gt;
==== Basic ====&lt;br /&gt;
A basic experience event:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;ol class=&amp;quot;vcalendar&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;li class=&amp;quot;experience vevent&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;span class=&amp;quot;summary&amp;quot;&amp;gt;President&amp;lt;/span&amp;gt;,&lt;br /&gt;
    &amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt;Preston High School&amp;lt;/span&amp;gt;,&lt;br /&gt;
    &amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;2004-09-01&amp;quot;&amp;gt;May 2004&amp;lt;/abbr&amp;gt; - &amp;lt;abbr title=&amp;quot;2005-05-25&amp;quot;&amp;gt;present&amp;lt;/abbr&amp;gt;&lt;br /&gt;
  &amp;lt;/li&amp;gt;&lt;br /&gt;
  ...&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Job Titles ====&lt;br /&gt;
To express one or more job titles/positions in the same experience event you should use one or more [[hcard|hCard]]s. hCard requires the &amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;fn&amp;lt;/code&amp;gt; (&amp;quot;formatted name&amp;quot;) field, but it isn't customary to repeat your name for every job title you mark up in [[hResume|hresume]]. So, you may use an &amp;lt;code class=&amp;quot;element&amp;quot;&amp;gt;&amp;amp;lt;object&amp;amp;gt;&amp;lt;/code&amp;gt; and the class name '&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;include&amp;lt;/code&amp;gt;' with a reference to the &amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;fn&amp;lt;/code&amp;gt; somewhere else on the page. &lt;br /&gt;
&lt;br /&gt;
Currently, the recommended way to reference includes within microformats is to use a hyperlink with class=&amp;quot;include&amp;quot;. See [[include-pattern|include-pattern]] for details.&lt;br /&gt;
&lt;br /&gt;
For example, this hCard refers to another hCard:&lt;br /&gt;
&lt;br /&gt;
Using &amp;lt;code&amp;gt;&amp;amp;lt;a&amp;amp;gt;&amp;lt;/code&amp;gt;:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;a href=&amp;quot;#pedro-name&amp;quot; class=&amp;quot;include&amp;quot; title=&amp;quot;Pedro Sanchez&amp;quot;&amp;gt;&amp;lt;/a&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;org&amp;quot;&amp;gt;Preston High School&amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;title&amp;quot;&amp;gt;Class President&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Using &amp;lt;code&amp;gt;&amp;amp;lt;object&amp;amp;gt;&amp;lt;/code&amp;gt;:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;object  data=&amp;quot;#pedro-name&amp;quot; class=&amp;quot;include&amp;quot;&amp;gt;&amp;lt;/object&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;org&amp;quot;&amp;gt;Preston High School&amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;title&amp;quot;&amp;gt;Class President&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Where &amp;quot;&amp;lt;code class=&amp;quot;attr-value&amp;quot;&amp;gt;pedro-name&amp;lt;/code&amp;gt;&amp;quot; is the id attribute value of the &amp;quot;&amp;lt;code class=&amp;quot;mf-prop&amp;quot;&amp;gt;fn n&amp;lt;/code&amp;gt;&amp;quot; element of the contact hCard at the top of the page, e.g. (shown here as a verbose hCard for purposes of illustration that the reference may be to a subtree, not just a text node):&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;address class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;fn n&amp;quot; id=&amp;quot;pedro-name&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;span class=&amp;quot;given-name&amp;quot;&amp;gt;Pedro&amp;lt;/span&amp;gt;&lt;br /&gt;
    &amp;lt;span class=&amp;quot;family-name&amp;quot;&amp;gt;Sanchez&amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/address&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This method of hCard property indirection via an object element [[include-pattern|has been generalized]] to apply to any/all string/text properties in hCard.&lt;br /&gt;
&lt;br /&gt;
Note: the object data attribute {{must}} be a local ID reference. External references (which would require a consuming application to load an external resource) are not supported by this method.&lt;br /&gt;
&lt;br /&gt;
=== Skills ===&lt;br /&gt;
Some sample skills tags:&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
I have skills in &amp;lt;a class=&amp;quot;skill&amp;quot; rel=&amp;quot;tag&amp;quot; href=&amp;quot;http://en.wikipedia.org/wiki/Bow_%28weapon%29&amp;quot;&amp;gt;bow hunting&amp;lt;/a&amp;gt; &lt;br /&gt;
and &amp;lt;a class=&amp;quot;skill&amp;quot; rel=&amp;quot;tag&amp;quot; href=&amp;quot;http://en.wikipedia.org/wiki/Nunchucks&amp;quot;&amp;gt;nunchucks&amp;lt;/a&amp;gt;.&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Affiliations ===&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;affiliation vcard&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;fn org&amp;quot;&amp;gt;National Honor Society&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Publications ===&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;cite&amp;gt;Breeding Ligers for Fun and Magic&amp;lt;/cite&amp;gt;, Idaho Press, 2004.&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Examples in the wild ==&lt;br /&gt;
See [[hresume-examples-in-wild]]&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 hResumes. If you have an hResume 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 like [[hresume-implementations]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* [http://www.cvmatch4jobs.com/ cvmatch4jobs] has implemented hResume import for publicly published CV's. A Career site for 3 UK building and proprety magazines from publishers UBM. 19 Jan 2010.&lt;br /&gt;
&lt;br /&gt;
* [http://careercv.mad.co.uk/ CareerCV] has implemented hResume import for publicly published CV's. A Career site for major UK design magazines from publishers Centaur Communications. 19 Jan 2010.&lt;br /&gt;
&lt;br /&gt;
* [http://lab.madgex.com/hresume/ Madgex] has implemented hResume to Microsoft Word and PDF conversion API. 13 Dec 2009. &lt;br /&gt;
&lt;br /&gt;
* [http://careers.stackoverflow.com/ Stack Overflow] generates hResume for its public CV hosting service for programmers. [http://careers.stackoverflow.com/klmr Stack Overflow CV example] Dec 2009.&lt;br /&gt;
&lt;br /&gt;
* [http://jobs.guardian.co.uk/profile/ Guardian Jobs] has implemented hResume import for publicly published CV's. 4 Sep 2009.&lt;br /&gt;
&lt;br /&gt;
* [http://www.yiid.com/ YIID - Your Internet Identity] supports importing of hResumes (e.g. here is the result of an import: http://pfefferle.yiid.com/cv [requires login] via @pfefferle)&lt;br /&gt;
&lt;br /&gt;
* [[Resume.app]]&lt;br /&gt;
&lt;br /&gt;
* [http://www.xing.com/ Xing] generates hResume for all Public Profiles. [http://www.xing.com/profile/Matthias_Pfefferle Xing Public Profile Example].&lt;br /&gt;
&lt;br /&gt;
* [http://linkedin.com LinkedIn] generates hResume for all Public Profiles. [http://www.linkedin.com/in/steveganz LinkedIn Public Profile Example].&lt;br /&gt;
&lt;br /&gt;
* [http://www.antix.co.uk Anthony Johnston] has implemented hResume (Creation and Import) in the [http://cv.antix.co.uk Antix CV Builder], an example resume using this site can be found [http://cv.antix.co.uk/ant here]&lt;br /&gt;
** The example resume is ''invalid''; job titles are marked with an hCard that is missing a &amp;quot;fn&amp;quot; (either directly or via object). --[[User:Gazza|Gazza]] 04:23, 1 May 2007 (PDT)&lt;br /&gt;
*** This is fixed now --[[User:Antix|Ant]] 00:38, 8 Dec 2007 (GMT)&lt;br /&gt;
&lt;br /&gt;
* The [http://spurinc.com Spur] team has created an hResume WordPress plugin located at [http://hresume.weblogswork.com/?page_id=3 hResume Plugin].  See an example of the hResume markup [http://hresume.weblogswork.com/?page_id=6 here].  Neat feature of the hResume plugin is that it automatically creates a new page for the resume - no cutting and pasting...&lt;br /&gt;
&lt;br /&gt;
* Spur also created a standalone hResume Creator located at [http://hresume.weblogswork.com/hresumecreator/ hResume Creator].  The creator will generate hResume markup ready to cut and paste into your webpage.&lt;br /&gt;
&lt;br /&gt;
== Copyright ==&lt;br /&gt;
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.&lt;br /&gt;
* [[RyanKing]]: I release all of my contributions to the public domain.&lt;br /&gt;
&lt;br /&gt;
Per the above, and the public domain release on the author, [[User:RyanKing|RyanKing]]'s, user page this specification is released into the public domain.&lt;br /&gt;
&lt;br /&gt;
{{MicroFormatPublicDomainContributionStatement}}&lt;br /&gt;
&lt;br /&gt;
== Patents ==&lt;br /&gt;
{{MicroFormatPatentStatement}}&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
=== Normative References ===&lt;br /&gt;
* [[hcard|hCard]]&lt;br /&gt;
* [[hcalendar|hCalendar]]&lt;br /&gt;
* [[include-pattern|include pattern]]&lt;br /&gt;
* [http://www.w3.org/TR/REC-html40/ HTML 4]&lt;br /&gt;
* [http://www.w3.org/TR/xhtml1/ XHTML]&lt;br /&gt;
* [http://gmpg.org/xmdp/ XMDP]&lt;br /&gt;
* [[rel-tag| Rel-Tag]]&lt;br /&gt;
* [[rfc-2119]]&lt;br /&gt;
* @TODO&lt;br /&gt;
&lt;br /&gt;
=== Informative References ===&lt;br /&gt;
* @TODO&lt;br /&gt;
&lt;br /&gt;
== Acknowledgements ==&lt;br /&gt;
=== Concept ===&lt;br /&gt;
* [http://theryanking.com/ Ryan King] ([http://technorati.com Technorati])&lt;br /&gt;
* [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati])&lt;br /&gt;
* James Levine ([http://simplyhired.com Simply Hired])&lt;br /&gt;
* [http://epeus.blogspot.com/ Kevin Marks] ([http://technorati.com Technorati])&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
{{hresume-related-pages}}&lt;br /&gt;
&lt;br /&gt;
== Further Reading ==&lt;br /&gt;
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].&lt;br /&gt;
* [http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-6-hresume/ Getting Semantic With Microformats, Part 6: hResume] by Emily Lewis&lt;br /&gt;
&lt;br /&gt;
[[Category:Draft Specifications]]&lt;br /&gt;
[[Category:hResume]]&lt;/div&gt;</summary>
		<author><name>Alik</name></author>
	</entry>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=hreview&amp;diff=43046</id>
		<title>hreview</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=hreview&amp;diff=43046"/>
		<updated>2010-09-05T20:52:09Z</updated>

		<summary type="html">&lt;p&gt;Alik: Unicode&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;entry-title&amp;gt;hReview 0.3&amp;lt;/entry-title&amp;gt;&lt;br /&gt;
{{DraftSpecification}}&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 HTML, XHTML, 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;
&amp;lt;div class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
;&amp;lt;span class=&amp;quot;role&amp;quot;&amp;gt;Editor&amp;lt;/span&amp;gt;&lt;br /&gt;
:&amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;[[User:Tantek|Tantek Çelik]]&amp;lt;/span&amp;gt; (&amp;lt;span class=&amp;quot;url&amp;quot;&amp;gt;http://tantek.com/&amp;lt;/span&amp;gt;, and before at [http://technorati.com Technorati, Inc.])&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
; Authors&lt;br /&gt;
: [[User:Tantek|Tantek Çelik]] (affiliations above)&lt;br /&gt;
: &amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;[http://360.yahoo.com/alidiabali Ali Diab]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ([http://yahoo.com Yahoo! Inc.])&lt;br /&gt;
: &amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;[http://ianmcall.blogspot.com/ Ian McAllister]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ([http://amazon.com/ Amazon.com])&lt;br /&gt;
: &amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;[http://journals.aol.com/panzerjohn/abstractioneer John Panzer]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ([http://www.aol.com America Online, Inc.])&lt;br /&gt;
: &amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;[http://ifindkarma.com/blog Adam Rifkin]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ([http://labs.commerce.net/ CommerceNet Labs])&lt;br /&gt;
: &amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;[http://sippey.typepad.com/ Michael Sippey]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ([http://sixapart.com Six Apart, Ltd])&lt;br /&gt;
&lt;br /&gt;
[[hreview#Copyright|copyright]] and [[hreview#Patents|patents]] statements apply.&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
hReview 0.3 is a microformats.org draft specification. Public discussion on hReview takes place on [[hreview-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-discuss/ microformats-discuss mailing list].&lt;br /&gt;
&lt;br /&gt;
=== Available languages ===&lt;br /&gt;
The English version of this specification is the only normative version. For translations of this document see the [[#translations]] section.&lt;br /&gt;
&lt;br /&gt;
=== Errata and Updates ===&lt;br /&gt;
Known errors and issues in this specification are corrected in [[hreview-issues-resolved|resolved]] and [[hreview-issues-closed|closed]] issues. Please check there before reporting [[hreview-issues|issues]].&lt;br /&gt;
&lt;br /&gt;
The hReview 0.4 update is currently under development and incorporates known errata corrections as well as the [[value-class-pattern]].&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;
{{rfc-2119-intro}}&lt;br /&gt;
&lt;br /&gt;
=== Scope ===&lt;br /&gt;
Reviews consistently share several common aspects.  Where possible hReview has been based on this minimal common subset.&lt;br /&gt;
&lt;br /&gt;
==== Out of scope ====&lt;br /&gt;
Portions of reviews that are specific to particular kinds of items 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;
== Format ==&lt;br /&gt;
=== In General ===&lt;br /&gt;
The hReview format is based on a set of properties common to numerous review sites and formats in use today on the web.  Where possible property 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 HTML 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;
=== Property details ===&lt;br /&gt;
Details of the hReview properties:&lt;br /&gt;
&lt;br /&gt;
'''version''':: This optional property permits hReview publishers to specify a particular version of hReview that their content uses.  By omitting this property, 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 property 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 property for this specification is &amp;quot;0.3&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''summary''':: This optional property serves as a short synopsis, title, or name of the review. Re-used from [[hCalendar]] which re-uses it from iCalendar (section 4.8.1.12 of RFC 2445).&lt;br /&gt;
&lt;br /&gt;
'''type''':: This optional property provides the type of the item being reviewed, one of the following: &amp;lt;code&amp;gt;product, business, place, person, event, website, url&amp;lt;/code&amp;gt;.  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;, &amp;quot;place&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''':: This required property {{must}} have at a minimum the name (using the subproperty &amp;quot;fn&amp;quot; - the formatted text corresponding to the name, except for an event item which {{must}} have the &amp;quot;summary&amp;quot; subproperty inside the respective hCalendar &amp;quot;vevent&amp;quot;) 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;.  Non-URL unique item IDs (e.g. ISBNs, UPCs) {{may}} be represented as a URN (&amp;quot;url&amp;quot;) for the item.  Encapsulated microformats (e.g. [[hcard|hCard]] and [[hcalendar|hCalendar]] events for now) may be set on the item itself (e.g. class=&amp;quot;item vcard&amp;quot;).  However, when using item info subproperties (&amp;quot;fn&amp;quot;, &amp;quot;url&amp;quot;, &amp;quot;photo&amp;quot;), they {{must}} be nested &amp;lt;em&amp;gt;inside&amp;lt;/em&amp;gt; the item element.&lt;br /&gt;
&lt;br /&gt;
'''reviewer''':: The optional property 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 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 property when present {{must}} provide an [[ISO-8601|ISO8601]] absolute date time of when the review was written or otherwise authored.  This property {{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 to indicate a different range (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 property serves as a more detailed synopsis of the review (i.e. full text representing the written opinion of the reviewer) than that provided by summary.  The property {{may}} include valid HTML 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 property.&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 property 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 property, 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.&lt;br /&gt;
&lt;br /&gt;
'''license''':: an hReview indicates the license for its contents using the '''[[rel-license]]''' microformat.&lt;br /&gt;
&lt;br /&gt;
The following property names have been reused from the [[hcard|hCard]] and [[hcalendar|hCalendar]] microformats: &amp;lt;code&amp;gt;version, summary, fn, url, photo, description&amp;lt;/code&amp;gt;.  In addition, items and reviewers described by hCards {{may}} contain any hCard property.  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;
=== 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;
* 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.0&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 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 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;
* 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;source lang=html4strict&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;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Adding hReview to this review is quite simple:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&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;/source&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;source lang=html4strict&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&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;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With an accompanying CSS style sheet like:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
a.url { display:block }&lt;br /&gt;
ul { margin:1em 0; padding:0 }&lt;br /&gt;
ul li { display:inline }&lt;br /&gt;
&amp;lt;/source&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;source lang=html4strict&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;/source&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;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;hreview&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;item&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;a class=&amp;quot;url fn&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;
  The Postal Service: Give Up&amp;lt;/a&amp;gt;&amp;lt;/span&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;/source&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;source lang=html4strict&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;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With hReview:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&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;/source&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'''. The number of hReview examples in the wild has expanded far beyond the capacity of being kept inline in this specification. They have been moved to a [[hreview-examples-in-wild|separate page]].&lt;br /&gt;
&lt;br /&gt;
See [[hreview-examples-in-wild|hReview Examples in the wild]].&lt;br /&gt;
&lt;br /&gt;
== Implementations ==&lt;br /&gt;
This section is '''informative'''. The number of hReview implementations has also expanded beyond the capacity of keeping them inline. They have been moved to a [[hreview-implementations|separate page]].&lt;br /&gt;
&lt;br /&gt;
See [[hreview-implementations|hReview Implementations]].&lt;br /&gt;
&lt;br /&gt;
== Design Principles ==&lt;br /&gt;
This section is '''informative'''.  hReview was designed using design [[principles]] similar to those that went into [[hCard]] and thus this overview is included for informational purposes.&lt;br /&gt;
&lt;br /&gt;
{{semantic-xhtml-design-principles}}&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: [[User:Richardault|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;
== 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;
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.&lt;br /&gt;
** When all authors/editors have done so, we can remove the MicroFormatCopyrightStatement template reference and replace it with the MicroFormatPublicDomainContributionStatement.&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 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;
== Further Reading ==&lt;br /&gt;
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
{{hreview-related-pages}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Draft Specifications]]&lt;br /&gt;
[[Category:hReview]]&lt;br /&gt;
&lt;br /&gt;
== Translations ==&lt;br /&gt;
Read the hReview draft specification in additional &amp;lt;span id=&amp;quot;languages&amp;quot;&amp;gt;languages&amp;lt;/span&amp;gt;:&lt;br /&gt;
* [[hreview-fr|français]]&lt;br /&gt;
* [[hreview-ja|日本語]]&lt;/div&gt;</summary>
		<author><name>Alik</name></author>
	</entry>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=hcalendar&amp;diff=43045</id>
		<title>hcalendar</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=hcalendar&amp;diff=43045"/>
		<updated>2010-09-05T20:51:27Z</updated>

		<summary type="html">&lt;p&gt;Alik: Unicode&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;entry-title&amp;gt;hCalendar 1.0&amp;lt;/entry-title&amp;gt;&lt;br /&gt;
&amp;lt;dfn style=&amp;quot;font-style:normal;font-weight:bold&amp;quot;&amp;gt;hCalendar&amp;lt;/dfn&amp;gt; is a simple, open, distributed calendaring and events format, using a 1:1 representation of standard iCalendar ([[rfc-2445|RFC2445]]) VEVENT properties and values in [[semantic-xhtml|semantic HTML or XHTML]]. hCalendar is one of several open [[microformats|microformat]] standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.&lt;br /&gt;
&lt;br /&gt;
'''Want to get started with writing an [[hcalendar|hCalendar]] event?''' Use the [http://microformats.org/code/hcalendar/creator hCalendar creator] to write up an event and publish it, or follow the [[hcalendar-authoring|hCalendar authoring tips]] to add hCalendar markup to your page of upcoming events or events you mention in blog posts, wikis, etc.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
; &amp;lt;span class=&amp;quot;role&amp;quot;&amp;gt;Editor&amp;lt;/span&amp;gt; &lt;br /&gt;
: &amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;[[User:Tantek|Tantek Çelik]]&amp;lt;/span&amp;gt; (&amp;lt;span class=&amp;quot;url&amp;quot;&amp;gt;http://tantek.com/&amp;lt;/span&amp;gt;, and before at [http://technorati.com Technorati, Inc.], and at [http://microsoft.com/ Microsoft Corporation])&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
; Authors: [http://tantek.com/ Tantek Çelik] (affiliations above)&lt;br /&gt;
: &amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;[[User:Brian|Brian Suda]]&amp;lt;/span&amp;gt; (&amp;lt;span class=&amp;quot;url&amp;quot;&amp;gt;http://suda.co.uk/&amp;lt;/span&amp;gt;)&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
; Acknowledgments: See [[hcalendar#Inspiration_and_Acknowledgments|acknowledgments]].&lt;br /&gt;
&lt;br /&gt;
[[hcalendar#Copyright|copyright]] and [[hcalendar#Patents|patents]] statements apply.&lt;br /&gt;
&lt;br /&gt;
== Example ==&lt;br /&gt;
Here is a simple event:&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;p&amp;gt;The microformats.org site was launched on 2005-06-20 at the Supernova Conference in San Francisco, CA, USA.&amp;lt;/p&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
marked up with hCalendar&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;span class=&amp;quot;summary&amp;quot;&amp;gt;The microformats.org site was launched&amp;lt;/span&amp;gt;&lt;br /&gt;
 on &amp;lt;span class=&amp;quot;dtstart&amp;quot;&amp;gt;2005-06-20&amp;lt;/span&amp;gt; &lt;br /&gt;
 at the Supernova Conference &lt;br /&gt;
 in &amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt;San Francisco, CA, USA&amp;lt;/span&amp;gt;.&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
hCalendar 1.0 is a microformats.org specification. Public discussion on hCalendar takes place on [[hcalendar-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-discuss/ microformats-discuss mailing list].&lt;br /&gt;
&lt;br /&gt;
=== Available languages ===&lt;br /&gt;
The English version of this specification is the only normative version. For translations of this document see the [[#translations]] section.&lt;br /&gt;
&lt;br /&gt;
=== Errata and Updates ===&lt;br /&gt;
Known errors and issues in this specification are corrected in [[hcalendar-issues-resolved|resolved]] and [[hcalendar-issues-closed|closed]] issues. Please check there before reporting [[hcalendar-issues|issues]].&lt;br /&gt;
&lt;br /&gt;
Note in particular the [[dtend-issue]] which affects end dates. Implementations {{should}} implement the issue resolution ASAP and [http://ufxtract.com/testsuite/hcalendar/hcalendar1.htm test it].&lt;br /&gt;
&lt;br /&gt;
The hCalendar 1.0.1 update is currently under development and incorporates known errata corrections as well as the [[value-class-pattern]].&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
The iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]), has been broadly interoperably implemented (e.g. Apple's &amp;quot;iCal&amp;quot; application built into MacOSX).&lt;br /&gt;
&lt;br /&gt;
In addition, bloggers often discuss events on their blogs -- upcoming events, writeups of past events, etc.  With just a tad bit of structure, bloggers can discuss events in their blog(s) in such a way that spiders and other aggregators can retrieve such events, automatically convert them to iCalendar, and use them in any iCalendar application or service.&lt;br /&gt;
&lt;br /&gt;
This specification introduces the '''hCalendar''' format, which is a 1:1 representation of the aforementioned iCalendar standard, in semantic HTML.  Bloggers can both embed hCalendar events directly in their web pages, and style them with CSS to make them appear as desired.  In addition, hCalendar enables applications to retrieve information about such events directly from web pages without having to reference a separate file.&lt;br /&gt;
&lt;br /&gt;
{{rfc-2119-intro}}&lt;br /&gt;
&lt;br /&gt;
== Semantic XHTML Design Principles ==&lt;br /&gt;
&lt;br /&gt;
{{semantic-xhtml-design-principles}}&lt;br /&gt;
&lt;br /&gt;
For practical implementations, it should be noted that Internet Explorer's support for styling &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; elements is poor, and may require wrapper elements.&lt;br /&gt;
&lt;br /&gt;
== Format ==&lt;br /&gt;
=== In General ===&lt;br /&gt;
The iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]) forms the basis of hCalendar.&lt;br /&gt;
&lt;br /&gt;
Note: the editor and authors of this specification are tracking the [http://lists.osafoundation.org/pipermail/ietf-calsify/ &amp;quot;iCal-Basic&amp;quot; effort] and intend to base the core hCalendar profile on iCal-Basic. See references for a link to the current draft.&lt;br /&gt;
&lt;br /&gt;
The basic format of hCalendar is to use iCalendar object/property names in lower-case for class names, and to map the nesting of iCalendar objects directly into nested XHTML elements.&lt;br /&gt;
&lt;br /&gt;
=== Root Class Name ===&lt;br /&gt;
The root class name for hCalendar is &amp;quot;vcalendar&amp;quot;.  An element with a class name of &amp;quot;vcalendar&amp;quot; is itself called an ''hCalendar''. &lt;br /&gt;
&lt;br /&gt;
The root class name for events is &amp;quot;vevent&amp;quot;. An element with a class name of &amp;quot;vevent&amp;quot; is itself called an ''hCalendar event''.&lt;br /&gt;
&lt;br /&gt;
For authoring convenience, both &amp;quot;vevent&amp;quot; and &amp;quot;vcalendar&amp;quot; are treated as root class names for parsing purposes.  If a document contains elements with class name &amp;quot;vevent&amp;quot; but not &amp;quot;vcalendar&amp;quot;, the entire document has an implied &amp;quot;vcalendar&amp;quot; context.&lt;br /&gt;
&lt;br /&gt;
'''vevent''' should be considered required for each event listing.&lt;br /&gt;
&lt;br /&gt;
=== Properties and Sub-properties ===&lt;br /&gt;
The properties of an hCalendar are represented by elements inside the hCalendar.  Elements with class names of the listed properties represent the values of those properties.  Some properties have sub-properties, and those are represented by elements inside the elements for properties.&lt;br /&gt;
&lt;br /&gt;
=== Property List ===&lt;br /&gt;
hCalendar properties (sub-properties in parentheses like this)&lt;br /&gt;
&lt;br /&gt;
'''Required:'''&lt;br /&gt;
* '''dtstart''' ([[iso-8601|ISO date]])&lt;br /&gt;
* '''summary'''&lt;br /&gt;
Optional:&lt;br /&gt;
* location&lt;br /&gt;
* url&lt;br /&gt;
* dtend (ISO date), duration (ISO date duration)&lt;br /&gt;
* rdate, rrule&lt;br /&gt;
* category, description&lt;br /&gt;
* uid&lt;br /&gt;
* geo (latitude, longitude)&lt;br /&gt;
* attendee (partstat, role), contact, organizer&lt;br /&gt;
* attach&lt;br /&gt;
* status&lt;br /&gt;
* ... editor's note: this list is incomplete (an incomplete list is better than no list) and is being currently edited from RFC2445 to here.  The above list of properties are those that are often used in hCalendar on the web.&lt;br /&gt;
&lt;br /&gt;
=== Profile ===&lt;br /&gt;
The hCalendar XMDP profile is at http://microformats.org/profile/hcalendar&lt;br /&gt;
&lt;br /&gt;
Content that uses hCalendar {{should}} reference this profile, e.g.&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;head profile=&amp;quot;http://microformats.org/profile/hcalendar&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
or&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;link rel=&amp;quot;profile&amp;quot; href=&amp;quot;http://microformats.org/profile/hcalendar&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
or&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
This content uses &amp;lt;a rel=&amp;quot;profile&amp;quot; href=&amp;quot;http://microformats.org/profile/hcalendar&amp;quot;&amp;gt;hCalendar&amp;lt;/a&amp;gt;.&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
Content may combine the above methods as well.&lt;br /&gt;
&lt;br /&gt;
=== More Semantic Equivalents ===&lt;br /&gt;
For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:&lt;br /&gt;
* &amp;lt;code&amp;gt;URL&amp;lt;/code&amp;gt; in iCalendar becomes  &amp;lt;code&amp;gt;&amp;amp;lt;a class=&amp;quot;url&amp;quot; href=&amp;quot;...&amp;quot;&amp;amp;gt;...&amp;amp;lt;/a&amp;amp;gt;&amp;lt;/code&amp;gt; inside the element with &amp;lt;code&amp;gt;class=&amp;quot;vevent&amp;quot;&amp;lt;/code&amp;gt; in hCalendar.&lt;br /&gt;
* &amp;lt;code&amp;gt;ATTENDEE&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;CONTACT&amp;lt;/code&amp;gt;, and &amp;lt;code&amp;gt;ORGANIZER&amp;lt;/code&amp;gt; in iCalendar {{may}} be represented by an [[hcard|hCard]] in hCalendar .&lt;br /&gt;
* A named &amp;lt;code&amp;gt;LOCATION&amp;lt;/code&amp;gt; (potentially with an address and/or geo) in iCalendar {{may}} be represented by a nested [[hcard|hCard]] in hCalendar. Similarly, an address &amp;lt;code&amp;gt;LOCATION&amp;lt;/code&amp;gt; {{may}} be represented by an [[adr]], and a geo (latitude and longitude) &amp;lt;code&amp;gt;LOCATION&amp;lt;/code&amp;gt; may be represented by a [[geo]].&lt;br /&gt;
* &amp;lt;code&amp;gt;UID&amp;lt;/code&amp;gt; in iCalendar simply becomes another semantic applied to a specific URL for an hCalendar event.&lt;br /&gt;
* &amp;lt;code&amp;gt;ATTACH&amp;lt;/code&amp;gt; in iCalendar becomes an img or object element (where the value is stored ito / retrieved from the 'src' or 'data' attributes respectively). An &amp;lt;code&amp;gt;&amp;amp;lt;a class=&amp;quot;attach&amp;quot;                           href=&amp;quot;...&amp;quot;&amp;amp;gt;...&amp;amp;lt;/a&amp;amp;gt;&amp;lt;/code&amp;gt; may also be used, in which case the 'href' attribute is used for the property value.&lt;br /&gt;
&lt;br /&gt;
=== Singular vs. Plural Properties ===&lt;br /&gt;
&lt;br /&gt;
For properties which are singular (e.g. &amp;quot;N&amp;quot; and &amp;quot;FN&amp;quot; from vCard), the first descendant element with that class {{should}} take effect, any others being ignored.&lt;br /&gt;
&lt;br /&gt;
For properties which can be plural (e.g. &amp;quot;TEL&amp;quot; from vCard), each class instance {{should}} create a instance of that property. Plural properties with subtypes (e.g. TEL with WORK, HOME, CELL from vCard) can be optimized to share a common element for the property itself, with each instance of subtype being an appropriately classed descendant of the property element.&lt;br /&gt;
&lt;br /&gt;
==== Plural Properties Singularized ====&lt;br /&gt;
&lt;br /&gt;
Since plural property names become their singular equivalents, even if the original plural property permitted only a single value with multiple components, those multiple components are represented each with their own singularly named property and the the property is effectively multivalued and subject to the above treatment of multivalued properties.&lt;br /&gt;
&lt;br /&gt;
=== Human vs. Machine readable ===&lt;br /&gt;
If an &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; element is used for a property, then the '&amp;lt;code&amp;gt;title&amp;lt;/code&amp;gt;' attribute of the &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; element is the value of the property, instead of the contents of the element,  which instead provide a human presentable version of the value.  This specification recommends that such &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; elements be used for the following iCalendar properties:&lt;br /&gt;
* DTSTART, DTEND, DURATION, RDATE, RRULE&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
&lt;br /&gt;
Here is a sample multiple-day event in an iCalendar:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;nowiki&amp;gt;&lt;br /&gt;
BEGIN:VCALENDAR&lt;br /&gt;
PRODID:-//XYZproduct//EN&lt;br /&gt;
VERSION:2.0&lt;br /&gt;
BEGIN:VEVENT&lt;br /&gt;
URL:http://conferences.oreillynet.com/pub/w/40/program.html&lt;br /&gt;
DTSTART:20051005&lt;br /&gt;
DTEND:20051008&lt;br /&gt;
SUMMARY:Web 2.0 Conference&lt;br /&gt;
LOCATION:Argent Hotel\, San Francisco\, CA&lt;br /&gt;
END:VEVENT&lt;br /&gt;
END:VCALENDAR&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and an equivalent event in hCalendar format with various elements optimized appropriately. See [[hcalendar-example1-steps]] for the derivation.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;a class=&amp;quot;url&amp;quot; href=&amp;quot;http://conferences.oreillynet.com/pub/w/40/program.html&amp;quot;&amp;gt;&lt;br /&gt;
  http://conferences.oreillynet.com/pub/w/40/program.html&lt;br /&gt;
 &amp;lt;/a&amp;gt;&lt;br /&gt;
 &amp;lt;span class=&amp;quot;summary&amp;quot;&amp;gt;Web 2.0 Conference&amp;lt;/span&amp;gt;: &lt;br /&gt;
 &amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;2005-10-05&amp;quot;&amp;gt;October 5&amp;lt;/abbr&amp;gt;-&lt;br /&gt;
 &amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;2005-10-07&amp;quot;&amp;gt;7&amp;lt;/abbr&amp;gt;,&lt;br /&gt;
 at the &amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt;Argent Hotel, San Francisco, CA&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
which could be displayed as:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;url&amp;quot;&amp;gt;http://conferences.oreillynet.com/pub/w/40/program.html&amp;lt;/span&amp;gt;&amp;amp;nbsp;&amp;lt;!-- note modified to account for idiosyncrasy of wiki software --&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;summary&amp;quot;&amp;gt;Web 2.0 Conference&amp;lt;/span&amp;gt;: &lt;br /&gt;
&amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;2005-10-05&amp;quot;&amp;gt;October 5&amp;lt;/abbr&amp;gt;-&lt;br /&gt;
&amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;2005-10-07&amp;quot;&amp;gt;7&amp;lt;/abbr&amp;gt;,&lt;br /&gt;
at the &amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt;Argent Hotel, San Francisco, CA&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note 1: that this is a '''live''' hCalendar microformat, which will be found on this page by parsers.&lt;br /&gt;
&lt;br /&gt;
Note 2: This example used to have &amp;quot;2005-10-08&amp;quot; as the value of the dtend, but per the resolution to the [[dtend-issue]], has been changed to &amp;quot;2005-10-07&amp;quot; in order to encourage publishers/implementers to update their markup/code immediately and [http://ufxtract.com/testsuite/hcalendar/hcalendar1.htm test it].&lt;br /&gt;
&lt;br /&gt;
Note 3: Note that the iCalendar in the first part of the example has the code &amp;lt;code&amp;gt;DTEND:20051008&amp;lt;/code&amp;gt;. That &amp;quot;8&amp;quot; is not a typo. iCalendar uses &amp;lt;em&amp;gt;exclusive&amp;lt;/em&amp;gt; whole end dates (DTEND values) and thus requires that the DTEND value be set to a whole day &amp;lt;em&amp;gt;after&amp;lt;/em&amp;gt; what content publishers visibly display as the ending date of an event. iCalendar's exclusive end dates convention has shown to be [[dtend-issue|problematic and confusing]] for content authors and publishers. Thus per the resolution to the [[dtend-issue]], in hCalendar, the end date is stated exactly as existing events publish visible end dates to humans, with an &amp;lt;em&amp;gt;inclusive&amp;lt;/em&amp;gt; end date (dtend property value), in this example, 2005-10-07.&lt;br /&gt;
&lt;br /&gt;
=== Meeting Example ===&lt;br /&gt;
The following &amp;lt;span id=&amp;quot;Example_2&amp;quot;&amp;gt;example&amp;lt;/span&amp;gt; specifies a scheduled meeting that begins&lt;br /&gt;
at 8:30 AM EST on March 12, 1998 and ends at 9:30 AM EST on March 12,&lt;br /&gt;
1998. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
     BEGIN:VCALENDAR&lt;br /&gt;
     BEGIN:VEVENT&lt;br /&gt;
     UID:guid-1.host1.com&lt;br /&gt;
     DTSTAMP:19980309T231000Z&lt;br /&gt;
     DESCRIPTION:Project XYZ Review Meeting&lt;br /&gt;
     SUMMARY:XYZ Project Review&lt;br /&gt;
     DTSTART:19980312T133000Z&lt;br /&gt;
     DTEND:19980312T143000Z&lt;br /&gt;
     LOCATION:1CP Conference Room 4350&lt;br /&gt;
     END:VEVENT&lt;br /&gt;
     END:VCALENDAR&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The equivalent in hCalendar:&lt;br /&gt;
&lt;br /&gt;
'''Note: This example needs to be updated to use the [[value-class-pattern]]. Use of full ISO8601 datetimes in abbr title attributes is deprecated in lieu of separate dates and times per the value-class-pattern.'''&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;h3 class=&amp;quot;summary&amp;quot;&amp;gt;XYZ Project Review&amp;lt;/h3&amp;gt;&lt;br /&gt;
&amp;lt;p class=&amp;quot;description&amp;quot;&amp;gt;Project XYZ Review Meeting&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;To be held on &amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;1998-03-12T08:30:00-05:00&amp;quot;&amp;gt;12 March 1998 from 8:30am EST&amp;lt;/abbr&amp;gt; &lt;br /&gt;
until &amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;1998-03-12T09:30:00-05:00&amp;quot;&amp;gt;9:30am EST&amp;lt;/abbr&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Location: &amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt;1CP Conference Room 4350&amp;lt;/span&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;small&amp;gt;Booked by: &amp;lt;span class=&amp;quot;uid&amp;quot;&amp;gt;guid-1.host1.com&amp;lt;/span&amp;gt; on &lt;br /&gt;
&amp;lt;abbr class=&amp;quot;dtstamp&amp;quot; title=&amp;quot;19980309T231000Z&amp;quot;&amp;gt;9 Mar 1998 6:00pm&amp;lt;/abbr&amp;gt;&amp;lt;/small&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This could be displayed as:&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h3 class=&amp;quot;summary&amp;quot;&amp;gt;XYZ Project Review&amp;lt;/h3&amp;gt;&lt;br /&gt;
&amp;lt;p class=&amp;quot;description&amp;quot;&amp;gt;Project XYZ Review Meeting&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;To be held on &amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;1998-03-12T08:30:00-05:00&amp;quot;&amp;gt;12 March 1998 from 8:30am EST&amp;lt;/abbr&amp;gt; &lt;br /&gt;
until &amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;1998-03-12T09:30:00-05:00&amp;quot;&amp;gt;9:30am EST&amp;lt;/abbr&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Location: &amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt;1CP Conference Room 4350&amp;lt;/span&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;small&amp;gt;Booked by: &amp;lt;span class=&amp;quot;uid&amp;quot;&amp;gt;guid-1.host1.com&amp;lt;/span&amp;gt; on &amp;lt;abbr class=&amp;quot;dtstamp&amp;quot; title=&amp;quot;19980309T231000Z&amp;quot;&amp;gt;9 Mar 1998 6:00pm&amp;lt;/abbr&amp;gt;&amp;lt;/small&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Note 1: The product information is not necessary since hCalendar is an interchange format.  When transforming hCalendar back into iCalendar, the transforming engine should add its own product ID.&lt;br /&gt;
&lt;br /&gt;
Note 2: A surrounding &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;span class=&amp;quot;vcalendar&amp;quot;&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; element is optional, and is left out as such.  It is optional since the context of a vcalendar is implied when a vevent is encountered.  The implied context/scope is that of the document.  Authors may explicitly use elements with class=&amp;quot;vcalendar&amp;quot; to wrap sets of vevents that all belong to the same calendar, e.g. when publishing multiple calendars on the same page.&lt;br /&gt;
&lt;br /&gt;
Note 3: The version information is unnecessary in hCalendar markup directly since the version will be defined by the profile of hCalendar that is used/referred to in the 'profile' attribute of the &amp;lt;head&amp;gt; element.&lt;br /&gt;
&lt;br /&gt;
Note 4: [[iso-8601|ISO8601]] datetimes (required by iCalendar) are not very human friendly.  In addition, the year is often understood implicitly by humans from the context.  Thus &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; elements are used to simultaneously provide a human friendly date and/or time in the visible contents of the element, while placing the respective machine parsable comprehensive ISO8601 datetime in the 'title' attribute.&lt;br /&gt;
The notation &amp;lt;code&amp;gt;YYYY-MM-DDThh:mm:ss&amp;lt;/code&amp;gt; should be used for better readability, following the format of RFC 3339.  '''Update: Per the [[value-class-pattern]], separate dates and times {{should}} be used by authors rather than a full ISO8601 datetime, for better readability and listenability.'''&lt;br /&gt;
&lt;br /&gt;
Note 5: Per the [[dtend-issue]] resolution, DTEND dates are provided as humans expecte them to be (consistent with what day an event ends on), rather than iCalendar's confusing definition (the day after). Thus hCalendar processors which produce iCalendar must make the transformation, which is to treat a whole hCalendar &amp;lt;code&amp;gt;dtend&amp;lt;/code&amp;gt; end date as *inclusive*, and convert it to an *[http://lists.osafoundation.org/pipermail/ietf-calsify/2005-September/000769.html exclusive DTEND]* end date when producing iCalendar.&lt;br /&gt;
&lt;br /&gt;
Note 6: The location in this example contains implicit structure (venue name, city, state) which could be marked up explicitly as an [[hcard|hCard]].  See [http://microformats.org/wiki/hcalendar-brainstorming#hCard_locations hCalendar brainstorming: hCard locations] for a informative explanation of how to do this.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== More Examples ===&lt;br /&gt;
See [[hcalendar-examples|hCalendar examples]] for more examples, including examples from iCalendar RFC 2445 converted into hCalendar.&lt;br /&gt;
&lt;br /&gt;
== Examples in the wild ==&lt;br /&gt;
This section is '''informative'''. The number of hCalendar examples in the wild has expanded far beyond the capacity of being kept inline in this specification. They have been moved to a [[hcalendar-examples-in-wild|separate page]].&lt;br /&gt;
&lt;br /&gt;
See [[hcalendar-examples-in-wild|hCalendar Examples in the wild]].&lt;br /&gt;
&lt;br /&gt;
== Implementations ==&lt;br /&gt;
This section is '''informative'''. The number of hCalendar implementations has also expanded beyond the capacity of keeping them inline. They have been moved to a [[hcalendar-implementations|separate page]].&lt;br /&gt;
&lt;br /&gt;
See [[hcalendar-implementations|hCalendar Implementations]].&lt;br /&gt;
&lt;br /&gt;
== Articles ==&lt;br /&gt;
This section is &amp;lt;strong&amp;gt;informative&amp;lt;/strong&amp;gt;. Articles and blog posts on hCalendar, most recent first. When it gets too big, we can move it to a page like [[hcalendar-articles]].&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span class=&amp;quot;hentry&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;published&amp;quot;&amp;gt;2009-08-19&amp;lt;/span&amp;gt; (Updated: &amp;lt;span class=&amp;quot;updated&amp;quot;&amp;gt;2009-09-10&amp;lt;/span&amp;gt;) &amp;lt;cite class=&amp;quot;entry-title&amp;quot;&amp;gt;[http://dev.opera.com/articles/view/styling-and-extracting-hcalendar/ Styling and extracting hCalendar]&amp;lt;/cite&amp;gt; by  &amp;lt;span class=&amp;quot;vcard author&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;fn org&amp;quot;&amp;gt;[http://dev.opera.com/author/1048426 Christopher Schmitt]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
* 2008-11-17 [http://forabeautifulweb.com/blog/about/a_tribute_to_microformats_a_reader_question_answered/ A tribute to Microformats (a reader question answered)] by [http://www.stuffandnonsense.co.uk/ Andy Clarke]&lt;br /&gt;
* 2008-10-01 [http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-4-hcalendar/ Getting Semantic With Microformats, Part 4: hCalendar] by [http://www.ablognotlimited.com/ Emily Lewis]&lt;br /&gt;
* 2008-02-01 [http://www.peachpit.com/guides/content.aspx?g=webdesign&amp;amp;seqNum=356 Microformats: The Art of Markup: hCalendar] by [http://www.stuffandnonsense.co.uk/ Andy Clarke]&lt;br /&gt;
* 2006-01-11 [http://weblog.infoworld.com/udell/2006/01/11.html#a1368 Moving forward with microformats] by [http://weblog.infoworld.com/udell Jon Udell] provides an hCalendar example and some discussion.&lt;br /&gt;
&lt;br /&gt;
See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page] and the [http://technorati.com/tags/hcalendar hCalendar tag]&lt;br /&gt;
&lt;br /&gt;
==Buttons==&lt;br /&gt;
This section is &amp;lt;strong&amp;gt;informative&amp;lt;/strong&amp;gt;. Don't forget that you can add one of our [[buttons#hCalendar|buttons]] to the page, to indicate the presence of hCalendar microformats. For example: http://www.boogdesign.com/images/buttons/microformat_hcalendar.png. If you can link it back to this page (or even page on your website, about your use of the microformat), so much the better!&lt;br /&gt;
&lt;br /&gt;
== Copyright ==&lt;br /&gt;
Per the public domain release on the authors' user pages ([[User:Tantek|Tantek Çelik]], [[User:Brian|Brian Suda]]) this specification is released into the public domain.&lt;br /&gt;
&lt;br /&gt;
{{MicroFormatPublicDomainContributionStatement}}&lt;br /&gt;
&lt;br /&gt;
== Patents ==&lt;br /&gt;
{{MicroFormatPatentStatement}}&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;
* [[hcard|hCard]]&lt;br /&gt;
* [http://www.ietf.org/rfc/rfc2445.txt iCalendar RFC2445]&lt;br /&gt;
* [[rfc-2119| RFC 2119]]&lt;br /&gt;
* [[iso-8601|ISO8601]]&lt;br /&gt;
&lt;br /&gt;
=== Informative References ===&lt;br /&gt;
This section is &amp;lt;strong&amp;gt;informative&amp;lt;/strong&amp;gt;.&lt;br /&gt;
* [http://w3.org/TR/REC-CSS1 CSS1]&lt;br /&gt;
* [http://tantek.com/log/2004/09.html#hcalendar hCalendar term introduced and defined on the Web, 20040930]&lt;br /&gt;
* [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation, 20040911]&lt;br /&gt;
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]&lt;br /&gt;
* [http://ietfreport.isoc.org/idref/draft-royer-ical-basic/ iCal-Basic (latest)] [http://www.faqs.org/ftp/pub/pub/internet-drafts/draft-royer-ical-basic-04.txt (draft 04)]&lt;br /&gt;
* [http://www.w3.org/TR/NOTE-datetime W3C Note on Date and Time Formats]&lt;br /&gt;
* [http://www.imc.org/pdi/ Internet Mail Consortium Personal Data Interchange vCard and vCalendar]&lt;br /&gt;
* Contributed from http://developers.technorati.com/wiki/hCalendar&lt;br /&gt;
&lt;br /&gt;
==== Specifications That Use hCalendar ====&lt;br /&gt;
* [[hreview|hReview]]&lt;br /&gt;
&lt;br /&gt;
==== Related Work ====&lt;br /&gt;
* [http://lists.osafoundation.org/pipermail/ietf-calsify/ IETF-calsify archives]&lt;br /&gt;
* [http://www.softwarestudio.org/iCal/2445Issues.html RFC2445 Issues List]&lt;br /&gt;
* [http://ietf.webdav.org/calsify/ CALSIFY WG Links And Resources]&lt;br /&gt;
&lt;br /&gt;
== Inspiration and Acknowledgments ==&lt;br /&gt;
Thanks to:&lt;br /&gt;
* Adam Bosworth for leading the [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation] which brought together a critical mass of interested parties.&lt;br /&gt;
&lt;br /&gt;
== Related Reading ==&lt;br /&gt;
This section is &amp;lt;strong&amp;gt;informative&amp;lt;/strong&amp;gt;.&lt;br /&gt;
Some &amp;lt;span id=&amp;quot;Further_Reading&amp;quot;&amp;gt;further reading&amp;lt;/span&amp;gt; on the broader topic of calendars and calendaring formats.&lt;br /&gt;
* [http://www.livejournal.com/users/jwz/444651.html jwz - Hula] (required reading)&lt;br /&gt;
* [http://www.jwz.org/doc/groupware.html Groupware Bad by Jamie Zawinski] crystalizes the reason for hCalendar ('''emphasis''' added):&lt;br /&gt;
&amp;lt;blockquote&amp;gt;Right now people can do that by publishing .ics files, but it's not trivial to do so, and it's work on the part of other people to look at them. '''If it's not HTML hanging off our friend's home page that can be viewed in any browser on a public terminal in a library, the bar to entry is too high and it's useless.'''&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
{{hcalendar-related-pages}}&lt;br /&gt;
* [http://en.wikipedia.org/wiki/HCalendar Wikipedia article on hCalendar]&lt;br /&gt;
&lt;br /&gt;
[[Category:Specifications]]&lt;br /&gt;
[[Category:hCalendar]]&lt;br /&gt;
&lt;br /&gt;
== Translations ==&lt;br /&gt;
Read the hCard specification in additional &amp;lt;span id=&amp;quot;languages&amp;quot;&amp;gt;languages&amp;lt;/span&amp;gt;:&lt;br /&gt;
* [[hcalendar-fr|français]]&lt;br /&gt;
* [[hcalendar-ru|Русский]]&lt;br /&gt;
* [[hcalendar-ja|日本語]]&lt;/div&gt;</summary>
		<author><name>Alik</name></author>
	</entry>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=hcalendar-ru&amp;diff=43044</id>
		<title>hcalendar-ru</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=hcalendar-ru&amp;diff=43044"/>
		<updated>2010-09-05T20:50:49Z</updated>

		<summary type="html">&lt;p&gt;Alik: Unicode&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= hCalendar =&lt;br /&gt;
&lt;br /&gt;
hCalendar является простым, открытым, распределённым форматом для разметки календарных и иного рода событий. Данный микроформат основан на стандарте iCalendar ([http://www.ietf.org/rfc/rfc2445.txt RFC 2445]). hCalendar можно внедрить в HTML, XHTML и XML-подобные языки разметки.&lt;br /&gt;
hCalendar — один из [[microformats-ru|микроформатов]].&lt;br /&gt;
&lt;br /&gt;
Хотите уже сейчас разметить события на своих страницах с помощью hCalendar? Попробуйте использовать [http://microformats.org/code/hcalendar/creator генератор hCalendar]. Помимо автоматического создания микроформата, вы можете самостоятельно его разметить, используя пошаговую [[hcalendar-authoring-ru|инструкцию]].&lt;br /&gt;
&lt;br /&gt;
{{authoring-ru|date=&lt;br /&gt;
|authors=&lt;br /&gt;
; Редактор &lt;br /&gt;
: [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc])&lt;br /&gt;
; Авторы &lt;br /&gt;
: [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc])&lt;br /&gt;
: [http://suda.co.uk/ Brian Suda]&lt;br /&gt;
|rights=}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- TOC START --&amp;gt;&lt;br /&gt;
{{TOC-right}}&lt;br /&gt;
&amp;lt;!-- TOC END --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- ADDED AFTER EDIT === Inspiration and Acknowledgments ===&lt;br /&gt;
Thanks to:&lt;br /&gt;
* Adam Bosworth for leading the [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation] which brought together a critical mass of interested parties. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Введение ==&lt;br /&gt;
Стандарт iCalendar ([http://www.ietf.org/rfc/rfc2445.txt RFC 2445]) уже довольно долгое время используется в сети и в прикладных приложениях (например, iCal в Mac OS X).&lt;br /&gt;
&lt;br /&gt;
В дополнение к этому, блоггеры очень часто обсуждают различные события в своих блогах: грядущие события или описания старых. С добавлением небольших изменений, блоггеры смогут обсуждать события в своём блоге таким образом, что различные поисковые роботы и другие аггрегаторы смогут автоматически их получать, конвертировать в iCalendar, а затем использовать в любых прикладных приложениях или сервисах.&lt;br /&gt;
&lt;br /&gt;
Данная спецификация включает в себя описание формата '''hCalendar''' в качестве проекции стандарта iCalendar на семантический (X)HTML. Таким образом, авторы блогов могут включать данный формат напрямую в свои страницы, а не ссылаться на определённый внешний файл.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Особенности реализации в XHTML ==&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
XHTML is built on XML, and thus XHTML based formats can be used not only for convenient display presentation, but also for general purpose data exchange.  In many ways, XHTML based formats exemplify the best of both HTML and XML worlds.  However, when building XHTML based formats, it helps to have a guiding set of principles.&lt;br /&gt;
&lt;br /&gt;
# Reuse the schema (names, objects, properties, values, types, hierarchies, constraints) as much as possible from pre-existing, established, well-supported standards by reference.  Avoid restating constraints expressed in the source standard.  Informative mentions are ok.&lt;br /&gt;
## For types with multiple components, use nested elements with class names equivalent to the names of the components.&lt;br /&gt;
## Plural components are made singular, and thus multiple nested elements are used to represent multiple text values that are comma-delimited.&lt;br /&gt;
# Use the most accurately precise [[semantic-xhtml|semantic XHTML]] building block for each object etc.&lt;br /&gt;
# Otherwise use a generic structural element (e.g. &amp;lt;code&amp;gt;&amp;amp;lt;span&amp;amp;gt;&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;&amp;amp;lt;div&amp;amp;gt;&amp;lt;/code&amp;gt;), or the appropriate contextual element (e.g. an &amp;lt;code&amp;gt;&amp;amp;lt;li&amp;amp;gt;&amp;lt;/code&amp;gt; inside a &amp;lt;code&amp;gt;&amp;amp;lt;ul&amp;amp;gt;&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;&amp;amp;lt;ol&amp;amp;gt;&amp;lt;/code&amp;gt;).&lt;br /&gt;
# Use class names based on names from the original schema, unless the semantic XHTML building block precisely represents that part of the original schema.  If names in the source schema are case-insensitive, then use an all lowercase equivalent.  Components names implicit in prose (rather than explicit in the defined schema) should also use lowercase equivalents for ease of use. Spaces in component names become dash '-' characters.&lt;br /&gt;
# Finally, if the format of the data according to the original schema is too long and/or not human-friendly, use &amp;lt;code&amp;gt;&amp;amp;lt;abbr&amp;amp;gt;&amp;lt;/code&amp;gt; instead of a generic structural element, and place the literal data into the 'title' attribute (where abbr expansions go), and the more brief and human readable equivalent into the element itself.  Further informative explanation of this use of &amp;lt;code&amp;gt;&amp;amp;lt;abbr&amp;amp;gt;&amp;lt;/code&amp;gt;: [http://tantek.com/log/2005/01.html#d26t0100 Human vs. ISO8601 dates problem solved] --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Стоит заметить, что поддержка &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; в Internet Explorer далека от совершенства и для полной работоспособности данного элемента могут понадобиться другие средства.&lt;br /&gt;
&lt;br /&gt;
См. подробнее [[semantic-xhtml-ru|особенности семантики]].&lt;br /&gt;
&lt;br /&gt;
== Формат ==&lt;br /&gt;
&lt;br /&gt;
=== Детальное описание ===&lt;br /&gt;
Стандарт iCalendar ([http://www.ietf.org/rfc/rfc2445.txt RFC 2445]) является основой для микроформата hCalendar.&lt;br /&gt;
&lt;br /&gt;
Одной из целью hCalendar является использование названий свойств iCalendar в нижнем регистре для имён классов и создания иерархии из XHTML-элементов, похожей на иерархию элементов iCalendar.&lt;br /&gt;
&lt;br /&gt;
=== Имя корневого класса ===&lt;br /&gt;
Корневым классом для hCalendar является '''vcalendar''', отсюда следует, что элемент с таким классом и будет называться hCalendar.&lt;br /&gt;
&lt;br /&gt;
Корневым классом для событий является '''vevent'''. Элемент с таким классом называется '''событием hCalendar''' (hCalendar event).&lt;br /&gt;
&lt;br /&gt;
Для облегчения внедрения формата и его последующей автоматической обработки, оба класса, vevent и vcalendar, считаются корневыми. Если документ содержит элементы с именем класса vevent, но не содержит элементов с классом vcalendar, значит весь документ принимает на себя контекст vcalendar.&lt;br /&gt;
&lt;br /&gt;
=== Свойства и подсвойства ===&lt;br /&gt;
Свойства hCalendar представляют собой вложенные внутри hCalendar (элемента с классом vcalendar или vevent) элементы. Элементы с указанными именами классов содержат в себе значения свойств hCalendar. У некоторых свойств есть подсвойства, которые обладают таким же свойством вложенности элементов.&lt;br /&gt;
&lt;br /&gt;
=== Список свойств ===&lt;br /&gt;
&lt;br /&gt;
'''Обязательные:'''&lt;br /&gt;
* ''dtstart'' ([[iso-8601|дата по ISO-стандарту (англ)]]) &amp;lt;!-- NEED RUSSIAN TRANSL. of ISO-8601 --&amp;gt;&lt;br /&gt;
* ''summary''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Необязательные''':&lt;br /&gt;
* location&lt;br /&gt;
* url&lt;br /&gt;
* dtend (дата по ISO-стандарту), duration (период по ISO-стандарту)&lt;br /&gt;
* rdate, rrule&lt;br /&gt;
* category, description&lt;br /&gt;
* uid&lt;br /&gt;
* geo (latitude, longitude)&lt;br /&gt;
&lt;br /&gt;
''Данный список является незавершённым, но он отображает те свойства, которые используются при разметке hCalendar чаще остальных.'' &lt;br /&gt;
&lt;br /&gt;
=== Семантические эквиваленты ===&lt;br /&gt;
Для некоторых свойств существуют более семантичные эквиваленты, поэтому они распознаются особым образом:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;URL&amp;lt;/code&amp;gt; в iCalendar превращается в &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; внутри элемента &amp;lt;code&amp;gt;class=&amp;quot;vevent&amp;quot;&amp;lt;/code&amp;gt; в hCalendar.&lt;br /&gt;
* &amp;lt;code&amp;gt;ATTENDEE&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;CONTACT&amp;lt;/code&amp;gt; и &amp;lt;code&amp;gt;ORGANIZER&amp;lt;/code&amp;gt; в iCalendar могут быть представлены с помощью микроформата [[hcard-ru|hCard]] в hCalendar .&lt;br /&gt;
* Названный &amp;lt;code&amp;gt;LOCATION&amp;lt;/code&amp;gt; (с адресом и/или географическими координатами) в iCalendar может быть представлен вложенным в hCalendar [[hcard-ru|hCard]]. Подобно ему, адрес в &amp;lt;code&amp;gt;LOCATION&amp;lt;/code&amp;gt; может быть представлен, используя микроформат [[adr-ru|adr]], а географические данные — [[geo-ru|geo]].&lt;br /&gt;
* &amp;lt;code&amp;gt;UID&amp;lt;/code&amp;gt; в iCalendar просто становится URL, где обозначено событие hCalendar.&lt;br /&gt;
&lt;br /&gt;
=== Однозначные и многозначные свойства ===&lt;br /&gt;
&lt;br /&gt;
Для свойств, которые встречаются (должны встречаться) только один раз (подобно ''N'' и ''FN'' из vCard), первый вложенный элемент с таким классом считается эффективным, остальные должны игнорироваться.&lt;br /&gt;
&lt;br /&gt;
Для свойств, которые могут встречаться неоднократно (как ''TEL'' из vCard), каждый элемент с таким классом должен создавать новый экземпляр этого свойства. Многозначные свойства с подтипами (как ''TEL'' с ''WORK'', ''HOME'', ''CELL'' из vCard) могут быть оптимизированы таким образом, чтобы разделять один общий элемент для самого свойства, тогда подтипы становятся потомком элемента, содержащего свойство.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- CAN_OMMIT&lt;br /&gt;
==== Plural Properties Singularized ====&lt;br /&gt;
&lt;br /&gt;
Since plural property names become their singular equivalents, even if the original plural property permitted only a single value with multiple components, those multiple components are represented each with their own singularly named property and the the property is effectively multivalued and subject to the above treatment of multivalued properties. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Удобочитаемость со стороны человека и машины ===&lt;br /&gt;
Если для отображения свойства используется элемент &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;, тогда применённый к нему атрибут &amp;lt;code&amp;gt;title&amp;lt;/code&amp;gt; является значением такого элемента, а не содержимое этого элемента, который, заместо этого, предоставляет удобочитаемый вариант свойства. Данная спецификация рекомендует использовать элемент &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code для отображения таких свойств, как:&lt;br /&gt;
&lt;br /&gt;
* DTSTART&lt;br /&gt;
* DTEND&lt;br /&gt;
* DURATION&lt;br /&gt;
* RDATE&lt;br /&gt;
* RRULE&lt;br /&gt;
&lt;br /&gt;
== Примеры ==&lt;br /&gt;
&lt;br /&gt;
=== iCalendar и hCalendar ===&lt;br /&gt;
&lt;br /&gt;
Пример описания события в iCalendar:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;nowiki&amp;gt;&lt;br /&gt;
BEGIN:VCALENDAR&lt;br /&gt;
PRODID:-//XYZproduct//EN&lt;br /&gt;
VERSION:2.0&lt;br /&gt;
BEGIN:VEVENT&lt;br /&gt;
URL:http://www.web2con.com/&lt;br /&gt;
DTSTART:20071005&lt;br /&gt;
DTEND:20071020&lt;br /&gt;
SUMMARY:Web 2.0 Conference&lt;br /&gt;
LOCATION:Argent Hotel\, San Francisco\, CA&lt;br /&gt;
END:VEVENT&lt;br /&gt;
END:VCALENDAR&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Эквивалентная вышеприведённому примеру разметка hCalendar&lt;br /&gt;
&amp;lt;!-- See [[hcalendar-example1-steps]] for the derivation. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;a class=&amp;quot;url&amp;quot; href=&amp;quot;http://www.web2con.com/&amp;quot;&amp;gt;http://www.web2con.com/&amp;lt;/a&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;summary&amp;quot;&amp;gt;Web 2.0 Conference&amp;lt;/span&amp;gt;: &lt;br /&gt;
  &amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;2007-10-05&amp;quot;&amp;gt;October 5&amp;lt;/abbr&amp;gt;-&lt;br /&gt;
  &amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;2007-10-20&amp;quot;&amp;gt;19&amp;lt;/abbr&amp;gt;,&lt;br /&gt;
 at the &amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt;Argent Hotel, San Francisco, CA&amp;lt;/span&amp;gt;&lt;br /&gt;
 &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Вышеотмеченная разметка hCalendar будет отображена похожим образом:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;url&amp;quot;&amp;gt;http://www.web2con.com/&amp;lt;/span&amp;gt;&amp;amp;nbsp;&amp;lt;!-- note modified to account for idiosyncrasy of wiki software --&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;summary&amp;quot;&amp;gt;Web 2.0 Conference&amp;lt;/span&amp;gt;: &lt;br /&gt;
&amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;2007-10-05&amp;quot;&amp;gt;October 5&amp;lt;/abbr&amp;gt;-&lt;br /&gt;
&amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;2007-10-20&amp;quot;&amp;gt;19&amp;lt;/abbr&amp;gt;,&lt;br /&gt;
at the &amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt;Argent Hotel, San Francisco, CA&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Заметьте, что парсеры уже сейчас могут найти этот микроформат на этой странице. &lt;br /&gt;
&lt;br /&gt;
=== hCalendar с размытым событием ===&lt;br /&gt;
&lt;br /&gt;
Следующий пример отмечает время встречи, которая начинается в 8:30 AM EST, 12 марта 1998 года и заканчивается в 9:30 AM EST, 12 марта 1998 года.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
     BEGIN:VCALENDAR&lt;br /&gt;
     BEGIN:VEVENT&lt;br /&gt;
     UID:guid-1.host1.com&lt;br /&gt;
     DTSTAMP:19980309T231000Z&lt;br /&gt;
     DESCRIPTION:Project XYZ Review Meeting&lt;br /&gt;
     SUMMARY:XYZ Project Review&lt;br /&gt;
     DTSTART:19980312T133000Z&lt;br /&gt;
     DTEND:19980312T143000Z&lt;br /&gt;
     LOCATION:1CP Conference Room 4350&lt;br /&gt;
     END:VEVENT&lt;br /&gt;
     END:VCALENDAR&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Эквивалент вышеприведённому примеру:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;h3 class=&amp;quot;summary&amp;quot;&amp;gt;XYZ Project Review&amp;lt;/h3&amp;gt;&lt;br /&gt;
&amp;lt;p class=&amp;quot;description&amp;quot;&amp;gt;Project XYZ Review Meeting&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;To be held on &amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;1998-03-12T08:30:00-05:00&amp;quot;&amp;gt;12 March 1998 from 8:30am EST&amp;lt;/abbr&amp;gt; &lt;br /&gt;
until &amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;1998-03-12T09:30:00-05:00&amp;quot;&amp;gt;9:30am EST&amp;lt;/abbr&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Location: &amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt;1CP Conference Room 4350&amp;lt;/span&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;small&amp;gt;Booked by: &amp;lt;span class=&amp;quot;uid&amp;quot;&amp;gt;guid-1.host1.com&amp;lt;/span&amp;gt; on &lt;br /&gt;
&amp;lt;abbr class=&amp;quot;dtstamp&amp;quot; title=&amp;quot;19980309T231000Z&amp;quot;&amp;gt;9 Mar 1998 6:00pm&amp;lt;/abbr&amp;gt;&amp;lt;/small&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Его возможное отображение:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;h3 class=&amp;quot;summary&amp;quot;&amp;gt;XYZ Project Review&amp;lt;/h3&amp;gt;&lt;br /&gt;
&amp;lt;p class=&amp;quot;description&amp;quot;&amp;gt;Project XYZ Review Meeting&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;To be held on &amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;1998-03-12T08:30:00-05:00&amp;quot;&amp;gt;12 March 1998 from 8:30am EST&amp;lt;/abbr&amp;gt; &lt;br /&gt;
until &amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;1998-03-12T09:30:00-05:00&amp;quot;&amp;gt;9:30am EST&amp;lt;/abbr&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Location: &amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt;1CP Conference Room 4350&amp;lt;/span&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;small&amp;gt;Booked by: &amp;lt;span class=&amp;quot;uid&amp;quot;&amp;gt;guid-1.host1.com&amp;lt;/span&amp;gt; on &amp;lt;abbr class=&amp;quot;dtstamp&amp;quot; title=&amp;quot;19980309T231000Z&amp;quot;&amp;gt;9 Mar 1998 6:00pm&amp;lt;/abbr&amp;gt;&amp;lt;/small&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Примечания к примеру ====&lt;br /&gt;
# Информация о продукте необязательна, так как hCalendar — формат для обмена. Когда hCalendar трансформируется обратно в iCalendar, сам транскодер может добавить его собственный ID (product ID).&lt;br /&gt;
# Окружение hCalendar элементом &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;span class=&amp;quot;vcalendar&amp;quot;&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; является необязательным, поэтому данный элемент в примере опущен. Если элемент vcalendar опускается, то vevent начинает принадлежать ко всему документу в целом, который в данном случае игрет роль vcalendar-контейнера. Авторы разметки могут напрямую указывать элементы с vcalendar, если у них, к примеру, на странице содержится несколько календарей, событийных веток.&lt;br /&gt;
# Информация о версии в hCalendar необязательна, так как её можно получить через атрибут ''profile'' элемента head.&lt;br /&gt;
# Даты по стандарту [[iso-8601|ISO 8601]] (требуемые стандартом iCalendar) не являются слишком дружелюбными человеческому глазу. В добавление к этому, год часто распознаётся читателями из контекста. Именно поэтому спецификация рекомендует использовать элемент &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;, с помощью которого можно вынести неудобочитаемые данные в атрибут ''title'', а приемлемые для осознавания сведения поместить в сам элемент.&lt;br /&gt;
## Для улучшения удобочитаемости следует использовать указанный в RFC 3339 формат данных: &amp;lt;code&amp;gt;YYYY-MM-DDThh:mm:ss&amp;lt;/code&amp;gt;&lt;br /&gt;
# Разница между ISO 8601 датой DTEND (2005-10-08) и удобочитаемой датой (7) '''не''' является ошибкой. [http://lists.osafoundation.org/pipermail/ietf-calsify/2005-September/000769.html DTEND — уникальное значение]. Это значит, что события кончается прямо '''перед''' DTEND. Для событий, начинающихся в один день и заканчивающихся в другой, дата в DTEND должна быть указана на день позже актуальной. &lt;br /&gt;
# Местоположение в данном примере непосредственно содержит в себе данные, которые можно было бы разметить с помощью [[hcard-ru|hCard]].&lt;br /&gt;
&lt;br /&gt;
=== Другие примеры ===&lt;br /&gt;
См. [[hcalendar-examples-ru|другие примеры hCalendar]].&lt;br /&gt;
&lt;br /&gt;
=== Примеры в сети ===&lt;br /&gt;
См. отдельную страницу с [[hcalendar-examples-in-wild-ru|примерами в сети]].&lt;br /&gt;
&lt;br /&gt;
== Кнопки ==&lt;br /&gt;
&lt;br /&gt;
* http://www.boogdesign.com/images/buttons/microformat_hcalendar.png&lt;br /&gt;
* См. [[buttons-ru#hCalendar|другие кнопки]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Реализации ==&lt;br /&gt;
См. [[hcalendar-implementations-ru|реализации]].&lt;br /&gt;
&lt;br /&gt;
== Ссылки ==&lt;br /&gt;
&lt;br /&gt;
=== Нормативные ===&lt;br /&gt;
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]&lt;br /&gt;
* [[hcard-ru|hCard]]&lt;br /&gt;
* [http://www.ietf.org/rfc/rfc2445.txt iCalendar RFC 2445]&lt;br /&gt;
* [[rfc-2119| RFC 2119]]&lt;br /&gt;
* [[iso-8601|ISO 8601]]&lt;br /&gt;
&lt;br /&gt;
=== Информативные ===&lt;br /&gt;
* [http://w3.org/TR/REC-CSS1 CSS1]&lt;br /&gt;
* [http://tantek.com/log/2004/09.html#hcalendar Введение термина hCalendar]&lt;br /&gt;
* [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars HTML для представления календарных событий]&lt;br /&gt;
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats Simple Semantic Formats]&lt;br /&gt;
* [http://ietfreport.isoc.org/idref/draft-royer-ical-basic/ iCal-Basic]  [http://www.faqs.org/ftp/pub/pub/internet-drafts/draft-royer-ical-basic-04.txt iCal-Basic (редакция)]&lt;br /&gt;
* [http://www.w3.org/TR/NOTE-datetime W3C относительно форматов даты и времени]&lt;br /&gt;
* [http://www.imc.org/pdi/ Internet Mail Consortium: vCard и vCalendar]&lt;br /&gt;
* См. также [http://developers.technorati.com/wiki/hCalendar Technorati Wiki для разработчиков]&lt;br /&gt;
&lt;br /&gt;
==== Связанные спецификации ====&lt;br /&gt;
* [[hreview-ru|hReview]]&lt;br /&gt;
&lt;br /&gt;
==== Связанные работы ====&lt;br /&gt;
* [http://lists.osafoundation.org/pipermail/ietf-calsify/ IETF-архивы]&lt;br /&gt;
* [http://www.softwarestudio.org/iCal/2445Issues.html Вопросы к RFC 2445]&lt;br /&gt;
* [http://ietf.webdav.org/calsify/ CALSIFY, ссылки и ресурсы]&lt;br /&gt;
&lt;br /&gt;
==== Дополнительный материал ====&lt;br /&gt;
* [http://www.livejournal.com/users/jwz/444651.html JWZ - Hula]&lt;br /&gt;
* [http://www.jwz.org/doc/groupware.html Groupware Bad от Jamie Zawinski]&lt;br /&gt;
* [http://muddybranch.thejkgroup.com/ Блог Jason Klemow]&lt;br /&gt;
* [http://weblog.infoworld.com/udell/2006/01/11.html#a1368 «Движение вперёд с микроформатами»] от [http://weblog.infoworld.com/udell Jon Udell].&lt;br /&gt;
* См. также [http://www.technorati.com/cosmos/referer.html блоги с обсуждениям] и статьи, отмеченные меткой [http://technorati.com/tags/hcalendar hCalendar].&lt;br /&gt;
* [http://en.wikipedia.org/wiki/HCalendar Wikipedia о hCalendar]&lt;br /&gt;
&lt;br /&gt;
==== Связанные страницы ====&lt;br /&gt;
* [[hcalendar-authoring-ru|Информация о внедрении hCalendar]] &lt;br /&gt;
* [http://microformats.org/code/hcalendar/creator Генератор hCalendar]&lt;br /&gt;
* [[hcalendar-cheatsheet|Подсказки hCalendar]]&lt;br /&gt;
* [[hcalendar-faq-ru|hCalendar FAQ]]&lt;br /&gt;
* [[hcalendar-parsing-ru|Автоматическая обработка hCalendar]]&lt;br /&gt;
* [[hcalendar-profile-ru|XMDP-профиль hCalendar]]&lt;br /&gt;
* [[hcalendar-tests-ru|Тесты парсерам hCalendar]]&lt;br /&gt;
&amp;lt;!-- * [[to-do#hCalendar|hCalendar &amp;quot;to do&amp;quot;]] - jobs to do --&amp;gt;&lt;br /&gt;
&amp;lt;!-- * [[advocacy#hCalendar|hCalendar advocacy]] - encourage others to use hCalendar. --&amp;gt;&lt;br /&gt;
* [[icalendar-implementations-ru|Реализации iCalendar]]&lt;/div&gt;</summary>
		<author><name>Alik</name></author>
	</entry>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=hcard-ru&amp;diff=43043</id>
		<title>hcard-ru</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=hcard-ru&amp;diff=43043"/>
		<updated>2010-09-05T20:49:14Z</updated>

		<summary type="html">&lt;p&gt;Alik: Unicode&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{working-ru|original=hcard}}&lt;br /&gt;
&amp;lt;h1&amp;gt;hCard&amp;lt;/h1&amp;gt;&lt;br /&gt;
hCard — это простой, открытый микроформат для описания людей, компаний, организаций и мест, используя всю мощь vCard ([[rfc-2426|RFC 2426 (англ.)]]). Имена классов hCard полностью отображают имена соответствующих полей vCard на [[semantic-xhtml-ru|семантический (X)HTML]]. hCard — это один из открытых [[microformats-ru|микроформатов]], который можно внедрить в HTML, XHTML, ATOM, RSS и XML.&lt;br /&gt;
&lt;br /&gt;
Хотите разметить собственный hCard? Попробуйте начать с [http://microformats.org/code/hcard/creator генератора hCard] или создайте разметку данного микроформата самостоятельно, следуя [[hcard-authoring-ru|подсказкам]] по внедрению на существующие страницы.&lt;br /&gt;
&lt;br /&gt;
{{authoring-ru|date=|authors=&lt;br /&gt;
&amp;lt;div class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
; &amp;lt;span class=&amp;quot;role&amp;quot;&amp;gt;Редактор&amp;lt;/span&amp;gt; &lt;br /&gt;
: &amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;[[User:Tantek|Tantek Çelik]]&amp;lt;/span&amp;gt; (&amp;lt;span class=&amp;quot;url&amp;quot;&amp;gt;http://tantek.com/&amp;lt;/span&amp;gt;, ранее в [http://technorati.com Technorati, Inc.], и в [http://microsoft.com/ Microsoft Corporation])&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
; Авторы: [http://tantek.com/ Tantek Çelik] (членство в организациях указано выше)&lt;br /&gt;
: &amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;[[User:Brian|Brian Suda]]&amp;lt;/span&amp;gt; (&amp;lt;span class=&amp;quot;url&amp;quot;&amp;gt;http://suda.co.uk/&amp;lt;/span&amp;gt;)&amp;lt;/span&amp;gt;&lt;br /&gt;
|rights=&lt;br /&gt;
; Официальные подтверждения: См. [[hcard#Официальные подтверждения|официальные подтверждения]].&lt;br /&gt;
; Защита прав&lt;br /&gt;
: См. [[hcard#Авторские права|авторские права]] и заявки на [[hcard#Патенты|патенты]].}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- TOC START --&amp;gt;&lt;br /&gt;
{{TOC-right}}&lt;br /&gt;
&amp;lt;!-- TOC END --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Введение ==&lt;br /&gt;
Стандарт vCard ([[rfc-2426|RFC 2426 (англ.)]]) был широко внедрен для обеспечения взаимодействия между различными приложениями (например, приложение «Address Book» компании Apple, встроенное в Mac OS X).Помимо этого, многие блоггеры идентифицируют себя по имени и обсуждают своих друзей и семью на страницах блогов. С помощью небольшой структуризации, блоггеры могут обсуждать (описывать) людей в своих блогах таким образом, что поисковые роботы и другие программы-обработчики смогут запросить эту информацию, автоматически конвертируя её в vCard и используя её впоследствии в любом сервисе или приложении, работающем с vCard.&lt;br /&gt;
&lt;br /&gt;
Эта спецификация представляет формат '''hCard''', который проецирует вышеупомянутый стандарт vCard в семантический HTML. Блоггеры могут внедрять hCard напрямую в Web-документы и оформлять их спомощью CSS для придания им желаемого внешнего вида. Также hCard позволяет приложениям запрашивать информацию прямиком из Web-документов, без обращений к отдельным файлам.&lt;br /&gt;
&lt;br /&gt;
Вы можете использовать [http://microformats.org/code/hcard/creator генератор hCard] и скопировать HTML-код, который он сгенерирует, в ваш блог или Web-сайт для публикации контактной информации.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- {{rfc-2119-intro}} --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Формат ==&lt;br /&gt;
&lt;br /&gt;
=== Особенности ===&lt;br /&gt;
Основополагающим стандартом для hCard является vCard. &lt;br /&gt;
&lt;br /&gt;
В hCard используются имена объектов/свойств vCard, преобразованные в нижний регистр для использования в качетсве имён классов и для создания иерархии HTML-элементов.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Корневой класс ===&lt;br /&gt;
Корневым классом для hCard является &amp;quot;vcard&amp;quot;. Элемент с именем класса &amp;quot;vcard&amp;quot; называется ''hCard''. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Свойства ===&lt;br /&gt;
Свойства hCard — это элементы внутри hCard. Элементы с именами классов указанных свойств представляют собой значения таких свойств. Некоторые свойства могут иметь более сложную вложенную структуру других свойств, но в целом их структура идентична.&lt;br /&gt;
&lt;br /&gt;
=== Список свойств ===&lt;br /&gt;
Свойства hCard&lt;br /&gt;
&lt;br /&gt;
'''Обязательные:'''&lt;br /&gt;
* '''fn'''&lt;br /&gt;
* &amp;lt;span id=&amp;quot;property-list-n&amp;quot;&amp;gt;'''n'''&amp;lt;sup style=&amp;quot;font-size:smaller&amp;quot;&amp;gt;[[#note1|1]]&amp;lt;/sup&amp;gt; (family-name, given-name, additional-name, honorific-prefix, honorific-suffix)&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Необязательные''':&lt;br /&gt;
* nickname, sort-string&lt;br /&gt;
* url, email (тип, значение), &amp;lt;span id=&amp;quot;property-list-tel&amp;quot;&amp;gt;tel&amp;lt;sup style=&amp;quot;font-size:smaller&amp;quot;&amp;gt;[[#note2|2]]&amp;lt;/sup&amp;gt; (тип, значение)&amp;lt;/span&amp;gt;&lt;br /&gt;
* adr (post-office-box, extended-address, street-address, locality, region, postal-code, country-name, type, value), label&lt;br /&gt;
* geo (latitude, longitude), tz&lt;br /&gt;
* photo, logo, sound, bday&lt;br /&gt;
* title, role, org (organization-name, organization-unit)&lt;br /&gt;
* category, note&lt;br /&gt;
* class, key, mailer, uid, rev&lt;br /&gt;
&lt;br /&gt;
=== Дополнительные указания ===&lt;br /&gt;
&amp;lt;span id=&amp;quot;note1&amp;quot;&amp;gt;[[#property-list-n|1. ^]]&amp;lt;/span&amp;gt;: ''n'' не является обязательным атрибутом (см. [[hcard#Оптимизация раздел об оптимизации]]&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;span id=&amp;quot;note2&amp;quot;&amp;gt;[[#property-list-tel|2. ^]]&amp;lt;/span&amp;gt;: Используя ''tel'', авторы могут следовать стандарту [http://en.wikipedia.org/wiki/E.123 E.123] для записи телефонных номеров. Символьные значения (например, +1-555-FORMATS) должны быть сконвертированы в числа. Используйте &amp;lt;code&amp;gt;abbr&amp;lt;/code&amp;gt;, чтобы отображать символьное представление и предоставлять числовое значение. Например:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr title=&amp;quot;+15553676287&amp;quot;&amp;gt;+1-555-FORMATS&amp;lt;/abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=== Единичные и множественные свойства ===&lt;br /&gt;
Список свойств, которые должны однозначно использоваться в формате (только один раз):&lt;br /&gt;
* 'fn'&lt;br /&gt;
* 'n'&lt;br /&gt;
* 'bday'&lt;br /&gt;
* 'tz'&lt;br /&gt;
* 'geo'&lt;br /&gt;
* 'sort-string'&lt;br /&gt;
* 'uid'&lt;br /&gt;
* 'class'&lt;br /&gt;
&lt;br /&gt;
Для таких свойств только первый дочерний элемент с таким классом должен иметь значение, остальные должны игнорироваться.&lt;br /&gt;
&lt;br /&gt;
Все другие свойства могут встречаться несколько раз. Каждый новый подобный класс создаёт новый параметр со значением данного свойства.&lt;br /&gt;
&lt;br /&gt;
=== Читабельность для человека и машины ===&lt;br /&gt;
Человеку доступно всё, что является содержимым элементов (это, собственно, и является содержимым определённого свойства микроформата), с некоторыми нюансами:&lt;br /&gt;
&lt;br /&gt;
* Если элемент ''&amp;lt;code&amp;gt;abbr&amp;lt;/code&amp;gt;'' используется для описания свойства, то атрибут ''&amp;lt;code&amp;gt;title&amp;lt;/code&amp;gt;'' (если обозначен) данного элемента является значением данного свойства, вместо содержимого данного элемента, которое, в данном случае, предоставляет более приемлемую для осознавания человеком информацию.&lt;br /&gt;
* Если для одного или нескольких свойств используется элемент ''&amp;lt;code&amp;gt;a&amp;lt;/code&amp;gt;'', он должен трактоваться следующим образом:&lt;br /&gt;
** Для свойства ''photo'' и любого другого свойства, состоящего из URI, значением является значение атрибута ''href''.&lt;br /&gt;
** Для любых других свойств значением является содержимое элемента.&lt;br /&gt;
* Если для одного или нескольких свойств используется элемент img, он должен трактоваться следующим образом:&lt;br /&gt;
** Для свойства ''photo'' и любого другого свойства, которое получает URI в качестве своего значения, значением является значение атрибута ''src''.&lt;br /&gt;
** Для других свойств, атрибут ''alt'' содержит в себе их значение.&lt;br /&gt;
* Если используется элемент ''object'' для указания одного или нескольких свойств, он должен распознаваться следующим образом:&lt;br /&gt;
** Для свойства ''photo'' и подобных этому свойству свойств, атрибут ''data'' является значением таких свойств.&lt;br /&gt;
** Для других свойств, содержимое элемента является их значением.&lt;br /&gt;
&lt;br /&gt;
=== Частичные значения ===&lt;br /&gt;
Иногда только часть элемента используется как значение определённого свойства. Такое часто происходит в тот момент, когда у свойства есть подтип (например, ''tel''). В данном случае используется специальное имя класса ''value'', чтобы выделить ту часть элемента, которая и будет являться значением свойства. &lt;br /&gt;
&lt;br /&gt;
Вот фрагмент hCard для разметки домашнего номера телефона:&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
vCard:&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
TEL;TYPE=HOME:+1.415.555.1212&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
hCard:&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Домашний телефон&amp;lt;/span&amp;gt;:&lt;br /&gt;
 &amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt;+1.415.555.1212&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Данный фрагмент hCard будет отображён следующим образом:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;border: thin dashed black; width: 95%; padding: .5em 1em;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Домашний телефон&amp;lt;/span&amp;gt;:&lt;br /&gt;
&amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt;+1.415.555.1212&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- &lt;br /&gt;
	note for Tantek: review/edit property casing from here on &lt;br /&gt;
	RUSSIAN_TRANSLATION_STANDART&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Исключения из свойств ===&lt;br /&gt;
У стандарта vCard есть несколько свойств, которые не играют особой роли или их роль берут на себя другие элементы на Web-странице. Этот раздел описывает, что с ними нужно делать.&lt;br /&gt;
&lt;br /&gt;
# Свойства '''NAME''', '''PROFILE''', '''SOURCE''', '''PRODID''', '''VERSION''' в vCard (как определено в разделах .1.2, 2.1.3, 2.1.4, 3.6.3, 3.6.9 [[rfc-2426-ru|RFC 2426]]. Авторы не должны использовать эти свойства в своих hCard, так же как и парсеры должны '''игнорировать''' данные свойства, если они будут обнаружены при обработке hCard. Напротив, конвертерам hCard-в-vCard следует использовать заголовок страницы, где hCard был обнаружен (элемент ''title'' в (X)HTML-документах), чтобы создать свойство NAME, могут вывести свойство PROFILE в соответствии с [[rfc-2426-ru|RFC 2426]], могут использовать URI страницы, где был обнаружен hCard, чтобы заполнить свойство SOURCE. Только приложения, которые создают vCard, должны записывать свойства PRODIF и VERSION (3.0) в соответствии с [[rfc-2426-ru|RFC 2426]].&lt;br /&gt;
&lt;br /&gt;
=== Информация об организации ===&lt;br /&gt;
Если свойства ''FN'' и ''ORG'' имеют одинаковые значения (например, данные классы могут относится к одному элементу, подобно ''class=&amp;quot;fn org&amp;quot;''), hCard представляет собой информацию о связи с компанией, организацией и их следует считать такими. В этом случае авторы '''не должны''' использовать свойство ''N'', но они могут устанавливать их в пустую строку. Из этого следует, что парсеры должны поступать таким же образом.&lt;br /&gt;
&lt;br /&gt;
=== Рекомендации по оптимизации ''n'' ===&lt;br /&gt;
Несмотря на то, что vCard обязует использовать свойство ''N'', сами авторы спецификации vCard не включают это свойство почти до конца спецификации (бывает и такое, да). Данное противоречие может быть разрешено следующим путём: необходимо позволить свойству ''FN'' заменять своим присутствием свойство ''N''. Это и было сделано в hCard. &lt;br /&gt;
&lt;br /&gt;
Если свойства ''FN'' и ''ORG'' не совпадают (см. предыдущий раздел) и значение свойства ''FN'' равно двум словам, разделённых пробелом и не указано свойство ''N'', то свойство ''N'' «получается» из свойства ''FN''. Если же ''FN'' не состоит ровно из двух слов, то авторы обязаны разметить свойство ''N'', если они не создают hCard для организации, конечно.&lt;br /&gt;
&lt;br /&gt;
# Содержимое ''FN'' разбито на два слова, разделённых пробелом.&lt;br /&gt;
# ''Первое'' слово в свойстве ''FN'' — это ''given-name'' для свойства ''N''.&lt;br /&gt;
# ''Второе (последнее)'' слово в этом свойстве интерпретируется как ''family-name'' для свойства ''N''.&lt;br /&gt;
# '''Исключение''': если первое слово заканчивается запятой «,» '''или''' второе слово состоит только из одного символа (после которого может  следовать точка «.»), то первое слово (не считая запятой) интерпретируется как ''family-name'', а второе слово — как ''given-name''.&lt;br /&gt;
&lt;br /&gt;
Вот примеры типичных ситуаций:&lt;br /&gt;
* given-name (пробел) family-name&lt;br /&gt;
* family-name (запятая) given-name&lt;br /&gt;
* family-name (запятая) given-name-first-initial&lt;br /&gt;
* family-name (пробел) given-name-first-initial (необязательная точка)&lt;br /&gt;
&lt;br /&gt;
=== Рекомендации по оптимизации ''nickname'' ===&lt;br /&gt;
Исходя из того, что в сети Интернет, в основном, используются никнеймы/псевдонимы для указания человека (автора), hCard также включает в себя свойство ''nickname''.&lt;br /&gt;
&lt;br /&gt;
По аналогии с оптимизацией ''n'', если свойства ''FN'' и ''ORG'' не совпадают и значением свойства ''FN'' является ровно одно слово, при этом отдельного свойства ''N'' не указано, то: &lt;br /&gt;
&lt;br /&gt;
# Содержимое ''FN'' должно считаться значением свойства ''nickname''.&lt;br /&gt;
# Обработчикам (парсерам) следует заполнить пустыми значениями пропущенное свойство ''N''. &lt;br /&gt;
&lt;br /&gt;
Авторы hCard должны непосредственно указывать свойство ''nickname'', например:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
	&amp;lt;span class=&amp;quot;fn nickname&amp;quot;&amp;gt;daveman692&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
hCard может иметь отдельный элемент с классом ''nickname'', значение которого и будет являться значением одноимённого свойства.&lt;br /&gt;
&lt;br /&gt;
=== Оптимизации ''organization-name'' ===&lt;br /&gt;
Свойство ''ORG'' включает в себя два подсвойства: ''organization-name'' и ''organization-unit''. Очень часто авторы публикуют только ''organization-name''. Из этого следует, что если ''organization-name'' не указано внутри ''ORG'', содержимое ''ORG'' должно трактоваться как ''organization-name''.&lt;br /&gt;
&lt;br /&gt;
=== Теги как категории ===&lt;br /&gt;
Категории в hCard могут быть представлены как теги c использованием микроформата [[rel-tag-ru|rel-tag]]. Когда категория размечена с помощью rel-tag, сам тег (как определено спецификацией rel-tag) и является этой категорией. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Пары значений ''type'' и ''value'' ===&lt;br /&gt;
Подсвойство ''type'' может принимать различные значения, зависящие от того, к какому свойству оно принадлежит. Значения данного подсвойства являются нечувствительными к регистру (это значит, что «Рабочий» — то же самое, что и «рабочий»). Пример:&lt;br /&gt;
&lt;br /&gt;
vCard:&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
TEL;TYPE=HOME,PREF:+1.415.555.1212&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
hCard:&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Home&amp;lt;/span&amp;gt; (&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;pref&amp;lt;/span&amp;gt;erred):&lt;br /&gt;
 &amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt;+1.415.555.1212&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Будет показано следующим образом:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;border: thin dashed black; width: 95%; padding: .5em 1em; &amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Home&amp;lt;/span&amp;gt; (&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;pref&amp;lt;/span&amp;gt;erred):&lt;br /&gt;
&amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt;+1.415.555.1212&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== ''type'' без указанного ''value'' ====&lt;br /&gt;
Когда указан ''type'' свойства и не указан ''value'' свойства, всё, что не является ''type'', считается ''value'' данного свойства, например:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Home&amp;lt;/span&amp;gt; +1.415.555.1212&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Равносильно следующему:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Home&amp;lt;/span&amp;gt;&amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt; +1.415.555.1212&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Следовательно, ''type'' — это «home», а значение — это «+1.415.555.1212»&lt;br /&gt;
&lt;br /&gt;
==== Возможные значения ''type'' для adr, tel и email ====&lt;br /&gt;
&amp;lt;em&amp;gt;См. также разделы 3.2.1 ADR, 3.3.1 TEL и 3.3.2 EMAIL в [[rfc-2426-ru|RFC 2426]] для нормативных сведений. Значение по умолчанию (даже если это несколько значений) — это первое значение в данном списке. &lt;br /&gt;
&lt;br /&gt;
* '''adr''': INTL, POSTAL, PARCEL, WORK, dom, home, pref&lt;br /&gt;
* '''tel''': VOICE, home, msg, work, pref, fax, cell, video, pager, bbs, modem, [http://flickr.com/photos/tags/carcellphone/ car], isdn, pcs&lt;br /&gt;
* '''email''': INTERNET, x400, pref, &amp;quot;other IANA registered address types&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Профиль XMDP ===&lt;br /&gt;
&lt;br /&gt;
См. [http://gmpg.org/xmdp XMDP] [[hcard-profile-ru|профиль hCard]], который содержит все указанные выше свойства.&lt;br /&gt;
&lt;br /&gt;
=== Информация об обработке ===&lt;br /&gt;
&lt;br /&gt;
См. [[hcard-parsing|обработка hCard]].&lt;br /&gt;
&lt;br /&gt;
== Примеры ==&lt;br /&gt;
&amp;lt;em&amp;gt;Данный раздел является информативным&amp;lt;/em&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Пример vCard ===&lt;br /&gt;
&lt;br /&gt;
Это пример vCard:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
BEGIN:VCARD&lt;br /&gt;
VERSION:3.0&lt;br /&gt;
N:Çelik;Tantek&lt;br /&gt;
FN:Tantek Çelik&lt;br /&gt;
URL:http://tantek.com/&lt;br /&gt;
END:VCARD&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
и эквивалент вышеприведённого vCard в разметке hCard: &amp;lt;!-- NOTE_TRANS:  See [[hcard-example1-steps| hCard Example 1]] for the derivation.  --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
	&amp;lt;a class=&amp;quot;url fn&amp;quot; href=&amp;quot;http://tantek.com/&amp;quot;&amp;gt;Tantek Çelik&amp;lt;/a&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Этот hCard будет отображён следующим образом:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;border: thin dashed black; width: 95%; padding: .5em 1em;&amp;quot;&amp;gt;&lt;br /&gt;
[http://tantek.com/ Tantek Çelik]&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''Замечание: информацию о версии не обязательно указывать в разметке hCard, так как эта информация будет включена в профиль hCard,  который будет использован путём утилизации атрибута '''profile''' в HTML-элементе '''head'''.''&lt;br /&gt;
&lt;br /&gt;
=== Пример ===&lt;br /&gt;
&lt;br /&gt;
Информация о связи с компанией [http://www.commerce.net/ Commercenet]. Данный мимкроформат уже сейчас можно определить на этой странице с помощью различных утилит. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;fn org&amp;quot;&amp;gt;'''CommerceNet'''&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;url&amp;quot;&amp;gt;'''&amp;lt;nowiki&amp;gt;http://www.commerce.net/&amp;lt;/nowiki&amp;gt;'''&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;adr&amp;quot;&amp;gt;'''&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Work&amp;lt;/span&amp;gt;:'''&lt;br /&gt;
&amp;lt;div class=&amp;quot;street-address&amp;quot;&amp;gt;'''169 University Avenue'''&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;locality&amp;quot;&amp;gt;'''Palo Alto'''&amp;lt;/span&amp;gt;, &amp;lt;span class=&amp;quot;region&amp;quot;&amp;gt;'''CA'''&amp;lt;/span&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;span class=&amp;quot;postal-code&amp;quot;&amp;gt;'''94301'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;country-name&amp;quot;&amp;gt;'''USA'''&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;tel&amp;quot;&amp;gt;'''&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Work&amp;lt;/span&amp;gt; +1-650-289-4040'''&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;tel&amp;quot;&amp;gt;'''&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Fax&amp;lt;/span&amp;gt; +1-650-289-4041'''&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div&amp;gt;'''Email &amp;lt;span class=&amp;quot;email&amp;quot;&amp;gt;&amp;lt;nowiki&amp;gt;info@commerce.net&amp;lt;/nowiki&amp;gt;&amp;lt;/span&amp;gt;'''&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Ниже представлена разметка с некоторыми семантическими улучшениями:&lt;br /&gt;
* &amp;lt;code&amp;gt;abbr&amp;lt;/code&amp;gt; используется для аббревиатур&lt;br /&gt;
* Имя организации представлено в виде ссылки&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;a class=&amp;quot;fn org url&amp;quot; href=&amp;quot;http://www.commerce.net/&amp;quot;&amp;gt;CommerceNet&amp;lt;/a&amp;gt;&lt;br /&gt;
  &amp;lt;div class=&amp;quot;adr&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Work&amp;lt;/span&amp;gt;:&lt;br /&gt;
    &amp;lt;div class=&amp;quot;street-address&amp;quot;&amp;gt;169 University Avenue&amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;span class=&amp;quot;locality&amp;quot;&amp;gt;Palo Alto&amp;lt;/span&amp;gt;,  &lt;br /&gt;
    &amp;lt;abbr class=&amp;quot;region&amp;quot; title=&amp;quot;California&amp;quot;&amp;gt;CA&amp;lt;/abbr&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&lt;br /&gt;
    &amp;lt;span class=&amp;quot;postal-code&amp;quot;&amp;gt;94301&amp;lt;/span&amp;gt;&lt;br /&gt;
    &amp;lt;div class=&amp;quot;country-name&amp;quot;&amp;gt;USA&amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;div class=&amp;quot;tel&amp;quot;&amp;gt;&lt;br /&gt;
   &amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Work&amp;lt;/span&amp;gt; +1-650-289-4040&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;div class=&amp;quot;tel&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Fax&amp;lt;/span&amp;gt; +1-650-289-4041&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;div&amp;gt;Email: &lt;br /&gt;
   &amp;lt;span class=&amp;quot;email&amp;quot;&amp;gt;info@commerce.net&amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Дополнительные примеры ===&lt;br /&gt;
Дополнительные примеры вы найдёте на странице [[hcard-examples-ru|примеров hCard]]. Там также представлены примеры конвертированных из vCard hCard.&lt;br /&gt;
&lt;br /&gt;
== Кнопки ==&lt;br /&gt;
Вы можете использовать следующие кнопки на вашей странице вместе с микроформатом hCard: &amp;lt;!-- [[buttons#hCard]] --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* http://www.davidjanes.com/images/mf_hcard.png&lt;br /&gt;
* http://rbach.priv.at/2006/buttons/hcard.png&lt;br /&gt;
* http://www.boogdesign.com/images/buttons/microformat_hcard.png&lt;br /&gt;
&amp;lt;!-- * CSS-powered button, as evidenced at [http://re-run.com/about/microformat-badges microformat badges @ re-run] --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Примеры в сети ==&lt;br /&gt;
Данный раздел является информативным. Количество примеров в сети очень большое, поэтому было решено переместить их на [[hcard-examples-in-wild-ru|отдельную страницу]]&lt;br /&gt;
&lt;br /&gt;
== Реализации ==&lt;br /&gt;
Данный раздел является информативным. &lt;br /&gt;
&lt;br /&gt;
См. [[hcard-implementations-ru|реализации]].&lt;br /&gt;
&lt;br /&gt;
== Ссылки ==&lt;br /&gt;
=== Нормативные ===&lt;br /&gt;
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]&lt;br /&gt;
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC 2426]&lt;br /&gt;
* [http://www.itu.int/rec/T-REC-E.123-200102-I/en Рекомендации ITU E.123] по записи телефонных номеров&lt;br /&gt;
* [[rfc-2119-ru|RFC 2119]]&lt;br /&gt;
&lt;br /&gt;
=== Информативные ===&lt;br /&gt;
* [[hcard-history-ru|История hCard]]&lt;br /&gt;
** [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats Презентация «Simple Semantic Formats» на FOO Camp 2004 (10 сентября 2004)]&lt;br /&gt;
** [http://tantek.com/log/2004/09.html#hcard Введение термина hCard (30 сентября 2004)]&lt;br /&gt;
** Некоторые материалы взяты с [http://developers.technorati.com/wiki/hCard Technorati Wiki для разработчиков]&lt;br /&gt;
* [http://www.dante.net/np/ds/osi/9594-6-X.520.A4.ps X.520 в Postscript] ([http://72.14.253.104/search?q=cache:FjqzsFu4h20J:www.dante.net/np/ds/osi/9594-6-X.520.A4.ps Google Cached материал]) - информация об свойстве ROLE.&lt;br /&gt;
* [http://www.w3.org/2002/12/cal/rfc2426 HTML-версия RFC 2426]&lt;br /&gt;
* [http://w3.org/TR/REC-CSS1 CSS1]&lt;br /&gt;
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]&lt;br /&gt;
* [http://en.wikipedia.org/wiki/E.123 Статья в Wikipedia о рекоменациях ITU-T по E.123] - для значений &amp;quot;TEL&amp;quot;.&lt;br /&gt;
* [http://www.imc.org/pdi/ vCard и vCalendar (Internet Mail Consortium)]&lt;br /&gt;
* [[iso-8601|ISO 8601]]&lt;br /&gt;
&lt;br /&gt;
==== Спецификации, связанные с hCard ====&lt;br /&gt;
* [[adr-ru|adr]]&lt;br /&gt;
* [[geo-ru|geo]]&lt;br /&gt;
* [[hcalendar-ru|hCalendar]]&lt;br /&gt;
* [[hreview-ru|hReview]]&lt;br /&gt;
&lt;br /&gt;
==== Подобные работы ====&lt;br /&gt;
* [http://www.intertwingly.net/wiki/pie/PaceBetterPersonElement Atom PaceBetterPersonElement]&lt;br /&gt;
* [http://www.jabber.org/jeps/jep-0054.html JEP-0054: vcard-temp]&lt;br /&gt;
&lt;br /&gt;
==== Идея ====&lt;br /&gt;
Спасибо моему хорошему другу [http://vadim.com/ Вадиму], который познакомил меня с vCard ''много'' лет назад. Если бы я был более внимательным, то многим людям не пришлось бы тратить своё время, изобретая колесо.&lt;br /&gt;
&lt;br /&gt;
==== Создание форматов на основе hCard ====&lt;br /&gt;
''Данный раздел является информативным.''&lt;br /&gt;
&lt;br /&gt;
См. [[hcard-design-methodology-ru|методологию дизайна hCard]].&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
=== More Semantic Equivalents ===&lt;br /&gt;
For some properties there are HTML elements which better match and convey their semantics.  The following properties SHOULD be encoded with the following HTML:&lt;br /&gt;
* &amp;lt;code&amp;gt;URL&amp;lt;/code&amp;gt; in vCard becomes  &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 &amp;lt;code&amp;gt;class=&amp;quot;vcard&amp;quot;&amp;lt;/code&amp;gt; in hCard.&lt;br /&gt;
* Similarly, &amp;lt;code&amp;gt;EMAIL&amp;lt;/code&amp;gt; in vCard becomes &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;
* &amp;lt;code&amp;gt;PHOTO&amp;lt;/code&amp;gt; in vCard becomes &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; or &amp;lt;code&amp;gt;&amp;lt;object class=&amp;quot;photo&amp;quot; data=&amp;quot;...&amp;quot; type=&amp;quot;...&amp;quot;&amp;gt;Photo of ...&amp;lt;/object&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
* &amp;lt;code&amp;gt;UID&amp;lt;/code&amp;gt; in vCard simply becomes another semantic applied to a specific URL (or EMAIL) for an hCard.&lt;br /&gt;
&lt;br /&gt;
=== Singular and Plural derivations ===&lt;br /&gt;
The [[hcard#Singular_vs._Plural_Properties|lists of singular and plural properties]] have been derived by analyzing the semantics of the individual properties in vCard RFC2426 and determining logically that they MUST be singular per their semantics.  See [[hcard-singular-properties]] for explanations.&lt;br /&gt;
&lt;br /&gt;
==== Plural Properties Singularized ====&lt;br /&gt;
Since plural property names become their singular equivalents, even if the original plural property permitted only a single value with multiple components, those multiple components are represented each with their own singularly named property and the the property is effectively multivalued and subject to the above treatment of multivalued properties.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
== Информация для ознакомления ==&lt;br /&gt;
* [http://www.digital-web.com/articles/microformats_primer/ Digital Web Magazine: Microformats Primer] by Garrett Dimon has a good intro to hCard&lt;br /&gt;
* [http://24ways.org/advent/practical-microformats-with-hcard Practical Microformats with hCard] by Drew McLellan&lt;br /&gt;
* [http://www.naturalsearchblog.com/archives/2006/09/28/tips-for-local-search-engine-optimization-for-your-site/ Local Search Engine Optimization using Microformats] by Chris Silver Smith&lt;br /&gt;
* [http://thedredge.org/ Andrew D. Hume] has written a blog post on [http://usabletype.com/articles/2005/usable-microformats/ usable microformats] which discusses hCard&lt;br /&gt;
* [http://www.thefutureoftheweb.com/blog/2006/1/hcard Jesse Skinner's introduction to hCard]&lt;br /&gt;
* [http://blog.usweb.com/ Shaun Shull's] great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], including his [[hcard|hCard]] as an example.&lt;br /&gt;
* [http://24ways.org/2006/styling-hcards-with-css 24 Ways: Styling hCards with CSS] A 24 Ways article - John Allsopp on styling hCard using CSS &lt;br /&gt;
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page] and the [http://technorati.com/tags/hcard hCard tag]&lt;br /&gt;
* [http://www.rfc-editor.org/rfc/rfc4770.txt &amp;lt;nowiki&amp;gt;RFC 4770&amp;lt;/nowiki&amp;gt; Extensions for Instant Messaging]&lt;br /&gt;
* [http://ungeekdapo.wordpress.com/2008/04/30/a-real-life-use-case-of-microformat-hcard-in-action/ A real life use case of Microformat hCard in action] by Bob Ngu&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- == См. также ==&lt;br /&gt;
{{hcard-related-pages}}&lt;br /&gt;
--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Alik</name></author>
	</entry>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=include-pattern&amp;diff=43042</id>
		<title>include-pattern</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=include-pattern&amp;diff=43042"/>
		<updated>2010-09-05T20:38:50Z</updated>

		<summary type="html">&lt;p&gt;Alik: Syntax highlighting&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt;Include Pattern&amp;lt;/h1&amp;gt;&lt;br /&gt;
{{TOC-right}}&lt;br /&gt;
The include pattern is a microformat design pattern, providing a mechanism to include a portion of data from one area of a page into another area of the same page, allowing the data to be reused by multiple microformats, independent of content order, without repeating all the information. The following is documentation for re-use of the pattern in other microformats, and for publishers working with it.&lt;br /&gt;
&lt;br /&gt;
;Editors: Tantek Celik&lt;br /&gt;
: Ben Ward&lt;br /&gt;
&lt;br /&gt;
== background ==&lt;br /&gt;
&lt;br /&gt;
[[hresume|hResume]] needed the ability to include a name from one hCard at the top of a resume — the person's contact details — into the separate hCards used in the same person's employment history. Repeating name information would not have matched the existing publishing practices used in Resumes and Curriculum Vit?, would be inconvenient to publishers, and irritating to consumers. The include pattern is a mechanism to reference data from the same page, avoiding repetition, or duplicate visible information.&lt;br /&gt;
&lt;br /&gt;
== scope ==&lt;br /&gt;
&lt;br /&gt;
The include pattern is strictly limited to the scope of the current page. It cannot be used to include content from other URLs.&lt;br /&gt;
&lt;br /&gt;
== quick reference==&lt;br /&gt;
&lt;br /&gt;
The include-pattern is a mechanism to include content from one microformat into another microformat elsewhere in the same document, using hyperlinks or &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt;. For example:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&amp;lt;a class=&amp;quot;include&amp;quot; href=&amp;quot;#author&amp;quot;&amp;gt;James Levine&amp;lt;/a&amp;gt;&amp;lt;/source&amp;gt;&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&amp;lt;object class=&amp;quot;include&amp;quot; data=&amp;quot;#author&amp;quot;&amp;gt;&amp;lt;/object&amp;gt;&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In specifications which cite the include-pattern, either of the above code snippets {{must}} cause a microformats parser to replace the &amp;lt;code&amp;gt;A&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt; element with class name &amp;quot;include&amp;quot; with the content fragment with ID &amp;quot;author&amp;quot;. Full examples follow.&lt;br /&gt;
&lt;br /&gt;
== in general==&lt;br /&gt;
&lt;br /&gt;
To reference includes, use an include element with class name &amp;quot;include&amp;quot; and a document fragment identifier. The content to be included should have an ID attribute set, and that ID should be referenced from the HREF or DATA attribute at the point of inclusion.&lt;br /&gt;
&lt;br /&gt;
The include element with class name &amp;quot;include&amp;quot; indicates a reference to a sub-tree elsewhere in the document which {{must}} be included in-place by microformat parsers. That is, the element with class &amp;quot;include&amp;quot; is _replaced_ in the DOM by the referenced sub-tree. Note that this means all other class names on the include element are discarded. Microformat class names should be included on the target of the include, not on the include element itself.&lt;br /&gt;
&lt;br /&gt;
To prevent infinite loops, if a class=&amp;quot;include&amp;quot; refers to itself or to an ancestor in the parse tree, then it is ignored and has no effect on the parser.&lt;br /&gt;
&lt;br /&gt;
Per the [[include-pattern#Scope|scope]], the &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt; 'data' attribute and hyperlink 'href' attribute {{must}} be local ID references when used as include pattern instances. External references (requiring a consuming application to load an external resource) are not supported by this method.&lt;br /&gt;
&lt;br /&gt;
There are two HTML elements available to reference includes, hyperlink/Anchor and &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt;. They are documented below.&lt;br /&gt;
&lt;br /&gt;
These methods of property indirection via a hyperlink element can apply to any/all properties in class-based microformats, but should only be used where a microformat explicitly states that the include-pattern is a dependency. For example, [[XOXO]] does not reference the include-pattern at this time, so sub-trees cannot be included by reference in XOXO. [[hResume]] and [[hReview]] do reference the include pattern.&lt;br /&gt;
&lt;br /&gt;
=== Hyperlink ===&lt;br /&gt;
&lt;br /&gt;
The recommended way to reference includes within microformats is to use a hyperlink.&lt;br /&gt;
&lt;br /&gt;
==== Hyperlink example====&lt;br /&gt;
&lt;br /&gt;
Here is an [[hcard|hCard]] for a bar, included at the top of a reviews page, shown here as a verbose hCard.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;vcard&amp;quot; id=&amp;quot;bricklayers-card&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;div class=&amp;quot;fn org&amp;quot;&amp;gt;The Bricklayers Arms&amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;div class=&amp;quot;adr&amp;quot;&amp;gt;&lt;br /&gt;
     &amp;lt;span class=&amp;quot;street-address&amp;quot;&amp;gt;31 Gresse Street&amp;lt;/span&amp;gt;,&lt;br /&gt;
     &amp;lt;span class=&amp;quot;locality&amp;quot;&amp;gt;Fitzrovia&amp;lt;/span&amp;gt;&lt;br /&gt;
     &amp;lt;span class=&amp;quot;region&amp;quot;&amp;gt;London&amp;lt;/span&amp;gt;&lt;br /&gt;
     &amp;lt;span class=&amp;quot;postal-code&amp;quot;&amp;gt;W1T 1QS&amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Elsewhere on the page, a number of reviews reference the hcard in the item property. Rather than repeat all the verbose detail, only the name is reprinted and the detailed hcard referenced using the include-pattern.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;hreview&amp;quot;&amp;gt;&lt;br /&gt;
   &amp;lt;h1 class=&amp;quot;summary&amp;quot;&amp;gt;A great venue for monthly gatherings!&amp;lt;/h1&amp;gt;&lt;br /&gt;
   &amp;lt;div class=&amp;quot;item&amp;quot;&amp;gt;&amp;lt;a class=&amp;quot;include&amp;quot; href=&amp;quot;#bricklayers-card&amp;quot;&amp;gt;The Bricklayers Arms&amp;lt;/a&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
   &amp;lt;p class=&amp;quot;description&amp;quot;&amp;gt;Wonderful pub, cheap beer, open fire to warm mince pies at Christmas.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;hreview&amp;quot;&amp;gt;&lt;br /&gt;
   &amp;lt;h1 class=&amp;quot;summary&amp;quot;&amp;gt;Takes a while to thin out, but!&amp;lt;/h1&amp;gt;&lt;br /&gt;
   &amp;lt;div class=&amp;quot;item&amp;quot;&amp;gt;&amp;lt;a class=&amp;quot;include&amp;quot; href=&amp;quot;#bricklayers-card&amp;quot;&amp;gt;The Bricklayers Arms&amp;lt;/a&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
   &amp;lt;p class=&amp;quot;rating&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt;5&amp;lt;/span&amp;gt;/&amp;lt;span class=&amp;quot;best&amp;quot;&amp;gt;5&amp;lt;/span&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Note that you {{must}} include content within the anchor element. See the notes and issues below.&lt;br /&gt;
&lt;br /&gt;
A microformat parser {{must}} treat each review as follows, with the hyperlink include element completely replaced (including inner-text) by the sub-tree that was referenced:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;hreview&amp;quot;&amp;gt;&lt;br /&gt;
   &amp;lt;h1 class=&amp;quot;summary&amp;quot;&amp;gt;A great venue for monthly gatherings!&amp;lt;/h1&amp;gt;&lt;br /&gt;
   &amp;lt;div class=&amp;quot;item&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;div class=&amp;quot;vcard&amp;quot; id=&amp;quot;bricklayers-card&amp;quot;&amp;gt;&lt;br /&gt;
        &amp;lt;div class=&amp;quot;fn org&amp;quot;&amp;gt;The Bricklayers Arms&amp;lt;/div&amp;gt;&lt;br /&gt;
        &amp;lt;div class=&amp;quot;adr&amp;quot;&amp;gt;&lt;br /&gt;
           &amp;lt;span class=&amp;quot;street-address&amp;quot;&amp;gt;31 Gresse Street&amp;lt;/span&amp;gt;,&lt;br /&gt;
           &amp;lt;span class=&amp;quot;locality&amp;quot;&amp;gt;Fitzrovia&amp;lt;/span&amp;gt;&lt;br /&gt;
           &amp;lt;span class=&amp;quot;region&amp;quot;&amp;gt;London&amp;lt;/span&amp;gt;&lt;br /&gt;
           &amp;lt;span class=&amp;quot;postal-code&amp;quot;&amp;gt;W1T 1QS&amp;lt;/span&amp;gt;&lt;br /&gt;
        &amp;lt;/div&amp;gt;&lt;br /&gt;
      &amp;lt;/div&amp;gt;&lt;br /&gt;
   &amp;lt;/div&amp;gt;&lt;br /&gt;
   &amp;lt;p class=&amp;quot;description&amp;quot;&amp;gt;Wonderful pub, cheap beer, open fire to warm mince pies at Christmas.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/source&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== notes and issues ====&lt;br /&gt;
&lt;br /&gt;
Note: The &amp;lt;code&amp;gt;id&amp;lt;/code&amp;gt; attribute value in the example &amp;quot;bricklayers-card&amp;quot; was chosen for demonstration purposes. The text of the value has no semantic per the include-pattern other than to connect the source of the include to the destination. Authors {{should}} use good [[POSH]] techniques to choose &amp;lt;code&amp;gt;id&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;class&amp;lt;/code&amp;gt; names.&lt;br /&gt;
&lt;br /&gt;
Authors {{must}} supply content text for the hyperlink itself. This can require repeating a small piece of information (such as a person's name in an hcard), or including generic text as appropriate to the context of the page. &lt;br /&gt;
&lt;br /&gt;
===== accessibility =====&lt;br /&gt;
&lt;br /&gt;
* Testing indicates that the only way to guarantee accessibility of hyperlinks to users of assistive technology (such as screen readers) is to include inner-text. [http://yuiblog.com/blog/2008/01/23/empty-links/ See: Empty Links and Screen Readers]&lt;br /&gt;
* You {{must}} include inner-text in the hyperlink element.&lt;br /&gt;
* You MAY enhance the rendered user experience (depending on the context of your page) by hiding the include element using CSS &amp;lt;code&amp;gt;display: none&amp;lt;/code&amp;gt;&lt;br /&gt;
* Where you wish to hide the content of the include element, you {{should not}} hide the include element using a CSS negative margin offset as the hidden link will remain in the tab order of the document. Use &amp;lt;code&amp;gt;display: none&amp;lt;/code&amp;gt; instead.&lt;br /&gt;
&lt;br /&gt;
Where a publishing constraint prevents putting content within the include-pattern, you {{must}} use the &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt; element pattern instead of a hyperlink.&lt;br /&gt;
&lt;br /&gt;
=== Object ===&lt;br /&gt;
&lt;br /&gt;
The Object Include Pattern is semantically superior to the Hyperlink Include; it is being used to embed content into the page. The &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt; element based include was the original developed include pattern. However, there are some browser compatibility issues that can affect some implementation scenarios and thus the above Hyperlink Include Pattern is preferred.&lt;br /&gt;
&lt;br /&gt;
==== Object example ====&lt;br /&gt;
&lt;br /&gt;
The [[hcard|hCard]] from the beginning of a resume describes the person who's resume it is:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;fn n&amp;quot; id=&amp;quot;james-hcard-name&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;span class=&amp;quot;given-name&amp;quot;&amp;gt;James&amp;lt;/span&amp;gt; &amp;lt;span class=&amp;quot;family-name&amp;quot;&amp;gt;Levine&amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Elsewhere on the page, a second hCard, with employer information, re-uses the &amp;quot;fn n&amp;quot; content from the first hCard:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;object class=&amp;quot;include&amp;quot; data=&amp;quot;#james-hcard-name&amp;quot;&amp;gt;&amp;lt;/object&amp;gt;&lt;br /&gt;
 &amp;lt;span class=&amp;quot;org&amp;quot;&amp;gt;SimplyHired&amp;lt;/span&amp;gt;&lt;br /&gt;
 &amp;lt;span class=&amp;quot;title&amp;quot;&amp;gt;Microformat Brainstormer&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt; &lt;br /&gt;
&lt;br /&gt;
A microformat parser {{must}} treat the second hCard as follows, with the &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt; include element completely replaced by the sub-tree that it referenced:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;fn n&amp;quot; id=&amp;quot;james-hcard-name&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;span class=&amp;quot;given-name&amp;quot;&amp;gt;James&amp;lt;/span&amp;gt; &amp;lt;span class=&amp;quot;family-name&amp;quot;&amp;gt;Levine&amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;org&amp;quot;&amp;gt;SimplyHired&amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;title&amp;quot;&amp;gt;Microformat Brainstormer&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This method of hCard property indirection via an object element can apply to any/all properties in class-based microformats.&lt;br /&gt;
&lt;br /&gt;
=== notes and issues===&lt;br /&gt;
&lt;br /&gt;
* Unlike the hyperlink pattern, the &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt; is not believed to cause problems in assistive technology when fallback text is absent. ('''research needed''')&lt;br /&gt;
* Apple's Safari 1.x browser has some rendering issues with this use of &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt;: Publishers {{should}} style a width and height of &amp;quot;0&amp;quot; for the include elements to resolve this ('''clarification of issue needed''').&lt;br /&gt;
* Bugs have been reported in some web browsers (Internet Explorer, Safari, Firefox) that &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt; elements referencing fragments of the same document erroneously cause the browser to make additional HTTP requests ('''version(s) affected needed'''). For scenarios where HTTP requests are a performance issue, publishers {{should}} use the hyperlink pattern instead.&lt;br /&gt;
* Versions of Microsoft Internet Explorer with ActiveX controls disabled will throw a warning prompt upon finding an &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt; element ('''version(s) affected needed''').&lt;br /&gt;
&lt;br /&gt;
== acknowledgements ==&lt;br /&gt;
&lt;br /&gt;
Thanks to discussions and brainstorms with a bunch of folks: [http://theryanking.com/ Ryan King], James Levine, the whole crowd at the [http://mashupcamp.com/index.cgi?HAtomFinalization Microformats specifications working session] at MashupCamp, [http://suda.co.uk/ Brian Suda], [http://randomchaos.com/ Scott Reynen], [http://allinthehead.com/ Drew McLellan]. Thanks to [http://www.isolani.co.uk/ Mike Davies] for accessibility research.&lt;br /&gt;
&lt;br /&gt;
== specifications using ==&lt;br /&gt;
* [[hresume|hResume]]&lt;br /&gt;
* [[hreview|hReview]]&lt;br /&gt;
&lt;br /&gt;
=== considering ===&lt;br /&gt;
All class-based microformats {{should}} consider using and explicitly normatively stating support for the include pattern.&lt;br /&gt;
* [[hatom|hAtom]]&lt;br /&gt;
* [[hcalendar|hCalendar]]&lt;br /&gt;
* [[hcard|hCard]]&lt;br /&gt;
&lt;br /&gt;
== implementations ==&lt;br /&gt;
* X2V implements the [[include-pattern]] when parsing [[hcard|hCards]] and [[hcalendar|hCalendars]] for both object.include and a.include.&lt;br /&gt;
&lt;br /&gt;
== references ==&lt;br /&gt;
&lt;br /&gt;
=== normative ===&lt;br /&gt;
* HTML 4.01&lt;br /&gt;
&lt;br /&gt;
=== informative ===&lt;br /&gt;
* [[hcard|hCard]]&lt;br /&gt;
* [[hresume|hResume]]&lt;br /&gt;
* XHTML 1.0&lt;br /&gt;
&lt;br /&gt;
== related pages==&lt;br /&gt;
{{include-pattern-related-pages}}&lt;br /&gt;
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].&lt;/div&gt;</summary>
		<author><name>Alik</name></author>
	</entry>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=hnews&amp;diff=43041</id>
		<title>hnews</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=hnews&amp;diff=43041"/>
		<updated>2010-09-05T20:37:40Z</updated>

		<summary type="html">&lt;p&gt;Alik: Syntax highlighting&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;entry-title&amp;gt;hNews 0.1&amp;lt;/entry-title&amp;gt;&lt;br /&gt;
{{Template:DraftSpecification}}&lt;br /&gt;
&lt;br /&gt;
hNews is a microformat for news content. hNews extends [http://microformats.org/wiki/hatom hAtom], introducing a number of fields that more completely describe a journalistic work. hNews also introduces another data format, [[rel-principles]], a format that describes the journalistic principles upheld by the journalist or news organization that has published the news item. hNews will be one of several open standards.&lt;br /&gt;
__TOC__&lt;br /&gt;
== Draft Specification ==&lt;br /&gt;
&lt;br /&gt;
;Editor/Author&lt;br /&gt;
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])&lt;br /&gt;
&lt;br /&gt;
;Contributors&lt;br /&gt;
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press]) &lt;br /&gt;
:[[:User:Martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])&lt;br /&gt;
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])&lt;br /&gt;
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])&lt;br /&gt;
&lt;br /&gt;
=== Copyright ===&lt;br /&gt;
Per the public domain release on the authors' user pages ([[:User:JonathanMalek|Jonathan Malek]]) this specification is released into the public domain. &lt;br /&gt;
&lt;br /&gt;
{{MicroFormatPublicDomainContributionStatement}}&lt;br /&gt;
&lt;br /&gt;
=== Patents ===&lt;br /&gt;
{{MicroFormatPatentStatement}}&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
hNews is a microformat for identifying semantic information in news stories. It builds on [[hAtom]], while adding a number of fields that more completely define a journalistic work. hNews can be thought of as inheriting from [[hAtom]], since parsers and tools that do not understand the hNews extensions can still parse the [[hAtom]] content. However, those parsers and applications that understand hNews can enable a richer set of semantic actions on news stories.&lt;br /&gt;
&lt;br /&gt;
{{rfc-2119-intro}}&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;
hNews extends hAtom. As the hAtom draft format notes, &amp;quot;Atom provides a lot more functionality than we need for a 'blog post' microformat, so we've taken the minimal number of elements needed.&amp;quot; News stories typically introduce more fields (for instance, the publishing organization) than the current 0.1 draft of hAtom, and those fields are very important when reading or evaluating a news story. We focus on those fields that enable the development of semantic actions around news: license, principles, dateline (geo) and source organization.&lt;br /&gt;
&lt;br /&gt;
=== Schema ===&lt;br /&gt;
The hNews schema consists of the following: &lt;br /&gt;
&lt;br /&gt;
* hNews ('''&amp;lt;code&amp;gt;hnews&amp;lt;/code&amp;gt;''') and '''&amp;lt;code&amp;gt;hentry&amp;lt;/code&amp;gt;'''.  required. Using [[hAtom]].&lt;br /&gt;
** '''&amp;lt;code&amp;gt;source-org&amp;lt;/code&amp;gt;'''. required. Using [[hCard]].[*]&lt;br /&gt;
** '''&amp;lt;code&amp;gt;dateline&amp;lt;/code&amp;gt;'''. optional. Using text or [[hCard]].&lt;br /&gt;
** '''&amp;lt;code&amp;gt;geo&amp;lt;/code&amp;gt;'''. optional. Using [[geo]].[*]&lt;br /&gt;
** '''&amp;lt;code&amp;gt;item-license&amp;lt;/code&amp;gt;'''. recommended. Using a [[licensing-brainstorming#item_as_container|brainstorm proposal]].&lt;br /&gt;
** '''&amp;lt;code&amp;gt;principles&amp;lt;/code&amp;gt;'''. recommended. Using the draft microformat [[principles-brainstorming#rel-principles_specification|rel-principles]].&lt;br /&gt;
&lt;br /&gt;
[*] Some required elements have defaults if missing, see below.&lt;br /&gt;
&lt;br /&gt;
=== Field and Element Details ===&lt;br /&gt;
&lt;br /&gt;
==== hAtom Fields ====&lt;br /&gt;
&lt;br /&gt;
===== Entry =====&lt;br /&gt;
* an hNews story {{must}} be encoded as an [[hAtom]] &amp;lt;code&amp;gt;hentry&amp;lt;/code&amp;gt;.&lt;br /&gt;
* if an hNews story cannot be parsed as an [[hAtom]] &amp;lt;code&amp;gt;hentry&amp;lt;/code&amp;gt;, it is invalid hNews.&lt;br /&gt;
&lt;br /&gt;
==== Additional Fields ====&lt;br /&gt;
&lt;br /&gt;
===== Source Organization =====&lt;br /&gt;
* a Source Organization element is identified by the class name &amp;lt;code&amp;gt;source-org&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Source Organization represents the originating organization for the news story.&lt;br /&gt;
* a Source Organization {{must}} be encoded in an [[hCard]].&lt;br /&gt;
* if the Source Organization is missing &lt;br /&gt;
** find the [[algorithm-nearest-in-parent]] element(s) with class name &amp;lt;code&amp;gt;source-org&amp;lt;/code&amp;gt; and that is/are a valid [[hCard]]&lt;br /&gt;
** otherwise the entry is invalid hNews&lt;br /&gt;
&lt;br /&gt;
===== Dateline =====&lt;br /&gt;
* a dateline element is identified by the class name &amp;lt;code&amp;gt;dateline&amp;lt;/code&amp;gt;.&lt;br /&gt;
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).&lt;br /&gt;
* a dateline element {{may}} be encoded in an [[hCard]].&lt;br /&gt;
* a news story {{should}} have a dateline element.&lt;br /&gt;
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.&lt;br /&gt;
&lt;br /&gt;
===== Geo =====&lt;br /&gt;
* a geo element is identified by the class name &amp;lt;code&amp;gt;geo&amp;lt;/code&amp;gt;&lt;br /&gt;
* geo represents the geographic coordinates of relevant locations in the news story.&lt;br /&gt;
* a geo element should be encoded in a [[geo]].&lt;br /&gt;
* in those cases where the latitude and longitude represent the dateline, a variant of [[geo]] should be used (see [http://microformats.org/wiki/geo-brainstorming#Geo_improvements Geo Improvements] for an example).&lt;br /&gt;
&lt;br /&gt;
===== License =====&lt;br /&gt;
* a license element is identified by the rel value of &amp;lt;code&amp;gt;item-license&amp;lt;/code&amp;gt;.&lt;br /&gt;
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].&lt;br /&gt;
* a news story {{should}} include a license element.&lt;br /&gt;
&lt;br /&gt;
===== Principles =====&lt;br /&gt;
* a principles element is identified by &amp;lt;code&amp;gt;rel-principles&amp;lt;/code&amp;gt;.&lt;br /&gt;
* principles represents the statement of principles and ethics used by the news organization that produced the news story.&lt;br /&gt;
* a principles element {{must}} be encoded in [[principles-brainstorming#rel-principles_specification|rel-principles]].&lt;br /&gt;
* a news story {{should}} include principles.&lt;br /&gt;
* principles {{should}} be linked to using the icons http://labs.ap.org/principles-button-blue.png or http://labs.ap.org/principles-book-blue.png.&lt;br /&gt;
&lt;br /&gt;
=== XMDP Profile ===&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;dl class=&amp;quot;profile&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;dt&amp;gt;class&amp;lt;/dt&amp;gt;&lt;br /&gt;
  &amp;lt;dd&amp;gt;&lt;br /&gt;
    &amp;lt;p&amp;gt;&amp;lt;a rel=&amp;quot;help&amp;quot; href=&amp;quot;http://www.w3.org/TR/html401/struct/global.html#adef-class&amp;quot;&amp;gt;&lt;br /&gt;
    HTML4 definition of the 'class' attribute.&amp;lt;/a&amp;gt;&lt;br /&gt;
    This meta data profile defines some 'class' attribute values (class names) &lt;br /&gt;
    and their meanings as suggested by a &lt;br /&gt;
    &amp;lt;a href=&amp;quot;http://www.w3.org/TR/WD-htmllink-970328#profile&amp;quot;&amp;gt;draft of&lt;br /&gt;
    &amp;quot;Hypertext Links in HTML&amp;quot;&amp;lt;/a&amp;gt;.&amp;lt;/p&amp;gt;&lt;br /&gt;
    &amp;lt;dl&amp;gt;&lt;br /&gt;
&lt;br /&gt;
      &amp;lt;dt&amp;gt;hnews&amp;lt;/dt&amp;gt;&lt;br /&gt;
      &amp;lt;dd&amp;gt;Used to describe semantic information associated with news stories.&amp;lt;/dd&amp;gt;&lt;br /&gt;
&lt;br /&gt;
      &amp;lt;dt&amp;gt;source-org&amp;lt;/dt&amp;gt;&lt;br /&gt;
      &amp;lt;dd&amp;gt;The originating organization for the news story.&amp;lt;/dd&amp;gt;&lt;br /&gt;
&lt;br /&gt;
      &amp;lt;dt&amp;gt;dateline&amp;lt;/dt&amp;gt;&lt;br /&gt;
      &amp;lt;dd&amp;gt;Represents the location where the news story was filed.&amp;lt;/dd&amp;gt;&lt;br /&gt;
&lt;br /&gt;
      &amp;lt;dt&amp;gt;geo&amp;lt;/dt&amp;gt;&lt;br /&gt;
      &amp;lt;dd&amp;gt;Represents geographic coordinates of relevant locations in the story.&amp;lt;/dd&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;/dl&amp;gt;&lt;br /&gt;
  &amp;lt;/dd&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;dt&amp;gt;rel&amp;lt;/dt&amp;gt;&lt;br /&gt;
  &amp;lt;dd&amp;gt;&lt;br /&gt;
    &amp;lt;dl&amp;gt;&lt;br /&gt;
&lt;br /&gt;
      &amp;lt;dt&amp;gt;item-license&amp;lt;/dt&amp;gt;&lt;br /&gt;
      &amp;lt;dd&amp;gt;Represents the license for the story.&amp;lt;/dd&amp;gt;&lt;br /&gt;
&lt;br /&gt;
      &amp;lt;dt&amp;gt;principles&amp;lt;/dt&amp;gt;&lt;br /&gt;
      &amp;lt;dd&amp;gt;Represents the statement of principles and ethics used by the news organization that produced the news story.&amp;lt;/dd&amp;gt;&lt;br /&gt;
&lt;br /&gt;
      &amp;lt;/dl&amp;gt;&lt;br /&gt;
   &amp;lt;/dd&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/dl&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
&lt;br /&gt;
See [[hnews-examples]].&lt;br /&gt;
&lt;br /&gt;
=== Examples in the wild ===&lt;br /&gt;
&lt;br /&gt;
See [[hnews-examples-in-wild]].&lt;br /&gt;
&lt;br /&gt;
== Implementations ==&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
=== Normative References ===&lt;br /&gt;
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0]&lt;br /&gt;
* [[hatom|hAtom]]&lt;br /&gt;
* [[hcard|hCard]]&lt;br /&gt;
* [http://gmpg.org/xmdp/ XMDP]&lt;br /&gt;
* [[rel-tag]]&lt;br /&gt;
* [[geo]]&lt;br /&gt;
* [[licensing-brainstorming#item_as_container_license|item-license brainstorm]]&lt;br /&gt;
* [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]&lt;br /&gt;
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]&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;
* Other news efforts: see [[news-formats]].&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;
=== Version 0.1 ===&lt;br /&gt;
&lt;br /&gt;
Version 0.1 was drafted August 2008.&lt;br /&gt;
&lt;br /&gt;
== Further Reading ==&lt;br /&gt;
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
* hnews&lt;br /&gt;
* [[news-brainstorming]]: thoughts for improving hNews. &lt;br /&gt;
* [[hnews-faq|hNews FAQ]]: if you have any questions about hNews, check here, and if you don't find answers, add your questions!&lt;br /&gt;
* [[hnews-issues]]: please add any issues with the specification to the issues page.&lt;br /&gt;
* [[news-formats]]: existing news and news management schemas.&lt;br /&gt;
* [[news-examples]]: examples of news formats on the web.&lt;br /&gt;
** [[hnews-examples]]: examples of how to implement hNews.&lt;br /&gt;
&lt;br /&gt;
[[Category:Draft Specifications]]&lt;br /&gt;
[[Category:hNews]]&lt;/div&gt;</summary>
		<author><name>Alik</name></author>
	</entry>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=hresume&amp;diff=43040</id>
		<title>hresume</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=hresume&amp;diff=43040"/>
		<updated>2010-09-05T20:35:19Z</updated>

		<summary type="html">&lt;p&gt;Alik: Syntax highlighting&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;entry-title&amp;gt;hResume&amp;lt;/entry-title&amp;gt;&lt;br /&gt;
{{DraftSpecification}}&lt;br /&gt;
__TOC__&lt;br /&gt;
hResume is a microformat for publishing resumes and CVs. hResume is one of several open microformat standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.&lt;br /&gt;
&lt;br /&gt;
Want to get started with writing an hResume? Use the [http://hresume.weblogswork.com/hresumecreator/ hResume Creator] to create your hResume and publish it, or follow the hResume authoring tips to add hResume markup to your web page or blog. &lt;br /&gt;
&lt;br /&gt;
==Microformats Draft Specification==&lt;br /&gt;
&lt;br /&gt;
; Editor/Author: [http://theryanking.com Ryan King]&lt;br /&gt;
; Acknowledgments: See [http://microformats.org/wiki/hresume#Acknowledgements  acknowledgments].&lt;br /&gt;
&lt;br /&gt;
Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.&lt;br /&gt;
&lt;br /&gt;
{{rfc-2119-intro}}&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
Draft, version 0.1.&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
=== Semantic XHTML Design Principles ===&lt;br /&gt;
{{SemanticXHTMLDesignPrinciples}}&lt;br /&gt;
&lt;br /&gt;
== Format ==&lt;br /&gt;
=== In General ===&lt;br /&gt;
The hResume format is based on a set of fields common to numerous resumes published today on the web.  Where possible field names have been chosen and reused from preexisting microformats.&lt;br /&gt;
&lt;br /&gt;
=== Schema ===&lt;br /&gt;
The hResume schema consists of the following:&lt;br /&gt;
&lt;br /&gt;
* hResume&lt;br /&gt;
** summary. optional. text.&lt;br /&gt;
** contact info. required. {{must}} use [[hcard|hCard]]; {{should}} use &amp;lt;code class=&amp;quot;element&amp;quot;&amp;gt;&amp;amp;lt;address&amp;amp;gt;&amp;lt;/code&amp;gt; + [[hcard|hCard]].&lt;br /&gt;
** experience. optional. One or more [[hcalendar]] events with the class name '&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;experience&amp;lt;/code&amp;gt;', with an embedded [[hcard|hCard]] indicating the job title, name of company, address of company etc.&lt;br /&gt;
** education. optional One or more [[hcalendar]] events with the class name '&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;education&amp;lt;/code&amp;gt;', with an embedded [[hcard|hCard]] indicating the name of school, address of school etc.&lt;br /&gt;
** skills. optional. phrases or keywords using the [[rel-tag]] microformat with the class name '&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;skill&amp;lt;/code&amp;gt;'.&lt;br /&gt;
** affiliations. optional. the class name &amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;affiliation&amp;lt;/code&amp;gt; along with an [[hcard]] of the organization&lt;br /&gt;
** publications. optional. One or more citations. Use cite tag.&lt;br /&gt;
&lt;br /&gt;
=== Field details ===&lt;br /&gt;
The fields of the hResume schema represent the following:&lt;br /&gt;
&lt;br /&gt;
* '''&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;hresume&amp;lt;/code&amp;gt;''':: root class name&lt;br /&gt;
* '''&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;summary&amp;lt;/code&amp;gt;''':: The class name &amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;summary&amp;lt;/code&amp;gt; is used to mark up an overview of qualifications and objectives.&lt;br /&gt;
* '''contact''':: Current contact info in an [[hCard]]; {{should}} use &amp;lt;code class=&amp;quot;element&amp;quot;&amp;gt;&amp;amp;lt;address&amp;amp;gt;&amp;lt;/code&amp;gt; with [[hCard]] when possible.&lt;br /&gt;
* '''&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;education&amp;lt;/code&amp;gt;''':: the class name '&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;education&amp;lt;/code&amp;gt;' is applied to an [[hcalendar]] event.&lt;br /&gt;
* '''&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;experience&amp;lt;/code&amp;gt;''':: the class name '&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;experience&amp;lt;/code&amp;gt;' is applied to an [[hcalendar]] event. Job titles/positions should use an [[hCard]].&lt;br /&gt;
* '''&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;skill&amp;lt;/code&amp;gt;''':: An hResume may be tagged using the [[rel-tag]] microformat and the '&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;skill&amp;lt;/code&amp;gt;' class name.&lt;br /&gt;
* '''&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;affiliation&amp;lt;/code&amp;gt;''':: The class name &amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;affiliation&amp;lt;/code&amp;gt; is used along with an [[hcard]] of the organization&lt;br /&gt;
* '''publications''':: just use &amp;lt;code class=&amp;quot;element&amp;quot;&amp;gt;&amp;amp;lt;cite&amp;amp;gt;&amp;lt;/code&amp;gt;.  When there is a [[citation]] microformat, then that can be used in combination with the cite element to further markup the components of the citation.&lt;br /&gt;
&lt;br /&gt;
=== XMDP Profile ===&lt;br /&gt;
* [[hresume-profile]] (@TODO)&lt;br /&gt;
&lt;br /&gt;
=== Notes ===&lt;br /&gt;
This section is informative.&lt;br /&gt;
&lt;br /&gt;
*...&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
=== Summary ===&lt;br /&gt;
An example summary:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;p class=&amp;quot;summary&amp;quot;&amp;gt;&lt;br /&gt;
  I have 10 years experience with all Web 2.0 technologies– I've been working with Ajax since 1996, &lt;br /&gt;
  designing with pastels while others will still using tiled background images and frames...&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Contact ===&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;address class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;Pedro Sanchez&amp;lt;/span&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;123 Fake St.&amp;lt;/span&amp;gt;&lt;br /&gt;
    &amp;lt;span class=&amp;quot;locality&amp;quot;&amp;gt;Preston&amp;lt;/span&amp;gt;, &amp;lt;span class=&amp;quot;region&amp;quot;&amp;gt;Idaho&amp;lt;/span&amp;gt; &amp;lt;span class=&amp;quot;postal-code&amp;quot;&amp;gt;83263&amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;span&amp;gt;Email: &amp;lt;a class=&amp;quot;email&amp;quot; href=&amp;quot;mailto:joe@example.com&amp;quot;&amp;gt;pedro@vote-for-pedro.com&amp;lt;/a&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;span&amp;gt;Homepage: &amp;lt;a class=&amp;quot;url&amp;quot; href=&amp;quot;http://vote-for-pedro.com/&amp;quot;&amp;gt;vote-for-pedro.com&amp;lt;/a&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;span&amp;gt;Phone: &amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;+01.208.555.4567&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/address&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Education ===&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;ol class=&amp;quot;vcalendar&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;li class=&amp;quot;education vevent&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;a class=&amp;quot;url summary&amp;quot; href=&amp;quot;http://example.edu/&amp;quot;&amp;gt;Preston High School&amp;lt;/a&amp;gt;&lt;br /&gt;
    (&amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;2001-01-24&amp;quot;&amp;gt;2001&amp;lt;/abbr&amp;gt; - &amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;2005-05-25&amp;quot;&amp;gt;2005&amp;lt;/abbr&amp;gt;)&lt;br /&gt;
  &amp;lt;/li&amp;gt;&lt;br /&gt;
  ...&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Experience ===&lt;br /&gt;
==== Basic ====&lt;br /&gt;
A basic experience event:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;ol class=&amp;quot;vcalendar&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;li class=&amp;quot;experience vevent&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;span class=&amp;quot;summary&amp;quot;&amp;gt;President&amp;lt;/span&amp;gt;,&lt;br /&gt;
    &amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt;Preston High School&amp;lt;/span&amp;gt;,&lt;br /&gt;
    &amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;2004-09-01&amp;quot;&amp;gt;May 2004&amp;lt;/abbr&amp;gt; - &amp;lt;abbr title=&amp;quot;2005-05-25&amp;quot;&amp;gt;present&amp;lt;/abbr&amp;gt;&lt;br /&gt;
  &amp;lt;/li&amp;gt;&lt;br /&gt;
  ...&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Job Titles ====&lt;br /&gt;
To express one or more job titles/positions in the same experience event you should use one or more [[hcard|hCard]]s. hCard requires the &amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;fn&amp;lt;/code&amp;gt; (&amp;quot;formatted name&amp;quot;) field, but it isn't customary to repeat your name for every job title you mark up in [[hResume|hresume]]. So, you may use an &amp;lt;code class=&amp;quot;element&amp;quot;&amp;gt;&amp;amp;lt;object&amp;amp;gt;&amp;lt;/code&amp;gt; and the class name '&amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;include&amp;lt;/code&amp;gt;' with a reference to the &amp;lt;code class=&amp;quot;class-name&amp;quot;&amp;gt;fn&amp;lt;/code&amp;gt; somewhere else on the page. &lt;br /&gt;
&lt;br /&gt;
Currently, the recommended way to reference includes within microformats is to use a hyperlink with class=&amp;quot;include&amp;quot;. See [[include-pattern|include-pattern]] for details.&lt;br /&gt;
&lt;br /&gt;
For example, this hCard refers to another hCard:&lt;br /&gt;
&lt;br /&gt;
Using &amp;lt;code&amp;gt;&amp;amp;lt;a&amp;amp;gt;&amp;lt;/code&amp;gt;:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;a href=&amp;quot;#pedro-name&amp;quot; class=&amp;quot;include&amp;quot; title=&amp;quot;Pedro Sanchez&amp;quot;&amp;gt;&amp;lt;/a&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;org&amp;quot;&amp;gt;Preston High School&amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;title&amp;quot;&amp;gt;Class President&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Using &amp;lt;code&amp;gt;&amp;amp;lt;object&amp;amp;gt;&amp;lt;/code&amp;gt;:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;object  data=&amp;quot;#pedro-name&amp;quot; class=&amp;quot;include&amp;quot;&amp;gt;&amp;lt;/object&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;org&amp;quot;&amp;gt;Preston High School&amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;title&amp;quot;&amp;gt;Class President&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Where &amp;quot;&amp;lt;code class=&amp;quot;attr-value&amp;quot;&amp;gt;pedro-name&amp;lt;/code&amp;gt;&amp;quot; is the id attribute value of the &amp;quot;&amp;lt;code class=&amp;quot;mf-prop&amp;quot;&amp;gt;fn n&amp;lt;/code&amp;gt;&amp;quot; element of the contact hCard at the top of the page, e.g. (shown here as a verbose hCard for purposes of illustration that the reference may be to a subtree, not just a text node):&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;address class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;fn n&amp;quot; id=&amp;quot;pedro-name&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;span class=&amp;quot;given-name&amp;quot;&amp;gt;Pedro&amp;lt;/span&amp;gt;&lt;br /&gt;
    &amp;lt;span class=&amp;quot;family-name&amp;quot;&amp;gt;Sanchez&amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/address&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This method of hCard property indirection via an object element [[include-pattern|has been generalized]] to apply to any/all string/text properties in hCard.&lt;br /&gt;
&lt;br /&gt;
Note: the object data attribute {{must}} be a local ID reference. External references (which would require a consuming application to load an external resource) are not supported by this method.&lt;br /&gt;
&lt;br /&gt;
=== Skills ===&lt;br /&gt;
Some sample skills tags:&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
I have skills in &amp;lt;a class=&amp;quot;skill&amp;quot; rel=&amp;quot;tag&amp;quot; href=&amp;quot;http://en.wikipedia.org/wiki/Bow_%28weapon%29&amp;quot;&amp;gt;bow hunting&amp;lt;/a&amp;gt; &lt;br /&gt;
and &amp;lt;a class=&amp;quot;skill&amp;quot; rel=&amp;quot;tag&amp;quot; href=&amp;quot;http://en.wikipedia.org/wiki/Nunchucks&amp;quot;&amp;gt;nunchucks&amp;lt;/a&amp;gt;.&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Affiliations ===&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;affiliation vcard&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;fn org&amp;quot;&amp;gt;National Honor Society&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Publications ===&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;cite&amp;gt;Breeding Ligers for Fun and Magic&amp;lt;/cite&amp;gt;, Idaho Press, 2004.&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Examples in the wild ==&lt;br /&gt;
See [[hresume-examples-in-wild]]&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 hResumes. If you have an hResume 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 like [[hresume-implementations]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* [http://www.cvmatch4jobs.com/ cvmatch4jobs] has implemented hResume import for publicly published CV's. A Career site for 3 UK building and proprety magazines from publishers UBM. 19 Jan 2010.&lt;br /&gt;
&lt;br /&gt;
* [http://careercv.mad.co.uk/ CareerCV] has implemented hResume import for publicly published CV's. A Career site for major UK design magazines from publishers Centaur Communications. 19 Jan 2010.&lt;br /&gt;
&lt;br /&gt;
* [http://lab.madgex.com/hresume/ Madgex] has implemented hResume to Microsoft Word and PDF conversion API. 13 Dec 2009. &lt;br /&gt;
&lt;br /&gt;
* [http://careers.stackoverflow.com/ Stack Overflow] generates hResume for its public CV hosting service for programmers. [http://careers.stackoverflow.com/klmr Stack Overflow CV example] Dec 2009.&lt;br /&gt;
&lt;br /&gt;
* [http://jobs.guardian.co.uk/profile/ Guardian Jobs] has implemented hResume import for publicly published CV's. 4 Sep 2009.&lt;br /&gt;
&lt;br /&gt;
* [http://www.yiid.com/ YIID - Your Internet Identity] supports importing of hResumes (e.g. here is the result of an import: http://pfefferle.yiid.com/cv [requires login] via @pfefferle)&lt;br /&gt;
&lt;br /&gt;
* [[Resume.app]]&lt;br /&gt;
&lt;br /&gt;
* [http://www.xing.com/ Xing] generates hResume for all Public Profiles. [http://www.xing.com/profile/Matthias_Pfefferle Xing Public Profile Example].&lt;br /&gt;
&lt;br /&gt;
* [http://linkedin.com LinkedIn] generates hResume for all Public Profiles. [http://www.linkedin.com/in/steveganz LinkedIn Public Profile Example].&lt;br /&gt;
&lt;br /&gt;
* [http://www.antix.co.uk Anthony Johnston] has implemented hResume (Creation and Import) in the [http://cv.antix.co.uk Antix CV Builder], an example resume using this site can be found [http://cv.antix.co.uk/ant here]&lt;br /&gt;
** The example resume is ''invalid''; job titles are marked with an hCard that is missing a &amp;quot;fn&amp;quot; (either directly or via object). --[[User:Gazza|Gazza]] 04:23, 1 May 2007 (PDT)&lt;br /&gt;
*** This is fixed now --[[User:Antix|Ant]] 00:38, 8 Dec 2007 (GMT)&lt;br /&gt;
&lt;br /&gt;
* The [http://spurinc.com Spur] team has created an hResume WordPress plugin located at [http://hresume.weblogswork.com/?page_id=3 hResume Plugin].  See an example of the hResume markup [http://hresume.weblogswork.com/?page_id=6 here].  Neat feature of the hResume plugin is that it automatically creates a new page for the resume - no cutting and pasting...&lt;br /&gt;
&lt;br /&gt;
* Spur also created a standalone hResume Creator located at [http://hresume.weblogswork.com/hresumecreator/ hResume Creator].  The creator will generate hResume markup ready to cut and paste into your webpage.&lt;br /&gt;
&lt;br /&gt;
== Copyright ==&lt;br /&gt;
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.&lt;br /&gt;
* [[RyanKing]]: I release all of my contributions to the public domain.&lt;br /&gt;
&lt;br /&gt;
Per the above, and the public domain release on the author, [[User:RyanKing|RyanKing]]'s, user page this specification is released into the public domain.&lt;br /&gt;
&lt;br /&gt;
{{MicroFormatPublicDomainContributionStatement}}&lt;br /&gt;
&lt;br /&gt;
== Patents ==&lt;br /&gt;
{{MicroFormatPatentStatement}}&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
=== Normative References ===&lt;br /&gt;
* [[hcard|hCard]]&lt;br /&gt;
* [[hcalendar|hCalendar]]&lt;br /&gt;
* [[include-pattern|include pattern]]&lt;br /&gt;
* [http://www.w3.org/TR/REC-html40/ HTML 4]&lt;br /&gt;
* [http://www.w3.org/TR/xhtml1/ XHTML]&lt;br /&gt;
* [http://gmpg.org/xmdp/ XMDP]&lt;br /&gt;
* [[rel-tag| Rel-Tag]]&lt;br /&gt;
* [[rfc-2119]]&lt;br /&gt;
* @TODO&lt;br /&gt;
&lt;br /&gt;
=== Informative References ===&lt;br /&gt;
* @TODO&lt;br /&gt;
&lt;br /&gt;
== Acknowledgements ==&lt;br /&gt;
=== Concept ===&lt;br /&gt;
* [http://theryanking.com/ Ryan King] ([http://technorati.com Technorati])&lt;br /&gt;
* [http://tantek.com/ Tantek Celik] ([http://technorati.com Technorati])&lt;br /&gt;
* James Levine ([http://simplyhired.com Simply Hired])&lt;br /&gt;
* [http://epeus.blogspot.com/ Kevin Marks] ([http://technorati.com Technorati])&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
{{hresume-related-pages}}&lt;br /&gt;
&lt;br /&gt;
== Further Reading ==&lt;br /&gt;
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].&lt;br /&gt;
* [http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-6-hresume/ Getting Semantic With Microformats, Part 6: hResume] by Emily Lewis&lt;br /&gt;
&lt;br /&gt;
[[Category:Draft Specifications]]&lt;br /&gt;
[[Category:hResume]]&lt;/div&gt;</summary>
		<author><name>Alik</name></author>
	</entry>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=hreview&amp;diff=43039</id>
		<title>hreview</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=hreview&amp;diff=43039"/>
		<updated>2010-09-05T20:33:50Z</updated>

		<summary type="html">&lt;p&gt;Alik: Syntax highlighting&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;entry-title&amp;gt;hReview 0.3&amp;lt;/entry-title&amp;gt;&lt;br /&gt;
{{DraftSpecification}}&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 HTML, XHTML, 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;
&amp;lt;div class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
;&amp;lt;span class=&amp;quot;role&amp;quot;&amp;gt;Editor&amp;lt;/span&amp;gt;&lt;br /&gt;
:&amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;[[User:Tantek|Tantek Celik]]&amp;lt;/span&amp;gt; (&amp;lt;span class=&amp;quot;url&amp;quot;&amp;gt;http://tantek.com/&amp;lt;/span&amp;gt;, and before at [http://technorati.com Technorati, Inc.])&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
; Authors&lt;br /&gt;
: [[User:Tantek|Tantek Celik]] (affiliations above)&lt;br /&gt;
: &amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;[http://360.yahoo.com/alidiabali Ali Diab]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ([http://yahoo.com Yahoo! Inc.])&lt;br /&gt;
: &amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;[http://ianmcall.blogspot.com/ Ian McAllister]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ([http://amazon.com/ Amazon.com])&lt;br /&gt;
: &amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;[http://journals.aol.com/panzerjohn/abstractioneer John Panzer]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ([http://www.aol.com America Online, Inc.])&lt;br /&gt;
: &amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;[http://ifindkarma.com/blog Adam Rifkin]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ([http://labs.commerce.net/ CommerceNet Labs])&lt;br /&gt;
: &amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;[http://sippey.typepad.com/ Michael Sippey]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; ([http://sixapart.com Six Apart, Ltd])&lt;br /&gt;
&lt;br /&gt;
[[hreview#Copyright|copyright]] and [[hreview#Patents|patents]] statements apply.&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
hReview 0.3 is a microformats.org draft specification. Public discussion on hReview takes place on [[hreview-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-discuss/ microformats-discuss mailing list].&lt;br /&gt;
&lt;br /&gt;
=== Available languages ===&lt;br /&gt;
The English version of this specification is the only normative version. For translations of this document see the [[#translations]] section.&lt;br /&gt;
&lt;br /&gt;
=== Errata and Updates ===&lt;br /&gt;
Known errors and issues in this specification are corrected in [[hreview-issues-resolved|resolved]] and [[hreview-issues-closed|closed]] issues. Please check there before reporting [[hreview-issues|issues]].&lt;br /&gt;
&lt;br /&gt;
The hReview 0.4 update is currently under development and incorporates known errata corrections as well as the [[value-class-pattern]].&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;
{{rfc-2119-intro}}&lt;br /&gt;
&lt;br /&gt;
=== Scope ===&lt;br /&gt;
Reviews consistently share several common aspects.  Where possible hReview has been based on this minimal common subset.&lt;br /&gt;
&lt;br /&gt;
==== Out of scope ====&lt;br /&gt;
Portions of reviews that are specific to particular kinds of items 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;
== Format ==&lt;br /&gt;
=== In General ===&lt;br /&gt;
The hReview format is based on a set of properties common to numerous review sites and formats in use today on the web.  Where possible property 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 HTML 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;
=== Property details ===&lt;br /&gt;
Details of the hReview properties:&lt;br /&gt;
&lt;br /&gt;
'''version''':: This optional property permits hReview publishers to specify a particular version of hReview that their content uses.  By omitting this property, 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 property 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 property for this specification is &amp;quot;0.3&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
'''summary''':: This optional property serves as a short synopsis, title, or name of the review. Re-used from [[hCalendar]] which re-uses it from iCalendar (section 4.8.1.12 of RFC 2445).&lt;br /&gt;
&lt;br /&gt;
'''type''':: This optional property provides the type of the item being reviewed, one of the following: &amp;lt;code&amp;gt;product, business, place, person, event, website, url&amp;lt;/code&amp;gt;.  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;, &amp;quot;place&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''':: This required property {{must}} have at a minimum the name (using the subproperty &amp;quot;fn&amp;quot; - the formatted text corresponding to the name, except for an event item which {{must}} have the &amp;quot;summary&amp;quot; subproperty inside the respective hCalendar &amp;quot;vevent&amp;quot;) 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;.  Non-URL unique item IDs (e.g. ISBNs, UPCs) {{may}} be represented as a URN (&amp;quot;url&amp;quot;) for the item.  Encapsulated microformats (e.g. [[hcard|hCard]] and [[hcalendar|hCalendar]] events for now) may be set on the item itself (e.g. class=&amp;quot;item vcard&amp;quot;).  However, when using item info subproperties (&amp;quot;fn&amp;quot;, &amp;quot;url&amp;quot;, &amp;quot;photo&amp;quot;), they {{must}} be nested &amp;lt;em&amp;gt;inside&amp;lt;/em&amp;gt; the item element.&lt;br /&gt;
&lt;br /&gt;
'''reviewer''':: The optional property 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 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 property when present {{must}} provide an [[ISO-8601|ISO8601]] absolute date time of when the review was written or otherwise authored.  This property {{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 to indicate a different range (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 property serves as a more detailed synopsis of the review (i.e. full text representing the written opinion of the reviewer) than that provided by summary.  The property {{may}} include valid HTML 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 property.&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 property 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 property, 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.&lt;br /&gt;
&lt;br /&gt;
'''license''':: an hReview indicates the license for its contents using the '''[[rel-license]]''' microformat.&lt;br /&gt;
&lt;br /&gt;
The following property names have been reused from the [[hcard|hCard]] and [[hcalendar|hCalendar]] microformats: &amp;lt;code&amp;gt;version, summary, fn, url, photo, description&amp;lt;/code&amp;gt;.  In addition, items and reviewers described by hCards {{may}} contain any hCard property.  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;
=== 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;
* 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.0&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 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 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;
* 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;source lang=html4strict&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;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Adding hReview to this review is quite simple:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&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;/source&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;source lang=html4strict&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&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;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With an accompanying CSS style sheet like:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
a.url { display:block }&lt;br /&gt;
ul { margin:1em 0; padding:0 }&lt;br /&gt;
ul li { display:inline }&lt;br /&gt;
&amp;lt;/source&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;source lang=html4strict&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;/source&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;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;hreview&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;item&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;a class=&amp;quot;url fn&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;
  The Postal Service: Give Up&amp;lt;/a&amp;gt;&amp;lt;/span&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;/source&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;source lang=html4strict&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;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With hReview:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&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;/source&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'''. The number of hReview examples in the wild has expanded far beyond the capacity of being kept inline in this specification. They have been moved to a [[hreview-examples-in-wild|separate page]].&lt;br /&gt;
&lt;br /&gt;
See [[hreview-examples-in-wild|hReview Examples in the wild]].&lt;br /&gt;
&lt;br /&gt;
== Implementations ==&lt;br /&gt;
This section is '''informative'''. The number of hReview implementations has also expanded beyond the capacity of keeping them inline. They have been moved to a [[hreview-implementations|separate page]].&lt;br /&gt;
&lt;br /&gt;
See [[hreview-implementations|hReview Implementations]].&lt;br /&gt;
&lt;br /&gt;
== Design Principles ==&lt;br /&gt;
This section is '''informative'''.  hReview was designed using design [[principles]] similar to those that went into [[hCard]] and thus this overview is included for informational purposes.&lt;br /&gt;
&lt;br /&gt;
{{semantic-xhtml-design-principles}}&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: [[User:Richardault|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;
== 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;
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.&lt;br /&gt;
** When all authors/editors have done so, we can remove the MicroFormatCopyrightStatement template reference and replace it with the MicroFormatPublicDomainContributionStatement.&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 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;
== Further Reading ==&lt;br /&gt;
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
{{hreview-related-pages}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Draft Specifications]]&lt;br /&gt;
[[Category:hReview]]&lt;br /&gt;
&lt;br /&gt;
== Translations ==&lt;br /&gt;
Read the hReview draft specification in additional &amp;lt;span id=&amp;quot;languages&amp;quot;&amp;gt;languages&amp;lt;/span&amp;gt;:&lt;br /&gt;
* [[hreview-fr|français]]&lt;br /&gt;
* [[hreview-ja|日本語]]&lt;/div&gt;</summary>
		<author><name>Alik</name></author>
	</entry>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=hcalendar&amp;diff=43038</id>
		<title>hcalendar</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=hcalendar&amp;diff=43038"/>
		<updated>2010-09-05T20:31:25Z</updated>

		<summary type="html">&lt;p&gt;Alik: Syntax highlighting&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;entry-title&amp;gt;hCalendar 1.0&amp;lt;/entry-title&amp;gt;&lt;br /&gt;
&amp;lt;dfn style=&amp;quot;font-style:normal;font-weight:bold&amp;quot;&amp;gt;hCalendar&amp;lt;/dfn&amp;gt; is a simple, open, distributed calendaring and events format, using a 1:1 representation of standard iCalendar ([[rfc-2445|RFC2445]]) VEVENT properties and values in [[semantic-xhtml|semantic HTML or XHTML]]. hCalendar is one of several open [[microformats|microformat]] standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.&lt;br /&gt;
&lt;br /&gt;
'''Want to get started with writing an [[hcalendar|hCalendar]] event?''' Use the [http://microformats.org/code/hcalendar/creator hCalendar creator] to write up an event and publish it, or follow the [[hcalendar-authoring|hCalendar authoring tips]] to add hCalendar markup to your page of upcoming events or events you mention in blog posts, wikis, etc.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
; &amp;lt;span class=&amp;quot;role&amp;quot;&amp;gt;Editor&amp;lt;/span&amp;gt; &lt;br /&gt;
: &amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;[[User:Tantek|Tantek Celik]]&amp;lt;/span&amp;gt; (&amp;lt;span class=&amp;quot;url&amp;quot;&amp;gt;http://tantek.com/&amp;lt;/span&amp;gt;, and before at [http://technorati.com Technorati, Inc.], and at [http://microsoft.com/ Microsoft Corporation])&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
; Authors: [http://tantek.com/ Tantek Celik] (affiliations above)&lt;br /&gt;
: &amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;[[User:Brian|Brian Suda]]&amp;lt;/span&amp;gt; (&amp;lt;span class=&amp;quot;url&amp;quot;&amp;gt;http://suda.co.uk/&amp;lt;/span&amp;gt;)&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
; Acknowledgments: See [[hcalendar#Inspiration_and_Acknowledgments|acknowledgments]].&lt;br /&gt;
&lt;br /&gt;
[[hcalendar#Copyright|copyright]] and [[hcalendar#Patents|patents]] statements apply.&lt;br /&gt;
&lt;br /&gt;
== Example ==&lt;br /&gt;
Here is a simple event:&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;p&amp;gt;The microformats.org site was launched on 2005-06-20 at the Supernova Conference in San Francisco, CA, USA.&amp;lt;/p&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
marked up with hCalendar&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;span class=&amp;quot;summary&amp;quot;&amp;gt;The microformats.org site was launched&amp;lt;/span&amp;gt;&lt;br /&gt;
 on &amp;lt;span class=&amp;quot;dtstart&amp;quot;&amp;gt;2005-06-20&amp;lt;/span&amp;gt; &lt;br /&gt;
 at the Supernova Conference &lt;br /&gt;
 in &amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt;San Francisco, CA, USA&amp;lt;/span&amp;gt;.&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Status ==&lt;br /&gt;
hCalendar 1.0 is a microformats.org specification. Public discussion on hCalendar takes place on [[hcalendar-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-discuss/ microformats-discuss mailing list].&lt;br /&gt;
&lt;br /&gt;
=== Available languages ===&lt;br /&gt;
The English version of this specification is the only normative version. For translations of this document see the [[#translations]] section.&lt;br /&gt;
&lt;br /&gt;
=== Errata and Updates ===&lt;br /&gt;
Known errors and issues in this specification are corrected in [[hcalendar-issues-resolved|resolved]] and [[hcalendar-issues-closed|closed]] issues. Please check there before reporting [[hcalendar-issues|issues]].&lt;br /&gt;
&lt;br /&gt;
Note in particular the [[dtend-issue]] which affects end dates. Implementations {{should}} implement the issue resolution ASAP and [http://ufxtract.com/testsuite/hcalendar/hcalendar1.htm test it].&lt;br /&gt;
&lt;br /&gt;
The hCalendar 1.0.1 update is currently under development and incorporates known errata corrections as well as the [[value-class-pattern]].&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
The iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]), has been broadly interoperably implemented (e.g. Apple's &amp;quot;iCal&amp;quot; application built into MacOSX).&lt;br /&gt;
&lt;br /&gt;
In addition, bloggers often discuss events on their blogs -- upcoming events, writeups of past events, etc.  With just a tad bit of structure, bloggers can discuss events in their blog(s) in such a way that spiders and other aggregators can retrieve such events, automatically convert them to iCalendar, and use them in any iCalendar application or service.&lt;br /&gt;
&lt;br /&gt;
This specification introduces the '''hCalendar''' format, which is a 1:1 representation of the aforementioned iCalendar standard, in semantic HTML.  Bloggers can both embed hCalendar events directly in their web pages, and style them with CSS to make them appear as desired.  In addition, hCalendar enables applications to retrieve information about such events directly from web pages without having to reference a separate file.&lt;br /&gt;
&lt;br /&gt;
{{rfc-2119-intro}}&lt;br /&gt;
&lt;br /&gt;
== Semantic XHTML Design Principles ==&lt;br /&gt;
&lt;br /&gt;
{{semantic-xhtml-design-principles}}&lt;br /&gt;
&lt;br /&gt;
For practical implementations, it should be noted that Internet Explorer's support for styling &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; elements is poor, and may require wrapper elements.&lt;br /&gt;
&lt;br /&gt;
== Format ==&lt;br /&gt;
=== In General ===&lt;br /&gt;
The iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]) forms the basis of hCalendar.&lt;br /&gt;
&lt;br /&gt;
Note: the editor and authors of this specification are tracking the [http://lists.osafoundation.org/pipermail/ietf-calsify/ &amp;quot;iCal-Basic&amp;quot; effort] and intend to base the core hCalendar profile on iCal-Basic. See references for a link to the current draft.&lt;br /&gt;
&lt;br /&gt;
The basic format of hCalendar is to use iCalendar object/property names in lower-case for class names, and to map the nesting of iCalendar objects directly into nested XHTML elements.&lt;br /&gt;
&lt;br /&gt;
=== Root Class Name ===&lt;br /&gt;
The root class name for hCalendar is &amp;quot;vcalendar&amp;quot;.  An element with a class name of &amp;quot;vcalendar&amp;quot; is itself called an ''hCalendar''. &lt;br /&gt;
&lt;br /&gt;
The root class name for events is &amp;quot;vevent&amp;quot;. An element with a class name of &amp;quot;vevent&amp;quot; is itself called an ''hCalendar event''.&lt;br /&gt;
&lt;br /&gt;
For authoring convenience, both &amp;quot;vevent&amp;quot; and &amp;quot;vcalendar&amp;quot; are treated as root class names for parsing purposes.  If a document contains elements with class name &amp;quot;vevent&amp;quot; but not &amp;quot;vcalendar&amp;quot;, the entire document has an implied &amp;quot;vcalendar&amp;quot; context.&lt;br /&gt;
&lt;br /&gt;
'''vevent''' should be considered required for each event listing.&lt;br /&gt;
&lt;br /&gt;
=== Properties and Sub-properties ===&lt;br /&gt;
The properties of an hCalendar are represented by elements inside the hCalendar.  Elements with class names of the listed properties represent the values of those properties.  Some properties have sub-properties, and those are represented by elements inside the elements for properties.&lt;br /&gt;
&lt;br /&gt;
=== Property List ===&lt;br /&gt;
hCalendar properties (sub-properties in parentheses like this)&lt;br /&gt;
&lt;br /&gt;
'''Required:'''&lt;br /&gt;
* '''dtstart''' ([[iso-8601|ISO date]])&lt;br /&gt;
* '''summary'''&lt;br /&gt;
Optional:&lt;br /&gt;
* location&lt;br /&gt;
* url&lt;br /&gt;
* dtend (ISO date), duration (ISO date duration)&lt;br /&gt;
* rdate, rrule&lt;br /&gt;
* category, description&lt;br /&gt;
* uid&lt;br /&gt;
* geo (latitude, longitude)&lt;br /&gt;
* attendee (partstat, role), contact, organizer&lt;br /&gt;
* attach&lt;br /&gt;
* status&lt;br /&gt;
* ... editor's note: this list is incomplete (an incomplete list is better than no list) and is being currently edited from RFC2445 to here.  The above list of properties are those that are often used in hCalendar on the web.&lt;br /&gt;
&lt;br /&gt;
=== Profile ===&lt;br /&gt;
The hCalendar XMDP profile is at http://microformats.org/profile/hcalendar&lt;br /&gt;
&lt;br /&gt;
Content that uses hCalendar {{should}} reference this profile, e.g.&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;head profile=&amp;quot;http://microformats.org/profile/hcalendar&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
or&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;link rel=&amp;quot;profile&amp;quot; href=&amp;quot;http://microformats.org/profile/hcalendar&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
or&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
This content uses &amp;lt;a rel=&amp;quot;profile&amp;quot; href=&amp;quot;http://microformats.org/profile/hcalendar&amp;quot;&amp;gt;hCalendar&amp;lt;/a&amp;gt;.&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
Content may combine the above methods as well.&lt;br /&gt;
&lt;br /&gt;
=== More Semantic Equivalents ===&lt;br /&gt;
For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:&lt;br /&gt;
* &amp;lt;code&amp;gt;URL&amp;lt;/code&amp;gt; in iCalendar becomes  &amp;lt;code&amp;gt;&amp;amp;lt;a class=&amp;quot;url&amp;quot; href=&amp;quot;...&amp;quot;&amp;amp;gt;...&amp;amp;lt;/a&amp;amp;gt;&amp;lt;/code&amp;gt; inside the element with &amp;lt;code&amp;gt;class=&amp;quot;vevent&amp;quot;&amp;lt;/code&amp;gt; in hCalendar.&lt;br /&gt;
* &amp;lt;code&amp;gt;ATTENDEE&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;CONTACT&amp;lt;/code&amp;gt;, and &amp;lt;code&amp;gt;ORGANIZER&amp;lt;/code&amp;gt; in iCalendar {{may}} be represented by an [[hcard|hCard]] in hCalendar .&lt;br /&gt;
* A named &amp;lt;code&amp;gt;LOCATION&amp;lt;/code&amp;gt; (potentially with an address and/or geo) in iCalendar {{may}} be represented by a nested [[hcard|hCard]] in hCalendar. Similarly, an address &amp;lt;code&amp;gt;LOCATION&amp;lt;/code&amp;gt; {{may}} be represented by an [[adr]], and a geo (latitude and longitude) &amp;lt;code&amp;gt;LOCATION&amp;lt;/code&amp;gt; may be represented by a [[geo]].&lt;br /&gt;
* &amp;lt;code&amp;gt;UID&amp;lt;/code&amp;gt; in iCalendar simply becomes another semantic applied to a specific URL for an hCalendar event.&lt;br /&gt;
* &amp;lt;code&amp;gt;ATTACH&amp;lt;/code&amp;gt; in iCalendar becomes an img or object element (where the value is stored ito / retrieved from the 'src' or 'data' attributes respectively). An &amp;lt;code&amp;gt;&amp;amp;lt;a class=&amp;quot;attach&amp;quot;                           href=&amp;quot;...&amp;quot;&amp;amp;gt;...&amp;amp;lt;/a&amp;amp;gt;&amp;lt;/code&amp;gt; may also be used, in which case the 'href' attribute is used for the property value.&lt;br /&gt;
&lt;br /&gt;
=== Singular vs. Plural Properties ===&lt;br /&gt;
&lt;br /&gt;
For properties which are singular (e.g. &amp;quot;N&amp;quot; and &amp;quot;FN&amp;quot; from vCard), the first descendant element with that class {{should}} take effect, any others being ignored.&lt;br /&gt;
&lt;br /&gt;
For properties which can be plural (e.g. &amp;quot;TEL&amp;quot; from vCard), each class instance {{should}} create a instance of that property. Plural properties with subtypes (e.g. TEL with WORK, HOME, CELL from vCard) can be optimized to share a common element for the property itself, with each instance of subtype being an appropriately classed descendant of the property element.&lt;br /&gt;
&lt;br /&gt;
==== Plural Properties Singularized ====&lt;br /&gt;
&lt;br /&gt;
Since plural property names become their singular equivalents, even if the original plural property permitted only a single value with multiple components, those multiple components are represented each with their own singularly named property and the the property is effectively multivalued and subject to the above treatment of multivalued properties.&lt;br /&gt;
&lt;br /&gt;
=== Human vs. Machine readable ===&lt;br /&gt;
If an &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; element is used for a property, then the '&amp;lt;code&amp;gt;title&amp;lt;/code&amp;gt;' attribute of the &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; element is the value of the property, instead of the contents of the element,  which instead provide a human presentable version of the value.  This specification recommends that such &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; elements be used for the following iCalendar properties:&lt;br /&gt;
* DTSTART, DTEND, DURATION, RDATE, RRULE&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
&lt;br /&gt;
Here is a sample multiple-day event in an iCalendar:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;nowiki&amp;gt;&lt;br /&gt;
BEGIN:VCALENDAR&lt;br /&gt;
PRODID:-//XYZproduct//EN&lt;br /&gt;
VERSION:2.0&lt;br /&gt;
BEGIN:VEVENT&lt;br /&gt;
URL:http://conferences.oreillynet.com/pub/w/40/program.html&lt;br /&gt;
DTSTART:20051005&lt;br /&gt;
DTEND:20051008&lt;br /&gt;
SUMMARY:Web 2.0 Conference&lt;br /&gt;
LOCATION:Argent Hotel\, San Francisco\, CA&lt;br /&gt;
END:VEVENT&lt;br /&gt;
END:VCALENDAR&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and an equivalent event in hCalendar format with various elements optimized appropriately. See [[hcalendar-example1-steps]] for the derivation.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;a class=&amp;quot;url&amp;quot; href=&amp;quot;http://conferences.oreillynet.com/pub/w/40/program.html&amp;quot;&amp;gt;&lt;br /&gt;
  http://conferences.oreillynet.com/pub/w/40/program.html&lt;br /&gt;
 &amp;lt;/a&amp;gt;&lt;br /&gt;
 &amp;lt;span class=&amp;quot;summary&amp;quot;&amp;gt;Web 2.0 Conference&amp;lt;/span&amp;gt;: &lt;br /&gt;
 &amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;2005-10-05&amp;quot;&amp;gt;October 5&amp;lt;/abbr&amp;gt;-&lt;br /&gt;
 &amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;2005-10-07&amp;quot;&amp;gt;7&amp;lt;/abbr&amp;gt;,&lt;br /&gt;
 at the &amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt;Argent Hotel, San Francisco, CA&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
which could be displayed as:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;url&amp;quot;&amp;gt;http://conferences.oreillynet.com/pub/w/40/program.html&amp;lt;/span&amp;gt;&amp;amp;nbsp;&amp;lt;!-- note modified to account for idiosyncrasy of wiki software --&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;summary&amp;quot;&amp;gt;Web 2.0 Conference&amp;lt;/span&amp;gt;: &lt;br /&gt;
&amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;2005-10-05&amp;quot;&amp;gt;October 5&amp;lt;/abbr&amp;gt;-&lt;br /&gt;
&amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;2005-10-07&amp;quot;&amp;gt;7&amp;lt;/abbr&amp;gt;,&lt;br /&gt;
at the &amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt;Argent Hotel, San Francisco, CA&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note 1: that this is a '''live''' hCalendar microformat, which will be found on this page by parsers.&lt;br /&gt;
&lt;br /&gt;
Note 2: This example used to have &amp;quot;2005-10-08&amp;quot; as the value of the dtend, but per the resolution to the [[dtend-issue]], has been changed to &amp;quot;2005-10-07&amp;quot; in order to encourage publishers/implementers to update their markup/code immediately and [http://ufxtract.com/testsuite/hcalendar/hcalendar1.htm test it].&lt;br /&gt;
&lt;br /&gt;
Note 3: Note that the iCalendar in the first part of the example has the code &amp;lt;code&amp;gt;DTEND:20051008&amp;lt;/code&amp;gt;. That &amp;quot;8&amp;quot; is not a typo. iCalendar uses &amp;lt;em&amp;gt;exclusive&amp;lt;/em&amp;gt; whole end dates (DTEND values) and thus requires that the DTEND value be set to a whole day &amp;lt;em&amp;gt;after&amp;lt;/em&amp;gt; what content publishers visibly display as the ending date of an event. iCalendar's exclusive end dates convention has shown to be [[dtend-issue|problematic and confusing]] for content authors and publishers. Thus per the resolution to the [[dtend-issue]], in hCalendar, the end date is stated exactly as existing events publish visible end dates to humans, with an &amp;lt;em&amp;gt;inclusive&amp;lt;/em&amp;gt; end date (dtend property value), in this example, 2005-10-07.&lt;br /&gt;
&lt;br /&gt;
=== Meeting Example ===&lt;br /&gt;
The following &amp;lt;span id=&amp;quot;Example_2&amp;quot;&amp;gt;example&amp;lt;/span&amp;gt; specifies a scheduled meeting that begins&lt;br /&gt;
at 8:30 AM EST on March 12, 1998 and ends at 9:30 AM EST on March 12,&lt;br /&gt;
1998. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
     BEGIN:VCALENDAR&lt;br /&gt;
     BEGIN:VEVENT&lt;br /&gt;
     UID:guid-1.host1.com&lt;br /&gt;
     DTSTAMP:19980309T231000Z&lt;br /&gt;
     DESCRIPTION:Project XYZ Review Meeting&lt;br /&gt;
     SUMMARY:XYZ Project Review&lt;br /&gt;
     DTSTART:19980312T133000Z&lt;br /&gt;
     DTEND:19980312T143000Z&lt;br /&gt;
     LOCATION:1CP Conference Room 4350&lt;br /&gt;
     END:VEVENT&lt;br /&gt;
     END:VCALENDAR&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The equivalent in hCalendar:&lt;br /&gt;
&lt;br /&gt;
'''Note: This example needs to be updated to use the [[value-class-pattern]]. Use of full ISO8601 datetimes in abbr title attributes is deprecated in lieu of separate dates and times per the value-class-pattern.'''&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;h3 class=&amp;quot;summary&amp;quot;&amp;gt;XYZ Project Review&amp;lt;/h3&amp;gt;&lt;br /&gt;
&amp;lt;p class=&amp;quot;description&amp;quot;&amp;gt;Project XYZ Review Meeting&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;To be held on &amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;1998-03-12T08:30:00-05:00&amp;quot;&amp;gt;12 March 1998 from 8:30am EST&amp;lt;/abbr&amp;gt; &lt;br /&gt;
until &amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;1998-03-12T09:30:00-05:00&amp;quot;&amp;gt;9:30am EST&amp;lt;/abbr&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Location: &amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt;1CP Conference Room 4350&amp;lt;/span&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;small&amp;gt;Booked by: &amp;lt;span class=&amp;quot;uid&amp;quot;&amp;gt;guid-1.host1.com&amp;lt;/span&amp;gt; on &lt;br /&gt;
&amp;lt;abbr class=&amp;quot;dtstamp&amp;quot; title=&amp;quot;19980309T231000Z&amp;quot;&amp;gt;9 Mar 1998 6:00pm&amp;lt;/abbr&amp;gt;&amp;lt;/small&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This could be displayed as:&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h3 class=&amp;quot;summary&amp;quot;&amp;gt;XYZ Project Review&amp;lt;/h3&amp;gt;&lt;br /&gt;
&amp;lt;p class=&amp;quot;description&amp;quot;&amp;gt;Project XYZ Review Meeting&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;To be held on &amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;1998-03-12T08:30:00-05:00&amp;quot;&amp;gt;12 March 1998 from 8:30am EST&amp;lt;/abbr&amp;gt; &lt;br /&gt;
until &amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;1998-03-12T09:30:00-05:00&amp;quot;&amp;gt;9:30am EST&amp;lt;/abbr&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Location: &amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt;1CP Conference Room 4350&amp;lt;/span&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;small&amp;gt;Booked by: &amp;lt;span class=&amp;quot;uid&amp;quot;&amp;gt;guid-1.host1.com&amp;lt;/span&amp;gt; on &amp;lt;abbr class=&amp;quot;dtstamp&amp;quot; title=&amp;quot;19980309T231000Z&amp;quot;&amp;gt;9 Mar 1998 6:00pm&amp;lt;/abbr&amp;gt;&amp;lt;/small&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Note 1: The product information is not necessary since hCalendar is an interchange format.  When transforming hCalendar back into iCalendar, the transforming engine should add its own product ID.&lt;br /&gt;
&lt;br /&gt;
Note 2: A surrounding &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;span class=&amp;quot;vcalendar&amp;quot;&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; element is optional, and is left out as such.  It is optional since the context of a vcalendar is implied when a vevent is encountered.  The implied context/scope is that of the document.  Authors may explicitly use elements with class=&amp;quot;vcalendar&amp;quot; to wrap sets of vevents that all belong to the same calendar, e.g. when publishing multiple calendars on the same page.&lt;br /&gt;
&lt;br /&gt;
Note 3: The version information is unnecessary in hCalendar markup directly since the version will be defined by the profile of hCalendar that is used/referred to in the 'profile' attribute of the &amp;lt;head&amp;gt; element.&lt;br /&gt;
&lt;br /&gt;
Note 4: [[iso-8601|ISO8601]] datetimes (required by iCalendar) are not very human friendly.  In addition, the year is often understood implicitly by humans from the context.  Thus &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; elements are used to simultaneously provide a human friendly date and/or time in the visible contents of the element, while placing the respective machine parsable comprehensive ISO8601 datetime in the 'title' attribute.&lt;br /&gt;
The notation &amp;lt;code&amp;gt;YYYY-MM-DDThh:mm:ss&amp;lt;/code&amp;gt; should be used for better readability, following the format of RFC 3339.  '''Update: Per the [[value-class-pattern]], separate dates and times {{should}} be used by authors rather than a full ISO8601 datetime, for better readability and listenability.'''&lt;br /&gt;
&lt;br /&gt;
Note 5: Per the [[dtend-issue]] resolution, DTEND dates are provided as humans expecte them to be (consistent with what day an event ends on), rather than iCalendar's confusing definition (the day after). Thus hCalendar processors which produce iCalendar must make the transformation, which is to treat a whole hCalendar &amp;lt;code&amp;gt;dtend&amp;lt;/code&amp;gt; end date as *inclusive*, and convert it to an *[http://lists.osafoundation.org/pipermail/ietf-calsify/2005-September/000769.html exclusive DTEND]* end date when producing iCalendar.&lt;br /&gt;
&lt;br /&gt;
Note 6: The location in this example contains implicit structure (venue name, city, state) which could be marked up explicitly as an [[hcard|hCard]].  See [http://microformats.org/wiki/hcalendar-brainstorming#hCard_locations hCalendar brainstorming: hCard locations] for a informative explanation of how to do this.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== More Examples ===&lt;br /&gt;
See [[hcalendar-examples|hCalendar examples]] for more examples, including examples from iCalendar RFC 2445 converted into hCalendar.&lt;br /&gt;
&lt;br /&gt;
== Examples in the wild ==&lt;br /&gt;
This section is '''informative'''. The number of hCalendar examples in the wild has expanded far beyond the capacity of being kept inline in this specification. They have been moved to a [[hcalendar-examples-in-wild|separate page]].&lt;br /&gt;
&lt;br /&gt;
See [[hcalendar-examples-in-wild|hCalendar Examples in the wild]].&lt;br /&gt;
&lt;br /&gt;
== Implementations ==&lt;br /&gt;
This section is '''informative'''. The number of hCalendar implementations has also expanded beyond the capacity of keeping them inline. They have been moved to a [[hcalendar-implementations|separate page]].&lt;br /&gt;
&lt;br /&gt;
See [[hcalendar-implementations|hCalendar Implementations]].&lt;br /&gt;
&lt;br /&gt;
== Articles ==&lt;br /&gt;
This section is &amp;lt;strong&amp;gt;informative&amp;lt;/strong&amp;gt;. Articles and blog posts on hCalendar, most recent first. When it gets too big, we can move it to a page like [[hcalendar-articles]].&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;span class=&amp;quot;hentry&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;published&amp;quot;&amp;gt;2009-08-19&amp;lt;/span&amp;gt; (Updated: &amp;lt;span class=&amp;quot;updated&amp;quot;&amp;gt;2009-09-10&amp;lt;/span&amp;gt;) &amp;lt;cite class=&amp;quot;entry-title&amp;quot;&amp;gt;[http://dev.opera.com/articles/view/styling-and-extracting-hcalendar/ Styling and extracting hCalendar]&amp;lt;/cite&amp;gt; by  &amp;lt;span class=&amp;quot;vcard author&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;fn org&amp;quot;&amp;gt;[http://dev.opera.com/author/1048426 Christopher Schmitt]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
* 2008-11-17 [http://forabeautifulweb.com/blog/about/a_tribute_to_microformats_a_reader_question_answered/ A tribute to Microformats (a reader question answered)] by [http://www.stuffandnonsense.co.uk/ Andy Clarke]&lt;br /&gt;
* 2008-10-01 [http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-4-hcalendar/ Getting Semantic With Microformats, Part 4: hCalendar] by [http://www.ablognotlimited.com/ Emily Lewis]&lt;br /&gt;
* 2008-02-01 [http://www.peachpit.com/guides/content.aspx?g=webdesign&amp;amp;seqNum=356 Microformats: The Art of Markup: hCalendar] by [http://www.stuffandnonsense.co.uk/ Andy Clarke]&lt;br /&gt;
* 2006-01-11 [http://weblog.infoworld.com/udell/2006/01/11.html#a1368 Moving forward with microformats] by [http://weblog.infoworld.com/udell Jon Udell] provides an hCalendar example and some discussion.&lt;br /&gt;
&lt;br /&gt;
See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page] and the [http://technorati.com/tags/hcalendar hCalendar tag]&lt;br /&gt;
&lt;br /&gt;
==Buttons==&lt;br /&gt;
This section is &amp;lt;strong&amp;gt;informative&amp;lt;/strong&amp;gt;. Don't forget that you can add one of our [[buttons#hCalendar|buttons]] to the page, to indicate the presence of hCalendar microformats. For example: http://www.boogdesign.com/images/buttons/microformat_hcalendar.png. If you can link it back to this page (or even page on your website, about your use of the microformat), so much the better!&lt;br /&gt;
&lt;br /&gt;
== Copyright ==&lt;br /&gt;
Per the public domain release on the authors' user pages ([[User:Tantek|Tantek Celik]], [[User:Brian|Brian Suda]]) this specification is released into the public domain.&lt;br /&gt;
&lt;br /&gt;
{{MicroFormatPublicDomainContributionStatement}}&lt;br /&gt;
&lt;br /&gt;
== Patents ==&lt;br /&gt;
{{MicroFormatPatentStatement}}&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;
* [[hcard|hCard]]&lt;br /&gt;
* [http://www.ietf.org/rfc/rfc2445.txt iCalendar RFC2445]&lt;br /&gt;
* [[rfc-2119| RFC 2119]]&lt;br /&gt;
* [[iso-8601|ISO8601]]&lt;br /&gt;
&lt;br /&gt;
=== Informative References ===&lt;br /&gt;
This section is &amp;lt;strong&amp;gt;informative&amp;lt;/strong&amp;gt;.&lt;br /&gt;
* [http://w3.org/TR/REC-CSS1 CSS1]&lt;br /&gt;
* [http://tantek.com/log/2004/09.html#hcalendar hCalendar term introduced and defined on the Web, 20040930]&lt;br /&gt;
* [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation, 20040911]&lt;br /&gt;
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]&lt;br /&gt;
* [http://ietfreport.isoc.org/idref/draft-royer-ical-basic/ iCal-Basic (latest)] [http://www.faqs.org/ftp/pub/pub/internet-drafts/draft-royer-ical-basic-04.txt (draft 04)]&lt;br /&gt;
* [http://www.w3.org/TR/NOTE-datetime W3C Note on Date and Time Formats]&lt;br /&gt;
* [http://www.imc.org/pdi/ Internet Mail Consortium Personal Data Interchange vCard and vCalendar]&lt;br /&gt;
* Contributed from http://developers.technorati.com/wiki/hCalendar&lt;br /&gt;
&lt;br /&gt;
==== Specifications That Use hCalendar ====&lt;br /&gt;
* [[hreview|hReview]]&lt;br /&gt;
&lt;br /&gt;
==== Related Work ====&lt;br /&gt;
* [http://lists.osafoundation.org/pipermail/ietf-calsify/ IETF-calsify archives]&lt;br /&gt;
* [http://www.softwarestudio.org/iCal/2445Issues.html RFC2445 Issues List]&lt;br /&gt;
* [http://ietf.webdav.org/calsify/ CALSIFY WG Links And Resources]&lt;br /&gt;
&lt;br /&gt;
== Inspiration and Acknowledgments ==&lt;br /&gt;
Thanks to:&lt;br /&gt;
* Adam Bosworth for leading the [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation] which brought together a critical mass of interested parties.&lt;br /&gt;
&lt;br /&gt;
== Related Reading ==&lt;br /&gt;
This section is &amp;lt;strong&amp;gt;informative&amp;lt;/strong&amp;gt;.&lt;br /&gt;
Some &amp;lt;span id=&amp;quot;Further_Reading&amp;quot;&amp;gt;further reading&amp;lt;/span&amp;gt; on the broader topic of calendars and calendaring formats.&lt;br /&gt;
* [http://www.livejournal.com/users/jwz/444651.html jwz - Hula] (required reading)&lt;br /&gt;
* [http://www.jwz.org/doc/groupware.html Groupware Bad by Jamie Zawinski] crystalizes the reason for hCalendar ('''emphasis''' added):&lt;br /&gt;
&amp;lt;blockquote&amp;gt;Right now people can do that by publishing .ics files, but it's not trivial to do so, and it's work on the part of other people to look at them. '''If it's not HTML hanging off our friend's home page that can be viewed in any browser on a public terminal in a library, the bar to entry is too high and it's useless.'''&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
{{hcalendar-related-pages}}&lt;br /&gt;
* [http://en.wikipedia.org/wiki/HCalendar Wikipedia article on hCalendar]&lt;br /&gt;
&lt;br /&gt;
[[Category:Specifications]]&lt;br /&gt;
[[Category:hCalendar]]&lt;br /&gt;
&lt;br /&gt;
== Translations ==&lt;br /&gt;
Read the hCard specification in additional &amp;lt;span id=&amp;quot;languages&amp;quot;&amp;gt;languages&amp;lt;/span&amp;gt;:&lt;br /&gt;
* [[hcalendar-fr|français]]&lt;br /&gt;
* [[hcalendar-ru|Русский]]&lt;br /&gt;
* [[hcalendar-ja|日本語]]&lt;/div&gt;</summary>
		<author><name>Alik</name></author>
	</entry>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=hcalendar-ru&amp;diff=43037</id>
		<title>hcalendar-ru</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=hcalendar-ru&amp;diff=43037"/>
		<updated>2010-09-05T20:24:08Z</updated>

		<summary type="html">&lt;p&gt;Alik: Syntax highlighting&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= hCalendar =&lt;br /&gt;
&lt;br /&gt;
hCalendar является простым, открытым, распределённым форматом для разметки календарных и иного рода событий. Данный микроформат основан на стандарте iCalendar ([http://www.ietf.org/rfc/rfc2445.txt RFC 2445]). hCalendar можно внедрить в HTML, XHTML и XML-подобные языки разметки.&lt;br /&gt;
hCalendar — один из [[microformats-ru|микроформатов]].&lt;br /&gt;
&lt;br /&gt;
Хотите уже сейчас разметить события на своих страницах с помощью hCalendar? Попробуйте использовать [http://microformats.org/code/hcalendar/creator генератор hCalendar]. Помимо автоматического создания микроформата, вы можете самостоятельно его разметить, используя пошаговую [[hcalendar-authoring-ru|инструкцию]].&lt;br /&gt;
&lt;br /&gt;
{{authoring-ru|date=&lt;br /&gt;
|authors=&lt;br /&gt;
; Редактор &lt;br /&gt;
: [http://tantek.com/ Tantek Celik] ([http://technorati.com Technorati, Inc])&lt;br /&gt;
; Авторы &lt;br /&gt;
: [http://tantek.com/ Tantek Celik] ([http://technorati.com Technorati, Inc])&lt;br /&gt;
: [http://suda.co.uk/ Brian Suda]&lt;br /&gt;
|rights=}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- TOC START --&amp;gt;&lt;br /&gt;
{{TOC-right}}&lt;br /&gt;
&amp;lt;!-- TOC END --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- ADDED AFTER EDIT === Inspiration and Acknowledgments ===&lt;br /&gt;
Thanks to:&lt;br /&gt;
* Adam Bosworth for leading the [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation] which brought together a critical mass of interested parties. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Введение ==&lt;br /&gt;
Стандарт iCalendar ([http://www.ietf.org/rfc/rfc2445.txt RFC 2445]) уже довольно долгое время используется в сети и в прикладных приложениях (например, iCal в Mac OS X).&lt;br /&gt;
&lt;br /&gt;
В дополнение к этому, блоггеры очень часто обсуждают различные события в своих блогах: грядущие события или описания старых. С добавлением небольших изменений, блоггеры смогут обсуждать события в своём блоге таким образом, что различные поисковые роботы и другие аггрегаторы смогут автоматически их получать, конвертировать в iCalendar, а затем использовать в любых прикладных приложениях или сервисах.&lt;br /&gt;
&lt;br /&gt;
Данная спецификация включает в себя описание формата '''hCalendar''' в качестве проекции стандарта iCalendar на семантический (X)HTML. Таким образом, авторы блогов могут включать данный формат напрямую в свои страницы, а не ссылаться на определённый внешний файл.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Особенности реализации в XHTML ==&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
XHTML is built on XML, and thus XHTML based formats can be used not only for convenient display presentation, but also for general purpose data exchange.  In many ways, XHTML based formats exemplify the best of both HTML and XML worlds.  However, when building XHTML based formats, it helps to have a guiding set of principles.&lt;br /&gt;
&lt;br /&gt;
# Reuse the schema (names, objects, properties, values, types, hierarchies, constraints) as much as possible from pre-existing, established, well-supported standards by reference.  Avoid restating constraints expressed in the source standard.  Informative mentions are ok.&lt;br /&gt;
## For types with multiple components, use nested elements with class names equivalent to the names of the components.&lt;br /&gt;
## Plural components are made singular, and thus multiple nested elements are used to represent multiple text values that are comma-delimited.&lt;br /&gt;
# Use the most accurately precise [[semantic-xhtml|semantic XHTML]] building block for each object etc.&lt;br /&gt;
# Otherwise use a generic structural element (e.g. &amp;lt;code&amp;gt;&amp;amp;lt;span&amp;amp;gt;&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;&amp;amp;lt;div&amp;amp;gt;&amp;lt;/code&amp;gt;), or the appropriate contextual element (e.g. an &amp;lt;code&amp;gt;&amp;amp;lt;li&amp;amp;gt;&amp;lt;/code&amp;gt; inside a &amp;lt;code&amp;gt;&amp;amp;lt;ul&amp;amp;gt;&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;&amp;amp;lt;ol&amp;amp;gt;&amp;lt;/code&amp;gt;).&lt;br /&gt;
# Use class names based on names from the original schema, unless the semantic XHTML building block precisely represents that part of the original schema.  If names in the source schema are case-insensitive, then use an all lowercase equivalent.  Components names implicit in prose (rather than explicit in the defined schema) should also use lowercase equivalents for ease of use. Spaces in component names become dash '-' characters.&lt;br /&gt;
# Finally, if the format of the data according to the original schema is too long and/or not human-friendly, use &amp;lt;code&amp;gt;&amp;amp;lt;abbr&amp;amp;gt;&amp;lt;/code&amp;gt; instead of a generic structural element, and place the literal data into the 'title' attribute (where abbr expansions go), and the more brief and human readable equivalent into the element itself.  Further informative explanation of this use of &amp;lt;code&amp;gt;&amp;amp;lt;abbr&amp;amp;gt;&amp;lt;/code&amp;gt;: [http://tantek.com/log/2005/01.html#d26t0100 Human vs. ISO8601 dates problem solved] --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Стоит заметить, что поддержка &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; в Internet Explorer далека от совершенства и для полной работоспособности данного элемента могут понадобиться другие средства.&lt;br /&gt;
&lt;br /&gt;
См. подробнее [[semantic-xhtml-ru|особенности семантики]].&lt;br /&gt;
&lt;br /&gt;
== Формат ==&lt;br /&gt;
&lt;br /&gt;
=== Детальное описание ===&lt;br /&gt;
Стандарт iCalendar ([http://www.ietf.org/rfc/rfc2445.txt RFC 2445]) является основой для микроформата hCalendar.&lt;br /&gt;
&lt;br /&gt;
Одной из целью hCalendar является использование названий свойств iCalendar в нижнем регистре для имён классов и создания иерархии из XHTML-элементов, похожей на иерархию элементов iCalendar.&lt;br /&gt;
&lt;br /&gt;
=== Имя корневого класса ===&lt;br /&gt;
Корневым классом для hCalendar является '''vcalendar''', отсюда следует, что элемент с таким классом и будет называться hCalendar.&lt;br /&gt;
&lt;br /&gt;
Корневым классом для событий является '''vevent'''. Элемент с таким классом называется '''событием hCalendar''' (hCalendar event).&lt;br /&gt;
&lt;br /&gt;
Для облегчения внедрения формата и его последующей автоматической обработки, оба класса, vevent и vcalendar, считаются корневыми. Если документ содержит элементы с именем класса vevent, но не содержит элементов с классом vcalendar, значит весь документ принимает на себя контекст vcalendar.&lt;br /&gt;
&lt;br /&gt;
=== Свойства и подсвойства ===&lt;br /&gt;
Свойства hCalendar представляют собой вложенные внутри hCalendar (элемента с классом vcalendar или vevent) элементы. Элементы с указанными именами классов содержат в себе значения свойств hCalendar. У некоторых свойств есть подсвойства, которые обладают таким же свойством вложенности элементов.&lt;br /&gt;
&lt;br /&gt;
=== Список свойств ===&lt;br /&gt;
&lt;br /&gt;
'''Обязательные:'''&lt;br /&gt;
* ''dtstart'' ([[iso-8601|дата по ISO-стандарту (англ)]]) &amp;lt;!-- NEED RUSSIAN TRANSL. of ISO-8601 --&amp;gt;&lt;br /&gt;
* ''summary''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Необязательные''':&lt;br /&gt;
* location&lt;br /&gt;
* url&lt;br /&gt;
* dtend (дата по ISO-стандарту), duration (период по ISO-стандарту)&lt;br /&gt;
* rdate, rrule&lt;br /&gt;
* category, description&lt;br /&gt;
* uid&lt;br /&gt;
* geo (latitude, longitude)&lt;br /&gt;
&lt;br /&gt;
''Данный список является незавершённым, но он отображает те свойства, которые используются при разметке hCalendar чаще остальных.'' &lt;br /&gt;
&lt;br /&gt;
=== Семантические эквиваленты ===&lt;br /&gt;
Для некоторых свойств существуют более семантичные эквиваленты, поэтому они распознаются особым образом:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;URL&amp;lt;/code&amp;gt; в iCalendar превращается в &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; внутри элемента &amp;lt;code&amp;gt;class=&amp;quot;vevent&amp;quot;&amp;lt;/code&amp;gt; в hCalendar.&lt;br /&gt;
* &amp;lt;code&amp;gt;ATTENDEE&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;CONTACT&amp;lt;/code&amp;gt; и &amp;lt;code&amp;gt;ORGANIZER&amp;lt;/code&amp;gt; в iCalendar могут быть представлены с помощью микроформата [[hcard-ru|hCard]] в hCalendar .&lt;br /&gt;
* Названный &amp;lt;code&amp;gt;LOCATION&amp;lt;/code&amp;gt; (с адресом и/или географическими координатами) в iCalendar может быть представлен вложенным в hCalendar [[hcard-ru|hCard]]. Подобно ему, адрес в &amp;lt;code&amp;gt;LOCATION&amp;lt;/code&amp;gt; может быть представлен, используя микроформат [[adr-ru|adr]], а географические данные — [[geo-ru|geo]].&lt;br /&gt;
* &amp;lt;code&amp;gt;UID&amp;lt;/code&amp;gt; в iCalendar просто становится URL, где обозначено событие hCalendar.&lt;br /&gt;
&lt;br /&gt;
=== Однозначные и многозначные свойства ===&lt;br /&gt;
&lt;br /&gt;
Для свойств, которые встречаются (должны встречаться) только один раз (подобно ''N'' и ''FN'' из vCard), первый вложенный элемент с таким классом считается эффективным, остальные должны игнорироваться.&lt;br /&gt;
&lt;br /&gt;
Для свойств, которые могут встречаться неоднократно (как ''TEL'' из vCard), каждый элемент с таким классом должен создавать новый экземпляр этого свойства. Многозначные свойства с подтипами (как ''TEL'' с ''WORK'', ''HOME'', ''CELL'' из vCard) могут быть оптимизированы таким образом, чтобы разделять один общий элемент для самого свойства, тогда подтипы становятся потомком элемента, содержащего свойство.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- CAN_OMMIT&lt;br /&gt;
==== Plural Properties Singularized ====&lt;br /&gt;
&lt;br /&gt;
Since plural property names become their singular equivalents, even if the original plural property permitted only a single value with multiple components, those multiple components are represented each with their own singularly named property and the the property is effectively multivalued and subject to the above treatment of multivalued properties. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Удобочитаемость со стороны человека и машины ===&lt;br /&gt;
Если для отображения свойства используется элемент &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;, тогда применённый к нему атрибут &amp;lt;code&amp;gt;title&amp;lt;/code&amp;gt; является значением такого элемента, а не содержимое этого элемента, который, заместо этого, предоставляет удобочитаемый вариант свойства. Данная спецификация рекомендует использовать элемент &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code для отображения таких свойств, как:&lt;br /&gt;
&lt;br /&gt;
* DTSTART&lt;br /&gt;
* DTEND&lt;br /&gt;
* DURATION&lt;br /&gt;
* RDATE&lt;br /&gt;
* RRULE&lt;br /&gt;
&lt;br /&gt;
== Примеры ==&lt;br /&gt;
&lt;br /&gt;
=== iCalendar и hCalendar ===&lt;br /&gt;
&lt;br /&gt;
Пример описания события в iCalendar:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;nowiki&amp;gt;&lt;br /&gt;
BEGIN:VCALENDAR&lt;br /&gt;
PRODID:-//XYZproduct//EN&lt;br /&gt;
VERSION:2.0&lt;br /&gt;
BEGIN:VEVENT&lt;br /&gt;
URL:http://www.web2con.com/&lt;br /&gt;
DTSTART:20071005&lt;br /&gt;
DTEND:20071020&lt;br /&gt;
SUMMARY:Web 2.0 Conference&lt;br /&gt;
LOCATION:Argent Hotel\, San Francisco\, CA&lt;br /&gt;
END:VEVENT&lt;br /&gt;
END:VCALENDAR&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Эквивалентная вышеприведённому примеру разметка hCalendar&lt;br /&gt;
&amp;lt;!-- See [[hcalendar-example1-steps]] for the derivation. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;a class=&amp;quot;url&amp;quot; href=&amp;quot;http://www.web2con.com/&amp;quot;&amp;gt;http://www.web2con.com/&amp;lt;/a&amp;gt;&lt;br /&gt;
  &amp;lt;span class=&amp;quot;summary&amp;quot;&amp;gt;Web 2.0 Conference&amp;lt;/span&amp;gt;: &lt;br /&gt;
  &amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;2007-10-05&amp;quot;&amp;gt;October 5&amp;lt;/abbr&amp;gt;-&lt;br /&gt;
  &amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;2007-10-20&amp;quot;&amp;gt;19&amp;lt;/abbr&amp;gt;,&lt;br /&gt;
 at the &amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt;Argent Hotel, San Francisco, CA&amp;lt;/span&amp;gt;&lt;br /&gt;
 &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Вышеотмеченная разметка hCalendar будет отображена похожим образом:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;url&amp;quot;&amp;gt;http://www.web2con.com/&amp;lt;/span&amp;gt;&amp;amp;nbsp;&amp;lt;!-- note modified to account for idiosyncrasy of wiki software --&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;summary&amp;quot;&amp;gt;Web 2.0 Conference&amp;lt;/span&amp;gt;: &lt;br /&gt;
&amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;2007-10-05&amp;quot;&amp;gt;October 5&amp;lt;/abbr&amp;gt;-&lt;br /&gt;
&amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;2007-10-20&amp;quot;&amp;gt;19&amp;lt;/abbr&amp;gt;,&lt;br /&gt;
at the &amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt;Argent Hotel, San Francisco, CA&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Заметьте, что парсеры уже сейчас могут найти этот микроформат на этой странице. &lt;br /&gt;
&lt;br /&gt;
=== hCalendar с размытым событием ===&lt;br /&gt;
&lt;br /&gt;
Следующий пример отмечает время встречи, которая начинается в 8:30 AM EST, 12 марта 1998 года и заканчивается в 9:30 AM EST, 12 марта 1998 года.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
     BEGIN:VCALENDAR&lt;br /&gt;
     BEGIN:VEVENT&lt;br /&gt;
     UID:guid-1.host1.com&lt;br /&gt;
     DTSTAMP:19980309T231000Z&lt;br /&gt;
     DESCRIPTION:Project XYZ Review Meeting&lt;br /&gt;
     SUMMARY:XYZ Project Review&lt;br /&gt;
     DTSTART:19980312T133000Z&lt;br /&gt;
     DTEND:19980312T143000Z&lt;br /&gt;
     LOCATION:1CP Conference Room 4350&lt;br /&gt;
     END:VEVENT&lt;br /&gt;
     END:VCALENDAR&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Эквивалент вышеприведённому примеру:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;h3 class=&amp;quot;summary&amp;quot;&amp;gt;XYZ Project Review&amp;lt;/h3&amp;gt;&lt;br /&gt;
&amp;lt;p class=&amp;quot;description&amp;quot;&amp;gt;Project XYZ Review Meeting&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;To be held on &amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;1998-03-12T08:30:00-05:00&amp;quot;&amp;gt;12 March 1998 from 8:30am EST&amp;lt;/abbr&amp;gt; &lt;br /&gt;
until &amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;1998-03-12T09:30:00-05:00&amp;quot;&amp;gt;9:30am EST&amp;lt;/abbr&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Location: &amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt;1CP Conference Room 4350&amp;lt;/span&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;small&amp;gt;Booked by: &amp;lt;span class=&amp;quot;uid&amp;quot;&amp;gt;guid-1.host1.com&amp;lt;/span&amp;gt; on &lt;br /&gt;
&amp;lt;abbr class=&amp;quot;dtstamp&amp;quot; title=&amp;quot;19980309T231000Z&amp;quot;&amp;gt;9 Mar 1998 6:00pm&amp;lt;/abbr&amp;gt;&amp;lt;/small&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Его возможное отображение:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;h3 class=&amp;quot;summary&amp;quot;&amp;gt;XYZ Project Review&amp;lt;/h3&amp;gt;&lt;br /&gt;
&amp;lt;p class=&amp;quot;description&amp;quot;&amp;gt;Project XYZ Review Meeting&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;To be held on &amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;1998-03-12T08:30:00-05:00&amp;quot;&amp;gt;12 March 1998 from 8:30am EST&amp;lt;/abbr&amp;gt; &lt;br /&gt;
until &amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;1998-03-12T09:30:00-05:00&amp;quot;&amp;gt;9:30am EST&amp;lt;/abbr&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Location: &amp;lt;span class=&amp;quot;location&amp;quot;&amp;gt;1CP Conference Room 4350&amp;lt;/span&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;small&amp;gt;Booked by: &amp;lt;span class=&amp;quot;uid&amp;quot;&amp;gt;guid-1.host1.com&amp;lt;/span&amp;gt; on &amp;lt;abbr class=&amp;quot;dtstamp&amp;quot; title=&amp;quot;19980309T231000Z&amp;quot;&amp;gt;9 Mar 1998 6:00pm&amp;lt;/abbr&amp;gt;&amp;lt;/small&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Примечания к примеру ====&lt;br /&gt;
# Информация о продукте необязательна, так как hCalendar — формат для обмена. Когда hCalendar трансформируется обратно в iCalendar, сам транскодер может добавить его собственный ID (product ID).&lt;br /&gt;
# Окружение hCalendar элементом &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;span class=&amp;quot;vcalendar&amp;quot;&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; является необязательным, поэтому данный элемент в примере опущен. Если элемент vcalendar опускается, то vevent начинает принадлежать ко всему документу в целом, который в данном случае игрет роль vcalendar-контейнера. Авторы разметки могут напрямую указывать элементы с vcalendar, если у них, к примеру, на странице содержится несколько календарей, событийных веток.&lt;br /&gt;
# Информация о версии в hCalendar необязательна, так как её можно получить через атрибут ''profile'' элемента head.&lt;br /&gt;
# Даты по стандарту [[iso-8601|ISO 8601]] (требуемые стандартом iCalendar) не являются слишком дружелюбными человеческому глазу. В добавление к этому, год часто распознаётся читателями из контекста. Именно поэтому спецификация рекомендует использовать элемент &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;, с помощью которого можно вынести неудобочитаемые данные в атрибут ''title'', а приемлемые для осознавания сведения поместить в сам элемент.&lt;br /&gt;
## Для улучшения удобочитаемости следует использовать указанный в RFC 3339 формат данных: &amp;lt;code&amp;gt;YYYY-MM-DDThh:mm:ss&amp;lt;/code&amp;gt;&lt;br /&gt;
# Разница между ISO 8601 датой DTEND (2005-10-08) и удобочитаемой датой (7) '''не''' является ошибкой. [http://lists.osafoundation.org/pipermail/ietf-calsify/2005-September/000769.html DTEND — уникальное значение]. Это значит, что события кончается прямо '''перед''' DTEND. Для событий, начинающихся в один день и заканчивающихся в другой, дата в DTEND должна быть указана на день позже актуальной. &lt;br /&gt;
# Местоположение в данном примере непосредственно содержит в себе данные, которые можно было бы разметить с помощью [[hcard-ru|hCard]].&lt;br /&gt;
&lt;br /&gt;
=== Другие примеры ===&lt;br /&gt;
См. [[hcalendar-examples-ru|другие примеры hCalendar]].&lt;br /&gt;
&lt;br /&gt;
=== Примеры в сети ===&lt;br /&gt;
См. отдельную страницу с [[hcalendar-examples-in-wild-ru|примерами в сети]].&lt;br /&gt;
&lt;br /&gt;
== Кнопки ==&lt;br /&gt;
&lt;br /&gt;
* http://www.boogdesign.com/images/buttons/microformat_hcalendar.png&lt;br /&gt;
* См. [[buttons-ru#hCalendar|другие кнопки]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Реализации ==&lt;br /&gt;
См. [[hcalendar-implementations-ru|реализации]].&lt;br /&gt;
&lt;br /&gt;
== Ссылки ==&lt;br /&gt;
&lt;br /&gt;
=== Нормативные ===&lt;br /&gt;
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]&lt;br /&gt;
* [[hcard-ru|hCard]]&lt;br /&gt;
* [http://www.ietf.org/rfc/rfc2445.txt iCalendar RFC 2445]&lt;br /&gt;
* [[rfc-2119| RFC 2119]]&lt;br /&gt;
* [[iso-8601|ISO 8601]]&lt;br /&gt;
&lt;br /&gt;
=== Информативные ===&lt;br /&gt;
* [http://w3.org/TR/REC-CSS1 CSS1]&lt;br /&gt;
* [http://tantek.com/log/2004/09.html#hcalendar Введение термина hCalendar]&lt;br /&gt;
* [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars HTML для представления календарных событий]&lt;br /&gt;
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats Simple Semantic Formats]&lt;br /&gt;
* [http://ietfreport.isoc.org/idref/draft-royer-ical-basic/ iCal-Basic]  [http://www.faqs.org/ftp/pub/pub/internet-drafts/draft-royer-ical-basic-04.txt iCal-Basic (редакция)]&lt;br /&gt;
* [http://www.w3.org/TR/NOTE-datetime W3C относительно форматов даты и времени]&lt;br /&gt;
* [http://www.imc.org/pdi/ Internet Mail Consortium: vCard и vCalendar]&lt;br /&gt;
* См. также [http://developers.technorati.com/wiki/hCalendar Technorati Wiki для разработчиков]&lt;br /&gt;
&lt;br /&gt;
==== Связанные спецификации ====&lt;br /&gt;
* [[hreview-ru|hReview]]&lt;br /&gt;
&lt;br /&gt;
==== Связанные работы ====&lt;br /&gt;
* [http://lists.osafoundation.org/pipermail/ietf-calsify/ IETF-архивы]&lt;br /&gt;
* [http://www.softwarestudio.org/iCal/2445Issues.html Вопросы к RFC 2445]&lt;br /&gt;
* [http://ietf.webdav.org/calsify/ CALSIFY, ссылки и ресурсы]&lt;br /&gt;
&lt;br /&gt;
==== Дополнительный материал ====&lt;br /&gt;
* [http://www.livejournal.com/users/jwz/444651.html JWZ - Hula]&lt;br /&gt;
* [http://www.jwz.org/doc/groupware.html Groupware Bad от Jamie Zawinski]&lt;br /&gt;
* [http://muddybranch.thejkgroup.com/ Блог Jason Klemow]&lt;br /&gt;
* [http://weblog.infoworld.com/udell/2006/01/11.html#a1368 «Движение вперёд с микроформатами»] от [http://weblog.infoworld.com/udell Jon Udell].&lt;br /&gt;
* См. также [http://www.technorati.com/cosmos/referer.html блоги с обсуждениям] и статьи, отмеченные меткой [http://technorati.com/tags/hcalendar hCalendar].&lt;br /&gt;
* [http://en.wikipedia.org/wiki/HCalendar Wikipedia о hCalendar]&lt;br /&gt;
&lt;br /&gt;
==== Связанные страницы ====&lt;br /&gt;
* [[hcalendar-authoring-ru|Информация о внедрении hCalendar]] &lt;br /&gt;
* [http://microformats.org/code/hcalendar/creator Генератор hCalendar]&lt;br /&gt;
* [[hcalendar-cheatsheet|Подсказки hCalendar]]&lt;br /&gt;
* [[hcalendar-faq-ru|hCalendar FAQ]]&lt;br /&gt;
* [[hcalendar-parsing-ru|Автоматическая обработка hCalendar]]&lt;br /&gt;
* [[hcalendar-profile-ru|XMDP-профиль hCalendar]]&lt;br /&gt;
* [[hcalendar-tests-ru|Тесты парсерам hCalendar]]&lt;br /&gt;
&amp;lt;!-- * [[to-do#hCalendar|hCalendar &amp;quot;to do&amp;quot;]] - jobs to do --&amp;gt;&lt;br /&gt;
&amp;lt;!-- * [[advocacy#hCalendar|hCalendar advocacy]] - encourage others to use hCalendar. --&amp;gt;&lt;br /&gt;
* [[icalendar-implementations-ru|Реализации iCalendar]]&lt;/div&gt;</summary>
		<author><name>Alik</name></author>
	</entry>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=hcard-ru&amp;diff=43036</id>
		<title>hcard-ru</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=hcard-ru&amp;diff=43036"/>
		<updated>2010-09-05T20:21:20Z</updated>

		<summary type="html">&lt;p&gt;Alik: Syntax highlighting&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{working-ru|original=hcard}}&lt;br /&gt;
&amp;lt;h1&amp;gt;hCard&amp;lt;/h1&amp;gt;&lt;br /&gt;
hCard — это простой, открытый микроформат для описания людей, компаний, организаций и мест, используя всю мощь vCard ([[rfc-2426|RFC 2426 (англ.)]]). Имена классов hCard полностью отображают имена соответствующих полей vCard на [[semantic-xhtml-ru|семантический (X)HTML]]. hCard — это один из открытых [[microformats-ru|микроформатов]], который можно внедрить в HTML, XHTML, ATOM, RSS и XML.&lt;br /&gt;
&lt;br /&gt;
Хотите разметить собственный hCard? Попробуйте начать с [http://microformats.org/code/hcard/creator генератора hCard] или создайте разметку данного микроформата самостоятельно, следуя [[hcard-authoring-ru|подсказкам]] по внедрению на существующие страницы.&lt;br /&gt;
&lt;br /&gt;
{{authoring-ru|date=|authors=&lt;br /&gt;
&amp;lt;div class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
; &amp;lt;span class=&amp;quot;role&amp;quot;&amp;gt;Редактор&amp;lt;/span&amp;gt; &lt;br /&gt;
: &amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;[[User:Tantek|Tantek Celik]]&amp;lt;/span&amp;gt; (&amp;lt;span class=&amp;quot;url&amp;quot;&amp;gt;http://tantek.com/&amp;lt;/span&amp;gt;, ранее в [http://technorati.com Technorati, Inc.], и в [http://microsoft.com/ Microsoft Corporation])&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
; Авторы: [http://tantek.com/ Tantek Celik] (членство в организациях указано выше)&lt;br /&gt;
: &amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;fn&amp;quot;&amp;gt;[[User:Brian|Brian Suda]]&amp;lt;/span&amp;gt; (&amp;lt;span class=&amp;quot;url&amp;quot;&amp;gt;http://suda.co.uk/&amp;lt;/span&amp;gt;)&amp;lt;/span&amp;gt;&lt;br /&gt;
|rights=&lt;br /&gt;
; Официальные подтверждения: См. [[hcard#Официальные подтверждения|официальные подтверждения]].&lt;br /&gt;
; Защита прав&lt;br /&gt;
: См. [[hcard#Авторские права|авторские права]] и заявки на [[hcard#Патенты|патенты]].}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- TOC START --&amp;gt;&lt;br /&gt;
{{TOC-right}}&lt;br /&gt;
&amp;lt;!-- TOC END --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Введение ==&lt;br /&gt;
Стандарт vCard ([[rfc-2426|RFC 2426 (англ.)]]) был широко внедрен для обеспечения взаимодействия между различными приложениями (например, приложение «Address Book» компании Apple, встроенное в Mac OS X).Помимо этого, многие блоггеры идентифицируют себя по имени и обсуждают своих друзей и семью на страницах блогов. С помощью небольшой структуризации, блоггеры могут обсуждать (описывать) людей в своих блогах таким образом, что поисковые роботы и другие программы-обработчики смогут запросить эту информацию, автоматически конвертируя её в vCard и используя её впоследствии в любом сервисе или приложении, работающем с vCard.&lt;br /&gt;
&lt;br /&gt;
Эта спецификация представляет формат '''hCard''', который проецирует вышеупомянутый стандарт vCard в семантический HTML. Блоггеры могут внедрять hCard напрямую в Web-документы и оформлять их спомощью CSS для придания им желаемого внешнего вида. Также hCard позволяет приложениям запрашивать информацию прямиком из Web-документов, без обращений к отдельным файлам.&lt;br /&gt;
&lt;br /&gt;
Вы можете использовать [http://microformats.org/code/hcard/creator генератор hCard] и скопировать HTML-код, который он сгенерирует, в ваш блог или Web-сайт для публикации контактной информации.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- {{rfc-2119-intro}} --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Формат ==&lt;br /&gt;
&lt;br /&gt;
=== Особенности ===&lt;br /&gt;
Основополагающим стандартом для hCard является vCard. &lt;br /&gt;
&lt;br /&gt;
В hCard используются имена объектов/свойств vCard, преобразованные в нижний регистр для использования в качетсве имён классов и для создания иерархии HTML-элементов.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Корневой класс ===&lt;br /&gt;
Корневым классом для hCard является &amp;quot;vcard&amp;quot;. Элемент с именем класса &amp;quot;vcard&amp;quot; называется ''hCard''. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Свойства ===&lt;br /&gt;
Свойства hCard — это элементы внутри hCard. Элементы с именами классов указанных свойств представляют собой значения таких свойств. Некоторые свойства могут иметь более сложную вложенную структуру других свойств, но в целом их структура идентична.&lt;br /&gt;
&lt;br /&gt;
=== Список свойств ===&lt;br /&gt;
Свойства hCard&lt;br /&gt;
&lt;br /&gt;
'''Обязательные:'''&lt;br /&gt;
* '''fn'''&lt;br /&gt;
* &amp;lt;span id=&amp;quot;property-list-n&amp;quot;&amp;gt;'''n'''&amp;lt;sup style=&amp;quot;font-size:smaller&amp;quot;&amp;gt;[[#note1|1]]&amp;lt;/sup&amp;gt; (family-name, given-name, additional-name, honorific-prefix, honorific-suffix)&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Необязательные''':&lt;br /&gt;
* nickname, sort-string&lt;br /&gt;
* url, email (тип, значение), &amp;lt;span id=&amp;quot;property-list-tel&amp;quot;&amp;gt;tel&amp;lt;sup style=&amp;quot;font-size:smaller&amp;quot;&amp;gt;[[#note2|2]]&amp;lt;/sup&amp;gt; (тип, значение)&amp;lt;/span&amp;gt;&lt;br /&gt;
* adr (post-office-box, extended-address, street-address, locality, region, postal-code, country-name, type, value), label&lt;br /&gt;
* geo (latitude, longitude), tz&lt;br /&gt;
* photo, logo, sound, bday&lt;br /&gt;
* title, role, org (organization-name, organization-unit)&lt;br /&gt;
* category, note&lt;br /&gt;
* class, key, mailer, uid, rev&lt;br /&gt;
&lt;br /&gt;
=== Дополнительные указания ===&lt;br /&gt;
&amp;lt;span id=&amp;quot;note1&amp;quot;&amp;gt;[[#property-list-n|1. ^]]&amp;lt;/span&amp;gt;: ''n'' не является обязательным атрибутом (см. [[hcard#Оптимизация раздел об оптимизации]]&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;span id=&amp;quot;note2&amp;quot;&amp;gt;[[#property-list-tel|2. ^]]&amp;lt;/span&amp;gt;: Используя ''tel'', авторы могут следовать стандарту [http://en.wikipedia.org/wiki/E.123 E.123] для записи телефонных номеров. Символьные значения (например, +1-555-FORMATS) должны быть сконвертированы в числа. Используйте &amp;lt;code&amp;gt;abbr&amp;lt;/code&amp;gt;, чтобы отображать символьное представление и предоставлять числовое значение. Например:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr title=&amp;quot;+15553676287&amp;quot;&amp;gt;+1-555-FORMATS&amp;lt;/abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=== Единичные и множественные свойства ===&lt;br /&gt;
Список свойств, которые должны однозначно использоваться в формате (только один раз):&lt;br /&gt;
* 'fn'&lt;br /&gt;
* 'n'&lt;br /&gt;
* 'bday'&lt;br /&gt;
* 'tz'&lt;br /&gt;
* 'geo'&lt;br /&gt;
* 'sort-string'&lt;br /&gt;
* 'uid'&lt;br /&gt;
* 'class'&lt;br /&gt;
&lt;br /&gt;
Для таких свойств только первый дочерний элемент с таким классом должен иметь значение, остальные должны игнорироваться.&lt;br /&gt;
&lt;br /&gt;
Все другие свойства могут встречаться несколько раз. Каждый новый подобный класс создаёт новый параметр со значением данного свойства.&lt;br /&gt;
&lt;br /&gt;
=== Читабельность для человека и машины ===&lt;br /&gt;
Человеку доступно всё, что является содержимым элементов (это, собственно, и является содержимым определённого свойства микроформата), с некоторыми нюансами:&lt;br /&gt;
&lt;br /&gt;
* Если элемент ''&amp;lt;code&amp;gt;abbr&amp;lt;/code&amp;gt;'' используется для описания свойства, то атрибут ''&amp;lt;code&amp;gt;title&amp;lt;/code&amp;gt;'' (если обозначен) данного элемента является значением данного свойства, вместо содержимого данного элемента, которое, в данном случае, предоставляет более приемлемую для осознавания человеком информацию.&lt;br /&gt;
* Если для одного или нескольких свойств используется элемент ''&amp;lt;code&amp;gt;a&amp;lt;/code&amp;gt;'', он должен трактоваться следующим образом:&lt;br /&gt;
** Для свойства ''photo'' и любого другого свойства, состоящего из URI, значением является значение атрибута ''href''.&lt;br /&gt;
** Для любых других свойств значением является содержимое элемента.&lt;br /&gt;
* Если для одного или нескольких свойств используется элемент img, он должен трактоваться следующим образом:&lt;br /&gt;
** Для свойства ''photo'' и любого другого свойства, которое получает URI в качестве своего значения, значением является значение атрибута ''src''.&lt;br /&gt;
** Для других свойств, атрибут ''alt'' содержит в себе их значение.&lt;br /&gt;
* Если используется элемент ''object'' для указания одного или нескольких свойств, он должен распознаваться следующим образом:&lt;br /&gt;
** Для свойства ''photo'' и подобных этому свойству свойств, атрибут ''data'' является значением таких свойств.&lt;br /&gt;
** Для других свойств, содержимое элемента является их значением.&lt;br /&gt;
&lt;br /&gt;
=== Частичные значения ===&lt;br /&gt;
Иногда только часть элемента используется как значение определённого свойства. Такое часто происходит в тот момент, когда у свойства есть подтип (например, ''tel''). В данном случае используется специальное имя класса ''value'', чтобы выделить ту часть элемента, которая и будет являться значением свойства. &lt;br /&gt;
&lt;br /&gt;
Вот фрагмент hCard для разметки домашнего номера телефона:&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
vCard:&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
TEL;TYPE=HOME:+1.415.555.1212&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
hCard:&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Домашний телефон&amp;lt;/span&amp;gt;:&lt;br /&gt;
 &amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt;+1.415.555.1212&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Данный фрагмент hCard будет отображён следующим образом:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;border: thin dashed black; width: 95%; padding: .5em 1em;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Домашний телефон&amp;lt;/span&amp;gt;:&lt;br /&gt;
&amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt;+1.415.555.1212&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- &lt;br /&gt;
	note for Tantek: review/edit property casing from here on &lt;br /&gt;
	RUSSIAN_TRANSLATION_STANDART&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Исключения из свойств ===&lt;br /&gt;
У стандарта vCard есть несколько свойств, которые не играют особой роли или их роль берут на себя другие элементы на Web-странице. Этот раздел описывает, что с ними нужно делать.&lt;br /&gt;
&lt;br /&gt;
# Свойства '''NAME''', '''PROFILE''', '''SOURCE''', '''PRODID''', '''VERSION''' в vCard (как определено в разделах .1.2, 2.1.3, 2.1.4, 3.6.3, 3.6.9 [[rfc-2426-ru|RFC 2426]]. Авторы не должны использовать эти свойства в своих hCard, так же как и парсеры должны '''игнорировать''' данные свойства, если они будут обнаружены при обработке hCard. Напротив, конвертерам hCard-в-vCard следует использовать заголовок страницы, где hCard был обнаружен (элемент ''title'' в (X)HTML-документах), чтобы создать свойство NAME, могут вывести свойство PROFILE в соответствии с [[rfc-2426-ru|RFC 2426]], могут использовать URI страницы, где был обнаружен hCard, чтобы заполнить свойство SOURCE. Только приложения, которые создают vCard, должны записывать свойства PRODIF и VERSION (3.0) в соответствии с [[rfc-2426-ru|RFC 2426]].&lt;br /&gt;
&lt;br /&gt;
=== Информация об организации ===&lt;br /&gt;
Если свойства ''FN'' и ''ORG'' имеют одинаковые значения (например, данные классы могут относится к одному элементу, подобно ''class=&amp;quot;fn org&amp;quot;''), hCard представляет собой информацию о связи с компанией, организацией и их следует считать такими. В этом случае авторы '''не должны''' использовать свойство ''N'', но они могут устанавливать их в пустую строку. Из этого следует, что парсеры должны поступать таким же образом.&lt;br /&gt;
&lt;br /&gt;
=== Рекомендации по оптимизации ''n'' ===&lt;br /&gt;
Несмотря на то, что vCard обязует использовать свойство ''N'', сами авторы спецификации vCard не включают это свойство почти до конца спецификации (бывает и такое, да). Данное противоречие может быть разрешено следующим путём: необходимо позволить свойству ''FN'' заменять своим присутствием свойство ''N''. Это и было сделано в hCard. &lt;br /&gt;
&lt;br /&gt;
Если свойства ''FN'' и ''ORG'' не совпадают (см. предыдущий раздел) и значение свойства ''FN'' равно двум словам, разделённых пробелом и не указано свойство ''N'', то свойство ''N'' «получается» из свойства ''FN''. Если же ''FN'' не состоит ровно из двух слов, то авторы обязаны разметить свойство ''N'', если они не создают hCard для организации, конечно.&lt;br /&gt;
&lt;br /&gt;
# Содержимое ''FN'' разбито на два слова, разделённых пробелом.&lt;br /&gt;
# ''Первое'' слово в свойстве ''FN'' — это ''given-name'' для свойства ''N''.&lt;br /&gt;
# ''Второе (последнее)'' слово в этом свойстве интерпретируется как ''family-name'' для свойства ''N''.&lt;br /&gt;
# '''Исключение''': если первое слово заканчивается запятой «,» '''или''' второе слово состоит только из одного символа (после которого может  следовать точка «.»), то первое слово (не считая запятой) интерпретируется как ''family-name'', а второе слово — как ''given-name''.&lt;br /&gt;
&lt;br /&gt;
Вот примеры типичных ситуаций:&lt;br /&gt;
* given-name (пробел) family-name&lt;br /&gt;
* family-name (запятая) given-name&lt;br /&gt;
* family-name (запятая) given-name-first-initial&lt;br /&gt;
* family-name (пробел) given-name-first-initial (необязательная точка)&lt;br /&gt;
&lt;br /&gt;
=== Рекомендации по оптимизации ''nickname'' ===&lt;br /&gt;
Исходя из того, что в сети Интернет, в основном, используются никнеймы/псевдонимы для указания человека (автора), hCard также включает в себя свойство ''nickname''.&lt;br /&gt;
&lt;br /&gt;
По аналогии с оптимизацией ''n'', если свойства ''FN'' и ''ORG'' не совпадают и значением свойства ''FN'' является ровно одно слово, при этом отдельного свойства ''N'' не указано, то: &lt;br /&gt;
&lt;br /&gt;
# Содержимое ''FN'' должно считаться значением свойства ''nickname''.&lt;br /&gt;
# Обработчикам (парсерам) следует заполнить пустыми значениями пропущенное свойство ''N''. &lt;br /&gt;
&lt;br /&gt;
Авторы hCard должны непосредственно указывать свойство ''nickname'', например:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
	&amp;lt;span class=&amp;quot;fn nickname&amp;quot;&amp;gt;daveman692&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
hCard может иметь отдельный элемент с классом ''nickname'', значение которого и будет являться значением одноимённого свойства.&lt;br /&gt;
&lt;br /&gt;
=== Оптимизации ''organization-name'' ===&lt;br /&gt;
Свойство ''ORG'' включает в себя два подсвойства: ''organization-name'' и ''organization-unit''. Очень часто авторы публикуют только ''organization-name''. Из этого следует, что если ''organization-name'' не указано внутри ''ORG'', содержимое ''ORG'' должно трактоваться как ''organization-name''.&lt;br /&gt;
&lt;br /&gt;
=== Теги как категории ===&lt;br /&gt;
Категории в hCard могут быть представлены как теги c использованием микроформата [[rel-tag-ru|rel-tag]]. Когда категория размечена с помощью rel-tag, сам тег (как определено спецификацией rel-tag) и является этой категорией. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Пары значений ''type'' и ''value'' ===&lt;br /&gt;
Подсвойство ''type'' может принимать различные значения, зависящие от того, к какому свойству оно принадлежит. Значения данного подсвойства являются нечувствительными к регистру (это значит, что «Рабочий» — то же самое, что и «рабочий»). Пример:&lt;br /&gt;
&lt;br /&gt;
vCard:&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
TEL;TYPE=HOME,PREF:+1.415.555.1212&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
hCard:&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Home&amp;lt;/span&amp;gt; (&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;pref&amp;lt;/span&amp;gt;erred):&lt;br /&gt;
 &amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt;+1.415.555.1212&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Будет показано следующим образом:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;border: thin dashed black; width: 95%; padding: .5em 1em; &amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Home&amp;lt;/span&amp;gt; (&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;pref&amp;lt;/span&amp;gt;erred):&lt;br /&gt;
&amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt;+1.415.555.1212&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== ''type'' без указанного ''value'' ====&lt;br /&gt;
Когда указан ''type'' свойства и не указан ''value'' свойства, всё, что не является ''type'', считается ''value'' данного свойства, например:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Home&amp;lt;/span&amp;gt; +1.415.555.1212&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Равносильно следующему:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;tel&amp;quot;&amp;gt;&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Home&amp;lt;/span&amp;gt;&amp;lt;span class=&amp;quot;value&amp;quot;&amp;gt; +1.415.555.1212&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Следовательно, ''type'' — это «home», а значение — это «+1.415.555.1212»&lt;br /&gt;
&lt;br /&gt;
==== Возможные значения ''type'' для adr, tel и email ====&lt;br /&gt;
&amp;lt;em&amp;gt;См. также разделы 3.2.1 ADR, 3.3.1 TEL и 3.3.2 EMAIL в [[rfc-2426-ru|RFC 2426]] для нормативных сведений. Значение по умолчанию (даже если это несколько значений) — это первое значение в данном списке. &lt;br /&gt;
&lt;br /&gt;
* '''adr''': INTL, POSTAL, PARCEL, WORK, dom, home, pref&lt;br /&gt;
* '''tel''': VOICE, home, msg, work, pref, fax, cell, video, pager, bbs, modem, [http://flickr.com/photos/tags/carcellphone/ car], isdn, pcs&lt;br /&gt;
* '''email''': INTERNET, x400, pref, &amp;quot;other IANA registered address types&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Профиль XMDP ===&lt;br /&gt;
&lt;br /&gt;
См. [http://gmpg.org/xmdp XMDP] [[hcard-profile-ru|профиль hCard]], который содержит все указанные выше свойства.&lt;br /&gt;
&lt;br /&gt;
=== Информация об обработке ===&lt;br /&gt;
&lt;br /&gt;
См. [[hcard-parsing|обработка hCard]].&lt;br /&gt;
&lt;br /&gt;
== Примеры ==&lt;br /&gt;
&amp;lt;em&amp;gt;Данный раздел является информативным&amp;lt;/em&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Пример vCard ===&lt;br /&gt;
&lt;br /&gt;
Это пример vCard:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
BEGIN:VCARD&lt;br /&gt;
VERSION:3.0&lt;br /&gt;
N:Celik;Tantek&lt;br /&gt;
FN:Tantek Celik&lt;br /&gt;
URL:http://tantek.com/&lt;br /&gt;
END:VCARD&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
и эквивалент вышеприведённого vCard в разметке hCard: &amp;lt;!-- NOTE_TRANS:  See [[hcard-example1-steps| hCard Example 1]] for the derivation.  --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
	&amp;lt;a class=&amp;quot;url fn&amp;quot; href=&amp;quot;http://tantek.com/&amp;quot;&amp;gt;Tantek Celik&amp;lt;/a&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Этот hCard будет отображён следующим образом:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;border: thin dashed black; width: 95%; padding: .5em 1em;&amp;quot;&amp;gt;&lt;br /&gt;
[http://tantek.com/ Tantek Celik]&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''Замечание: информацию о версии не обязательно указывать в разметке hCard, так как эта информация будет включена в профиль hCard,  который будет использован путём утилизации атрибута '''profile''' в HTML-элементе '''head'''.''&lt;br /&gt;
&lt;br /&gt;
=== Пример ===&lt;br /&gt;
&lt;br /&gt;
Информация о связи с компанией [http://www.commerce.net/ Commercenet]. Данный мимкроформат уже сейчас можно определить на этой странице с помощью различных утилит. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;fn org&amp;quot;&amp;gt;'''CommerceNet'''&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;url&amp;quot;&amp;gt;'''&amp;lt;nowiki&amp;gt;http://www.commerce.net/&amp;lt;/nowiki&amp;gt;'''&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;adr&amp;quot;&amp;gt;'''&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Work&amp;lt;/span&amp;gt;:'''&lt;br /&gt;
&amp;lt;div class=&amp;quot;street-address&amp;quot;&amp;gt;'''169 University Avenue'''&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;span class=&amp;quot;locality&amp;quot;&amp;gt;'''Palo Alto'''&amp;lt;/span&amp;gt;, &amp;lt;span class=&amp;quot;region&amp;quot;&amp;gt;'''CA'''&amp;lt;/span&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;span class=&amp;quot;postal-code&amp;quot;&amp;gt;'''94301'''&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;country-name&amp;quot;&amp;gt;'''USA'''&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;tel&amp;quot;&amp;gt;'''&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Work&amp;lt;/span&amp;gt; +1-650-289-4040'''&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;tel&amp;quot;&amp;gt;'''&amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Fax&amp;lt;/span&amp;gt; +1-650-289-4041'''&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div&amp;gt;'''Email &amp;lt;span class=&amp;quot;email&amp;quot;&amp;gt;&amp;lt;nowiki&amp;gt;info@commerce.net&amp;lt;/nowiki&amp;gt;&amp;lt;/span&amp;gt;'''&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Ниже представлена разметка с некоторыми семантическими улучшениями:&lt;br /&gt;
* &amp;lt;code&amp;gt;abbr&amp;lt;/code&amp;gt; используется для аббревиатур&lt;br /&gt;
* Имя организации представлено в виде ссылки&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=html4strict&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;vcard&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;a class=&amp;quot;fn org url&amp;quot; href=&amp;quot;http://www.commerce.net/&amp;quot;&amp;gt;CommerceNet&amp;lt;/a&amp;gt;&lt;br /&gt;
  &amp;lt;div class=&amp;quot;adr&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Work&amp;lt;/span&amp;gt;:&lt;br /&gt;
    &amp;lt;div class=&amp;quot;street-address&amp;quot;&amp;gt;169 University Avenue&amp;lt;/div&amp;gt;&lt;br /&gt;
    &amp;lt;span class=&amp;quot;locality&amp;quot;&amp;gt;Palo Alto&amp;lt;/span&amp;gt;,  &lt;br /&gt;
    &amp;lt;abbr class=&amp;quot;region&amp;quot; title=&amp;quot;California&amp;quot;&amp;gt;CA&amp;lt;/abbr&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&lt;br /&gt;
    &amp;lt;span class=&amp;quot;postal-code&amp;quot;&amp;gt;94301&amp;lt;/span&amp;gt;&lt;br /&gt;
    &amp;lt;div class=&amp;quot;country-name&amp;quot;&amp;gt;USA&amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;div class=&amp;quot;tel&amp;quot;&amp;gt;&lt;br /&gt;
   &amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Work&amp;lt;/span&amp;gt; +1-650-289-4040&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;div class=&amp;quot;tel&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;span class=&amp;quot;type&amp;quot;&amp;gt;Fax&amp;lt;/span&amp;gt; +1-650-289-4041&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;div&amp;gt;Email: &lt;br /&gt;
   &amp;lt;span class=&amp;quot;email&amp;quot;&amp;gt;info@commerce.net&amp;lt;/span&amp;gt;&lt;br /&gt;
  &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Дополнительные примеры ===&lt;br /&gt;
Дополнительные примеры вы найдёте на странице [[hcard-examples-ru|примеров hCard]]. Там также представлены примеры конвертированных из vCard hCard.&lt;br /&gt;
&lt;br /&gt;
== Кнопки ==&lt;br /&gt;
Вы можете использовать следующие кнопки на вашей странице вместе с микроформатом hCard: &amp;lt;!-- [[buttons#hCard]] --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* http://www.davidjanes.com/images/mf_hcard.png&lt;br /&gt;
* http://rbach.priv.at/2006/buttons/hcard.png&lt;br /&gt;
* http://www.boogdesign.com/images/buttons/microformat_hcard.png&lt;br /&gt;
&amp;lt;!-- * CSS-powered button, as evidenced at [http://re-run.com/about/microformat-badges microformat badges @ re-run] --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Примеры в сети ==&lt;br /&gt;
Данный раздел является информативным. Количество примеров в сети очень большое, поэтому было решено переместить их на [[hcard-examples-in-wild-ru|отдельную страницу]]&lt;br /&gt;
&lt;br /&gt;
== Реализации ==&lt;br /&gt;
Данный раздел является информативным. &lt;br /&gt;
&lt;br /&gt;
См. [[hcard-implementations-ru|реализации]].&lt;br /&gt;
&lt;br /&gt;
== Ссылки ==&lt;br /&gt;
=== Нормативные ===&lt;br /&gt;
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]&lt;br /&gt;
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC 2426]&lt;br /&gt;
* [http://www.itu.int/rec/T-REC-E.123-200102-I/en Рекомендации ITU E.123] по записи телефонных номеров&lt;br /&gt;
* [[rfc-2119-ru|RFC 2119]]&lt;br /&gt;
&lt;br /&gt;
=== Информативные ===&lt;br /&gt;
* [[hcard-history-ru|История hCard]]&lt;br /&gt;
** [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats Презентация «Simple Semantic Formats» на FOO Camp 2004 (10 сентября 2004)]&lt;br /&gt;
** [http://tantek.com/log/2004/09.html#hcard Введение термина hCard (30 сентября 2004)]&lt;br /&gt;
** Некоторые материалы взяты с [http://developers.technorati.com/wiki/hCard Technorati Wiki для разработчиков]&lt;br /&gt;
* [http://www.dante.net/np/ds/osi/9594-6-X.520.A4.ps X.520 в Postscript] ([http://72.14.253.104/search?q=cache:FjqzsFu4h20J:www.dante.net/np/ds/osi/9594-6-X.520.A4.ps Google Cached материал]) - информация об свойстве ROLE.&lt;br /&gt;
* [http://www.w3.org/2002/12/cal/rfc2426 HTML-версия RFC 2426]&lt;br /&gt;
* [http://w3.org/TR/REC-CSS1 CSS1]&lt;br /&gt;
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]&lt;br /&gt;
* [http://en.wikipedia.org/wiki/E.123 Статья в Wikipedia о рекоменациях ITU-T по E.123] - для значений &amp;quot;TEL&amp;quot;.&lt;br /&gt;
* [http://www.imc.org/pdi/ vCard и vCalendar (Internet Mail Consortium)]&lt;br /&gt;
* [[iso-8601|ISO 8601]]&lt;br /&gt;
&lt;br /&gt;
==== Спецификации, связанные с hCard ====&lt;br /&gt;
* [[adr-ru|adr]]&lt;br /&gt;
* [[geo-ru|geo]]&lt;br /&gt;
* [[hcalendar-ru|hCalendar]]&lt;br /&gt;
* [[hreview-ru|hReview]]&lt;br /&gt;
&lt;br /&gt;
==== Подобные работы ====&lt;br /&gt;
* [http://www.intertwingly.net/wiki/pie/PaceBetterPersonElement Atom PaceBetterPersonElement]&lt;br /&gt;
* [http://www.jabber.org/jeps/jep-0054.html JEP-0054: vcard-temp]&lt;br /&gt;
&lt;br /&gt;
==== Идея ====&lt;br /&gt;
Спасибо моему хорошему другу [http://vadim.com/ Вадиму], который познакомил меня с vCard ''много'' лет назад. Если бы я был более внимательным, то многим людям не пришлось бы тратить своё время, изобретая колесо.&lt;br /&gt;
&lt;br /&gt;
==== Создание форматов на основе hCard ====&lt;br /&gt;
''Данный раздел является информативным.''&lt;br /&gt;
&lt;br /&gt;
См. [[hcard-design-methodology-ru|методологию дизайна hCard]].&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
=== More Semantic Equivalents ===&lt;br /&gt;
For some properties there are HTML elements which better match and convey their semantics.  The following properties SHOULD be encoded with the following HTML:&lt;br /&gt;
* &amp;lt;code&amp;gt;URL&amp;lt;/code&amp;gt; in vCard becomes  &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 &amp;lt;code&amp;gt;class=&amp;quot;vcard&amp;quot;&amp;lt;/code&amp;gt; in hCard.&lt;br /&gt;
* Similarly, &amp;lt;code&amp;gt;EMAIL&amp;lt;/code&amp;gt; in vCard becomes &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;
* &amp;lt;code&amp;gt;PHOTO&amp;lt;/code&amp;gt; in vCard becomes &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; or &amp;lt;code&amp;gt;&amp;lt;object class=&amp;quot;photo&amp;quot; data=&amp;quot;...&amp;quot; type=&amp;quot;...&amp;quot;&amp;gt;Photo of ...&amp;lt;/object&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
* &amp;lt;code&amp;gt;UID&amp;lt;/code&amp;gt; in vCard simply becomes another semantic applied to a specific URL (or EMAIL) for an hCard.&lt;br /&gt;
&lt;br /&gt;
=== Singular and Plural derivations ===&lt;br /&gt;
The [[hcard#Singular_vs._Plural_Properties|lists of singular and plural properties]] have been derived by analyzing the semantics of the individual properties in vCard RFC2426 and determining logically that they MUST be singular per their semantics.  See [[hcard-singular-properties]] for explanations.&lt;br /&gt;
&lt;br /&gt;
==== Plural Properties Singularized ====&lt;br /&gt;
Since plural property names become their singular equivalents, even if the original plural property permitted only a single value with multiple components, those multiple components are represented each with their own singularly named property and the the property is effectively multivalued and subject to the above treatment of multivalued properties.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
== Информация для ознакомления ==&lt;br /&gt;
* [http://www.digital-web.com/articles/microformats_primer/ Digital Web Magazine: Microformats Primer] by Garrett Dimon has a good intro to hCard&lt;br /&gt;
* [http://24ways.org/advent/practical-microformats-with-hcard Practical Microformats with hCard] by Drew McLellan&lt;br /&gt;
* [http://www.naturalsearchblog.com/archives/2006/09/28/tips-for-local-search-engine-optimization-for-your-site/ Local Search Engine Optimization using Microformats] by Chris Silver Smith&lt;br /&gt;
* [http://thedredge.org/ Andrew D. Hume] has written a blog post on [http://usabletype.com/articles/2005/usable-microformats/ usable microformats] which discusses hCard&lt;br /&gt;
* [http://www.thefutureoftheweb.com/blog/2006/1/hcard Jesse Skinner's introduction to hCard]&lt;br /&gt;
* [http://blog.usweb.com/ Shaun Shull's] great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], including his [[hcard|hCard]] as an example.&lt;br /&gt;
* [http://24ways.org/2006/styling-hcards-with-css 24 Ways: Styling hCards with CSS] A 24 Ways article - John Allsopp on styling hCard using CSS &lt;br /&gt;
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page] and the [http://technorati.com/tags/hcard hCard tag]&lt;br /&gt;
* [http://www.rfc-editor.org/rfc/rfc4770.txt &amp;lt;nowiki&amp;gt;RFC 4770&amp;lt;/nowiki&amp;gt; Extensions for Instant Messaging]&lt;br /&gt;
* [http://ungeekdapo.wordpress.com/2008/04/30/a-real-life-use-case-of-microformat-hcard-in-action/ A real life use case of Microformat hCard in action] by Bob Ngu&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- == См. также ==&lt;br /&gt;
{{hcard-related-pages}}&lt;br /&gt;
--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Alik</name></author>
	</entry>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=About_Microformats-ru&amp;diff=43035</id>
		<title>About Microformats-ru</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=About_Microformats-ru&amp;diff=43035"/>
		<updated>2010-09-05T15:40:34Z</updated>

		<summary type="html">&lt;p&gt;Alik: /* Микроформаты не являются */ «Онтологий» (Ontologies), not «Антологий» (Anthologies)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;float:right;margin-left:1em&amp;quot;&amp;gt;__TOC__&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Что такое микроформаты?==&lt;br /&gt;
&lt;br /&gt;
Микроформаты разработаны в первую очередь для людей, но также они направлены на облегчение обработки данных программными средствами. Микроформаты — это набор простых, открытых форматов данных, которые построены на существующих широко-распространённых стандартах. &lt;br /&gt;
&lt;br /&gt;
Вместо того, чтобы убирать всё, что было создано ранее, микроформаты нацелены на решение простых проблем путём адаптирования существующих принципов разработки и использования паттернов (например, XHTML, блоггинг).&lt;br /&gt;
&lt;br /&gt;
http://microformats.org/media/2008/micro-diagram.gif&lt;br /&gt;
&lt;br /&gt;
==Микроформаты — это==&lt;br /&gt;
* направление мыслей о данных&lt;br /&gt;
* принципы дизайна форматов&lt;br /&gt;
* адаптирование существующих средств и принципов разработки и использование паттернов.&lt;br /&gt;
* форматы, тесно связанные с семантическим XHTML, также известным как семантика реального мира, прописной семантический Web, XHTML без потерь (lossless XHTML)&lt;br /&gt;
* простой организованный набор стандартов форматов данных, большинство из которых активно разрабатываются и внедряются для более структурированного блоггинга в частности и всего размеченного микроформатами содержимого в целом&lt;br /&gt;
* &amp;quot;эволюционная революция&amp;quot;&lt;br /&gt;
* всё вышесказанное&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Микроформаты не являются==&lt;br /&gt;
* новым языком&lt;br /&gt;
* бесконечно расширяемыми и полностью открытыми&lt;br /&gt;
* попыткой заставить всех сменить тактику и переписать свои утилиты&lt;br /&gt;
* панацеей от таксономий, онтологий и других подобных абстракций &lt;br /&gt;
* определением мира&lt;br /&gt;
* всем вышесказанным&lt;br /&gt;
&lt;br /&gt;
==Принципы микроформатов==&lt;br /&gt;
* Решать определённую узкую задачу&lt;br /&gt;
* Быть простым настолько, насколько это возможно (Keep It Simple)&lt;br /&gt;
* Быть ближе к людям во-первых, к машинам во-вторых&lt;br /&gt;
* Использовать вновь и вновь существующие широко-распространённые стандарты&lt;br /&gt;
* '''Модульность''', '''встраиваемость'''&lt;br /&gt;
* Децентрализованная разработка, контент, сервисы&lt;/div&gt;</summary>
		<author><name>Alik</name></author>
	</entry>
</feed>