False or absence of this element indicates a regular event. Otherwise, this attribute indicates that the event is an all-day event. All day events may span multiple days. By convention, all day events start at 12:00:00 am of the day of startTime, regardless of what time it actually is, and it will end at 11:59:59 pm of the endTime date. In other words, if the allDay element is present and has value=true, .NET Calendar will ignore the actual times of the events and consider only the date part of the field. <br/>The allDay tag is meant to operate as a hint to UI renders to display specialized icons indicating an all-day event. allDay events are distinguishable between 24-hr events starting at 12am. In the case of a meeting request, an allDay event will <b>not</b> appear in the local user's time zone, but rather in the organizer's time zone.

The cuid (CorrelationUID) links an organizer's event to an attendee's event. It identifies which response from an attendee is for which request from an organizer, and which meeting request update from the organizer is for which previously accepted meeting by the attendee. The "cuid" is the same on both the attendee's and the organizer's copy of the appointment. It is also identical on the orphan exception and the recurring master. This value is assigned by the .NET Calendar server and is non-modifiable. <br/><b>ICAL Equivalent</b>: UID.

The endTime method defines the end time of the event. An all-day event by convention ends at 11:59:59 PM of the ending day. This is stored in UTC. Maximum range is January 1, 1753 to December 31, 9999 to an accuracy of 3.33 milliseconds. The duration of the event is inferred from endTime - startTime.

The floating attribute indicates that this event is to occur in the current local time zone no matter what time zone the system is currently in (that is, it floats). For example, holidays are floating events. Floating values are stored as-is: no time-zone translations are needed to convert them to UTC or any local time zone.

This optional element annotates the freeBusy behavior of this event. All events by default appear as "busy". The user may explicitly define this event to be annotated by setting .NET Calendar values to free, tentative, busy or away. <br/>CONSIDER: turn into some freeform mechanism + set values.

This element contains an xhtml-compliant, free form, full description of the event.

This is updated by the organizer whenever s/he creates and sends a new meeting request. This helps the attendee to identify which meeting request is the most recent one. It is stored in UTC. This property is not modifiable by clients and is assigned by the server on modification and by the sendMeetingRequest. <br/><b>ICAL Equivalent</b>: DTSTAMP.

This optional element contains the event's location.

Tracks the status of this meeting {not-sent, sent, cancelled}. A regular appointment will not have this element. If <meetingStatus> exists, this event should be rendered as a meeting, not as an appointment.

This is the email address of the event organizer for non-.NET My Services organizers. <br/><b>ICAL Equivalent</b>: ORGANIZER.

The recurrence id indicates the original start time of an occurrence of a recurring master appointment. It is required to identify what instance an orphan exception is modifying, since users are allowed to change the start time on the orphan. The recurrenceId method is stored in UTC. It does not appear in the master schema, except in the specific case that an attendee is invited to an instance of a recurring event. Otherwise, <recurrenceId> is usually only a part of getCalendarDays. <br/><b>ICAL Equivalent</b>: RECURRENCEID

The startTime method defines the start time of the event. An all-day event by convention starts at 12:00:00 AM of the day of the event. This is stored in UTC. Maximum range is January 1, 1753 to December 31, 9999 to an accuracy of 3.33 milliseconds. <br/>If this event is a <b>recurring event</b>, <startTime> defines the dateTime when the recurrence window starts. The recurring master does not have to be an instance of the recurring event itself. An event in March set to recur every April will only appear in April.

This is the amount of time (in minutes) that it takes to return from the meeting location. <p> This optional element shows in free/busy calculations. </p>

This is the amount of time (in minutes) that it takes to travel to the meeting location. <p> This optional element shows in free/busy calculations. </p>

Additional body elements.