From Microformats Wiki
hcalendar-issues /
Revision as of 06:23, 1 September 2009 by Martin de la Iglesia (talk | contribs) (→‎Issues: new issue)
Jump to navigation Jump to search

<entry-title>hCalendar issues</entry-title>

These are externally raised issues about 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.

IMPORTANT: Please read the hCalendar FAQ and the hCalendar resolved issues before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.

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. — Tantek

For matters relating to the iCalendar specification itself, see icalendar-errata and icalendar-suggestions.

See related hCard issues.

closed issues

See: hCalendar closed issues.

resolved issues

Issues that are resolved but may have outstanding To Do items. See: hCalendar resolved issues.


Please add new issues to the bottom of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

issues 2007

  • open issue! Update: see dtend-issue for current summary and options on this issue 2007-01-20 raised by Andy Mabbett
    1. Where DTEND is a date, and not a date-time, it is required to be the day after the end of the event, thus: <abbr class="dtend" title="2007-04-30">29 April 2007</abbr>. However, "29 April 2007" 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 abbr element.
      • The ISO date 2007-04-30 is directly equivalent to 2007-04-30 00:00:00, which is why it's used as the end time of an event occuring on 2007-04-29. In this fuller context then you can view it as an abbreviation of 'the end of 29 April 2007'. Authors uncomfortable with this could use <abbr class="dtend" title="2007-04-29 23:59:59">29 April 2007</abbr>, or be more specific with their times. - Ciaran McNulty 09:21, 12 May 2007 [GMT]
        • The ISO standard has 2007-04-29 24:00:00 expressly to mark the end of the day 2007-04-29 rather than the start of the day 2007-04-30. This seems far preferable to 23:59:59. Matthew 15:22, 17 Jul 2007 (PDT)
      • This certainly risks confusion. The abbr title includes different information than the content; different when read by a 'normal' user who does not know about the exclusive-end-date.
        • The trouble is going to be with dates (rather than date-times). User expectation is different if you are talking about "3 o'clock", which really is a point-in-time, and "29th April", something lasting 24 hours. No problem saying an end time is 'exclusive', but an end-date can be either and is typically inclusive.
        • Using a more precise dtend is just a workround, you might not really want to say to the second when an event ends (as in 2007-04-29 23:59:59). You might easily want to say it runs from the Wednesday to Friday without committing to precise times - or that the event is sometime on that Friday but you don't know when.
      • Possible options could be:
        • Include a note in the standard that contradictory markup such as <abbr class="dtend" title="2007-04-30">29 April 2007</abbr> is bad practice and should be avoided
        • Make a break with the ical usage that end dates are exclusive.
        • Make the meaning clear:
          <abbr class="dtend" title="value=date:value=inclusive:2007-04-29">29 April 2007</abbr>
          <abbr class="dtend" title="value=exclusive:2007-04-30">29 April 2007</abbr>
          or maybe
          <abbr class="dtend;value=date:value=inclusive" title="2007-04-29">29 April 2007</abbr> Webf2 00:25, 13 May 2007 (PDT)
      • ACCEPTED BRAINSTORM SPECUPDATE. In practice (e.g. http://barcamp.org ) it appears all too often (thus easy) to make the mistake of assuming a dtend value is inclusive, and thus the last day of many events is truncated by a day. I am proposing a solution on hCalendar Brainstorming in an attempt to help this move forward. In short, introduce the syntactic sugar "dtlast", which treats date values as *inclusive* for the last day of an event. Semantically "dtlast" is merely an override for any "dtend" property setting on that hCalendar event, with the aforementioned slight difference in handling. More details on hCalendar brainstorming: dtlast. Tantek 07:48, 1 Sep 2008 (PDT)
      • REOPENING based on new data. It seems the number of instances that dtend is being used to indicate an inclusive end date has only increased in the past year, and by knowledgable authors as well. Adding a new property just for inclusive end dates may very well only confuse the matter. We need to seriously consider changing "dtend" to *be* inclusive for "date" values only, keeping its current functionality for datetime values (suggested by Webf2 above). This is probably worthy of documenting on its own page, something like dtend-issue. - Tantek 05:40, 26 August 2009 (UTC)

Issues 2009

open issue! 2009-09-01 raised by Martin de la Iglesia

  • DURATION format. Is there a specification of the format used for durations? In example 4 (http://microformats.org/wiki/hcalendar-examples), the duration value is "PT1H". I guess "1H" is one hour, but what does "PT" mean? And this example doesn't work anyway; neither Google calendar nor Yahoo! calendar recognize this duration.


Consider using this format (copy and paste this to the end of the list to add your issues; replace ~~~ with an external link if preferred) to report issues or feedback, so that issues can show up in hAtom subscriptions of this issues page. If open issues lack this markup, please add it.

Please post one issue per entry, to make them easier to manage. Avoid combining multiple issues into single reports, as this can confuse or muddle feedback, and puts a burden of separating the discrete issues onto someone else who 1. may not have the time, and 2. may not understand the issue in the same way as the original reporter.

<div class="hentry">
<span class="entry-summary author vcard">
 <span class="published">2011-MM-DD</span> 
 raised by <span class="fn">~~~</span>
<div class="entry-content discussion issues">
* <strong class="entry-title">«Short title of issue»</strong>. «Description of Issue»
** Follow-up comment #1
** Follow-up comment #2

Related Pages

This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.