110 likes | 255 Views
IETF Calendar and Scheduling Working Committee. Board discussion San Francisco 2/99. Model. Calendar is associated with a calendar user (CU) Calendar is a collection of calendar properties and calendar entries Calendar properties are attributes associated with the calendar as a whole
E N D
IETF Calendar and Scheduling Working Committee Board discussion San Francisco 2/99
Model • Calendar is associated with a calendar user (CU) • Calendar is a collection of calendar properties and calendar entries • Calendar properties are attributes associated with the calendar as a whole • Entries are a collection of properties associated with a date • Entries examples: events, to-dos, journals • Property is a named value
Calendar User (CU) • An individual, group, resource or room addressable in a calendar domain • May be represented by a Calendar User Agent (CUA) • CU may add, delete, modify (ie, manipulate) calendar properties or entries (ie, calendar content) within its own calendar..subject to access control • CU may manipulate calendar content associated with another calendar user..subject to the access control of the other calendar
Property • A named value • Strongly typed • Maybe further qualified by property parameters • May be multi-valued • May have multiple instances • May be logically grouped • Calendar and component specific
CalendarObject Model Calendar Component Properties Calendar Components To-do Calendar Properties Event Alarm Alarm Journal Timezone FreeBusy
Calendar User Agent (CUA) Calendar User Agent (CUA) Mail User Agent (MUA) Mail User Agent (MUA) Mail Transfer Agent (MTA) Mail Transfer Agent (MTA) Transport Transport CalendarMail Transport Model Calendar User (CU) Calendar User (CU) Calendar Exchange Protocol (CXP)
CalendarSystem Model Calendar User (CU) Calendar User Agent (CUA) Calendar Exchange Protocol Calendar Calendar Access Protocol (CAP) Calendar Exchange Medium Calendar Calendar Service CAP Calendar User (CU) Aggregate CUA
Calendar User Agent/Calendar-Boundary Interactions • CUA-1 creates an entry in a calendar that it owns (doesn’t involve CUA, CXP) • CUA-1 creates an entry in own calendar and requests a copy be created in one or more other CUAs calendar called a group scheduled entry (e.g., EVENT-REQUEST) • CUA-1 can make updates to a group scheduled entry that it owns (e.g., EVENT-REPLACE, EVENT-CANCEL, EVENT-DELEGATE) that will require interactions with CUA-2..CUA-n • CUA-2 can make certain updates to a group scheduled entry that it does not own that will require interaction with CUA-1 (e.g., EVENT-REPLY, EVENT-COUNTER, EVENT-DELEGATE) • CUA-2 can make other updates to group scheduled entry that it does not own that will not require interaction with CUA-1
Other Protocols in use with the CAP protocol • IMIP • Icalendar Messaging-based Interoperability protocol • to send calendars as a message over email • IRIP • Internet Real-Time Interoperability Protocol • Allow calendar stores to talk direct to other calendar stores, real time • ITIP • iCalendar Transport-Independent Interoperability Protocol • added semantics for group scheduling methods