[Cosmo-dev] new eim record type for event overrides
Randy Letness
randy at osafoundation.org
Tue Jan 9 11:36:01 PST 2007
Currently, there is a single event record type that is used to represent
master events and override events. Override events are represented by a
non-null "RecurrenceId" attribute. This means that the primary key for
event records is really the event uuid and the recurrenceId. This is a
problem for master events, because they have a null recurrenceId. Also,
override events will never use rdate, exdate, rrule, exrule.
After talking to Brian, he proposed having a separated record type to
represent override events. This new "override" record type would have
two key fields, uuid and recurrenceId, and the current event recordtype
would no longer need the recurrenceId attribute. So things look like:
<event:record xmlns:event="http://osafoundation.org/eim/event">
<event:uuid eim:type="text" eim:key="true"><![CDATA[e55b5f1c-a20d-4d47-acda-c43049967281]]></event:uuid>
<event:dtstart eim:type="text"><![CDATA[20061220T090000]]></event:dtstart>
<event:dtend eim:type="text"><![CDATA[20061220T100000]]></event:dtend>
<event:location eim:type="text"><![CDATA[]]></event:location>
<event:rrule eim:type="text" />
<event:exrule eim:type="text" />
<event:rdate eim:type="text" />
<event:exdate eim:type="text" />
<event:status eim:type="text" />
</event:record>
<eventOverride:record xmlns:event="http://osafoundation.org/eim/eventOverride">
<eventOverride:uuid eim:type="text" eim:key="true"><![CDATA[e55b5f1c-a20d-4d47-acda-c43049967281]]></eventOverride:uuid>
<eventOverride:recurrenceId eim:type="text" eim:key="true"><![CDATA[20061220T090000]]></eventOverride:recurrenceId>
<eventOverride:dtstart eim:type="text"><![CDATA[20061220T090000]]></eventOverride:dtstart>
<eventOverride:dtend eim:type="text"><![CDATA[20061220T100000]]></eventOverride:dtend>
<eventOverride:location eim:type="text"><![CDATA[]]></eventOverride:location>
<eventOverride:status eim:type="text" />
</eventOverride:record>
Does this make sense? Comments, suggestions, concerns?
-Randy
More information about the cosmo-dev
mailing list