Re: [Storagesync] Storagesync Digest, Vol 5, Issue 1

["Fei Song" <[e-mail]>]

>you are giving a good example of something vastly different. Calendering 
>is a very well structured and very limited dataset (compared to free 
>text) that was made by design with sync considerations. The latest 
>version of vcard was also designed with sync considerations, and it took 
>a lot of time to get it right, (I can tell you I was the chair of 
>vcarddav when we did this). And a vcard is a pretty simple dataset and 
>very structured.

Good to know that~
If it is so hard for such simple and well-structured vcard case, should we handle this issue by seperating file based on their property?
The situation might be easier. 
Then the user can decide at the very beginning: I want to solve "File level conflicts" or "Interleaved level conflicts"

>
>So I think your point just shows the inverse. Merging complex, free, not 
>structured-limited-dataset files is very very difficult.
>
>I guess your goal is great, but to me, that is for research. So if 
>people want to do this work, I would split it into two working groups:
>- one on the IRTF side about generic sync-merge algorithms
>- one on the IETF side for the protocol components.
>
>Marc.

Fei Song