[caldeveloper-l] DTSTART that doesn't match RRULE pattern

[Neil Jenkins]

On Thu, 11 Oct 2018, at 6:46 AM, Cyrus Daboo wrote: 
> The intent of that was to effectively deprecate the behavior of DTSTART not  
> matching the pattern (without making it outright illegal by using a MUST),  
> with the idea that a future update to 5545 would switch to MUST. 
 
That's lovely in theory, but in practice there are still many clients that allow you to create such events. Apple Calendar, to take one example. While we can (and do in the FastMail UI) enforce that events *we* create have recurrence rules that match their DTSTART, we still have to handle events created in other clients, so for compatibility between different clients and calendar systems I think we should specify it rather than leave it undefined. The most sensible thing would be to choose the behaviour that's currently most prevalent and standardise on that. 
 
The FastMail UI currently matches the Apple Calendar behaviour (for compatibility with this): the DTSTART is always counted as the first occurrence, even if it doesn't match the rule. 
 
Neil. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.calconnect.org/pipermail/caldeveloper-l-calconnect.org/attachments/20181010/22e7caa8/attachment.html>