[Ietf-caldav] Data model issue
daboo at isamet.com
Wed Aug 25 14:13:22 PDT 2004
--On Wednesday, August 25, 2004 2:10 PM -0700 Lisa Dusseault
<lisa at osafoundation.org> wrote:
> I agree with all of that.
'That' being the second of the two possible ways of doing it, right?
> On Aug 25, 2004, at 2:06 PM, Cyrus Daboo wrote:
>> What is the 'raw' iCal data in each vevent etc resource? Is it a full
>> iCalendar data object (i.e. BEGIN:VCALENDAR...END:VCALENDAR), or just
>> the component (i.e. BEGIN:VEVENT...END:VEVENT)?
>> If the former, that adds a lot of redundant information to each
>> resource, given that the calendar-specific info could be gleaned from
>> properties on the calendar collection that contains the components.
>> If the later, we must require clients to check the VERSION/CALSCALE
>> etc on the calendar collection to be sure it can handle components of
>> that type. Plus I think the MIME type should not be text/calendar, but
>> rather a new text/calendar-component type.
More information about the Ietf-caldav