Tickets :: Comment on [#12516] CardDav attribute value delete

* Your Email Address
* Spam protection	Enter the letters below: .___. ,.__ .___..__ [__ \./ [__) \| \| \ [___ \| [__) \| \|__/
Comment	> Reading a bit more, it looks indeed as the exchanged vCard object > represents the complete contacts object. (The same applies for > iCalendar and events of course). That means that importing a vCard > object should only use the available properties and delete any other > properties from the server. > > I still don't feel comfortable with that, because: > 1) we would have to make sure to export all properties completely > so that clients at least have a chance to not lose data when sending > updates back to the server > 2) I would expect that some clients simply won't re-export some > unsupported properties leading to data loss when sending updates back > > The same is of course true for Turba as the CardDAV server. We drop > unsupported properties too. To fix this, we would have to store the > complete vCard/iCalendar objects for every import. > https://oxpedia.org/wiki/index.php?title=AppSuite:VCardMapping has > some good algorithms as how to proceed with such an attempt. > > TL;DR: this requires massive changes and restructuring in how Turba, > Kronolith, and Nag work.
Attachment
Watch this ticket