freebusy annotations

David Faure dfaure at
Mon Oct 25 20:22:52 CEST 2004

On Monday 25 October 2004 16:43, David Faure wrote:
> On Monday 25 October 2004 16:25, Bernhard Reiter wrote:
> > There is one question: 
> > What about notes and tasks folders for which we would require a
> > similiar annotation, but only for reminders (aka alarms).
> Oh. Then maybe we should rename the annotation to, hmmm....
> /vendor/kolab/incidences-for ?
> /vendor/kolab/relevant-for ?
> /vendor/kolab/incidences-relevance ?

Still thinking about naming, and semantics...

In fact this is quite related to the "attendees" of the incidence, isn't it?

Except that I could create an event where Till is an attendee, and keep it in 
my calendar, and this shouldn't generate freebusy and alarms for Till, since
he would have no way to fix that. That's the problem of correctness of the
information, but in a perfect world an incidence would simply relevant to 
whoever attends it. So while we don't want to actually parse incidences and
read the attendees from it, the semantic is still something like that.
So, unless this is too confusing, the freebusy-and-alarm-relevance annotation
could be named /vendor/kolab/attendees : "nobody", "owner", "readers"  (*)

(*) I just thought that "writers" could be useful too. If a calendar folder 
is shared by N people that are part of a working group (and have write
access to that calendar), and a few other people can read this calendar
for their information (secretary, higher-level boss, etc.), then the "attendees"
are the members of the group, but not the mere lurkers. Just a thought;
can always be implemented later.

David Faure -- faure at, dfaure at
Qt/KDE/KOffice developer
Klarälvdalens Datakonsult AB, Platform-independent software solutions

More information about the format mailing list