[Cosmo-dev] sharing update 12/20

[Brian Moseley]

after a long and productive meeting on irc where we hammered out many
if not all of the remaining eimml issues, the spec is updated:

<http://wiki.osafoundation.org/bin/view/Projects/EimmlSpec>

changes include:

    * made record's uuid a field (mandatory, since it is the record key)
    * removed the namespace from recordset's uuid attribute to make it
clear that recordset is the only core element that knows anything
about uuids
    * added eim:key attribute denoting a field that is a record's
primary key (or part of a compound primary key)
    * added integer field type
    * added timestamp field type and made item:createdOn a timestamp field
    * replaced lob field type with clob and blob field types and made
note:body a clob field

cosmo is now outputting xml exactly like spec example #1.

still to do:

    *  handle unknown records and fields [bcm]
    * consume and emit event records for event exception instances [bcm]
    * correctly parse and store timezones for datetime fields
(requires DateAttribute? to store timezone) [randy]
    * add new Item attribute that stores item:createdOn rather than
overwriting the server creation date [randy]

open questions:

    * cosmo only supports event rdates and exdates that specify lists
of icalendar dates. icalendar also allows rdates and exdates to
specify lists of periods. is it okay for event:rdate and event:exdate
to have values containing either dates or periods? if either, that
implies we need to include the icalendar VALUE parameter in the field
value as well.

    * similarly, cosmo only supports icalendar datetimes for event
dtstart, dtend, and recurrenceid. do we need to support icalendar
dates as well? these icalendar properties all have a VALUE parameter
too.