Picking up an old thread, as I try to catch up on my design list reading: Morgen Sagen wrote: > > On Nov 9, 2005, at 10:29 PM, Alec Flett wrote: >> We could include version information along with sharing information >> when we post CloudXML to cosmo, then you could "play back" the changes >> within your repository, and commit in between each change so that your >> repository versions match the version set you just downloaded. > > One problem is that while we could add additional version info to > CloudXML (basically replacing CloudXML with a log of changes), just > about all CalendarEvent properties are shared via iCalendar (.ics) > resources, which we don't really have the ability to change the format of.
As it happens, iCalendar has the notion of a sequence number associated with events, an event can be serialized as a sequence of revisions. At the moment Chandler ignores the sequence number, but this is a bug. It's not clear to me how the iCalendar model of versioning will interact with what Chandler needs, but we wouldn't be starting from nothing. Sincerely, Jeffrey _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
