[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Recurring Anniversary Instances?
Doug shot back:
>> Is DTSTART;VALUE=DATE:19990730 equivalent to
>> DTSTART;VALUE=DATE-TIME:19990730T000000Z?
>
>No, not at all!
>
>> Is DTEND;VALUE=DATE:19990730 equivalent to
>> DTEND;VALUE=DATE-TIME:19990730T235959Z (or should that be
> DTEND;VALUE=DATE-TIME:19990801T000000Z since its "non-inclusive")?
>
>No, not at all!
So, tell me then what is the effective 'starting time' (or 'ending time') of each of the following:
1: DTSTART;VALUE=DATE:19990730
2: DTSTART;VALUE=DATE-TIME:19990730T000000
3: DTEND;VALUE=DATE:19990730
4: DTEND;VALUE=DATE-TIME:19990730T235959
(2 are freebies I know but included for refrence.). When I used the term equivalent I mean they refer to the same point in time; not that they are necessarily interchagable (ie: mixing a VALUE=DATE w/a VALUE=DATE-TIME, etc). Until now I thought we had agreement on this but perhaps not.
What about input from the other RFC and draft editors (Steve S., Steve M., Derik S, Lisa, Tony, etc)??
>If I PUBLISH a VEVENT for New Years Day, it's Jan 1 in the CUA's time zone.
>Its not 00:00:00Z, or 00:00:00 US/Pacific or 00:00:00 in any other time zone.
Actually using 00:00:00 (floating WRT the CU/CUAs TZ) is what it is. When its 19990102T000001 in New York City, its only 19990101T230001 in the Central Time Zone (Chicago??, Kansas City?) and hence its still "New years day" there for another 59+ minutes.
Bruce
===========================================================================
Bruce Kahn INet: Bruce_Kahn@iris.com
Iris Associates Phone: 978.392.5335
Westford, MA, USA 01886 FAX: and nothing but the FAX...
Standard disclaimers apply, even where prohibited by law...