https://microformats.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=MarkPilgrimMicroformats Wiki - User contributions [en]2026-04-06T07:24:27ZUser contributionsMediaWiki 1.38.4https://microformats.org/wiki/index.php?title=book-examples&diff=4580book-examples2006-01-30T19:44:27Z<p>MarkPilgrim: additional links and notes about MarkPilgrim books</p>
<hr />
<div>= Book Examples =<br />
<br />
== Contributors ==<br />
<br />
* Håkon Wium Lie<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* Bert Bos<br />
<br />
== Introduction ==<br />
<br />
Examples of books that people actually publish on the Web. This is focused predominantly on the books themselves rather than references to books. For references to books, see the [[cite-examples]] page and related pages.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Examples ==<br />
<br />
* Books by MarkPilgrim: [http://diveintopython.org/toc/index.html Dive Into Python], [http://diveintogreasemonkey.org/toc/ Dive Into Greasemonkey], and arguably [http://feedparser.org/docs/ Feed Parser Documentation]. All of these are produced with a similar toolchain (DocBook XML to HTML via XSLT).<br />
<br />
== See Also ==<br />
<br />
* [[book-formats]]<br />
* [[book-brainstorming]]</div>MarkPilgrimhttps://microformats.org/wiki/index.php?title=resume-examples&diff=4232resume-examples2006-01-18T22:40:54Z<p>MarkPilgrim: </p>
<hr />
<div>= Resume Examples =<br />
<br />
== Resumes from the wild ==<br />
<br />
=== Tantek Çelik ===<br />
* [http://tantek.com/projects/resume.html Tantek Çelik] (needs updating, this is about a year old)<br />
<br />
==== Qualifications ====<br />
<br />
Tantek has a list of his qualifications:<br />
<pre><nowiki><br />
<ul class="quals"><br />
<li><br />
Manager &amp; technical leader (10 years). Led and set direction for teams of up to 12.<br />
</li><br />
...<br />
</nowiki></pre><br />
<br />
==== Employment ====<br />
<br />
Tantek then lists his employment history:<br />
<pre><nowiki><br />
<h2>Employment &amp; Products</h2><br />
<ol class="experience"><br />
<li class="job" id="technorati"><br />
<h3><span class="dates">2004 - present</span><a href="http://www.technorati.com" class="company">Technorati</a>, <a href="http://maps.yahoo.com/py/maps.py?BFCat=&amp;Pyt=Tmap&amp;addr=665+3rd+St&amp;csz=San+Francisco+CA+94107" class="location">San Francisco, CA</a></h3><br />
<h4><span class="dates">2004 July - present</span><br />
<span class="jobtitle">Senior Technologist.</span></h4><br />
Investigate and define new standards and new technologies companywide. Lead adoption of and implementation of valid semantic XHTML and CSS across all web sites. A primary contributor to the design, development, and launch of <a href="http://politics.technorati.com">politics.technorati.com</a> "Election Watch 2004" site in <em>13 days</em>.<br />
<div class="completed"><br />
<h5>Websites Developed and Launched</h5><br />
<ul class="websites"><br />
<li><a href="http://www.technorati.com/">Technorati main site</a> (valid XHTML+CSS green redesign, XHTML strict update)</li><br />
<li><a href="http://politics.technorati.com/">Election Watch 2004</a> (initial valid XHTML+CSS release, XHTML strict update with new Attention Index, Charts features)</li><br />
</ul><br />
</div> <br />
</li><br />
</nowiki></pre><br />
<br />
The implied scheme seems to be (in CSS selectors):<br />
<br />
<pre><nowiki><br />
ol.experience<br />
ol li.job<br />
ol li.job .dates<br />
ol li.job .company<br />
ol li.job .jobtitle<br />
ol li.job .completed<br />
ol li.job .products<br />
</nowiki></pre><br />
<br />
The set of .jobtitle, .completed and .products is repeated for cases where he had more than one position at a company.<br />
<br />
==== patents ====<br />
Tantek also has a section on patents:<br />
<br />
<pre><nowiki><br />
<div class="patents" id="patents"><br />
<h2><abbr title="United States">US</abbr> Patents</h2><br />
<div class="issued"><br />
<h3 class="sidelabel">Issued(6):</h3><br />
<ol><br />
<li id="PatNo5752056" value="5752056"><br />
<h4><a href="http://patft.uspto.gov/netacgi/nph-Parser?d=PALL&amp;p=1&amp;u=%2Fnetahtml%2Fsrchnum.htm&amp;r=1&amp;f=G&amp;l=50&amp;s1=5,752,056&amp;OS=&amp;RS=">System for binding document parts and handlers by fidelity of parts or by automatic translation of parts</a></h4><br />
<a class="altlink" href="http://www.delphion.com/details?pn=US05752056__">(delphion US05752056)</a> <br />
<a class="inventor">[sole inventor]</a></li><br />
...<br />
</nowiki></pre><br />
<br />
I'm not going to dig into this, because I already doubt it will be common enough for inclusion. --[[User:RyanKing|RyanKing]] 13:33, 18 Jan 2006 (PST)<br />
<br />
<br />
==== Publications ====<br />
<br />
<pre><nowiki><br />
<div class="publications" id="publications"><br />
<h2>Publications &amp; Presentations</h2><br />
<br />
<h3 id="recs">Recommendations and Candidate Recommendations (CRs)</h3><br />
<ol><br />
<br />
<li>&Ccedil;elik T.<br />
"<a class="title" href="http://www.w3.org/TR/css3-ui">CSS3 Basic User Interface Module</a>"<br />
<a class="publisher" href="http://w3.org/TR">W3C Technical Reports and Publications</a><br />
&lt;<a class="URL" href="http://www.w3.org/TR/2004/CR-css3-ui-20040511">http://www.w3.org/TR/2004/CR-css3-ui-20040511</a>&gt;<br />
(2004)<br />
</li><br />
</nowiki></pre><br />
<br />
Definite material for citation microformat work. Need analysis in that context. --[[User:RyanKing|RyanKing]] 13:33, 18 Jan 2006 (PST)<br />
<br />
==== presentations ====<br />
<pre><nowiki><br />
<h3 id="presentations">Invited Presentations</h3><br />
<ol><br />
<li>Marks K, &Ccedil;elik T.<br />
"<a class="title" href="http://sdforum.org/SDForum/Templates/CalendarEvent.aspx?CID=1524"> Semantic XHTML: Can your website be your API? - Using semantic XHTML to show what you mean</a>",<br />
<a class="publisher" href="http://sdforum.org/"><abbr title="Software Development Forum">SD Forum</abbr></a> <br />
<a class="event" href="http://www.sdforum.org/SDForum/Templates/Level1.aspx?pid=10117&amp;sid=7">Web Services <abbr title="Special Interest Group">SIG</abbr></a>,<br />
<span class="location">eBay's Silicon Valley Conference Center 2161 North First Street San Jose, CA 95131</span> <br />
(28 September 2004)<br />
</li><br />
...<br />
</nowiki></pre><br />
<br />
Tantek has a list of presentations, which includes presenters' names, event URL, publisher (seems to be used like 'organizer'), the event (ie, conference, workshop) URL and name, location and date.<br />
<br />
<br />
==== Education ====<br />
<pre><nowiki><br />
<div class="education"><br />
<h2>Education</h2><br />
<ol><br />
<li class="school"><br />
<h3><span class="dates">20 June 2001</span><a href="http://www.edwardtufte.com/tufte/" class="institution">Edward Tufte</a></h3><br />
<ul class="courses"><br />
<li><a href="http://www.edwardtufte.com/tufte/courses">Presenting Data and Information</a></li><br />
</ul><br />
</li><br />
....<br />
</nowiki></pre><br />
<br />
Tantek lists his education, including 'dates', a list of 'courses' (which includes name and optional URL) and list of degrees.<br />
<br />
==== Awards ====<br />
<pre><nowiki><br />
<div class="awards" id="awards"><br />
<h2>Awards</h2><br />
<ol><br />
<li><span class="dates">2004</span><br />
<a href="http://2004.sxsw.com/interactive">SXSW interactive conference</a>, <br />
<!--<a href="http://www.sxsw.com/interactive/panels/ratings04/">--><a href="http://2004.sxsw.com/interactive/panels/ratings04/">Top rated moderator (4.70 out of possible 5.0)</a>.</li><br />
</nowiki></pre><br />
<br />
List with dates, event name, url and award name.<br />
<br />
<br />
==== Interests ====<br />
<pre><nowiki><br />
<div class="interests"><br />
<h2>Other Interests</h2><br />
<ul><br />
<li>Alternative transport: skate, bicycle, motorcycle. Run? Only <a href="http://www.asylumsfx.com/movies/belly.mov" target="m">when chased</a>.</li><br />
</nowiki></pre><br />
<br />
==== Affiliations ====<br />
<pre><nowiki><br />
<h2>Member of</h2><br />
<ul><li><a href="http://www.cpsr.org">Computer Professionals for Social Responsibility (<abbr>CPSR</abbr>)</a> (life),</li><br />
</nowiki></pre><br />
<br />
List of memberships/affiliations, each with URL and name.<br />
<br />
=== Dan Connolly ===<br />
[http://www.w3.org/People/Connolly/misc/vita Dan Connolly] (needs elaboration for MIT purposes; has been GRDDL'd to some extent)<br />
<br />
==== Affilitations ====<br />
For affiliations, Dan has:<br />
<pre><nowiki><br />
<div class="affiliation"><br />
<em class="position">Research Scientist</em><br /><br />
<b class="org">MIT Computer Science and Artificial Intelligence Laboratory (<a rel="aff"<br />
href="http://www.csail.mit.edu/">CSAIL</a>)</b><br />
</div><br />
</nowiki></pre><br />
<br />
Not sure what rel="aff" means. --[[User:RyanKing|RyanKing]] 17:17, 17 Jan 2006 (PST)<br />
<br />
==== Contact ====<br />
For contact info:<br />
<pre><nowiki><br />
<div class="contact"><br />
<span class='street'>200 Technology Square</span><br />
<span class='city'>Cambridge</span>, <span class='st'>MA</span><br />
<span class="zip">02139</span><br /><br />
<code class='homePageAddr'>http://www.w3.org/People/Connolly/</code><br />
</div><br />
</nowiki></pre><br />
<br />
<br />
==== Education ====<br />
<br />
<pre><nowiki><br />
<h2>Education</h2><br />
</nowiki></pre><br />
...followed by more affiliation <code>div</code>'s (see above).<br />
<br />
Under his education entry, he has a list of what appear to be honors/awards:<br />
<br />
<pre><nowiki><br />
<ul><br />
<li>National Merit Scholar</li><br />
<li>Natural Sciences <a<br />
href="http://www.cs.utexas.edu/users/cline/dsbrochure.html">Dean's<br />
Scholar</a></li><br />
<li><a href="http://www.arlut.utexas.edu/">Applied Research<br />
Laboratories</a> Scholarship</li><br />
</ul><br />
</nowiki></pre><br />
<br />
<br />
==== Publications ==== <br />
<br />
Publications section:<br />
<br />
<pre><nowiki><br />
<h2>Selected Publications</h2><br />
<ul><br />
<li>Berners-Lee, Connolly, Swick, <a href="/1999/04/WebData"><cite>Web<br />
Architecture: Describing and Exchanging Data</cite></a> (World Wide Web<br />
Consortium Note, 1999)</li><br />
<li><dl><br />
<dt>Connolly, <a<br />
href="http://helix.nature.com/webmatters/xml.html"><cite>The XML<br />
Revolution</cite></a> Nature's <a<br />
href="http://helix.nature.com/webmatters/">Web Matters</a>, Oct 1998<br<br />
/><br />
</dt><br />
</dl><br />
</li><br />
....<br />
</nowiki></pre><br />
<br />
Not sure what's up with the <code>dl</code>'s.<br />
<br />
Dan also has a section on professional experience:<br />
<br />
<pre><nowiki><br />
<div><br />
<h2>Professional Experience</h2><br />
<ul><br />
<li>Domain Lead, W3C Architecture Domain, 1996-1998</li><br />
...<br />
</nowiki></pre><br />
<br />
Also a section on 'Appearance and Awards'<br />
<br />
<pre><nowiki><br />
<div><br />
<h2>Selected Appearances and Awards</h2><br />
<ul><br />
<li><a<br />
href="http://www.zdnet.com/intweek/printhigh/120897/top25.html"><cite>The<br />
Top 25 Unsung Heroes Of The Net</cite></a> by <a<br />
href="http://www.zdnet.com/intweek/">Inter@ctive Week</a> 1997</li><br />
....<br />
</nowiki></pre><br />
<br />
=== Mark Pilgrim ===<br />
* [http://diveintomark.org/about/resume/]<br />
<br />
== Experiments in microformatting ==<br />
* [http://cs.usfca.edu/~rking/resume.html ryan king]<br />
* [http://cs.usfca.edu/~rking/niall.html Niall Kennedy] (microformatted by RyanKing)<br />
* My resume uses hCard, hCalendar, XFN, and rel-license: http://edward.oconnor.cx/resume/ [[User:EdwardOConnor|EdwardOConnor]]<br />
* [http://steve.ganz.name/resume/resume.html Steve Ganz] - A work-in-progress. Currently using [[hCard]], [[hCalendar]], and a little [http://gmpg.org/xfn/ XFN]. Where there weren't any appropriate existing microformats to draw upon, I looked to [http://xmlresume.sourceforge.net/ XML Resume] for semantics or simply improvised (class="qualifications"). I also created a few custom link type values: rel="employer current" and rel="employer former" (no profile yet).<br />
<br />
== Aggregate Analysis ==<br />
To be filled in from the above examples, experience, and discussions.<br />
<br />
== See Also ==<br />
<br />
* [[resume-formats]]<br />
* [[resume-brainstorming]]</div>MarkPilgrimhttps://microformats.org/wiki/index.php?title=rel-tag&diff=4249rel-tag2006-01-11T16:59:19Z<p>MarkPilgrim: fixed link to RFC 3986, apparently MediaWiki autolinks RFCs</p>
<hr />
<div>= rel=&quot;tag&quot; =<br />
__TOC__<br />
<br />
== Draft Specification 2005-01-10 ==<br />
=== Editor/Author ===<br />
[http://tantek.com/ Tantek Çelik]<br />
<br />
=== Concept ===<br />
[http://powazek.com/ Derek Powazek]<br />
[http://epeus.blogspot.com/ Kevin Marks]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Abstract ==<br />
[[Rel-Tag]] is one of several [[MicroFormats]]. By adding <code>rel=&quot;tag&quot;</code> to a hyperlink, a page indicates that the destination of that hyperlink is an author-designated &quot;tag&quot; (or keyword/subject) of 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,<br />
<br />
<pre><nowiki><a href=&quot;http://technorati.com/tag/tech&quot; rel=&quot;tag&quot;>tech</a></nowiki></pre><br />
<br />
the author indicates that the page (or some portion of the page) has the tag &quot;tech&quot;.<br />
<br />
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<br />
is the text of the tag, so <br />
<br />
<pre><nowiki><a href=&quot;http://technorati.com/tag/tech&quot; rel=&quot;tag&quot;>fish</a></nowiki></pre><br />
<br />
would indicate the tag &quot;tech&quot; rather than &quot;fish&quot;.<br />
<br />
== Scope ==<br />
rel=&quot;tag&quot; is specifically designed for &quot;tagging&quot; content, typically web pages (or portions thereof, like blog posts).<br />
<br />
rel=&quot;tag&quot; is NOT designed for &quot;tagging&quot; arbitrary URLs or external content. There is demand for a general decentralized syntax for tagging URLs, and that is certainly something to think about, but this is not meant for that. <br />
<br />
== XMDP profile ==<br />
<pre><nowiki><br />
<dl class=&quot;profile&quot;><br />
<dt id=&quot;rel&quot;>rel</dt><br />
<dd><p><br />
<a rel=&quot;help&quot; href=&quot;http://www.w3.org/TR/html401/struct/links.html#adef-rel&quot;><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id=&quot;tag&quot;>tag</dt><br />
<dd>Indicates that the referred resource serves as a &quot;tag&quot;, <br />
or keyword/subject, for the referring page.</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
== Tag Spaces ==<br />
<br />
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 "/" character) contains the tag value. For example, the URI <pre><nowiki>http://www.example.com/tags/foo</nowiki></pre> contains the tag &quot;foo&quot;. <br />
<br />
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.<br />
<br />
''Need more formal language about comparison and extraction process.''<br />
<br />
The destination of a rel=&quot;tag&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. <br />
<br />
<pre><nowiki>http://technorati.com/tag/tech </nowiki></pre><br />
<br />
is a URL for the tag &quot;tech&quot;.<br />
<br />
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.<br />
<br />
<pre><nowiki>http://technorati.com/tag/tech?tag=fish#emu </nowiki></pre><br />
<br />
is still a URL for the tag &quot;tech&quot;, not &quot;fish&quot; or &quot;emu&quot;.<br />
<br />
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:<br />
<br />
<pre><nowiki> http://en.wikipedia.org/wiki/Technology </nowiki></pre><br />
<br />
== Encoding issues ==<br />
Spaces can be encoded either as <code>+</code> or <code>%20</code>. Unicode characters are encoded as specified in [http://www.ietf.org/rfc/rfc3986.txt RFC 3986]. For example:<br />
<br />
<pre><nowiki><a href=&quot;http://technorati.com/tag/Sant%C3%A9+et+bien-%C3%AAtre&quot; rel=&quot;tag&quot;>Santé et bien-être</a> </nowiki></pre><br />
<br />
== Tags Are Visible Metadata ==<br />
<code>rel=&quot;tag&quot;</code> 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.<br />
<br />
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.<br />
<br />
As a result the invisible tag link syntax variant: <code><link rel=&quot;tag&quot; href=&quot;...&quot; /></code> SHOULD NOT be supported by implementations.<br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
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.<br />
<br />
* [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.<br />
* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] rel-tags for user entered tags.<br />
* [http://evdb.com EVDB] publishes rel-tags for user entered tags.<br />
* [http://dev.wp-plugins.org/wiki/BunnysTechnoratiTags &quot;Tag plugin for wordpress&quot;]<br />
* Technorati first implemented rel-tag in its [http://technorati.com/tag/ Technorati Tags] service. Technorati indexes rel-tag tags.<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/REC-html40/ HTML 4]<br />
* [http://www.w3.org/TR/xhtml1/ XHTML 1]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* RFC 3986 specifies URL syntax. Section 3.3 specifies URL paths and path segments.<br />
<br />
=== Informative References ===<br />
* [[hreview|hReview]] uses rel-tag for tags and scalar tags<br />
* [[xfolk|xFolk]] uses rel-tag to build a distributed remote resource tagging construct<br />
* [http://developers.technorati.com/wiki/attentionxml Attention.XML] uses rel-tag for reader tagging of pages, posts, feeds<br />
* [[hcard|hCard]] can use rel-tag for categories<br />
* [[hcalendar|hCalendar]] can use rel-tag for categories<br />
* [http://technorati.com/help/tags.html Using Technorati Tags]<br />
<br />
== Discussions ==<br />
<br />
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
<br />
=== Q&A ===<br />
* If you have any questions about rel-tag, check the [[rel-faq|rel FAQ]], and if you don't find answers, add your questions!<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[rel-tag-issues|rel-tag issues]] document.</div>MarkPilgrimhttps://microformats.org/wiki/index.php?title=rel-tag&diff=4121rel-tag2006-01-11T16:57:13Z<p>MarkPilgrim: fixed language about path segments, added note about query params and fragments</p>
<hr />
<div>= rel=&quot;tag&quot; =<br />
__TOC__<br />
<br />
== Draft Specification 2005-01-10 ==<br />
=== Editor/Author ===<br />
[http://tantek.com/ Tantek Çelik]<br />
<br />
=== Concept ===<br />
[http://powazek.com/ Derek Powazek]<br />
[http://epeus.blogspot.com/ Kevin Marks]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Abstract ==<br />
[[Rel-Tag]] is one of several [[MicroFormats]]. By adding <code>rel=&quot;tag&quot;</code> to a hyperlink, a page indicates that the destination of that hyperlink is an author-designated &quot;tag&quot; (or keyword/subject) of 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,<br />
<br />
<pre><nowiki><a href=&quot;http://technorati.com/tag/tech&quot; rel=&quot;tag&quot;>tech</a></nowiki></pre><br />
<br />
the author indicates that the page (or some portion of the page) has the tag &quot;tech&quot;.<br />
<br />
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<br />
is the text of the tag, so <br />
<br />
<pre><nowiki><a href=&quot;http://technorati.com/tag/tech&quot; rel=&quot;tag&quot;>fish</a></nowiki></pre><br />
<br />
would indicate the tag &quot;tech&quot; rather than &quot;fish&quot;.<br />
<br />
== Scope ==<br />
rel=&quot;tag&quot; is specifically designed for &quot;tagging&quot; content, typically web pages (or portions thereof, like blog posts).<br />
<br />
rel=&quot;tag&quot; is NOT designed for &quot;tagging&quot; arbitrary URLs or external content. There is demand for a general decentralized syntax for tagging URLs, and that is certainly something to think about, but this is not meant for that. <br />
<br />
== XMDP profile ==<br />
<pre><nowiki><br />
<dl class=&quot;profile&quot;><br />
<dt id=&quot;rel&quot;>rel</dt><br />
<dd><p><br />
<a rel=&quot;help&quot; href=&quot;http://www.w3.org/TR/html401/struct/links.html#adef-rel&quot;><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id=&quot;tag&quot;>tag</dt><br />
<dd>Indicates that the referred resource serves as a &quot;tag&quot;, <br />
or keyword/subject, for the referring page.</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
== Tag Spaces ==<br />
<br />
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 "/" character) contains the tag value. For example, the URI <pre><nowiki>http://www.example.com/tags/foo</nowiki></pre> contains the tag &quot;foo&quot;. <br />
<br />
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.<br />
<br />
''Need more formal language about comparison and extraction process.''<br />
<br />
The destination of a rel=&quot;tag&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. <br />
<br />
<pre><nowiki>http://technorati.com/tag/tech </nowiki></pre><br />
<br />
is a URL for the tag &quot;tech&quot;.<br />
<br />
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.<br />
<br />
<pre><nowiki>http://technorati.com/tag/tech?tag=fish#emu </nowiki></pre><br />
<br />
is still a URL for the tag &quot;tech&quot;, not &quot;fish&quot; or &quot;emu&quot;.<br />
<br />
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:<br />
<br />
<pre><nowiki> http://en.wikipedia.org/wiki/Technology </nowiki></pre><br />
<br />
== Encoding issues ==<br />
Spaces can be encoded either as <code>+</code> or <code>%20</code>. Unicode characters are encoded as specified in [http://www.ietf.org/rfc/rfc3986.txt RFC 3986]. For example:<br />
<br />
<pre><nowiki><a href=&quot;http://technorati.com/tag/Sant%C3%A9+et+bien-%C3%AAtre&quot; rel=&quot;tag&quot;>Santé et bien-être</a> </nowiki></pre><br />
<br />
== Tags Are Visible Metadata ==<br />
<code>rel=&quot;tag&quot;</code> 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.<br />
<br />
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.<br />
<br />
As a result the invisible tag link syntax variant: <code><link rel=&quot;tag&quot; href=&quot;...&quot; /></code> SHOULD NOT be supported by implementations.<br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
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.<br />
<br />
* [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.<br />
* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] rel-tags for user entered tags.<br />
* [http://evdb.com EVDB] publishes rel-tags for user entered tags.<br />
* [http://dev.wp-plugins.org/wiki/BunnysTechnoratiTags &quot;Tag plugin for wordpress&quot;]<br />
* Technorati first implemented rel-tag in its [http://technorati.com/tag/ Technorati Tags] service. Technorati indexes rel-tag tags.<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/REC-html40/ HTML 4]<br />
* [http://www.w3.org/TR/xhtml1/ XHTML 1]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [http://www.ietf.org/rfc/rfc3986.txt RFC 3986] specifies URL syntax. Section 3.3 specifies URL paths and path segments.<br />
<br />
=== Informative References ===<br />
* [[hreview|hReview]] uses rel-tag for tags and scalar tags<br />
* [[xfolk|xFolk]] uses rel-tag to build a distributed remote resource tagging construct<br />
* [http://developers.technorati.com/wiki/attentionxml Attention.XML] uses rel-tag for reader tagging of pages, posts, feeds<br />
* [[hcard|hCard]] can use rel-tag for categories<br />
* [[hcalendar|hCalendar]] can use rel-tag for categories<br />
* [http://technorati.com/help/tags.html Using Technorati Tags]<br />
<br />
== Discussions ==<br />
<br />
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
<br />
=== Q&A ===<br />
* If you have any questions about rel-tag, check the [[rel-faq|rel FAQ]], and if you don't find answers, add your questions!<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[rel-tag-issues|rel-tag issues]] document.</div>MarkPilgrimhttps://microformats.org/wiki/index.php?title=rel-tag&diff=4120rel-tag2006-01-11T16:49:41Z<p>MarkPilgrim: reverted Serginandr's spam</p>
<hr />
<div>= rel=&quot;tag&quot; =<br />
__TOC__<br />
<br />
== Draft Specification 2005-01-10 ==<br />
=== Editor/Author ===<br />
[http://tantek.com/ Tantek Çelik]<br />
<br />
=== Concept ===<br />
[http://powazek.com/ Derek Powazek]<br />
[http://epeus.blogspot.com/ Kevin Marks]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Abstract ==<br />
[[Rel-Tag]] is one of several [[MicroFormats]]. By adding <code>rel=&quot;tag&quot;</code> to a hyperlink, a page indicates that the destination of that hyperlink is an author-designated &quot;tag&quot; (or keyword/subject) of 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,<br />
<br />
<pre><nowiki><a href=&quot;http://technorati.com/tag/tech&quot; rel=&quot;tag&quot;>tech</a></nowiki></pre><br />
<br />
the author indicates that the page (or some portion of the page) has the tag &quot;tech&quot;.<br />
<br />
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<br />
is the text of the tag, so <br />
<br />
<pre><nowiki><a href=&quot;http://technorati.com/tag/tech&quot; rel=&quot;tag&quot;>fish</a></nowiki></pre><br />
<br />
would indicate the tag &quot;tech&quot; rather than &quot;fish&quot;.<br />
<br />
== Scope ==<br />
rel=&quot;tag&quot; is specifically designed for &quot;tagging&quot; content, typically web pages (or portions thereof, like blog posts).<br />
<br />
rel=&quot;tag&quot; is NOT designed for &quot;tagging&quot; arbitrary URLs or external content. There is demand for a general decentralized syntax for tagging URLs, and that is certainly something to think about, but this is not meant for that. <br />
<br />
== XMDP profile ==<br />
<pre><nowiki><br />
<dl class=&quot;profile&quot;><br />
<dt id=&quot;rel&quot;>rel</dt><br />
<dd><p><br />
<a rel=&quot;help&quot; href=&quot;http://www.w3.org/TR/html401/struct/links.html#adef-rel&quot;><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id=&quot;tag&quot;>tag</dt><br />
<dd>Indicates that the referred resource serves as a &quot;tag&quot;, <br />
or keyword/subject, for the referring page.</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
== Tag Spaces ==<br />
<br />
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 contains the tag value. For example, the URI <pre><nowiki>http://www.example.com/tags/foo</nowiki></pre> contains the tag &quot;foo&quot;. <br />
<br />
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.<br />
<br />
''Need more formal language about comparison and extraction process.''<br />
<br />
The destination of a rel=&quot;tag&quot; hyperlink is required to be a tag space (a place that collates or defines tags), where the last component of the URL is the tag, e.g. <br />
<br />
<pre><nowiki>http://technorati.com/tag/tech </nowiki></pre><br />
<br />
is a URL for the tag &quot;tech&quot;.<br />
<br />
Since the only part of a tag space URL of which any structure is required is the last 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:<br />
<br />
<pre><nowiki> http://en.wikipedia.org/wiki/Technology </nowiki></pre><br />
<br />
== Encoding issues ==<br />
Spaces can be encoded either as <code>+</code> or <code>%20</code>. Unicode characters are encoded as specified in [http://www.ietf.org/rfc/rfc3986.txt RFC 3986]. For example:<br />
<br />
<pre><nowiki><a href=&quot;http://technorati.com/tag/Sant%C3%A9+et+bien-%C3%AAtre&quot; rel=&quot;tag&quot;>Santé et bien-être</a> </nowiki></pre><br />
<br />
== Tags Are Visible Metadata ==<br />
<code>rel=&quot;tag&quot;</code> 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.<br />
<br />
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.<br />
<br />
As a result the invisible tag link syntax variant: <code><link rel=&quot;tag&quot; href=&quot;...&quot; /></code> SHOULD NOT be supported by implementations.<br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
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.<br />
<br />
* [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.<br />
* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] rel-tags for user entered tags.<br />
* [http://evdb.com EVDB] publishes rel-tags for user entered tags.<br />
* [http://dev.wp-plugins.org/wiki/BunnysTechnoratiTags &quot;Tag plugin for wordpress&quot;]<br />
* Technorati first implemented rel-tag in its [http://technorati.com/tag/ Technorati Tags] service. Technorati indexes rel-tag tags.<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/REC-html40/ HTML 4]<br />
* [http://www.w3.org/TR/xhtml1/ XHTML 1]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [http://www.ietf.org/rfc/rfc3986.txt RFC 3986 specifies URL syntax]<br />
<br />
=== Informative References ===<br />
* [[hreview|hReview]] uses rel-tag for tags and scalar tags<br />
* [[xfolk|xFolk]] uses rel-tag to build a distributed remote resource tagging construct<br />
* [http://developers.technorati.com/wiki/attentionxml Attention.XML] uses rel-tag for reader tagging of pages, posts, feeds<br />
* [[hcard|hCard]] can use rel-tag for categories<br />
* [[hcalendar|hCalendar]] can use rel-tag for categories<br />
* [http://technorati.com/help/tags.html Using Technorati Tags]<br />
<br />
== Discussions ==<br />
<br />
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
<br />
=== Q&A ===<br />
* If you have any questions about rel-tag, check the [[rel-faq|rel FAQ]], and if you don't find answers, add your questions!<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[rel-tag-issues|rel-tag issues]] document.</div>MarkPilgrimhttps://microformats.org/wiki/index.php?title=hreview-examples&diff=5493hreview-examples2005-10-13T22:00:23Z<p>MarkPilgrim: </p>
<hr />
<div>= hReview examples =<br />
<br />
Example [[hreview|hReviews]].<br />
<br />
__TOC__<br />
<br />
== Authors ==<br />
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]<br />
* [http://360.yahoo.com/alidiabali Ali Diab],[http://yahoo.com Yahoo! Inc.]<br />
* [http://spaces.msn.com/members/ianmcallister/ Ian McAllister], [http://microsoft.com/ Microsoft Corporation]<br />
* [http://journals.aol.com/panzerjohn/abstractioneer John Panzer], [http://www.aol.com America Online, Inc.]<br />
* [http://ifindkarma.com/blog Adam Rifkin], [http://labs.commerce.net/ CommerceNet Labs]<br />
* [http://sippey.typepad.com/ Michael Sippey], [http://sixapart.com Six Apart, Ltd.]<br />
<br />
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.<br />
<br />
== Restaurant review ==<br />
<br />
Here is an example of a simple online restaurant review:<br />
<br />
<pre><nowiki><br />
<div><br />
<span>5 stars out of 5 stars</span><br />
<h4>Crepes on Cole is awesome</h4><br />
<span>Reviewer: <span>Tantek</span> - April 18, 2005</span><br />
<blockquote><p><br />
Crepes on Cole is one of the best little creperies in San Francisco. <br />
Excellent food and service. Plenty of tables in a variety of sizes <br />
for parties large and small. Window seating makes for excellent <br />
people watching to/from the N-Judah which stops right outside. <br />
I've had many fun social gatherings here, as well as gotten <br />
plenty of work done thanks to neighborhood WiFi.<br />
</p></blockquote><br />
<p>Visit date: <span>April 2005</span></p><br />
<p>Food eaten: <span>Florentine crepe</span></p><br />
</div><br />
</nowiki></pre><br />
<br />
Adding hReview to this review is quite simple:<br />
<br />
<pre><nowiki><br />
<div class="hreview"><br />
<span><span class="rating">5</span> out of 5 stars</span><br />
<h4 class="summary"><span class="item fn">Crepes on Cole</span> is awesome</h4><br />
<span>Reviewer: <span class="reviewer fn">Tantek</span> - <br />
<abbr class="dtreviewed" title="20050418T2300-0700">April 18, 2005</abbr></span><br />
<blockquote class="description"><p><br />
Crepes on Cole is one of the best little creperies in San Francisco.<br />
Excellent food and service. Plenty of tables in a variety of sizes <br />
for parties large and small. Window seating makes for excellent <br />
people watching to/from the N-Judah which stops right outside. <br />
I've had many fun social gatherings here, as well as gotten <br />
plenty of work done thanks to neighborhood WiFi.<br />
</p></blockquote><br />
<p>Visit date: <span>April 2005</span></p><br />
<p>Food eaten: <span>Florentine crepe</span></p><br />
</div><br />
</nowiki></pre><br />
<br />
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.<br />
<br />
This sample hReview could be rendered like this:<br />
<br />
5 stars out of 5 stars<br /><br />
'''Crepes on Cole is awesome'''<br /><br />
Reviewer: Tantek - April 18, 2005<br /><br />
<br />
<blockquote>Crepes on Cole is one of the best little creperies in San Francisco. Excellent food and service. Plenty of tables in a variety of sizes for parties large and small. Window seating makes for excellent people watching to/from the N-Judah which stops right outside. I've had many fun social gatherings here, as well as gotten plenty of work done thanks to neighborhood wifi.</blockquote><br />
<br />
Visit date: April 2005<br /><br />
Food eaten: Florentine crepe<br /><br />
<br />
=== Multidimensional Restaurant Review ===<br />
<br />
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.<br />
<br />
Here is one such review in text format:<br />
<br />
Cafe Borrone<br />
<br />
1010 El Camino Real, Menlo Park, CA 94025, +1-650-327-0830;<br />
cafeborrone.com<br />
<br />
Food: 18/30; Ambience: 19/30; Service: 15/30; Price: $$...<br />
<br />
This cafe is a welcoming oasis on the Peninsula. It even has a fountain<br />
outside which cloaks the nearby sounds of El Camino traffic. Next door to a <br />
superb indy bookstore, Cafe Borrone is an ideal spot to grab a coffee or a <br />
snack to accompany a newly purchased book or imported periodical. Soups and <br />
sandwich specials rotate daily. The corn chowder with croutons and big <br />
chunks of cheese goes especially well with a freshly toasted mini-baguette. <br />
Evenings are often crowded and may require sharing a table with a perfect <br />
stranger. Espresso afficionados will appreciate the Illy coffee. Noise <br />
levels can vary from peaceful in the late mornings to nearly overwhelming on <br />
jazz band nights.<br />
<br />
As an hReview:<br />
<br />
<pre><nowiki><br />
<div class="hreview"><br />
<div class="item vcard"><br />
<div class="fn org summary">Cafe Borrone</div><br />
<span class="adr"><br />
<span class="street-address">1010 El Camino Real</span>,<br />
<span class="locality">San Francisco</span>,<br />
<span class="region">CA</span><br />
<span class="postal-code">94025</span>,<br />
</span><br />
<span class="tel"><span class="voice work">+1-650-327-0830</span></span>;<br />
<a class="url" href="http://cafeborrone.com">cafeborrone.com</a><br />
</div><br />
<ul class="categories"><br />
<li><a href="http://en.wikipedia.org/wiki/Food" rel="tag"><br />
Food: <span class="rating">18</span>/<span class="best">30</span></a>;</li><br />
<li><a href="http://flickr.com/photos/tags/Ambience" rel="tag"><br />
Ambience: <span class="rating">19</span>/<span class="best">30</span></a>;</li><br />
<li><a href="http://en.wikipedia.org/wiki/Service" rel="tag"><br />
Service: <span class="rating">15</span>/<span class="best">30</span></a>;</li><br />
<li><a href="http://en.wikipedia.org/wiki/Price" rel="tag"><br />
Price: <abbr class="rating" title="2">$$</abbr>...</a></li><br />
</ul><br />
<blockquote class="description"><p><br />
This <abbr class="type" title="business"><br />
<a href="http://en.wikipedia.org/wiki/cafe" rel="tag">cafe</a></abbr> <br />
is a welcoming oasis on the Peninsula. <br />
It even has a fountain outside which nearly eliminates <br />
the sounds of El Camino traffic. Next door to a superb indy bookstore, <br />
Cafe Borrone is an ideal spot to grab a <br />
<a href="http://en.wikipedia.org/wiki/coffee" rel="tag">coffee</a> <br />
or a meal to accompany a newly purchased book or imported periodical. <br />
<a href="http://technorati.com/tag/soup" rel="tag">Soups</a> and <br />
<a href="http://technorati.com/tag/sandwich" rel="tag">sandwich</a> <br />
specials rotate daily. The corn chowder with croutons and big chunks of cheese <br />
goes especially well with a freshly toasted mini-baguette. Evenings are <br />
often crowded and may require sharing a table with a perfect stranger. <br />
<a href="http://flickr.com/photos/tags/espresso" rel="tag">Espresso</a> <br />
afficionados will appreciate the <br />
<a href="http://en.wikipedia.org/wiki/Illy" rel="tag">Illy</a> coffee. <br />
Noise levels can vary from peaceful in the late mornings to nearly overwhelming on <br />
<a href="http://en.wikipedia.org/wiki/jazz" rel="tag">jazz</a> band nights.<br />
</p></blockquote><br />
Review (<a href="http://microformats.org/wiki/hreview"> <br />
hReview v<span class="version">0.2</span></a>)<br />
by <span class="reviewer">anonymous</span>, <br />
<abbr class="dtreviewed" title="20050428T2130-0700">April 28th, 2005</abbr>.<br />
</div><br />
</nowiki></pre><br />
<br />
With an accompanying CSS style sheet like:<br />
<br />
<pre><nowiki><br />
a.url { display:block }<br />
ul.categories { margin:1em 0; padding:0 }<br />
.categories li { display:inline }<br />
</nowiki></pre><br />
<br />
This hReview could be presented similar to the original text:<br />
<br />
Cafe Borrone<br /><br />
1010 El Camino Real, Menlo Park, CA 94025, +1-650-327-0830;<br /><br />
[http://cafeborrone.com/ cafeborrone.com]<br /><br />
<br /><br />
[http://en.wikipedia.org/wiki/Food Food: 18/30];<br />
[http://flickr.com/photos/tags/Ambience Ambience: 19/30];<br />
[http://en.wikipedia.org/wiki/Service Service: 15/30];<br />
[http://en.wikipedia.org/wiki/Price Price: $$...]<br /><br />
<br />
<blockquote>This [http://en.wikipedia.org/wiki/cafe cafe] is a welcoming oasis on the Peninsula. It even has a fountain outside which cloaks the nearby sounds of El Camino traffic. Next door to a superb indy bookstore, Cafe Borrone is an ideal spot to grab a [http://en.wikipedia.org/wiki/coffee coffee] or a snack to accompany a newly purchased book or imported periodical. [http://technorati.com/tag/soup Soups] and [http://technorati.com/tag/sandwich sandwich] specials rotate daily. The corn chowder with croutons and big chunks of cheese goes especially well with a freshly toasted mini-baguette. Evenings are often crowded and may require sharing a table with a perfect stranger. [http://flickr.com/photos/tags/espresso Espresso] afficionados will appreciate the [http://en.wikipedia.org/wiki/Illy Illy] coffee. Noise levels can vary from peaceful in the late mornings to nearly overwhelming on [http://en.wikipedia.org/wiki/jazz jazz] band nights.</blockquote><br />
<br />
Review ([http://microformats.org/wiki/hreview hReview v0.2]) by anonymous, April 28th, 2005.<br />
<br />
== Product review ==<br />
<br />
Here is an example of a product review:<br />
<br />
<pre><nowiki><br />
<div><br />
<a href="http://www.amazon.com/exec/obidos/ASIN/B000089CJI/"><br />
<img src="http://images.amazon.com/images/P/B000089CJI.01._SCTHUMBZZZ_.jpg" <br />
alt="Album cover photo: The Postal Service: Give Up." /><br />
The Postal Service: Give Up</a><br />
<blockquote><p><br />
"The people thought they were just being rewarded for treating others <br />
as they like to be treated, for obeying stop signs and curing diseases, <br />
for mailing letters with the address of the sender... Don't wake me, <br />
I plan on sleeping in..."<br />
</p><p><br />
"Nothing Better" is a great track on this album, too... <br />
</p></blockquote><br />
(*****)<br />
</div><br />
</nowiki></pre><br />
<br />
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:<br />
<br />
<pre><nowiki><br />
<div class="hreview"><br />
<a class="item url" href="http://www.amazon.com/exec/obidos/ASIN/B000089CJI/"><br />
<img src="http://images.amazon.com/images/P/B000089CJI.01._SCTHUMBZZZ_.jpg" <br />
alt="Album cover photo: The Postal Service: Give Up. " <br />
class="photo" /><br />
<span class="fn">The Postal Service: Give Up</span></a><br />
<blockquote class="description"><p><br />
"The people thought they were just being rewarded for treating others <br />
as they like to be treated, for obeying stop signs and curing diseases, <br />
for mailing letters with the address of the sender... Don't wake me, <br />
I plan on sleeping in..."<br />
</p><p><br />
"Nothing Better" is a great track on this album, too... <br />
</p></blockquote><br />
(<abbr class="rating" title="5">*****</abbr>)<br />
<p class="reviewer vcard">Review by <br />
<a class="url fn" href="http://ifindkarma.com/blog/">Adam Rifkin</a>, <br />
<abbr class="dtreviewed" title="200502">February 2005</abbr><br />
</p><br />
</div><br />
</nowiki></pre><br />
<br />
And this hReview might be presented like this:<br />
<br />
<br />
[Album cover photo: ]<br />
[The Postal Service:]<br />
[ Give Up ]<br />
<br />
The Postal Service: Give Up<br />
<br />
<blockquote>"The people thought they were just being rewarded for treating others as they like to be treated, for obeying stop signs and curing diseases, for mailing letters with the address of the sender... Don't wake me, I plan on sleeping in..."</blockquote><br />
<br />
<blockquote>"Nothing Better" is a great track on this album, too... </blockquote><br />
<br />
(*****)<br />
<br />
Review by Adam Rifkin, February 2005.<br />
<br />
== Movie Review ==<br />
Finally, here is an example of a movie review.<br />
<br />
<pre><nowiki><br />
<div><br />
<span>anonymous, April 18th, 2005</span><br />
<div><br />
<a lang="zh" href="http://www.imdb.com/title/tt0299977/"><br />
Ying Xiong (<span lang="en">HERO</span>)<br />
</a><br />
</div><br />
<div>Rating: 4 out of 5</div><br />
<blockquote><p><br />
This movie has great visuals and music.<br />
</p></blockquote><br />
</div><br />
</nowiki></pre><br />
<br />
With hReview:<br />
<br />
<pre><nowiki><br />
<div class="hreview"><br />
<span class="reviewer"><br />
<span class="fn">anonymous</span>, <br />
<abbr class="dtreviewed" title="20050418">April 18th, 2005</abbr><br />
</span><br />
<div class="item"><br />
<a lang="zh" class="url fn" href="http://www.imdb.com/title/tt0299977/"><br />
Ying Xiong (<span lang="en">HERO</span>)<br />
</a><br />
</div><br />
<div>Rating: <span class="rating">4</span> out of 5</div><br />
<blockquote class="description"><p><br />
This movie has great music and visuals.<br />
</p></blockquote><br />
</div><br />
</nowiki></pre><br />
<br />
Which could be presented like this:<br />
<br />
anonymous, April 18th, 2005<br /><br />
Ying Xiong (HERO)<br /><br />
Rating: 4 out of 5<br /><br />
<br />
This movie has great music and visuals.<br />
<br />
== Examples in the wild ==<br />
<br />
This section is '''informative'''.<br />
<br />
The following sites have published hReviews, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If you publish hReviews on your own page, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.<br />
<br />
* [http://blog.ftwr.co.uk/ Peter Westwood] has written an [http://blog.ftwr.co.uk/archives/2005/10/03/blubeckers-hampton-court/ hReview of Blubeckers Hampton Court]<br />
* [http://dougal.gunters.org/blog/ Dougal] has published an [http://dougal.gunters.org/blog/2005/08/03/french-vanilla-latte hReview of Wolfgang Puck’s Gourmet French Vanilla Latte].<br />
* [http://www.dinnerbuzz.com/ Dinnerbuzz] is a great site for posting tagged reviews of restaurants, and they publish and summarize all their reviews in hReview!<br />
* [http://soldierant.net/ Bryce Glass] posted an [http://soldierant.net/archives/2005/06/product_review.html hReview of the Uniden ELBT 595 Bluetooth Cordless Phone].<br />
* dda posted an [http://sungnyemun.org/wordpress/?p=20 hReview of hReview] :) <br />
* An [http://tbp.xomerang.com/?p=3 hReview of Caffè Camardo coffee].<br />
* [http://loadaveragezero.com/hnav/contact.php Douglas Clifton] posted [http://loadaveragezero.com/#May-12-2005 comments] regarding adapting his list of ~800 [http://loadaveragezero.com/app/drx Developer Resources] as a format for evaluating hReview.<br />
* [http://www.oliverbrown.me.uk/ Oliver Brown] [http://www.oliverbrown.me.uk/2005/05/09/sitereviewsorg-supports-hreview-i-think/ has announced] that his [http://en-us.sitereviews.org/ SiteReviews.org] (which reviews websites) publishes its reviews using hReview, e.g. here is the [http://en-us.sitereviews.org/review-photomatt.net review on SiteReviews.org for photomatt.net].<br />
* [http://www.myelin.co.nz/post/ Phillip Pearson] is publishing hReviews in the [http://coffee.gen.nz/rss/reviews RSS feed of cafe reviews] on his [http://coffee.gen.nz/ kiwi coffee review site], which of course has the reviews in HTML with embedded hReview markup as well.<br />
* [http://station11.net/ticker/ Kjell] is publishing his link blog as a [http://station11.net/ticker/ list of hReviews].<br />
* [http://epeus.blogspot.com/ Kevin Marks] has [http://epeus.blogspot.com/2005_04_01_epeus_archive.html#111484565269684374 published two hReviews] and used unicode "star" characters for his ratings!<br />
* JamesStewart is publishing hReviews in the location pages at his [http://grwifi.net Grand Rapids WiFi site].<br />
* [http://soldierant.net/ Soldier Ant] has [http://soldierant.net/archives/2005/06/product_review.html reviewed a cordless phone].<br />
* [http://www.happenchance.co.uk/ Paul Livingstone] uses hreview to voice his opinion on [http://www.happenchance.co.uk/archives/2005/07/war_of_the_worl.php books], [http://www.happenchance.co.uk/archives/2005/03/im_going_to_fin.php movies] and [http://www.happenchance.co.uk/archives/2005/05/eels_carling_ac.php music].</div>MarkPilgrimhttps://microformats.org/wiki/index.php?title=hreview-examples&diff=2138hreview-examples2005-10-13T21:59:24Z<p>MarkPilgrim: </p>
<hr />
<div>= hReview examples =<br />
<br />
Example [[hreview|hReviews]].<br />
<br />
__TOC__<br />
<br />
== Authors ==<br />
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]<br />
* [http://360.yahoo.com/alidiabali Ali Diab],[http://yahoo.com Yahoo! Inc.]<br />
* [http://spaces.msn.com/members/ianmcallister/ Ian McAllister], [http://microsoft.com/ Microsoft Corporation]<br />
* [http://journals.aol.com/panzerjohn/abstractioneer John Panzer], [http://www.aol.com America Online, Inc.]<br />
* [http://ifindkarma.com/blog Adam Rifkin], [http://labs.commerce.net/ CommerceNet Labs]<br />
* [http://sippey.typepad.com/ Michael Sippey], [http://sixapart.com Six Apart, Ltd.]<br />
<br />
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.<br />
<br />
=== Restaurant reviews ===<br />
<br />
Here is an example of a simple online restaurant review:<br />
<br />
<pre><nowiki><br />
<div><br />
<span>5 stars out of 5 stars</span><br />
<h4>Crepes on Cole is awesome</h4><br />
<span>Reviewer: <span>Tantek</span> - April 18, 2005</span><br />
<blockquote><p><br />
Crepes on Cole is one of the best little creperies in San Francisco. <br />
Excellent food and service. Plenty of tables in a variety of sizes <br />
for parties large and small. Window seating makes for excellent <br />
people watching to/from the N-Judah which stops right outside. <br />
I've had many fun social gatherings here, as well as gotten <br />
plenty of work done thanks to neighborhood WiFi.<br />
</p></blockquote><br />
<p>Visit date: <span>April 2005</span></p><br />
<p>Food eaten: <span>Florentine crepe</span></p><br />
</div><br />
</nowiki></pre><br />
<br />
Adding hReview to this review is quite simple:<br />
<br />
<pre><nowiki><br />
<div class="hreview"><br />
<span><span class="rating">5</span> out of 5 stars</span><br />
<h4 class="summary"><span class="item fn">Crepes on Cole</span> is awesome</h4><br />
<span>Reviewer: <span class="reviewer fn">Tantek</span> - <br />
<abbr class="dtreviewed" title="20050418T2300-0700">April 18, 2005</abbr></span><br />
<blockquote class="description"><p><br />
Crepes on Cole is one of the best little creperies in San Francisco.<br />
Excellent food and service. Plenty of tables in a variety of sizes <br />
for parties large and small. Window seating makes for excellent <br />
people watching to/from the N-Judah which stops right outside. <br />
I've had many fun social gatherings here, as well as gotten <br />
plenty of work done thanks to neighborhood WiFi.<br />
</p></blockquote><br />
<p>Visit date: <span>April 2005</span></p><br />
<p>Food eaten: <span>Florentine crepe</span></p><br />
</div><br />
</nowiki></pre><br />
<br />
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.<br />
<br />
This sample hReview could be rendered like this:<br />
<br />
5 stars out of 5 stars<br /><br />
'''Crepes on Cole is awesome'''<br /><br />
Reviewer: Tantek - April 18, 2005<br /><br />
<br />
<blockquote>Crepes on Cole is one of the best little creperies in San Francisco. Excellent food and service. Plenty of tables in a variety of sizes for parties large and small. Window seating makes for excellent people watching to/from the N-Judah which stops right outside. I've had many fun social gatherings here, as well as gotten plenty of work done thanks to neighborhood wifi.</blockquote><br />
<br />
Visit date: April 2005<br /><br />
Food eaten: Florentine crepe<br /><br />
<br />
==== Multidimensional Restaurant Review ====<br />
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.<br />
<br />
Here is one such review in text format:<br />
<br />
Cafe Borrone<br />
<br />
1010 El Camino Real, Menlo Park, CA 94025, +1-650-327-0830;<br />
cafeborrone.com<br />
<br />
Food: 18/30; Ambience: 19/30; Service: 15/30; Price: $$...<br />
<br />
This cafe is a welcoming oasis on the Peninsula. It even has a fountain<br />
outside which cloaks the nearby sounds of El Camino traffic. Next door to a <br />
superb indy bookstore, Cafe Borrone is an ideal spot to grab a coffee or a <br />
snack to accompany a newly purchased book or imported periodical. Soups and <br />
sandwich specials rotate daily. The corn chowder with croutons and big <br />
chunks of cheese goes especially well with a freshly toasted mini-baguette. <br />
Evenings are often crowded and may require sharing a table with a perfect <br />
stranger. Espresso afficionados will appreciate the Illy coffee. Noise <br />
levels can vary from peaceful in the late mornings to nearly overwhelming on <br />
jazz band nights.<br />
<br />
As an hReview:<br />
<br />
<pre><nowiki><br />
<div class="hreview"><br />
<div class="item vcard"><br />
<div class="fn org summary">Cafe Borrone</div><br />
<span class="adr"><br />
<span class="street-address">1010 El Camino Real</span>,<br />
<span class="locality">San Francisco</span>,<br />
<span class="region">CA</span><br />
<span class="postal-code">94025</span>,<br />
</span><br />
<span class="tel"><span class="voice work">+1-650-327-0830</span></span>;<br />
<a class="url" href="http://cafeborrone.com">cafeborrone.com</a><br />
</div><br />
<ul class="categories"><br />
<li><a href="http://en.wikipedia.org/wiki/Food" rel="tag"><br />
Food: <span class="rating">18</span>/<span class="best">30</span></a>;</li><br />
<li><a href="http://flickr.com/photos/tags/Ambience" rel="tag"><br />
Ambience: <span class="rating">19</span>/<span class="best">30</span></a>;</li><br />
<li><a href="http://en.wikipedia.org/wiki/Service" rel="tag"><br />
Service: <span class="rating">15</span>/<span class="best">30</span></a>;</li><br />
<li><a href="http://en.wikipedia.org/wiki/Price" rel="tag"><br />
Price: <abbr class="rating" title="2">$$</abbr>...</a></li><br />
</ul><br />
<blockquote class="description"><p><br />
This <abbr class="type" title="business"><br />
<a href="http://en.wikipedia.org/wiki/cafe" rel="tag">cafe</a></abbr> <br />
is a welcoming oasis on the Peninsula. <br />
It even has a fountain outside which nearly eliminates <br />
the sounds of El Camino traffic. Next door to a superb indy bookstore, <br />
Cafe Borrone is an ideal spot to grab a <br />
<a href="http://en.wikipedia.org/wiki/coffee" rel="tag">coffee</a> <br />
or a meal to accompany a newly purchased book or imported periodical. <br />
<a href="http://technorati.com/tag/soup" rel="tag">Soups</a> and <br />
<a href="http://technorati.com/tag/sandwich" rel="tag">sandwich</a> <br />
specials rotate daily. The corn chowder with croutons and big chunks of cheese <br />
goes especially well with a freshly toasted mini-baguette. Evenings are <br />
often crowded and may require sharing a table with a perfect stranger. <br />
<a href="http://flickr.com/photos/tags/espresso" rel="tag">Espresso</a> <br />
afficionados will appreciate the <br />
<a href="http://en.wikipedia.org/wiki/Illy" rel="tag">Illy</a> coffee. <br />
Noise levels can vary from peaceful in the late mornings to nearly overwhelming on <br />
<a href="http://en.wikipedia.org/wiki/jazz" rel="tag">jazz</a> band nights.<br />
</p></blockquote><br />
Review (<a href="http://microformats.org/wiki/hreview"> <br />
hReview v<span class="version">0.2</span></a>)<br />
by <span class="reviewer">anonymous</span>, <br />
<abbr class="dtreviewed" title="20050428T2130-0700">April 28th, 2005</abbr>.<br />
</div><br />
</nowiki></pre><br />
<br />
With an accompanying CSS style sheet like:<br />
<br />
<pre><nowiki><br />
a.url { display:block }<br />
ul.categories { margin:1em 0; padding:0 }<br />
.categories li { display:inline }<br />
</nowiki></pre><br />
<br />
This hReview could be presented similar to the original text:<br />
<br />
Cafe Borrone<br /><br />
1010 El Camino Real, Menlo Park, CA 94025, +1-650-327-0830;<br /><br />
[http://cafeborrone.com/ cafeborrone.com]<br /><br />
<br /><br />
[http://en.wikipedia.org/wiki/Food Food: 18/30];<br />
[http://flickr.com/photos/tags/Ambience Ambience: 19/30];<br />
[http://en.wikipedia.org/wiki/Service Service: 15/30];<br />
[http://en.wikipedia.org/wiki/Price Price: $$...]<br /><br />
<br />
<blockquote>This [http://en.wikipedia.org/wiki/cafe cafe] is a welcoming oasis on the Peninsula. It even has a fountain outside which cloaks the nearby sounds of El Camino traffic. Next door to a superb indy bookstore, Cafe Borrone is an ideal spot to grab a [http://en.wikipedia.org/wiki/coffee coffee] or a snack to accompany a newly purchased book or imported periodical. [http://technorati.com/tag/soup Soups] and [http://technorati.com/tag/sandwich sandwich] specials rotate daily. The corn chowder with croutons and big chunks of cheese goes especially well with a freshly toasted mini-baguette. Evenings are often crowded and may require sharing a table with a perfect stranger. [http://flickr.com/photos/tags/espresso Espresso] afficionados will appreciate the [http://en.wikipedia.org/wiki/Illy Illy] coffee. Noise levels can vary from peaceful in the late mornings to nearly overwhelming on [http://en.wikipedia.org/wiki/jazz jazz] band nights.</blockquote><br />
<br />
Review ([http://microformats.org/wiki/hreview hReview v0.2]) by anonymous, April 28th, 2005.<br />
<br />
=== Product review ===<br />
Here is an example of a product review:<br />
<br />
<pre><nowiki><br />
<div><br />
<a href="http://www.amazon.com/exec/obidos/ASIN/B000089CJI/"><br />
<img src="http://images.amazon.com/images/P/B000089CJI.01._SCTHUMBZZZ_.jpg" <br />
alt="Album cover photo: The Postal Service: Give Up." /><br />
The Postal Service: Give Up</a><br />
<blockquote><p><br />
"The people thought they were just being rewarded for treating others <br />
as they like to be treated, for obeying stop signs and curing diseases, <br />
for mailing letters with the address of the sender... Don't wake me, <br />
I plan on sleeping in..."<br />
</p><p><br />
"Nothing Better" is a great track on this album, too... <br />
</p></blockquote><br />
(*****)<br />
</div><br />
</nowiki></pre><br />
<br />
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:<br />
<br />
<pre><nowiki><br />
<div class="hreview"><br />
<a class="item url" href="http://www.amazon.com/exec/obidos/ASIN/B000089CJI/"><br />
<img src="http://images.amazon.com/images/P/B000089CJI.01._SCTHUMBZZZ_.jpg" <br />
alt="Album cover photo: The Postal Service: Give Up. " <br />
class="photo" /><br />
<span class="fn">The Postal Service: Give Up</span></a><br />
<blockquote class="description"><p><br />
"The people thought they were just being rewarded for treating others <br />
as they like to be treated, for obeying stop signs and curing diseases, <br />
for mailing letters with the address of the sender... Don't wake me, <br />
I plan on sleeping in..."<br />
</p><p><br />
"Nothing Better" is a great track on this album, too... <br />
</p></blockquote><br />
(<abbr class="rating" title="5">*****</abbr>)<br />
<p class="reviewer vcard">Review by <br />
<a class="url fn" href="http://ifindkarma.com/blog/">Adam Rifkin</a>, <br />
<abbr class="dtreviewed" title="200502">February 2005</abbr><br />
</p><br />
</div><br />
</nowiki></pre><br />
<br />
And this hReview might be presented like this:<br />
<br />
<br />
[Album cover photo: ]<br />
[The Postal Service:]<br />
[ Give Up ]<br />
<br />
The Postal Service: Give Up<br />
<br />
<blockquote>"The people thought they were just being rewarded for treating others as they like to be treated, for obeying stop signs and curing diseases, for mailing letters with the address of the sender... Don't wake me, I plan on sleeping in..."</blockquote><br />
<br />
<blockquote>"Nothing Better" is a great track on this album, too... </blockquote><br />
<br />
(*****)<br />
<br />
Review by Adam Rifkin, February 2005.<br />
<br />
=== Movie Review ===<br />
Finally, here is an example of a movie review.<br />
<br />
<pre><nowiki><br />
<div><br />
<span>anonymous, April 18th, 2005</span><br />
<div><br />
<a lang="zh" href="http://www.imdb.com/title/tt0299977/"><br />
Ying Xiong (<span lang="en">HERO</span>)<br />
</a><br />
</div><br />
<div>Rating: 4 out of 5</div><br />
<blockquote><p><br />
This movie has great visuals and music.<br />
</p></blockquote><br />
</div><br />
</nowiki></pre><br />
<br />
With hReview:<br />
<br />
<pre><nowiki><br />
<div class="hreview"><br />
<span class="reviewer"><br />
<span class="fn">anonymous</span>, <br />
<abbr class="dtreviewed" title="20050418">April 18th, 2005</abbr><br />
</span><br />
<div class="item"><br />
<a lang="zh" class="url fn" href="http://www.imdb.com/title/tt0299977/"><br />
Ying Xiong (<span lang="en">HERO</span>)<br />
</a><br />
</div><br />
<div>Rating: <span class="rating">4</span> out of 5</div><br />
<blockquote class="description"><p><br />
This movie has great music and visuals.<br />
</p></blockquote><br />
</div><br />
</nowiki></pre><br />
<br />
Which could be presented like this:<br />
<br />
anonymous, April 18th, 2005<br /><br />
Ying Xiong (HERO)<br /><br />
Rating: 4 out of 5<br /><br />
<br />
This movie has great music and visuals.<br />
<br />
== Examples in the wild ==<br />
This section is '''informative'''.<br />
<br />
The following sites have published hReviews, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If you publish hReviews on your own page, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.<br />
<br />
* [http://blog.ftwr.co.uk/ Peter Westwood] has written an [http://blog.ftwr.co.uk/archives/2005/10/03/blubeckers-hampton-court/ hReview of Blubeckers Hampton Court]<br />
* [http://dougal.gunters.org/blog/ Dougal] has published an [http://dougal.gunters.org/blog/2005/08/03/french-vanilla-latte hReview of Wolfgang Puck’s Gourmet French Vanilla Latte].<br />
* [http://www.dinnerbuzz.com/ Dinnerbuzz] is a great site for posting tagged reviews of restaurants, and they publish and summarize all their reviews in hReview!<br />
* [http://soldierant.net/ Bryce Glass] posted an [http://soldierant.net/archives/2005/06/product_review.html hReview of the Uniden ELBT 595 Bluetooth Cordless Phone].<br />
* dda posted an [http://sungnyemun.org/wordpress/?p=20 hReview of hReview] :) <br />
* An [http://tbp.xomerang.com/?p=3 hReview of Caffè Camardo coffee].<br />
* [http://loadaveragezero.com/hnav/contact.php Douglas Clifton] posted [http://loadaveragezero.com/#May-12-2005 comments] regarding adapting his list of ~800 [http://loadaveragezero.com/app/drx Developer Resources] as a format for evaluating hReview.<br />
* [http://www.oliverbrown.me.uk/ Oliver Brown] [http://www.oliverbrown.me.uk/2005/05/09/sitereviewsorg-supports-hreview-i-think/ has announced] that his [http://en-us.sitereviews.org/ SiteReviews.org] (which reviews websites) publishes its reviews using hReview, e.g. here is the [http://en-us.sitereviews.org/review-photomatt.net review on SiteReviews.org for photomatt.net].<br />
* [http://www.myelin.co.nz/post/ Phillip Pearson] is publishing hReviews in the [http://coffee.gen.nz/rss/reviews RSS feed of cafe reviews] on his [http://coffee.gen.nz/ kiwi coffee review site], which of course has the reviews in HTML with embedded hReview markup as well.<br />
* [http://station11.net/ticker/ Kjell] is publishing his link blog as a [http://station11.net/ticker/ list of hReviews].<br />
* [http://epeus.blogspot.com/ Kevin Marks] has [http://epeus.blogspot.com/2005_04_01_epeus_archive.html#111484565269684374 published two hReviews] and used unicode "star" characters for his ratings!<br />
* JamesStewart is publishing hReviews in the location pages at his [http://grwifi.net Grand Rapids WiFi site].<br />
* [http://soldierant.net/ Soldier Ant] has [http://soldierant.net/archives/2005/06/product_review.html reviewed a cordless phone].<br />
* [http://www.happenchance.co.uk/ Paul Livingstone] uses hreview to voice his opinion on [http://www.happenchance.co.uk/archives/2005/07/war_of_the_worl.php books], [http://www.happenchance.co.uk/archives/2005/03/im_going_to_fin.php movies] and [http://www.happenchance.co.uk/archives/2005/05/eels_carling_ac.php music].</div>MarkPilgrimhttps://microformats.org/wiki/index.php?title=hreview&diff=2139hreview2005-10-13T21:57:59Z<p>MarkPilgrim: </p>
<hr />
<div>= hReview 0.2 =<br />
<br />
hReview is a simple, open, distributed reviews format suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. hReview is one of several [[microformats]] open standards.<br />
<br />
__TOC__<br />
<br />
== Draft Specification 2005-06-07 ==<br />
<br />
=== Editor ===<br />
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]<br />
<br />
=== Authors ===<br />
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]<br />
* [http://360.yahoo.com/alidiabali Ali Diab],[http://yahoo.com Yahoo! Inc.]<br />
* [http://spaces.msn.com/members/ianmcallister/ Ian McAllister], [http://microsoft.com/ Microsoft Corporation]<br />
* [http://journals.aol.com/panzerjohn/abstractioneer John Panzer], [http://www.aol.com America Online, Inc.]<br />
* [http://ifindkarma.com/blog Adam Rifkin], [http://labs.commerce.net/ CommerceNet Labs]<br />
* [http://sippey.typepad.com/ Michael Sippey], [http://sixapart.com Six Apart, Ltd.]<br />
<br />
== Introduction ==<br />
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.<br />
<br />
In order to enable and encourage the sharing, distribution, syndication, and aggregation, of reviews, the authors propose the hReview MicroFormat, an open standard for distributed reviews. The authors have researched numerous earlier attempts at ReviewsFormats, and have designed hReview around a simple minimal schema for reviews. Feedback is encouraged on the ["hReviewFeedback"] page.<br />
<br />
=== Working Name ===<br />
The name "hReview" is a working name for this microformat. The name was suggested as it shares much with the hCard and hCalendar microformats, despite not having an IETF RFC to reference for a normative schema.<br />
<br />
=== Copyright ===<br />
{{MicroformatCopyrightStatement2005}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
=== Inspiration and Acknowledgments ===<br />
Thanks to everyone who responded to the open call for implementor participation for hReview. The authors in particular wish to thank the following individuals for their constructive input and feedback: [http://www.richardault.com/ Richard Ault], [http://dannyayers.com Danny Ayers], [http://www.vertexdev.com/~jeff/ Jeffrey Barr],[http://adriancuthbert.blogspot.com/ Adrian Cuthbert],[http://jason.defillippo.com/ Jason DeFillippo], [http://www.hybernaut.com/bdv Brian Del Vecchio], Scott Derringer, [http://budgibson.com/home/ Bud Gibson], [http://joi.ito.com/ Joi Ito], [http://www.kanai.net/weblog/ Gen Kanai],[http://niallkennedy.com/ Niall Kennedy], [http://labs.commerce.net/wiki/index.php/Rohit_Khare Rohit Khare], [http://theryanking.com/ Ryan King], [http://www.jluster.org/ Jonas Luster], [http://epeus.blogspot.com/ Kevin Marks], [http://www.powazek.com/ Derek Powazek], [http://www.judysbook.com/ Jeff Rodenburg], [http://sifry.com/alerts/ David Sifry], [http://jystewart.net/ James Stewart], [http://kung-foo.tv/ Adriaan Tijsseling], [http://www.flashenabled.com/ Phillip Torrone], Thai Tran, [http://w6daily.winn.com/ Phillip Winn], [http://yohei-y.blogspot.com YAMAMOTO Yohei].<br />
<br />
=== Scope ===<br />
Reviews consistently share several common fields. Where possible hReview has been based on this minimal common subset.<br />
<br />
==== Out of scope ====<br />
Fields that are type-specific have been omitted from hReview. It is important that hReview be kept simple and minimal from the start. Additional features can be added as deemed necessary by practical implementation experience.<br />
<br />
The concept of a "universal object identifier", that is, how to identify the same object/item/product across different shopping sites, though something very useful to have, is outside the scope of this format.<br />
<br />
== Semantic XHTML Design Principles ==<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
=== In General ===<br />
The hReview format is based on a set of fields common to numerous review sites and formats in use today on the web. Where possible field names have been chosen based on those defined by the related [[hcard|hCard]] and [[hcalendar|hCalendar]] standards.<br />
<br />
=== Schema ===<br />
The hReview schema consists of the following:<br />
<br />
* hReview<br />
** version. optional. text.<br />
** summary. optional. text.<br />
** item type. optional. product | business | event | person | place | website | url.<br />
** item info. required. (fn || url || photo ) | [[hcard|hCard]] (for person or business).<br />
** reviewer. required. [[hcard|hCard]] | fn | email | url.<br />
** dtreviewed. required. ISO8601 absolute date time.<br />
** rating. optional. integer [1-5], with optional alternate worst (default:1) and/or best (default:5), also integers.<br />
** description. optional. text with optional valid XHTML markup.<br />
** tags. optional. keywords or phrases, using RelTag, each with optional rating.<br />
** permalink. optional.<br />
<br />
=== Field details ===<br />
The fields of the hReview schema represent the following:<br />
<br />
'''version''':: This optional field permits hReview publishers to specify a particular version of hReview that their content uses. By omitting this field, the publisher is stating that implementations may interpret the hReviews according to any version of the hReview specification v0.2 or later. In practice the authors of this specification are comitted to maintaining backward compatibility with content produced using earlier versions of the specification. This field is syntax compatible with, and thus reuses the semantics of "VERSION" as defined in vCard RFC2426 section "3.6.9 VERSION Type Definition". The value of this field for this specification is "0.2".<br />
<br />
'''summary''':: This optional field serves as a title for the review itself.<br />
<br />
'''item type''':: This optional field "type" provides the type of the item being reviewed, one of the following: product, business, event, person, place, website, url. <br />
<br />
'''item info''':: This required field MUST have at a minimum the name ("fn" - the formatted text corresponding to the name) of the item , SHOULD provide at least one URI ("url") for the item, and MAY provide at least one URL to a photo or depiction ("photo") of the item. For items of type person or business, the item info (fn, url, photo) SHOULD be encapsulated in an [[hcard|hCard]]. Unique item IDs (e.g. ISBNs, UPCs) MAY be represented as a URN ("url") for the item.<br />
<br />
'''reviewer''':: The person who authored the review. An hCard representing the reviewer SHOULD be provided with full name and URL. Alternatively, just a name, email address, or URL to the person MAY be provided. To specify more than one of those, encapsulate them in an hCard. For anonymous reviews, use "anonymous" (without quotes) for the full name of the reviewer.<br />
<br />
'''dtreviewed''':: This required field MUST provide an ISO8601 absolute date time of when the review was written or otherwise authored. This field SHOULD use UTC, but MAY use the time zone offset syntax.<br />
<br />
'''rating''':: The rating is an integer from 1 to 5 inclusive indicating a rating for the item, higher indicating a better rating. Optionally a different integral "worst" value and/or "best" value MAY be specified (e.g. 6 from 0-10).<br />
<br />
'''description''':: This optional field contains the full text representing the written opinion of the reviewer. The field MAY include valid XHTML markup (e.g. paragraphs). User agents SHOULD preserve any markup. Multiple descriptions or section descriptions (e.g. pros and cons, plusses and minusses) SHOULD be included in the description field.<br />
<br />
'''tags''':: Tags are represented using a list of keywords or phrases (using the [[rel-tag|RelTag]] microformat for each individual keyword or phrase tag) that the reviewer associates with the item. The reviewer MAY optionally provide a tag-specific rating inside each [[rel-tag|RelTag]], e.g. ambience:5. Tag-specific ratings by default use the same range as an overall rating for the item if present, and MAY also have a custom worst...best range specified. Authors MAY enclose all tags for a review inside an element with a specific classname, e.g. "categories" (from vCard RFC2426 and iCalendar RFC2445), but are not required to do so.<br />
<br />
'''permalink''':: This optional field is a URL for the hReview. In addition to using the <code><a href></code> tag for this field, the attribute <code>rel="self bookmark"</code> MUST be used to indicate that the hyperlink is a permalink for the review itself. If the hyperlink already contains a <code>rel</code> attribute, then the values <code>self</code> and <code>bookmark</code> MUST be included among the space-separated set of values in the attribute. Indexers MAY treat the permalink of a review as a unique ID in order to identify and collate the same review from multiple sources (such as indexing a page multiple times). The permalink MAY also be used to indicate or imply the origin of the review. Authors MAY use the classname of "permalink" on the element representing the permalink, but are not required to do so.<br />
<br />
The following field names have been reused from the [[hcard|hCard]] and [[hcalendar|hCalendar]] microformats: <code>version, summary, fn, url, email, photo, description, categories</code>. In addition, items and reviewers described by hCards MAY contain any hCard field. The rel value "self" has been reused from the [http://atompub.org/2005/07/11/draft-ietf-atompub-format-10.html Atom 1.0 specification].<br />
<br />
=== More Semantic Equivalents ===<br />
<br />
For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.: <br />
<br />
* For any "url", use <code><a class="url" href="...">...</a></code> inside the element with class="hreview" in hReview. <br />
* Similarly, any "email", use <code><nowiki><a class="email" href="mailto:...">...</a></nowiki></code> <br />
* And for "photo", use <code><img class="photo" src="..." alt="Photo of ..." /></code> <br />
<br />
* Ratings are often presented either as a set of images or characters, e.g. "***". For these, the <code>&lt;abbr&gt;</code> element is particularly useful, as such characters are an abbreviation for the precise rating, e.g. <code>&lt;abbr class="rating" title="3"&gt;***&lt;/abbr&gt;</code>. This is further explored in the next section.<br />
<br />
==== Language ====<br />
* To explicitly convey the natural language that an hReview is written in, use the standard (X)HTML 'lang' attribute on the element with class="hreview", e.g. <code>&lt;div class="hreview" lang="en"&gt; ... &lt;/div&gt;</code> If portions of an hReview (e.g. the item name) are in a different language, use the 'lang' attribute on those portions.<br />
* hReview processors which need to handle the language of reviews MUST process the standard (X)HTML 'lang' attribute as specified.<br />
<br />
=== Human vs. Machine Readable ===<br />
If an <code>&lt;abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value. <br />
<br />
Similarly, if an <code><img /></code> element is used for one or more properties, it MUST be treated as follows: <br />
<br />
# For the "photo" property and any other property that takes a URL as its value, the <code>src="..."</code> attribute provides the property value. <br />
# For other properties, the <code><img /></code> element's '<code>alt</code>' attribute is the value of the property.<br />
<br />
=== Notes ===<br />
This section is informative.<br />
<br />
* 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.<br />
* The enumerated list of item types is under development and may be extended.<br />
* Each type may have custom hReview fields that follow the common set.<br />
* Additional details about a particular item should be specified with the rest of the item's info at the URL provided for the item.<br />
* Most rating systems use the range 1 to 5, and most of those represent the rating as a number of stars. Sites may use whatever graphic they wish to represent the rating.<br />
<br />
== Examples ==<br />
<br />
Moved to [[hreview-examples]]<br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
The following implementations have been developed which either generate or parse hReviews. If you have an hReview implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.<br />
<br />
* [http://www.goodpic.com/mt/aws/index_us.html Goodpic] has written:<br />
** [http://www.goodpic.com/mt/aws/index_us.html hReview creator for Amazon.com products]<br />
** [http://www.goodpic.com/mt/aws/index_uk.html hReview creator for Amazon.co.uk products]<br />
** [http://www.goodpic.com/mt/aws/index_uk.html hReview creator for Amazon.co.jp products]<br />
** be sure to choose the "hRview" tab from among the choices on the page that says "You can choose from more than 30 designs, please click the tab to select categories."<br />
* See the microformats.org [http://microformats.org/code/hreview/creator hReview creator]<br />
* [http://www.eigaseikatu.com/ Eigaseikatu], one of the largest movie community sites in Japan, provides [http://www.eigaseikatu.com/hreview/ hReview creator] for movie review.<br />
* [http://sungnyemun.org/wordpress/?p=22 hReview plugin for WordPress]<br />
* [http://theryanking.com/ Ryan King] has an [http://theryanking.com/microformats/hreview-creator.html hReview Creator].<br />
* [http://rvu.ning.com/ Rvu] is a [http://ning.com Ning] app that lets you write reviews of reviews and publishes them in hReview<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[hcard|hCard]]<br />
* [[hcalendar|hCalendar]]<br />
* [[rel-tag]]<br />
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]<br />
* [http://www.ietf.org/rfc/rfc3986.txt RFC3986]<br />
* [http://atompub.org/2005/07/11/draft-ietf-atompub-format-10.html Atom 1.0]<br />
<br />
=== Informative References ===<br />
* [http://www.w3.org/TR/REC-CSS1 CSS1]<br />
* ISO.8601.1988<br />
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.<br />
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]<br />
* [http://www.ietf.org/rfc/rfc3667.txt RFC3667]<br />
* [http://www.ietf.org/rfc/rfc3668.txt RFC3668]<br />
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]<br />
* Other reviews efforts. See [[reviews-formats]].<br />
* Contributed from http://developers.technorati.com/wiki/hReview.<br />
<br />
==== Similar Work ====<br />
* [[xoxo]]<br />
<br />
== Work in progress ==<br />
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. <br />
<br />
=== Changes from v0.1 ===<br />
The following changes have been made in hReview v0.2:<br />
# '''version'''. Added optional "version" field.<br />
# '''language'''. Made explicit the reuse of (X)HTML 'lang' attribute to convey natural language information.<br />
# '''tags requirement removed'''. Removed requirement of classname "tags" for the tags field, and thus removed the requirement to have an explicit tags field at all, permitting tags anywhere inside the hReview, e.g. inside the description.<br />
# '''permalink requirement removed'''. Removed requirement of classname "permalink", as it is unnecessary, given that the permalink field explicitly requires a hyperlink with rel values of "self" and "bookmark".<br />
# Updated examples accordingly.<br />
<br />
== Discussions ==<br />
<br />
* Feedback is encouraged on the [[hreview-feedback]] page.<br />
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
<br />
=== Q&A ===<br />
* If you have any questions about hReview, check the [[hreview-faq|hReview FAQ]], and if you don't find answers, add your questions to the end!<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[hreview-issues|hReview issues]] document.</div>MarkPilgrimhttps://microformats.org/wiki/index.php?title=hcalendar-examples&diff=2144hcalendar-examples2005-10-13T21:54:05Z<p>MarkPilgrim: </p>
<hr />
<div>= hCalendar examples =<br />
<br />
Example [[hcalendar|hCalendars]].<br />
<br />
== Authors ==<br />
* [http://diveintomark.org/ Mark Pilgrim]<br />
* [http://theryanking.com/ Ryan King]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
<br />
== RFC 2445 examples in hCalendar ==<br />
These are 1:1 hCalendar examples for each example in RFC 2445.<br />
<br />
Errata applied from [http://www.rfc-editor.org/cgi-bin/errata.pl#rfc2445 here].<br />
<br />
=== 4.6.1 Event Component ===<br />
The following is an example of the "VEVENT" calendar component used to represent a meeting that will also be opaque to searches for busy time:<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
UID:19970901T130000Z-123401@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19970903T163000Z<br />
DTEND:19970903T190000Z<br />
SUMMARY:Annual Employee Review<br />
CLASS:PRIVATE<br />
CATEGORIES:BUSINESS,HUMAN RESOURCES<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h5 class="summary">Annual Employee Review</h5><br />
<div>posted on <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></div><br />
<div>UID: <span class="uid">19970901T130000Z-123401@host.com</span></div><br />
<div>Dates: <abbr class="dtstart" title="19970903T163000Z">Septempter 3, 1997, 16:30</abbr> -<br />
<abbr class="dtend" title="19970903T190000Z">19:00 UTC</abbr></div><br />
<div>This meeting is <strong class="class">private</strong>.</div><br />
<div>Filed under:</div><br />
<ul><br />
<li class="category">Business</li><br />
<li class="category">Human Resources</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<div class="vevent"><br />
<br />
<h5 class="summary">Annual Employee Review</h5><br />
<div>posted on <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></div><br />
<div>UID: <span class="uid">19970901T130000Z-123401@host.com</span></div><br />
<div>Dates: <abbr class="dtstart" title="19970903T163000Z">Septempter 3, 1997, 16:30</abbr> - <abbr class="dtend" title="19970903T190000Z">19:00 UTC</abbr></div><br />
<div>This meeting is <strong class="class">Private</strong>.</div><br />
<div>Filed under:</div><br />
<ul><br />
<li class="category">Business</li><br />
<li class="category">Human Resources</li><br />
</ul><br />
</div><br />
<br />
==== Example 2 ====<br />
The following is an example of the "VEVENT" calendar component used to represent a reminder that will not be opaque, but rather transparent, to searches for busy time:<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
UID:19970901T130000Z-123402@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19970401T163000Z<br />
DTEND:19970402T010000Z<br />
SUMMARY:Laurel is in sensitivity awareness class.<br />
CLASS:PUBLIC<br />
CATEGORIES:BUSINESS,HUMAN RESOURCES<br />
TRANSP:TRANSPARENT<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar fragment:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h5 class="summary">Laurel is in sensitivity awareness class.</h5><br />
<div>Posted on: <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></div><br />
<div class="uid">19970901T130000Z-123402@host.com</div><br />
<div>Dates: <abbr class="dtstart" title="19970401T163000Z">April 1, 1997, 16:30 UTC</abbr>-<br />
<abbr class="dtend" title="19970402T010000Z">April 2, 1997 01:00 UTC</abbr></div><br />
<div>This event is <span class="class">public</span> and <span class="transp">transparent</span> to free/busy scheduling.</div><br />
<div>Filed under:</div><br />
<ul><br />
<li class="category">Business</li><br />
<li class="category">Human Resources</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
<div class="vevent"><br />
<h5 class="summary">Laurel is in sensitivity awareness class.</h5><br />
<div>Posted on: <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></div><br />
<div class="uid">19970901T130000Z-123402@host.com</div><br />
<div>Dates: <abbr class="dtstart" title="19970401T163000Z">April 1, 1997, 16:30 UTC</abbr>-<abbr class="dtend" title="19970402T010000Z">April 2, 1997 01:00 UTC</abbr></div><br />
<div>This event is <span class="class">public</span> and <span class="transp">transparent</span> to free/busy scheduling.</div><br />
<div>Filed under:</div><br />
<ul><br />
<li class="category">Business</li><br />
<li class="category">Human Resources</li><br />
</ul><br />
</div><br />
<br />
<br />
==== Example 3 ====<br />
<br />
The following is an example of the "VEVENT" calendar component used to represent an anniversary that will occur annually. Since it takes up no time, it will not appear as opaque in a search for busy time; no matter what the value of the "TRANSP" property indicates:<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
UID:19970901T130000Z-123403@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19971102<br />
SUMMARY:Our Blissful Anniversary<br />
CLASS:CONFIDENTIAL<br />
CATEGORIES:ANNIVERSARY,PERSONAL,SPECIAL OCCASION<br />
RRULE:FREQ=YEARLY<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar fragment:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h5 class="summary">Our Blissful Anniversary</h5><br />
<div>Posted on: <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></div><br />
<div class="uid">19970901T130000Z-123403@host.com</div><br />
<div>Date: <abbr class="dtstart" title="19971102">November 2, 1997</abbr></div><br />
<div>This event is <strong class="class">confidential</stong>.</div><br />
<div>Filed under:</div><br />
<ul><br />
<li class="category">Anniversary</li><br />
<li class="category">PersonaL</li><br />
<li class="category">Special Occassion</li><br />
</ul><br />
<div class="rrule">Repeat <span class="freq">yearly</span>.</div><br />
</div><br />
</nowiki></pre><br />
<br />
ISSUES:<br />
* We have a larger discusion about RRULE that needs to be resolved, hopefully these examples will help that. --RyanKing<br />
<br />
This hCalendar could be displayed as:<br />
<br />
<div class="vevent"><br />
<h5 class="summary">Our Blissful Anniversary</h5><br />
<div>Posted on: <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></div><br />
<div class="uid">19970901T130000Z-123403@host.com</div><br />
<div>Date: <abbr class="dtstart" title="19971102">November 2, 1997</abbr></div><br />
<div>This event is <span class="class">confidential</span>.</div><br />
<div>Filed under:</div><br />
<ul><br />
<li class="category">Anniversary</li><br />
<li class="category">Personal</li><br />
<li class="category">Special Occassion</li><br />
</ul><br />
<div class="rrule">Repeat <span class="freq">yearly</span></div><br />
</div><br />
<br />
<br />
=== 5. iCalendar Object Examples ===<br />
<br />
The following example specifies a three-day conference that begins at 8:00 AM EDT, September 18, 1996 and end at 6:00 PM EDT, September 20, 1996.<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
DTSTAMP:19960704T120000Z<br />
UID:uid1@host.com<br />
ORGANIZER:MAILTO:jsmith@host.com<br />
DTSTART:19960918T143000Z<br />
DTEND:19960920T220000Z<br />
STATUS:CONFIRMED<br />
CATEGORIES:CONFERENCE <br />
SUMMARY:Networld+Interop Conference<br />
DESCRIPTION:Networld+Interop Conference and Exhibit\nAtlanta World Congress Center\nAtlant\, Georgia<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar fragment:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h5 class="summary">Networld+Interop Conference</h5><br />
<div class="description">Networld+Interop Conference and Exhibit Atlanta World Congress<br />
Center Atlanta, Georgia</div><br />
<div>Posted on: <abbr class="dtstamp" title="19960704T120000Z">July 4, 1996</abbr></div><br />
<div class="uid">uid1@host.com</div><br />
<div>Organized by: <a class="organizer" href="mailto:jsmith@host.com">jsmith@host.com</a></div><br />
<div>Dates: <abbr class="dtstart" title="19960918T143000Z">September 18, 1996, 14:30 UTC</abbr> -<br />
<abbr class="dtend" title="19960920T220000Z">September 20, 1996, 22:00 UTC</abbr></div><br />
<div>Status: <span class="status">CONFIRMED</span></div><br />
<div>Filed under:</div><br />
<ul class="categories"><br />
<li>Conference</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
<div class="vevent"><br />
<h5 class="summary">Networld+Interop Conference</h5><br />
<div class="description">Networld+Interop Conference and Exhibit Atlanta World Congress<br />
Center Atlanta, Georgia</div><br />
<div>Posted on: <abbr class="dtstamp" title="19960704T120000Z">July 4, 1996</abbr></div><br />
<div class="uid">uid1@host.com</div><br />
<div>Organized by: [mailto:jsmith@host.com jsmith@host.com]</div><br />
<div>Dates: <abbr class="dtstart" title="19960918T143000Z">September 18, 1996, 14:30 UTC</abbr> -<br />
<abbr class="dtend" title="19960920T220000Z">September 20, 1996, 22:00 UTC</abbr></div><br />
<div>Status: <span class="status">confirmed</span></div><br />
<div>Filed under:</div><br />
<ul class="categories"><br />
<li>Conference</li><br />
</ul><br />
</div><br />
<br />
<br />
==== Example 2 ====<br />
The following example specifies a group scheduled meeting that begin at 8:30 AM EST on March 12, 1998 and end at 9:30 AM EST on March 12, 1998. The "Organizer" has scheduled the meeting with one or more calendar users in a group. A time zone specification for Eastern United States has been specified.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
PRODID:-//RDU Software//NONSGML HandCal//EN<br />
VERSION:2.0<br />
BEGIN:VTIMEZONE<br />
TZID:US-Eastern<br />
BEGIN:STANDARD<br />
DTSTART:19981025T020000<br />
RDATE:19981025T020000<br />
TZOFFSETFROM:-0400<br />
TZOFFSETTO:-0500<br />
TZNAME:EST<br />
END:STANDARD<br />
BEGIN:DAYLIGHT<br />
DTSTART:19990404T020000<br />
RDATE:19990404T020000<br />
TZOFFSETFROM:-0500<br />
TZOFFSETTO:-0400<br />
TZNAME:EDT<br />
END:DAYLIGHT<br />
END:VTIMEZONE<br />
BEGIN:VEVENT<br />
DTSTAMP:19980309T231000Z<br />
UID:guid-1.host1.com<br />
ORGANIZER;ROLE=CHAIR:MAILTO:mrbig@host.com<br />
ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT;CUTYPE=GROUP:MAILTO:employee-A@host.com<br />
DESCRIPTION:Project XYZ Review Meeting<br />
CATEGORIES:MEETING<br />
CLASS:PUBLIC<br />
CREATED:19980309T130000Z<br />
SUMMARY:XYZ Project Review<br />
DTSTART;TZID=US-Eastern:19980312T083000<br />
DTEND;TZID=US-Eastern:19980312T093000<br />
LOCATION:1CP Conference Room 4350<br />
END:VEVENT<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 3 ====<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
METHOD:xyz<br />
VERSION:2.0<br />
PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
BEGIN:VEVENT<br />
DTSTAMP:19970324T1200Z<br />
SEQUENCE:0<br />
UID:uid3@host1.com<br />
ORGANIZER:MAILTO:jdoe@host1.com<br />
ATTENDEE;RSVP=TRUE:MAILTO:jsmith@host1.com<br />
DTSTART:19970324T123000Z<br />
DTEND:19970324T210000Z<br />
CATEGORIES:MEETING,PROJECT<br />
CLASS:PUBLIC<br />
SUMMARY:Calendaring Interoperability Planning Meeting<br />
DESCRIPTION:Discuss how we can test c&s interoperability\nusing iCalendar and other IETF standards.<br />
LOCATION:LDB Lobby<br />
ATTACH;FMTTYPE=application/postscript:ftp://xyzCorp.com/pub/conf/bkgrnd.ps<br />
END:VEVENT<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vcalendar"><br />
<div>Method: <span class="method">xyz</span></div><br />
<div class="vevent"><br />
<div>Posted at: <span class="dtstamp">19970324T1200Z</span></div><br />
<div>Sequence: <span class="sequence">0</span></div><br />
<div>UID: <span class="uid">uid3@host1.com</span></div><br />
<div>Organzied by: <a class="organizer" href="mailto:jdoe@host1.com">jdoe@host1.com</a></div><br />
<div>Attending: <span class="attendee"><a class="value" href="mailto:jsmith@host1.com">jsmith@host1.com</a> RSVPed? <span class="rsvp">TRUE></span></span></div><br />
<div>Start Time: <abbr class="dtstart" title="19970324T123000Z">March 24, 1997 12:30 UTC</abbr></div><br />
<div>End Time: <abbr class="dtend" title="19970324T210000Z">March 24, 1997, 21:00 UTC</abbr></div><br />
<ul class="categories"><br />
<li>Meeting</li><br />
<li>Project</li><br />
</ul><br />
<div>This event is <strong class="class">Public</strong></div><br />
<div class="summary">Calendaring Interoperability Planning Meeting</div><br />
<div class="description">Discuss how we can test c&s interoperability using iCalendar and other IETF standards.</div><br />
<div class="location">LDB Lobby</div><br />
<div>Attachment: <a class="attach" type="application/postscript" href="ftp://xyzCorp.com/pub/conf/bkgrnd.ps">ftp://xyzCorp.com/pub/conf/bkgrnd.ps</a></div><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
<div class="vcalendar"><br />
<div>Method: <span class="method">xyz</span></div><br />
<div class="vevent"><br />
<div>Posted at: <span class="dtstamp">19970324T1200Z</span></div><br />
<div>Sequence: <span class="sequence">0</span></div><br />
<div>UID: <span class="uid">uid3@host1.com</span></div><br />
<div>Organzied by: [mailto:jdoe@host1.com jdoe@host1.com]</div><br />
<div>Attending: <span class="attendee">[mailto:jsmith@host1.com jsmith@host1.com], RSVPed? <span class="rsvp">TRUE></span></span></div><br />
<div>Start Time: <abbr class="dtstart" title="19970324T123000Z">March 24, 1997 12:30 UTC</abbr></div><br />
<div>End Time: <abbr class="dtend" title="19970324T210000Z">March 24, 1997, 21:00 UTC</abbr></div><br />
<ul class="categories"><br />
<li>Meeting</li><br />
<li>Project</li><br />
</ul><br />
<div>This event is <strong class="class">Public</strong></div><br />
<div class="summary">Calendaring Interoperability Planning Meeting</div><br />
<div class="description">Discuss how we can test c&s interoperability using iCalendar and other IETF standards.</div><br />
<div class="location">LDB Lobby</div><br />
<div>Attachment: <a class="attach" type="application/postscript" href="ftp://xyzCorp.com/pub/conf/bkgrnd.ps">ftp://xyzCorp.com/pub/conf/bkgrnd.ps</a></div><br />
</div><br />
</div><br />
<br />
<br />
==== Example 4 ====<br />
<br />
The following is an example of a to-do due on April 15, 1998. An audio alarm has been specified to remind the calendar user at noon, the day before the to-do is expected to be completed and repeat hourly, four additional times. The to-do definition has been modified twice since it was initially created.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
VERSION:2.0<br />
PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
BEGIN:VTODO<br />
DTSTAMP:19980130T134500Z<br />
SEQUENCE:2<br />
UID:uid4@host1.com<br />
ORGANIZER:MAILTO:unclesam@us.gov<br />
ATTENDEE;PARTSTAT=ACCEPTED:MAILTO:jqpublic@host.com<br />
DUE:19980415T235959<br />
STATUS:NEEDS-ACTION<br />
SUMMARY:Submit Income Taxes<br />
BEGIN:VALARM<br />
ACTION:AUDIO<br />
TRIGGER:19980403T120000<br />
ATTACH;FMTTYPE=audio/basic:http://host.com/pub/audio-files/ssbanner.aud<br />
REPEAT:4<br />
DURATION:PT1H<br />
END:VALARM<br />
END:VTODO<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vcalendar"><br />
<div class="vtodo"><br />
<div>Posted at: <span class="dtstamp">19980130T134500Z</span></div><br />
<div>Sequence <span class="sequence">2</span></div><br />
<div>UID: <span class="uid">uid4@host1.com</span></div><br />
<div>Organizer: [mailto:unclesam@us.gov unclesam@us.gov]</div><br />
<div>Attending: [mailto:jqpublic@host.com jqpublic@host.com], <span class="partstat">ACCEPTED</span></span></div><br />
<div>Due: <abbr class="due" title="19980415T235959">one minute before midnight on April 15, 1998</abbr></div><br />
<div>Status: <span class="status">needs-action</span></div><br />
<div class="summary">Submit Income Taxes</div><br />
<div class="valarm"><br />
<div>Action: <span class="action">AUDIO</span></div><br />
<div>Trigger: <span class="trigger">19980403T120000</span></div><br />
<div>Attachment: <a class="attach" type="audio/basic" href="http://host.com/pub/audio-files/ssbanner.aud">http://host.com/pub/audio-files/ssbanner.aud</a></div><br />
<div>Repeat: <span class="repeat">4</span></div><br />
<div>Duration: <span class="duration">PT1H</span></div><br />
</div><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
<div class="vcalendar"><br />
<div class="vtodo"><br />
<div>Posted at: <span class="dtstamp">19980130T134500Z</span></div><br />
<div>Sequence <span class="sequence">2</span></div><br />
<div>UID: <span class="uid">uid4@host1.com</span></div><br />
<div>Organizer: [mailto:unclesam@us.gov unclesam@us.gov]</div><br />
<div>Attending: [mailto:jqpublic@host.com jqpublic@host.com], <span class="partstat">ACCEPTED</span></span></div><br />
<div>Due: <abbr class="due" title="19980415T235959">one minute before midnight on April 15, 1998</abbr></div><br />
<div>Status: <span class="status">needs-action</span></div><br />
<div class="summary">Submit Income Taxes</div><br />
<div class="valarm"><br />
<div>Action: <span class="action">AUDIO</span></div><br />
<div>Trigger: <span class="trigger">19980403T120000</span></div><br />
<div>Attachment: [http://host.com/pub/audio-files/ssbanner.aud http://host.com/pub/audio-files/ssbanner.aud]</div><br />
<div>Repeat: <span class="repeat">4</span></div><br />
<div>Duration: <span class="duration">PT1H</span></div><br />
</div><br />
</div><br />
</div><br />
<br />
==== Example 5: journal entry ====<br />
The following is an example of a journal entry.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
VERSION:2.0<br />
PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
BEGIN:VJOURNAL<br />
DTSTAMP:19970324T120000Z<br />
UID:uid5@host1.com<br />
ORGANIZER:MAILTO:jsmith@host.com<br />
STATUS:DRAFT<br />
CLASS:PUBLIC<br />
CATEGORY:Project Report, XYZ, Weekly Meeting<br />
DESCRIPTION:Project xyz Review Meeting Minutes\nAgenda\n<br />
1. Review of project version 1.0 requirements.\n<br />
2. Definition of project processes.\n<br />
3. Review of project schedule.\nParticipants: John Smith, Jane Doe, Jim Dandy\n<br />
-It was decided that the requirements need to be signed off by product marketing.\n<br />
-Project processes were accepted.\n<br />
-Project schedule needs to account for scheduled holidays and employee vacation time. Check with HR for specific dates.\n<br />
-New schedule will be distributed by Friday.\n<br />
-Next weeks meeting is cancelled. No meeting until 3/23.<br />
END:VJOURNAL<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
(*note*: line-breaks have been added into the description, in reality it should be one line)<br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vcalendar"><br />
<div class="vjournal"><br />
<div>Posted at: <abbr class="dtstamp" title="19970324T120000Z">March 24, 1997, 12:00 UTC</abbr></div><br />
<div class="uid">uid5@host1.com</div><br />
<div>Organizer: <a class="organizer" href="mailto:jsmith@host.com">jsmith@host.com</a></div><br />
<div>Status: <span class="status">Draft</span></div><br />
<div>This journal is<span class="class">Public</span>.</div><br />
<div>Filed under:</div><br />
<ul class="category"><br />
<li>Project Report</li><br />
<li>xyz</li><br />
<li>Weekly Meeting</li><br />
</ul><br />
<div class="description">Project xyz Review Meeting Minutes<br /><br />
Agenda<br /><br />
1. Review of project version 1.0 requirements.<br /><br />
2. Definition of project processes.<br /><br />
3. Review of project schedule.<br /><br />
Participants: John Smith, Jane Doe, Jim Dandy<br /><br />
-It was decided that the requirements need to be signed off by product marketing.<br /><br />
-Project processes were accepted.<br /><br />
-Project schedule needs to account for scheduled holidays and employee vacation time. Check with HR for specific dates.<br /><br />
-New schedule will be distributed by Friday.<br /><br />
-Next weeks meeting is cancelled. No meeting until 3/23.<br />
</div><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
<div class="vcalendar"><br />
<div class="vjournal"><br />
<div>Posted at: <abbr class="dtstamp" title="19970324T120000Z">March 24, 1997, 12:00 UTC</abbr></div><br />
<div class="uid">uid5@host1.com</div><br />
<div>Organizer: [mailto:jsmith@host.com jsmith@host.com]</div><br />
<div>Status: <span class="status">Draft</span></div><br />
<div>This journal is<span class="class">Public</span>.</div><br />
<div>Filed under:</div><br />
<ul class="category"><br />
<li>Project Report</li><br />
<li>xyz</li><br />
<li>Weekly Meeting</li><br />
</ul><br />
<div class="description">Project xyz Review Meeting Minutes<br /><br />
Agenda<br /><br />
1. Review of project version 1.0 requirements.<br /><br />
2. Definition of project processes.<br /><br />
3. Review of project schedule.<br /><br />
Participants: John Smith, Jane Doe, Jim Dandy<br /><br />
-It was decided that the requirements need to be signed off by product marketing.<br /><br />
-Project processes were accepted.<br /><br />
-Project schedule needs to account for scheduled holidays and employee vacation time. Check with HR for specific dates.<br /><br />
-New schedule will be distributed by Friday.<br /><br />
-Next weeks meeting is cancelled. No meeting until 3/23.<br />
</div><br />
</div><br />
</div><br />
<br />
==== Example 6. Free/Busy time ====<br />
<br />
The following is an example of published busy time information. The iCalendar object might be placed in the network resource www.host.com/calendar/busytime/jsmith.ifb.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
VERSION:2.0<br />
PRODID:-//RDU Software//NONSGML HandCal//EN<br />
BEGIN:VFREEBUSY<br />
ORGANIZER:MAILTO:jsmith@host.com<br />
DTSTART:19980313T141711Z<br />
DTEND:19980410T141711Z<br />
FREEBUSY:19980314T233000Z/19980315T003000Z<br />
FREEBUSY:19980316T153000Z/19980316T163000Z<br />
FREEBUSY:19980318T030000Z/19980318T040000Z<br />
URL:http://www.host.com/calendar/busytime/jsmith.ifb<br />
END:VFREEBUSY<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
== Other ==<br />
<br />
* See [[hcalendar-brainstorming]] for more examples (which may eventually be moved here) and analysis.</div>MarkPilgrimhttps://microformats.org/wiki/index.php?title=abbr-design-pattern&diff=3172abbr-design-pattern2005-10-13T21:49:29Z<p>MarkPilgrim: </p>
<hr />
<div>= Abbr design pattern =<br />
<br />
== Purpose ==<br />
* Use the [[abbr-design-pattern]] to make text that is human readable also formally machine readable<br />
* Avoiding using the [[abbr-design-pattern]] to re-encode human text or to hide data<br />
<br />
== How to use it ==<br />
* enclose the human-friendly text that you want to make machine readable with <code>&lt;abbr></code> <br />
* as per the [[class-design-pattern]], add the appropriate <code>class</code> attribute to the <code>abbr</code> element<br />
* add a <code>title</code> attribute to the <code>abbr</code> element with the machine readable data as the value<br />
<br />
== Example ==<br />
The [[datetime-design-pattern]] formally encodes (the notoriously unparsable) datetimes into an <code>abbr</code> element.<br />
<br />
Before:<br />
<br />
<pre><br />
The party is at 10 o'clock on the 10th.<br />
</pre><br />
<br />
After:<br />
<br />
<pre><br />
The party is at <br />
<abbr class="dtstart" title="20051010T10:10:10-0100">10 o'clock on the 10th</abbr>.<br />
</pre><br />
<br />
== Discussion ==<br />
''This discussion is culled from [http://microformats.org/discuss/mail/microformats-discuss/2005-October/001277.html here]''. Consider two possible uses for the [[abbr-design-pattern]]:<br />
<br />
<ol><br />
<li><br />
using ABBR to encode machine readable data around human readable data<br />
<br />
<pre><br />
<abbr class="dtstart" title="20051010T10:10:10-0100">10 o'clock on the 10th</abbr><br />
</pre><br />
</li><br />
<li><br />
using ABBR to encode more formal human data around something less formal <br />
<br />
<pre><br />
<abbr class="author" title="Danny Ayers">Danny</abbr> <br />
</pre><br />
</li><br />
</ol><br />
<br />
Use #1 is encouraged if there's a reasonable need for it. Use #2 is discouraged under the [http://c2.com/cgi-bin/wiki?DontRepeatYourself Don't Repeat Yourself principle], as: "#2 is a case of *more* information being invisibly present, namely, the<br />
last name in this case. If someone is not willing to make some information visible, then we<br />
shouldn't be encouraging them to store that information invisibly, for all<br />
the same reasons that invisible metadata is bad/futile in the first place."<br />
<br />
''I'd like to delete this below, as the points are covered above''<br />
<br />
* Theoretically, this could be done with almost any HTML element. But is it a good idea? If it's not, is abbr the only one? [[DavidJanes]]<br />
* abbr-design-pattern should be avoided, if possible. [[RobertBachmann]]<br />
** why, or under what circumstances? For example, it is quite useful with datetimes. Should there not be other potentially analogous situations? [[DavidJanes]]<br />
<br />
== See Also ==<br />
* [[Main_Page#Design_Patterns|All microformat design patterns]]<br />
* [http://microformats.org/discuss/mail/microformats-discuss/2005-October/001277.html discussion in microformats-discuss]<br />
* [[datetime-design-pattern]] uses [[abbr-design-pattern]]<br />
* [http://www.w3.org/TR/REC-html40/struct/text.html#edef-ABBR HTML 4.01 definition]</div>MarkPilgrimhttps://microformats.org/wiki/index.php?title=hcalendar-examples&diff=2038hcalendar-examples2005-10-11T16:48:35Z<p>MarkPilgrim: </p>
<hr />
<div>= hCalendar examples =<br />
<br />
Example [[hcalendar|hCalendars]].<br />
<br />
== Authors ==<br />
* [http://diveintomark.org/ Mark Pilgrim]<br />
* [http://theryanking.com/ Ryan King]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
<br />
== RFC 2445 examples in hCalendar ==<br />
<br />
These are 1:1 hCalendar examples for each example in [http://www.ietf.org/rfc/rfc2445.txt RFC 2445].<br />
<br />
Errata applied from [http://www.rfc-editor.org/cgi-bin/errata.pl#rfc2445 here].<br />
<br />
=== 4.6.1 Event Component ===<br />
<br />
The following is an example of the "VEVENT" calendar component used to represent a meeting that will also be opaque to searches for busy time:<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
UID:19970901T130000Z-123401@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19970903T163000Z<br />
DTEND:19970903T190000Z<br />
SUMMARY:Annual Employee Review<br />
CLASS:PRIVATE<br />
CATEGORIES:BUSINESS,HUMAN RESOURCES<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Annual Employee Review</h1><br />
<p>posted on <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<p>UID: <span class="uid">19970901T130000Z-123401@host.com</span></p><br />
<p>Dates: <abbr class="dtstart" title="19970903T163000Z">Septempter 3, 1997, 16:30</abbr> -<br />
<abbr class="dtend" title="19970903T190000Z">19:00 UTC</abbr></p><br />
<p>This meeting is <span class="class">PRIVATE</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
<h1 class="summary">Annual Employee Review</h1><br />
<p>posted on <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<p>UID: <span class="uid">19970901T130000Z-123401@host.com</span></p><br />
<p>Dates: <abbr class="dtstart" title="19970903T163000Z">Septempter 3, 1997, 16:30</abbr> - <abbr class="dtend" title="19970903T190000Z">19:00 UTC</abbr></p><br />
<p>This meeting is <span class="class">PRIVATE</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
<br />
==== Example 2 ====<br />
The following is an example of the "VEVENT" calendar component used to represent a reminder that will not be opaque, but rather transparent, to searches for busy time:<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
UID:19970901T130000Z-123402@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19970401T163000Z<br />
DTEND:19970402T010000Z<br />
SUMMARY:Laurel is in sensitivity awareness class.<br />
CLASS:PUBLIC<br />
CATEGORIES:BUSINESS,HUMAN RESOURCES<br />
TRANSP:TRANSPARENT<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar fragment:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Laurel is in sensitivity awareness class.</h1><br />
<p>Posted on: <abbr class="dtstamp" title=19970901T1300Z">September 1, 1997</abbr></p><br />
<p class="uid">19970901T130000Z-123402@host.com</p><br />
<p>Dates: <abbr class="dtstart" title="19970401T163000Z">April 1, 1997, 16:30 UTC</abbr>-<br />
<abbr class="dtend" title="19970402T010000Z">April 2, 1997 01:00 UTC</abbr></p><br />
<p>This event is <span class="class">public</span> and <span class="transp">transparent</span> to free/busy scheduling.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
<div class="vevent"><br />
<h1 class="summary">Laurel is in sensitivity awareness class.</h1><br />
<p>Posted on: <abbr class="dtstamp" title=19970901T1300Z">September 1, 1997</abbr></p><br />
<p class="uid">19970901T130000Z-123402@host.com</p><br />
<p>Dates: <abbr class="dtstart" title="19970401T163000Z">April 1, 1997, 16:30 UTC</abbr>-<br />
<abbr class="dtend" title="19970402T010000Z">April 2, 1997 01:00 UTC</abbr></p><br />
<p>This event is <span class="class">public</span> and <span class="transp">transparent</span> to free/busy scheduling.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
</div><br />
<br />
==== Example 3 ====<br />
<br />
The following is an example of the "VEVENT" calendar component used to represent an anniversary that will occur annually. Since it takes up no time, it will not appear as opaque in a search for busy time; no matter what the value of the "TRANSP" property indicates:<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
UID:19970901T130000Z-123403@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19971102<br />
SUMMARY:Our Blissful Anniversary<br />
CLASS:CONFIDENTIAL<br />
CATEGORIES:ANNIVERSARY,PERSONAL,SPECIAL OCCASION<br />
RRULE:FREQ=YEARLY<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar fragment:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Our Blissful Anniversary</h1><br />
<p>Posted on: <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<p class="uid">19970901T130000Z-123403@host.com</p><br />
<p>Date: <abbr class="dtstart" title="19971102">November 2, 1997</abbr></p><br />
<p>This event is <span class="class">confidential</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">ANNIVERSARY</li><br />
<li class="category">PERSONAL</li><br />
<li class="category">SPECIAL OCCASSION</li><br />
</ul><br />
<p class="rrule">Repeat <span class="freq">yearly</span></p><br />
</div><br />
</nowiki></pre><br />
<br />
ISSUES:<br />
* We have a larger discusion about RRULE that needs to be resolved, hopefully these examples will help that. --RyanKing<br />
<br />
This hCalendar could be displayed as:<br />
<br />
<div class="vevent"><br />
<h1 class="summary">Our Blissful Anniversary</h1><br />
<p>Posted on: <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<p class="uid">19970901T130000Z-123403@host.com</p><br />
<p>Date: <abbr class="dtstart" title="19971102">November 2, 1997</abbr></p><br />
<p>This event is <span class="class">confidential</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">ANNIVERSARY</li><br />
<li class="category">PERSONAL</li><br />
<li class="category">SPECIAL OCCASSION</li><br />
</ul><br />
<p class="rrule">Repeat <span class="freq">yearly</span></p><br />
</div><br />
<br />
=== 5. iCalendar Object Examples ===<br />
<br />
The following example specifies a three-day conference that begins at 8:00 AM EDT, September 18, 1996 and end at 6:00 PM EDT, September 20, 1996.<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
DTSTAMP:19960704T120000Z<br />
UID:uid1@host.com<br />
ORGANIZER:MAILTO:jsmith@host.com<br />
DTSTART:19960918T143000Z<br />
DTEND:19960920T220000Z<br />
STATUS:CONFIRMED<br />
CATEGORIES:CONFERENCE <br />
SUMMARY:Networld+Interop Conference<br />
DESCRIPTION:Networld+Interop Conference and Exhibit\nAtlanta World Congress Center\nAtlant\, Georgia<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar fragment:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Networld+Interop Conference</h1><br />
<p class="description">Networld+Interop Conference and Exhibit Atlanta World Congress<br />
Center Atlanta, Georgia</p><br />
<p>Posted on: <abbr class="dtstamp" title="19960704T120000Z">July 4, 1996</abbr></p><br />
<p class="uid">uid1@host.com</p><br />
<p>Organized by: <a class="organizer" href="mailto:jsmith@host.com">jsmith@host.com</a></p><br />
<p>Dates: <abbr class="dtstart" title="19960918T143000Z">September 18, 1996, 14:30 UTC</abbr> -<br />
<abbr class="dtend" title="19960920T220000Z">September 20, 1996, 22:00 UTC</abbr></p><br />
<p>Status: <span class="status">CONFIRMED</span></p><br />
<p>Filed under:</p><br />
<ul class="categories"><br />
<li>CONFERENCE</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
<div class="vevent"><br />
<h1 class="summary">Networld+Interop Conference</h1><br />
<p class="description">Networld+Interop Conference and Exhibit Atlanta World Congress<br />
Center Atlanta, Georgia</p><br />
<p>Posted on: <abbr class="dtstamp" title="19960704T120000Z">July 4, 1996</abbr></p><br />
<p class="uid">uid1@host.com</p><br />
<p>Organized by: <a class="organizer" href="mailto:jsmith@host.com">jsmith@host.com</a></p><br />
<p>Dates: <abbr class="dtstart" title="19960918T143000Z">September 18, 1996, 14:30 UTC</abbr> -<br />
<abbr class="dtend" title="19960920T220000Z">September 20, 1996, 22:00 UTC</abbr></p><br />
<p>Status: <span class="status">CONFIRMED</span></p><br />
<p>Filed under:</p><br />
<ul class="categories"><br />
<li>CONFERENCE</li><br />
</ul><br />
</div><br />
<br />
==== Example 2 ====<br />
The following example specifies a group scheduled meeting that begin at 8:30 AM EST on March 12, 1998 and end at 9:30 AM EST on March 12, 1998. The "Organizer" has scheduled the meeting with one or more calendar users in a group. A time zone specification for Eastern United States has been specified.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
PRODID:-//RDU Software//NONSGML HandCal//EN<br />
VERSION:2.0<br />
BEGIN:VTIMEZONE<br />
TZID:US-Eastern<br />
BEGIN:STANDARD<br />
DTSTART:19981025T020000<br />
RDATE:19981025T020000<br />
TZOFFSETFROM:-0400<br />
TZOFFSETTO:-0500<br />
TZNAME:EST<br />
END:STANDARD<br />
BEGIN:DAYLIGHT<br />
DTSTART:19990404T020000<br />
RDATE:19990404T020000<br />
TZOFFSETFROM:-0500<br />
TZOFFSETTO:-0400<br />
TZNAME:EDT<br />
END:DAYLIGHT<br />
END:VTIMEZONE<br />
BEGIN:VEVENT<br />
DTSTAMP:19980309T231000Z<br />
UID:guid-1.host1.com<br />
ORGANIZER;ROLE=CHAIR:MAILTO:mrbig@host.com<br />
ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT;CUTYPE=GROUP:MAILTO:employee-A@host.com<br />
DESCRIPTION:Project XYZ Review Meeting<br />
CATEGORIES:MEETING<br />
CLASS:PUBLIC<br />
CREATED:19980309T130000Z<br />
SUMMARY:XYZ Project Review<br />
DTSTART;TZID=US-Eastern:19980312T083000<br />
DTEND;TZID=US-Eastern:19980312T093000<br />
LOCATION:1CP Conference Room 4350<br />
END:VEVENT<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 3 ====<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
METHOD:xyz<br />
VERSION:2.0<br />
PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
BEGIN:VEVENT<br />
DTSTAMP:19970324T1200Z<br />
SEQUENCE:0<br />
UID:uid3@host1.com<br />
ORGANIZER:MAILTO:jdoe@host1.com<br />
ATTENDEE;RSVP=TRUE:MAILTO:jsmith@host1.com<br />
DTSTART:19970324T123000Z<br />
DTEND:19970324T210000Z<br />
CATEGORIES:MEETING,PROJECT<br />
CLASS:PUBLIC<br />
SUMMARY:Calendaring Interoperability Planning Meeting<br />
DESCRIPTION:Discuss how we can test c&s interoperability\nusing iCalendar and other IETF standards.<br />
LOCATION:LDB Lobby<br />
ATTACH;FMTTYPE=application/postscript:ftp://xyzCorp.com/pub/conf/bkgrnd.ps<br />
END:VEVENT<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vcalendar"><br />
<p>Method: <span class="method">xyz</span></p><br />
<p>Version: <span class="version">2.0</span></p><br />
<p>PRODID: <span class="prodid">-//ABC Corporation//NONSGML My Product//EN</span></p><br />
<div class="vevent"><br />
<p>DTSTAMP: span class="dtstamp">19970324T1200Z</span></p><br />
<p>SEQUENCE: <span class="sequence">0</span></p><br />
<p>UID: <span class="uid">uid3@host1.com</span></p><br />
<p>ORGANIZER: <a class="organizer" href="mailto:jdoe@host1.com">jdoe@host1.com</a></p><br />
<p>ATTENDEE: <span class="attendee"><a class="value" href="mailto:jsmith@host1.com">jsmith@host1.com</a> RSVPed? <span class="rsvp">TRUE></span></p><br />
<p>START TIME: <abbr class="dtstart" tite="19970324T123000Z"></abbr></p><br />
<p>END TIME: <abbr class="dtend title="19970324T210000Z"></abbr></p><br />
<ul class="categories"><br />
<li>MEETING</li><br />
<li>PROJECT</li><br />
</ul><br />
<p>CLASS: <span class="class">PUBLIC</span></p><br />
<p class="summary">Calendaring Interoperability Planning Meeting</p><br />
<p class="description">Discuss how we can test c&s interoperability using iCalendar and other IETF standards.</p><br />
<p class="location">LDB Lobby</p><br />
<p>Attachment: <a class="attach" type="application/postscript" href="ftp://xyzCorp.com/pub/conf/bkgrnd.ps">ftp://xyzCorp.com/pub/conf/bkgrnd.ps</a></p><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 4 ====<br />
<br />
The following is an example of a to-do due on April 15, 1998. An audio alarm has been specified to remind the calendar user at noon, the day before the to-do is expected to be completed and repeat hourly, four additional times. The to-do definition has been modified twice since it was initially created.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
VERSION:2.0<br />
PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
BEGIN:VTODO<br />
DTSTAMP:19980130T134500Z<br />
SEQUENCE:2<br />
UID:uid4@host1.com<br />
ORGANIZER:MAILTO:unclesam@us.gov<br />
ATTENDEE;PARTSTAT=ACCEPTED:MAILTO:jqpublic@host.com<br />
DUE:19980415T235959<br />
STATUS:NEEDS-ACTION<br />
SUMMARY:Submit Income Taxes<br />
BEGIN:VALARM<br />
ACTION:AUDIO<br />
TRIGGER:19980403T120000<br />
ATTACH;FMTTYPE=audio/basic:http://host.com/pub/audio-files/ssbanner.aud<br />
REPEAT:4<br />
DURATION:PT1H<br />
END:VALARM<br />
END:VTODO<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vcalendar"><br />
<p>VERSION: <span class="version">2.0</span></p><br />
<p>PRODID: <span class="prodid">-//ABC Corporation//NONSGML My Product//EN</span></p><br />
<div class="vtodo"><br />
<p>DTSTAMP: <span class="dtstamp">19980130T134500Z</span></p><br />
<p>SEQUENCE: <span class="sequence">2</span></p><br />
<p>UID: <span class="uid">uid4@host1.com</span></p><br />
<p>ORGANIZER: <a class="organizer" href="mailto:unclesam@us.gov">unclesam@us.gov</a></p><br />
<p>ATTENDEE: <span class="attendee"><a class="value" href="mailto:jqpublic@host.com">jqpublic@host.com</a>, <span class="partstat">ACCEPTED</span></span></p><br />
<p>DUE: <abbr class="due" title="19980415T235959">April 15, 1998</abbr></p><br />
<p>STATUS: <span class="status">NEEDS-ACTION</span></p><br />
<p class="summary">Submit Income Taxes</p><br />
<div class="valarm"><br />
<p>ACTION: <span class="action">AUDIO</span></p><br />
<p>TRIGGER: <span class="trigger">19980403T120000</span></p><br />
<p>ATTACHMENT: <a class="attach" type="audio/basic" href="http://host.com/pub/audio-files/ssbanner.aud">http://host.com/pub/audio-files/ssbanner.aud</a></p><br />
<p>REPEAT: <span class="repeat">4</span></p><br />
<p>DURATION: <span class="duration">PT1H</span></p><br />
</div><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 5: journal entry ====<br />
The following is an example of a journal entry.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
VERSION:2.0<br />
PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
BEGIN:VJOURNAL<br />
DTSTAMP:19970324T120000Z<br />
UID:uid5@host1.com<br />
ORGANIZER:MAILTO:jsmith@host.com<br />
STATUS:DRAFT<br />
CLASS:PUBLIC<br />
CATEGORY:Project Report, XYZ, Weekly Meeting<br />
DESCRIPTION:Project xyz Review Meeting Minutes\nAgenda\n<br />
1. Review of project version 1.0 requirements.\n<br />
2. Definition of project processes.\n<br />
3. Review of project schedule.\nParticipants: John Smith, Jane Doe, Jim Dandy\n<br />
-It was decided that the requirements need to be signed off by product marketing.\n<br />
-Project processes were accepted.\n-Project schedule needs to account for scheduled <br />
holidays and employee vacation time. Check with HR for specific dates.\n<br />
-New schedule will be distributed by Friday.\n<br />
-Next weeks meeting is cancelled. No meeting until 3/23.<br />
END:VJOURNAL<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
(*note*: line-breaks have been added into the description, in reality it should be one line)<br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vcalendar"><br />
@TODO: VERSION:2.0<br />
@TODO: PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
<div class="vjournal"><br />
<p>Posted at: <abbr class="dtstamp" title="19970324T120000Z">March 24, 1997, 12:00 UTC</abbr></p><br />
<p class="uid">uid5@host1.com</p><br />
<p>Organizer: <a class="organizer"mailto:jsmith@host.com">jsmith@host.com</a><br />
<p>Status: <span class="status">DRAFT</span></p><br />
<p>This journal is<span class="class">PUBLIC</span></p><br />
<p>Filed under:</p><br />
<ul class="category"><br />
<li>Project Report<br />
<li>XYZ</li><br />
<li>Weekly Meeting</li><br />
</ul><br />
<p class="description">DESCRIPTION:Project xyz Review Meeting Minutes<br /><br />
Agenda<br /><br />
1. Review of project version 1.0 requirements.<br /><br />
2. Definition of project processes.<br /><br />
3. Review of project schedule.<br /><br />
Participants: John Smith, Jane Doe, Jim Dandy<br /><br />
-It was decided that the requirements need to be signed off by product marketing.<br /><br />
-Project processes were accepted.\n-Project schedule needs to account for scheduled <br />
holidays and employee vacation time. Check with HR for specific dates.<br /><br />
-New schedule will be distributed by Friday.<br /><br />
-Next weeks meeting is cancelled. No meeting until 3/23.<br />
<p><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 6. Free/Busy time ====<br />
<br />
The following is an example of published busy time information. The iCalendar object might be placed in the network resource www.host.com/calendar/busytime/jsmith.ifb.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
VERSION:2.0<br />
PRODID:-//RDU Software//NONSGML HandCal//EN<br />
BEGIN:VFREEBUSY<br />
ORGANIZER:MAILTO:jsmith@host.com<br />
DTSTART:19980313T141711Z<br />
DTEND:19980410T141711Z<br />
FREEBUSY:19980314T233000Z/19980315T003000Z<br />
FREEBUSY:19980316T153000Z/19980316T163000Z<br />
FREEBUSY:19980318T030000Z/19980318T040000Z<br />
URL:http://www.host.com/calendar/busytime/jsmith.ifb<br />
END:VFREEBUSY<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
== Other ==<br />
<br />
* See [[hcalendar-brainstorming]] for more examples (which may eventually be moved here) and analysis.</div>MarkPilgrimhttps://microformats.org/wiki/index.php?title=hcalendar-examples&diff=2037hcalendar-examples2005-10-11T16:47:22Z<p>MarkPilgrim: </p>
<hr />
<div>= hCalendar examples =<br />
<br />
Example [[hcalendar|hCalendars]].<br />
<br />
== Authors ==<br />
* [http://diveintomark.org/ Mark Pilgrim]<br />
* [http://theryanking.com/ Ryan King]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
<br />
== RFC 2445 examples in hCalendar ==<br />
<br />
These are 1:1 hCalendar examples for each example in [http://www.ietf.org/rfc/rfc2445.txt RFC 2445].<br />
<br />
Errata applied from [http://www.rfc-editor.org/cgi-bin/errata.pl#rfc2445 here].<br />
<br />
=== 4.6.1 Event Component ===<br />
<br />
The following is an example of the "VEVENT" calendar component used to represent a meeting that will also be opaque to searches for busy time:<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
UID:19970901T130000Z-123401@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19970903T163000Z<br />
DTEND:19970903T190000Z<br />
SUMMARY:Annual Employee Review<br />
CLASS:PRIVATE<br />
CATEGORIES:BUSINESS,HUMAN RESOURCES<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Annual Employee Review</h1><br />
<p>posted on <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<p>UID: <span class="uid">19970901T130000Z-123401@host.com</span></p><br />
<p>Dates: <abbr class="dtstart" title="19970903T163000Z">Septempter 3, 1997, 16:30</abbr> -<br />
<abbr class="dtend" title="19970903T190000Z">19:00 UTC</abbr></p><br />
<p>This meeting is <span class="class">PRIVATE</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
<h1 class="summary">Annual Employee Review</h1><br />
<p>posted on <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<p>UID: <span class="uid">19970901T130000Z-123401@host.com</span></p><br />
<p>Dates: <abbr class="dtstart" title="19970903T163000Z">Septempter 3, 1997, 16:30</abbr> - <abbr class="dtend" title="19970903T190000Z">19:00 UTC</abbr></p><br />
<p>This meeting is <span class="class">PRIVATE</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
<br />
==== Example 2 ====<br />
The following is an example of the "VEVENT" calendar component used to represent a reminder that will not be opaque, but rather transparent, to searches for busy time:<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
UID:19970901T130000Z-123402@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19970401T163000Z<br />
DTEND:19970402T010000Z<br />
SUMMARY:Laurel is in sensitivity awareness class.<br />
CLASS:PUBLIC<br />
CATEGORIES:BUSINESS,HUMAN RESOURCES<br />
TRANSP:TRANSPARENT<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar fragment:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Laurel is in sensitivity awareness class.</h1><br />
<p>Posted on: <abbr class="dtstamp" title=19970901T1300Z">September 1, 1997</abbr></p><br />
<p class="uid">19970901T130000Z-123402@host.com</p><br />
<p>Dates: <abbr class="dtstart" title="19970401T163000Z">April 1, 1997, 16:30 UTC</abbr>-<br />
<abbr class="dtend" title="19970402T010000Z">April 2, 1997 01:00 UTC</abbr></p><br />
<p>This event is <span class="class">public</span> and <span class="transp">transparent</span> to free/busy scheduling.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
<div class="vevent"><br />
<h1 class="summary">Laurel is in sensitivity awareness class.</h1><br />
<p>Posted on: <abbr class="dtstamp" title=19970901T1300Z">September 1, 1997</abbr></p><br />
<p class="uid">19970901T130000Z-123402@host.com</p><br />
<p>Dates: <abbr class="dtstart" title="19970401T163000Z">April 1, 1997, 16:30 UTC</abbr>-<br />
<abbr class="dtend" title="19970402T010000Z">April 2, 1997 01:00 UTC</abbr></p><br />
<p>This event is <span class="class">public</span> and <span class="transp">transparent</span> to free/busy scheduling.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
</div><br />
<br />
==== Example 3 ====<br />
<br />
The following is an example of the "VEVENT" calendar component used to represent an anniversary that will occur annually. Since it takes up no time, it will not appear as opaque in a search for busy time; no matter what the value of the "TRANSP" property indicates:<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
UID:19970901T130000Z-123403@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19971102<br />
SUMMARY:Our Blissful Anniversary<br />
CLASS:CONFIDENTIAL<br />
CATEGORIES:ANNIVERSARY,PERSONAL,SPECIAL OCCASION<br />
RRULE:FREQ=YEARLY<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar fragment:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Our Blissful Anniversary</h1><br />
<p>Posted on: <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<p class="uid">19970901T130000Z-123403@host.com</p><br />
<p>Date: <abbr class="dtstart" title="19971102">November 2, 1997</abbr></p><br />
<p>This event is <span class="class">confidential</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">ANNIVERSARY</li><br />
<li class="category">PERSONAL</li><br />
<li class="category">SPECIAL OCCASSION</li><br />
</ul><br />
<p class="rrule">Repeat <span class="freq">yearly</span></p><br />
</div><br />
</nowiki></pre><br />
<br />
ISSUES:<br />
* We have a larger discusion about RRULE that needs to be resolved, hopefully these examples will help that. --RyanKing<br />
<br />
This hCalendar could be displayed as:<br />
<br />
<div class="vevent"><br />
<h1 class="summary">Our Blissful Anniversary</h1><br />
<p>Posted on: <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<p class="uid">19970901T130000Z-123403@host.com</p><br />
<p>Date: <abbr class="dtstart" title="19971102">November 2, 1997</abbr></p><br />
<p>This event is <span class="class">confidential</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">ANNIVERSARY</li><br />
<li class="category">PERSONAL</li><br />
<li class="category">SPECIAL OCCASSION</li><br />
</ul><br />
<p class="rrule">Repeat <span class="freq">yearly</span></p><br />
</div><br />
<br />
=== 5. iCalendar Object Examples ===<br />
<br />
The following example specifies a three-day conference that begins at 8:00 AM EDT, September 18, 1996 and end at 6:00 PM EDT, September 20, 1996.<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
DTSTAMP:19960704T120000Z<br />
UID:uid1@host.com<br />
ORGANIZER:MAILTO:jsmith@host.com<br />
DTSTART:19960918T143000Z<br />
DTEND:19960920T220000Z<br />
STATUS:CONFIRMED<br />
CATEGORIES:CONFERENCE <br />
SUMMARY:Networld+Interop Conference<br />
DESCRIPTION:Networld+Interop Conference and Exhibit\nAtlanta World Congress Center\nAtlant\, Georgia<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar fragment:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Networld+Interop Conference</h1><br />
<p class="description">Networld+Interop Conference and Exhibit Atlanta World Congress<br />
Center Atlanta, Georgia</p><br />
<p>Posted on: <abbr class="dtstamp" title="19960704T120000Z">July 4, 1996</abbr></p><br />
<p class="uid">uid1@host.com</p><br />
<p>Orgainzed by: <a class="organizer" href="mailto:jsmith@host.com">jsmith@host.com</a></p><br />
<p>Dates: <abbr class="dtstart" title="19960918T143000Z">September 18, 1996, 14:30 UTC</abbr> -<br />
<abbr class="dtend" title="19960920T220000Z">September 20, 1996, 22:00 UTC</abbr></p><br />
<p>Status: <span class="status">CONFIRMED</span></p><br />
<p>Filed under:</p><br />
<ul class="categories"><br />
<li>CONFERENCE</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 2 ====<br />
The following example specifies a group scheduled meeting that begin at 8:30 AM EST on March 12, 1998 and end at 9:30 AM EST on March 12, 1998. The "Organizer" has scheduled the meeting with one or more calendar users in a group. A time zone specification for Eastern United States has been specified.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
PRODID:-//RDU Software//NONSGML HandCal//EN<br />
VERSION:2.0<br />
BEGIN:VTIMEZONE<br />
TZID:US-Eastern<br />
BEGIN:STANDARD<br />
DTSTART:19981025T020000<br />
RDATE:19981025T020000<br />
TZOFFSETFROM:-0400<br />
TZOFFSETTO:-0500<br />
TZNAME:EST<br />
END:STANDARD<br />
BEGIN:DAYLIGHT<br />
DTSTART:19990404T020000<br />
RDATE:19990404T020000<br />
TZOFFSETFROM:-0500<br />
TZOFFSETTO:-0400<br />
TZNAME:EDT<br />
END:DAYLIGHT<br />
END:VTIMEZONE<br />
BEGIN:VEVENT<br />
DTSTAMP:19980309T231000Z<br />
UID:guid-1.host1.com<br />
ORGANIZER;ROLE=CHAIR:MAILTO:mrbig@host.com<br />
ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT;CUTYPE=GROUP:MAILTO:employee-A@host.com<br />
DESCRIPTION:Project XYZ Review Meeting<br />
CATEGORIES:MEETING<br />
CLASS:PUBLIC<br />
CREATED:19980309T130000Z<br />
SUMMARY:XYZ Project Review<br />
DTSTART;TZID=US-Eastern:19980312T083000<br />
DTEND;TZID=US-Eastern:19980312T093000<br />
LOCATION:1CP Conference Room 4350<br />
END:VEVENT<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 3 ====<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
METHOD:xyz<br />
VERSION:2.0<br />
PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
BEGIN:VEVENT<br />
DTSTAMP:19970324T1200Z<br />
SEQUENCE:0<br />
UID:uid3@host1.com<br />
ORGANIZER:MAILTO:jdoe@host1.com<br />
ATTENDEE;RSVP=TRUE:MAILTO:jsmith@host1.com<br />
DTSTART:19970324T123000Z<br />
DTEND:19970324T210000Z<br />
CATEGORIES:MEETING,PROJECT<br />
CLASS:PUBLIC<br />
SUMMARY:Calendaring Interoperability Planning Meeting<br />
DESCRIPTION:Discuss how we can test c&s interoperability\nusing iCalendar and other IETF standards.<br />
LOCATION:LDB Lobby<br />
ATTACH;FMTTYPE=application/postscript:ftp://xyzCorp.com/pub/conf/bkgrnd.ps<br />
END:VEVENT<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vcalendar"><br />
<p>Method: <span class="method">xyz</span></p><br />
<p>Version: <span class="version">2.0</span></p><br />
<p>PRODID: <span class="prodid">-//ABC Corporation//NONSGML My Product//EN</span></p><br />
<div class="vevent"><br />
<p>DTSTAMP: span class="dtstamp">19970324T1200Z</span></p><br />
<p>SEQUENCE: <span class="sequence">0</span></p><br />
<p>UID: <span class="uid">uid3@host1.com</span></p><br />
<p>ORGANIZER: <a class="organizer" href="mailto:jdoe@host1.com">jdoe@host1.com</a></p><br />
<p>ATTENDEE: <span class="attendee"><a class="value" href="mailto:jsmith@host1.com">jsmith@host1.com</a> RSVPed? <span class="rsvp">TRUE></span></p><br />
<p>START TIME: <abbr class="dtstart" tite="19970324T123000Z"></abbr></p><br />
<p>END TIME: <abbr class="dtend title="19970324T210000Z"></abbr></p><br />
<ul class="categories"><br />
<li>MEETING</li><br />
<li>PROJECT</li><br />
</ul><br />
<p>CLASS: <span class="class">PUBLIC</span></p><br />
<p class="summary">Calendaring Interoperability Planning Meeting</p><br />
<p class="description">Discuss how we can test c&s interoperability using iCalendar and other IETF standards.</p><br />
<p class="location">LDB Lobby</p><br />
<p>Attachment: <a class="attach" type="application/postscript" href="ftp://xyzCorp.com/pub/conf/bkgrnd.ps">ftp://xyzCorp.com/pub/conf/bkgrnd.ps</a></p><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 4 ====<br />
<br />
The following is an example of a to-do due on April 15, 1998. An audio alarm has been specified to remind the calendar user at noon, the day before the to-do is expected to be completed and repeat hourly, four additional times. The to-do definition has been modified twice since it was initially created.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
VERSION:2.0<br />
PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
BEGIN:VTODO<br />
DTSTAMP:19980130T134500Z<br />
SEQUENCE:2<br />
UID:uid4@host1.com<br />
ORGANIZER:MAILTO:unclesam@us.gov<br />
ATTENDEE;PARTSTAT=ACCEPTED:MAILTO:jqpublic@host.com<br />
DUE:19980415T235959<br />
STATUS:NEEDS-ACTION<br />
SUMMARY:Submit Income Taxes<br />
BEGIN:VALARM<br />
ACTION:AUDIO<br />
TRIGGER:19980403T120000<br />
ATTACH;FMTTYPE=audio/basic:http://host.com/pub/audio-files/ssbanner.aud<br />
REPEAT:4<br />
DURATION:PT1H<br />
END:VALARM<br />
END:VTODO<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vcalendar"><br />
<p>VERSION: <span class="version">2.0</span></p><br />
<p>PRODID: <span class="prodid">-//ABC Corporation//NONSGML My Product//EN</span></p><br />
<div class="vtodo"><br />
<p>DTSTAMP: <span class="dtstamp">19980130T134500Z</span></p><br />
<p>SEQUENCE: <span class="sequence">2</span></p><br />
<p>UID: <span class="uid">uid4@host1.com</span></p><br />
<p>ORGANIZER: <a class="organizer" href="mailto:unclesam@us.gov">unclesam@us.gov</a></p><br />
<p>ATTENDEE: <span class="attendee"><a class="value" href="mailto:jqpublic@host.com">jqpublic@host.com</a>, <span class="partstat">ACCEPTED</span></span></p><br />
<p>DUE: <abbr class="due" title="19980415T235959">April 15, 1998</abbr></p><br />
<p>STATUS: <span class="status">NEEDS-ACTION</span></p><br />
<p class="summary">Submit Income Taxes</p><br />
<div class="valarm"><br />
<p>ACTION: <span class="action">AUDIO</span></p><br />
<p>TRIGGER: <span class="trigger">19980403T120000</span></p><br />
<p>ATTACHMENT: <a class="attach" type="audio/basic" href="http://host.com/pub/audio-files/ssbanner.aud">http://host.com/pub/audio-files/ssbanner.aud</a></p><br />
<p>REPEAT: <span class="repeat">4</span></p><br />
<p>DURATION: <span class="duration">PT1H</span></p><br />
</div><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 5: journal entry ====<br />
The following is an example of a journal entry.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
VERSION:2.0<br />
PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
BEGIN:VJOURNAL<br />
DTSTAMP:19970324T120000Z<br />
UID:uid5@host1.com<br />
ORGANIZER:MAILTO:jsmith@host.com<br />
STATUS:DRAFT<br />
CLASS:PUBLIC<br />
CATEGORY:Project Report, XYZ, Weekly Meeting<br />
DESCRIPTION:Project xyz Review Meeting Minutes\nAgenda\n<br />
1. Review of project version 1.0 requirements.\n<br />
2. Definition of project processes.\n<br />
3. Review of project schedule.\nParticipants: John Smith, Jane Doe, Jim Dandy\n<br />
-It was decided that the requirements need to be signed off by product marketing.\n<br />
-Project processes were accepted.\n-Project schedule needs to account for scheduled <br />
holidays and employee vacation time. Check with HR for specific dates.\n<br />
-New schedule will be distributed by Friday.\n<br />
-Next weeks meeting is cancelled. No meeting until 3/23.<br />
END:VJOURNAL<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
(*note*: line-breaks have been added into the description, in reality it should be one line)<br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vcalendar"><br />
@TODO: VERSION:2.0<br />
@TODO: PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
<div class="vjournal"><br />
<p>Posted at: <abbr class="dtstamp" title="19970324T120000Z">March 24, 1997, 12:00 UTC</abbr></p><br />
<p class="uid">uid5@host1.com</p><br />
<p>Organizer: <a class="organizer"mailto:jsmith@host.com">jsmith@host.com</a><br />
<p>Status: <span class="status">DRAFT</span></p><br />
<p>This journal is<span class="class">PUBLIC</span></p><br />
<p>Filed under:</p><br />
<ul class="category"><br />
<li>Project Report<br />
<li>XYZ</li><br />
<li>Weekly Meeting</li><br />
</ul><br />
<p class="description">DESCRIPTION:Project xyz Review Meeting Minutes<br /><br />
Agenda<br /><br />
1. Review of project version 1.0 requirements.<br /><br />
2. Definition of project processes.<br /><br />
3. Review of project schedule.<br /><br />
Participants: John Smith, Jane Doe, Jim Dandy<br /><br />
-It was decided that the requirements need to be signed off by product marketing.<br /><br />
-Project processes were accepted.\n-Project schedule needs to account for scheduled <br />
holidays and employee vacation time. Check with HR for specific dates.<br /><br />
-New schedule will be distributed by Friday.<br /><br />
-Next weeks meeting is cancelled. No meeting until 3/23.<br />
<p><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 6. Free/Busy time ====<br />
<br />
The following is an example of published busy time information. The iCalendar object might be placed in the network resource www.host.com/calendar/busytime/jsmith.ifb.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
VERSION:2.0<br />
PRODID:-//RDU Software//NONSGML HandCal//EN<br />
BEGIN:VFREEBUSY<br />
ORGANIZER:MAILTO:jsmith@host.com<br />
DTSTART:19980313T141711Z<br />
DTEND:19980410T141711Z<br />
FREEBUSY:19980314T233000Z/19980315T003000Z<br />
FREEBUSY:19980316T153000Z/19980316T163000Z<br />
FREEBUSY:19980318T030000Z/19980318T040000Z<br />
URL:http://www.host.com/calendar/busytime/jsmith.ifb<br />
END:VFREEBUSY<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
== Other ==<br />
<br />
* See [[hcalendar-brainstorming]] for more examples (which may eventually be moved here) and analysis.</div>MarkPilgrimhttps://microformats.org/wiki/index.php?title=hcalendar-examples&diff=2036hcalendar-examples2005-10-11T16:46:15Z<p>MarkPilgrim: </p>
<hr />
<div>= hCalendar examples =<br />
<br />
Example [[hcalendar|hCalendars]].<br />
<br />
== Authors ==<br />
* [http://diveintomark.org/ Mark Pilgrim]<br />
* [http://theryanking.com/ Ryan King]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
<br />
== RFC 2445 examples in hCalendar ==<br />
<br />
These are 1:1 hCalendar examples for each example in [http://www.ietf.org/rfc/rfc2445.txt RFC 2445].<br />
<br />
Errata applied from [http://www.rfc-editor.org/cgi-bin/errata.pl#rfc2445 here].<br />
<br />
=== 4.6.1 Event Component ===<br />
<br />
The following is an example of the "VEVENT" calendar component used to represent a meeting that will also be opaque to searches for busy time:<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
UID:19970901T130000Z-123401@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19970903T163000Z<br />
DTEND:19970903T190000Z<br />
SUMMARY:Annual Employee Review<br />
CLASS:PRIVATE<br />
CATEGORIES:BUSINESS,HUMAN RESOURCES<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Annual Employee Review</h1><br />
<p>posted on <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<p>UID: <span class="uid">19970901T130000Z-123401@host.com</span></p><br />
<p>Dates: <abbr class="dtstart" title="19970903T163000Z">Septempter 3, 1997, 16:30</abbr> -<br />
<abbr class="dtend" title="19970903T190000Z">19:00 UTC</abbr></p><br />
<p>This meeting is <span class="class">PRIVATE</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
<h1 class="summary">Annual Employee Review</h1><br />
<p>posted on <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<p>UID: <span class="uid">19970901T130000Z-123401@host.com</span></p><br />
<p>Dates: <abbr class="dtstart" title="19970903T163000Z">Septempter 3, 1997, 16:30</abbr> - <abbr class="dtend" title="19970903T190000Z">19:00 UTC</abbr></p><br />
<p>This meeting is <span class="class">PRIVATE</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
<br />
==== Example 2 ====<br />
The following is an example of the "VEVENT" calendar component used to represent a reminder that will not be opaque, but rather transparent, to searches for busy time:<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
UID:19970901T130000Z-123402@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19970401T163000Z<br />
DTEND:19970402T010000Z<br />
SUMMARY:Laurel is in sensitivity awareness class.<br />
CLASS:PUBLIC<br />
CATEGORIES:BUSINESS,HUMAN RESOURCES<br />
TRANSP:TRANSPARENT<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar fragment:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Laurel is in sensitivity awareness class.</h1><br />
<p>Posted on: <abbr class="dtstamp" title=19970901T1300Z">September 1, 1997</abbr></p><br />
<p class="uid">19970901T130000Z-123402@host.com</p><br />
<p>Dates: <abbr class="dtstart" title="19970401T163000Z">April 1, 1997, 16:30 UTC</abbr>-<br />
<abbr class="dtend" title="19970402T010000Z">April 2, 1997 01:00 UTC</abbr></p><br />
<p>This event is <span class="class">public</span> and <span class="transp">transparent</span> to free/busy scheduling.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
<div class="vevent"><br />
<h1 class="summary">Laurel is in sensitivity awareness class.</h1><br />
<p>Posted on: <abbr class="dtstamp" title=19970901T1300Z">September 1, 1997</abbr></p><br />
<p class="uid">19970901T130000Z-123402@host.com</p><br />
<p>Dates: <abbr class="dtstart" title="19970401T163000Z">April 1, 1997, 16:30 UTC</abbr>-<br />
<abbr class="dtend" title="19970402T010000Z">April 2, 1997 01:00 UTC</abbr></p><br />
<p>This event is <span class="class">public</span> and <span class="transp">transparent</span> to free/busy scheduling.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
</div><br />
<br />
==== Example 3 ====<br />
<br />
The following is an example of the "VEVENT" calendar component used to represent an anniversary that will occur annually. Since it takes up no time, it will not appear as opaque in a search for busy time; no matter what the value of the "TRANSP" property indicates:<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
UID:19970901T130000Z-123403@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19971102<br />
SUMMARY:Our Blissful Anniversary<br />
CLASS:CONFIDENTIAL<br />
CATEGORIES:ANNIVERSARY,PERSONAL,SPECIAL OCCASION<br />
RRULE:FREQ=YEARLY<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar fragment:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Our Blissful Anniversary</h1><br />
<p>Posted on: <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<span class="uid">19970901T130000Z-123403@host.com</span><br />
<p>Date: <abbr class="dtstart" title="19971102">November 2, 1997</abbr></p><br />
<p>This event is <span class="class">confidential</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">ANNIVERSARY</li><br />
<li class="category">PERSONAL</li><br />
<li class="category">SPECIAL OCCASSION</li><br />
</ul><br />
<p class="rrule">Repeat <span class="freq">yearly</span></p><br />
</div><br />
</nowiki></pre><br />
<br />
ISSUES:<br />
* We have a larger discusion about RRULE that needs to be resolved, hopefully these examples will help that. --RyanKing<br />
<br />
This hCalendar could be displayed as:<br />
<br />
<div class="vevent"><br />
<h1 class="summary">Our Blissful Anniversary</h1><br />
<p>Posted on: <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<span class="uid">19970901T130000Z-123403@host.com</span><br />
<p>Date: <abbr class="dtstart" title="19971102">November 2, 1997</abbr></p><br />
<p>This event is <span class="class">confidential</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">ANNIVERSARY</li><br />
<li class="category">PERSONAL</li><br />
<li class="category">SPECIAL OCCASSION</li><br />
</ul><br />
<p class="rrule">Repeat <span class="freq">yearly</span></p><br />
</div><br />
<br />
=== 5. iCalendar Object Examples ===<br />
<br />
The following example specifies a three-day conference that begins at 8:00 AM EDT, September 18, 1996 and end at 6:00 PM EDT, September 20, 1996.<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
DTSTAMP:19960704T120000Z<br />
UID:uid1@host.com<br />
ORGANIZER:MAILTO:jsmith@host.com<br />
DTSTART:19960918T143000Z<br />
DTEND:19960920T220000Z<br />
STATUS:CONFIRMED<br />
CATEGORIES:CONFERENCE <br />
SUMMARY:Networld+Interop Conference<br />
DESCRIPTION:Networld+Interop Conference and Exhibit\nAtlanta World Congress Center\nAtlant\, Georgia<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar fragment:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Networld+Interop Conference</h1><br />
<p class="description">Networld+Interop Conference and Exhibit Atlanta World Congress<br />
Center Atlanta, Georgia</p><br />
<p>Posted on: <abbr class="dtstamp" title="19960704T120000Z">July 4, 1996</abbr></p><br />
<p class="uid">uid1@host.com</p><br />
<p>Orgainzed by: <a class="organizer" href="mailto:jsmith@host.com">jsmith@host.com</a></p><br />
<p>Dates: <abbr class="dtstart" title="19960918T143000Z">September 18, 1996, 14:30 UTC</abbr> -<br />
<abbr class="dtend" title="19960920T220000Z">September 20, 1996, 22:00 UTC</abbr></p><br />
<p>Status: <span class="status">CONFIRMED</span></p><br />
<p>Filed under:</p><br />
<ul class="categories"><br />
<li>CONFERENCE</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 2 ====<br />
The following example specifies a group scheduled meeting that begin at 8:30 AM EST on March 12, 1998 and end at 9:30 AM EST on March 12, 1998. The "Organizer" has scheduled the meeting with one or more calendar users in a group. A time zone specification for Eastern United States has been specified.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
PRODID:-//RDU Software//NONSGML HandCal//EN<br />
VERSION:2.0<br />
BEGIN:VTIMEZONE<br />
TZID:US-Eastern<br />
BEGIN:STANDARD<br />
DTSTART:19981025T020000<br />
RDATE:19981025T020000<br />
TZOFFSETFROM:-0400<br />
TZOFFSETTO:-0500<br />
TZNAME:EST<br />
END:STANDARD<br />
BEGIN:DAYLIGHT<br />
DTSTART:19990404T020000<br />
RDATE:19990404T020000<br />
TZOFFSETFROM:-0500<br />
TZOFFSETTO:-0400<br />
TZNAME:EDT<br />
END:DAYLIGHT<br />
END:VTIMEZONE<br />
BEGIN:VEVENT<br />
DTSTAMP:19980309T231000Z<br />
UID:guid-1.host1.com<br />
ORGANIZER;ROLE=CHAIR:MAILTO:mrbig@host.com<br />
ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT;CUTYPE=GROUP:MAILTO:employee-A@host.com<br />
DESCRIPTION:Project XYZ Review Meeting<br />
CATEGORIES:MEETING<br />
CLASS:PUBLIC<br />
CREATED:19980309T130000Z<br />
SUMMARY:XYZ Project Review<br />
DTSTART;TZID=US-Eastern:19980312T083000<br />
DTEND;TZID=US-Eastern:19980312T093000<br />
LOCATION:1CP Conference Room 4350<br />
END:VEVENT<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 3 ====<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
METHOD:xyz<br />
VERSION:2.0<br />
PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
BEGIN:VEVENT<br />
DTSTAMP:19970324T1200Z<br />
SEQUENCE:0<br />
UID:uid3@host1.com<br />
ORGANIZER:MAILTO:jdoe@host1.com<br />
ATTENDEE;RSVP=TRUE:MAILTO:jsmith@host1.com<br />
DTSTART:19970324T123000Z<br />
DTEND:19970324T210000Z<br />
CATEGORIES:MEETING,PROJECT<br />
CLASS:PUBLIC<br />
SUMMARY:Calendaring Interoperability Planning Meeting<br />
DESCRIPTION:Discuss how we can test c&s interoperability\nusing iCalendar and other IETF standards.<br />
LOCATION:LDB Lobby<br />
ATTACH;FMTTYPE=application/postscript:ftp://xyzCorp.com/pub/conf/bkgrnd.ps<br />
END:VEVENT<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vcalendar"><br />
<p>Method: <span class="method">xyz</span></p><br />
<p>Version: <span class="version">2.0</span></p><br />
<p>PRODID: <span class="prodid">-//ABC Corporation//NONSGML My Product//EN</span></p><br />
<div class="vevent"><br />
<p>DTSTAMP: span class="dtstamp">19970324T1200Z</span></p><br />
<p>SEQUENCE: <span class="sequence">0</span></p><br />
<p>UID: <span class="uid">uid3@host1.com</span></p><br />
<p>ORGANIZER: <a class="organizer" href="mailto:jdoe@host1.com">jdoe@host1.com</a></p><br />
<p>ATTENDEE: <span class="attendee"><a class="value" href="mailto:jsmith@host1.com">jsmith@host1.com</a> RSVPed? <span class="rsvp">TRUE></span></p><br />
<p>START TIME: <abbr class="dtstart" tite="19970324T123000Z"></abbr></p><br />
<p>END TIME: <abbr class="dtend title="19970324T210000Z"></abbr></p><br />
<ul class="categories"><br />
<li>MEETING</li><br />
<li>PROJECT</li><br />
</ul><br />
<p>CLASS: <span class="class">PUBLIC</span></p><br />
<p class="summary">Calendaring Interoperability Planning Meeting</p><br />
<p class="description">Discuss how we can test c&s interoperability using iCalendar and other IETF standards.</p><br />
<p class="location">LDB Lobby</p><br />
<p>Attachment: <a class="attach" type="application/postscript" href="ftp://xyzCorp.com/pub/conf/bkgrnd.ps">ftp://xyzCorp.com/pub/conf/bkgrnd.ps</a></p><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 4 ====<br />
<br />
The following is an example of a to-do due on April 15, 1998. An audio alarm has been specified to remind the calendar user at noon, the day before the to-do is expected to be completed and repeat hourly, four additional times. The to-do definition has been modified twice since it was initially created.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
VERSION:2.0<br />
PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
BEGIN:VTODO<br />
DTSTAMP:19980130T134500Z<br />
SEQUENCE:2<br />
UID:uid4@host1.com<br />
ORGANIZER:MAILTO:unclesam@us.gov<br />
ATTENDEE;PARTSTAT=ACCEPTED:MAILTO:jqpublic@host.com<br />
DUE:19980415T235959<br />
STATUS:NEEDS-ACTION<br />
SUMMARY:Submit Income Taxes<br />
BEGIN:VALARM<br />
ACTION:AUDIO<br />
TRIGGER:19980403T120000<br />
ATTACH;FMTTYPE=audio/basic:http://host.com/pub/audio-files/ssbanner.aud<br />
REPEAT:4<br />
DURATION:PT1H<br />
END:VALARM<br />
END:VTODO<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vcalendar"><br />
<p>VERSION: <span class="version">2.0</span></p><br />
<p>PRODID: <span class="prodid">-//ABC Corporation//NONSGML My Product//EN</span></p><br />
<div class="vtodo"><br />
<p>DTSTAMP: <span class="dtstamp">19980130T134500Z</span></p><br />
<p>SEQUENCE: <span class="sequence">2</span></p><br />
<p>UID: <span class="uid">uid4@host1.com</span></p><br />
<p>ORGANIZER: <a class="organizer" href="mailto:unclesam@us.gov">unclesam@us.gov</a></p><br />
<p>ATTENDEE: <span class="attendee"><a class="value" href="mailto:jqpublic@host.com">jqpublic@host.com</a>, <span class="partstat">ACCEPTED</span></span></p><br />
<p>DUE: <abbr class="due" title="19980415T235959">April 15, 1998</abbr></p><br />
<p>STATUS: <span class="status">NEEDS-ACTION</span></p><br />
<p class="summary">Submit Income Taxes</p><br />
<div class="valarm"><br />
<p>ACTION: <span class="action">AUDIO</span></p><br />
<p>TRIGGER: <span class="trigger">19980403T120000</span></p><br />
<p>ATTACHMENT: <a class="attach" type="audio/basic" href="http://host.com/pub/audio-files/ssbanner.aud">http://host.com/pub/audio-files/ssbanner.aud</a></p><br />
<p>REPEAT: <span class="repeat">4</span></p><br />
<p>DURATION: <span class="duration">PT1H</span></p><br />
</div><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 5: journal entry ====<br />
The following is an example of a journal entry.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
VERSION:2.0<br />
PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
BEGIN:VJOURNAL<br />
DTSTAMP:19970324T120000Z<br />
UID:uid5@host1.com<br />
ORGANIZER:MAILTO:jsmith@host.com<br />
STATUS:DRAFT<br />
CLASS:PUBLIC<br />
CATEGORY:Project Report, XYZ, Weekly Meeting<br />
DESCRIPTION:Project xyz Review Meeting Minutes\nAgenda\n<br />
1. Review of project version 1.0 requirements.\n<br />
2. Definition of project processes.\n<br />
3. Review of project schedule.\nParticipants: John Smith, Jane Doe, Jim Dandy\n<br />
-It was decided that the requirements need to be signed off by product marketing.\n<br />
-Project processes were accepted.\n-Project schedule needs to account for scheduled <br />
holidays and employee vacation time. Check with HR for specific dates.\n<br />
-New schedule will be distributed by Friday.\n<br />
-Next weeks meeting is cancelled. No meeting until 3/23.<br />
END:VJOURNAL<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
(*note*: line-breaks have been added into the description, in reality it should be one line)<br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vcalendar"><br />
@TODO: VERSION:2.0<br />
@TODO: PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
<div class="vjournal"><br />
<p>Posted at: <abbr class="dtstamp" title="19970324T120000Z">March 24, 1997, 12:00 UTC</abbr></p><br />
<p class="uid">uid5@host1.com</p><br />
<p>Organizer: <a class="organizer"mailto:jsmith@host.com">jsmith@host.com</a><br />
<p>Status: <span class="status">DRAFT</span></p><br />
<p>This journal is<span class="class">PUBLIC</span></p><br />
<p>Filed under:</p><br />
<ul class="category"><br />
<li>Project Report<br />
<li>XYZ</li><br />
<li>Weekly Meeting</li><br />
</ul><br />
<p class="description">DESCRIPTION:Project xyz Review Meeting Minutes<br /><br />
Agenda<br /><br />
1. Review of project version 1.0 requirements.<br /><br />
2. Definition of project processes.<br /><br />
3. Review of project schedule.<br /><br />
Participants: John Smith, Jane Doe, Jim Dandy<br /><br />
-It was decided that the requirements need to be signed off by product marketing.<br /><br />
-Project processes were accepted.\n-Project schedule needs to account for scheduled <br />
holidays and employee vacation time. Check with HR for specific dates.<br /><br />
-New schedule will be distributed by Friday.<br /><br />
-Next weeks meeting is cancelled. No meeting until 3/23.<br />
<p><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 6. Free/Busy time ====<br />
<br />
The following is an example of published busy time information. The iCalendar object might be placed in the network resource www.host.com/calendar/busytime/jsmith.ifb.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
VERSION:2.0<br />
PRODID:-//RDU Software//NONSGML HandCal//EN<br />
BEGIN:VFREEBUSY<br />
ORGANIZER:MAILTO:jsmith@host.com<br />
DTSTART:19980313T141711Z<br />
DTEND:19980410T141711Z<br />
FREEBUSY:19980314T233000Z/19980315T003000Z<br />
FREEBUSY:19980316T153000Z/19980316T163000Z<br />
FREEBUSY:19980318T030000Z/19980318T040000Z<br />
URL:http://www.host.com/calendar/busytime/jsmith.ifb<br />
END:VFREEBUSY<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
== Other ==<br />
<br />
* See [[hcalendar-brainstorming]] for more examples (which may eventually be moved here) and analysis.</div>MarkPilgrimhttps://microformats.org/wiki/index.php?title=hcalendar-examples&diff=2035hcalendar-examples2005-10-11T16:45:40Z<p>MarkPilgrim: </p>
<hr />
<div>= hCalendar examples =<br />
<br />
Example [[hcalendar|hCalendars]].<br />
<br />
== Authors ==<br />
* [http://diveintomark.org/ Mark Pilgrim]<br />
* [http://theryanking.com/ Ryan King]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
<br />
== RFC 2445 examples in hCalendar ==<br />
<br />
These are 1:1 hCalendar examples for each example in [http://www.ietf.org/rfc/rfc2445.txt RFC 2445].<br />
<br />
Errata applied from [http://www.rfc-editor.org/cgi-bin/errata.pl#rfc2445 here].<br />
<br />
=== 4.6.1 Event Component ===<br />
<br />
The following is an example of the "VEVENT" calendar component used to represent a meeting that will also be opaque to searches for busy time:<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
UID:19970901T130000Z-123401@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19970903T163000Z<br />
DTEND:19970903T190000Z<br />
SUMMARY:Annual Employee Review<br />
CLASS:PRIVATE<br />
CATEGORIES:BUSINESS,HUMAN RESOURCES<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Annual Employee Review</h1><br />
<p>posted on <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<p>UID: <span class="uid">19970901T130000Z-123401@host.com</span></p><br />
<p>Dates: <abbr class="dtstart" title="19970903T163000Z">Septempter 3, 1997, 16:30</abbr> -<br />
<abbr class="dtend" title="19970903T190000Z">19:00 UTC</abbr></p><br />
<p>This meeting is <span class="class">PRIVATE</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
<h1 class="summary">Annual Employee Review</h1><br />
<p>posted on <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<p>UID: <span class="uid">19970901T130000Z-123401@host.com</span></p><br />
<p>Dates: <abbr class="dtstart" title="19970903T163000Z">Septempter 3, 1997, 16:30</abbr> - <abbr class="dtend" title="19970903T190000Z">19:00 UTC</abbr></p><br />
<p>This meeting is <span class="class">PRIVATE</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
<br />
==== Example 2 ====<br />
The following is an example of the "VEVENT" calendar component used to represent a reminder that will not be opaque, but rather transparent, to searches for busy time:<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
UID:19970901T130000Z-123402@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19970401T163000Z<br />
DTEND:19970402T010000Z<br />
SUMMARY:Laurel is in sensitivity awareness class.<br />
CLASS:PUBLIC<br />
CATEGORIES:BUSINESS,HUMAN RESOURCES<br />
TRANSP:TRANSPARENT<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar fragment:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Laurel is in sensitivity awareness class.</h1><br />
<p>Posted on: <abbr class="dtstamp" title=19970901T1300Z">September 1, 1997</abbr></p><br />
<p class="uid">19970901T130000Z-123402@host.com</p><br />
<p>Dates: <abbr class="dtstart" title="19970401T163000Z">April 1, 1997, 16:30 UTC</abbr>-<br />
<abbr class="dtend" title="19970402T010000Z">April 2, 1997 01:00 UTC</abbr></p><br />
<p>This event is <span class="class">public</span> and <span class="transp">transparent</span> to free/busy scheduling.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
<div class="vevent"><br />
<h1 class="summary">Laurel is in sensitivity awareness class.</h1><br />
<p>Posted on: <abbr class="dtstamp" title=19970901T1300Z">September 1, 1997</abbr></p><br />
<p class="uid">19970901T130000Z-123402@host.com</p><br />
<p>Dates: <abbr class="dtstart" title="19970401T163000Z">April 1, 1997, 16:30 UTC</abbr>-<br />
<abbr class="dtend" title="19970402T010000Z">April 2, 1997 01:00 UTC</abbr></p><br />
<p>This event is <span class="class">public</span> and <span class="transp">transparent</span> to free/busy scheduling.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
</div><br />
<br />
==== Example 3 ====<br />
<br />
The following is an example of the "VEVENT" calendar component used to represent an anniversary that will occur annually. Since it takes up no time, it will not appear as opaque in a search for busy time; no matter what the value of the "TRANSP" property indicates:<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
UID:19970901T130000Z-123403@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19971102<br />
SUMMARY:Our Blissful Anniversary<br />
CLASS:CONFIDENTIAL<br />
CATEGORIES:ANNIVERSARY,PERSONAL,SPECIAL OCCASION<br />
RRULE:FREQ=YEARLY<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar fragment:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Our Blissful Anniversary</h1><br />
<p>Posted on: <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<span class="uid">19970901T130000Z-123403@host.com</span><br />
<p>Date: <abbr class="dtstart" title="19971102">November 2, 1997</abbr></p><br />
<p>This event is <span class="class">confidential</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">ANNIVERSARY</li><br />
<li class="category">PERSONAL</li><br />
<li class="category">SPECIAL OCCASSION</li><br />
</ul><br />
<p class="rrule">Repeat <span class="freq">yearly</span></p><br />
</div><br />
</nowiki></pre><br />
<br />
ISSUES:<br />
* We have a larger discusion about RRULE that needs to be resolved, hopefully these examples will help that. --RyanKing<br />
<br />
This hCalendar could be displayed as:<br />
<br />
<div class="vevent"><br />
<h1 class="summary">Our Blissful Anniversary</h1><br />
<p>Posted on: <span class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<span class="uid">19970901T130000Z-123403@host.com</span><br />
<p>Date: <abbr class="dtstart" title="19971102">November 2, 1997</abbr></p><br />
<p>This event is <span class="class">confidential</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">ANNIVERSARY</li><br />
<li class="category">PERSONAL</li><br />
<li class="category">SPECIAL OCCASSION</li><br />
</ul><br />
<p class="rrule">Repeat <span class="freq">yearly</span></p><br />
</div><br />
<br />
=== 5. iCalendar Object Examples ===<br />
<br />
The following example specifies a three-day conference that begins at 8:00 AM EDT, September 18, 1996 and end at 6:00 PM EDT, September 20, 1996.<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
DTSTAMP:19960704T120000Z<br />
UID:uid1@host.com<br />
ORGANIZER:MAILTO:jsmith@host.com<br />
DTSTART:19960918T143000Z<br />
DTEND:19960920T220000Z<br />
STATUS:CONFIRMED<br />
CATEGORIES:CONFERENCE <br />
SUMMARY:Networld+Interop Conference<br />
DESCRIPTION:Networld+Interop Conference and Exhibit\nAtlanta World Congress Center\nAtlant\, Georgia<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar fragment:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Networld+Interop Conference</h1><br />
<p class="description">Networld+Interop Conference and Exhibit Atlanta World Congress<br />
Center Atlanta, Georgia</p><br />
<p>Posted on: <abbr class="dtstamp" title="19960704T120000Z">July 4, 1996</abbr></p><br />
<p class="uid">uid1@host.com</p><br />
<p>Orgainzed by: <a class="organizer" href="mailto:jsmith@host.com">jsmith@host.com</a></p><br />
<p>Dates: <abbr class="dtstart" title="19960918T143000Z">September 18, 1996, 14:30 UTC</abbr> -<br />
<abbr class="dtend" title="19960920T220000Z">September 20, 1996, 22:00 UTC</abbr></p><br />
<p>Status: <span class="status">CONFIRMED</span></p><br />
<p>Filed under:</p><br />
<ul class="categories"><br />
<li>CONFERENCE</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 2 ====<br />
The following example specifies a group scheduled meeting that begin at 8:30 AM EST on March 12, 1998 and end at 9:30 AM EST on March 12, 1998. The "Organizer" has scheduled the meeting with one or more calendar users in a group. A time zone specification for Eastern United States has been specified.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
PRODID:-//RDU Software//NONSGML HandCal//EN<br />
VERSION:2.0<br />
BEGIN:VTIMEZONE<br />
TZID:US-Eastern<br />
BEGIN:STANDARD<br />
DTSTART:19981025T020000<br />
RDATE:19981025T020000<br />
TZOFFSETFROM:-0400<br />
TZOFFSETTO:-0500<br />
TZNAME:EST<br />
END:STANDARD<br />
BEGIN:DAYLIGHT<br />
DTSTART:19990404T020000<br />
RDATE:19990404T020000<br />
TZOFFSETFROM:-0500<br />
TZOFFSETTO:-0400<br />
TZNAME:EDT<br />
END:DAYLIGHT<br />
END:VTIMEZONE<br />
BEGIN:VEVENT<br />
DTSTAMP:19980309T231000Z<br />
UID:guid-1.host1.com<br />
ORGANIZER;ROLE=CHAIR:MAILTO:mrbig@host.com<br />
ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT;CUTYPE=GROUP:MAILTO:employee-A@host.com<br />
DESCRIPTION:Project XYZ Review Meeting<br />
CATEGORIES:MEETING<br />
CLASS:PUBLIC<br />
CREATED:19980309T130000Z<br />
SUMMARY:XYZ Project Review<br />
DTSTART;TZID=US-Eastern:19980312T083000<br />
DTEND;TZID=US-Eastern:19980312T093000<br />
LOCATION:1CP Conference Room 4350<br />
END:VEVENT<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 3 ====<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
METHOD:xyz<br />
VERSION:2.0<br />
PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
BEGIN:VEVENT<br />
DTSTAMP:19970324T1200Z<br />
SEQUENCE:0<br />
UID:uid3@host1.com<br />
ORGANIZER:MAILTO:jdoe@host1.com<br />
ATTENDEE;RSVP=TRUE:MAILTO:jsmith@host1.com<br />
DTSTART:19970324T123000Z<br />
DTEND:19970324T210000Z<br />
CATEGORIES:MEETING,PROJECT<br />
CLASS:PUBLIC<br />
SUMMARY:Calendaring Interoperability Planning Meeting<br />
DESCRIPTION:Discuss how we can test c&s interoperability\nusing iCalendar and other IETF standards.<br />
LOCATION:LDB Lobby<br />
ATTACH;FMTTYPE=application/postscript:ftp://xyzCorp.com/pub/conf/bkgrnd.ps<br />
END:VEVENT<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vcalendar"><br />
<p>Method: <span class="method">xyz</span></p><br />
<p>Version: <span class="version">2.0</span></p><br />
<p>PRODID: <span class="prodid">-//ABC Corporation//NONSGML My Product//EN</span></p><br />
<div class="vevent"><br />
<p>DTSTAMP: span class="dtstamp">19970324T1200Z</span></p><br />
<p>SEQUENCE: <span class="sequence">0</span></p><br />
<p>UID: <span class="uid">uid3@host1.com</span></p><br />
<p>ORGANIZER: <a class="organizer" href="mailto:jdoe@host1.com">jdoe@host1.com</a></p><br />
<p>ATTENDEE: <span class="attendee"><a class="value" href="mailto:jsmith@host1.com">jsmith@host1.com</a> RSVPed? <span class="rsvp">TRUE></span></p><br />
<p>START TIME: <abbr class="dtstart" tite="19970324T123000Z"></abbr></p><br />
<p>END TIME: <abbr class="dtend title="19970324T210000Z"></abbr></p><br />
<ul class="categories"><br />
<li>MEETING</li><br />
<li>PROJECT</li><br />
</ul><br />
<p>CLASS: <span class="class">PUBLIC</span></p><br />
<p class="summary">Calendaring Interoperability Planning Meeting</p><br />
<p class="description">Discuss how we can test c&s interoperability using iCalendar and other IETF standards.</p><br />
<p class="location">LDB Lobby</p><br />
<p>Attachment: <a class="attach" type="application/postscript" href="ftp://xyzCorp.com/pub/conf/bkgrnd.ps">ftp://xyzCorp.com/pub/conf/bkgrnd.ps</a></p><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 4 ====<br />
<br />
The following is an example of a to-do due on April 15, 1998. An audio alarm has been specified to remind the calendar user at noon, the day before the to-do is expected to be completed and repeat hourly, four additional times. The to-do definition has been modified twice since it was initially created.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
VERSION:2.0<br />
PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
BEGIN:VTODO<br />
DTSTAMP:19980130T134500Z<br />
SEQUENCE:2<br />
UID:uid4@host1.com<br />
ORGANIZER:MAILTO:unclesam@us.gov<br />
ATTENDEE;PARTSTAT=ACCEPTED:MAILTO:jqpublic@host.com<br />
DUE:19980415T235959<br />
STATUS:NEEDS-ACTION<br />
SUMMARY:Submit Income Taxes<br />
BEGIN:VALARM<br />
ACTION:AUDIO<br />
TRIGGER:19980403T120000<br />
ATTACH;FMTTYPE=audio/basic:http://host.com/pub/audio-files/ssbanner.aud<br />
REPEAT:4<br />
DURATION:PT1H<br />
END:VALARM<br />
END:VTODO<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vcalendar"><br />
<p>VERSION: <span class="version">2.0</span></p><br />
<p>PRODID: <span class="prodid">-//ABC Corporation//NONSGML My Product//EN</span></p><br />
<div class="vtodo"><br />
<p>DTSTAMP: <span class="dtstamp">19980130T134500Z</span></p><br />
<p>SEQUENCE: <span class="sequence">2</span></p><br />
<p>UID: <span class="uid">uid4@host1.com</span></p><br />
<p>ORGANIZER: <a class="organizer" href="mailto:unclesam@us.gov">unclesam@us.gov</a></p><br />
<p>ATTENDEE: <span class="attendee"><a class="value" href="mailto:jqpublic@host.com">jqpublic@host.com</a>, <span class="partstat">ACCEPTED</span></span></p><br />
<p>DUE: <abbr class="due" title="19980415T235959">April 15, 1998</abbr></p><br />
<p>STATUS: <span class="status">NEEDS-ACTION</span></p><br />
<p class="summary">Submit Income Taxes</p><br />
<div class="valarm"><br />
<p>ACTION: <span class="action">AUDIO</span></p><br />
<p>TRIGGER: <span class="trigger">19980403T120000</span></p><br />
<p>ATTACHMENT: <a class="attach" type="audio/basic" href="http://host.com/pub/audio-files/ssbanner.aud">http://host.com/pub/audio-files/ssbanner.aud</a></p><br />
<p>REPEAT: <span class="repeat">4</span></p><br />
<p>DURATION: <span class="duration">PT1H</span></p><br />
</div><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 5: journal entry ====<br />
The following is an example of a journal entry.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
VERSION:2.0<br />
PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
BEGIN:VJOURNAL<br />
DTSTAMP:19970324T120000Z<br />
UID:uid5@host1.com<br />
ORGANIZER:MAILTO:jsmith@host.com<br />
STATUS:DRAFT<br />
CLASS:PUBLIC<br />
CATEGORY:Project Report, XYZ, Weekly Meeting<br />
DESCRIPTION:Project xyz Review Meeting Minutes\nAgenda\n<br />
1. Review of project version 1.0 requirements.\n<br />
2. Definition of project processes.\n<br />
3. Review of project schedule.\nParticipants: John Smith, Jane Doe, Jim Dandy\n<br />
-It was decided that the requirements need to be signed off by product marketing.\n<br />
-Project processes were accepted.\n-Project schedule needs to account for scheduled <br />
holidays and employee vacation time. Check with HR for specific dates.\n<br />
-New schedule will be distributed by Friday.\n<br />
-Next weeks meeting is cancelled. No meeting until 3/23.<br />
END:VJOURNAL<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
(*note*: line-breaks have been added into the description, in reality it should be one line)<br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vcalendar"><br />
@TODO: VERSION:2.0<br />
@TODO: PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
<div class="vjournal"><br />
<p>Posted at: <abbr class="dtstamp" title="19970324T120000Z">March 24, 1997, 12:00 UTC</abbr></p><br />
<p class="uid">uid5@host1.com</p><br />
<p>Organizer: <a class="organizer"mailto:jsmith@host.com">jsmith@host.com</a><br />
<p>Status: <span class="status">DRAFT</span></p><br />
<p>This journal is<span class="class">PUBLIC</span></p><br />
<p>Filed under:</p><br />
<ul class="category"><br />
<li>Project Report<br />
<li>XYZ</li><br />
<li>Weekly Meeting</li><br />
</ul><br />
<p class="description">DESCRIPTION:Project xyz Review Meeting Minutes<br /><br />
Agenda<br /><br />
1. Review of project version 1.0 requirements.<br /><br />
2. Definition of project processes.<br /><br />
3. Review of project schedule.<br /><br />
Participants: John Smith, Jane Doe, Jim Dandy<br /><br />
-It was decided that the requirements need to be signed off by product marketing.<br /><br />
-Project processes were accepted.\n-Project schedule needs to account for scheduled <br />
holidays and employee vacation time. Check with HR for specific dates.<br /><br />
-New schedule will be distributed by Friday.<br /><br />
-Next weeks meeting is cancelled. No meeting until 3/23.<br />
<p><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 6. Free/Busy time ====<br />
<br />
The following is an example of published busy time information. The iCalendar object might be placed in the network resource www.host.com/calendar/busytime/jsmith.ifb.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
VERSION:2.0<br />
PRODID:-//RDU Software//NONSGML HandCal//EN<br />
BEGIN:VFREEBUSY<br />
ORGANIZER:MAILTO:jsmith@host.com<br />
DTSTART:19980313T141711Z<br />
DTEND:19980410T141711Z<br />
FREEBUSY:19980314T233000Z/19980315T003000Z<br />
FREEBUSY:19980316T153000Z/19980316T163000Z<br />
FREEBUSY:19980318T030000Z/19980318T040000Z<br />
URL:http://www.host.com/calendar/busytime/jsmith.ifb<br />
END:VFREEBUSY<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
== Other ==<br />
<br />
* See [[hcalendar-brainstorming]] for more examples (which may eventually be moved here) and analysis.</div>MarkPilgrimhttps://microformats.org/wiki/index.php?title=hcalendar-examples&diff=2034hcalendar-examples2005-10-11T16:44:59Z<p>MarkPilgrim: </p>
<hr />
<div>= hCalendar examples =<br />
<br />
Example [[hcalendar|hCalendars]].<br />
<br />
== Authors ==<br />
* [http://diveintomark.org/ Mark Pilgrim]<br />
* [http://theryanking.com/ Ryan King]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
<br />
== RFC 2445 examples in hCalendar ==<br />
<br />
These are 1:1 hCalendar examples for each example in [http://www.ietf.org/rfc/rfc2445.txt RFC 2445].<br />
<br />
Errata applied from [http://www.rfc-editor.org/cgi-bin/errata.pl#rfc2445 here].<br />
<br />
=== 4.6.1 Event Component ===<br />
<br />
The following is an example of the "VEVENT" calendar component used to represent a meeting that will also be opaque to searches for busy time:<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
UID:19970901T130000Z-123401@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19970903T163000Z<br />
DTEND:19970903T190000Z<br />
SUMMARY:Annual Employee Review<br />
CLASS:PRIVATE<br />
CATEGORIES:BUSINESS,HUMAN RESOURCES<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Annual Employee Review</h1><br />
<p>posted on <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<p>UID: <span class="uid">19970901T130000Z-123401@host.com</span></p><br />
<p>Dates: <abbr class="dtstart" title="19970903T163000Z">Septempter 3, 1997, 16:30</abbr> -<br />
<abbr class="dtend" title="19970903T190000Z">19:00 UTC</abbr></p><br />
<p>This meeting is <span class="class">PRIVATE</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
<h1 class="summary">Annual Employee Review</h1><br />
<p>posted on <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<p>UID: <span class="uid">19970901T130000Z-123401@host.com</span></p><br />
<p>Dates: <abbr class="dtstart" title="19970903T163000Z">Septempter 3, 1997, 16:30</abbr> - <abbr class="dtend" title="19970903T190000Z">19:00 UTC</abbr></p><br />
<p>This meeting is <span class="class">PRIVATE</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
<br />
==== Example 2 ====<br />
The following is an example of the "VEVENT" calendar component used to represent a reminder that will not be opaque, but rather transparent, to searches for busy time:<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
UID:19970901T130000Z-123402@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19970401T163000Z<br />
DTEND:19970402T010000Z<br />
SUMMARY:Laurel is in sensitivity awareness class.<br />
CLASS:PUBLIC<br />
CATEGORIES:BUSINESS,HUMAN RESOURCES<br />
TRANSP:TRANSPARENT<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar fragment:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Laurel is in sensitivity awareness class.</h1><br />
<p>Posted on: <abbr class="dtstamp" title=19970901T1300Z">September 1, 1997</abbr></p><br />
<p class="uid">19970901T130000Z-123402@host.com</p><br />
<p>Dates: <abbr class="dtstart" title="19970401T163000Z">April 1, 1997, 16:30 UTC</abbr>-<br />
<abbr class="dtend" title="19970402T010000Z">April 2, 1997 01:00 UTC</abbr></p><br />
<p>This event is <span class="class">public</span> and <span class="transp">transparent</span> to free/busy scheduling.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
<div class="vevent"><br />
<h1 class="summary">Laurel is in sensitivity awareness class.</h1><br />
<p>Posted on: <abbr class="dtstamp" title=19970901T1300Z">September 1, 1997</abbr></p><br />
<p class="uid">19970901T130000Z-123402@host.com</p><br />
<p>Dates: <abbr class="dtstart" title="19970401T163000Z">April 1, 1997, 16:30 UTC</abbr>-<br />
<abbr class="dtend" title="19970402T010000Z">April 2, 1997 01:00 UTC</abbr></p><br />
<p>This event is <span class="class">public</span> and <span class="transp">transparent</span> to free/busy scheduling.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
</div><br />
<br />
==== Example 3 ====<br />
<br />
The following is an example of the "VEVENT" calendar component used to represent an anniversary that will occur annually. Since it takes up no time, it will not appear as opaque in a search for busy time; no matter what the value of the "TRANSP" property indicates:<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
UID:19970901T130000Z-123403@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19971102<br />
SUMMARY:Our Blissful Anniversary<br />
CLASS:CONFIDENTIAL<br />
CATEGORIES:ANNIVERSARY,PERSONAL,SPECIAL OCCASION<br />
RRULE:FREQ=YEARLY<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar fragment:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Our Blissful Anniversary</h1><br />
<p>Posted on: <span class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<span class="uid">19970901T130000Z-123403@host.com</span><br />
<p>Date: <abbr class="dtstart" title="19971102">November 2, 1997</abbr></p><br />
<p>This event is <span class="class">confidential</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">ANNIVERSARY</li><br />
<li class="category">PERSONAL</li><br />
<li class="category">SPECIAL OCCASSION</li><br />
</ul><br />
<p class="rrule">Repeat <span class="freq">yearly</span></p><br />
</div><br />
</nowiki></pre><br />
<br />
ISSUES:<br />
* We have a larger discusion about RRULE that needs to be resolved, hopefully these examples will help that. --RyanKing<br />
<br />
This hCalendar could be displayed as:<br />
<br />
<div class="vevent"><br />
<h1 class="summary">Our Blissful Anniversary</h1><br />
<p>Posted on: <span class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<span class="uid">19970901T130000Z-123403@host.com</span><br />
<p>Date: <abbr class="dtstart" title="19971102">November 2, 1997</abbr></p><br />
<p>This event is <span class="class">confidential</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">ANNIVERSARY</li><br />
<li class="category">PERSONAL</li><br />
<li class="category">SPECIAL OCCASSION</li><br />
</ul><br />
<p class="rrule">Repeat <span class="freq">yearly</span></p><br />
</div><br />
<br />
=== 5. iCalendar Object Examples ===<br />
<br />
The following example specifies a three-day conference that begins at 8:00 AM EDT, September 18, 1996 and end at 6:00 PM EDT, September 20, 1996.<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
DTSTAMP:19960704T120000Z<br />
UID:uid1@host.com<br />
ORGANIZER:MAILTO:jsmith@host.com<br />
DTSTART:19960918T143000Z<br />
DTEND:19960920T220000Z<br />
STATUS:CONFIRMED<br />
CATEGORIES:CONFERENCE <br />
SUMMARY:Networld+Interop Conference<br />
DESCRIPTION:Networld+Interop Conference and Exhibit\nAtlanta World Congress Center\nAtlant\, Georgia<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar fragment:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Networld+Interop Conference</h1><br />
<p class="description">Networld+Interop Conference and Exhibit Atlanta World Congress<br />
Center Atlanta, Georgia</p><br />
<p>Posted on: <abbr class="dtstamp" title="19960704T120000Z">July 4, 1996</abbr></p><br />
<p class="uid">uid1@host.com</p><br />
<p>Orgainzed by: <a class="organizer" href="mailto:jsmith@host.com">jsmith@host.com</a></p><br />
<p>Dates: <abbr class="dtstart" title="19960918T143000Z">September 18, 1996, 14:30 UTC</abbr> -<br />
<abbr class="dtend" title="19960920T220000Z">September 20, 1996, 22:00 UTC</abbr></p><br />
<p>Status: <span class="status">CONFIRMED</span></p><br />
<p>Filed under:</p><br />
<ul class="categories"><br />
<li>CONFERENCE</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 2 ====<br />
The following example specifies a group scheduled meeting that begin at 8:30 AM EST on March 12, 1998 and end at 9:30 AM EST on March 12, 1998. The "Organizer" has scheduled the meeting with one or more calendar users in a group. A time zone specification for Eastern United States has been specified.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
PRODID:-//RDU Software//NONSGML HandCal//EN<br />
VERSION:2.0<br />
BEGIN:VTIMEZONE<br />
TZID:US-Eastern<br />
BEGIN:STANDARD<br />
DTSTART:19981025T020000<br />
RDATE:19981025T020000<br />
TZOFFSETFROM:-0400<br />
TZOFFSETTO:-0500<br />
TZNAME:EST<br />
END:STANDARD<br />
BEGIN:DAYLIGHT<br />
DTSTART:19990404T020000<br />
RDATE:19990404T020000<br />
TZOFFSETFROM:-0500<br />
TZOFFSETTO:-0400<br />
TZNAME:EDT<br />
END:DAYLIGHT<br />
END:VTIMEZONE<br />
BEGIN:VEVENT<br />
DTSTAMP:19980309T231000Z<br />
UID:guid-1.host1.com<br />
ORGANIZER;ROLE=CHAIR:MAILTO:mrbig@host.com<br />
ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT;CUTYPE=GROUP:MAILTO:employee-A@host.com<br />
DESCRIPTION:Project XYZ Review Meeting<br />
CATEGORIES:MEETING<br />
CLASS:PUBLIC<br />
CREATED:19980309T130000Z<br />
SUMMARY:XYZ Project Review<br />
DTSTART;TZID=US-Eastern:19980312T083000<br />
DTEND;TZID=US-Eastern:19980312T093000<br />
LOCATION:1CP Conference Room 4350<br />
END:VEVENT<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 3 ====<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
METHOD:xyz<br />
VERSION:2.0<br />
PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
BEGIN:VEVENT<br />
DTSTAMP:19970324T1200Z<br />
SEQUENCE:0<br />
UID:uid3@host1.com<br />
ORGANIZER:MAILTO:jdoe@host1.com<br />
ATTENDEE;RSVP=TRUE:MAILTO:jsmith@host1.com<br />
DTSTART:19970324T123000Z<br />
DTEND:19970324T210000Z<br />
CATEGORIES:MEETING,PROJECT<br />
CLASS:PUBLIC<br />
SUMMARY:Calendaring Interoperability Planning Meeting<br />
DESCRIPTION:Discuss how we can test c&s interoperability\nusing iCalendar and other IETF standards.<br />
LOCATION:LDB Lobby<br />
ATTACH;FMTTYPE=application/postscript:ftp://xyzCorp.com/pub/conf/bkgrnd.ps<br />
END:VEVENT<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vcalendar"><br />
<p>Method: <span class="method">xyz</span></p><br />
<p>Version: <span class="version">2.0</span></p><br />
<p>PRODID: <span class="prodid">-//ABC Corporation//NONSGML My Product//EN</span></p><br />
<div class="vevent"><br />
<p>DTSTAMP: span class="dtstamp">19970324T1200Z</span></p><br />
<p>SEQUENCE: <span class="sequence">0</span></p><br />
<p>UID: <span class="uid">uid3@host1.com</span></p><br />
<p>ORGANIZER: <a class="organizer" href="mailto:jdoe@host1.com">jdoe@host1.com</a></p><br />
<p>ATTENDEE: <span class="attendee"><a class="value" href="mailto:jsmith@host1.com">jsmith@host1.com</a> RSVPed? <span class="rsvp">TRUE></span></p><br />
<p>START TIME: <abbr class="dtstart" tite="19970324T123000Z"></abbr></p><br />
<p>END TIME: <abbr class="dtend title="19970324T210000Z"></abbr></p><br />
<ul class="categories"><br />
<li>MEETING</li><br />
<li>PROJECT</li><br />
</ul><br />
<p>CLASS: <span class="class">PUBLIC</span></p><br />
<p class="summary">Calendaring Interoperability Planning Meeting</p><br />
<p class="description">Discuss how we can test c&s interoperability using iCalendar and other IETF standards.</p><br />
<p class="location">LDB Lobby</p><br />
<p>Attachment: <a class="attach" type="application/postscript" href="ftp://xyzCorp.com/pub/conf/bkgrnd.ps">ftp://xyzCorp.com/pub/conf/bkgrnd.ps</a></p><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 4 ====<br />
<br />
The following is an example of a to-do due on April 15, 1998. An audio alarm has been specified to remind the calendar user at noon, the day before the to-do is expected to be completed and repeat hourly, four additional times. The to-do definition has been modified twice since it was initially created.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
VERSION:2.0<br />
PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
BEGIN:VTODO<br />
DTSTAMP:19980130T134500Z<br />
SEQUENCE:2<br />
UID:uid4@host1.com<br />
ORGANIZER:MAILTO:unclesam@us.gov<br />
ATTENDEE;PARTSTAT=ACCEPTED:MAILTO:jqpublic@host.com<br />
DUE:19980415T235959<br />
STATUS:NEEDS-ACTION<br />
SUMMARY:Submit Income Taxes<br />
BEGIN:VALARM<br />
ACTION:AUDIO<br />
TRIGGER:19980403T120000<br />
ATTACH;FMTTYPE=audio/basic:http://host.com/pub/audio-files/ssbanner.aud<br />
REPEAT:4<br />
DURATION:PT1H<br />
END:VALARM<br />
END:VTODO<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vcalendar"><br />
<p>VERSION: <span class="version">2.0</span></p><br />
<p>PRODID: <span class="prodid">-//ABC Corporation//NONSGML My Product//EN</span></p><br />
<div class="vtodo"><br />
<p>DTSTAMP: <span class="dtstamp">19980130T134500Z</span></p><br />
<p>SEQUENCE: <span class="sequence">2</span></p><br />
<p>UID: <span class="uid">uid4@host1.com</span></p><br />
<p>ORGANIZER: <a class="organizer" href="mailto:unclesam@us.gov">unclesam@us.gov</a></p><br />
<p>ATTENDEE: <span class="attendee"><a class="value" href="mailto:jqpublic@host.com">jqpublic@host.com</a>, <span class="partstat">ACCEPTED</span></span></p><br />
<p>DUE: <abbr class="due" title="19980415T235959">April 15, 1998</abbr></p><br />
<p>STATUS: <span class="status">NEEDS-ACTION</span></p><br />
<p class="summary">Submit Income Taxes</p><br />
<div class="valarm"><br />
<p>ACTION: <span class="action">AUDIO</span></p><br />
<p>TRIGGER: <span class="trigger">19980403T120000</span></p><br />
<p>ATTACHMENT: <a class="attach" type="audio/basic" href="http://host.com/pub/audio-files/ssbanner.aud">http://host.com/pub/audio-files/ssbanner.aud</a></p><br />
<p>REPEAT: <span class="repeat">4</span></p><br />
<p>DURATION: <span class="duration">PT1H</span></p><br />
</div><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 5: journal entry ====<br />
The following is an example of a journal entry.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
VERSION:2.0<br />
PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
BEGIN:VJOURNAL<br />
DTSTAMP:19970324T120000Z<br />
UID:uid5@host1.com<br />
ORGANIZER:MAILTO:jsmith@host.com<br />
STATUS:DRAFT<br />
CLASS:PUBLIC<br />
CATEGORY:Project Report, XYZ, Weekly Meeting<br />
DESCRIPTION:Project xyz Review Meeting Minutes\nAgenda\n<br />
1. Review of project version 1.0 requirements.\n<br />
2. Definition of project processes.\n<br />
3. Review of project schedule.\nParticipants: John Smith, Jane Doe, Jim Dandy\n<br />
-It was decided that the requirements need to be signed off by product marketing.\n<br />
-Project processes were accepted.\n-Project schedule needs to account for scheduled <br />
holidays and employee vacation time. Check with HR for specific dates.\n<br />
-New schedule will be distributed by Friday.\n<br />
-Next weeks meeting is cancelled. No meeting until 3/23.<br />
END:VJOURNAL<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
(*note*: line-breaks have been added into the description, in reality it should be one line)<br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vcalendar"><br />
@TODO: VERSION:2.0<br />
@TODO: PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
<div class="vjournal"><br />
<p>Posted at: <abbr class="dtstamp" title="19970324T120000Z">March 24, 1997, 12:00 UTC</abbr></p><br />
<p class="uid">uid5@host1.com</p><br />
<p>Organizer: <a class="organizer"mailto:jsmith@host.com">jsmith@host.com</a><br />
<p>Status: <span class="status">DRAFT</span></p><br />
<p>This journal is<span class="class">PUBLIC</span></p><br />
<p>Filed under:</p><br />
<ul class="category"><br />
<li>Project Report<br />
<li>XYZ</li><br />
<li>Weekly Meeting</li><br />
</ul><br />
<p class="description">DESCRIPTION:Project xyz Review Meeting Minutes<br /><br />
Agenda<br /><br />
1. Review of project version 1.0 requirements.<br /><br />
2. Definition of project processes.<br /><br />
3. Review of project schedule.<br /><br />
Participants: John Smith, Jane Doe, Jim Dandy<br /><br />
-It was decided that the requirements need to be signed off by product marketing.<br /><br />
-Project processes were accepted.\n-Project schedule needs to account for scheduled <br />
holidays and employee vacation time. Check with HR for specific dates.<br /><br />
-New schedule will be distributed by Friday.<br /><br />
-Next weeks meeting is cancelled. No meeting until 3/23.<br />
<p><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 6. Free/Busy time ====<br />
<br />
The following is an example of published busy time information. The iCalendar object might be placed in the network resource www.host.com/calendar/busytime/jsmith.ifb.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
VERSION:2.0<br />
PRODID:-//RDU Software//NONSGML HandCal//EN<br />
BEGIN:VFREEBUSY<br />
ORGANIZER:MAILTO:jsmith@host.com<br />
DTSTART:19980313T141711Z<br />
DTEND:19980410T141711Z<br />
FREEBUSY:19980314T233000Z/19980315T003000Z<br />
FREEBUSY:19980316T153000Z/19980316T163000Z<br />
FREEBUSY:19980318T030000Z/19980318T040000Z<br />
URL:http://www.host.com/calendar/busytime/jsmith.ifb<br />
END:VFREEBUSY<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
== Other ==<br />
<br />
* See [[hcalendar-brainstorming]] for more examples (which may eventually be moved here) and analysis.</div>MarkPilgrimhttps://microformats.org/wiki/index.php?title=hcalendar-examples&diff=2033hcalendar-examples2005-10-11T16:42:20Z<p>MarkPilgrim: </p>
<hr />
<div>= hCalendar examples =<br />
<br />
Example [[hcalendar|hCalendars]].<br />
<br />
== Authors ==<br />
* [http://diveintomark.org/ Mark Pilgrim]<br />
* [http://theryanking.com/ Ryan King]<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
<br />
== RFC 2445 examples in hCalendar ==<br />
<br />
These are 1:1 hCalendar examples for each example in [http://www.ietf.org/rfc/rfc2445.txt RFC 2445].<br />
<br />
Errata applied from [http://www.rfc-editor.org/cgi-bin/errata.pl#rfc2445 here].<br />
<br />
=== 4.6.1 Event Component ===<br />
<br />
The following is an example of the "VEVENT" calendar component used to represent a meeting that will also be opaque to searches for busy time:<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
UID:19970901T130000Z-123401@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19970903T163000Z<br />
DTEND:19970903T190000Z<br />
SUMMARY:Annual Employee Review<br />
CLASS:PRIVATE<br />
CATEGORIES:BUSINESS,HUMAN RESOURCES<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Annual Employee Review</h1><br />
<p>posted on <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<p>UID: <span class="uid">19970901T130000Z-123401@host.com</span></p><br />
<p>Dates: <abbr class="dtstart" title="19970903T163000Z">Septempter 3, 1997, 16:30</abbr> -<br />
<abbr class="dtend" title="19970903T190000Z">19:00 UTC</abbr></p><br />
<p>This meeting is <span class="class">PRIVATE</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
<h1 class="summary">Annual Employee Review</h1><br />
<p>posted on <abbr class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<p>UID: <span class="uid">19970901T130000Z-123401@host.com</span></p><br />
<p>Dates: <abbr class="dtstart" title="19970903T163000Z">Septempter 3, 1997, 16:30</abbr> - <abbr class="dtend" title="19970903T190000Z">19:00 UTC</abbr></p><br />
<p>This meeting is <span class="class">PRIVATE</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
<br />
==== Example 2 ====<br />
The following is an example of the "VEVENT" calendar component used to represent a reminder that will not be opaque, but rather transparent, to searches for busy time:<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
UID:19970901T130000Z-123402@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19970401T163000Z<br />
DTEND:19970402T010000Z<br />
SUMMARY:Laurel is in sensitivity awareness class.<br />
CLASS:PUBLIC<br />
CATEGORIES:BUSINESS,HUMAN RESOURCES<br />
TRANSP:TRANSPARENT<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar fragment:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Laurel is in sensitivity awareness class.</h1><br />
<p>Posted on: <abbr class="dtstamp" title=19970901T1300Z">September 1, 1997</abbr></p><br />
<p class="uid">19970901T130000Z-123402@host.com</p><br />
<p>Dates: <abbr class="dtstart" title="19970401T163000Z">April 1, 1997, 16:30 UTC</abbr>-<br />
<abbr class="dtend" title="19970402T010000Z">April 2, 1997 01:00 UTC</abbr></p><br />
<p>This event is <span class="class">public</span> and <span class="transp">transparent</span> to free/busy scheduling.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
<div class="vevent"><br />
<h1 class="summary">Laurel is in sensitivity awareness class.</h1><br />
<p>Posted on: <abbr class="dtstamp" title=19970901T1300Z">September 1, 1997</abbr></p><br />
<p class="uid">19970901T130000Z-123402@host.com</p><br />
<p>Dates: <abbr class="dtstart" title="19970401T163000Z">April 1, 1997, 16:30 UTC</abbr>-<br />
<abbr class="dtend" title="19970402T010000Z">April 2, 1997 01:00 UTC</abbr></p><br />
<p>This event is <span class="class">public</span> and <span class="transp">transparent</span> to free/busy scheduling.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">BUSINESS</li><br />
<li class="category">HUMAN RESOURCES</li><br />
</ul><br />
</div><br />
<br />
==== Example 3 ====<br />
<br />
The following is an example of the "VEVENT" calendar component used to represent an anniversary that will occur annually. Since it takes up no time, it will not appear as opaque in a search for busy time; no matter what the value of the "TRANSP" property indicates:<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
UID:19970901T130000Z-123403@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19971102<br />
SUMMARY:Our Blissful Anniversary<br />
CLASS:CONFIDENTIAL<br />
CATEGORIES:ANNIVERSARY,PERSONAL,SPECIAL OCCASION<br />
RRULE:FREQ=YEARLY<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar fragment:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Our Blissful Anniversary</h1><br />
<p>Posted on: <span class="dtstamp" title="19970901T1300Z">September 1, 1997</abbr></p><br />
<span class="uid">19970901T130000Z-123403@host.com</span><br />
<p>Date: <abbr class="dtstart" title="19971102">November 2, 1997</abbr></p><br />
<p>This event is <span class="class">confidential</span>.</p><br />
<p>Filed under:</p><br />
<ul><br />
<li class="category">ANNIVERSARY</li><br />
<li class="category">PERSONAL</li><br />
<li class="category">SPECIAL OCCASSION</li><br />
</ul><br />
<p class="rrule">Repeat <span class="freq">yearly</span></p><br />
</div><br />
</nowiki></pre><br />
<br />
ISSUES:<br />
* We have a larger discusion about RRULE that needs to be resolved, hopefully these examples will help that. --RyanKing<br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
=== 5. iCalendar Object Examples ===<br />
<br />
The following example specifies a three-day conference that begins at 8:00 AM EDT, September 18, 1996 and end at 6:00 PM EDT, September 20, 1996.<br />
<br />
<pre><nowiki><br />
BEGIN:VEVENT<br />
DTSTAMP:19960704T120000Z<br />
UID:uid1@host.com<br />
ORGANIZER:MAILTO:jsmith@host.com<br />
DTSTART:19960918T143000Z<br />
DTEND:19960920T220000Z<br />
STATUS:CONFIRMED<br />
CATEGORIES:CONFERENCE <br />
SUMMARY:Networld+Interop Conference<br />
DESCRIPTION:Networld+Interop Conference and Exhibit\nAtlanta World Congress Center\nAtlant\, Georgia<br />
END:VEVENT<br />
</nowiki></pre><br />
<br />
This iCalendar event as an hCalendar fragment:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<h1 class="summary">Networld+Interop Conference</h1><br />
<p class="description">Networld+Interop Conference and Exhibit Atlanta World Congress<br />
Center Atlanta, Georgia</p><br />
<p>Posted on: <abbr class="dtstamp" title="19960704T120000Z">July 4, 1996</abbr></p><br />
<p class="uid">uid1@host.com</p><br />
<p>Orgainzed by: <a class="organizer" href="mailto:jsmith@host.com">jsmith@host.com</a></p><br />
<p>Dates: <abbr class="dtstart" title="19960918T143000Z">September 18, 1996, 14:30 UTC</abbr> -<br />
<abbr class="dtend" title="19960920T220000Z">September 20, 1996, 22:00 UTC</abbr></p><br />
<p>Status: <span class="status">CONFIRMED</span></p><br />
<p>Filed under:</p><br />
<ul class="categories"><br />
<li>CONFERENCE</li><br />
</ul><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 2 ====<br />
The following example specifies a group scheduled meeting that begin at 8:30 AM EST on March 12, 1998 and end at 9:30 AM EST on March 12, 1998. The "Organizer" has scheduled the meeting with one or more calendar users in a group. A time zone specification for Eastern United States has been specified.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
PRODID:-//RDU Software//NONSGML HandCal//EN<br />
VERSION:2.0<br />
BEGIN:VTIMEZONE<br />
TZID:US-Eastern<br />
BEGIN:STANDARD<br />
DTSTART:19981025T020000<br />
RDATE:19981025T020000<br />
TZOFFSETFROM:-0400<br />
TZOFFSETTO:-0500<br />
TZNAME:EST<br />
END:STANDARD<br />
BEGIN:DAYLIGHT<br />
DTSTART:19990404T020000<br />
RDATE:19990404T020000<br />
TZOFFSETFROM:-0500<br />
TZOFFSETTO:-0400<br />
TZNAME:EDT<br />
END:DAYLIGHT<br />
END:VTIMEZONE<br />
BEGIN:VEVENT<br />
DTSTAMP:19980309T231000Z<br />
UID:guid-1.host1.com<br />
ORGANIZER;ROLE=CHAIR:MAILTO:mrbig@host.com<br />
ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT;CUTYPE=GROUP:MAILTO:employee-A@host.com<br />
DESCRIPTION:Project XYZ Review Meeting<br />
CATEGORIES:MEETING<br />
CLASS:PUBLIC<br />
CREATED:19980309T130000Z<br />
SUMMARY:XYZ Project Review<br />
DTSTART;TZID=US-Eastern:19980312T083000<br />
DTEND;TZID=US-Eastern:19980312T093000<br />
LOCATION:1CP Conference Room 4350<br />
END:VEVENT<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 3 ====<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
METHOD:xyz<br />
VERSION:2.0<br />
PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
BEGIN:VEVENT<br />
DTSTAMP:19970324T1200Z<br />
SEQUENCE:0<br />
UID:uid3@host1.com<br />
ORGANIZER:MAILTO:jdoe@host1.com<br />
ATTENDEE;RSVP=TRUE:MAILTO:jsmith@host1.com<br />
DTSTART:19970324T123000Z<br />
DTEND:19970324T210000Z<br />
CATEGORIES:MEETING,PROJECT<br />
CLASS:PUBLIC<br />
SUMMARY:Calendaring Interoperability Planning Meeting<br />
DESCRIPTION:Discuss how we can test c&s interoperability\nusing iCalendar and other IETF standards.<br />
LOCATION:LDB Lobby<br />
ATTACH;FMTTYPE=application/postscript:ftp://xyzCorp.com/pub/conf/bkgrnd.ps<br />
END:VEVENT<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vcalendar"><br />
<p>Method: <span class="method">xyz</span></p><br />
<p>Version: <span class="version">2.0</span></p><br />
<p>PRODID: <span class="prodid">-//ABC Corporation//NONSGML My Product//EN</span></p><br />
<div class="vevent"><br />
<p>DTSTAMP: span class="dtstamp">19970324T1200Z</span></p><br />
<p>SEQUENCE: <span class="sequence">0</span></p><br />
<p>UID: <span class="uid">uid3@host1.com</span></p><br />
<p>ORGANIZER: <a class="organizer" href="mailto:jdoe@host1.com">jdoe@host1.com</a></p><br />
<p>ATTENDEE: <span class="attendee"><a class="value" href="mailto:jsmith@host1.com">jsmith@host1.com</a> RSVPed? <span class="rsvp">TRUE></span></p><br />
<p>START TIME: <abbr class="dtstart" tite="19970324T123000Z"></abbr></p><br />
<p>END TIME: <abbr class="dtend title="19970324T210000Z"></abbr></p><br />
<ul class="categories"><br />
<li>MEETING</li><br />
<li>PROJECT</li><br />
</ul><br />
<p>CLASS: <span class="class">PUBLIC</span></p><br />
<p class="summary">Calendaring Interoperability Planning Meeting</p><br />
<p class="description">Discuss how we can test c&s interoperability using iCalendar and other IETF standards.</p><br />
<p class="location">LDB Lobby</p><br />
<p>Attachment: <a class="attach" type="application/postscript" href="ftp://xyzCorp.com/pub/conf/bkgrnd.ps">ftp://xyzCorp.com/pub/conf/bkgrnd.ps</a></p><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 4 ====<br />
<br />
The following is an example of a to-do due on April 15, 1998. An audio alarm has been specified to remind the calendar user at noon, the day before the to-do is expected to be completed and repeat hourly, four additional times. The to-do definition has been modified twice since it was initially created.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
VERSION:2.0<br />
PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
BEGIN:VTODO<br />
DTSTAMP:19980130T134500Z<br />
SEQUENCE:2<br />
UID:uid4@host1.com<br />
ORGANIZER:MAILTO:unclesam@us.gov<br />
ATTENDEE;PARTSTAT=ACCEPTED:MAILTO:jqpublic@host.com<br />
DUE:19980415T235959<br />
STATUS:NEEDS-ACTION<br />
SUMMARY:Submit Income Taxes<br />
BEGIN:VALARM<br />
ACTION:AUDIO<br />
TRIGGER:19980403T120000<br />
ATTACH;FMTTYPE=audio/basic:http://host.com/pub/audio-files/ssbanner.aud<br />
REPEAT:4<br />
DURATION:PT1H<br />
END:VALARM<br />
END:VTODO<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vcalendar"><br />
<p>VERSION: <span class="version">2.0</span></p><br />
<p>PRODID: <span class="prodid">-//ABC Corporation//NONSGML My Product//EN</span></p><br />
<div class="vtodo"><br />
<p>DTSTAMP: <span class="dtstamp">19980130T134500Z</span></p><br />
<p>SEQUENCE: <span class="sequence">2</span></p><br />
<p>UID: <span class="uid">uid4@host1.com</span></p><br />
<p>ORGANIZER: <a class="organizer" href="mailto:unclesam@us.gov">unclesam@us.gov</a></p><br />
<p>ATTENDEE: <span class="attendee"><a class="value" href="mailto:jqpublic@host.com">jqpublic@host.com</a>, <span class="partstat">ACCEPTED</span></span></p><br />
<p>DUE: <abbr class="due" title="19980415T235959">April 15, 1998</abbr></p><br />
<p>STATUS: <span class="status">NEEDS-ACTION</span></p><br />
<p class="summary">Submit Income Taxes</p><br />
<div class="valarm"><br />
<p>ACTION: <span class="action">AUDIO</span></p><br />
<p>TRIGGER: <span class="trigger">19980403T120000</span></p><br />
<p>ATTACHMENT: <a class="attach" type="audio/basic" href="http://host.com/pub/audio-files/ssbanner.aud">http://host.com/pub/audio-files/ssbanner.aud</a></p><br />
<p>REPEAT: <span class="repeat">4</span></p><br />
<p>DURATION: <span class="duration">PT1H</span></p><br />
</div><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 5: journal entry ====<br />
The following is an example of a journal entry.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
VERSION:2.0<br />
PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
BEGIN:VJOURNAL<br />
DTSTAMP:19970324T120000Z<br />
UID:uid5@host1.com<br />
ORGANIZER:MAILTO:jsmith@host.com<br />
STATUS:DRAFT<br />
CLASS:PUBLIC<br />
CATEGORY:Project Report, XYZ, Weekly Meeting<br />
DESCRIPTION:Project xyz Review Meeting Minutes\nAgenda\n<br />
1. Review of project version 1.0 requirements.\n<br />
2. Definition of project processes.\n<br />
3. Review of project schedule.\nParticipants: John Smith, Jane Doe, Jim Dandy\n<br />
-It was decided that the requirements need to be signed off by product marketing.\n<br />
-Project processes were accepted.\n-Project schedule needs to account for scheduled <br />
holidays and employee vacation time. Check with HR for specific dates.\n<br />
-New schedule will be distributed by Friday.\n<br />
-Next weeks meeting is cancelled. No meeting until 3/23.<br />
END:VJOURNAL<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
(*note*: line-breaks have been added into the description, in reality it should be one line)<br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
<div class="vcalendar"><br />
@TODO: VERSION:2.0<br />
@TODO: PRODID:-//ABC Corporation//NONSGML My Product//EN<br />
<div class="vjournal"><br />
<p>Posted at: <abbr class="dtstamp" title="19970324T120000Z">March 24, 1997, 12:00 UTC</abbr></p><br />
<p class="uid">uid5@host1.com</p><br />
<p>Organizer: <a class="organizer"mailto:jsmith@host.com">jsmith@host.com</a><br />
<p>Status: <span class="status">DRAFT</span></p><br />
<p>This journal is<span class="class">PUBLIC</span></p><br />
<p>Filed under:</p><br />
<ul class="category"><br />
<li>Project Report<br />
<li>XYZ</li><br />
<li>Weekly Meeting</li><br />
</ul><br />
<p class="description">DESCRIPTION:Project xyz Review Meeting Minutes<br /><br />
Agenda<br /><br />
1. Review of project version 1.0 requirements.<br /><br />
2. Definition of project processes.<br /><br />
3. Review of project schedule.<br /><br />
Participants: John Smith, Jane Doe, Jim Dandy<br /><br />
-It was decided that the requirements need to be signed off by product marketing.<br /><br />
-Project processes were accepted.\n-Project schedule needs to account for scheduled <br />
holidays and employee vacation time. Check with HR for specific dates.<br /><br />
-New schedule will be distributed by Friday.<br /><br />
-Next weeks meeting is cancelled. No meeting until 3/23.<br />
<p><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
==== Example 6. Free/Busy time ====<br />
<br />
The following is an example of published busy time information. The iCalendar object might be placed in the network resource www.host.com/calendar/busytime/jsmith.ifb.<br />
<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
VERSION:2.0<br />
PRODID:-//RDU Software//NONSGML HandCal//EN<br />
BEGIN:VFREEBUSY<br />
ORGANIZER:MAILTO:jsmith@host.com<br />
DTSTART:19980313T141711Z<br />
DTEND:19980410T141711Z<br />
FREEBUSY:19980314T233000Z/19980315T003000Z<br />
FREEBUSY:19980316T153000Z/19980316T163000Z<br />
FREEBUSY:19980318T030000Z/19980318T040000Z<br />
URL:http://www.host.com/calendar/busytime/jsmith.ifb<br />
END:VFREEBUSY<br />
END:VCALENDAR<br />
</nowiki></pre><br />
<br />
This iCalendar as an hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
This hCalendar could be displayed as:<br />
<br />
@TODO<br />
<br />
== Other ==<br />
<br />
* See [[hcalendar-brainstorming]] for more examples (which may eventually be moved here) and analysis.</div>MarkPilgrim