From kde-pim  Tue May 31 00:50:47 2005
From: Reinhold Kainhofer <reinhold () kainhofer ! com>
Date: Tue, 31 May 2005 00:50:47 +0000
To: kde-pim
Subject: [Kde-pim] Re: Toltec connector and exceptions to recurring events
Message-Id: <200505310250.48992.reinhold () kainhofer ! com>
X-MARC-Message: https://marc.info/?l=kde-pim&m=111750066506691
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============1043163623=="

--===============1043163623==
Content-Type: multipart/signed;
  boundary="nextPart2120301.GEOz2ypOgq";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart2120301.GEOz2ypOgq
Content-Type: text/plain;
  charset="iso-8859-6"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Am Dienstag, 31. Mai 2005 02:26 schrieb Reinhold Kainhofer:
> Okay. So you imagine an event that start on June 1, 2005 and 14:00 recurs
> every Wednesday for 4 times. In OGo you store this as four events, that
> occur on
> -) June 1, 2005, 14:00
> -) June 8, 2005, 14:00
> -) June 15, 2005, 14:00
> -) June 22, 2005, 14:00
>
> What happens to the event on the server if you change the start date of t=
he
> June 15 event to June 13, 10:00, and you also change the summary? Will the
> recurrence still be detected as such?
>
> The iCalendar way would be that the original event has an RRULE:
>
> UID:1234567890
> DTSTART;TZID=3DCEST:20050601T140000
> RRULE:FREQ=3DWEEKLY;COUNT=3D4
>
> and when you change the start date of the June 15 event, the original eve=
nt
> would get an EXDATE:
>
> EXDATE;TZID=3DCEST:20050615T140000
>
> And a newly created event would have the new summary and:
>
> UID:1234567890
> RECURRENCE-ID:20050613T100000
> DTSTART;TZID=3DCEST:20050601T140000
>
> (Or something like that. I'm writing down these things from my head, so I
> might get some details wrong).

Okay, after re-reading rfc 2445, I think I got this completely and utterly=
=20
wrong (rfc  2445 doesn't really explain recurrence-ids very well).=20
There wouldn't be an EXDATE. And the newly created event would have the new=
=20
summary and:

UID:1234567890
RECURRENCE-ID;TZID=3DCEST:20050615T140000
DTSTART;TZID=3DCEST:20050613T100000

So, the recurrence-id determines which of the occurences of the original RR=
ULE=20
will be changed, and the DTSTART gives the new time for it.=20
Of course, this requires that the original event already has a recurrence s=
et=20
(either RRULE or RDATEs).

What I still don't understand is how this might ever work with the=20
THISANDFUTURE values of the RANGE property. If you change the date of the=20
recurrence, how will that be applied to all future events???

Cheers,
Reinhold

=2D-=20
=2D-----------------------------------------------------------------
Reinhold Kainhofer, Vienna, Austria
email: reinhold@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 / KPilot maintain=
er

--nextPart2120301.GEOz2ypOgq
Content-Type: application/pgp-signature

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

iD8DBQBCm7ToTqjEwhXvPN0RArSRAJwNcTtwzEICref4+5RQQv2VxoWL8gCgpdvw
UB2dfilNlDDqlmNGwAqRF0g=
=vukX
-----END PGP SIGNATURE-----

--nextPart2120301.GEOz2ypOgq--

--===============1043163623==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
kde-pim mailing list
kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
--===============1043163623==--