[Ietf-calsify] dtstart in tz or utc time and dtend in floating time

Reinhold Kainhofer reinhold at kainhofer.com
Thu Mar 29 13:42:14 PST 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Donnerstag, 29. März 2007 schrieb Petr Tomasek:
> > Shouldn't we go one step further and say that if the DTSTART value type
> > is FORM #1: DATE WITH LOCAL TIME (See
> > http://tools.ietf.org/wg/calsify/draft-ietf-calsify-rfc2445bis/draft-ietf
> >-calsify-rfc2445bis-06.html#VALUE.DATE-TIME), DTEND should also be of the
> > same form.
>
> But You would have no way to express events like:
> "event X starts on friday xy at 18:00 and ends on sunday xy".
>
> If You force both DTSTART and DTEND to be the same type, then
> this event would be transformed into:
> "event X starts on friday xy at 18:00 and ends on sunday xy 24:00",
> which is not the same!

Frank Dawson, one of the authors of rfc 2445, says in the following mail that 
it was the intention of rfc 2445 that DTSTART, DTEND, UNTIL, etc. have the 
same value type. It was just not stated clear enough (yeah, that's a 
euphemism for "not at all") in the original RFC:

http://www.imc.org/ietf-calendar/archive1/msg03648.html

See also the summary of the whole discussion on
http://tipi.sourceforge.net/doc/recur/apa.html

Cheers,
Reinhold



- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: reinhold at kainhofer.com, http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
 * K Desktop Environment, http://www.kde.org, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGDDK4TqjEwhXvPN0RAjhPAKCkdCt53lYsK5XNAg6aeyO9jt4RAACfZY/E
wxDHhSQwsTPP3RZOpzBQLDs=
=IKwK
-----END PGP SIGNATURE-----


More information about the Ietf-calsify mailing list