[caldeveloper-l] Recurrence override with RRULE

[Filip Navara]

It is possible to have both properties in some cases, but it's also not universally supported and interoperable.




The case is having "RECURRENCE-ID;RANGE=THISANDFUTURE:" and then overriding the rest of a the recurring series with a new RRULE. In practice most clients split the recurrence into two separate events and deal with the consequences (https://github.com/apple/ccs-calendarserver/blob/master/doc/Extensions/caldav-recursplit.txt).




F.
 

-----Original Message-----
From: "Garry Shutler" <garry at cronofy.com>
To: caldeveloper-l at lists.calconnect.org
Date: 04/05/18 12:46
Subject: [caldeveloper-l] Recurrence override with RRULE


Hi,


We've come across a weird one which I can't decide from the RFCs how it should be dealt with (so we're going by how it's displayed when imported).


Here's a cut down example of what we've seen:



BEGIN:VCALENDAR
VERSION:2.0
BEGIN:VEVENT
DTSTART:20180323T070000Z
DTEND:20180323T083000Z
RRULE:FREQ=DAILY
SEQUENCE:0
SUMMARY:example
UID:override-with-rrule
END:VEVENT
BEGIN:VEVENT
DTSTART:20180323T080000Z
DTEND:20180323T093000Z
RECURRENCE-ID:20180323T070000z
RRULE:FREQ=DAILY
SEQUENCE:0
SUMMARY:example
UID:override-with-rrule
END:VEVENT
END:VCALENDAR


I thought that a RECURRENCE-ID couldn't have a RRULE and/or that only the master should have RRULEs. I can't find anything in the RFCs to confirm this (my Google-fu/reading skills may be weak!).


To reflect what is displayed in Calendar.app we're ignoring the RRULE in the override. However, I wanted to check here to see if that's what we should be doing, whether this is valid, etc.


Cheers,

Garry




Garry Shutler | CTO

_______________________________________________
caldeveloper-l mailing list
caldeveloper-l at lists.calconnect.org
http://lists.calconnect.org/listinfo.cgi/caldeveloper-l-calconnect.org


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.calconnect.org/pipermail/caldeveloper-l-calconnect.org/attachments/20180405/697fa57e/attachment.html>