[Ietf-calsify] Sync: Was Question on VFREEBUSY

[Tim Hare]

I think if we are going to discuss sync we need a draft which documents how 
we can fit with SyncML or other generalized synchronization efforts to 
avoid reinventing the wheel.



At 02:08 PM 9/5/2005, Doug Royer wrote:

>In addition to those, synchronization information needs to
>be defined. As how to merge if both sides edited the same
>VEVENT.
>
>This is not a calsify issue as it has not been covered in any
>spec I have seen. I think this would have to be a new draft.
>
>
>Timi Soinio wrote:
>>ext Lisa Dusseault wrote:
>>
>>>These are good questions... my gut feel is that we certainly need 
>>>separate documents, perhaps more separate documents than we already 
>>>have. In practice, iCalendar is used for 3 separate purposes:
>>>- import and export -- where you don't worry about saving VFREEBUSY 
>>>information that duplicates event start/end times
>>>- invitation
>>>- CalDAV (or other access/sharing)
>>
>>In addition to these three usage purposes, I would also consider 
>>synchronization (with e.g. OMA DS) as a fourth important purpose for 
>>using iCalendar. Technically, it resembles import and export cases but it 
>>can contain some iCal properties that normally are left out from simple 
>>import/export (PUBLISH?) cases, e.g. ATTENDEE information.
>>-Timi
>>_______________________________________________
>>Ietf-calsify mailing list
>>Ietf-calsify at osafoundation.org
>>http://lists.osafoundation.org/mailman/listinfo/ietf-calsify
>
>--
>
>Doug Royer                     | http://INET-Consulting.com
>-------------------------------|-----------------------------
>
>               We Do Standards - You Need Standards
>
>
>
>
>
>_______________________________________________
>Ietf-calsify mailing list
>Ietf-calsify at osafoundation.org
>http://lists.osafoundation.org/mailman/listinfo/ietf-calsify

Tim Hare
Interested Bystander, Non-Inc.