This page

This page will eventually describe the calendar, task and event content models, along with information on date/time data. It's so far completely unorganized, I'm just throwing information together on the same page.

Related Links

• iCalendar UML -- diagrams

More calendar/task model cleanup

These are the items that aren't finished, and weren't done in the May/June timeframe as I was originally thinking....

• Work on attendee model?
• Work on date/time model
• Rationalize Body attribute with Mimi's 'notes' (see StampingWorkflow#Trash.ContentModel)
• Make recurrence work
• Make reminders work
• Make task requestee and meeting organizer work
• Rationalize how tasks and events relate to emails
• Make processing work

Calendar Cleanup Task - May 2004

Status: now done

Event changes gleaned from MitchKapor20040427, reviewed in the context of the existing content model, discussed with Mitch -- this forms a list of minor tasks involved in cleaning up the event and task content model and splitting them.

• Tackle dates or participants next -- gives me chance to mull over as I modify other event stuff
• Headline attribute: keep
• Body attribute: remove? What else would we do? Is it used?
  • Catch up with Mimi's design -- rationalize with Note
  • Remove if not used
• Location attribute: keep
• eventsAtLocation attribute: remove from Event...
• Recurrence: remove? is recurrence a requirement for 0.4?
  • If not used, remove
• Reminders: remove? Are these a requirement for 0.4?
  • If not used, remove
• Resources attribute: keep
• taskVsEvent: not how I would model...
  • Go ahead and split up
• Requestee attribute: remove -- probably won't be implemented all the way through any time soon.
  • Go ahead and remove until we know what we're doing with participant
• DependsOn^??/Blocks attributes: remove -- not required for 0.4
  • agreed
• Status attribute: keep for task, but not for event
  • Rename to TaskStatus^?
• Calendar attribute: remove because we're not doing it this way?
• Organizer attrribute: remove because we're not doing it this way?
• Time Transparency attribute: keep
• Add "event status" -- tentative, confirmed, cancelled -- to event only (split out task)?
• Add "related mail message" -- but what about our general approach to relationships?

-- LisaDusseault - 14 May 2004

Comments welcome

[Comment moved from ContentModelProject]

I found this summary of ISO 8601 date/time notation very useful. This summary provides a bit more detail. Unfortunately the complete specification seems only to be orderable from ISO or the US delegate to ISO, ANSI for $88. The W3C issued a note defining a "profile...[t]o reduce the scope for error and the complexity of software."

-- GrantBowman - 02 Apr 2004