> there is definite value in coming up with some kind of > calendaring standard, or else we will never have calendaring > interoperability, which is completely ridiculous. agreed.
personally i would be very interested in porting some of the datamodel behind calendaring to nodetypes. like the vcalendar, vevent and so forth. i think this would be very helpful to get calendaring interoperable. i believe that storing calendar information in a content repository is the right way to go. serialization/deserialization to and from icalendar and icalendar-xml should be straight forward. i think the above should be undoubted. once that is done we will have a generic way to bi-directionally access calendaring information through webdav. if someone feels compelled to then implement MKCALENDAR and the rest of CalDAV i think it should not be a lot of effort. regards, david
