[Cosmo-dev] simplifying eimml

[Brian Moseley]

On 12/1/06, Morgen Sagen <morgen at osafoundation.org> wrote:
> 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.

hmm... we had talked a while back about metadata records that
described the structure of the data records, but thinking about how
that would work is making my head spin.

> 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>

if we group by item, then is there any need to include the uuid in
each individual record? and if we do this grouping, then we lose the
tabular eim structure, don't we? is that a problem?

i had assumed that it was the responsibility of the eim processor to
group records related to the same item. is that at odds with your sync
algorithm?