Pre-KEP input sought: Priority for events? (in line with tasks?)(similar to VEVENT & VTODO?)

Doug Finch dfinch at
Wed Jun 1 23:22:06 CEST 2011

As a middle ware integration company, we find that we must accommodate
both sides of the equation.  It may be that the majority of people
don't use priorities in calendar events or tasks, but you will hear
from the one company that uses them and now cannot.  Exchange is
everywhere and because of that, whether we want to admit it or not, we
all compete with it.  If Outlook has a feature that Exchange users are
used to using - when we try to sell our product to them they will
expect it to work there also. As for handling both sides of the
equation, since there is no "priority" currently, we had to blaze our
own method (see Shawn Walker's post) of handling these events so that
our client (Bynari Connector) knows what to do with them.  The reality
is that, even though our customers don't use Exchange, they may be
interacting with people that do.  If an Exchange user sends a meeting
request to you with a high priority assigned to it, the client must
know what to do with that information.  Our Outlook users are going to
expect to see it working.Regards,

 Doug Finch
 222 W. Las Colinas Blvd, Suite 1540E
 Irving, TX 75039
 Skype ID dfsixstring [1]

 ------ Original Message ------
 From: Bernhard Reiter 
 Date: Wednesday, June 1st, 2011 4:18 AM CDT
 To: kolab-format at
 Subject: Re: Pre-KEP input sought: Priority for events? (in line with
tasks?)(similar to VEVENT & VTODO?)

 Am Dienstag, 31. Mai 2011 19:24:01 schrieb Georg C. F. Greve:>  (a)
Does anyone else have this requirement, and particular cases they>    
    would request to have taken into account?So far I have not
encountered a request here.I'd be interested in understandingthe
requirements of this request better.What problem are they attempting
to solve? Is there a special workflow?>  (b1) Should we add priority
to the 'event' object type?>>  (b2) Or should we move priority one
level up from 'task' into the common> fields in events and tasks, of
which there are already several?b2) sounds good, if we are about to
make the change.>  (c1) Should we implement the 0-9 priorities of
iCalendar?>>  (c2) Or should we stay with the 1-5 approach?All I can
say is that I have not seen priorities used a lot,not even with tasks.
The iCalendar task system seems to be missing a lot to become a real
project or inter-project management product, for cases where a
specialised tool is required. In order to keep users happy, we want to
offer them a solution to their organisational needs. Adding priorities
could be a solution, but it might not be a good or preferred solution.
This is why I usually aim for understanding of the challenge the user
faces first, before making that call.Best,Bernhard-- Managing Director
- Owner:       (Free Software Company)Deputy
Coordinator Germany: Board member: GmbH, Osnabrück, DE; Amtsgericht
Osnabrück, HRB 18998Geschäftsführer Frank Koormann,
Bernhard Reiter, Dr. Jan-Oliver Wagner

More information about the format mailing list