[uf-discuss] all day events
Ryan King
ryan at technorati.com
Mon Feb 13 23:14:20 PST 2006
On Feb 8, 2006, at 5:02 PM, Mark Mansour wrote:
>> 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.
You're right there is a date type, but we ignore it for good reason.
Sorry that I took me awhile to respond, but I couldn't remember at
first the exact reason for the way we do it.
Anyway, the reason we confound the DATE and DATETIME types is that
they are treated essentially the same by calendaring applications.
For example, I just created an event in Apple's iCal.app for 2/6-2/9
(last week), then exported it:
> BEGIN:VCALENDAR
> VERSION:2.0
> X-WR-CALNAME:blah
> PRODID:-//Apple Computer\, Inc//iCal 2.0//EN
> X-WR-RELCALID:4BA2A3D9-23D1-495E-BFA2-AA439939BF0C
> X-WR-TIMEZONE:America/Los_Angeles
> CALSCALE:GREGORIAN
> METHOD:PUBLISH
> BEGIN:VEVENT
> DTSTART;VALUE=DATE:20060206
> DTEND;VALUE=DATE:20060209
> SUMMARY:blah
> UID:26F9A96A-5D25-455A-8240-12EED1ADF63C
> SEQUENCE:4
> DTSTAMP:20060214T070829Z
> END:VEVENT
> END:VCALENDAR
Notice that, though I created the event as ending on 2006-02-08, it
put 2006-02-09, making 2006-02-09 == 2006-02-09T00:00.
-ryan
--
Ryan King
ryan at technorati.com
More information about the microformats-discuss
mailing list