<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://microformats.org/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Webf</id>
	<title>Microformats Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://microformats.org/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Webf"/>
	<link rel="alternate" type="text/html" href="http://microformats.org/wiki/Special:Contributions/Webf"/>
	<updated>2026-04-27T03:12:32Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.38.4</generator>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=hcalendar-issues&amp;diff=13043</id>
		<title>hcalendar-issues</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=hcalendar-issues&amp;diff=13043"/>
		<updated>2007-01-21T21:23:54Z</updated>

		<summary type="html">&lt;p&gt;Webf: /* Issues */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= hCalendar Issues =&lt;br /&gt;
&lt;br /&gt;
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]&lt;br /&gt;
&lt;br /&gt;
See related [[hcard-issues]].&lt;br /&gt;
&lt;br /&gt;
== Issues ==&lt;br /&gt;
&lt;br /&gt;
Please use this format:&lt;br /&gt;
* &amp;lt;nowiki&amp;gt;{{OpenIssue}}&amp;lt;/nowiki&amp;gt; YYYY-MM-DD raised by AUTHORNAME&lt;br /&gt;
*# ''Issue 1: Here is the first issue I have.''&lt;br /&gt;
*# ''Issue 2: Here is the second issue I have.''&lt;br /&gt;
&lt;br /&gt;
And add new issues to the top of the list:&lt;br /&gt;
&lt;br /&gt;
* {{OpenIssue}} 2007-01-20 raised by [[User:AndyMabbett|Andy Mabbett]]&lt;br /&gt;
*# Where &amp;lt;code&amp;gt;DTEND&amp;lt;/code&amp;gt; is a date, and not a date-time, it is required to be the day after the end of the event, thus: &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;2007-04-30&amp;quot;&amp;gt;29 April 2007&amp;lt;/abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;. However, &amp;quot;29 April 2007&amp;quot; is '''''not''''' an abbreviation of 2007-04-30; it is an abbreviation of 2007-04-29. The markup as shown is semantically incorrect and likely to cause problems for users and user-agents which read the title attribute, and not the text value, of the &amp;lt;code&amp;gt;abbr&amp;lt;/code&amp;gt; element.&lt;br /&gt;
&lt;br /&gt;
* {{OpenIssue}} 2007-01-07 raised by [[User:Webf|Webf]]&lt;br /&gt;
*# Looking for a mechanism for specifying a dtstart without using &amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;. Would be used where there are a number of events (as in the [http://www.webfeet.org/events.html Webfeet events lists]) where you do not want to have the visible date repeated&lt;br /&gt;
*#* &amp;lt;code&amp;gt;abbr&amp;lt;/code&amp;gt; is the correct - and only - element to use, unless you wish to display the raw ISO-formatted date-time to the user. Use it with the [[include-pattern]], thus:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;nowiki&amp;gt;&lt;br /&gt;
	&amp;lt;dt id=&amp;quot;D20070120&amp;quot;&amp;gt;&lt;br /&gt;
		&amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;20070120&amp;quot;&amp;gt;&lt;br /&gt;
		Saturday, 20 January 2007&lt;br /&gt;
		&amp;lt;/abbr&amp;gt;&lt;br /&gt;
	&amp;lt;/dt&amp;gt;&lt;br /&gt;
	&amp;lt;dd&amp;gt;&lt;br /&gt;
		&amp;lt;span class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
		&amp;lt;object class=&amp;quot;include&amp;quot; data=&amp;quot;#D20070120&amp;quot;&amp;gt;&amp;lt;/object&amp;gt;&lt;br /&gt;
		[Details of first event]&lt;br /&gt;
		&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
		&amp;lt;span class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
		&amp;lt;object class=&amp;quot;include&amp;quot; data=&amp;quot;#D20070120&amp;quot;&amp;gt;&amp;lt;/object&amp;gt;&lt;br /&gt;
		[Details of second event]&lt;br /&gt;
		&amp;lt;/span&amp;gt;&lt;br /&gt;
	&amp;lt;/dd&amp;gt;&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:but please note that you should validate your HTML - it has over 3,000 errors! The high number of hCalendar microformats (&amp;gt;500) is causing parsers such as Firefox's Tails and Operator to respond very slowly. You should use CSS, not non-breaking spaces and multiple line-breaks, to layout your page - this will reduce it's size and enable parsers to work more quickly. You will need to style &amp;lt;code&amp;gt;object .include&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;display:none&amp;lt;/code&amp;gt; [[User:AndyMabbett|Andy Mabbett]] 04:10, 16 Jan 2007 (PST)&lt;br /&gt;
&lt;br /&gt;
:Thanks Andy!&lt;br /&gt;
:* This use of &amp;lt;code&amp;gt;object&amp;lt;/code&amp;gt; is a proposal at this stage? It does not seem to be mentioned in the [[hCalendar|hCalendar]] page and only marked 'under consideration' in [[include-pattern#Specifications_Using|Include Pattern]]&lt;br /&gt;
:* Re: '&amp;gt;500 entries', I would think that User Agents ''should'' be able to deal with this. The linked page displays a collection of events (not all pages will have so many :-) however I would expect a User Agent to worry mainly about the events visible on the screen (really, a ''small'' part of the whole page). &lt;br /&gt;
:** Brainstorming a little, I would hope that the UA could track an event I've inserted ino my calendar and notice any changes, such as the event being postponed/cancelled, pick up this info and update my calendar. Worth thinking what implications this might bring to the markup.&lt;br /&gt;
:** I'm thinking though that the primary effort with a UA would be making sure the 99.99% pages which ''do not'' include hCalendar markup are not slowed down!&lt;br /&gt;
:* Re: &amp;lt;code&amp;gt;abbr&amp;lt;/code&amp;gt; as the ''only'' way, I can see &amp;lt;code&amp;gt;abbr&amp;lt;/code&amp;gt; used within the [[hCalendar|hCalendar]] page and, yes, it looks a exceptionally neat way of rolling up some markup but I don't see it defined as a mandatory for marking up an event.&lt;br /&gt;
:** Am I missing some rationale? Why is &amp;lt;code&amp;gt;abbr&amp;lt;/code&amp;gt; the ''only'' option?&lt;br /&gt;
:** Should the spec be written up more formally? should hCalendar be more relaxed? My take is that &amp;lt;code&amp;gt;abbr&amp;lt;/code&amp;gt; is OK but it would be wrong for it to be mandatory. Think that screen readers may be reading the expanded content (as with &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr title=&amp;quot;Web Accessibility Initiative&amp;quot;&amp;gt;WAI&amp;lt;/abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;). The underlying issue is that [[hCalendar|hCalendar]] seems to want &amp;lt;code&amp;gt;abbr&amp;lt;/code&amp;gt; to &amp;lt;em&amp;gt;disambiguate&amp;lt;/em&amp;gt; a displayed date and this is not really the same as an abbreviation. UA's should be liberal when looking for a &amp;lt;code&amp;gt;class=&amp;quot;dtstart&amp;quot;&amp;lt;/code&amp;gt;, after all they &amp;lt;em&amp;gt;do&amp;lt;/em&amp;gt; know that they are within an event markup as they have met the &amp;lt;code&amp;gt;class=&amp;quot;vevent&amp;quot;&amp;lt;/code&amp;gt;....&lt;br /&gt;
:*Feel free to move the above thoughts to a brainstorming area. I might come back to the other points later - but maybe better in a talk page. :-) [[User:Webf|Webf]] 13:23, 21 Jan 2007 (PST)&lt;br /&gt;
&lt;br /&gt;
* {{OpenIssue}} 2006-10-21 raised by [[User:AndyMabbett|AndyMabbett]]&lt;br /&gt;
*# there should be some way to say that the URL of an hCard or hCalendar event is the URL of the page itself, without having to include a redundant, and accessibility-damaging link to that page, on &lt;br /&gt;
the page itself.&lt;br /&gt;
&lt;br /&gt;
* {{OpenIssue}} 2006-09-22 raised by [[User:AndyMabbett|AndyMabbett]]&lt;br /&gt;
*# How are Julian dates to be displayed? So far as I am aware, ISO8601 has no facility for marking up Julian dates, so should the form &amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;[Gregorian date]&amp;quot;&amp;gt;[Julian date]&amp;lt;/abbr&amp;gt; &amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt; be used? If so, that should be indicated, via an example.&lt;br /&gt;
&lt;br /&gt;
* {{OpenIssue}} 2006-08-14 raised by [[User:Elias|Elias Sinderson]]&lt;br /&gt;
*# ''Issue 1: Although ISO 8601 allows both basic (sans delimiters) and extended formats, the extended format (where hyphens and colons are explicitly added) is broadly preferred for the web. While RFC 2445 specifies that the basic form be used in in iCalendar date / time fields, the W3C has published a technical [http://www.w3.org/TR/NOTE-datetime note] (submitted by Reuters), which recommends that the extended (delimited) format be used, and the [http://www.w3.org/TR/html401/types.html#h-6.11 HTML 4.0 spec] uses the extended format. Further, RFC 3339 defines a ISO 8601 profile for dates and time representations on the internet that future specs SHOULD use; recommending a fully delimited representation (see sec. 5.6). Lastly, it should be noted that the [http://www.w3.org/TR/xmlschema-2/#date xsd:date] and [http://www.w3.org/TR/xmlschema-2/#dateTime xsd:dateTime] types are specified as being the ISO 8601 extended format. So, given that hCalendar is based on iCalendar, it is understandable that it allows both formats, however this is clearly a case in which it would be very reasonable to require users to upconvert the format into the least ambiguous and most easily parsed / validated representation. Think of the children.&lt;br /&gt;
&lt;br /&gt;
* {{OpenIssue}} 2006-03-07 raised by [[User:Ragdoll|Justin McDowell]]&lt;br /&gt;
*# ''Issue 1: I'd love to see a Property List, similar to what is seen in the hCard spec, that lists all the available properties and sub-properties in a nice, compact list. This saves a lot of time and is really useful for quickly and easily getting aquainted with the possibilities of vCalendar.''&lt;br /&gt;
&lt;br /&gt;
* 2006-02-17 raised by [[User:Mark Mansour|Mark Mansour]] - notes are summarized [[hcalendar-irc-meetup-20060225|here]]&lt;br /&gt;
*# Should vcalendar be a class?  Section 4.4 of RFC2445 says: &amp;quot;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.&amp;quot;  Also the vcalendar class would allow properties on the calendar itself such as METHOD and CALSCALE (I don't think VERSION and PRODID are particularly relevant).&lt;br /&gt;
*#* ACCEPTED SPECUPDATE/FAQ.  Is this a case of fixing something that isn't broken?  Note that &amp;quot;iCalendar object&amp;quot; != &amp;quot;vcalendar&amp;quot;.  This is a bit confusing so read RFC 2445 carefully in that regard.  In addition, the [[hcalendar|hCalendar]] spec should say *precisely* how to generate VCALENDAR properties in their absence.&lt;br /&gt;
*# How are axis and headers going to be handled?&lt;br /&gt;
*#* ACCEPTED.  This is documented in [[hcalendar-brainstorming]] but MUST be moved to [[hcalendar|hCalendar]] proper as the editors and implementers have all agreed on it (months ago). Add this as a [[to-do]] for Tantek.&lt;br /&gt;
*# 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?&lt;br /&gt;
*#* REJECTED. Please RTFM.  Searching the [[hcalendar|hCalendar]] spec for *either* &amp;quot;axis&amp;quot; or &amp;quot;headers&amp;quot; would have found the following example in the wild:  [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.&lt;br /&gt;
*# 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).&lt;br /&gt;
*#* ACCEPTED SPECUPDATE/FAQ. Another [[to-do]] for Tantek.  Explicitly specify which additional iCalendar objects (in addition to VEVENT) are permitted in hCalendar.  Current additional candidates: VTODO (many examples of this info on the web), VFREEBUSY (already at least one site publishing this info), VALARM (maybe, seems harmless enough, but without a compelling real world use case we should probably omit it).  Currently dropping: VTIMEZONE (terrible construct), VJOURNAL (obsoleted by [[hatom|hAtom]]).&lt;br /&gt;
*# 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?&lt;br /&gt;
*#* ACCEPT PARTIAL.  We probably need an hCalendar ''validator'' before we can declare any set of tests to be official.&lt;br /&gt;
*# 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. &lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;a name=&amp;quot;myfrag&amp;quot;&amp;gt;heading&amp;lt;/a&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;div class=&amp;quot;description&amp;quot;&amp;gt;A nice event&amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;2005-10-05&amp;quot;&amp;gt;October 5&amp;lt;/abbr&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
*#* ACCEPTED. We should clarify to converters how to interpret a fragement id.  The interpretations are all consistent.  It points to the element that is to be converted.  If that element is empty then so is the conversion.  There is no issue here other than a need for more documentation.&lt;br /&gt;
* 2006-02-01 raised by [[RyanKing]]&lt;br /&gt;
*# ''Issue 1: Given that now, or soon will have hAtom, should we disallow vJournal, so that we don't have 2 blog-post formats?''&lt;br /&gt;
*#* ACCEPTED.  Yes, we should expliclty DROP &amp;quot;vjournal&amp;quot; from [[hcalendar|hCalendar]].&lt;br /&gt;
* 2006-01-04 raised by [[User:CGranade|CGranade]]&lt;br /&gt;
*# ''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 &amp;lt;code&amp;gt;class&amp;lt;/code&amp;gt; attribute is ''not'' portable across schemas.''&lt;br /&gt;
*#* 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.&lt;br /&gt;
*# ''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.''&lt;br /&gt;
*#* ACCEPTED.  This is definitely something to be added to *-examples pages for each microformat.&lt;br /&gt;
* 2005-10-14 raised by [[User:MarkoMrdjenovic|MarkoMrdjenovic]]&lt;br /&gt;
*# ''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''.&lt;br /&gt;
*#* 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 &amp;quot;@&amp;quot; signs since the issue points out that such UIDs crash some calendaring software.&lt;br /&gt;
*# ''DTSTAMP also has to be present in iCal event for Microsoft Outlook. I think DTSTAMP should be user visible information so implementation with class=&amp;quot;dtstamp&amp;quot; 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.'' [Suggestion:] why not set DTSTAMP to DTSTART if not explicitly defined? -- [[DimitriGlazkov]]&lt;br /&gt;
*#* ACCEPTED.  We should come up with a way to encourage/synthesize/imply DTSTAMP property values.&lt;br /&gt;
*# ''Here is an example from Midgard CMS (which will be easy to change according to bergie on irc):''&lt;br /&gt;
*#* For more discussion of this, please see [http://microformats.org/wiki/hcalendar-brainstorming#UID_handling hCalendar brainstorming: UID handling]&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
  &amp;lt;li class=&amp;quot;vevent&amp;quot; id=&amp;quot;2678c3f94af4a49f9ccbb69b92a82aba-midgardGuid&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;2005-10-20T14:34:45Z&amp;quot;&amp;gt;Torstai 20. Lokakuu 17:34&amp;lt;/abbr&amp;gt; -&lt;br /&gt;
    &amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;2005-10-20T15:33:56Z&amp;quot;&amp;gt;18:33&amp;lt;/abbr&amp;gt;&lt;br /&gt;
    &amp;lt;a class=&amp;quot;url&amp;quot; href=&amp;quot;/bergie/another-calendar/82457028ba83407451edd8aaeaa40622.html&amp;quot;&amp;gt;&lt;br /&gt;
        &amp;lt;span class=&amp;quot;summary&amp;quot;&amp;gt;From the other cal&amp;lt;/span&amp;gt;&lt;br /&gt;
    &amp;lt;/a&amp;gt;&lt;br /&gt;
    &amp;lt;abbr class=&amp;quot;dtstamp&amp;quot; title=&amp;quot;2005-10-14T12:16:45Z&amp;quot;&amp;gt;Torstai 14. Lokakuu 12:16&amp;lt;/abbr&amp;gt;&lt;br /&gt;
  &amp;lt;/li&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
* 2005-09-29 raised by RyanKing&lt;br /&gt;
*# ''How does one use ATTENDEE?''&lt;br /&gt;
*#* ACCEPTED.  Another [[to-do]] for Tantek - document how to use ATTENDEE with [[hcard|hCard]].&lt;br /&gt;
* 2005-07-27 raised by Paolo Massa&lt;br /&gt;
*# ''I tried to add a hcalendar event in my blog but it rendered orribly. The problem was I already have a 'class=&amp;quot;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=&amp;quot;summary&amp;quot; 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 &amp;quot;shield&amp;quot; attribute &amp;quot;inside&amp;quot; microformats from being interpreted as &amp;quot;normal&amp;quot; attributes. For example for the hCalendar microformats the relative CSS could be something like:&lt;br /&gt;
&lt;br /&gt;
.vevent .summary {&lt;br /&gt;
&lt;br /&gt;
//remove all the previously set properties, for example:&lt;br /&gt;
&lt;br /&gt;
text-decoration: none;&lt;br /&gt;
&lt;br /&gt;
font-size: 100%;&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
Since the hCalendar microformat is the following,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;a class=&amp;quot;url&amp;quot; href=&amp;quot;http://www.web2con.com/&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;summary&amp;quot;&amp;gt;Web 2.0 Conference&amp;lt;/span&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
I hope to have been clear but I'm not so sure ;-)''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* 2005-07-21 raised by Neil Jensen &lt;br /&gt;
*# ''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].''&lt;br /&gt;
&lt;br /&gt;
* 2005-07-11 raised by Kragen&lt;br /&gt;
*# ''The specification of class=&amp;quot;url&amp;quot; as &amp;amp;lt;a href=&amp;quot;...&amp;quot;&amp;gt; should be a &amp;quot;should&amp;quot;, not a &amp;quot;must&amp;quot;.  Other ways of referencing the event URL, such as &amp;amp;lt;iframe src=&amp;quot;...&amp;quot;&amp;gt; and &amp;amp;lt;embed src=&amp;quot;...&amp;quot;&amp;gt;, shoul be mentioned.  At present X2V doesn't appear to handle them.  This came up in a discussion about [[xfolk|xFolk]].''&lt;br /&gt;
*#* REJECTED. Lack of use case.  We should not add additional &amp;quot;ways of referencing the event URL&amp;quot; unless you can show a concrete real world example on the Web which requires it.&lt;br /&gt;
&lt;br /&gt;
* 2005-06-21 raised by Hixie&lt;br /&gt;
*# ''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?&lt;br /&gt;
*#* ACCEPTED. Another [[to-do]] for Tantek, write-up [[hcalendar-parsing]] that documents precisely how user agents are to parse [[hcalendar|hCalendar]] markup.&lt;br /&gt;
* 2005-02-22 raised by Matt Raymond [http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2005-February/003124.html on the whatwg list]:&lt;br /&gt;
*# ''There is no copyright statement and no patent statement.''&lt;br /&gt;
*#* ACCEPTED. I have updated [[hcalendar]] (and [[hcard]], and all other MicroFormats) with a standard copyright statement and patent statement.&lt;br /&gt;
&lt;br /&gt;
* 2005-02-18 raised by Matt Raymond [http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2005-February/003116.html on the whatwg list]:&lt;br /&gt;
*# ''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.''&lt;br /&gt;
*#* 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.&lt;br /&gt;
*# ''As a result of the above, user agents would not be able to reliably allow users to access extension properties such as &amp;quot;x-mozilla-alarm-default-length&amp;quot; (which is an actual extension used in Sunbird).''&lt;br /&gt;
*#* REJECTED (out of scope).  Extension properties are outside the current scope of hCalendar.&lt;br /&gt;
*# ''The use of &amp;lt;abbr&amp;gt; for dates is incorrect. &amp;quot;August 5th, 2004&amp;quot; is not the abbreviation of 2004-09-05. In fact, the opposite is closer to the truth.''&lt;br /&gt;
*#* REJECTED (false statement).  This is simply a false statement.  See this article for an explanation of this use of &amp;lt;abbr&amp;gt;: [http://tantek.com/log/2005/01.html#d26t0100 Human vs. ISO8601 dates problem solved]&lt;br /&gt;
*# ''You have to create a complex set of rules for all possible uses of legacy markup within &amp;lt;span class=&amp;quot;vcalendar&amp;quot;&amp;gt; which can easily be implemented incorrectly.''&lt;br /&gt;
*#* 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.&lt;br /&gt;
*# ''There are styling and tooltip issues that are unresolved.''&lt;br /&gt;
*#* 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.&lt;br /&gt;
*# ''hCalendar/hCard is more complicated for webmasters to read and understand and more complicated for developers to implement.''&lt;br /&gt;
*#* REJECTED (empty statements, invalid comparator).  Please state specific examples which show the perceived complexity.  The comparison &amp;quot;more complicated&amp;quot; requires two items, no second item was provided.&lt;br /&gt;
*#  ''I dislike the entire system of using class names as markup.  Class names should be reserved for user-defined semantics.''&lt;br /&gt;
*#* ACCEPT-PARTIAL.  When specific elements are available, they should be used instead of class names, but even then class names work well to &amp;quot;subclass&amp;quot; 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.&lt;br /&gt;
*#* ''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 &amp;quot;User agents may... perform some activity based on known conventions for that profile&amp;quot;?  Should this be a part of [[microformats]] specifications in general?  (If not, why not?)''&lt;br /&gt;
*#** 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.&lt;br /&gt;
*#*** ''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] &amp;quot;This is precisely the reason that GMPG was founded and created, to provide permanent URLs/homes for microformat profiles.&amp;quot; How does one cause GMPG to issue a profile URL?''&lt;br /&gt;
*#**** ACCEPTED. See [[profile-uris]]; this is moving from Tantek's [[to-do]] list, to both provide profiles and URLs (probably at gmpg.org) for those profiles for hCalendar etc.&lt;br /&gt;
* {{OpenIssue}} 2006-04-10 raised by [[User:ScottReynen|Scott Reynen]].&lt;br /&gt;
*# ''When someone looks at the [[hcalendar]] pages, one sees no collection of real-world publishing of event data nor discussion of the properties implied by such examples, I think it's far too easy to infer that microformats come from other formats more than actual behavior.  There's nothing on the [[process]] nor the hcalendar pages explaining this discrepancy.  I would argue that there should be an explanation, probably in both places.''&lt;br /&gt;
* {{OpenIssue}} 2006-04-13 raised by Tantek&lt;br /&gt;
*# ''Need to add a section on &amp;quot;Property Exceptions&amp;quot; like that in [[hcard|hCard]] to document how to publish / handle the '''METHOD''' property and potentially others.  I.e. typically publishers may omit the METHOD property, however, converters whose function is to convert [[hcalendar|hCalendar]] to iCalendar for consumption/subscription by a calendar aggregator, should probably insert a default '''METHOD:PUBLISH''' on the '''VCALENDAR''' object in the resultant .ics stream.''&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
{{hcalendar-related-pages}}&lt;/div&gt;</summary>
		<author><name>Webf</name></author>
	</entry>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=hcalendar-examples-in-wild&amp;diff=12617</id>
		<title>hcalendar-examples-in-wild</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=hcalendar-examples-in-wild&amp;diff=12617"/>
		<updated>2007-01-16T06:25:16Z</updated>

		<summary type="html">&lt;p&gt;Webf: /* Examples with some problems */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt;hCalendar Examples in the wild&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page is an '''informative''' section of the [[hcalendar|hCalendar specification]].&lt;br /&gt;
&lt;br /&gt;
The following sites have published events using [[hcalendar|hCalendar]], and thus are a great place to start for anyone looking for examples &amp;quot;in the wild&amp;quot; to try parsing, indexing, organizing etc.  &lt;br /&gt;
&lt;br /&gt;
If events on your site are marked up with hCalendar, feel free to add it to the top of this list. Please be sure to include at least one URL of a page on your site that includes actual [[hcalendar|hCalendar]] markup. Examples added without the URL of a page with hCalendar markup may be removed.&lt;br /&gt;
&lt;br /&gt;
Want to get started with writing an [[hcalendar|hCalendar]] event? Use the [http://microformats.org/code/hcalendar/creator hCalendar creator] to write up an event and publish it, or follow the [[hcalendar-authoring|hCalendar authoring tips]] to add hCalendar markup to your page of upcoming events or events you mention in blog posts, wikis, etc.&lt;br /&gt;
&lt;br /&gt;
==New Examples==&lt;br /&gt;
Please add new examples to the '''top''' of this section.&lt;br /&gt;
&lt;br /&gt;
* [http://wikevent.org WikEvent] aims to make it as easy as possible to put events on the web with semantic markup, including hCalendar for events and hCard for venues and artists.&lt;br /&gt;
* [http://fundyfilm.ca/calendar/ The Fundy Film Society] uses hCalendar for their calendar of upcoming film screenings.&lt;br /&gt;
* Psychology Press and Routledge's Behavioral Sciences' publishing division have implemented hCalendar on their conferences listings on 17 of their websites (example on the conference listing on their [http://www.clinicalpsychologyarena.com/resources/conferences.asp Clinical Psychology Arena])&lt;br /&gt;
* [http://jhtc.org Jewish High Tech Community] uses hCalendar on event pages.&lt;br /&gt;
*[http://www.gore-tex.com/remote/Satellite?c=fabrics_content_c&amp;amp;cid=1162322807952&amp;amp;pagename=goretex_en_US%2Ffabrics_content_c%2FKnowWhatsInsideDetail Gore-Tex &amp;quot;Know What's Inside&amp;quot;] tour dates in hCalendar by [http://microformats.org/wiki/User:Csarven csarven]&lt;br /&gt;
* [http://finetoothcog.com/site/stolen_bikes Finetoothcog] uses hCalendar to markup when bikes are stolen.&lt;br /&gt;
* [https://www.urbanbody.com/information/contact-us Urban Body Men's Clothing] uses hCalendar for business hours and hCard for business locations.&lt;br /&gt;
* [http://www.infoiasi.ro The website of the Faculty of Computer Science], &amp;quot;A. I. Cuza&amp;quot; University Ia&amp;amp;#351;i, Romania, uses hCalendar to markup events.&lt;br /&gt;
* [http://www.crosbyheritage.co.uk/events/ Colin Crosby Heritage Tours] uses hCalendar to markup events.&lt;br /&gt;
* [http://www.facebook.com Facebook] use hCalendar to markup events.&lt;br /&gt;
* [http://www.newbury-college.ac.uk/ Newbury College UK] uses a smattering of hCalendar and hCard&lt;br /&gt;
* [http://07.pagesd.info/ardeche/agenda.aspx 07.pagesd.info] uses hCalendar and hCard to mark up events of the Ardèche département in France.&lt;br /&gt;
* [http://climbtothestars.org Stephanie Booth] announced the [http://climbtothestars.org/archives/2006/09/14/microformats-et-bloggy-friday-doctobre/ Bloggy Friday for October 2006] using hCalendar.&lt;br /&gt;
* The [http://www.westmidlandbirdclub.com/ West Midland Bird Club], in the English Midlands, uses hCal (with nested hCard) on its [http://www.westmidlandbirdclub.com/diary/ diary of birding events].&lt;br /&gt;
* [http://www.comtec-ars.com/press-releases/ ComTec audience response systems' press releases] use hCalendar as a method to organize  by title and date.&lt;br /&gt;
* [http://webdirections.org/program/ The Web Directions Conference (Sydney Australia)] uses hCalendar for their program. It uses axis and headers for events in a table, and demonstrates how easy it is to make the whole thing downloadable using X2V.&lt;br /&gt;
* [http://www.thestreet.org.au/ The Street Theatre (Canberra, Australia)] now uses hCalendar for performances on its [http://www.thestreet.org.au/whats_on.htm What's On] page.&lt;br /&gt;
* [http://www.clacksweb.org.uk Clackmannanshire Council] uses hCalendar on its [http://www.clacksweb.org.uk/community/events/ event diary] listing pages and individual event pages.&lt;br /&gt;
* [http://www.markthisdate.com/ Calendarportal MarkThisDate.com] now uses hCalendar for all calendars. On our website visitors can add calendars and download calendars to Outlook, Lotus Notes, iCal, Netvibes, 30Boxes, Google Calendar and many others. Over 600 calendars were already uploaded. &lt;br /&gt;
* [http://mogue.jp/ mogue] uses hCalendar at [http://mogue.jp/event/1000/ event detail] pages.&lt;br /&gt;
* [http://www.gustavus.edu/events/nobelconference/2006/schedule.cfm 2006 Nobel Conference] uses hCalendar for the conference schedule&lt;br /&gt;
* [http://www.geekinthepark.co.uk Geek in the Park] uses hCalendar for the event information. -- by [[User:Trovster|trovster]]&lt;br /&gt;
* [http://www.besancon.fr/ official site of Besançon (France)] for its events&lt;br /&gt;
* [http://2006.dconstruct.org/schedule/ Conference schedule for d.Construct 2006] is published using hCalendar.&lt;br /&gt;
* [http://local.yahoo.com Yahoo Local] now supports hCalendar&lt;br /&gt;
* We used hcalendar for the [http://www.fuckparade.org/flyer/2006/ F’parade flyer 2006], a counter demonstration to the Love Parade in Berlin, alas the '''Firefox tails extension''' doesn't get a summary when it's an alt-text in an image.&lt;br /&gt;
* [http://www.harper-adams.ac.uk/press/events.cfm Harper Adams University College] uses hCalendar to mark up all University events on the Homepage and Events Calendar page.&lt;br /&gt;
* [http://www.capital.edu/ Capital University] uses hCalendar on multiple pages to provide feeds of events, relevant to page content&lt;br /&gt;
* [http://www.thesession.org/events/ The Session events] uses hCalendar to mark up concerts, festivals and workshops related to Irish traditional music.&lt;br /&gt;
* [http://rubyandrails.org/usergroups/newcastle ncl.rb] uses hCalendar to mark up new meetings.&lt;br /&gt;
* [http://gross.org.za/calendar GROSSUG Calendar] - Uses hCalendar to mark up meetings and other events.&lt;br /&gt;
* [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.&lt;br /&gt;
* [http://www.tendenci.com/en/calendarevents/search.asp Tendenci Calendar Events] with hCalendar&lt;br /&gt;
* [http://www.argolon.com/2006/04/17/web20-conference-in-dublin/ Web2.0 Conference in Dublin] hCalendar event&lt;br /&gt;
* [http://www.meetup.com/ Meetup.com] has marked up [http://www.meetup.com/cities/us/ny/new_york city event calendars], [http://photo.meetup.com/100/events/ group event lists], and [http://www.meetup.com/ signed-in homepages] with hCalendar.&lt;br /&gt;
* [http://ukwindsurfing.com/ ukwindsurfing.com] has marked upcoming events with hCalendar, and the [http://ukwindsurfing.com/events/ events page] in a table.&lt;br /&gt;
* [http://ocono.com/ ocono.com] has marked up it's &amp;quot;Upcoming Events&amp;quot; list with hCalendar.&lt;br /&gt;
* [http://www.austinbloggers.org/ Austin Bloggers] has marked up their &amp;quot;Upcoming Events&amp;quot; box with hCalendar ([http://www.austinbloggers.org/blog/a/001123.html announcement]).&lt;br /&gt;
* Ning's cloneable Group app has [[hcalendar|hCalendar]] markup on its [http://group.ning.com/index.php?controller=event&amp;amp;action=list event calendar] and [http://group.ning.com/index.php?controller=event&amp;amp;action=view&amp;amp;id=727220 event detail] pages.&lt;br /&gt;
* [http://tantek.com/microformats/2006/03-01-TechPlenAgenda.html Agenda: W3C Technical Plenary Day, March 1 2006] has [[hcard|hCard]] and [[hcalendar|hCalendar]] markup. ([http://www.w3.org/2006/03/01-TechPlenAgenda.html original here]).&lt;br /&gt;
* The National Arbor Day Foundation has started using hCalendars for their [http://arborday.org/programs/conferences/communityforestry/index.cfm upcoming] [http://arborday.org/programs/conferences/hazardtrees-treeplanting/ conferences].&lt;br /&gt;
* [http://www.stateofflux.com/ State of Flux street art site] has started adding events in hCalendar format&lt;br /&gt;
* The [http://barcamp.org/#BarCamps BarCamp home page lists upcoming BarCamps marked up with hCalendar] and even has a &amp;quot;Subscribe...&amp;quot; link.&lt;br /&gt;
* [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.&lt;br /&gt;
* [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].&lt;br /&gt;
* [http://grouper.ieee.org/groups/754 IEEE 754 Working Group] - trying hCalendar for upcoming meetings.&lt;br /&gt;
* [http://www.pehuen.org/node/494  Elecciones 2005 Chile] - the first spanish language hCalendar event found in the wild.&lt;br /&gt;
* [http://www.codewitch.org/it/2005/11/17/no-creative-commons-no-party/ Giocolando » No Creative Commons? No Party!] is marked up with hCalendar&lt;br /&gt;
* [http://www.cmprofessionals.org/events/calendar.html CM Pros Events Calendar] by Bob Doyle&lt;br /&gt;
* [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] &lt;br /&gt;
* [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]&lt;br /&gt;
* [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.&lt;br /&gt;
* [http://tantek.com/microformats/2005/syndicate/tracks-sessions-schedule.html Syndicate - Tracks &amp;amp;amp; Sessions]&lt;br /&gt;
* [http://tantek.com/microformats/2005/web2/program.html Web 2.0 Conference schedule page marked up with hCalendar]&lt;br /&gt;
* [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.&lt;br /&gt;
* [http://ifreebusy.com/ ifreebusy.com] will display freebusy information using hCalendar. See this [http://ifreebusy.com/neiljensen/freebusy/ example].&lt;br /&gt;
* [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.&lt;br /&gt;
* [http://www.asdvbonaparte.nl/ ASDV Bonaparte] is a Dutch debating society. Their events calendar has been marked up with the hCalendar conventions.&lt;br /&gt;
* [http://chocnvodka.blogware.com/blog Suw Charman] has marked up [http://suw.org.uk/archives/category/events/ her events] with hCalendar.&lt;br /&gt;
* [http://www.blogbusinesssummit.com/ Blog Business Summit] has published their [http://www.blogbusinesssummit.com/details.htm event details] marked up with hCalendar.&lt;br /&gt;
* [http://eventful.com Eventful.com] publishes all events with hCalendar and venues with [[hcard|hCard]].  Took them only 15 minutes to implement both! Their Atom feeds also contain hCalendar/hCard.&lt;br /&gt;
* [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.&lt;br /&gt;
* 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.&lt;br /&gt;
* [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.&lt;br /&gt;
* [http://www.complexspiral.com/ Complex Spiral Consulting], both in the &amp;quot;Events&amp;quot; box on left side, and the separate [http://www.complexspiral.com/events/ Events page]. &lt;br /&gt;
* [http://tantek.com/log Tantek's Thoughts], specifically the &amp;quot;Events&amp;quot; roll in the right-most column.&lt;br /&gt;
* [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.&lt;br /&gt;
* [http://norman.walsh.name/2005/itinerary/ Norm Walsh's travel schedule] use hCalendar as well as GRDDL.&lt;br /&gt;
* [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.&lt;br /&gt;
* 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.&lt;br /&gt;
* The [http://laughingsquid.com/laughing-squid-10th-anniversary-party/ Laughing Squid 10th Anniversary Party] has an hcalendar page.&lt;br /&gt;
* SPRACI has hcalendar versions of its nightlife/clubbing/gigs/festivals listings for many cities worldwide - eg: [http://www.spraci.com/listhcalendar.php?parea=sydney&amp;amp;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&lt;br /&gt;
* WWF-Australia events calendars: [http://wwf.org.au/act/events/ What's on], [http://wwf.org.au/act/volunteer/ Volunteer]&lt;br /&gt;
* [http://rubyholic.com rubyholic] uses hCalendar to publish calendars for ruby groups.&lt;br /&gt;
* [http://www.bath.ac.uk/whats-on/ University of Bath What's On] uses hCalendar on individual event pages&lt;br /&gt;
* The [http://www.kiez-ev.de/ Kiez] is a small cinema and has published its [http://www.kiez-ev.de/programm program] marked up with hCalendar&lt;br /&gt;
&lt;br /&gt;
===World Cup Kick-off===&lt;br /&gt;
* [http://www.worldcupkickoff.com/ World Cup KickOff] where you can download and keep all the fixtures you are interested in so you will never miss a single game of the 2006 football World Cup!&lt;br /&gt;
** This link was on the [http://www.lifehacker.com/software/sports/world-cup-start-times-for-ical-etc-175393.php Lifehackers site] and made its way to the yahoo news site:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&lt;br /&gt;
Mon May 22, 4:00 PM ET&lt;br /&gt;
The World Cup, one of the world's most watched sporting events, is almost upon us. If you've ever tried to follow your favorite team through the Cup you know that it can sometimes be difficult to know when they're on. World Cup Kickoff can help.&lt;br /&gt;
&lt;br /&gt;
World Cup KickOff is all you will ever need for knowing all the match details for the upcoming World Cup 2006. Whether you use your mobile phone, MS Outlook, Apple iCal or Mozilla Calendar, you can download and keep all the fixtures you are interested in so you will never miss a single game!&lt;br /&gt;
&lt;br /&gt;
Next tip? We'll show you how to get up at 2 AM to watch your matches. ;0) Thanks to Tom for the tip!&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Examples with some problems==&lt;br /&gt;
&lt;br /&gt;
Entries may be moved here if there's a problem with the way hCalendar is used on the page concerned. If the page is yours, and you want to improve it, see the [[hcalendar-faq|hCalendar FAQ]], or raise any queries on [[hcalendar-issues|hCalendar Issues]] or [[mailing-lists#microformats-discuss|the mailing list]], where people will be happy to help you. &lt;br /&gt;
&lt;br /&gt;
* [http://www.webfeet.org/events.html Webfeet events] includes hCalendar markup in its aggregated events lists.&lt;br /&gt;
** &amp;lt;s&amp;gt;Possibly a case where &amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt; won't work for dtstart/dtend as there are many events listed under a single date. [[User:Webf|Webf]] 15:19, 15 Jan 2007 (PST)&amp;lt;/s&amp;gt;&lt;br /&gt;
**Malformed e.g &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;span class=&amp;quot;dtstart&amp;quot; title=&amp;quot;20070120&amp;quot;&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; [[User:AndyMabbett|Andy Mabbett]] 15:41, 15 Jan 2007 (PST)&lt;br /&gt;
** Continue the discussion under [[hcalendar-issues|hCalendar Issues]] perhaps. [[User:Webf|Webf]] 22:25, 15 Jan 2007 (PST)&lt;br /&gt;
* [http://www.theatrestudies.llc.ed.ac.uk/ Theatre Studies: European Theatre] at the University of Edinburgh uses hCalendar to markup news and events on the index page.&lt;br /&gt;
**Uses &amp;quot;display:none&amp;quot; on image. [[User:AndyMabbett|Andy Mabbett]] 15:32, 13 Nov 2006 (PST)&lt;br /&gt;
* [http://www.bokle.de/ s'Bokle] is a German music pub. Their events calendar has been marked up with hCalendar.&lt;br /&gt;
** improper use of rrule --[[User:RyanKing|RyanKing]] 16:04, 6 Jan 2006 (PST)&lt;br /&gt;
* [http://plan9.tryphon.org/nancy/list Plan9] - Uses hCalendar to mark up events !&lt;br /&gt;
** dtstart/dtend are implemented on span element [[User:TomArmitage|Tom Armitage]] June 23, 2006&lt;br /&gt;
* [http://www.socaltech.com socalTECH] is a news and information site. Their front page event listing is marked up with hCalendar.&lt;br /&gt;
** dtstart/dtend implemented on span element [[User:TomArmitage|Tom Armitage]] June 23, 2006&lt;br /&gt;
* [http://www.multipack.co.uk The Multipack] features a vevent for the next meeting information.&lt;br /&gt;
** dtstart/dtend are implemented on em element [[User:TomArmitage|Tom Armitage]] June 23, 2006&lt;br /&gt;
* [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]&lt;br /&gt;
** dtstart/dtend are implemented on td element [[User:TomArmitage|Tom Armitage]] June 23, 2006&lt;br /&gt;
&lt;br /&gt;
- whilst Tails parses dtstart/dtend on &amp;lt;em&amp;gt;any&amp;lt;/em&amp;gt; element, technically it really needs to be on abbr. Technorati Microformats Search only looks for the title element on &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; tags, for instance.&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
{{hcalendar-related-pages}}&lt;/div&gt;</summary>
		<author><name>Webf</name></author>
	</entry>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=hcalendar-examples-in-wild&amp;diff=12541</id>
		<title>hcalendar-examples-in-wild</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=hcalendar-examples-in-wild&amp;diff=12541"/>
		<updated>2007-01-15T23:19:18Z</updated>

		<summary type="html">&lt;p&gt;Webf: /* Examples with some problems */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h1&amp;gt;hCalendar Examples in the wild&amp;lt;/h1&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page is an '''informative''' section of the [[hcalendar|hCalendar specification]].&lt;br /&gt;
&lt;br /&gt;
The following sites have published events using [[hcalendar|hCalendar]], and thus are a great place to start for anyone looking for examples &amp;quot;in the wild&amp;quot; to try parsing, indexing, organizing etc.  &lt;br /&gt;
&lt;br /&gt;
If events on your site are marked up with hCalendar, feel free to add it to the top of this list. Please be sure to include at least one URL of a page on your site that includes actual [[hcalendar|hCalendar]] markup. Examples added without the URL of a page with hCalendar markup may be removed.&lt;br /&gt;
&lt;br /&gt;
Want to get started with writing an [[hcalendar|hCalendar]] event? Use the [http://microformats.org/code/hcalendar/creator hCalendar creator] to write up an event and publish it, or follow the [[hcalendar-authoring|hCalendar authoring tips]] to add hCalendar markup to your page of upcoming events or events you mention in blog posts, wikis, etc.&lt;br /&gt;
&lt;br /&gt;
==New Examples==&lt;br /&gt;
Please add new examples to the '''top''' of this section.&lt;br /&gt;
&lt;br /&gt;
* [http://wikevent.org WikEvent] aims to make it as easy as possible to put events on the web with semantic markup, including hCalendar for events and hCard for venues and artists.&lt;br /&gt;
* [http://fundyfilm.ca/calendar/ The Fundy Film Society] uses hCalendar for their calendar of upcoming film screenings.&lt;br /&gt;
* Psychology Press and Routledge's Behavioral Sciences' publishing division have implemented hCalendar on their conferences listings on 17 of their websites (example on the conference listing on their [http://www.clinicalpsychologyarena.com/resources/conferences.asp Clinical Psychology Arena])&lt;br /&gt;
* [http://jhtc.org Jewish High Tech Community] uses hCalendar on event pages.&lt;br /&gt;
*[http://www.gore-tex.com/remote/Satellite?c=fabrics_content_c&amp;amp;cid=1162322807952&amp;amp;pagename=goretex_en_US%2Ffabrics_content_c%2FKnowWhatsInsideDetail Gore-Tex &amp;quot;Know What's Inside&amp;quot;] tour dates in hCalendar by [http://microformats.org/wiki/User:Csarven csarven]&lt;br /&gt;
* [http://finetoothcog.com/site/stolen_bikes Finetoothcog] uses hCalendar to markup when bikes are stolen.&lt;br /&gt;
* [https://www.urbanbody.com/information/contact-us Urban Body Men's Clothing] uses hCalendar for business hours and hCard for business locations.&lt;br /&gt;
* [http://www.infoiasi.ro The website of the Faculty of Computer Science], &amp;quot;A. I. Cuza&amp;quot; University Ia&amp;amp;#351;i, Romania, uses hCalendar to markup events.&lt;br /&gt;
* [http://www.crosbyheritage.co.uk/events/ Colin Crosby Heritage Tours] uses hCalendar to markup events.&lt;br /&gt;
* [http://www.facebook.com Facebook] use hCalendar to markup events.&lt;br /&gt;
* [http://www.newbury-college.ac.uk/ Newbury College UK] uses a smattering of hCalendar and hCard&lt;br /&gt;
* [http://07.pagesd.info/ardeche/agenda.aspx 07.pagesd.info] uses hCalendar and hCard to mark up events of the Ardèche département in France.&lt;br /&gt;
* [http://climbtothestars.org Stephanie Booth] announced the [http://climbtothestars.org/archives/2006/09/14/microformats-et-bloggy-friday-doctobre/ Bloggy Friday for October 2006] using hCalendar.&lt;br /&gt;
* The [http://www.westmidlandbirdclub.com/ West Midland Bird Club], in the English Midlands, uses hCal (with nested hCard) on its [http://www.westmidlandbirdclub.com/diary/ diary of birding events].&lt;br /&gt;
* [http://www.comtec-ars.com/press-releases/ ComTec audience response systems' press releases] use hCalendar as a method to organize  by title and date.&lt;br /&gt;
* [http://webdirections.org/program/ The Web Directions Conference (Sydney Australia)] uses hCalendar for their program. It uses axis and headers for events in a table, and demonstrates how easy it is to make the whole thing downloadable using X2V.&lt;br /&gt;
* [http://www.thestreet.org.au/ The Street Theatre (Canberra, Australia)] now uses hCalendar for performances on its [http://www.thestreet.org.au/whats_on.htm What's On] page.&lt;br /&gt;
* [http://www.clacksweb.org.uk Clackmannanshire Council] uses hCalendar on its [http://www.clacksweb.org.uk/community/events/ event diary] listing pages and individual event pages.&lt;br /&gt;
* [http://www.markthisdate.com/ Calendarportal MarkThisDate.com] now uses hCalendar for all calendars. On our website visitors can add calendars and download calendars to Outlook, Lotus Notes, iCal, Netvibes, 30Boxes, Google Calendar and many others. Over 600 calendars were already uploaded. &lt;br /&gt;
* [http://mogue.jp/ mogue] uses hCalendar at [http://mogue.jp/event/1000/ event detail] pages.&lt;br /&gt;
* [http://www.gustavus.edu/events/nobelconference/2006/schedule.cfm 2006 Nobel Conference] uses hCalendar for the conference schedule&lt;br /&gt;
* [http://www.geekinthepark.co.uk Geek in the Park] uses hCalendar for the event information. -- by [[User:Trovster|trovster]]&lt;br /&gt;
* [http://www.besancon.fr/ official site of Besançon (France)] for its events&lt;br /&gt;
* [http://2006.dconstruct.org/schedule/ Conference schedule for d.Construct 2006] is published using hCalendar.&lt;br /&gt;
* [http://local.yahoo.com Yahoo Local] now supports hCalendar&lt;br /&gt;
* We used hcalendar for the [http://www.fuckparade.org/flyer/2006/ F’parade flyer 2006], a counter demonstration to the Love Parade in Berlin, alas the '''Firefox tails extension''' doesn't get a summary when it's an alt-text in an image.&lt;br /&gt;
* [http://www.harper-adams.ac.uk/press/events.cfm Harper Adams University College] uses hCalendar to mark up all University events on the Homepage and Events Calendar page.&lt;br /&gt;
* [http://www.capital.edu/ Capital University] uses hCalendar on multiple pages to provide feeds of events, relevant to page content&lt;br /&gt;
* [http://www.thesession.org/events/ The Session events] uses hCalendar to mark up concerts, festivals and workshops related to Irish traditional music.&lt;br /&gt;
* [http://rubyandrails.org/usergroups/newcastle ncl.rb] uses hCalendar to mark up new meetings.&lt;br /&gt;
* [http://gross.org.za/calendar GROSSUG Calendar] - Uses hCalendar to mark up meetings and other events.&lt;br /&gt;
* [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.&lt;br /&gt;
* [http://www.tendenci.com/en/calendarevents/search.asp Tendenci Calendar Events] with hCalendar&lt;br /&gt;
* [http://www.argolon.com/2006/04/17/web20-conference-in-dublin/ Web2.0 Conference in Dublin] hCalendar event&lt;br /&gt;
* [http://www.meetup.com/ Meetup.com] has marked up [http://www.meetup.com/cities/us/ny/new_york city event calendars], [http://photo.meetup.com/100/events/ group event lists], and [http://www.meetup.com/ signed-in homepages] with hCalendar.&lt;br /&gt;
* [http://ukwindsurfing.com/ ukwindsurfing.com] has marked upcoming events with hCalendar, and the [http://ukwindsurfing.com/events/ events page] in a table.&lt;br /&gt;
* [http://ocono.com/ ocono.com] has marked up it's &amp;quot;Upcoming Events&amp;quot; list with hCalendar.&lt;br /&gt;
* [http://www.austinbloggers.org/ Austin Bloggers] has marked up their &amp;quot;Upcoming Events&amp;quot; box with hCalendar ([http://www.austinbloggers.org/blog/a/001123.html announcement]).&lt;br /&gt;
* Ning's cloneable Group app has [[hcalendar|hCalendar]] markup on its [http://group.ning.com/index.php?controller=event&amp;amp;action=list event calendar] and [http://group.ning.com/index.php?controller=event&amp;amp;action=view&amp;amp;id=727220 event detail] pages.&lt;br /&gt;
* [http://tantek.com/microformats/2006/03-01-TechPlenAgenda.html Agenda: W3C Technical Plenary Day, March 1 2006] has [[hcard|hCard]] and [[hcalendar|hCalendar]] markup. ([http://www.w3.org/2006/03/01-TechPlenAgenda.html original here]).&lt;br /&gt;
* The National Arbor Day Foundation has started using hCalendars for their [http://arborday.org/programs/conferences/communityforestry/index.cfm upcoming] [http://arborday.org/programs/conferences/hazardtrees-treeplanting/ conferences].&lt;br /&gt;
* [http://www.stateofflux.com/ State of Flux street art site] has started adding events in hCalendar format&lt;br /&gt;
* The [http://barcamp.org/#BarCamps BarCamp home page lists upcoming BarCamps marked up with hCalendar] and even has a &amp;quot;Subscribe...&amp;quot; link.&lt;br /&gt;
* [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.&lt;br /&gt;
* [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].&lt;br /&gt;
* [http://grouper.ieee.org/groups/754 IEEE 754 Working Group] - trying hCalendar for upcoming meetings.&lt;br /&gt;
* [http://www.pehuen.org/node/494  Elecciones 2005 Chile] - the first spanish language hCalendar event found in the wild.&lt;br /&gt;
* [http://www.codewitch.org/it/2005/11/17/no-creative-commons-no-party/ Giocolando » No Creative Commons? No Party!] is marked up with hCalendar&lt;br /&gt;
* [http://www.cmprofessionals.org/events/calendar.html CM Pros Events Calendar] by Bob Doyle&lt;br /&gt;
* [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] &lt;br /&gt;
* [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]&lt;br /&gt;
* [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.&lt;br /&gt;
* [http://tantek.com/microformats/2005/syndicate/tracks-sessions-schedule.html Syndicate - Tracks &amp;amp;amp; Sessions]&lt;br /&gt;
* [http://tantek.com/microformats/2005/web2/program.html Web 2.0 Conference schedule page marked up with hCalendar]&lt;br /&gt;
* [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.&lt;br /&gt;
* [http://ifreebusy.com/ ifreebusy.com] will display freebusy information using hCalendar. See this [http://ifreebusy.com/neiljensen/freebusy/ example].&lt;br /&gt;
* [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.&lt;br /&gt;
* [http://www.asdvbonaparte.nl/ ASDV Bonaparte] is a Dutch debating society. Their events calendar has been marked up with the hCalendar conventions.&lt;br /&gt;
* [http://chocnvodka.blogware.com/blog Suw Charman] has marked up [http://suw.org.uk/archives/category/events/ her events] with hCalendar.&lt;br /&gt;
* [http://www.blogbusinesssummit.com/ Blog Business Summit] has published their [http://www.blogbusinesssummit.com/details.htm event details] marked up with hCalendar.&lt;br /&gt;
* [http://eventful.com Eventful.com] publishes all events with hCalendar and venues with [[hcard|hCard]].  Took them only 15 minutes to implement both! Their Atom feeds also contain hCalendar/hCard.&lt;br /&gt;
* [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.&lt;br /&gt;
* 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.&lt;br /&gt;
* [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.&lt;br /&gt;
* [http://www.complexspiral.com/ Complex Spiral Consulting], both in the &amp;quot;Events&amp;quot; box on left side, and the separate [http://www.complexspiral.com/events/ Events page]. &lt;br /&gt;
* [http://tantek.com/log Tantek's Thoughts], specifically the &amp;quot;Events&amp;quot; roll in the right-most column.&lt;br /&gt;
* [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.&lt;br /&gt;
* [http://norman.walsh.name/2005/itinerary/ Norm Walsh's travel schedule] use hCalendar as well as GRDDL.&lt;br /&gt;
* [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.&lt;br /&gt;
* 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.&lt;br /&gt;
* The [http://laughingsquid.com/laughing-squid-10th-anniversary-party/ Laughing Squid 10th Anniversary Party] has an hcalendar page.&lt;br /&gt;
* SPRACI has hcalendar versions of its nightlife/clubbing/gigs/festivals listings for many cities worldwide - eg: [http://www.spraci.com/listhcalendar.php?parea=sydney&amp;amp;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&lt;br /&gt;
* WWF-Australia events calendars: [http://wwf.org.au/act/events/ What's on], [http://wwf.org.au/act/volunteer/ Volunteer]&lt;br /&gt;
* [http://rubyholic.com rubyholic] uses hCalendar to publish calendars for ruby groups.&lt;br /&gt;
* [http://www.bath.ac.uk/whats-on/ University of Bath What's On] uses hCalendar on individual event pages&lt;br /&gt;
* The [http://www.kiez-ev.de/ Kiez] is a small cinema and has published its [http://www.kiez-ev.de/programm program] marked up with hCalendar&lt;br /&gt;
&lt;br /&gt;
===World Cup Kick-off===&lt;br /&gt;
* [http://www.worldcupkickoff.com/ World Cup KickOff] where you can download and keep all the fixtures you are interested in so you will never miss a single game of the 2006 football World Cup!&lt;br /&gt;
** This link was on the [http://www.lifehacker.com/software/sports/world-cup-start-times-for-ical-etc-175393.php Lifehackers site] and made its way to the yahoo news site:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&lt;br /&gt;
Mon May 22, 4:00 PM ET&lt;br /&gt;
The World Cup, one of the world's most watched sporting events, is almost upon us. If you've ever tried to follow your favorite team through the Cup you know that it can sometimes be difficult to know when they're on. World Cup Kickoff can help.&lt;br /&gt;
&lt;br /&gt;
World Cup KickOff is all you will ever need for knowing all the match details for the upcoming World Cup 2006. Whether you use your mobile phone, MS Outlook, Apple iCal or Mozilla Calendar, you can download and keep all the fixtures you are interested in so you will never miss a single game!&lt;br /&gt;
&lt;br /&gt;
Next tip? We'll show you how to get up at 2 AM to watch your matches. ;0) Thanks to Tom for the tip!&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Examples with some problems==&lt;br /&gt;
&lt;br /&gt;
Entries may be moved here if there's a problem with the way hCalendar is used on the page concerned. If the page is yours, and you want to improve it, see the [[hcalendar-faq|hCalendar FAQ]], or raise any queries on [[hcalendar-issues|hCalendar Issues]] or [[mailing-lists#microformats-discuss|the mailing list]], where people will be happy to help you. &lt;br /&gt;
&lt;br /&gt;
* [http://www.webfeet.org/events.html Webfeet events] includes hCalendar markup in its aggregated events lists.&lt;br /&gt;
** Possibly a case where &amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt; won't work for dtstart/dtend as there are many events listed under a single date. [[User:Webf|Webf]] 15:19, 15 Jan 2007 (PST)&lt;br /&gt;
* [http://www.theatrestudies.llc.ed.ac.uk/ Theatre Studies: European Theatre] at the University of Edinburgh uses hCalendar to markup news and events on the index page.&lt;br /&gt;
**Uses &amp;quot;display:none&amp;quot; on image. [[User:AndyMabbett|Andy Mabbett]] 15:32, 13 Nov 2006 (PST)&lt;br /&gt;
* [http://www.bokle.de/ s'Bokle] is a German music pub. Their events calendar has been marked up with hCalendar.&lt;br /&gt;
** improper use of rrule --[[User:RyanKing|RyanKing]] 16:04, 6 Jan 2006 (PST)&lt;br /&gt;
* [http://plan9.tryphon.org/nancy/list Plan9] - Uses hCalendar to mark up events !&lt;br /&gt;
** dtstart/dtend are implemented on span element [[User:TomArmitage|Tom Armitage]] June 23, 2006&lt;br /&gt;
* [http://www.socaltech.com socalTECH] is a news and information site. Their front page event listing is marked up with hCalendar.&lt;br /&gt;
** dtstart/dtend implemented on span element [[User:TomArmitage|Tom Armitage]] June 23, 2006&lt;br /&gt;
* [http://www.multipack.co.uk The Multipack] features a vevent for the next meeting information.&lt;br /&gt;
** dtstart/dtend are implemented on em element [[User:TomArmitage|Tom Armitage]] June 23, 2006&lt;br /&gt;
* [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]&lt;br /&gt;
** dtstart/dtend are implemented on td element [[User:TomArmitage|Tom Armitage]] June 23, 2006&lt;br /&gt;
&lt;br /&gt;
- whilst Tails parses dtstart/dtend on &amp;lt;em&amp;gt;any&amp;lt;/em&amp;gt; element, technically it really needs to be on abbr. Technorati Microformats Search only looks for the title element on &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; tags, for instance.&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
{{hcalendar-related-pages}}&lt;/div&gt;</summary>
		<author><name>Webf</name></author>
	</entry>
	<entry>
		<id>http://microformats.org/wiki/index.php?title=hcalendar-issues&amp;diff=12553</id>
		<title>hcalendar-issues</title>
		<link rel="alternate" type="text/html" href="http://microformats.org/wiki/index.php?title=hcalendar-issues&amp;diff=12553"/>
		<updated>2007-01-10T22:06:56Z</updated>

		<summary type="html">&lt;p&gt;Webf: /* Issues */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= hCalendar Issues =&lt;br /&gt;
&lt;br /&gt;
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]&lt;br /&gt;
&lt;br /&gt;
See related [[hcard-issues]].&lt;br /&gt;
&lt;br /&gt;
== Issues ==&lt;br /&gt;
&lt;br /&gt;
Please use this format:&lt;br /&gt;
* &amp;lt;nowiki&amp;gt;{{OpenIssue}}&amp;lt;/nowiki&amp;gt; YYYY-MM-DD raised by AUTHORNAME&lt;br /&gt;
*# ''Issue 1: Here is the first issue I have.''&lt;br /&gt;
*# ''Issue 2: Here is the second issue I have.''&lt;br /&gt;
&lt;br /&gt;
And add new issues to the top of the list:&lt;br /&gt;
&lt;br /&gt;
* {{OpenIssue}} 2007-01-07 raised by [[User:Webf|Webf]]&lt;br /&gt;
*# Looking for a mechanism for specifying a dtstart without using &amp;lt;nowiki&amp;gt;&amp;lt;abbr&amp;gt;&amp;lt;/nowiki&amp;gt;. Would be used where there are a number of events (as in the [http://www.webfeet.org/events.html Webfeet events lists]) where you do not want to have the visible date repeated&lt;br /&gt;
&lt;br /&gt;
* {{OpenIssue}} 2006-10-21 raised by [[User:AndyMabbett|AndyMabbett]]&lt;br /&gt;
*# there should be some way to say that the URL of an hCard or hCalendar event is the URL of the page itself, without having to include a redundant, and accessibility-damaging link to that page, on &lt;br /&gt;
the page itself.&lt;br /&gt;
&lt;br /&gt;
* {{OpenIssue}} 2006-09-22 raised by [[User:AndyMabbett|AndyMabbett]]&lt;br /&gt;
*# How are Julian dates to be displayed? So far as I am aware, ISO8601 has no facility for marking up Julian dates, so should the form &amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;[Gregorian date]&amp;quot;&amp;gt;[Julian date]&amp;lt;/abbr&amp;gt; &amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt; be used? If so, that should be indicated, via an example.&lt;br /&gt;
&lt;br /&gt;
* {{OpenIssue}} 2006-08-14 raised by [[User:Elias|Elias Sinderson]]&lt;br /&gt;
*# ''Issue 1: Although ISO 8601 allows both basic (sans delimiters) and extended formats, the extended format (where hyphens and colons are explicitly added) is broadly preferred for the web. While RFC 2445 specifies that the basic form be used in in iCalendar date / time fields, the W3C has published a technical [http://www.w3.org/TR/NOTE-datetime note] (submitted by Reuters), which recommends that the extended (delimited) format be used, and the [http://www.w3.org/TR/html401/types.html#h-6.11 HTML 4.0 spec] uses the extended format. Further, RFC 3339 defines a ISO 8601 profile for dates and time representations on the internet that future specs SHOULD use; recommending a fully delimited representation (see sec. 5.6). Lastly, it should be noted that the [http://www.w3.org/TR/xmlschema-2/#date xsd:date] and [http://www.w3.org/TR/xmlschema-2/#dateTime xsd:dateTime] types are specified as being the ISO 8601 extended format. So, given that hCalendar is based on iCalendar, it is understandable that it allows both formats, however this is clearly a case in which it would be very reasonable to require users to upconvert the format into the least ambiguous and most easily parsed / validated representation. Think of the children.&lt;br /&gt;
&lt;br /&gt;
* {{OpenIssue}} 2006-03-07 raised by [[User:Ragdoll|Justin McDowell]]&lt;br /&gt;
*# ''Issue 1: I'd love to see a Property List, similar to what is seen in the hCard spec, that lists all the available properties and sub-properties in a nice, compact list. This saves a lot of time and is really useful for quickly and easily getting aquainted with the possibilities of vCalendar.''&lt;br /&gt;
&lt;br /&gt;
* 2006-02-17 raised by [[User:Mark Mansour|Mark Mansour]] - notes are summarized [[hcalendar-irc-meetup-20060225|here]]&lt;br /&gt;
*# Should vcalendar be a class?  Section 4.4 of RFC2445 says: &amp;quot;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.&amp;quot;  Also the vcalendar class would allow properties on the calendar itself such as METHOD and CALSCALE (I don't think VERSION and PRODID are particularly relevant).&lt;br /&gt;
*#* ACCEPTED SPECUPDATE/FAQ.  Is this a case of fixing something that isn't broken?  Note that &amp;quot;iCalendar object&amp;quot; != &amp;quot;vcalendar&amp;quot;.  This is a bit confusing so read RFC 2445 carefully in that regard.  In addition, the [[hcalendar|hCalendar]] spec should say *precisely* how to generate VCALENDAR properties in their absence.&lt;br /&gt;
*# How are axis and headers going to be handled?&lt;br /&gt;
*#* ACCEPTED.  This is documented in [[hcalendar-brainstorming]] but MUST be moved to [[hcalendar|hCalendar]] proper as the editors and implementers have all agreed on it (months ago). Add this as a [[to-do]] for Tantek.&lt;br /&gt;
*# 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?&lt;br /&gt;
*#* REJECTED. Please RTFM.  Searching the [[hcalendar|hCalendar]] spec for *either* &amp;quot;axis&amp;quot; or &amp;quot;headers&amp;quot; would have found the following example in the wild:  [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.&lt;br /&gt;
*# 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).&lt;br /&gt;
*#* ACCEPTED SPECUPDATE/FAQ. Another [[to-do]] for Tantek.  Explicitly specify which additional iCalendar objects (in addition to VEVENT) are permitted in hCalendar.  Current additional candidates: VTODO (many examples of this info on the web), VFREEBUSY (already at least one site publishing this info), VALARM (maybe, seems harmless enough, but without a compelling real world use case we should probably omit it).  Currently dropping: VTIMEZONE (terrible construct), VJOURNAL (obsoleted by [[hatom|hAtom]]).&lt;br /&gt;
*# 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?&lt;br /&gt;
*#* ACCEPT PARTIAL.  We probably need an hCalendar ''validator'' before we can declare any set of tests to be official.&lt;br /&gt;
*# 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. &lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;a name=&amp;quot;myfrag&amp;quot;&amp;gt;heading&amp;lt;/a&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;div class=&amp;quot;description&amp;quot;&amp;gt;A nice event&amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;2005-10-05&amp;quot;&amp;gt;October 5&amp;lt;/abbr&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
*#* ACCEPTED. We should clarify to converters how to interpret a fragement id.  The interpretations are all consistent.  It points to the element that is to be converted.  If that element is empty then so is the conversion.  There is no issue here other than a need for more documentation.&lt;br /&gt;
* 2006-02-01 raised by [[RyanKing]]&lt;br /&gt;
*# ''Issue 1: Given that now, or soon will have hAtom, should we disallow vJournal, so that we don't have 2 blog-post formats?''&lt;br /&gt;
*#* ACCEPTED.  Yes, we should expliclty DROP &amp;quot;vjournal&amp;quot; from [[hcalendar|hCalendar]].&lt;br /&gt;
* 2006-01-04 raised by [[User:CGranade|CGranade]]&lt;br /&gt;
*# ''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 &amp;lt;code&amp;gt;class&amp;lt;/code&amp;gt; attribute is ''not'' portable across schemas.''&lt;br /&gt;
*#* 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.&lt;br /&gt;
*# ''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.''&lt;br /&gt;
*#* ACCEPTED.  This is definitely something to be added to *-examples pages for each microformat.&lt;br /&gt;
* 2005-10-14 raised by [[User:MarkoMrdjenovic|MarkoMrdjenovic]]&lt;br /&gt;
*# ''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''.&lt;br /&gt;
*#* 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 &amp;quot;@&amp;quot; signs since the issue points out that such UIDs crash some calendaring software.&lt;br /&gt;
*# ''DTSTAMP also has to be present in iCal event for Microsoft Outlook. I think DTSTAMP should be user visible information so implementation with class=&amp;quot;dtstamp&amp;quot; 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.'' [Suggestion:] why not set DTSTAMP to DTSTART if not explicitly defined? -- [[DimitriGlazkov]]&lt;br /&gt;
*#* ACCEPTED.  We should come up with a way to encourage/synthesize/imply DTSTAMP property values.&lt;br /&gt;
*# ''Here is an example from Midgard CMS (which will be easy to change according to bergie on irc):''&lt;br /&gt;
*#* For more discussion of this, please see [http://microformats.org/wiki/hcalendar-brainstorming#UID_handling hCalendar brainstorming: UID handling]&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;&lt;br /&gt;
  &amp;lt;li class=&amp;quot;vevent&amp;quot; id=&amp;quot;2678c3f94af4a49f9ccbb69b92a82aba-midgardGuid&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;abbr class=&amp;quot;dtstart&amp;quot; title=&amp;quot;2005-10-20T14:34:45Z&amp;quot;&amp;gt;Torstai 20. Lokakuu 17:34&amp;lt;/abbr&amp;gt; -&lt;br /&gt;
    &amp;lt;abbr class=&amp;quot;dtend&amp;quot; title=&amp;quot;2005-10-20T15:33:56Z&amp;quot;&amp;gt;18:33&amp;lt;/abbr&amp;gt;&lt;br /&gt;
    &amp;lt;a class=&amp;quot;url&amp;quot; href=&amp;quot;/bergie/another-calendar/82457028ba83407451edd8aaeaa40622.html&amp;quot;&amp;gt;&lt;br /&gt;
        &amp;lt;span class=&amp;quot;summary&amp;quot;&amp;gt;From the other cal&amp;lt;/span&amp;gt;&lt;br /&gt;
    &amp;lt;/a&amp;gt;&lt;br /&gt;
    &amp;lt;abbr class=&amp;quot;dtstamp&amp;quot; title=&amp;quot;2005-10-14T12:16:45Z&amp;quot;&amp;gt;Torstai 14. Lokakuu 12:16&amp;lt;/abbr&amp;gt;&lt;br /&gt;
  &amp;lt;/li&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
* 2005-09-29 raised by RyanKing&lt;br /&gt;
*# ''How does one use ATTENDEE?''&lt;br /&gt;
*#* ACCEPTED.  Another [[to-do]] for Tantek - document how to use ATTENDEE with [[hcard|hCard]].&lt;br /&gt;
* 2005-07-27 raised by Paolo Massa&lt;br /&gt;
*# ''I tried to add a hcalendar event in my blog but it rendered orribly. The problem was I already have a 'class=&amp;quot;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=&amp;quot;summary&amp;quot; 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 &amp;quot;shield&amp;quot; attribute &amp;quot;inside&amp;quot; microformats from being interpreted as &amp;quot;normal&amp;quot; attributes. For example for the hCalendar microformats the relative CSS could be something like:&lt;br /&gt;
&lt;br /&gt;
.vevent .summary {&lt;br /&gt;
&lt;br /&gt;
//remove all the previously set properties, for example:&lt;br /&gt;
&lt;br /&gt;
text-decoration: none;&lt;br /&gt;
&lt;br /&gt;
font-size: 100%;&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
Since the hCalendar microformat is the following,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;vevent&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;a class=&amp;quot;url&amp;quot; href=&amp;quot;http://www.web2con.com/&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;summary&amp;quot;&amp;gt;Web 2.0 Conference&amp;lt;/span&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
I hope to have been clear but I'm not so sure ;-)''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* 2005-07-21 raised by Neil Jensen &lt;br /&gt;
*# ''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].''&lt;br /&gt;
&lt;br /&gt;
* 2005-07-11 raised by Kragen&lt;br /&gt;
*# ''The specification of class=&amp;quot;url&amp;quot; as &amp;amp;lt;a href=&amp;quot;...&amp;quot;&amp;gt; should be a &amp;quot;should&amp;quot;, not a &amp;quot;must&amp;quot;.  Other ways of referencing the event URL, such as &amp;amp;lt;iframe src=&amp;quot;...&amp;quot;&amp;gt; and &amp;amp;lt;embed src=&amp;quot;...&amp;quot;&amp;gt;, shoul be mentioned.  At present X2V doesn't appear to handle them.  This came up in a discussion about [[xfolk|xFolk]].''&lt;br /&gt;
*#* REJECTED. Lack of use case.  We should not add additional &amp;quot;ways of referencing the event URL&amp;quot; unless you can show a concrete real world example on the Web which requires it.&lt;br /&gt;
&lt;br /&gt;
* 2005-06-21 raised by Hixie&lt;br /&gt;
*# ''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?&lt;br /&gt;
*#* ACCEPTED. Another [[to-do]] for Tantek, write-up [[hcalendar-parsing]] that documents precisely how user agents are to parse [[hcalendar|hCalendar]] markup.&lt;br /&gt;
* 2005-02-22 raised by Matt Raymond [http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2005-February/003124.html on the whatwg list]:&lt;br /&gt;
*# ''There is no copyright statement and no patent statement.''&lt;br /&gt;
*#* ACCEPTED. I have updated [[hcalendar]] (and [[hcard]], and all other MicroFormats) with a standard copyright statement and patent statement.&lt;br /&gt;
&lt;br /&gt;
* 2005-02-18 raised by Matt Raymond [http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2005-February/003116.html on the whatwg list]:&lt;br /&gt;
*# ''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.''&lt;br /&gt;
*#* 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.&lt;br /&gt;
*# ''As a result of the above, user agents would not be able to reliably allow users to access extension properties such as &amp;quot;x-mozilla-alarm-default-length&amp;quot; (which is an actual extension used in Sunbird).''&lt;br /&gt;
*#* REJECTED (out of scope).  Extension properties are outside the current scope of hCalendar.&lt;br /&gt;
*# ''The use of &amp;lt;abbr&amp;gt; for dates is incorrect. &amp;quot;August 5th, 2004&amp;quot; is not the abbreviation of 2004-09-05. In fact, the opposite is closer to the truth.''&lt;br /&gt;
*#* REJECTED (false statement).  This is simply a false statement.  See this article for an explanation of this use of &amp;lt;abbr&amp;gt;: [http://tantek.com/log/2005/01.html#d26t0100 Human vs. ISO8601 dates problem solved]&lt;br /&gt;
*# ''You have to create a complex set of rules for all possible uses of legacy markup within &amp;lt;span class=&amp;quot;vcalendar&amp;quot;&amp;gt; which can easily be implemented incorrectly.''&lt;br /&gt;
*#* 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.&lt;br /&gt;
*# ''There are styling and tooltip issues that are unresolved.''&lt;br /&gt;
*#* 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.&lt;br /&gt;
*# ''hCalendar/hCard is more complicated for webmasters to read and understand and more complicated for developers to implement.''&lt;br /&gt;
*#* REJECTED (empty statements, invalid comparator).  Please state specific examples which show the perceived complexity.  The comparison &amp;quot;more complicated&amp;quot; requires two items, no second item was provided.&lt;br /&gt;
*#  ''I dislike the entire system of using class names as markup.  Class names should be reserved for user-defined semantics.''&lt;br /&gt;
*#* ACCEPT-PARTIAL.  When specific elements are available, they should be used instead of class names, but even then class names work well to &amp;quot;subclass&amp;quot; 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.&lt;br /&gt;
*#* ''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 &amp;quot;User agents may... perform some activity based on known conventions for that profile&amp;quot;?  Should this be a part of [[microformats]] specifications in general?  (If not, why not?)''&lt;br /&gt;
*#** 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.&lt;br /&gt;
*#*** ''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] &amp;quot;This is precisely the reason that GMPG was founded and created, to provide permanent URLs/homes for microformat profiles.&amp;quot; How does one cause GMPG to issue a profile URL?''&lt;br /&gt;
*#**** ACCEPTED. See [[profile-uris]]; this is moving from Tantek's [[to-do]] list, to both provide profiles and URLs (probably at gmpg.org) for those profiles for hCalendar etc.&lt;br /&gt;
* {{OpenIssue}} 2006-04-10 raised by [[User:ScottReynen|Scott Reynen]].&lt;br /&gt;
*# ''When someone looks at the [[hcalendar]] pages, one sees no collection of real-world publishing of event data nor discussion of the properties implied by such examples, I think it's far too easy to infer that microformats come from other formats more than actual behavior.  There's nothing on the [[process]] nor the hcalendar pages explaining this discrepancy.  I would argue that there should be an explanation, probably in both places.''&lt;br /&gt;
* {{OpenIssue}} 2006-04-13 raised by Tantek&lt;br /&gt;
*# ''Need to add a section on &amp;quot;Property Exceptions&amp;quot; like that in [[hcard|hCard]] to document how to publish / handle the '''METHOD''' property and potentially others.  I.e. typically publishers may omit the METHOD property, however, converters whose function is to convert [[hcalendar|hCalendar]] to iCalendar for consumption/subscription by a calendar aggregator, should probably insert a default '''METHOD:PUBLISH''' on the '''VCALENDAR''' object in the resultant .ics stream.''&lt;br /&gt;
&lt;br /&gt;
== Related Pages ==&lt;br /&gt;
{{hcalendar-related-pages}}&lt;/div&gt;</summary>
		<author><name>Webf</name></author>
	</entry>
</feed>