Re: [calsify] SKIP was Re: AD review of draft-ietf-calext-rscale-03

[Barry Leiba <[e-mail]>]

> As mentioned in another thread, I'd prefer to have SKIP=BACKWARD as default
> to reduce the total amount of text in RRULEs (that is, sum of all RRULEs
> stored in the world). Length of RRULEs matter from both performance and
> readability point of view. But SKIP=OMIT is an acceptable compromise if
> consensus points in this direction.

And yet I'm still concerned that trying to define SKIP rules outside
the context of implementation of a specific calendar is complex and
error prone.  It remains my contention that the best thing to do
(which also keeps the rules short) is to say that how RRULEs that
contain RSCALE work without SKIP is dependent upon the calendar
specified in RRULE, and that when you implement a particular calendar,
you have to know how that calendar works and support it properly.
Then we reserve SKIP for exception situations.

I do NOT think that we need to accompany this with any list of
calendars.  Whoever implements a particular calendar needs to know how
it works in order to generate the right SKIP values anyway.  So why
not just say that, and forget about having to include the SKIPs?

Barry