http://microformats.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=Mark+MansourMicroformats Wiki - User contributions [en]2026-04-27T04:45:12ZUser contributionsMediaWiki 1.38.4http://microformats.org/wiki/index.php?title=to-do&diff=5727to-do2006-03-11T01:02:39Z<p>Mark Mansour: </p>
<hr />
<div><h1>To Do</h1><br />
<br />
This page is for posting [[microformats]] related shared to do items. If you want to use this page for your microformats related to-do items, create a section with your name on it. The reason we are keeping these all on the same page is to make it easier to tell when people are working on similar things, and to make it more obvious when people help out with other people's tasks. In theory this probably won't scale, but let's first see how it does in practice. :) - [http://tantek.com Tantek]<br />
<br />
__TOC__<br />
<br />
== Lazyweb ==<br />
<br />
Just some nice things, feel free to do any of these.<br />
<br />
=== for all microformats ===<br />
* quick and easy "how to" pages for each microformat. [[use]] is a good overall start.<br />
* brief summary statements for each microformat that explain why it matters, what does it accomplish for the publisher.<br />
* write up [http://microformats.org/discuss/ mailing-list] questions and answers in the appropriate [[faq]] pages.<br />
<br />
=== hReview ===<br />
* [[hreview|hReview]] support in Ecto (hey Adriaan!), requested by Andy Smith<br />
* an [[hreview|hReview]] validator<br />
* a semantic, clean css star rating picker (e.g. a UI widget to rate from 1-5 stars)<br />
** both [http://komodomedia.com/blog/index.php/2005/08/24/creating-a-star-rater-using-css/ this] and [http://factorycity.net/demos/drupal/rating/default.html this] have some flaws. Ask [[User:RyanKing|Ryan King]] for an explanation.<br />
<br />
=== hCard ===<br />
* microformatted versions of conference pages<br />
** Do a revision of the [http://conferences.oreillynet.com/etel2006/ ETel] [http://conferences.oreillynet.com/pub/w/44/speakers.html speaker's page] with all the speakers marked up with [[hcard|hCard]] and links to "Add hCards to Address Book" etc., similar to the [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 speakers page which Tantek did a revision of last fall].<br />
* vcard to hcard converter<br />
** would be nice to have a web upload UI that would take one or more vcards from apple's address book and give them back to you hcards<br />
** [[User:RobertBachmann | RobertBachmann]] suggests starting points:<br />
*** For Ruby: http://vpim.rubyforge.org/ <br />
*** For C: http://freshmeat.net/projects/libvc/<br />
*** For Python: http://www.nongnu.org/python-pdi/<br />
*** For PHP: http://pear.php.net/package/Contact_Vcard_Parse/<br />
<br />
=== hCalendar/hCard/hReview editor ===<br />
* onblur in the URL field (e.g. on hCalendar), goes out and tries to retrieve an object of same time (e.g. an hCalendar vevent) from that URL and uses it to autofill the form, same thing if the creator is loaded with that URL prefilled (e.g. due to a ?url=http://example.com/ in the URL that loads the creator).<br />
<br />
=== WordPress patches for microformats ===<br />
* submit patches for WordPress code/templates for microformats improvement<br />
** &lt;address class="vcard"&gt; improvement in post author publication (e.g. home page of http://microformats.org/ )<br />
* Wordpress plugin for microformats, specifically hReview and hCalendar<br />
** See [http://www.surfarama.com/index.php?p=227 lazyweb request]<br />
<br />
=== Yahoo Open Source Library Patches ===<br />
<br />
Several of these could very much be improved with a little microformats markup. Do we just make patches and submit them? Contact Nate Koechley at Yahoo (see Tantek for contact info) to follow-up.<br />
<br />
* [http://developer.yahoo.net/yui/ Yahoo! User Interface Library]<br />
* [http://developer.yahoo.net/ypatterns/ Yahoo! Design Patterns Library]<br />
* [http://www.yuiblog.com Yahoo! User Interface Blog]<br />
<br />
== Tantek ==<br />
<br />
I'm keeping a few microformats related to-do items here both for my own convenience, and for folks looking to help out with small tasks. If so, just create a new section with your name, and and maybe copy the item there, and put your name next to the item in my list. We'll figure this out as we go along. Thanks, [http://tantek.com Tantek].<br />
<br />
=== for all microformat specs ===<br />
* sort implementations by authoring/creating/publishing, browsing/viewing, converting/importing, indexing/searching.<br />
<br />
Hmmm... I like: '''A'''uthoring, '''B'''rowsing, '''C'''onverting, '''I'''ndexing, '''L'''ibraries (for developers), and '''P'''otential (for open source projects we want to add support to). Anybody have alternative suggestions for this vocabulary? I don't have a particularly strong preference so I'm going to go with these four until I find examples that don't fit, or someone suggests something better.<br />
<br />
See: [http://microformats.org/wiki/hcalendar#Implementations hCalendar Implementations] for a first attempt at this. Assuming folks like that, we can go ahead with categorizing the implementations sections of other microformats specifications.<br />
<br />
=== iterate on current microformats ===<br />
==== [[hreview|hReview]] ====<br />
* Write hReview 0.3 XMDP profile, and reconcile with [[hcalendar-profile]] and [[hcard-profile]]. Makes sense to have a combined profile of all three for hReview, since hReview normatively depends on hCard and hCalendar.<br />
<br />
==== [[hcalendar|hCalendar]] ====<br />
* need spec details and then [[hcalendar-examples]] of multi-instance [[hcalendar|hCalendar]] events<br />
* need spec details and then [[hcalendar-examples]] of repeating events<br />
* add explicit explanation and examples for LOCATION [[hcard|hCards]] and ATTENDEE [[hcard|hCards]], perhaps on a separate [[hcalendar-examples]] page.<br />
* need to resolve all outstanding [[hcalendar-issues]] to-do items.<br />
* create [[hcalendar-profile]] and have folks verify it. note that it will likely need reconciliation with the [[hcard-profile]], especially since [[hcalendar|hCalendar]] normatively depends on [[hcard|hCard]]. Probably makes sense to have a combined profile which hCalendar would use.<br />
<br />
==== [[hcard|hCard]] ====<br />
* [[hcard-examples]]<br />
** add examples of [[hcard|hCard]]s with work telephone, mailing address etc.<br />
** add examples of marking up an organization vs. a person, then link to it from [http://microformats.org/wiki/hcard#Organization_Contact_Info hCard spec section on Organization Contact Info].<br />
** add example of organization-name and organization-unit usage.<br />
* more examples in the wild<br />
** help dglazkov markup: http://glazkov.com/blog/archive/2003/12/17/147.aspx<br />
<br />
=== introduction / community ===<br />
* microformats-discuss<br />
** introductory email sent to new subscribers needs to direct people to [[process]] and [[how-to-play]]<br />
* Need to add more to the [[naming-principles]], to cover in particular:<br />
** avoid using the same name to mean two things<br />
** avoid using two names to mean the same thing<br />
** seek to keep the microformats vocabulary minimal, memorable, and usable.<br />
<br />
=== profiles ===<br />
<br />
* update XMDP with new required features:<br />
** ability for one profile to include/import another (rel="import" ?)<br />
** ability to reference an XMDP via rel="profile" (similar to XHTML2 rel value by same name)<br />
** ability/suggestion to reference an XMDP using &lt;a href&gt; in addition to &lt;link&gt;<br />
<br />
=== microformat parsing documentation ===<br />
* Add XPath equivalents where appropriate in [[hcard-parsing]]<br />
<br />
=== create microformats wiki pages for ===<br />
* microformats [[history]]<br />
** introduction of terms (when were microformats terms introduced, by whom, etc.)<br />
** introduction of specs (when were microformats specifications first introduced)<br />
*** use the history on Technorati's developer wiki for evidence of earliest dates.<br />
*** use the [[presentations]] as a source as well.<br />
<br />
=== improve usability and automation on the site ===<br />
* figure out how to get wordpress to autopost blog posts to the microformats-announce list<br />
** ideally use the from address of the author of the blog post<br />
** maybe photomatt knows how to do this.<br />
<br />
=== help with microformat implementations ===<br />
* [http://microformats.org/code/hcard/creator hCard creator] - add features/fields<br />
** email<br />
** aim / instant messaging contact info<br />
* wordpress improvements<br />
** WP admin for new profiles<br />
*** should simply read blog URL<br />
*** look for hcards and parse them<br />
* [http://gmpg.org/xfn/creator XFN Creator] localizations<br />
** Get someone to verify the [http://gmpg.org/xfn/creator-ru XFN Creator Russian localization].<br />
** Add it to the [http://gmpg.org/xfn/tools XFN Tools] page.<br />
** Add rel="alternate" href="creator-ru" &lt;link&gt;s to the other XFN Creators.<br />
* Conference Schedule Creator<br />
** We need to ASAP build a simple conference schedule creator (and editor?) that builds upon the hCalendar creator. We should make it *trivial* for conference organizers to build/edit/publish an [[hcalendar|hCalendar]] schedule for their conference, including auto-generated "Subscribe..." link which produces the proper "webcal:..." link with X2V. Note: see the "axis" and "header" attributes in HTML4, specifically in the section on Tables.<br />
<br />
=== help with new microformat requests ===<br />
* expense reports (really just a list of "expense" items), [http://flickr.com/photos/edyson/56774178/ requested by ED], should look at UBL as a pre-existing format<br />
* photo-notes microformat<br />
** clean up Subethaedit notes from working session with Greg Elin, Ryan King, Kevin Marks, Suw Charman and email to folks and figure out next steps<br />
** iterate on [[photo-note-examples]] and start [[photo-note-formats]] and [[photo-note-brainstorming]].<br />
<br />
* Can we make "microformat" and "microformats" into [http://factoryjoe.com/blog/2006/01/14/the-case-for-community-marks/ Community Marks]?<br />
<br />
==Ryan==<br />
=== hCalendar/hCard/hReview creator improvements ===<br />
* get all creators working in IE/Win, IE/Mac, Safari/OSX.3<br />
<br />
=== *-authoring microformats wiki pages ===<br />
* Add some tips to [[hcard-authoring]] - a tutorial on creating an hCard for your site, blog (common platforms), etc.<br />
* [[hcalendar-authoring]] - a tutorial on how to blog events so your friends can subscribe to them<br />
* [[hreview-authoring]] - a tutorial on how to blog reviews so that they'll be aggregated.<br />
<br />
=== other ===<br />
* add an example of how to use DURATION in hcalendar see http://www.policyawareweb.org/2005/ftf2/paw-mtg#item15) -> verify http://svn.lifelint.com/hcalendar_tests/calendar-todo-multiple-attendees-and-alarm.xml<br />
<br />
=== rel-payment ===<br />
* update rel-payment to reference the IANA registry [http://www1.ietf.org/mail-archive/web/ietf-announce/current/msg02055.html]<br />
<br />
=== hcalendar ===<br />
* move tests from http://svn.lifelint.com/hcalendar_tests/ to subversion on microformats.org<br />
* make sure we explicitly disallow 'vjournal'<br />
<br />
== Dimitri Glazkov ==<br />
<br />
* Figure out REST/Microformats thing<br />
* Work on result set idea<br />
* Implement h-creators using Web Forms 2.0<br />
<br />
== Chris Messina ==<br />
<br />
* Work on a microformat for play-lists (is it just a XOXO ordererd list of play-items?)<br />
* Work on a microformat for play-item<br />
<br />
=== Wishlist ===<br />
<br />
* Microformat for "buyable items" (see [[listing-examples]] and related documents)<br />
* Location MF -- right click "map this" (see [[geo]] and [[adr]])<br />
* Better hCard support in the browser -- right click "IM this person...", "Add to contacts"<br />
* Better hCal support -- support many views of same hCal data on one page using XSLT<br />
<br />
== Robert Bachmann ==<br />
<br />
* make hatom2atom.xsl conformant to [[hatom]].<br />
<br />
== Brian Suda ==<br />
=== Citation Microformats ===<br />
Add all my notes to the Wiki<br />
<br />
=== X2V ===<br />
Make changes and update site (almost stable)<br />
Get ATTENDEE and other strange attributes working<br />
<br />
<br />
== Mark Rickerby ==<br />
<br />
=== Current Tasks ===<br />
<br />
* Follow up on usability review<br />
** Edits to homepage feature box text <br />
** Draft of [[getting-started]] page<br />
* Review content for new pages - [[start-simple]], [[modularity]], [[reuse]], [[humans-first]]<br />
* xoxo datatype examples<br />
** test case lists<br />
** transmitting key/value lists<br />
* practical feedback on hresume<br />
<br />
=== Wishlist ===<br />
<br />
* hmmm<br />
<br />
== Ernest Prabhakar ==<br />
=== Wiki-Thon Proposal ===<br />
Set aside several hours (probably a Friday night US PST) for focused work on the Wiki, including both physical (e.g., a room in the Bay Area) and virtual (IRC/iChat) participants.<br />
<br />
==== Goals ====<br />
# Improve understanding of what needs to be done for Wiki<br />
#* IMHO - this should be done here, in [[to-do]] incrementally. -Tantek<br />
# Tackle larger projects (~1-2 hours) than people usually have time for<br />
#* I'd like to see these projects *documented* first on [[to-do]] before we spend 1-2 hours of a bunch of folk's collective time to go through them. -Tantek<br />
# Motivate community to have fun with otherwise tedious "housecleaning" chores<br />
<br />
==== Agenda (Wishlist) ====<br />
In parallel:<br />
* Coalesce/prioritize existing To-Do items (above)<br />
* Review/revise desired pathways for:<br />
** New users learning about microformats<br />
*** e.g., intro, about, explore, tutorials, etc.<br />
*** cf. [http://www.rubyonrails.com/ Rails] front page<br />
****Get Excited (Why, background, motivation)<br />
****Get Started (What, downloads, getting started)<br />
****Get Better (How, tutorials, )<br />
****Get Involved (Who)<br />
** Microformat lifecycle<br />
*** e.g., research->brainstorm->proposal->spec->maintain<br />
*** see http://theryanking.com/microformats/method.txt --[[User:RyanKing|RyanKing]] 15:35, 22 Feb 2006 (PST)<br />
*** ensure information easy to find, follow, and up-to-date<br />
* Review existing specs for completeness and consistency<br />
* Identify areas of 'bitrot' or 'hole-filling'<br />
* Do it!<br />
<br />
== New Person 2 ==<br />
<br />
etc.</div>Mark Mansourhttp://microformats.org/wiki/index.php?title=events/2006-03-07-etech-microformats&diff=5296events/2006-03-07-etech-microformats2006-03-01T09:56:29Z<p>Mark Mansour: update to ETech schedule with location fix and example page.</p>
<hr />
<div><h1>Microformats panel at O'Reilly ETech</h1><br />
<br />
One of several microformats [[events]].<br />
<br />
During [http://conferences.oreillynet.com/et2006/ O'Reilly's ETech 2006] conference, there will be a [http://conferences.oreillynet.com/cs/et2006/view/e_sess/8292 Microformats presentation] consisting of a short intro/overview by Tantek, and then a series of lightning demonstrations.<br />
<br />
Presenters, please see To Do section.<br />
__TOC__<br />
== Session Details ==<br />
* What: Microformats<br />
* Who (confirmed presenters): Tantek Çelik, Rohit Khare, Kevin Marks, Mark Pilgrim<br />
* When: Tuesday March 7th, 5:30pm - 6:15pm<br />
* Where: Elizabeth Ballroom A, Manchester Grand Hyatt, San Diego, CA<br />
<br />
== Attending ==<br />
Please add your name here if you are attending ETech (whether you are speaking or not), alphabetically sorted by last name. Consider adding yourself to the [http://wiki.oreillynet.com/etech06/index.cgi?RideSharing RideSharing page] as well to coordinate sharing rides/taxis to/from the airport.<br />
* Tantek Çelik<br />
* Ali Diab<br />
* Yoz Grahame<br />
* Joe Gregorio<br />
* Ian Kallen<br />
* Rohit Khare<br />
* Kevin Marks<br />
* Chris Messina<br />
* Mark Pilgrim<br />
* David Sifry<br />
* ...<br />
<br />
== To Do ==<br />
Please check the to do list to see if you can help out.<br />
* '''ASAP: Anybody with who can help''' add [[hcalendar|hCalendar]] and [[hcard|hCard]] markup to the ETech speakers and schedule pages. Email the result to O'Reilly so they can update the pages. Host the marked up version on your own site in the meantime, and for redundancy's sake.<br />
** [http://conferences.oreillynet.com/pub/w/43/program.html ETech schedule], [http://conferences.oreillynet.com/pub/w/43/tutorials.html tutorials], [http://conferences.oreillynet.com/pub/w/43/sessions.html sessions], [http://conferences.oreillynet.com/pub/w/43/events.html events], [http://conferences.oreillynet.com/pub/w/43/bof.html BoF] pages<br />
*** They've put some hCalendar in already! <br />
*** Needs fixes to ISO8601 Dates. <br />
**** 2006036 should be 20060306 etc.<br />
**** All ISO8601 dates need timezone offset (-0800) appended to them.<br />
*** Locations need to be fixed. Should be in the form (a full version is here: <http://lifelint.com/test/program.html>)<br />
<pre><span style='font-weight:bold;'>Location: </span><span class='location'>Elizabeth Ballroom A</span></pre><br />
*** Needs hCard markup for speaker names/URLs in session schedule.<br />
** Need hCards on (feel free to put you name next to one to claim it and start working on it) <br />
*** [http://conferences.oreillynet.com/pub/w/43/see_do.html see and do]<br />
*** [http://conferences.oreillynet.com/pub/w/43/sponsors.html sponsors]<br />
*** [http://conferences.oreillynet.com/pub/w/43/speakers.html speakers (which is missing some people, Tantek Çelik)]<br />
** Need to send to O'Reilly folks so they can look at the diffs and update their pages <br />
*** [http://conferences.oreillynet.com/pub/w/43/invite.html invitation] (see [http://rbach.priv.at/repos/misc/microformatting/ETech2006/invite.html invite.html updated by RobertBachmann], reviewed/tested/confirmed by Tantek)<br />
*** [http://conferences.oreillynet.com/pub/w/43/register.html registration] (see [http://rbach.priv.at/repos/misc/microformatting/ETech2006/register.html register.html by RobertBachmann], reviewed/tested by Tantek. Notes: two "O'Reilly Media" hCards = two vCards = two address book entries, may need to implement merging at some point in X2V, perhaps a good point for discussion.) <br />
*** [http://conferences.oreillynet.com/pub/w/43/hotel.html hotel/travel] (See [http://rbach.priv.at/repos/misc/microformatting/ETech2006/hotel.html hotel.html by Robert Bachmann])<br />
*** [http://conferences.oreillynet.com/pub/w/43/exhibitors.html exhibitors] (See [http://rbach.priv.at/repos/misc/microformatting/ETech2006/exhibitors.html exhibitors.html by Robert Bachmann])<br />
<br />
* All lightning demonstrations should confirm that demonstrations are done, ready, practiced, and timed to complete within 5 minutes. Link to them from here as soon as possible (even drafts) so we can all review and see where everyone is at.<br />
** Tantek Çelik: working on slides, demo script for hCard and hCalendar import to Apple Address Book and Apple iCal calendaring application.<br />
** Kevin Marks (Tags demo): status unknown<br />
** Rohit Khare (Ångstro demo): status unknown<br />
** Mark Pilgrim (Magicline demo): status unknown<br />
** Yoz Grahame (Ning demo)<br />
** demo slot 5<br />
** demo slot 6<br />
<br />
== Short Summary ==<br />
<br />
This is simply a direct quote from http://conferences.oreillynet.com/cs/et2006/view/e_sess/8292 :<br />
<br />
* Microformats<br />
* Tantek Çelik, Technorati, Rohit Khare, CommerceNet Labs, Mark Pilgrim, IBM<br />
* Date: Tuesday, March 07<br />
* Time: 5:30pm - 6:15pm<br />
* Location: Elizabeth Ballroom A<br />
<br />
Microformats are simple semantic XHTML extensions for expressing numerous common concepts (people, events, etc.) on today's Web. Tantek Çelik will provide a short introduction, followed by a series of speakers performing lightning demonstrations of their microformats enabled tools, sites, hacks and other implementations.<br />
<br />
== Lightning Demonstrations ==<br />
<br />
Note about the lightning demonstrations. All demonstrations MUST:<br />
* '''Use or produce content published in one or more microformats'''. I suppose that should be obvious. ;)<br />
* '''Be completed in 5 minutes''' from start to finish, ''including'' setup time. We are working under strict time constraints, and thus I must cut-off demonstrations at the 5 minute mark so that we have time for the remaining demonstrations. If your demonstration stalls or appears to not work, we will move onto the next demo and if we have time, may come back, so be sure you have practiced your demo and are sure it will work (you can assume presence of a network, but being able to also run locally is a good thing).<br />
* '''Demonstrate end user benefit.''' Showing the code that makes it behind the scenes and discussing the microformats used briefly is good, but strictly ''secondary'' to showing something working with actual microformat content.<br />
<br />
== Proposed Demonstrations ==<br />
<br />
I have deliberately kept a few of the demonstration slots open for new/latecomers/implementers to be able to demonstrate their cool microformat implementations. If you have a useful and dazzling microformat implementation that you can successfully explain and demonstrate in 5 minutes please add your name, and brief explanation of what you plan to demonstrate, and we'll see if we can fit folks in. Some of the criteria to help decide will include:<br />
* Does the demo run *today*? (2006-02-19)<br />
* Does it demonstrate a microformat not currently being demonstrated by the other demos? E.g. one or more of:<br />
** [[xfolk|xFolk]]<br />
** [[hreview|hReview]] (perhaps [http://judysbook.com Judy's Book])<br />
** [[hresume|hResume]] (SimplyHired if they can get it working in time)<br />
** [[hlisting-proposal|hListing]] (Oodle, and perhaps Edgeio if they can get it working)<br />
<br />
Proposed lightning demos:<br />
<br />
* Name, Company, title/summary, URL to working demo/download<br />
* ...<br />
* ...<br />
* ...<br />
* ...<br />
* ...<br />
<br />
<br />
== Longer Session Description ==<br />
<br />
I am working on this here, and will submit to O'Reilly to update on the page for the session: http://conferences.oreillynet.com/cs/et2006/view/e_sess/8292<br />
<br />
- Tantek<br />
<br />
* Microformats<br />
* Tantek Çelik, Technorati<br />
* Yoz Grahame, Ning<br />
* Rohit Khare, CommerceNet<br />
* Kevin Marks, Technorati<br />
* Mark Pilgrim, IBM<br />
* Date: Tuesday, March 07<br />
* Time: 5:30pm - 6:15pm<br />
* Location: Elizabeth Ballroom A<br />
<br />
Microformats are simple semantic XHTML extensions for expressing numerous common concepts (people, events, etc.) on today's Web. Tantek Çelik will provide a short introduction, followed by a series of speakers performing lightning demonstrations of their microformats enabled tools, sites, hacks and other implementations.</div>Mark Mansourhttp://microformats.org/wiki/index.php?title=hcalendar-irc-meetup-20060225&diff=5222hcalendar-irc-meetup-200602252006-02-25T06:43:44Z<p>Mark Mansour: </p>
<hr />
<div>= Attendees =<br />
* Mark Mansour<br />
* Brian Suda<br />
* Kevin Marks<br />
* Ryan King<br />
<br />
= Source =<br />
The [http://rbach.priv.at/Microformats-IRC/2006-02-25 hcalendar irc meetup on 20060225] attempted to solve the [http://microformats.org/wiki/hcalendar-issues issues listed on 2006-02-17].<br />
<br />
= hCalendar tests =<br />
The LifeLint hCalendar tests are to be donated to microformats.org. [[RyanKing]] will move these over to a subversion server at microformats.org. No time was given for when these tests would be available at microformats.org.<br />
<br />
= The worth of a vcalendar class =<br />
* vcalendar class allows multiple calendars to appear on the one web page<br />
** this is not being done in the wild<br />
* vcalendar class allows items to be added to a calendar object<br />
** there are four properties on a calendar which are PRODID, VERSION, METHOD, CALSCALE. VERSION is always 2.0 and does not look likely to change. PRODID tells us who made the calendar, but if it gets transformed a new PRODID will be added - i.e. it gets overridden. CALSCALE value is GREGORIAN as is the whole ical spec - there would have to be massive changes for this to be a different value. The METHOD property is disucced in more detail in [http://www.ietf.org/rfc/rfc2446.txt iTIP] and defines the possible values. It appears that calendar user agents ignore this anyway. NOTE: If producing an ICS for consumption by Outlook, then the METHOD property must be set. <br />
<br />
Therefore:<br />
* the vcalendar class is not needed and it can be assumed that if a vevent is found on a page, then it is part of a hCalendar.<br />
* when producing ICS files, the METHOD property on the VCALENDAR should be set to PUBLISH.<br />
** The PUBLISH value seems to be the most suitable value as it works for all component types and posting information to a web page is equivalent to publishing a calendar.<br />
<br />
= Axis/Header layout of calendar data =<br />
* There are no examples in the wild. [[RyanKing]] and [http://suda.co.uk/ Brian Suda] have examples which they are going to make public. <br />
<br />
= Components =<br />
* The components defined by ical are VEVENT, VTODO, VALARM, VFREEBUSY, VJOURNAL and VTIMEZONE. <br />
* There are two places that components can exist, either as "components" or "subcomponents"<br />
** components live directly inside a calendar -> VEVENT, VTODO, VFREEBUSY, VJOURNAL and VTIMEZONE<br />
*** VTIMEZONE has been removed from ical-basic draft 04 so should probably be removed from hCalendar<br />
*** the value of VJOURNAL has been questioned by [[RyanKing]] since since hAtom probably serves the same purpose.<br />
*** VEVENT are currently allowed and are used in the wild<br />
*** VALARMs may not appear at the same level as events (line 2864 of ical)<br />
*** need to work out if VTODO, VFREEBUSY are worth having.<br />
** subcomponents live within other components -> VALARM<br />
*** VALARMs must be nested inside VEVENTs or VTODOs. (line 3912 of ical)<br />
*** hCalendar does not support these at the moment<br />
<br />
Followup:<br />
* find VTODOs, VFREEBUSYs and VALARMs in the wild<br />
<br />
= Fragments =<br />
* As both [[RyanKing]] and [http://suda.co.uk/ Brian Suda] point out, the [http://svn.lifelint.com/hcalendar_tests/calendar-fragment.xml fragment hCalendar test] are wrong because:<br />
** The [http://www.w3.org/TR/xhtml1/#C_8 XHTML spec] defines fragments to use the id attribute and the test was using the name attribute<br />
** The child elements of a fragment should be inspected to determine values.</div>Mark Mansourhttp://microformats.org/wiki/index.php?title=hcalendar-issues&diff=5213hcalendar-issues2006-02-25T05:43:09Z<p>Mark Mansour: </p>
<hr />
<div>= hCalendar Issues =<br />
<br />
These are externally raised issues about [[hcalendar|hCalendar]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec. Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/log/ Tantek]<br />
<br />
See related [[hcard-issues]].<br />
<br />
== Issues ==<br />
<br />
Please use this format:<br />
* YYYY-MM-DD raised by AUTHORNAME<br />
*# ''Issue 1: Here is the first issue I have.''<br />
*# ''Issue 2: Here is the second issue I have.''<br />
<br />
And add new issues to the top of the list:<br />
<br />
* 2006-02-17 raised by [[User:Mark Mansour|Mark Mansour]] - notes are summarized [[hcalendar-irc-meetup-20060225|here]]<br />
*# should vcalendar be a class? Section 4.4 of RFC2445 says: "The Calendaring and Scheduling Core Object is a collection of calendaring and scheduling information. Typically, this information will consist of a single iCalendar object. However, multiple iCalendar objects can be sequentially grouped together." Also the hcalendar class would allow properties on the calendar itself such as METHOD and CALSCALE (I don't think VERSION and PRODID are particularly relevant).<br />
*# how are axis and headers going to be handled? There has been talk that table axis and headers should be used to capture calendar information in a more compact format, but no example are available. Does anyone have examples or should we try to invent some?<br />
*# should embeded components be allowed? [[RyanKing]] has already noted that vJournal overlaps blog-posts (although not yet accepted), but should the components to-do, free/busy, timezone, alarms be allowed? They all considered as just as relevant by the ical spec as events are (my interpretation).<br />
*# validation of the hCalendar tests. The hCalendar tests have been available for a while now, but only Brian Suda and I have made contributions to their content. Does anyone else have thoughts and should we try to make these the beginning of 'official' hCalendar tests?<br />
*# The use of fragments is unclear. Fragment interpretation seems to be agent dependant. Fragments usually denote a heading or marker, like a goto statement for HTML. Unfortunately it may jump in the middle of elements (rather to the beginning of an element). How should this be handled. i.e. <br />
<pre><br />
<a name="myfrag">heading</a><br />
<div class="vevent"><br />
<div class="description">A nice event</div><br />
<abbr class="dtstart" title="2005-10-05">October 5</abbr><br />
</div><br />
</pre><br />
* 2006-02-01 raised by [[RyanKing]]<br />
*# ''Issue 1: Given that now, or soon will have hAtom, should we disallow vJournal, so that we don't have 2 blog-post formats?''<br />
* 2006-01-04 raised by [[User:CGranade|CGranade]]<br />
*# ''Interactions with strong namespacing. So far, it seems that hCalendar cannot be embedded into non-XHTML schemas that are also strongly namespaced (e.g.: RDF, Atom) without a resultant validation error, as the <code>class</code> attribute is ''not'' portable across schemas.''<br />
*#* REJECTED. The class attribute is used on XHTML elements, which are XML, which can be embedded in any other XML. The issue as raised doesn't make sense.<br />
*# ''All examples in XHTML. XHTML should not be the only host to microformats, and thus it should not be the only example host language. Rather, examples in Atom, RSS, RDF, etc. should also be provided.''<br />
*#* ACCEPTED. This is definitely something to be added to *-examples pages for each microformat.<br />
* 2005-10-14 raised by [[User:MarkoMrdjenovic|MarkoMrdjenovic]]<br />
*# ''UID has to be present in iCal events if they want to be used in Microsoft Outlook. [Suggestion:] it should probably be added to the vevent tag as html attribute id. There is also the problem of converters - x2v has UID commented out. [http://www.ietf.org/rfc/rfc2445.txt RFC] recommends use of addr format for uids which is problematic in html id (does not validate). [[User:HenriBergius|HenriBergius]] pointed out some calendaring software crashes when @ is in the UID, so some other form of identification should be used - along the lines of dtstart-dtend-hash(title,summary)-sample-org''<br />
*#* ACCEPTED-PARTIAL. Yes, it appears RFC2445 requires UID. However, typical mentions of events by web authors do not provide anything equivalent to a UID, nor should we require authors to do so. Thus we must come up with an algorithm for implied UID, similar to some of the other properties. We REJECT the use of the html 'id' attributre as a substitute for UID as they are of different scopes and thus such a translation will likely be problematic. As part of this algorithm, we MUST disallow "@" signs since the issue points out that such UIDs crash some calendaring software.<br />
*# ''DTSTAMP also has to be present in iCal event for Microsoft Outlook. I think DTSTAMP should be user visible information so implementation with class="dtstamp" is fine. x2v already supports it so it should just be added to the standard and examples. The converters might also think of a way to force (create) dtstamp if it's not present.''<br />
*#* ACCEPTED. We should come up with a way to encourage/synthesize/imply DTSTAMP property values.<br />
*# ''Here is an example from Midgard CMS (which will be easy to change according to bergie on irc):''<br />
*#* For more discussion of this, please see [http://microformats.org/wiki/hcalendar-brainstorming#UID_handling hCalendar brainstorming: UID handling]<br />
<pre><nowiki><br />
<li class="vevent" id="2678c3f94af4a49f9ccbb69b92a82aba-midgardGuid"><br />
<abbr class="dtstart" title="2005-10-20T14:34:45Z">Torstai 20. Lokakuu 17:34</abbr> -<br />
<abbr class="dtend" title="2005-10-20T15:33:56Z">18:33</abbr><br />
<a class="url" href="/bergie/another-calendar/82457028ba83407451edd8aaeaa40622.html"><br />
<span class="summary">From the other cal</span><br />
</a><br />
<abbr class="dtstamp" title="2005-10-14T12:16:45Z">Torstai 14. Lokakuu 12:16</abbr><br />
</li></nowiki></pre><br />
* 2005-09-29 raised by RyanKing<br />
*# ''How does one use ATTENDEE?''<br />
* 2005-07-27 raised by Paolo Massa<br />
*# ''I tried to add a hcalendar event in my blog but it rendered orribly. The problem was I already have a 'class="summary' in my normal HTML (it is the title of the posts) and my CSS displays it bigger and bold. In this way the summary of the event was as big as the titles of the posts, destroying readability. The problem is Overloading of class attributes, it might be the case that a blogger already use, for example, class="summary" for different purposes. What can be a solution? Providing in every microformat wiki page a CSS file that users can download and insert in their blog as additional CSS. This CSS file will "shield" attribute "inside" microformats from being interpreted as "normal" attributes. For example for the hCalendar microformats the relative CSS could be something like:<br />
<br />
.vevent .summary {<br />
<br />
//remove all the previously set properties, for example:<br />
<br />
text-decoration: none;<br />
<br />
font-size: 100%;<br />
<br />
...<br />
<br />
}<br />
<br />
Since the hCalendar microformat is the following,<br />
<br />
<span class="vevent"><br />
<br />
<a class="url" href="http://www.web2con.com/"><br />
<br />
<span class="summary">Web 2.0 Conference</span>:<br />
<br />
...<br />
<br />
I hope to have been clear but I'm not so sure ;-)''<br />
<br />
<br />
* 2005-07-21 raised by Neil Jensen <br />
*# ''should we create a vfreebusy class for HTML representations of freebusy data? Discussion [http://microformats.org/wiki/hcalendar-brainstorming#Free.2FBusy_information on hCalendar brainstorming]. Additional background: [http://www.ifreebusy.com/cyclical/blog/calendar/3.html here].''<br />
<br />
* 2005-07-11 raised by Kragen<br />
*# ''The specification of class="url" as &lt;a href="..."> should be a "should", not a "must". Other ways of referencing the event URL, such as &lt;iframe src="..."> and &lt;embed src="...">, shoul be mentioned. At present X2V doesn't appear to handle them. This came up in a discussion about [[xfolk|xFolk]].''<br />
<br />
* 2005-06-21 raised by Hixie<br />
*# ''Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how hCalendars must be parsed, how to handle errors, and so forth. Is it defined in terms of the DOM? Is it defined in terms of a serialisation? How do you handle unexpected content or missing content?<br />
<br />
* 2005-02-22 raised by Matt Raymond [http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2005-February/003124.html on the whatwg list]:<br />
*# ''There is no copyright statement and no patent statement.''<br />
*#* ACCEPTED. I have updated [[hcalendar]] (and [[hcard]], and all other MicroFormats) with a standard copyright statement and patent statement.<br />
<br />
* 2005-02-18 raised by Matt Raymond [http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2005-February/003116.html on the whatwg list]:<br />
*# ''There is no way for some reading the markup to tell if a class name is the name of an attribute or simply the name of a class used for styling.''<br />
*#* REJECTED (strawman, poor assumption). There is no need to differentiate in the general case. In the specific case, a vocabulary is defined within a context.<br />
*# ''As a result of the above, user agents would not be able to reliably allow users to access extension properties such as "x-mozilla-alarm-default-length" (which is an actual extension used in Sunbird).''<br />
*#* REJECTED (out of scope). Extension properties are outside the current scope of hCalendar.<br />
*# ''The use of <abbr> for dates is incorrect. "August 5th, 2004" is not the abbreviation of 2004-09-05. In fact, the opposite is closer to the truth.''<br />
*#* REJECTED (false statement). This is simply a false statement. See this article for an explanation of this use of <abbr>: [http://tantek.com/log/2005/01.html#d26t0100 Human vs. ISO8601 dates problem solved]<br />
*# ''You have to create a complex set of rules for all possible uses of legacy markup within <span class="vcalendar"> which can easily be implemented incorrectly.''<br />
*#* REJECTED (false statements, strawman). There is no legacy markup. There is no need to create rules for all possible uses of legacy markup. There is no need to create a complex set of rules.<br />
*# ''There are styling and tooltip issues that are unresolved.''<br />
*#* REJECTED (empty statements). See the [[hcalendar-faq|hCalendar FAQ]] for answers to specific styling and tooltip questions. Otherwise, please raise specific issues here with clear valid examples.<br />
*# ''hCalendar/hCard is more complicated for webmasters to read and understand and more complicated for developers to implement.''<br />
*#* REJECTED (empty statements, invalid comparator). Please state specific examples which show the perceived complexity. The comparison "more complicated" requires two items, no second item was provided.<br />
*# ''I dislike the entire system of using class names as markup. Class names should be reserved for user-defined semantics.''<br />
*#* ACCEPT-PARTIAL. When specific elements are available, they should be used instead of class names, but even then class names work well to "subclass" specific elements. This is thoroughly discussed in the essay [http://tantek.com/log/2002/12.html#L20021216 A Touch of Class]. And yes, class names can and should be used for user-defined semantics. [[hcalendar|hCalendar]] is one such user, and it is reasonable for users to use each others class names.<br />
*#* ''Would it be more in the spirit of HTML to define these classes in a [http://www.w3.org/TR/html401/struct/global.html#h-7.4.4.3 metadata profile], so that "User agents may... perform some activity based on known conventions for that profile"? Should this be a part of [[microformats]] specifications in general? (If not, why not?)''<br />
*#** ACCEPTED. Yes, all [[microformats]] that introduce new classnames SHOULD include an [http://gmpg.org/xmdp/ XMDP] profile (which itself is a microformat for defining HTML metadata profiles) that defines those classnames.<br />
*#*** ''Ok, but in order to refer to a profile, it needs a URI. Tantek writes in [http://microformats.org/discuss/mail/microformats-discuss/2005-July/000407.html a message of Jul 21] "This is precisely the reason that GMPG was founded and created, to provide permanent URLs/homes for microformat profiles." How does one cause GMPG to issue a profile URL?''<br />
*#**** ACCEPTED. This is on Tantek's [[to-do]] list, to both provide profiles and URLs (probably at gmpg.org) for those profiles for hCalendar etc.</div>Mark Mansourhttp://microformats.org/wiki/index.php?title=hcalendar-issues&diff=5161hcalendar-issues2006-02-25T04:09:09Z<p>Mark Mansour: </p>
<hr />
<div>= hCalendar Issues =<br />
<br />
These are externally raised issues about [[hcalendar|hCalendar]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec. Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/log/ Tantek]<br />
<br />
See related [[hcard-issues]].<br />
<br />
== Issues ==<br />
<br />
Please use this format:<br />
* YYYY-MM-DD raised by AUTHORNAME<br />
*# ''Issue 1: Here is the first issue I have.''<br />
*# ''Issue 2: Here is the second issue I have.''<br />
<br />
And add new issues to the top of the list:<br />
<br />
* 2006-02-17 raised by [[User:Mark Mansour|Mark Mansour]]<br />
*# should vcalendar be a class? Section 4.4 of RFC2445 says: "The Calendaring and Scheduling Core Object is a collection of calendaring and scheduling information. Typically, this information will consist of a single iCalendar object. However, multiple iCalendar objects can be sequentially grouped together." Also the hcalendar class would allow properties on the calendar itself such as METHOD and CALSCALE (I don't think VERSION and PRODID are particularly relevant).<br />
*# how are axis and headers going to be handled? There has been talk that table axis and headers should be used to capture calendar information in a more compact format, but no example are available. Does anyone have examples or should we try to invent some?<br />
*# should embeded components be allowed? [[RyanKing]] has already noted that vJournal overlaps blog-posts (although not yet accepted), but should the components to-do, free/busy, timezone, alarms be allowed? They all considered as just as relevant by the ical spec as events are (my interpretation).<br />
*# validation of the hCalendar tests. The hCalendar tests have been available for a while now, but only Brian Suda and I have made contributions to their content. Does anyone else have thoughts and should we try to make these the beginning of 'official' hCalendar tests?<br />
*# The use of fragments is unclear. Fragment interpretation seems to be agent dependant. Fragments usually denote a heading or marker, like a goto statement for HTML. Unfortunately it may jump in the middle of elements (rather to the beginning of an element). How should this be handled. i.e. <br />
<pre><br />
<a name="myfrag">heading</a><br />
<div class="vevent"><br />
<div class="description">A nice event</div><br />
<abbr class="dtstart" title="2005-10-05">October 5</abbr><br />
</div><br />
</pre><br />
* 2006-02-01 raised by [[RyanKing]]<br />
*# ''Issue 1: Given that now, or soon will have hAtom, should we disallow vJournal, so that we don't have 2 blog-post formats?''<br />
* 2006-01-04 raised by [[User:CGranade|CGranade]]<br />
*# ''Interactions with strong namespacing. So far, it seems that hCalendar cannot be embedded into non-XHTML schemas that are also strongly namespaced (e.g.: RDF, Atom) without a resultant validation error, as the <code>class</code> attribute is ''not'' portable across schemas.''<br />
*#* REJECTED. The class attribute is used on XHTML elements, which are XML, which can be embedded in any other XML. The issue as raised doesn't make sense.<br />
*# ''All examples in XHTML. XHTML should not be the only host to microformats, and thus it should not be the only example host language. Rather, examples in Atom, RSS, RDF, etc. should also be provided.''<br />
*#* ACCEPTED. This is definitely something to be added to *-examples pages for each microformat.<br />
* 2005-10-14 raised by [[User:MarkoMrdjenovic|MarkoMrdjenovic]]<br />
*# ''UID has to be present in iCal events if they want to be used in Microsoft Outlook. [Suggestion:] it should probably be added to the vevent tag as html attribute id. There is also the problem of converters - x2v has UID commented out. [http://www.ietf.org/rfc/rfc2445.txt RFC] recommends use of addr format for uids which is problematic in html id (does not validate). [[User:HenriBergius|HenriBergius]] pointed out some calendaring software crashes when @ is in the UID, so some other form of identification should be used - along the lines of dtstart-dtend-hash(title,summary)-sample-org''<br />
*#* ACCEPTED-PARTIAL. Yes, it appears RFC2445 requires UID. However, typical mentions of events by web authors do not provide anything equivalent to a UID, nor should we require authors to do so. Thus we must come up with an algorithm for implied UID, similar to some of the other properties. We REJECT the use of the html 'id' attributre as a substitute for UID as they are of different scopes and thus such a translation will likely be problematic. As part of this algorithm, we MUST disallow "@" signs since the issue points out that such UIDs crash some calendaring software.<br />
*# ''DTSTAMP also has to be present in iCal event for Microsoft Outlook. I think DTSTAMP should be user visible information so implementation with class="dtstamp" is fine. x2v already supports it so it should just be added to the standard and examples. The converters might also think of a way to force (create) dtstamp if it's not present.''<br />
*#* ACCEPTED. We should come up with a way to encourage/synthesize/imply DTSTAMP property values.<br />
*# ''Here is an example from Midgard CMS (which will be easy to change according to bergie on irc):''<br />
*#* For more discussion of this, please see [http://microformats.org/wiki/hcalendar-brainstorming#UID_handling hCalendar brainstorming: UID handling]<br />
<pre><nowiki><br />
<li class="vevent" id="2678c3f94af4a49f9ccbb69b92a82aba-midgardGuid"><br />
<abbr class="dtstart" title="2005-10-20T14:34:45Z">Torstai 20. Lokakuu 17:34</abbr> -<br />
<abbr class="dtend" title="2005-10-20T15:33:56Z">18:33</abbr><br />
<a class="url" href="/bergie/another-calendar/82457028ba83407451edd8aaeaa40622.html"><br />
<span class="summary">From the other cal</span><br />
</a><br />
<abbr class="dtstamp" title="2005-10-14T12:16:45Z">Torstai 14. Lokakuu 12:16</abbr><br />
</li></nowiki></pre><br />
* 2005-09-29 raised by RyanKing<br />
*# ''How does one use ATTENDEE?''<br />
* 2005-07-27 raised by Paolo Massa<br />
*# ''I tried to add a hcalendar event in my blog but it rendered orribly. The problem was I already have a 'class="summary' in my normal HTML (it is the title of the posts) and my CSS displays it bigger and bold. In this way the summary of the event was as big as the titles of the posts, destroying readability. The problem is Overloading of class attributes, it might be the case that a blogger already use, for example, class="summary" for different purposes. What can be a solution? Providing in every microformat wiki page a CSS file that users can download and insert in their blog as additional CSS. This CSS file will "shield" attribute "inside" microformats from being interpreted as "normal" attributes. For example for the hCalendar microformats the relative CSS could be something like:<br />
<br />
.vevent .summary {<br />
<br />
//remove all the previously set properties, for example:<br />
<br />
text-decoration: none;<br />
<br />
font-size: 100%;<br />
<br />
...<br />
<br />
}<br />
<br />
Since the hCalendar microformat is the following,<br />
<br />
<span class="vevent"><br />
<br />
<a class="url" href="http://www.web2con.com/"><br />
<br />
<span class="summary">Web 2.0 Conference</span>:<br />
<br />
...<br />
<br />
I hope to have been clear but I'm not so sure ;-)''<br />
<br />
<br />
* 2005-07-21 raised by Neil Jensen <br />
*# ''should we create a vfreebusy class for HTML representations of freebusy data? Discussion [http://microformats.org/wiki/hcalendar-brainstorming#Free.2FBusy_information on hCalendar brainstorming]. Additional background: [http://www.ifreebusy.com/cyclical/blog/calendar/3.html here].''<br />
<br />
* 2005-07-11 raised by Kragen<br />
*# ''The specification of class="url" as &lt;a href="..."> should be a "should", not a "must". Other ways of referencing the event URL, such as &lt;iframe src="..."> and &lt;embed src="...">, shoul be mentioned. At present X2V doesn't appear to handle them. This came up in a discussion about [[xfolk|xFolk]].''<br />
<br />
* 2005-06-21 raised by Hixie<br />
*# ''Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how hCalendars must be parsed, how to handle errors, and so forth. Is it defined in terms of the DOM? Is it defined in terms of a serialisation? How do you handle unexpected content or missing content?<br />
<br />
* 2005-02-22 raised by Matt Raymond [http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2005-February/003124.html on the whatwg list]:<br />
*# ''There is no copyright statement and no patent statement.''<br />
*#* ACCEPTED. I have updated [[hcalendar]] (and [[hcard]], and all other MicroFormats) with a standard copyright statement and patent statement.<br />
<br />
* 2005-02-18 raised by Matt Raymond [http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2005-February/003116.html on the whatwg list]:<br />
*# ''There is no way for some reading the markup to tell if a class name is the name of an attribute or simply the name of a class used for styling.''<br />
*#* REJECTED (strawman, poor assumption). There is no need to differentiate in the general case. In the specific case, a vocabulary is defined within a context.<br />
*# ''As a result of the above, user agents would not be able to reliably allow users to access extension properties such as "x-mozilla-alarm-default-length" (which is an actual extension used in Sunbird).''<br />
*#* REJECTED (out of scope). Extension properties are outside the current scope of hCalendar.<br />
*# ''The use of <abbr> for dates is incorrect. "August 5th, 2004" is not the abbreviation of 2004-09-05. In fact, the opposite is closer to the truth.''<br />
*#* REJECTED (false statement). This is simply a false statement. See this article for an explanation of this use of <abbr>: [http://tantek.com/log/2005/01.html#d26t0100 Human vs. ISO8601 dates problem solved]<br />
*# ''You have to create a complex set of rules for all possible uses of legacy markup within <span class="vcalendar"> which can easily be implemented incorrectly.''<br />
*#* REJECTED (false statements, strawman). There is no legacy markup. There is no need to create rules for all possible uses of legacy markup. There is no need to create a complex set of rules.<br />
*# ''There are styling and tooltip issues that are unresolved.''<br />
*#* REJECTED (empty statements). See the [[hcalendar-faq|hCalendar FAQ]] for answers to specific styling and tooltip questions. Otherwise, please raise specific issues here with clear valid examples.<br />
*# ''hCalendar/hCard is more complicated for webmasters to read and understand and more complicated for developers to implement.''<br />
*#* REJECTED (empty statements, invalid comparator). Please state specific examples which show the perceived complexity. The comparison "more complicated" requires two items, no second item was provided.<br />
*# ''I dislike the entire system of using class names as markup. Class names should be reserved for user-defined semantics.''<br />
*#* ACCEPT-PARTIAL. When specific elements are available, they should be used instead of class names, but even then class names work well to "subclass" specific elements. This is thoroughly discussed in the essay [http://tantek.com/log/2002/12.html#L20021216 A Touch of Class]. And yes, class names can and should be used for user-defined semantics. [[hcalendar|hCalendar]] is one such user, and it is reasonable for users to use each others class names.<br />
*#* ''Would it be more in the spirit of HTML to define these classes in a [http://www.w3.org/TR/html401/struct/global.html#h-7.4.4.3 metadata profile], so that "User agents may... perform some activity based on known conventions for that profile"? Should this be a part of [[microformats]] specifications in general? (If not, why not?)''<br />
*#** ACCEPTED. Yes, all [[microformats]] that introduce new classnames SHOULD include an [http://gmpg.org/xmdp/ XMDP] profile (which itself is a microformat for defining HTML metadata profiles) that defines those classnames.<br />
*#*** ''Ok, but in order to refer to a profile, it needs a URI. Tantek writes in [http://microformats.org/discuss/mail/microformats-discuss/2005-July/000407.html a message of Jul 21] "This is precisely the reason that GMPG was founded and created, to provide permanent URLs/homes for microformat profiles." How does one cause GMPG to issue a profile URL?''<br />
*#**** ACCEPTED. This is on Tantek's [[to-do]] list, to both provide profiles and URLs (probably at gmpg.org) for those profiles for hCalendar etc.</div>Mark Mansourhttp://microformats.org/wiki/index.php?title=hcalendar-issues&diff=5160hcalendar-issues2006-02-25T01:11:16Z<p>Mark Mansour: </p>
<hr />
<div>= hCalendar Issues =<br />
<br />
These are externally raised issues about [[hcalendar|hCalendar]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec. Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/log/ Tantek]<br />
<br />
See related [[hcard-issues]].<br />
<br />
== Issues ==<br />
<br />
Please use this format:<br />
* YYYY-MM-DD raised by AUTHORNAME<br />
*# ''Issue 1: Here is the first issue I have.''<br />
*# ''Issue 2: Here is the second issue I have.''<br />
<br />
And add new issues to the top of the list:<br />
<br />
* 2006-02-17 raised by [[Mark Mansour]]<br />
*# should vcalendar be a class? Section 4.4 of RFC2445 says: "The Calendaring and Scheduling Core Object is a collection of calendaring and scheduling information. Typically, this information will consist of a single iCalendar object. However, multiple iCalendar objects can be sequentially grouped together." Also the hcalendar class would allow properties on the calendar itself such as METHOD and CALSCALE (I don't think VERSION and PRODID are particularly relevant).<br />
*# how are axis and headers going to be handled? There has been talk that table axis and headers should be used to capture calendar information in a more compact format, but no example are available. Does anyone have examples or should we try to invent some?<br />
*# should embeded components be allowed? [[RyanKing]] has already noted that vJournal overlaps blog-posts (although not yet accepted), but should the components to-do, free/busy, timezone, alarms be allowed? They all considered as just as relevant by the ical spec as events are (my interpretation).<br />
*# validation of the hCalendar tests. The hCalendar tests have been available for a while now, but only Brian Suda and I have made contributions to their content. Does anyone else have thoughts and should we try to make these the beginning of 'official' hCalendar tests?<br />
*# The use of fragments is unclear. Fragment interpretation seems to be agent dependant. Fragments usually denote a heading or marker, like a goto statement for HTML. Unfortunately it may jump in the middle of elements (rather to the beginning of an element). How should this be handled. i.e. <br />
<pre><br />
<a name="myfrag">heading</a><br />
<div class="vevent"><br />
<div class="description">A nice event</div><br />
<abbr class="dtstart" title="2005-10-05">October 5</abbr><br />
</div><br />
</pre><br />
* 2006-02-01 raised by [[RyanKing]]<br />
*# ''Issue 1: Given that now, or soon will have hAtom, should we disallow vJournal, so that we don't have 2 blog-post formats?''<br />
* 2006-01-04 raised by [[User:CGranade|CGranade]]<br />
*# ''Interactions with strong namespacing. So far, it seems that hCalendar cannot be embedded into non-XHTML schemas that are also strongly namespaced (e.g.: RDF, Atom) without a resultant validation error, as the <code>class</code> attribute is ''not'' portable across schemas.''<br />
*#* REJECTED. The class attribute is used on XHTML elements, which are XML, which can be embedded in any other XML. The issue as raised doesn't make sense.<br />
*# ''All examples in XHTML. XHTML should not be the only host to microformats, and thus it should not be the only example host language. Rather, examples in Atom, RSS, RDF, etc. should also be provided.''<br />
*#* ACCEPTED. This is definitely something to be added to *-examples pages for each microformat.<br />
* 2005-10-14 raised by [[User:MarkoMrdjenovic|MarkoMrdjenovic]]<br />
*# ''UID has to be present in iCal events if they want to be used in Microsoft Outlook. [Suggestion:] it should probably be added to the vevent tag as html attribute id. There is also the problem of converters - x2v has UID commented out. [http://www.ietf.org/rfc/rfc2445.txt RFC] recommends use of addr format for uids which is problematic in html id (does not validate). [[User:HenriBergius|HenriBergius]] pointed out some calendaring software crashes when @ is in the UID, so some other form of identification should be used - along the lines of dtstart-dtend-hash(title,summary)-sample-org''<br />
*#* ACCEPTED-PARTIAL. Yes, it appears RFC2445 requires UID. However, typical mentions of events by web authors do not provide anything equivalent to a UID, nor should we require authors to do so. Thus we must come up with an algorithm for implied UID, similar to some of the other properties. We REJECT the use of the html 'id' attributre as a substitute for UID as they are of different scopes and thus such a translation will likely be problematic. As part of this algorithm, we MUST disallow "@" signs since the issue points out that such UIDs crash some calendaring software.<br />
*# ''DTSTAMP also has to be present in iCal event for Microsoft Outlook. I think DTSTAMP should be user visible information so implementation with class="dtstamp" is fine. x2v already supports it so it should just be added to the standard and examples. The converters might also think of a way to force (create) dtstamp if it's not present.''<br />
*#* ACCEPTED. We should come up with a way to encourage/synthesize/imply DTSTAMP property values.<br />
*# ''Here is an example from Midgard CMS (which will be easy to change according to bergie on irc):''<br />
*#* For more discussion of this, please see [http://microformats.org/wiki/hcalendar-brainstorming#UID_handling hCalendar brainstorming: UID handling]<br />
<pre><nowiki><br />
<li class="vevent" id="2678c3f94af4a49f9ccbb69b92a82aba-midgardGuid"><br />
<abbr class="dtstart" title="2005-10-20T14:34:45Z">Torstai 20. Lokakuu 17:34</abbr> -<br />
<abbr class="dtend" title="2005-10-20T15:33:56Z">18:33</abbr><br />
<a class="url" href="/bergie/another-calendar/82457028ba83407451edd8aaeaa40622.html"><br />
<span class="summary">From the other cal</span><br />
</a><br />
<abbr class="dtstamp" title="2005-10-14T12:16:45Z">Torstai 14. Lokakuu 12:16</abbr><br />
</li></nowiki></pre><br />
* 2005-09-29 raised by RyanKing<br />
*# ''How does one use ATTENDEE?''<br />
* 2005-07-27 raised by Paolo Massa<br />
*# ''I tried to add a hcalendar event in my blog but it rendered orribly. The problem was I already have a 'class="summary' in my normal HTML (it is the title of the posts) and my CSS displays it bigger and bold. In this way the summary of the event was as big as the titles of the posts, destroying readability. The problem is Overloading of class attributes, it might be the case that a blogger already use, for example, class="summary" for different purposes. What can be a solution? Providing in every microformat wiki page a CSS file that users can download and insert in their blog as additional CSS. This CSS file will "shield" attribute "inside" microformats from being interpreted as "normal" attributes. For example for the hCalendar microformats the relative CSS could be something like:<br />
<br />
.vevent .summary {<br />
<br />
//remove all the previously set properties, for example:<br />
<br />
text-decoration: none;<br />
<br />
font-size: 100%;<br />
<br />
...<br />
<br />
}<br />
<br />
Since the hCalendar microformat is the following,<br />
<br />
<span class="vevent"><br />
<br />
<a class="url" href="http://www.web2con.com/"><br />
<br />
<span class="summary">Web 2.0 Conference</span>:<br />
<br />
...<br />
<br />
I hope to have been clear but I'm not so sure ;-)''<br />
<br />
<br />
* 2005-07-21 raised by Neil Jensen <br />
*# ''should we create a vfreebusy class for HTML representations of freebusy data? Discussion [http://microformats.org/wiki/hcalendar-brainstorming#Free.2FBusy_information on hCalendar brainstorming]. Additional background: [http://www.ifreebusy.com/cyclical/blog/calendar/3.html here].''<br />
<br />
* 2005-07-11 raised by Kragen<br />
*# ''The specification of class="url" as &lt;a href="..."> should be a "should", not a "must". Other ways of referencing the event URL, such as &lt;iframe src="..."> and &lt;embed src="...">, shoul be mentioned. At present X2V doesn't appear to handle them. This came up in a discussion about [[xfolk|xFolk]].''<br />
<br />
* 2005-06-21 raised by Hixie<br />
*# ''Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how hCalendars must be parsed, how to handle errors, and so forth. Is it defined in terms of the DOM? Is it defined in terms of a serialisation? How do you handle unexpected content or missing content?<br />
<br />
* 2005-02-22 raised by Matt Raymond [http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2005-February/003124.html on the whatwg list]:<br />
*# ''There is no copyright statement and no patent statement.''<br />
*#* ACCEPTED. I have updated [[hcalendar]] (and [[hcard]], and all other MicroFormats) with a standard copyright statement and patent statement.<br />
<br />
* 2005-02-18 raised by Matt Raymond [http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2005-February/003116.html on the whatwg list]:<br />
*# ''There is no way for some reading the markup to tell if a class name is the name of an attribute or simply the name of a class used for styling.''<br />
*#* REJECTED (strawman, poor assumption). There is no need to differentiate in the general case. In the specific case, a vocabulary is defined within a context.<br />
*# ''As a result of the above, user agents would not be able to reliably allow users to access extension properties such as "x-mozilla-alarm-default-length" (which is an actual extension used in Sunbird).''<br />
*#* REJECTED (out of scope). Extension properties are outside the current scope of hCalendar.<br />
*# ''The use of <abbr> for dates is incorrect. "August 5th, 2004" is not the abbreviation of 2004-09-05. In fact, the opposite is closer to the truth.''<br />
*#* REJECTED (false statement). This is simply a false statement. See this article for an explanation of this use of <abbr>: [http://tantek.com/log/2005/01.html#d26t0100 Human vs. ISO8601 dates problem solved]<br />
*# ''You have to create a complex set of rules for all possible uses of legacy markup within <span class="vcalendar"> which can easily be implemented incorrectly.''<br />
*#* REJECTED (false statements, strawman). There is no legacy markup. There is no need to create rules for all possible uses of legacy markup. There is no need to create a complex set of rules.<br />
*# ''There are styling and tooltip issues that are unresolved.''<br />
*#* REJECTED (empty statements). See the [[hcalendar-faq|hCalendar FAQ]] for answers to specific styling and tooltip questions. Otherwise, please raise specific issues here with clear valid examples.<br />
*# ''hCalendar/hCard is more complicated for webmasters to read and understand and more complicated for developers to implement.''<br />
*#* REJECTED (empty statements, invalid comparator). Please state specific examples which show the perceived complexity. The comparison "more complicated" requires two items, no second item was provided.<br />
*# ''I dislike the entire system of using class names as markup. Class names should be reserved for user-defined semantics.''<br />
*#* ACCEPT-PARTIAL. When specific elements are available, they should be used instead of class names, but even then class names work well to "subclass" specific elements. This is thoroughly discussed in the essay [http://tantek.com/log/2002/12.html#L20021216 A Touch of Class]. And yes, class names can and should be used for user-defined semantics. [[hcalendar|hCalendar]] is one such user, and it is reasonable for users to use each others class names.<br />
*#* ''Would it be more in the spirit of HTML to define these classes in a [http://www.w3.org/TR/html401/struct/global.html#h-7.4.4.3 metadata profile], so that "User agents may... perform some activity based on known conventions for that profile"? Should this be a part of [[microformats]] specifications in general? (If not, why not?)''<br />
*#** ACCEPTED. Yes, all [[microformats]] that introduce new classnames SHOULD include an [http://gmpg.org/xmdp/ XMDP] profile (which itself is a microformat for defining HTML metadata profiles) that defines those classnames.<br />
*#*** ''Ok, but in order to refer to a profile, it needs a URI. Tantek writes in [http://microformats.org/discuss/mail/microformats-discuss/2005-July/000407.html a message of Jul 21] "This is precisely the reason that GMPG was founded and created, to provide permanent URLs/homes for microformat profiles." How does one cause GMPG to issue a profile URL?''<br />
*#**** ACCEPTED. This is on Tantek's [[to-do]] list, to both provide profiles and URLs (probably at gmpg.org) for those profiles for hCalendar etc.</div>Mark Mansourhttp://microformats.org/wiki/index.php?title=hcalendar-issues&diff=5159hcalendar-issues2006-02-25T00:58:49Z<p>Mark Mansour: Notes for the hCalendar IRC meetup</p>
<hr />
<div>= hCalendar Issues =<br />
<br />
These are externally raised issues about [[hcalendar|hCalendar]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec. Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/log/ Tantek]<br />
<br />
See related [[hcard-issues]].<br />
<br />
== Issues ==<br />
<br />
Please use this format:<br />
* YYYY-MM-DD raised by AUTHORNAME<br />
*# ''Issue 1: Here is the first issue I have.''<br />
*# ''Issue 2: Here is the second issue I have.''<br />
<br />
And add new issues to the top of the list:<br />
<br />
* 2006-02-17 raised by [[Mark Mansour]]<br />
*# should vcalendar be a class? Section 4.4 of RFC2445 says: "The Calendaring and Scheduling Core Object is a collection of calendaring and scheduling information. Typically, this information will consist of a single iCalendar object. However, multiple iCalendar objects can be sequentially grouped together." Also the hcalendar class would allow properties on the calendar itself such as METHOD and CALSCALE (I don't think VERSION and PRODID are particularly relevant).<br />
*# how are axis and headers going to be handled? There has been talk that table axis and headers should be used to capture calendar information in a more compact format, but no example are available. Does anyone have examples or should we try to invent some?<br />
*# should embeded components be allowed? [[RyanKing]] has already noted that vJournal overlaps blog-posts (although not yet accepted), but should the components to-do, free/busy, timezone, alarms be allowed? They all considered as just as relevant by the ical spec as events are (my interpretation).<br />
*# validation of the hCalendar tests. The hCalendar tests have been available for a while now, but only Brian Suda and I have made contributions to their content. Does anyone else have thoughts and should we try to make these the beginning of 'official' hCalendar tests?<br />
*# The use of fragments is unclear. Fragment interpretation seems to be agent dependant. Fragments usually denote a heading or marker, like a goto statement for HTML. Unfortunately it may jump in the middle of elements (rather to the beginning of an element). How should this be handled. i.e. <br />
<pre><br />
<a name="myfrag">heading</a><br />
<div class="vevent"><a name="myfrag"></a>here is my stuff</div><br />
</pre><br />
* 2006-02-01 raised by [[RyanKing]]<br />
*# ''Issue 1: Given that now, or soon will have hAtom, should we disallow vJournal, so that we don't have 2 blog-post formats?''<br />
* 2006-01-04 raised by [[User:CGranade|CGranade]]<br />
*# ''Interactions with strong namespacing. So far, it seems that hCalendar cannot be embedded into non-XHTML schemas that are also strongly namespaced (e.g.: RDF, Atom) without a resultant validation error, as the <code>class</code> attribute is ''not'' portable across schemas.''<br />
*#* REJECTED. The class attribute is used on XHTML elements, which are XML, which can be embedded in any other XML. The issue as raised doesn't make sense.<br />
*# ''All examples in XHTML. XHTML should not be the only host to microformats, and thus it should not be the only example host language. Rather, examples in Atom, RSS, RDF, etc. should also be provided.''<br />
*#* ACCEPTED. This is definitely something to be added to *-examples pages for each microformat.<br />
* 2005-10-14 raised by [[User:MarkoMrdjenovic|MarkoMrdjenovic]]<br />
*# ''UID has to be present in iCal events if they want to be used in Microsoft Outlook. [Suggestion:] it should probably be added to the vevent tag as html attribute id. There is also the problem of converters - x2v has UID commented out. [http://www.ietf.org/rfc/rfc2445.txt RFC] recommends use of addr format for uids which is problematic in html id (does not validate). [[User:HenriBergius|HenriBergius]] pointed out some calendaring software crashes when @ is in the UID, so some other form of identification should be used - along the lines of dtstart-dtend-hash(title,summary)-sample-org''<br />
*#* ACCEPTED-PARTIAL. Yes, it appears RFC2445 requires UID. However, typical mentions of events by web authors do not provide anything equivalent to a UID, nor should we require authors to do so. Thus we must come up with an algorithm for implied UID, similar to some of the other properties. We REJECT the use of the html 'id' attributre as a substitute for UID as they are of different scopes and thus such a translation will likely be problematic. As part of this algorithm, we MUST disallow "@" signs since the issue points out that such UIDs crash some calendaring software.<br />
*# ''DTSTAMP also has to be present in iCal event for Microsoft Outlook. I think DTSTAMP should be user visible information so implementation with class="dtstamp" is fine. x2v already supports it so it should just be added to the standard and examples. The converters might also think of a way to force (create) dtstamp if it's not present.''<br />
*#* ACCEPTED. We should come up with a way to encourage/synthesize/imply DTSTAMP property values.<br />
*# ''Here is an example from Midgard CMS (which will be easy to change according to bergie on irc):''<br />
*#* For more discussion of this, please see [http://microformats.org/wiki/hcalendar-brainstorming#UID_handling hCalendar brainstorming: UID handling]<br />
<pre><nowiki><br />
<li class="vevent" id="2678c3f94af4a49f9ccbb69b92a82aba-midgardGuid"><br />
<abbr class="dtstart" title="2005-10-20T14:34:45Z">Torstai 20. Lokakuu 17:34</abbr> -<br />
<abbr class="dtend" title="2005-10-20T15:33:56Z">18:33</abbr><br />
<a class="url" href="/bergie/another-calendar/82457028ba83407451edd8aaeaa40622.html"><br />
<span class="summary">From the other cal</span><br />
</a><br />
<abbr class="dtstamp" title="2005-10-14T12:16:45Z">Torstai 14. Lokakuu 12:16</abbr><br />
</li></nowiki></pre><br />
* 2005-09-29 raised by RyanKing<br />
*# ''How does one use ATTENDEE?''<br />
* 2005-07-27 raised by Paolo Massa<br />
*# ''I tried to add a hcalendar event in my blog but it rendered orribly. The problem was I already have a 'class="summary' in my normal HTML (it is the title of the posts) and my CSS displays it bigger and bold. In this way the summary of the event was as big as the titles of the posts, destroying readability. The problem is Overloading of class attributes, it might be the case that a blogger already use, for example, class="summary" for different purposes. What can be a solution? Providing in every microformat wiki page a CSS file that users can download and insert in their blog as additional CSS. This CSS file will "shield" attribute "inside" microformats from being interpreted as "normal" attributes. For example for the hCalendar microformats the relative CSS could be something like:<br />
<br />
.vevent .summary {<br />
<br />
//remove all the previously set properties, for example:<br />
<br />
text-decoration: none;<br />
<br />
font-size: 100%;<br />
<br />
...<br />
<br />
}<br />
<br />
Since the hCalendar microformat is the following,<br />
<br />
<span class="vevent"><br />
<br />
<a class="url" href="http://www.web2con.com/"><br />
<br />
<span class="summary">Web 2.0 Conference</span>:<br />
<br />
...<br />
<br />
I hope to have been clear but I'm not so sure ;-)''<br />
<br />
<br />
* 2005-07-21 raised by Neil Jensen <br />
*# ''should we create a vfreebusy class for HTML representations of freebusy data? Discussion [http://microformats.org/wiki/hcalendar-brainstorming#Free.2FBusy_information on hCalendar brainstorming]. Additional background: [http://www.ifreebusy.com/cyclical/blog/calendar/3.html here].''<br />
<br />
* 2005-07-11 raised by Kragen<br />
*# ''The specification of class="url" as &lt;a href="..."> should be a "should", not a "must". Other ways of referencing the event URL, such as &lt;iframe src="..."> and &lt;embed src="...">, shoul be mentioned. At present X2V doesn't appear to handle them. This came up in a discussion about [[xfolk|xFolk]].''<br />
<br />
* 2005-06-21 raised by Hixie<br />
*# ''Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how hCalendars must be parsed, how to handle errors, and so forth. Is it defined in terms of the DOM? Is it defined in terms of a serialisation? How do you handle unexpected content or missing content?<br />
<br />
* 2005-02-22 raised by Matt Raymond [http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2005-February/003124.html on the whatwg list]:<br />
*# ''There is no copyright statement and no patent statement.''<br />
*#* ACCEPTED. I have updated [[hcalendar]] (and [[hcard]], and all other MicroFormats) with a standard copyright statement and patent statement.<br />
<br />
* 2005-02-18 raised by Matt Raymond [http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2005-February/003116.html on the whatwg list]:<br />
*# ''There is no way for some reading the markup to tell if a class name is the name of an attribute or simply the name of a class used for styling.''<br />
*#* REJECTED (strawman, poor assumption). There is no need to differentiate in the general case. In the specific case, a vocabulary is defined within a context.<br />
*# ''As a result of the above, user agents would not be able to reliably allow users to access extension properties such as "x-mozilla-alarm-default-length" (which is an actual extension used in Sunbird).''<br />
*#* REJECTED (out of scope). Extension properties are outside the current scope of hCalendar.<br />
*# ''The use of <abbr> for dates is incorrect. "August 5th, 2004" is not the abbreviation of 2004-09-05. In fact, the opposite is closer to the truth.''<br />
*#* REJECTED (false statement). This is simply a false statement. See this article for an explanation of this use of <abbr>: [http://tantek.com/log/2005/01.html#d26t0100 Human vs. ISO8601 dates problem solved]<br />
*# ''You have to create a complex set of rules for all possible uses of legacy markup within <span class="vcalendar"> which can easily be implemented incorrectly.''<br />
*#* REJECTED (false statements, strawman). There is no legacy markup. There is no need to create rules for all possible uses of legacy markup. There is no need to create a complex set of rules.<br />
*# ''There are styling and tooltip issues that are unresolved.''<br />
*#* REJECTED (empty statements). See the [[hcalendar-faq|hCalendar FAQ]] for answers to specific styling and tooltip questions. Otherwise, please raise specific issues here with clear valid examples.<br />
*# ''hCalendar/hCard is more complicated for webmasters to read and understand and more complicated for developers to implement.''<br />
*#* REJECTED (empty statements, invalid comparator). Please state specific examples which show the perceived complexity. The comparison "more complicated" requires two items, no second item was provided.<br />
*# ''I dislike the entire system of using class names as markup. Class names should be reserved for user-defined semantics.''<br />
*#* ACCEPT-PARTIAL. When specific elements are available, they should be used instead of class names, but even then class names work well to "subclass" specific elements. This is thoroughly discussed in the essay [http://tantek.com/log/2002/12.html#L20021216 A Touch of Class]. And yes, class names can and should be used for user-defined semantics. [[hcalendar|hCalendar]] is one such user, and it is reasonable for users to use each others class names.<br />
*#* ''Would it be more in the spirit of HTML to define these classes in a [http://www.w3.org/TR/html401/struct/global.html#h-7.4.4.3 metadata profile], so that "User agents may... perform some activity based on known conventions for that profile"? Should this be a part of [[microformats]] specifications in general? (If not, why not?)''<br />
*#** ACCEPTED. Yes, all [[microformats]] that introduce new classnames SHOULD include an [http://gmpg.org/xmdp/ XMDP] profile (which itself is a microformat for defining HTML metadata profiles) that defines those classnames.<br />
*#*** ''Ok, but in order to refer to a profile, it needs a URI. Tantek writes in [http://microformats.org/discuss/mail/microformats-discuss/2005-July/000407.html a message of Jul 21] "This is precisely the reason that GMPG was founded and created, to provide permanent URLs/homes for microformat profiles." How does one cause GMPG to issue a profile URL?''<br />
*#**** ACCEPTED. This is on Tantek's [[to-do]] list, to both provide profiles and URLs (probably at gmpg.org) for those profiles for hCalendar etc.</div>Mark Mansourhttp://microformats.org/wiki/index.php?title=irc&diff=5009irc2006-02-16T14:04:23Z<p>Mark Mansour: </p>
<hr />
<div>__NOTOC__<br />
= Microformats IRC =<br />
<br />
We have an IRC channel, [irc://irc.freenode.net#microformats #microformats on the freenode network].<br />
<br />
There's typically someone there at any point during the day, though there isn't always active discussion. Sometimes, though this is the best place to discuss issues that need lots of back and forth discussion.<br />
<br />
== People on irc ==<br />
A list of IRC regulars and their normal timezones.<br />
<br />
* [[User:BenjaminCarlyle|BenjaminCarlyle]] (+1000)<br />
* [[User:B.K._DeLong|bkdelong]] (-0500)<br />
* [[User:Cgriego|cgriego]] (-0600)<br />
* [[User:ChrisCasciano|pnhChris]] (-0500)<br />
* [[User:DimitriGlazkov|dglazkov]] (-0600)<br />
* [[User:ChrisMessina|factoryjoe]] (-0800)<br />
* [[User:EdwardOConnor|hober]] (-0800)<br />
* [[User:Enric|enric]] (-0800)<br />
* [[User:Fil|Fil]] (+0200)<br />
* [[User:IanHickson|Hixie]] (-0800)<br />
* [[User:Izo|IZO]]<br />
* [[User:JoeGregorio|jcgregorio]]<br />
* [http://epeus.blogspot.com/ KevinMarks] (-0800)<br />
* [[User:neuro|neuro`]]<br />
* [[User:RyanKing|kingryan]] (-0800)<br />
* [[User:RobertBachmann|RobertBachmann]] (+0100)<br />
* [[User:Tantek|Tantek]] (-0800)<br />
* [[User:ChristopherStJohn|cks]] (-0600)<br />
* [[User:Mark Mansour|Mark Mansour]] (+1100)<br />
<br />
=== bots ===<br />
<br />
* [[mfbot]]<br />
* [[mflogbot]]<br />
* [http://joi.ito.com/joiwiki/JiBot jibot]<br />
<br />
== Logs ==<br />
<br />
Available here: http://rbach.priv.at/Microformats-IRC/<br />
<br />
== IRC meetups ==<br />
<br />
The idea of having IRC meetups (that is, a set time for meeting on IRC) has been suggested by [[User:RyanKing|Ryan King]], as it appears to work well for the WordPress community and may help us from time-to-time. As of yet, there are no plans to have meetups, though.</div>Mark Mansourhttp://microformats.org/wiki/index.php?title=User:Mark_Mansour&diff=31722User:Mark Mansour2006-02-16T14:03:01Z<p>Mark Mansour: </p>
<hr />
<div>http://lifelint.com/blog/</div>Mark Mansourhttp://microformats.org/wiki/index.php?title=hcalendar-examples&diff=6345hcalendar-examples2006-02-14T07:39:11Z<p>Mark Mansour: </p>
<hr />
<div>= hCalendar examples =<br />
<br />
Example [[hcalendar|hCalendars]].<br />
<br />
[http://lifelint.com/ Mark Mansour of Life Lint] has maintains a set of [http://svn.lifelint.com/hcalendar_tests/ publicly available hCalendar tests] for use by the hCalendar community. The [http://www.lifelint.com/blog/2006/02/07/hcalendar-test-cases/ blog entry] describing the tests provides more details.<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</strong>.</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 />
=== 4.6.2 To-do Component ===<br />
<br />
Example: The following is an example of a "VTODO" calendar component:<br />
<br />
<pre><nowiki><br />
BEGIN:VTODO<br />
UID:19970901T130000Z-123404@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19970415T133000Z<br />
DUE:19970416T045959Z<br />
SUMMARY:1996 Income Tax Preparation<br />
CLASS:CONFIDENTIAL<br />
CATEGORIES:FAMILY,FINANCE<br />
PRIORITY:1<br />
STATUS:NEEDS-ACTION<br />
END:VTODO<br />
</nowiki></pre><br />
<br />
This iCalendar fragment as hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
=== 4.6.3 Journal Component ===<br />
<br />
Example: The following is an example of the "VJOURNAL" calendar component:<br />
<br />
BEGIN:VJOURNAL<br />
UID:19970901T130000Z-123405@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART;VALUE=DATE:19970317<br />
SUMMARY:Staff meeting minutes<br />
DESCRIPTION:1. Staff meeting: Participants include Joe\, Lisa<br />
and Bob. Aurora project plans were reviewed. There is currently<br />
no budget reserves for this project. Lisa will escalate to<br />
management. Next meeting on Tuesday.\n<br />
2. Telephone Conference: ABC Corp. sales representative called<br />
to discuss new printer. Promised to get us a demo by Friday.\n<br />
3. Henry Miller (Handsoff Insurance): Car was totaled by tree.<br />
Is looking into a loaner car. 654-2323 (tel).<br />
END:VJOURNAL<br />
<br />
This iCalendar fragment as hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
=== 4.6.4. Free/Busy Component ===<br />
<br />
Example: The following is an example of a "VFREEBUSY" calendar component used to request free or busy time information:<br />
<br />
<pre><nowiki><br />
BEGIN:VFREEBUSY<br />
ORGANIZER:MAILTO:jane_doe@host1.com<br />
ATTENDEE:MAILTO:john_public@host2.com<br />
DTSTART:19971015T050000Z<br />
DTEND:19971016T050000Z<br />
DTSTAMP:19970901T083000Z<br />
END:VFREEBUSY<br />
</nowiki></pre><br />
<br />
This iCalendar fragment as hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
The following is an example of a "VFREEBUSY" calendar component used to reply to the request with busy time information:<br />
<br />
<pre><nowiki><br />
BEGIN:VFREEBUSY<br />
ORGANIZER:MAILTO:jane_doe@host1.com<br />
ATTENDEE:MAILTO:john_public@host2.com<br />
DTSTAMP:19970901T100000Z<br />
FREEBUSY;VALUE=PERIOD:19971015T050000Z/PT8H30M,<br />
19971015T160000Z/PT5H30M,19971015T223000Z/PT6H30M<br />
URL:http://host2.com/pub/busy/jpublic-01.ifb<br />
COMMENT:This iCalendar file contains busy time information for<br />
the next three months.<br />
END:VFREEBUSY<br />
</nowiki></pre><br />
<br />
This iCalendar fragment as hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
The following is an example of a "VFREEBUSY" calendar component used to publish busy time information.<br />
<br />
<pre><nowiki><br />
BEGIN:VFREEBUSY<br />
ORGANIZER: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 />
</nowiki></pre><br />
<br />
This iCalendar fragment as hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><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: ''the attendee markup looks incomplete''<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><br />
<li class="category">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><br />
<li class="category">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><br />
<li class="category">Meeting</li><br />
<li class="category">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><br />
<li class="category">Meeting</li><br />
<li class="category">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: [ftp://xyzCorp.com/pub/conf/bkgrnd.ps ftp://xyzCorp.com/pub/conf/bkgrnd.ps]</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><br />
<li class="category">Project Report</li><br />
<li class="category">xyz</li><br />
<li class="category">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><br />
<li class="category">Project Report</li><br />
<li class="category">xyz</li><br />
<li class="category">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 />
<div class="vcalendar"><br />
<div>Version: <span class="version">2.0</span></div><br />
<div>ProdID:<span class="prodid">-//RDU Software//NONSGML HandCal//EN</span></div><br />
<div class="vfreebusy"><br />
<div>Organizer: <span class="organizer">MAILTO:jsmith@host.com</span></div><br />
<div>Start Time: <abbr class="dtstart" title="19980313T141711Z">March 13, 1998 14:17:11 UTC</abbr></div><br />
<div>End time: <abbr class="dtend" title="19980410T141711Z">April 10, 1998 14:17:11 UTC</abbr></div><br />
<p>Busy times:</p> <!-- note that the default is BUSY --><br />
<ol><br />
<li class="freebusy"><abbr class="dtstart" title="19980314T233000Z">1998-03-14 23:30:00 UTC</abbr> - <abbr class="dtend" title="19980315T003000Z">1998-03-15- 00:30:00 UTC</abbr></li><br />
<li class="freebusy"><abbr class="dtstart" title="19980316T153000Z">1998-03-16 15:30:00 UTC</abbr> - <abbr class="dtend" title="19980316T163000Z">1998-03-16 16:30:00 UTC</abbr></li><br />
<li class="freebusy"><abbr class="dtstart" title="19980318T030000Z">1998-03-18 03:00:00 UTC</abbr> - <abbr class="dtend" title="19980318T040000Z">1998-03-18 04:00:00 UTC</abbr></li><br />
</ol><br />
<div>URL <a class="url" href="http://www.host.com/calendar/busytime/jsmith.ifb">http://www.host.com/calendar/busytime/jsmith.ifb</a></div><br />
</div><br />
</div><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>Mark Mansourhttp://microformats.org/wiki/index.php?title=hcalendar-examples&diff=4952hcalendar-examples2006-02-07T22:29:03Z<p>Mark Mansour: /* hCalendar examples */</p>
<hr />
<div>= hCalendar examples =<br />
<br />
Example [[hcalendar|hCalendars]].<br />
<br />
[http://lifelint.com/ Mark Mansour of Life Lint] has created and maintains a set of [http://lifelint.com/test/hCalendar/ publicly available hCalendar tests] for use by the hCalendar community. The [http://www.lifelint.com/blog/2006/02/07/hcalendar-test-cases/ blog entry] describing the tests provides more details.<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</strong>.</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 />
=== 4.6.2 To-do Component ===<br />
<br />
Example: The following is an example of a "VTODO" calendar component:<br />
<br />
<pre><nowiki><br />
BEGIN:VTODO<br />
UID:19970901T130000Z-123404@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19970415T133000Z<br />
DUE:19970416T045959Z<br />
SUMMARY:1996 Income Tax Preparation<br />
CLASS:CONFIDENTIAL<br />
CATEGORIES:FAMILY,FINANCE<br />
PRIORITY:1<br />
STATUS:NEEDS-ACTION<br />
END:VTODO<br />
</nowiki></pre><br />
<br />
This iCalendar fragment as hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
=== 4.6.3 Journal Component ===<br />
<br />
Example: The following is an example of the "VJOURNAL" calendar component:<br />
<br />
BEGIN:VJOURNAL<br />
UID:19970901T130000Z-123405@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART;VALUE=DATE:19970317<br />
SUMMARY:Staff meeting minutes<br />
DESCRIPTION:1. Staff meeting: Participants include Joe\, Lisa<br />
and Bob. Aurora project plans were reviewed. There is currently<br />
no budget reserves for this project. Lisa will escalate to<br />
management. Next meeting on Tuesday.\n<br />
2. Telephone Conference: ABC Corp. sales representative called<br />
to discuss new printer. Promised to get us a demo by Friday.\n<br />
3. Henry Miller (Handsoff Insurance): Car was totaled by tree.<br />
Is looking into a loaner car. 654-2323 (tel).<br />
END:VJOURNAL<br />
<br />
This iCalendar fragment as hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
=== 4.6.4. Free/Busy Component ===<br />
<br />
Example: The following is an example of a "VFREEBUSY" calendar component used to request free or busy time information:<br />
<br />
<pre><nowiki><br />
BEGIN:VFREEBUSY<br />
ORGANIZER:MAILTO:jane_doe@host1.com<br />
ATTENDEE:MAILTO:john_public@host2.com<br />
DTSTART:19971015T050000Z<br />
DTEND:19971016T050000Z<br />
DTSTAMP:19970901T083000Z<br />
END:VFREEBUSY<br />
</nowiki></pre><br />
<br />
This iCalendar fragment as hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
The following is an example of a "VFREEBUSY" calendar component used to reply to the request with busy time information:<br />
<br />
<pre><nowiki><br />
BEGIN:VFREEBUSY<br />
ORGANIZER:MAILTO:jane_doe@host1.com<br />
ATTENDEE:MAILTO:john_public@host2.com<br />
DTSTAMP:19970901T100000Z<br />
FREEBUSY;VALUE=PERIOD:19971015T050000Z/PT8H30M,<br />
19971015T160000Z/PT5H30M,19971015T223000Z/PT6H30M<br />
URL:http://host2.com/pub/busy/jpublic-01.ifb<br />
COMMENT:This iCalendar file contains busy time information for<br />
the next three months.<br />
END:VFREEBUSY<br />
</nowiki></pre><br />
<br />
This iCalendar fragment as hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
The following is an example of a "VFREEBUSY" calendar component used to publish busy time information.<br />
<br />
<pre><nowiki><br />
BEGIN:VFREEBUSY<br />
ORGANIZER: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 />
</nowiki></pre><br />
<br />
This iCalendar fragment as hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><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: ''the attendee markup looks incomplete''<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><br />
<li class="category">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><br />
<li class="category">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><br />
<li class="category">Meeting</li><br />
<li class="category">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><br />
<li class="category">Meeting</li><br />
<li class="category">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: [ftp://xyzCorp.com/pub/conf/bkgrnd.ps ftp://xyzCorp.com/pub/conf/bkgrnd.ps]</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><br />
<li class="category">Project Report</li><br />
<li class="category">xyz</li><br />
<li class="category">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><br />
<li class="category">Project Report</li><br />
<li class="category">xyz</li><br />
<li class="category">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 />
<div class="vcalendar"><br />
<div>Version: <span class="version">2.0</span></div><br />
<div>ProdID:<span class="prodid">-//RDU Software//NONSGML HandCal//EN</span></div><br />
<div class="vfreebusy"><br />
<div>Organizer: <span class="organizer">MAILTO:jsmith@host.com</span></div><br />
<div>Start Time: <abbr class="dtstart" title="19980313T141711Z">March 13, 1998 14:17:11 UTC</abbr></div><br />
<div>End time: <abbr class="dtend" title="19980410T141711Z">April 10, 1998 14:17:11 UTC</abbr></div><br />
<p>Busy times:</p> <!-- note that the default is BUSY --><br />
<ol><br />
<li class="freebusy"><abbr class="dtstart" title="19980314T233000Z">1998-03-14 23:30:00 UTC</abbr> - <abbr class="dtend" title="19980315T003000Z">1998-03-15- 00:30:00 UTC</abbr></li><br />
<li class="freebusy"><abbr class="dtstart" title="19980316T153000Z">1998-03-16 15:30:00 UTC</abbr> - <abbr class="dtend" title="19980316T163000Z">1998-03-16 16:30:00 UTC</abbr></li><br />
<li class="freebusy"><abbr class="dtstart" title="19980318T030000Z">1998-03-18 03:00:00 UTC</abbr> - <abbr class="dtend" title="19980318T040000Z">1998-03-18 04:00:00 UTC</abbr></li><br />
</ol><br />
<div>URL <a class="url" href="http://www.host.com/calendar/busytime/jsmith.ifb">http://www.host.com/calendar/busytime/jsmith.ifb</a></div><br />
</div><br />
</div><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>Mark Mansourhttp://microformats.org/wiki/index.php?title=hcalendar-examples&diff=4845hcalendar-examples2006-02-07T22:27:09Z<p>Mark Mansour: /* hCalendar examples */</p>
<hr />
<div>= hCalendar examples =<br />
<br />
Example [[hcalendar|hCalendars]].<br />
<br />
[http://lifelint.com/ Mark Mansour of Life Lint] has created and maintains a set of [http://lifelint.com/test/hCalendar/ publicly available hCalendar tests] for use by the hCalendar community.<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</strong>.</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 />
=== 4.6.2 To-do Component ===<br />
<br />
Example: The following is an example of a "VTODO" calendar component:<br />
<br />
<pre><nowiki><br />
BEGIN:VTODO<br />
UID:19970901T130000Z-123404@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART:19970415T133000Z<br />
DUE:19970416T045959Z<br />
SUMMARY:1996 Income Tax Preparation<br />
CLASS:CONFIDENTIAL<br />
CATEGORIES:FAMILY,FINANCE<br />
PRIORITY:1<br />
STATUS:NEEDS-ACTION<br />
END:VTODO<br />
</nowiki></pre><br />
<br />
This iCalendar fragment as hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
=== 4.6.3 Journal Component ===<br />
<br />
Example: The following is an example of the "VJOURNAL" calendar component:<br />
<br />
BEGIN:VJOURNAL<br />
UID:19970901T130000Z-123405@host.com<br />
DTSTAMP:19970901T1300Z<br />
DTSTART;VALUE=DATE:19970317<br />
SUMMARY:Staff meeting minutes<br />
DESCRIPTION:1. Staff meeting: Participants include Joe\, Lisa<br />
and Bob. Aurora project plans were reviewed. There is currently<br />
no budget reserves for this project. Lisa will escalate to<br />
management. Next meeting on Tuesday.\n<br />
2. Telephone Conference: ABC Corp. sales representative called<br />
to discuss new printer. Promised to get us a demo by Friday.\n<br />
3. Henry Miller (Handsoff Insurance): Car was totaled by tree.<br />
Is looking into a loaner car. 654-2323 (tel).<br />
END:VJOURNAL<br />
<br />
This iCalendar fragment as hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
=== 4.6.4. Free/Busy Component ===<br />
<br />
Example: The following is an example of a "VFREEBUSY" calendar component used to request free or busy time information:<br />
<br />
<pre><nowiki><br />
BEGIN:VFREEBUSY<br />
ORGANIZER:MAILTO:jane_doe@host1.com<br />
ATTENDEE:MAILTO:john_public@host2.com<br />
DTSTART:19971015T050000Z<br />
DTEND:19971016T050000Z<br />
DTSTAMP:19970901T083000Z<br />
END:VFREEBUSY<br />
</nowiki></pre><br />
<br />
This iCalendar fragment as hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
The following is an example of a "VFREEBUSY" calendar component used to reply to the request with busy time information:<br />
<br />
<pre><nowiki><br />
BEGIN:VFREEBUSY<br />
ORGANIZER:MAILTO:jane_doe@host1.com<br />
ATTENDEE:MAILTO:john_public@host2.com<br />
DTSTAMP:19970901T100000Z<br />
FREEBUSY;VALUE=PERIOD:19971015T050000Z/PT8H30M,<br />
19971015T160000Z/PT5H30M,19971015T223000Z/PT6H30M<br />
URL:http://host2.com/pub/busy/jpublic-01.ifb<br />
COMMENT:This iCalendar file contains busy time information for<br />
the next three months.<br />
END:VFREEBUSY<br />
</nowiki></pre><br />
<br />
This iCalendar fragment as hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><br />
<br />
The following is an example of a "VFREEBUSY" calendar component used to publish busy time information.<br />
<br />
<pre><nowiki><br />
BEGIN:VFREEBUSY<br />
ORGANIZER: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 />
</nowiki></pre><br />
<br />
This iCalendar fragment as hCalendar:<br />
<br />
<pre><nowiki><br />
@TODO<br />
</nowiki></pre><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: ''the attendee markup looks incomplete''<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><br />
<li class="category">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><br />
<li class="category">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><br />
<li class="category">Meeting</li><br />
<li class="category">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><br />
<li class="category">Meeting</li><br />
<li class="category">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: [ftp://xyzCorp.com/pub/conf/bkgrnd.ps ftp://xyzCorp.com/pub/conf/bkgrnd.ps]</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><br />
<li class="category">Project Report</li><br />
<li class="category">xyz</li><br />
<li class="category">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><br />
<li class="category">Project Report</li><br />
<li class="category">xyz</li><br />
<li class="category">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 />
<div class="vcalendar"><br />
<div>Version: <span class="version">2.0</span></div><br />
<div>ProdID:<span class="prodid">-//RDU Software//NONSGML HandCal//EN</span></div><br />
<div class="vfreebusy"><br />
<div>Organizer: <span class="organizer">MAILTO:jsmith@host.com</span></div><br />
<div>Start Time: <abbr class="dtstart" title="19980313T141711Z">March 13, 1998 14:17:11 UTC</abbr></div><br />
<div>End time: <abbr class="dtend" title="19980410T141711Z">April 10, 1998 14:17:11 UTC</abbr></div><br />
<p>Busy times:</p> <!-- note that the default is BUSY --><br />
<ol><br />
<li class="freebusy"><abbr class="dtstart" title="19980314T233000Z">1998-03-14 23:30:00 UTC</abbr> - <abbr class="dtend" title="19980315T003000Z">1998-03-15- 00:30:00 UTC</abbr></li><br />
<li class="freebusy"><abbr class="dtstart" title="19980316T153000Z">1998-03-16 15:30:00 UTC</abbr> - <abbr class="dtend" title="19980316T163000Z">1998-03-16 16:30:00 UTC</abbr></li><br />
<li class="freebusy"><abbr class="dtstart" title="19980318T030000Z">1998-03-18 03:00:00 UTC</abbr> - <abbr class="dtend" title="19980318T040000Z">1998-03-18 04:00:00 UTC</abbr></li><br />
</ol><br />
<div>URL <a class="url" href="http://www.host.com/calendar/busytime/jsmith.ifb">http://www.host.com/calendar/busytime/jsmith.ifb</a></div><br />
</div><br />
</div><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>Mark Mansourhttp://microformats.org/wiki/index.php?title=hcalendar&diff=4875hcalendar2006-02-07T22:22:27Z<p>Mark Mansour: Life Lint parser addition</p>
<hr />
<div>= hCalendar =<br />
<br />
hCalendar is a simple open, distributed calendaring and events format, based on the iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]), suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. hCalendar is one of several open [[microformats|microformat]] standards.<br />
<br />
__TOC__<br />
<br />
== Draft Specification ==<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://suda.co.uk/ Brian Suda]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
=== Inspiration and Acknowledgments ===<br />
Thanks to:<br />
* Adam Bosworth for leading the [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation] which brought together a critical mass of interested parties.<br />
<br />
<br />
<br />
== Introduction ==<br />
The iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]), has been broadly interoperably implemented (e.g. Apple's &quot;iCal&quot; application built into MacOSX).<br />
<br />
In addition, bloggers often discuss events on their blogs -- upcoming events, writeups of past events, etc. With just a tad bit of structure, bloggers can discuss events in their blog(s) in such a way that spiders and other aggregators can retrieve such events, automatically convert them to iCalendar, and use them in any iCalendar application or service.<br />
<br />
This specification introduces the '''hCalendar''' format, which is a 1:1 representation of the aforementioned iCalendar standard, in semantic XHTML. Bloggers can both embed hCalendar events directly in their web pages, and style them with CSS to make them appear as desired. In addition, hCalendar enables applications to retrieve information about such events directly from web pages without having to reference a separate file.<br />
<br />
== Semantic XHTML Design Principles ==<br />
<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
<br />
=== In General ===<br />
<br />
The iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]) forms the basis of hCalendar.<br />
<br />
Note: the editor and authors of this specification are tracking the [http://lists.osafoundation.org/pipermail/ietf-calsify/ &quot;iCal-Basic&quot; effort] and intend to base the core hCalendar profile on iCal-Basic. See references for a link to the current draft.<br />
<br />
The basic format of hCalendar is to use iCalendar object/property names in lower-case for class names, and to map the nesting of iCalendar objects directly into nested XHTML.<br />
<br />
=== More Semantic Equivalents ===<br />
<br />
However, for some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:<br />
* <code>URL</code> in iCalendar becomes <code><a class=&quot;url&quot; href=&quot;...&quot;>...</a></code> inside the element with <code>class=&quot;vevent&quot;</code> in hCalendar.<br />
* <code>ATTENDEE</code> in iCalendar may in hCalendar be represented by an [[hcard]].<br />
<br />
=== Singular vs. Plural Properties ===<br />
<br />
For properties which are singular (e.g. &quot;N&quot; and &quot;FN&quot; from vCard), the first descendant element with that class should take effect, any others being ignored.<br />
<br />
For properties which can be plural (e.g. &quot;TEL&quot; from vCard), each class instance should create a instance of that property. Plural properties with subtypes (e.g. TEL with WORK, HOME, CELL from vCard) can be optimized to share a common element for the property itself, with each instance of subtype being an appropriately classed descendant of the property element. <br />
<br />
=== Human vs. Machine readable ===<br />
If an <code>&lt;abbr&gt;</code> element is used for a property, then the '<code>title</code>' attribute of the <code>&lt;abbr&gt;</code> element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value. This specification recommends that such <code>&lt;abbr&gt;</code> elements be used for the following iCalendar properties:<br />
* DTSTART, DTEND, DURATION, RDATE, RRULE<br />
<br />
== Example ==<br />
<br />
Here is a sample event in an iCalendar:<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
PRODID:-//XYZproduct//EN<br />
VERSION:2.0<br />
BEGIN:VEVENT<br />
URL:http://www.web2con.com/<br />
DTSTART:20051005<br />
DTEND:20051008<br />
SUMMARY:Web 2.0 Conference<br />
LOCATION:Argent Hotel\, San Francisco\, CA<br />
END:VEVENT<br />
END:VCALENDAR<br />
</nowiki></pre><br />
and an equivalent event in hCalendar format with various elements optimized appropriately. See [[hcalendar-example1-steps]] for the derivation.<br />
<br />
<pre><nowiki><br />
<span class=&quot;vevent&quot;><br />
<a class=&quot;url&quot; href=&quot;http://www.web2con.com/&quot;><br />
<span class=&quot;summary&quot;>Web 2.0 Conference</span>: <br />
<abbr class=&quot;dtstart&quot; title=&quot;2005-10-05&quot;>October 5</abbr>-<br />
<abbr class=&quot;dtend&quot; title=&quot;2005-10-08&quot;>7</abbr>,<br />
at the <span class=&quot;location&quot;>Argent Hotel, San Francisco, CA</span><br />
</a><br />
</span><br />
</nowiki></pre><br />
which could be displayed as:<br />
<br />
[http://www.web2con.com/ Web 2.0 Conference: October 5-7, at the Argent Hotel, San Francisco, CA]<br />
<br />
Note 1: The product information is not necessary since hCalendar is an interchange format. When transforming hCalendar back into iCalendar, the transforming engine should add its own product ID.<br />
<br />
Note 2: A surrounding <span class=&quot;vcalendar&quot;> element is optional, and is left out as such. It is optional since the context of a vcalendar is implied when a vevent is encountered. The implied context/scope is that of the document. Authors may explicitly use elements with class=&quot;vcalendar&quot; to wrap sets of vevents that all belong to the same calendar, e.g. when publishing multiple calendars on the same page.<br />
<br />
Note 3: The version information is unnecessary in hCalendar markup directly since the version will be defined by the profile of hCalendar that is used/referred to in the 'profile' attribute of the <head> element.<br />
<br />
Note 4: ISO8601 dates (required by iCalendar) are not very human friendly. In addition, the year is often understood implicitly by humans from the context. Thus <code>&lt;abbr&gt;</code> elements are used to simultaneously provide a human friendly date and/or time in the visible contents of the element, while placing the respective machine parsable comprehensive ISO8601 datetime in the 'title' attribute.<br />
The notation YYYY-MM-DD should be used for better readability.<br />
<br />
Note 5: The difference between the DTEND ISO8601 date (2005-10-08) and the human readable date (7) is NOT a mistake. [http://lists.osafoundation.org/pipermail/ietf-calsify/2005-September/000769.html DTEND is exclusive], meaning, that the event ends just before the DTEND. Thus for events which start on one day and end on another day, the DTEND date must be specified as the day after the day that a human would say is the last day of the event.<br />
<br />
See [[hcalendar-examples]] for more hCalendar examples<br />
<br />
== Examples in the wild ==<br />
This section is '''informative'''.<br />
<br />
The following sites have implemented hCalendar, and thus are a great place to start for anyone looking for examples &quot;in the wild&quot; to try parsing, indexing, organizing etc. If events on your pages are marked up with hCalendar, 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 />
=== New Examples ===<br />
Please add new examples to this section.<br />
* ...<br />
* [http://www.stateofflux.com/ State of Flux street art site] has started adding events in hCalendar format<br />
* The [http://barcamp.org/#BarCamps BarCamp home page lists upcoming BarCamps marked up with hCalenar] and even has a "Subscribe..." link.<br />
* [http://www.w3.org/2005/12/allgroupoverview.html 2006 W3C Technical Plenary Week] has marked up the schedule and events for the week with hCalendar.<br />
* [http://www.code4lib.org/2006/schedule code4lib Conference 2006 Schedule] is marked up with hCalendar as [http://www.code4lib.org/node/65 announced on their blog].<br />
* [http://grouper.ieee.org/groups/754 IEEE 754 Working Group] - trying hCalendar for upcoming meetings.<br />
* [http://www.pehuen.org/node/494 Elecciones 2005 Chile] - the first spanish language hCalendar event found in the wild.<br />
* [http://www.codewitch.org/it/2005/11/17/no-creative-commons-no-party/ Giocolando » No Creative Commons? No Party!] is marked up with hCalendar<br />
* [http://www.cmprofessionals.org/events/calendar.html CM Pros Events Calendar] by Bob Doyle<br />
* [http://www.midgard-project.org/community/events/ Midgard CMS Event calendar] - as [http://bergie.iki.fi/blog/new-event-calendar-for-midcom.html blogged by Henri Bergius] <br />
* [http://www.iowamilitaryveteransband.com/schedule/ Iowa Military Veterans Band Schedule] - hCalendar markup [http://weblog.randomchaos.com/archive/2005/10/24/Microformats/ added by Scott Reynen]<br />
* [http://www.funfairgames.net/weblog/posts/00000011.html Upcoming events on Jason A.R. Moody Amusements Weblog] posted by Jason Moody on 15 Oct 2005. [http://www.funfairgames.net/weblog/index.html His weblog] in general has hCalendar events posted inside the blog posts.<br />
* [http://tantek.com/microformats/2005/syndicate/tracks-sessions-schedule.html Syndicate - Tracks &amp; Sessions]<br />
* [http://tantek.com/microformats/2005/web2/program.html Web 2.0 Conference schedule page marked up with hCalendar]<br />
* [http://www.thisiscmon.com/ C'MON] is a rock band from Canada, and their [http://www.thisiscmon.com/shows/ tour dates] have been marked up by [http://www.d2digitalmedia.com/ Ray Dickman] with hCalendar.<br />
* [http://ifreebusy.com/ ifreebusy.com] will display freebusy information using hCalendar. See this [http://ifreebusy.com/neiljensen/freebusy/ example].<br />
* [http://we05.com/ Web Essentials 05] has marked up their [http://we05.com/program.cfm program schedule table with hCalendar], using the 'axis' and 'headers' attributes.<br />
* [http://www.asdvbonaparte.nl/ ASDV Bonaparte] is a Dutch debating society. Their events calendar has been marked up with the hCalendar conventions.<br />
* [http://chocnvodka.blogware.com/blog Suw Charman] has marked up [http://suw.org.uk/archives/category/events/ her events] with hCalendar.<br />
* [http://www.blogbusinesssummit.com/ Blog Business Summit] has published their [http://www.blogbusinesssummit.com/details.htm event details] marked up with hCalendar.<br />
* [http://evdb.com EVDB], the Events and Venues database, publishes all events with hCalendar and venues with [[hcard|hCard]]. Took them only 15 minutes to implement both!<br />
* [http://upcoming.org Upcoming.org] publishes all events and lists of events with hCalendar. Took them only an hour to add hCalendar support to the site.<br />
* The [http://laughingsquid.com/squidlist/calendar/ Laughing Squid Calendar] events, [http://laughingsquid.com/squidlist/calendar/9949/2005/5/9 e.g. this party], now supports hCalendar.<br />
* [http://paulschreiber.com/ Paul] Schreiber's [http://concerts.shrub.ca/ Sunnyvale House Concerts] site publishes hCalendar event information for upcoming concerts. In addition the [http://concerts.shrub.ca/shows Past Shows] page contains hCalendar events for all past concerts.<br />
* [http://paulschreiber.com/ Paul] Schreiber's [http://iceoasis.shrub.ca/ unofficial schedule site] publishes hCalendar information for upcoming hockey games at [http://www.iceoasis.com/ Ice Oasis]<br />
* [http://www.complexspiral.com/ Complex Spiral Consulting], both in the &quot;Events&quot; box on left side, and the separate [http://www.complexspiral.com/events/ Events page]. <br />
* [http://tantek.com/log Tantek's Thoughts], specifically the &quot;Events&quot; roll in the right-most column.<br />
* [http://suda.co.uk/projects/holidays/ Lesser Known Holidays], a list of holidays on [http://suda.co.uk suda.co.uk] that can be imported via iCal and hCal so you can compare actual transformation versus intended.<br />
* [http://norman.walsh.name/2005/itinerary/ Norm Walsh's travel schedule] use hCalendar as well as GRDDL.<br />
* [http://www.policyawareweb.org/2005/ftf2/paw-mtg Policy Aware Web (PAW) Project Meeting] uses hCalendar to record date-related decisions, and uses a vtodo microformat to record action items.<br />
* The [http://www.kiez-ev.de/ Kiez] is a small cinema and has published its [http://www.kiez-ev.de/programm.htm program] marked up with hCalendar.<br />
* The [http://lufgi4.informatik.rwth-aachen.de Laboratory for Dependable Distributed Systems] publishes it's [http://lufgi4.informatik.rwth-aachen.de/cfps list of notable CfPs on dependability and security] with hCalendar-todo elements.<br />
* The [http://laughingsquid.com/laughing-squid-10th-anniversary-party/ Laughing Squid 10th Anniversary Party] has an hcalendar page.<br />
* SPRACI has hcalendar versions of its nightlife/clubbing/gigs/festivals listings for many cities worldwide - eg: [http://www.spraci.com/listhcalendar.php?parea=sydney&category=all Events in Sydney] (check the [http://www.spraci.com/api/ API] pages in the faq section of [http://www.spraci.com/ SPRACI] for more info about the area/city keywords and category tags to use to get data for your city/categories<br />
<br />
=== Examples with some problems ===<br />
* [http://www.webanalyticsassociation.org/en/calendarevents/search.asp Web Analytics Association] - hCalendar microformat is in place on all Tendenci sites on the calendar events search page and consolidated list page.<br />
** WARNINGS<br />
*** has only dates where there should be datetime's<br />
*** has abbr's with no title<br />
*** should probably markup the description --[[User:RyanKing|RyanKing]] 16:04, 6 Jan 2006 (PST)<br />
* [http://www.bokle.de/ s'Bokle] is a German music pub. Their events calendar has been marked up with hCalendar.<br />
** improper use of rrule --[[User:RyanKing|RyanKing]] 16:04, 6 Jan 2006 (PST)<br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
The following implementations have been developed which either generate or parse hCalendars. If you have an hCalendar 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 />
=== Generation ===<br />
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCalendar and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].<br />
* [http://www.midgard-project.org/documentation/net-nemein-calendar/ Midgard CMS - net.nemein.calendar] - as [http://bergie.iki.fi/blog/new-event-calendar-for-midcom.html blogged by Henri Bergius] <br />
* [http://www.decafbad.com/blog/2005/06/08/greasemonkey_magic magic_hcalendar Greasemonkey user script by Les Orchard] - allows easy form entry of an event into any textarea, e.g. into a blog post text area.<br />
* [http://microformats.org/code/hcalendar/creator microformats.org hCalendar creator]<br />
* [http://hybernaut.com/upcoming-hcal Drupal Upcoming.org syndication module emits hCalendar]<br />
* [http://theryanking.com/ Ryan King] has an [http://theryanking.com/microformats/hcalendar-creator.html hCalendar creator].<br />
<br />
=== Conversion and consumption ===<br />
* [http://lifelint.net/ Life Lint Parser] parses hCalendar and produces .ics, .rdf and debugging information and attempts to be more fully compliant to the iCal standard than previous implementations. It can be used in the same manner as X2V.<br />
* [http://blog.codeeg.com/tails-firefox-extension/ Tails is a Firefox Extension] that will display the presence of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage.<br />
* In [http://www.xfytec.com/community/ xfy Community], there are some hCalendar implementations. "hCalendar via RSS" parses an RSS feed, retrieves XHTML documents linked from that feed, and syndicates hCalendars into a calendar view.<br />
* [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats simple hCalendar parser] by [http://virtuelvis.com/ Arve Bersvendsen]<br />
* [http://george.hotelling.net/90percent/ George] has built a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script that detects hCalendar events and allows users to easily add them to their calendar application(s)].<br />
* [http://blogmatrix.blogmatrix.com/ David Janes] has produced a [[Greasemonkey]] [http://www.blogmatrix.com/include/microformat-find.user.js script] that finds many microformat elements, including hCalendar events, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. The hCalendar to vCalendar conversion is done internally within the script. ''This does not work with FireFox 1.5+/GreaseMonkey 0.6.4+.''<br />
* [http://suda.co.uk/projects/X2V/ X2V] parses hCalendar and produces a .ics (iCalendar) stream. Note: needs to be updated to track changes in the specification as they occur.<br />
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] by [[User:DanC]] includes toICal.xsl and test materials; it works much like xhtml2vcal.xsl in X2V. See also: [http://www.w3.org/2002/12/cal/ RDF Calendar workspace] with icalendar test materials.<br />
* [http://web.mit.edu/glasser/www/JSCalendar/ JSCalendar] parses hCalendar and produces a displayable HTML table/CSS-based calendar.<br />
<br />
Investigation:<br />
* [http://wiki.mozilla.org/Calendar_Talk:Lightning#hCalendar_publish_and_subscribe_support Mozilla Calendar / Lightning / Sunbird hCalendar support discussion]<br />
<br />
=== Potential implementations ===<br />
<br />
These are open source projects that could be potentially enhanced to support hCalendar.<br />
<br />
* [http://www.k5n.us/webcalendar.php?topic=About WebCalendar]<br />
* [http://phpicalendar.net/documentation/index.php?title=Main_Page PHP iCalendar]<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]<br />
* [[hcard|hCard]]<br />
* [http://www.ietf.org/rfc/rfc2445.txt iCalendar RFC2445]<br />
<br />
=== Informative References ===<br />
* [http://w3.org/TR/REC-CSS1 CSS1]<br />
* [http://tantek.com/log/2004/09.html#hcalendar hCalendar term introduced and defined on the Web, 20040930]<br />
* [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation, 20040911]<br />
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]<br />
* [http://www.ietf.org/internet-drafts/draft-royer-ical-basic-02.txt iCal-Basic draft 02]<br />
* Contributed from http://developers.technorati.com/wiki/hCalendar<br />
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]<br />
<br />
==== Related ====<br />
* [[icalendar-implementations|iCalendar implementations]]<br />
* [http://lists.osafoundation.org/pipermail/ietf-calsify/ IETF-calsify archives]<br />
* [http://www.livejournal.com/users/jwz/444651.html jwz - Hula] (required reading)<br />
* [http://www.jwz.org/doc/groupware.html Groupware Bad by Jamie Zawinski] crystalizes the reason for hCalendar ('''emphasis''' added):<br />
<blockquote>&quot;Right now people can do that by publishing .ics files, but it's not trivial to do so, and it's work on the part of other people to look at them. '''If it's not HTML hanging off our friend's home page that can be viewed in any browser on a public terminal in a library, the bar to entry is too high and it's useless.'''&quot;</blockquote><br />
<br />
* [http://muddybranch.thejkgroup.com/ Jason Klemow's blog]<br />
* [http://www.softwarestudio.org/iCal/2445Issues.html RFC2445 Issues List]<br />
* [http://ietf.webdav.org/calsify/ CALSIFY WG Links And Resources]<br />
<br />
=== Similar Work ===<br />
* [[XOXO]]<br />
<br />
== Discussions ==<br />
<br />
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. There is a separate document where we are keeping our brainstorms and other explorations relating to hCalendar:<br />
<br />
* [[hcalendar-brainstorming]]<br />
<br />
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
** [http://weblog.infoworld.com/udell/2006/01/11.html#a1368 Moving forward with microformats] by [http://weblog.infoworld.com/udell Jon Udell] provides an hCalendar example and some discussion.<br />
<br />
=== Q&A ===<br />
* If you have any questions about hCalendar, check the [[hcalendar-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 [[hcalendar-issues]] document.</div>Mark Mansourhttp://microformats.org/wiki/index.php?title=hcalendar&diff=4843hcalendar2006-02-05T12:28:58Z<p>Mark Mansour: new site with hCalendar</p>
<hr />
<div>= hCalendar =<br />
<br />
hCalendar is a simple open, distributed calendaring and events format, based on the iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]), suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. hCalendar is one of several open [[microformats|microformat]] standards.<br />
<br />
__TOC__<br />
<br />
== Draft Specification ==<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://suda.co.uk/ Brian Suda]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
=== Inspiration and Acknowledgments ===<br />
Thanks to:<br />
* Adam Bosworth for leading the [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation] which brought together a critical mass of interested parties.<br />
<br />
<br />
<br />
== Introduction ==<br />
The iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]), has been broadly interoperably implemented (e.g. Apple's &quot;iCal&quot; application built into MacOSX).<br />
<br />
In addition, bloggers often discuss events on their blogs -- upcoming events, writeups of past events, etc. With just a tad bit of structure, bloggers can discuss events in their blog(s) in such a way that spiders and other aggregators can retrieve such events, automatically convert them to iCalendar, and use them in any iCalendar application or service.<br />
<br />
This specification introduces the '''hCalendar''' format, which is a 1:1 representation of the aforementioned iCalendar standard, in semantic XHTML. Bloggers can both embed hCalendar events directly in their web pages, and style them with CSS to make them appear as desired. In addition, hCalendar enables applications to retrieve information about such events directly from web pages without having to reference a separate file.<br />
<br />
== Semantic XHTML Design Principles ==<br />
<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
<br />
=== In General ===<br />
<br />
The iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]) forms the basis of hCalendar.<br />
<br />
Note: the editor and authors of this specification are tracking the [http://lists.osafoundation.org/pipermail/ietf-calsify/ &quot;iCal-Basic&quot; effort] and intend to base the core hCalendar profile on iCal-Basic. See references for a link to the current draft.<br />
<br />
The basic format of hCalendar is to use iCalendar object/property names in lower-case for class names, and to map the nesting of iCalendar objects directly into nested XHTML.<br />
<br />
=== More Semantic Equivalents ===<br />
<br />
However, for some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:<br />
* <code>URL</code> in iCalendar becomes <code><a class=&quot;url&quot; href=&quot;...&quot;>...</a></code> inside the element with <code>class=&quot;vevent&quot;</code> in hCalendar.<br />
* <code>ATTENDEE</code> in iCalendar may in hCalendar be represented by an [[hcard]].<br />
<br />
=== Singular vs. Plural Properties ===<br />
<br />
For properties which are singular (e.g. &quot;N&quot; and &quot;FN&quot; from vCard), the first descendant element with that class should take effect, any others being ignored.<br />
<br />
For properties which can be plural (e.g. &quot;TEL&quot; from vCard), each class instance should create a instance of that property. Plural properties with subtypes (e.g. TEL with WORK, HOME, CELL from vCard) can be optimized to share a common element for the property itself, with each instance of subtype being an appropriately classed descendant of the property element. <br />
<br />
=== Human vs. Machine readable ===<br />
If an <code>&lt;abbr&gt;</code> element is used for a property, then the '<code>title</code>' attribute of the <code>&lt;abbr&gt;</code> element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value. This specification recommends that such <code>&lt;abbr&gt;</code> elements be used for the following iCalendar properties:<br />
* DTSTART, DTEND, DURATION, RDATE, RRULE<br />
<br />
== Example ==<br />
<br />
Here is a sample event in an iCalendar:<br />
<pre><nowiki><br />
BEGIN:VCALENDAR<br />
PRODID:-//XYZproduct//EN<br />
VERSION:2.0<br />
BEGIN:VEVENT<br />
URL:http://www.web2con.com/<br />
DTSTART:20051005<br />
DTEND:20051008<br />
SUMMARY:Web 2.0 Conference<br />
LOCATION:Argent Hotel\, San Francisco\, CA<br />
END:VEVENT<br />
END:VCALENDAR<br />
</nowiki></pre><br />
and an equivalent event in hCalendar format with various elements optimized appropriately. See [[hcalendar-example1-steps]] for the derivation.<br />
<br />
<pre><nowiki><br />
<span class=&quot;vevent&quot;><br />
<a class=&quot;url&quot; href=&quot;http://www.web2con.com/&quot;><br />
<span class=&quot;summary&quot;>Web 2.0 Conference</span>: <br />
<abbr class=&quot;dtstart&quot; title=&quot;2005-10-05&quot;>October 5</abbr>-<br />
<abbr class=&quot;dtend&quot; title=&quot;2005-10-08&quot;>7</abbr>,<br />
at the <span class=&quot;location&quot;>Argent Hotel, San Francisco, CA</span><br />
</a><br />
</span><br />
</nowiki></pre><br />
which could be displayed as:<br />
<br />
[http://www.web2con.com/ Web 2.0 Conference: October 5-7, at the Argent Hotel, San Francisco, CA]<br />
<br />
Note 1: The product information is not necessary since hCalendar is an interchange format. When transforming hCalendar back into iCalendar, the transforming engine should add its own product ID.<br />
<br />
Note 2: A surrounding <span class=&quot;vcalendar&quot;> element is optional, and is left out as such. It is optional since the context of a vcalendar is implied when a vevent is encountered. The implied context/scope is that of the document. Authors may explicitly use elements with class=&quot;vcalendar&quot; to wrap sets of vevents that all belong to the same calendar, e.g. when publishing multiple calendars on the same page.<br />
<br />
Note 3: The version information is unnecessary in hCalendar markup directly since the version will be defined by the profile of hCalendar that is used/referred to in the 'profile' attribute of the <head> element.<br />
<br />
Note 4: ISO8601 dates (required by iCalendar) are not very human friendly. In addition, the year is often understood implicitly by humans from the context. Thus <code>&lt;abbr&gt;</code> elements are used to simultaneously provide a human friendly date and/or time in the visible contents of the element, while placing the respective machine parsable comprehensive ISO8601 datetime in the 'title' attribute.<br />
The notation YYYY-MM-DD should be used for better readability.<br />
<br />
Note 5: The difference between the DTEND ISO8601 date (2005-10-08) and the human readable date (7) is NOT a mistake. [http://lists.osafoundation.org/pipermail/ietf-calsify/2005-September/000769.html DTEND is exclusive], meaning, that the event ends just before the DTEND. Thus for events which start on one day and end on another day, the DTEND date must be specified as the day after the day that a human would say is the last day of the event.<br />
<br />
See [[hcalendar-examples]] for more hCalendar examples<br />
<br />
== Examples in the wild ==<br />
This section is '''informative'''.<br />
<br />
The following sites have implemented hCalendar, and thus are a great place to start for anyone looking for examples &quot;in the wild&quot; to try parsing, indexing, organizing etc. If events on your pages are marked up with hCalendar, 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 />
=== New Examples ===<br />
Please add new examples to this section.<br />
* ...<br />
* [http://www.stateofflux.com/ State of Flux street art site] has started adding events in hCalendar format<br />
* The [http://barcamp.org/#BarCamps BarCamp home page lists upcoming BarCamps marked up with hCalenar] and even has a "Subscribe..." link.<br />
* [http://www.w3.org/2005/12/allgroupoverview.html 2006 W3C Technical Plenary Week] has marked up the schedule and events for the week with hCalendar.<br />
* [http://www.code4lib.org/2006/schedule code4lib Conference 2006 Schedule] is marked up with hCalendar as [http://www.code4lib.org/node/65 announced on their blog].<br />
* [http://grouper.ieee.org/groups/754 IEEE 754 Working Group] - trying hCalendar for upcoming meetings.<br />
* [http://www.pehuen.org/node/494 Elecciones 2005 Chile] - the first spanish language hCalendar event found in the wild.<br />
* [http://www.codewitch.org/it/2005/11/17/no-creative-commons-no-party/ Giocolando » No Creative Commons? No Party!] is marked up with hCalendar<br />
* [http://www.cmprofessionals.org/events/calendar.html CM Pros Events Calendar] by Bob Doyle<br />
* [http://www.midgard-project.org/community/events/ Midgard CMS Event calendar] - as [http://bergie.iki.fi/blog/new-event-calendar-for-midcom.html blogged by Henri Bergius] <br />
* [http://www.iowamilitaryveteransband.com/schedule/ Iowa Military Veterans Band Schedule] - hCalendar markup [http://weblog.randomchaos.com/archive/2005/10/24/Microformats/ added by Scott Reynen]<br />
* [http://www.funfairgames.net/weblog/posts/00000011.html Upcoming events on Jason A.R. Moody Amusements Weblog] posted by Jason Moody on 15 Oct 2005. [http://www.funfairgames.net/weblog/index.html His weblog] in general has hCalendar events posted inside the blog posts.<br />
* [http://tantek.com/microformats/2005/syndicate/tracks-sessions-schedule.html Syndicate - Tracks &amp; Sessions]<br />
* [http://tantek.com/microformats/2005/web2/program.html Web 2.0 Conference schedule page marked up with hCalendar]<br />
* [http://www.thisiscmon.com/ C'MON] is a rock band from Canada, and their [http://www.thisiscmon.com/shows/ tour dates] have been marked up by [http://www.d2digitalmedia.com/ Ray Dickman] with hCalendar.<br />
* [http://ifreebusy.com/ ifreebusy.com] will display freebusy information using hCalendar. See this [http://ifreebusy.com/neiljensen/freebusy/ example].<br />
* [http://we05.com/ Web Essentials 05] has marked up their [http://we05.com/program.cfm program schedule table with hCalendar], using the 'axis' and 'headers' attributes.<br />
* [http://www.asdvbonaparte.nl/ ASDV Bonaparte] is a Dutch debating society. Their events calendar has been marked up with the hCalendar conventions.<br />
* [http://chocnvodka.blogware.com/blog Suw Charman] has marked up [http://suw.org.uk/archives/category/events/ her events] with hCalendar.<br />
* [http://www.blogbusinesssummit.com/ Blog Business Summit] has published their [http://www.blogbusinesssummit.com/details.htm event details] marked up with hCalendar.<br />
* [http://evdb.com EVDB], the Events and Venues database, publishes all events with hCalendar and venues with [[hcard|hCard]]. Took them only 15 minutes to implement both!<br />
* [http://upcoming.org Upcoming.org] publishes all events and lists of events with hCalendar. Took them only an hour to add hCalendar support to the site.<br />
* The [http://laughingsquid.com/squidlist/calendar/ Laughing Squid Calendar] events, [http://laughingsquid.com/squidlist/calendar/9949/2005/5/9 e.g. this party], now supports hCalendar.<br />
* [http://paulschreiber.com/ Paul] Schreiber's [http://concerts.shrub.ca/ Sunnyvale House Concerts] site publishes hCalendar event information for upcoming concerts. In addition the [http://concerts.shrub.ca/shows Past Shows] page contains hCalendar events for all past concerts.<br />
* [http://paulschreiber.com/ Paul] Schreiber's [http://iceoasis.shrub.ca/ unofficial schedule site] publishes hCalendar information for upcoming hockey games at [http://www.iceoasis.com/ Ice Oasis]<br />
* [http://www.complexspiral.com/ Complex Spiral Consulting], both in the &quot;Events&quot; box on left side, and the separate [http://www.complexspiral.com/events/ Events page]. <br />
* [http://tantek.com/log Tantek's Thoughts], specifically the &quot;Events&quot; roll in the right-most column.<br />
* [http://suda.co.uk/projects/holidays/ Lesser Known Holidays], a list of holidays on [http://suda.co.uk suda.co.uk] that can be imported via iCal and hCal so you can compare actual transformation versus intended.<br />
* [http://norman.walsh.name/2005/itinerary/ Norm Walsh's travel schedule] use hCalendar as well as GRDDL.<br />
* [http://www.policyawareweb.org/2005/ftf2/paw-mtg Policy Aware Web (PAW) Project Meeting] uses hCalendar to record date-related decisions, and uses a vtodo microformat to record action items.<br />
* The [http://www.kiez-ev.de/ Kiez] is a small cinema and has published its [http://www.kiez-ev.de/programm.htm program] marked up with hCalendar.<br />
* The [http://lufgi4.informatik.rwth-aachen.de Laboratory for Dependable Distributed Systems] publishes it's [http://lufgi4.informatik.rwth-aachen.de/cfps list of notable CfPs on dependability and security] with hCalendar-todo elements.<br />
* The [http://laughingsquid.com/laughing-squid-10th-anniversary-party/ Laughing Squid 10th Anniversary Party] has an hcalendar page.<br />
* SPRACI has hcalendar versions of its nightlife/clubbing/gigs/festivals listings for many cities worldwide - eg: [http://www.spraci.com/listhcalendar.php?parea=sydney&category=all Events in Sydney] (check the [http://www.spraci.com/api/ API] pages in the faq section of [http://www.spraci.com/ SPRACI] for more info about the area/city keywords and category tags to use to get data for your city/categories<br />
<br />
=== Examples with some problems ===<br />
* [http://www.webanalyticsassociation.org/en/calendarevents/search.asp Web Analytics Association] - hCalendar microformat is in place on all Tendenci sites on the calendar events search page and consolidated list page.<br />
** WARNINGS<br />
*** has only dates where there should be datetime's<br />
*** has abbr's with no title<br />
*** should probably markup the description --[[User:RyanKing|RyanKing]] 16:04, 6 Jan 2006 (PST)<br />
* [http://www.bokle.de/ s'Bokle] is a German music pub. Their events calendar has been marked up with hCalendar.<br />
** improper use of rrule --[[User:RyanKing|RyanKing]] 16:04, 6 Jan 2006 (PST)<br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
The following implementations have been developed which either generate or parse hCalendars. If you have an hCalendar 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 />
=== Generation ===<br />
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCalendar and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].<br />
* [http://www.midgard-project.org/documentation/net-nemein-calendar/ Midgard CMS - net.nemein.calendar] - as [http://bergie.iki.fi/blog/new-event-calendar-for-midcom.html blogged by Henri Bergius] <br />
* [http://www.decafbad.com/blog/2005/06/08/greasemonkey_magic magic_hcalendar Greasemonkey user script by Les Orchard] - allows easy form entry of an event into any textarea, e.g. into a blog post text area.<br />
* [http://microformats.org/code/hcalendar/creator microformats.org hCalendar creator]<br />
* [http://hybernaut.com/upcoming-hcal Drupal Upcoming.org syndication module emits hCalendar]<br />
* [http://theryanking.com/ Ryan King] has an [http://theryanking.com/microformats/hcalendar-creator.html hCalendar creator].<br />
<br />
=== Conversion and consumption ===<br />
* [http://blog.codeeg.com/tails-firefox-extension/ Tails is a Firefox Extension] that will display the presence of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage.<br />
* In [http://www.xfytec.com/community/ xfy Community], there are some hCalendar implementations. "hCalendar via RSS" parses an RSS feed, retrieves XHTML documents linked from that feed, and syndicates hCalendars into a calendar view.<br />
* [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats simple hCalendar parser] by [http://virtuelvis.com/ Arve Bersvendsen]<br />
* [http://george.hotelling.net/90percent/ George] has built a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script that detects hCalendar events and allows users to easily add them to their calendar application(s)].<br />
* [http://blogmatrix.blogmatrix.com/ David Janes] has produced a [[Greasemonkey]] [http://www.blogmatrix.com/include/microformat-find.user.js script] that finds many microformat elements, including hCalendar events, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. The hCalendar to vCalendar conversion is done internally within the script. ''This does not work with FireFox 1.5+/GreaseMonkey 0.6.4+.''<br />
* [http://suda.co.uk/projects/X2V/ X2V] parses hCalendar and produces a .ics (iCalendar) stream. Note: needs to be updated to track changes in the specification as they occur.<br />
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] by [[User:DanC]] includes toICal.xsl and test materials; it works much like xhtml2vcal.xsl in X2V. See also: [http://www.w3.org/2002/12/cal/ RDF Calendar workspace] with icalendar test materials.<br />
* [http://web.mit.edu/glasser/www/JSCalendar/ JSCalendar] parses hCalendar and produces a displayable HTML table/CSS-based calendar.<br />
<br />
Investigation:<br />
* [http://wiki.mozilla.org/Calendar_Talk:Lightning#hCalendar_publish_and_subscribe_support Mozilla Calendar / Lightning / Sunbird hCalendar support discussion]<br />
<br />
=== Potential implementations ===<br />
<br />
These are open source projects that could be potentially enhanced to support hCalendar.<br />
<br />
* [http://www.k5n.us/webcalendar.php?topic=About WebCalendar]<br />
* [http://phpicalendar.net/documentation/index.php?title=Main_Page PHP iCalendar]<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]<br />
* [[hcard|hCard]]<br />
* [http://www.ietf.org/rfc/rfc2445.txt iCalendar RFC2445]<br />
<br />
=== Informative References ===<br />
* [http://w3.org/TR/REC-CSS1 CSS1]<br />
* [http://tantek.com/log/2004/09.html#hcalendar hCalendar term introduced and defined on the Web, 20040930]<br />
* [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation, 20040911]<br />
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]<br />
* [http://www.ietf.org/internet-drafts/draft-royer-ical-basic-02.txt iCal-Basic draft 02]<br />
* Contributed from http://developers.technorati.com/wiki/hCalendar<br />
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]<br />
<br />
==== Related ====<br />
* [[icalendar-implementations|iCalendar implementations]]<br />
* [http://lists.osafoundation.org/pipermail/ietf-calsify/ IETF-calsify archives]<br />
* [http://www.livejournal.com/users/jwz/444651.html jwz - Hula] (required reading)<br />
* [http://www.jwz.org/doc/groupware.html Groupware Bad by Jamie Zawinski] crystalizes the reason for hCalendar ('''emphasis''' added):<br />
<blockquote>&quot;Right now people can do that by publishing .ics files, but it's not trivial to do so, and it's work on the part of other people to look at them. '''If it's not HTML hanging off our friend's home page that can be viewed in any browser on a public terminal in a library, the bar to entry is too high and it's useless.'''&quot;</blockquote><br />
<br />
* [http://muddybranch.thejkgroup.com/ Jason Klemow's blog]<br />
* [http://www.softwarestudio.org/iCal/2445Issues.html RFC2445 Issues List]<br />
* [http://ietf.webdav.org/calsify/ CALSIFY WG Links And Resources]<br />
<br />
=== Similar Work ===<br />
* [[XOXO]]<br />
<br />
== Discussions ==<br />
<br />
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. There is a separate document where we are keeping our brainstorms and other explorations relating to hCalendar:<br />
<br />
* [[hcalendar-brainstorming]]<br />
<br />
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
** [http://weblog.infoworld.com/udell/2006/01/11.html#a1368 Moving forward with microformats] by [http://weblog.infoworld.com/udell Jon Udell] provides an hCalendar example and some discussion.<br />
<br />
=== Q&A ===<br />
* If you have any questions about hCalendar, check the [[hcalendar-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 [[hcalendar-issues]] document.</div>Mark Mansourhttp://microformats.org/wiki/index.php?title=hcalendar-examples&diff=4201hcalendar-examples2006-01-05T16:02:46Z<p>Mark Mansour: </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</strong>.</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: ''the attendee markup looks incomplete''<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><br />
<li class="category">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><br />
<li class="category">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><br />
<li class="category">Meeting</li><br />
<li class="category">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><br />
<li class="category">Meeting</li><br />
<li class="category">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: [ftp://xyzCorp.com/pub/conf/bkgrnd.ps ftp://xyzCorp.com/pub/conf/bkgrnd.ps]</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><br />
<li class="category">Project Report</li><br />
<li class="category">xyz</li><br />
<li class="category">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><br />
<li class="category">Project Report</li><br />
<li class="category">xyz</li><br />
<li class="category">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 />
<div class="vcalendar"><br />
<div>Version: <span class="version">2.0</span></div><br />
<div>ProdID:<span class="prodid">-//RDU Software//NONSGML HandCal//EN</span></div><br />
<div class="vfreebusy"><br />
<div>Organizer: <span class="organizer">MAILTO:jsmith@host.com</span></div><br />
<div>Start Time: <abbr class="dtstart" title="19980313T141711Z">March 13, 1998 14:17:11 UTC</abbr></div><br />
<div>End time: <abbr class="dtend" title="19980410T141711Z">April 10, 1998 14:17:11 UTC</abbr></div><br />
<p>Busy times:</p> <!-- note that the default is BUSY --><br />
<ol><br />
<li class="freebusy"><abbr class="dtstart" title="19980314T233000Z">1998-03-14 23:30:00 UTC</abbr> - <abbr class="dtend" title="19980315T003000Z">1998-03-15- 00:30:00 UTC</abbr></li><br />
<li class="freebusy"><abbr class="dtstart" title="19980316T153000Z">1998-03-16 15:30:00 UTC</abbr> - <abbr class="dtend" title="19980316T163000Z">1998-03-16 16:30:00 UTC</abbr></li><br />
<li class="freebusy"><abbr class="dtstart" title="19980318T030000Z">1998-03-18 03:00:00 UTC</abbr> - <abbr class="dtend" title="19980318T040000Z">1998-03-18 04:00:00 UTC</abbr></li><br />
</ol><br />
<div>URL <a class="url" href="http://www.host.com/calendar/busytime/jsmith.ifb">http://www.host.com/calendar/busytime/jsmith.ifb</a></div><br />
</div><br />
</div><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>Mark Mansourhttp://microformats.org/wiki/index.php?title=hcalendar-examples&diff=3920hcalendar-examples2006-01-05T11:15:31Z<p>Mark Mansour: </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</strong>.</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: ''the attendee markup looks incomplete''<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><br />
<li class="category">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><br />
<li class="category">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><br />
<li class="category">Meeting</li><br />
<li class="category">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><br />
<li class="category">Meeting</li><br />
<li class="category">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: [ftp://xyzCorp.com/pub/conf/bkgrnd.ps ftp://xyzCorp.com/pub/conf/bkgrnd.ps]</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><br />
<li class="category">Project Report</li><br />
<li class="category">xyz</li><br />
<li class="category">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><br />
<li class="category">Project Report</li><br />
<li class="category">xyz</li><br />
<li class="category">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 />
<div class="vcalendar"><br />
<div>Version: <span class="version">2.0</span></div><br />
<div>ProdID:<span class="prodid">-//RDU Software//NONSGML HandCal//EN</span></div><br />
<div class="vfreebusy"><br />
<div>Organizer: <span class="organizer">:MAILTO:jsmith@host.com</span></div><br />
<div>Start Time: <abbr class="dtstart" title="19980313T141711Z">March 13, 1998 14:17:11 UTC</abbr></div><br />
<div>End time: <abbr class="dtend" title="19980410T141711Z">April 10, 1998 14:17:11 UTC</abbr></div><br />
<p>Busy times:</p> <!-- note that the default is BUSY --><br />
<ol><br />
<li class="freebusy"><abbr class="dtstart" title="19980314T233000Z">1998-03-14 23:30:00 UTC</abbr> - <abbr class="dtend" title="19980315T003000Z">1998-03-15- 00:30:00 UTC</abbr></li><br />
<li class="freebusy"><abbr class="dtstart" title="19980316T153000Z">1998-03-16 15:30:00 UTC</abbr> - <abbr class="dtend" title="19980316T163000Z">1998-03-16 16:30:00 UTC</abbr></li><br />
<li class="freebusy"><abbr class="dtstart" title="19980318T030000Z">1998-03-18 03:00:00 UTC</abbr> - <abbr class="dtend" title="19980318T040000Z">1998-03-18 04:00:00 UTC</abbr></li><br />
</ol><br />
<div>URL <a class="url" href="http://www.host.com/calendar/busytime/jsmith.ifb">http://www.host.com/calendar/busytime/jsmith.ifb</a></div><br />
</div><br />
</div><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>Mark Mansour