[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RECAP & Questions of CPL RECUR Issues.
> If my calendar turns "every Monday for a year" into "1/1, 1/8, 1/15,
>1/22, ...", then I can't edit it to be "every Tuesday" without a massive
>investment of my time.
Under the covers it is going to have to roll it out somehow so that the entries can be shown in the UI to you (or so that 'exceptions' or changes to individual instances can be applied and managed!). If the UI makes a change that requires _you_ to jump thru hoops to reschedule them all, is that the problem w/the spec or w/the CUA? We are not in the business of spec'ing out UIs for CUAs here, we are in the business of specing out a data interchange and interop format. They are not the same things; go get a better CUA w/a better UI...
>Yeah, but I don't think they simplify the conceptual model; they just add extra
>limitations that the user has to understand.
From what Ive been able to get out of the exchange between iptel and calsch is that the concerns are not those of the end users but rather the vendors implementing iptel. As such, "user confusion" is not a likely conern (unless you expect a poor UI/GUI and thats not something we can or should try to spec out).
Besides, what CU is actually reading RRULEs that their CUA generates and trying to understand them?!?! A whole lot fewer than those that don't do/try it. The recurrence grammar/model is not something that CUs will (or should!) really have to worry about. They simply want to be able to schedule "that weekly Monday AM and Thursday PM team meeting for the next 18 months at 9AM".
Bruce Kahn INet: Bruce_Kahn@xxxxxxxx
Iris Associates Phone: 978.392.5335
Westford, MA, USA 01886 FAX: and nothing but the FAX...
Standard disclaimers apply, even where prohibited by law...