[Ietf-calsify] Recommendations for stripping down iCal to
a manageable 'standard'
Chris_Stoner at notesdev.ibm.com
Chris_Stoner at notesdev.ibm.com
Wed Aug 18 08:28:25 PDT 2004
Dan Winship wrote:
> > 2.1) Better examples
>
> In particular, "the last work day of the month" requires both BYDAY and
> BYSETPOS, and that should probably be expressible.
>
> Lots of holidays require multiple BY*s as well (eg, the "U.S.
> Presidential Election Day" example uses 3). But then, does anyone really
> use those? I can't imagine what a UI would look like that would let you
> create an event like that...
>
> The RRULE semantics are just awful. (See how long it takes you to
> actually generate the aforementioned election day rule.) It would be
> nice to come up with a comprehensive list of examples, covering all the
> sorts of recurrences we think the spec should cover, and then come up
> with a new, simpler recurrence rule grammar that covers that.
This is exactly why a list of time/dates sounds to me like a better option
- we avoid having to think of and provide every possible rule situation
where the reciever needs to infer what you meant when you sent the invite.
-CS
More information about the Ietf-calsify
mailing list