[Tickets #8703] Re: %-completion on tasks submitted by Kontact/Akonadi is not accepted
bugs at horde.org
bugs at horde.org
Mon Nov 30 13:01:52 UTC 2009
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/8703
------------------------------------------------------------------------------
Ticket | 8703
Updated By | Jan Schneider <jan at horde.org>
Summary | %-completion on tasks submitted by Kontact/Akonadi is
| not accepted
Queue | Nag
Version | FRAMEWORK_3
Type | Bug
-State | Feedback
+State | Not A Bug
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------
Jan Schneider <jan at horde.org> (2009-11-30 08:01) wrote:
Re-reading RFC 2445 again, I'm pretty sure that Akonadi is wrong. They
use the PERCENT-COMPLETE property to indicate the task status instead
of the STATUS property like Nag does. RFC 2445 says:
Property Name: PERCENT-COMPLETE
Purpose: This property is used by an assignee or delegatee of a to-do
to convey the percent completion of a to-do to the Organizer.
Property Name: STATUS
Purpose: This property defines the overall status or confirmation for
the calendar component.
Description: In a group scheduled calendar component, the property is
used by the "Organizer" to provide a confirmation of the event to the
"Attendees".
So the difference is that PERCENT-COMPLETE is used by attendees to be
consumed by organizers, while STATUS is used by organizers to be
consumed by attendees. Editing and saving a task on the (Nag) server
is done by the task organizer (or anyone with the same permissions)
and authoritative for anyone consuming this task. This is *not* an
update from an attendee sent to the organizer. The RFC even explicitly
mentions that PERCENT-COMPLETE is per attendee, so that attendees can
report back different completion states for their parts of the task.
It is *not* to be stored with the task. How should that work anyway if
this a property of the VTODO component but can be different for each
attendee?
More information about the bugs
mailing list