URLs/Rationalizing UUIDs treatment/ACLs/Export
jeffrey at osafoundation.org
Tue Aug 1 16:09:29 PDT 2006
>> EmailAddress is a separate item from a contact. When I share an event
>> with you, I let you know the UUIDs for any EmailAddresses in the to:
>> field. In this case lets say the EmailAddress is for PinkFlamingo, a
>> contact you already have. When you receive the item, your Chandler
>> would note the UUID my EmailAddress used in your version of PinkFlamingo
>> or PinkFlamingo's EmailAddress (probably creating a stub item with that
> This would certainly be the ideal solution. What's a good way to phase
> this? Store the UUID for now...but defer the reconciliation
> functionality until later.
Yup. Tracking the UUIDs is easy. We can write merge UI whenever we
need it in the future.
>> In this architecture, we could have a special restore-from-export option
>> that would get back the original UUIDs, we wouldn't need backup and
>> export actions.
> How realistic is this in Beta? Sorry to be a broken record.
This is less than a day's work on the export side of things for
iCalendar data. "Restoring" instead of importing iCalendar is similarly
easy. Merging UI may be time consuming, but presumably we can do that
when we do contact merging.
More information about the Design