[Cosmo-dev] changing the format of modification recurrence-ids in eim

[Brian Moseley]

as bug 9054 describes, eim modification uuids are really long and hard
to understand with casual inspection by humans.

given that eim is the data model for cosmo's public atom-based api as
well as morse code, and that items are addressed in this api by their
uuids (eg http://localhost/cosmo/atom/collection/<uuid>), it would be
preferable for all item uuids, modification or otherwise, be
relatively easy to read, parse, paste into emails, and otherwise
examine by humans.

jeffrey and i came up with the idea of representing the recurrence-id
part of the modification uuid as a utc timestamp rather than as
icalendar-like value with embedded properties and internal delimiters
and so on. so the example from bug 9054,
"f2953300-6fcb-4547-ad7b-22e193b6903f::;VALUE=DATE-TIME:20070511T090000",
would turn into something like
"f2953300-6fcb-4547-ad7b-22e193b6903f:1178666002".

jeffrey suggested this would be a couple days' work on the chandler
end to translate between the timestamp and whatever internal data
structure chandler requires. as far as i can tell, no changes would be
required on the cosmo end.

we think it makes sense to make the change before preview. assuming
that the server does not require any changes, then it can be done on
the desktop's schedule.

morgen, grant, randy - thoughts?