Re: Questions regarding recurrence rules

Reinhold Kainhofer <[email protected]> Fri, 3 Jun 2005 00:41:52 +0200
Newsgroups gmane.ietf.calendar
Organization Vienna University of Technology
Message-ID <[email protected]>
--nextPart4225827.ZUWxiI19yr
Content-Type: text/plain;
  charset="iso-8859-6"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Am Donnerstag, 2. Juni 2005 21:15 schrieb Doug Royer:
> This is more documentation supporting my assertion that recurrence
> rules are not as portable as many claim.
>
> I would suggest using RDATE's and no RRULE or EXRULE. They are
> easy to unwind, only after clearly defined and consistently used.

Using only RDATE means loosing data (namely the actual intent) and the=20
possibility to edit the data later on.=20
If you have a course with the following data (from a student's perspecitive=
):
Mar 2, 7, 9, 14, ...
Can you be sure that it is really meant as a course that happens every mond=
ay=20
and wednesday? No, you'll have to look at your calendar for every date. If=
=20
you see that the recurrence is every monday and friday, you don't need to=20
look at your calendar, but sooner or later you'll remember.

Also, in KOrganizer we also use iCalendar to store the whole calendar on di=
sk,=20
and there we absolutely need a way to store the way in which a date is=20
recurring. Simply discarding all RRULES and using RDATES instead might be a=
=20
solution for sending invitations, but it's not a solution for storing on=20
disk, and also not for exchanging events between two calendaring applicatio=
ns=20
(i.e. import/export of events).=20

Cheers,
Reinhold

=2D-=20
=2D-----------------------------------------------------------------
Reinhold Kainhofer, Vienna, Austria
email: [email protected], http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at
 * K Desktop Environment, http://www.kde.org/, KOrganizer / KPilot maintain=
er

--nextPart4225827.ZUWxiI19yr
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBCn4s+TqjEwhXvPN0RAqVXAJ4qbCgEKLTKhICUqnCDBs5BSbBM0QCgjz1x
b7HuEW2P/N14XvrLCsGdkuU=
=OMxE
-----END PGP SIGNATURE-----

--nextPart4225827.ZUWxiI19yr--