Hi Ryan, > > There are two recommendations > > - the wording on how timezones are handled needs to be changed; and > > - the way datetimes are handled could be changed, but unfortunately it > > would affect hCard. > > I presume this sums up your issue:
yes it does. > > So back to Christmas. According to hCalendar, the correct way to > > represent Christmas in iCal is 20061225T000000 instead of 20061225, > > but we've now transformed a date into a 'floating' (timezoneless) > > datetime. Is it the end of the world - no, not at all, but it just > > seems a little clunky. Do I want the spec changed? I can live with > > it the way it is, but I think it is more cleanly represented as a > > date. > > Which is really a moot point, because there is no 'date' type in > iCalendar, only datetime, so, in effect, 20061225 = 20061225T000000, > they're both datetimes. That is not my interpretation of rfc2445. Section 4.3 defines the value data types, of which there is a date (4.3.4) and datetime (4.3.5) datatype. My issues is that we are converting between data types and changing the information in a subtle manner. Mark _______________________________________________ microformats-discuss mailing list [email protected] http://microformats.org/mailman/listinfo/microformats-discuss
