[Cosmo-dev] Sharing work plan

[Katie Capps Parlante]

Morgen and I were discussing the steps for the sharing format 
implementation in more detail, in particular how they might fit up with 
the schedule and dependencies. I thought I'd write this up on the Cosmo 
list to make sure we're all in sync.

He listed out these tasks:
A. EIM record definitions         (first pass done)
B. XML serialization              (discussions in progress)
C. Implement importer/exporter callbacks
    - records --> items, items --> records
    - xml --> records, records --> xml
D. Implement synchronization/conflict detection algorithm
E. Dump/reload items to files
F. Hook up to DAV                 (current plan is to skip this step)
G. Hook up to morse-code

A couple of notes:
- We have not finalized the domain model on the Chandler side, so we 
could still need make changes to the EIM record definitions. In 
particular we'll need to review them for changes made to the recurrence 
implementation, for dashboard/triage support, for changes made to the 
mail schema, and for edit/update workflow support. (Edit/update workflow 
is about knowing who made the last edit, change notifications, etc.)

- Morgen is working on (C: importer/exporter callbacks) now, and expects 
that to take him ~3 weeks. He'll do a first pass at (E: dump/reload) as 
a way of testing the importer/exporter callbacks.

- The EIM API (and implementation) to support (C: importer/exporter 
callbacks) is ready. The EIM API (and implementation) to support (D: 
sync implementation) is happening in parallel with (C: importer/exporter 
callbacks).

- After previous discussions with BCM and Randy, we expect to skip (F: 
hook up to DAV) altogether and go straight to morse-code. The one worry 
we have is that we won't be able to hit a January deadline. An 
alternative is to have EIM-over-DAV up and running as a first stage, in 
January, as this will be quicker to get up and running. Another 
alternative is to get Andi to help with the protocol work to bring in 
the schedule.

Does this fit everyone's expectations? Will making changes to EIM 
records later in the process have a negative impact on Cosmo scheduling? 
Any other thoughts/concerns?

Cheers,
Katie