[Ietf-caldav] Some issues with caldav - subscriptions
gsbarnes at u.washington.edu
Thu Jul 28 10:50:22 PDT 2005
On Thu, 28 Jul 2005, Mike Douglass wrote:
> I don't think that works too well for something like free-busy. What if our
> user subscribes to our public "movies" calendar say and wants all of them to
> count as busy time? (I guess there might be a better example.)
A better example would be a 'Holidays' calendar. I want every Holiday to
be unschedulable busy time.
Or if I'm a member of the English Department, maybe I don't want any
meetings scheduled that overlap a lecture in the English Department's
Distinguished Lecturer series.
Computing and Communications, University of Washington
gsbarnes at washington.edu
> Also, if we use multiple clients the user has to configure all clients the
> same way to see the same results. I believe calendar aggregation is a
> sufficiently useful feature that servers should (also) be doing it and I
> believe it's also the only way to get a correct free-busy result.
> I understand that clients CAN do this and how. I just believe that we should
> allow servers to do it and make the appropriate accomodation in the protocol.
> Cyrus Daboo wrote:
>> Hi Mike,
>> --On July 27, 2005 9:02:58 AM -0400 Mike Douglass <douglm at rpi.edu> wrote:
>>> The result is that those events appear within their view of events,
>>> almost as if they were actually part of the calendar.
>> I believe that providing a single view of multiple calendars is a
>> client-side feature (preference) that is easily implemented with CalDAV by
>> running reports on each calendar and aggregating the results into one view.
>>> There's another feature which is that of 'adding' single events from
>>> other calendars into their own calendar. This is actually implemented as
>>> a sort of reference to the real event.
>> A CalDAV server could choose to support the proposed WebDAV BIND method as
>> discussed in
>> <http://www.ietf.org/internet-drafts/draft-ietf-webdav-bind-12.txt> to
>> support 'adding' single events to other calendars. I don't think we should
>> require support of that for CalDAV - it ought to be an option that each
>> implementation can support if it desires.
> Mike Douglass douglm at rpi.edu
> Senior Systems Programmer
> Communication & Collaboration Technologies 518 276 6780(voice) 2809
> Rensselaer Polytechnic Institute 110 8th Street, Troy, NY 12180
> Ietf-caldav mailing list -- Ietf-caldav at osafoundation.org
> See http://ietf.webdav.org/caldav/ for more CalDAV resources
More information about the Ietf-caldav