| Thanks, that does help. RFC 2445 refers to those date times at "floating", which I always preferred, since "local" is overloaded and makes it difficult to talk about: http://www.ietf.org/rfc/rfc2445.txt "floating" is a weird term, and I hate making words up, but at least it doesn't get confused in conversation with a time-zone-decorated timestamp that just happens to be in the user's local timezone. But as long as it's possible to do what we need, which is sounds like it is, then that's what matters. Thanks for the writeup. EDIT: Regarding "Birthdays, Holidays and relative points in time", MonthDay is not sufficient to describe all of the types of "floating" times, the canonical example given in RFC 2445 is of a user who wishes to appear unavailable at lunch every day, regardless of what time zone they are in. That's a more granular resolution than a day, but it's the same concept: an arbitrary precision, time-zone-less date that has no equivalent UTC start time until it is "observed". |