[Ietf-caldav] Dead properties on CalDAV events / folders

[Helge Hess]

On 19. Dez 2005, at 06:34 Uhr, douglm at rpi.edu wrote:
> We should be able to state quite explicitly the requirements for
> interoperability.

There was plenty of discussion on that now and honestly I think  
further discussion will lead to nowhere, everyone has stated his  
opinion.
So far everyone seems to have a different opinion on that and I have  
the impression that the topic will just get "dropped" as  
unresolvable? Or is there some way to vote on the issue in a useful way?


In response to the valid issues raised by Julian (and others) I think  
I've changed my opinion to:
- CalDAV servers are required to store verbatim copies
- PROPPATCH is a SHOULD just like in WebDAV
Why? Because HTTP/WebDAV is designed with that assumption in mind and  
it keeps the CalDAV protocol clean.

If a server doesn't comply with all strict requirements of CalDAV it  
is very likely to work with real world clients nevertheless. But to  
be fully-CalDAV compliant, it would need to work exactly as described  
in the spec.

This is how it works in the real-world for WebDAV. Few do 100%  
correct implementations but still interoperability is quite good.


> at least we can still see the events and invite people to our  
> meetings and surely that's the main point.

For inviting people to our meetings we can already use iMIP. IMHO the  
main point of CalDAV is to provide a client/server calendar _storage_  
protocol. And if most/all clients will need an _additional_ storage  
to save their "own" stuff, this would be extremely annoying.

Eg if our Outlook storage provider can't store additional Outlook  
information in X- fields there is no other way but to require the  
user to enter a CalDAV URL _and_ another URL where additional data  
will get stored. Then it will also need to keep those in-sync. Major  
bummer ...

Greets,
   Helge

PS: this "abuse" subthread is IMHO indeed paranoid. M$ will modify/ 
call a mixup derivate CalDAV whenever they like, this isn't bound to  
any specific feature in CalDAV. (Windows WebFolders is a prime  
example ...)
-- 
http://docs.opengroupware.org/Members/helge/
OpenGroupware.org