[Ietf-caldav] Dead properties on CalDAV events / folders
douglm at rpi.edu
Thu Dec 15 07:54:27 PST 2005
As it say's in the rfc
x-name = "X-" [vendorid "-"] 1*(ALPHA / DIGIT / "-")
; Reservered for experimental use. Not intended for use in
; released products.
As a server I won't know if an x property is supposed to be multi-valued
for example. I would take the position that I shouldn't have to preserve
I think it would also be a problem to require that the server store
arbitarry non-calendar - that would make it more diffficult to interface
existing calendar systems with a caldav front-end
Helge Hess wrote:
> I think it would be good if the CalDAV spec would be very specific on
> whether or not a CalDAV server is required to support arbitary dead
> properties for authenticated users.
> Some WebDAV implementations simply reject PROPPATCHes with a 403
> Forbidden (usually because they do not support custom properties [501
> would be more appropriate, but with a 403 the operation can be
> rejected while still being "formally compliant" ...]).
> This is important to resolve because a client developer must know
> whether he can rely on using dead properties to store non-iCal
> associated state in the server (which seems natural) or whether he
> must resort to use x- properties. And even for the latter it would be
> good if CalDAV would explicitly specify whether the server is
> required to preserve arbitary iCalendar x- attributes in the content.
> To give a real world example, a MAPI storage provider would need some
> place to store additional MAPI properties not covered by plain
> iCalendar (for example the color label in OL 2003).
> The same goes for folder information (eg MAPI associated contents of
> a folder which are used to store the last selected view).
Mike Douglass douglm at rpi.edu
Senior Systems Programmer
Communication & Collaboration Technologies 518 276 6780(voice) 2809
Rensselaer Polytechnic Institute 110 8th Street, Troy, NY 12180
More information about the Ietf-caldav