hcalendar-issues-resolved

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

resolved issues

hCalendar issues that are resolved but may have outstanding to-do items.

As issues are resolved, they will be moved from the Issues list to this section.

As actions are taken according to the resolutions noted in the issues, they are moved to hcalendar-issues-closed.

resolved 2005

• 2005-02-18 raised by Matt Raymond on the whatwg list:
  1. ...
  2. ...
  3. ...
  4. ...
  5. ...
  6. ...
  7. I dislike the entire system of using class names as markup. Class names should be reserved for user-defined semantics.
     • ACCEPT-PARTIAL FAQ. When specific elements are available, they should be used instead of class names, but even then class names work well to "subclass" specific elements. This is thoroughly discussed in the essay A Touch of Class. And yes, class names can and should be used for user-defined semantics. hCalendar is one such user, and it is reasonable for users to use each others class names.
     • Would it be more in the spirit of HTML to define these classes in a metadata profile, so that "User agents may... perform some activity based on known conventions for that profile"? Should this be a part of microformats specifications in general? (If not, why not?)
       • ACCEPTED. Yes, all microformats that introduce new classnames SHOULD include an XMDP profile (which itself is a microformat for defining HTML metadata profiles) that defines those classnames.
         • Ok, but in order to refer to a profile, it needs a URI. Tantek writes in a message of Jul 21 "This is precisely the reason that GMPG was founded and created, to provide permanent URLs/homes for microformat profiles." How does one cause GMPG to issue a profile URL?
           • 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.
           • UPDATE: hCalendar profile: http://microformats.org/profile/hcalendar. to-do - add this to hcalendar-faq.

• 2005-06-21 raised by Hixie
  1. 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?
     • ACCEPTED. Another to-do for Tantek, write-up hcalendar-parsing that documents precisely how user agents are to parse hCalendar markup.

• 2005-07-11 raised by Kragen
  1. The specification of class="url" as <a href="..."> should be a "should", not a "must". Other ways of referencing the event URL, such as <iframe src="..."> and <embed src="...">, should be mentioned. At present X2V doesn't appear to handle them. This came up in a discussion about xFolk.
     • REJECTED feature request. Lack of use case. We should not add new "ways of referencing the event URL" unless there are concrete real world example on the Web which requires it.
     • ACCEPTED clarification. The processing model for "url" properties (e.g. hcard-parsing, hcalendar-parsing) should state what to do with all valid HTML4 elements that reference external URLs (like <iframe>), and all such valid HTML5 elements (like <embed> - Tantek 08:16, 26 August 2009 (UTC)

• 2005-07-27 raised by Paolo Massa
  1. I tried to add a hcalendar event in my blog but it rendered horribly. The problem was I already have a 'class="summary' in my normal HTML (it is the title of the posts) and my CSS displays it bigger and bold. In this way the summary of the event was as big as the titles of the posts, destroying readability. The problem is Overloading of class attributes, it might be the case that a blogger already use, for example, class="summary" for different purposes. What can be a solution? Providing in every microformat wiki page a CSS file that users can download and insert in their blog as additional CSS. This CSS file will "shield" attribute "inside" microformats from being interpreted as "normal" attributes. For example for the hCalendar microformats the relative CSS could be something like:

     .vevent .summary { text-decoration: none; font-size: 100%; }
     

     Since the hCalendar microformat is the following,

     <span class="vevent"><a class="url" href="http://www.web2con.com/"><span class="summary">Web 2.0 Conference</span></a></span>
     

     ... I hope to have been clear but I'm not so sure ;-)
     • ACCEPTED FAQ. to-do expand the current FAQ class interactions entry with contextual selector examples.

• 2005-09-29 raised by RyanKing
  1. How does one use ATTENDEE?
     • ACCEPTED. Another to-do for Tantek - document how to use ATTENDEE with hCard.
     • UPDATE: This has now been documented in hCalendar brainstorming: hCard attendees. The remaining to-do is to incorporate the SHOULD use hCard attendees suggestion into the hCalendar 1.0.1 specification.

• 2005-10-14 raised by MarkoMrdjenovic
  1. 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. RFC recommends use of addr format for uids which is problematic in html id (does not validate). 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.
     • ACCEPTED-PARTIAL. Yes, it appears RFC2445 requires UID. However, typical mentions of events by web authors do not provide anything equivalent to a UID, nor should we require authors to do so. Thus we must come up with an algorithm for implied UID, similar to some of the other properties. We REJECT the use of the html 'id' attributre as a substitute for UID as they are of different scopes and thus such a translation will likely be problematic. As part of this algorithm, we MUST disallow "@" signs since the issue points out that such UIDs crash some calendaring software.
     • UPDATE: Which version(s) of Microsoft Outlook have this problem? Please document in icalendar-implementations.
  2. DTSTAMP also has to be present in iCal event for Microsoft Outlook. I think DTSTAMP should be user visible information so implementation with class="dtstamp" is fine. x2v already supports it so it should just be added to the standard and examples. The converters might also think of a way to force (create) dtstamp if it's not present. *#* [Suggestion:] why not set DTSTAMP to DTSTART if not explicitly defined? -- DimitriGlazkov
     • ACCEPTED. We should come up with a way to encourage/synthesize/imply DTSTAMP property values.
  3. Here is an example from Midgard CMS (which will be easy to change according to bergie on irc):

  <li class="vevent" id="2678c3f94af4a49f9ccbb69b92a82aba-midgardGuid">
    <abbr class="dtstart" title="2005-10-20T14:34:45Z">Torstai 20. Lokakuu 17:34</abbr> -
    <abbr class="dtend" title="2005-10-20T15:33:56Z">18:33</abbr>
    <a class="url" href="/bergie/another-calendar/82457028ba83407451edd8aaeaa40622.html">
        <span class="summary">From the other cal</span>
    </a>
    <abbr class="dtstamp" title="2005-10-14T12:16:45Z">Torstai 14. Lokakuu 12:16</abbr>
  </li>

• 1. • For more discussion of this, please see hCalendar brainstorming: UID handling

resolved 2006

• 2006-02-17 raised by Mark Mansour - notes are summarized here
  1. Should vcalendar be a class? Section 4.4 of RFC2445 says: "The Calendaring and Scheduling Core Object is a collection of calendaring and scheduling information. Typically, this information will consist of a single iCalendar object. However, multiple iCalendar objects can be sequentially grouped together." Also the vcalendar class would allow properties on the calendar itself such as METHOD and CALSCALE (I don't think VERSION and PRODID are particularly relevant).
     • ACCEPTED SPECUPDATE/FAQ. Is this a case of fixing something that isn't broken? Note that "iCalendar object" != "vcalendar". This is a bit confusing so read RFC 2445 carefully in that regard. In addition, the hCalendar spec should say *precisely* how to generate VCALENDAR properties in their absence.
  2. How are axis and headers going to be handled?
     • ACCEPTED. This is documented in hcalendar-brainstorming but MUST be moved to hCalendar proper as the editors and implementers have all agreed on it (months ago). Add this as a to-do for Tantek.
  3. 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?
     • ACCEPTED FAQ. Searching the hCalendar spec for *either* "axis" or "headers" would have found the following example in the wild: Web Essentials 05 (original page http://we05.com/ is offline) has marked up their program schedule table with hCalendar (original page http://we05.com/program.cfm is offline), using the 'axis' and 'headers' attributes. This should be written up in the hcalendar-faq.
  4. 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).
     • 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).
  5. 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?
     • ACCEPT PARTIAL. We probably need an hCalendar validator before we can declare any set of tests to be official.
  6. 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.

<a name="myfrag">heading</a>
<div class="vevent">
  <div class="description">A nice event</div>
  <abbr class="dtstart" title="2005-10-05">October 5</abbr>
</div>

• 1. • 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.
• 2006-02-01 raised by RyanKing
  1. Issue 1: Given that now, or soon will have hAtom, should we disallow vJournal, so that we don't have 2 blog-post formats?
     • ACCEPTED. Yes, we should expliclty DROP "vjournal" from hCalendar.
• 2006-01-04 raised by CGranade
  1. ...
  2. 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.
     • ACCEPTED. This is definitely something to be added to *-examples pages for each microformat.

resolved 2007

• ...

see also

• hcalendar-issues
• hcalendar-issues-closed