I intend to use VTODO. Right now I only use VEVENT. Conceptually I do not support TODO items YET.

But while I use VEVENT, I do not force user to add attendee......the by-product of that is that organizer can create an event just for himself. Which effectively can be a TODO item for the Organizer.

I did not intend it this way. It turned out this way. Now I am just testing various use-cases.

When I conceptually support TODO, I will use VTODO as that is right way to do things.

Best Regards,

On Thu, Mar 19, 2015 at 3:33 PM, Andre LaBranche <dre@apple.com> wrote:

On Mar 19, 2015, at 12:12 PM, Gaurav Jain <monkeyfdude@gmail.com> wrote:

Its an experiment to find out if VEVENT can be used for VTODO.....

Hi,

I’m all for experimentation, however I’m curious why you wouldn’t want to use VTODO for task items. I can’t personally enumerate all the reasons that VTODO exists as a distinct component type, but I feel confident in saying that there are reasons :)

Looks like RFC 2445 contains the formal definitions of the VTODO and VEVENT component types, in section 4.6.

-dre