Re: [calsify] Feedback on draft-ietf-calext-icalendar-series

Thanks Neil

On 11/18/19 07:14, Neil Jenkins wrote:
> I think this concept is good, but this spec needs a fair bit more work 
> (as noted in the meeting today, this should have been a call for 
> adoption, not WGLC!)
>
> The "series master" is a kind of template; it's not an event itself, 
> it just generates them. It might make more sense therefore to make 
> this a different component, e.g. |VEVENTTEMPLATE|. Clients that don't 
> support the spec should simply ignore them, which is what we want. We 
> can also then reuse standard RRULE etc. properties and don't need to 
> define separate SRULE etc. properties.
>
Good idea - I'll work on that.
> I think we should mandate that the server manages generating the 
> instances; that's going to be by far the most useful option and we can 
> clearly define when this should happen in the spec.
That ties the data model in with one or more protocols. I'd prefer to 
leave that to related specs (or sections). However, I can see that with 
say a CalDAV stored series it MUST be the server.
> Changing the template (series master) should not change any generated 
> event that's now in the past; the question is what to do about those 
> in the future. It probably depends on what the change is (what if you 
> change the template SUMMARY? What about adding an RDATE? What about 
> changing the RRULE? Have iTIP messages already been sent out inviting 
> people to the event?). More thought needed here I think.
>
> I was very unclear how the "SPLIT" thing was meant to work in the 
> spec, which is related to the above; I would be interested to know 
> more about what Mike's proposing here.
I'll reread. I want to standardize the split approach from the start so 
we don't have the current recurrence issues. Dangling future overrides 
are always a problem if the rules change - this has been a major problem 
- set up months worth of instances - every one different then chaneg 
from weekly to bi-weekly.
>
> Neil.
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify