[Ietf-caldav] CalDAV Client work?
lisa at osafoundation.org
Mon Aug 16 13:23:15 PDT 2004
Right now, integration would be barely possible but certainly not
stable. Until we move to publishing something based on a standard
format, other projects could integrate with Chandler as a one-off
project -- not too hard but certainly extra work. The attributes
Chandler uses internally aren't pure iCalendar data, although of course
there's some similarity.
On Aug 14, 2004, at 10:29 AM, Helge Hess wrote:
> On Aug 13, 2004, at 19:14, Lisa Dusseault wrote:
>>>> Chandler also uses vanilla WebDAV to share its content items of all
>>> Could you elaborate? How does it use WebDAV for that?
>> We're currently working on a spec and an implementation for that.
>> Some highlights of the current plan:
>> - Chandler collections are mapped to WebDAV collections
>> - Chandler content items are mapped to one or more WebDAV resources
>> - Chandler attributes on items are mapped to WebDAV properties
>> - Thus, a user will be able to publish a calendar by selecting the
>> collection and uploading it to a new WebDAV collection, and another
>> client can download the calendar or be granted shared access to the
>> event items in the calendar
>> - Both the initial calendar publisher and the people sharing the
>> calendar will synchronize changes periodically
> Sounds good :-)
> Because the Chandler attributes are something non-standard this won't
> be useful for integration? Or do the attributes follow some "standard"
> (eg match iCal/xCal properties)?
More information about the Ietf-caldav