[cosmo-dev] caldav<-->chandler model

Grant Baillie grant at osafoundation.org
Fri May 16 10:53:47 PDT 2008


Hi, Randy

Comments inline below ...

--Grant

On 16 May, 2008, at 09:29, Randy Letness wrote:

> Bug 12037 (https://bugzilla.osafoundation.org/show_bug.cgi?id=12037)  
> deals with changing the way caldav resources are mapped to the  
> chandler model.
>
> Currently the caldav mapping looks like:
>
> new VEVENT--> NoteItem with EventStamp
> new VTODO --> NoteItem with TaskStamp
> new VJOURNAL --> NoteItem
>
> NoteItem with EventStamp --> VEVENT
> NoteItem with no EventStamp, but with TaskStamp --> VTODO
> NoteItem with no EventStamp and no TaskStamp --> VJOURNAL
>
> The bug proposes we export all NoteItems without an EventStamp as  
> VTODO to make it easier to share information with clients such as  
> iCal.  If we do this, what happens to VJOURNAL?  Do we support it?   
> Do we import VJOURNAL as a NoteItem the first time and export it as  
> VTODO the next time?  I don't know of any clients that support  
> VJOURNAL so I'm not sure if its even worth supporting.
>
> Also, VTODOs can contain date information and the server just stores  
> this extra data and doesn't do anything meaningful with it.  Should  
> a VTODO with date information be imported as NoteItem + TaskStamp +  
> EventStamp and the same item be exported as VTODO?  How does the  
> desktop handle this?  This would require a lot more work but would  
> probably make more sense.

That is what the desktop does (i.e. VTODO+DUE --> Note+TaskStamp 
+EventStamp, though "TaskStamp" is now "Starred"). See also Bug 11922 (https://bugzilla.osafoundation.org/show_bug.cgi?id=11922 
) which is the desktop analog to the above cosmo bug.

Currently, the desktop doesn't support import/export of VJOURNAL,  
largely because of its scarcity in the wild. In theory, in the CalDAV  
case, we know which components the server supports, and tailor note  
export to use VTODO/VJOURNAL accordingly. Unfortunately for Cosmo, in  
the reverse case there's no requirement for clients to identify what  
they support.

> So the mapping would look like:
>
> VEVENT --> NoteItem with EventStamp
> VTODO without dates --> NoteItem
> VTODO with dates --> NoteItem with TaskStamp and EventStamp
>
> Thoughts?
>
> -Randy
>
>
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev



More information about the cosmo-dev mailing list