[Cosmo-dev] simplifying eimml

[Morgen Sagen]

I don't have much more to add beyond what Phillip explained so well.   
The fact that the sync algorithm can work on current and future  
schemas (even those extended by third parties) without having to  
understand the specific domain models is a big win.  I believe that  
one issue that came up when he and I were working on the algorithm  
was that records we get from Cosmo need to be grouped by item UUID,  
so that the Chandler sharing layer knows which item the records  
correspond to without needing to know what the various fields inside  
a record actually signify -- in other words, without having to know  
that the first field of a record happens to be a UUID.  Something like:

ex 5:

  <item uuid="d1dd801c-f682-4bcb-b187-46b8c427e77f">

   <item:record>
    <item:uuid>d1dd801c-f682-4bcb-b187-46b8c427e77f</item:uuid>
    <item:title>Cosmo: Status</item:title>
    <item:createdOn>2006-11-29T12:30:09-0800</item:createdOn>
  </item:record>

  <note:record>
    <note:uuid>d1dd801c-f682-4bcb-b187-46b8c427e77f</note:uuid>
    <note:body>Cosmo status meeting</note:body>
    <note:icalUid>1e2d48c0-d66b-494c-bb33-c3d75a1ba66b</note:icalUid>
  </note:record>

  <event:record>
    <event:uuid>d1dd801c-f682-4bcb-b187-46b8c427e77f</event:uuid>
    <event:dtstart>20061130T140000</event:dtstart>
    <event:dtend>20061130T150000</event:dtend>
    <event:rrule>FREQ=WEEKLY</event:rrule>
    <event:status>CONFIRMED</event:status>
  </event:record>

  </item>

Phillip, correct me if I'm wrong, but does the grouping-by-item  
requirement go away when we truly start sending diffs back and forth  
and not always send complete sets of records?

~morgen