Schema for .NET Calendar service Copyright (c) 2001 Microsoft Corporation. All rights reserved. This element encapsulates the content document for this service. This element establishes a global cache scope for the service and contains other root level system attributes for this instance of the service. This element defines the basic myCalendar types. The event is the myCalendar root object for calendar events, appointments, and meetings. This element contains an xhtml-compliant, free form, full description of the event. 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. 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.
ICAL Equivalent: RECURRENCEID 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.
ICAL Equivalent: DTSTAMP. 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.
If this event is a recurring event, <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. 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. 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.
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 not appear in the local user's time zone, but rather in the organizer's time zone. 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 is the amount of time (in minutes) that it takes to travel to the meeting location.

This optional element shows in free/busy calculations.

This is the amount of time (in minutes) that it takes to return from the meeting location.

This optional element shows in free/busy calculations.

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.
CONSIDER: turn into some freeform mechanism + set values. 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.
ICAL Equivalent: UID. This is the email address of the event organizer for non-.NET My Services organizers.
ICAL Equivalent: ORGANIZER. Additional body elements. Additional recurrence rule logic that cannot be expressed in .NET Calendar logic. Additional recurrence rule elements. This is required in order to exactly determine which timezone recurrence rule to use. We cannot use the startTime of the event because of the ability to create events in the past and in the future. This stores what the first day of the week is for this user. Typical values are (su) Sunday or (mo) Monday.

Recurrence rule's specified FirstDOW for calculating the recurrence expansion. Allows recurring meetings to be expanded in the organizer's FirstDOW instead of the invitee's FirstDOW.
Outlook and ICAL Equivalents: FirstDOW Identifies the time zone for this recurring event. All dateTime information in this event is stored in UTC (converted from the local time zone defined by the time zone sub-schema). If this field is absent, the recurring event is assumed to be recurring in UTC time. However, it is only a floating recurring event if the <floating> attribute is set. @afterDay is used as a placeholder for v1. @afterDay will not be use for .NET My Services V1. 
        <timeZone floating="..." id="...">1..1
            <standardBias>1..1</standardBias>
            <additionalDaylightBias>0..1</additionalDaylightBias>
            <standardDate>0..1
                <transitionRule weekdayOfMonth="..." day="..." dayOfMonth="..." month="..." afterDay="...">1..1</transitionRule>
                <transitionTime>1..1</transitionTime>
            </standardDate>
            <daylightDate>0..1
                <transitionRule weekdayOfMonth="..." day="..." dayOfMonth="..." month="..." afterDay="...">1..1</transitionRule>
                <transitionTime>1..1</transitionTime>
            </daylightDate>
        </timeZone>
[International calendar support]
It is possible to derive isLeapYear from leapMonthValue, but .NET Calendar stores both separately. See leapMonthValue for a use-case scenario. [International calendar support]
<leapMonthValue> cannot be derived from a particular year and thus must be stored. For example, a user creates a recurrence on a Hebrew Lunar calendar. The year is a leap year and it has 13 months. In that year, the leapMonthValue is 7. This dateTime indicates the end of the window over which the recurrence occurs. This is stored in UTC. Maximum range is January 1, 1753 to December 31, 9999 to an accuracy of 3.33 milliseconds. TODO: windowEnd, repeatForever, repeatInstances should be xsd:choice when implemented by XDB. Overrides the windowEnd date and specifies that this recurrence repeats forever. Client implementations cannot depend on date values repeating forever, like 23:59:59pm Dec 31, 9999 or 23:59 Aug 31, 4500. Overrides the windowEnd date and specifies that this recurrence repeats for the specified number of instances. repeatInstances and repeatForever are mutually exclusive, but repeatInstances will override repeatForever for errant schemas. Exceptions to a recurrence rule are added as an element list of dates. The service logic ignores the hh:mm:ss of the dateTime and merely blocks out the particular day. Any days can be added to an exception rule, including days where no occurrences of a recurrence rule would fall in the first place (ICAL EXDATE). This is stored in UTC. Repeat every [...] days. The periodicity of days over which repetition occurs, for example, repeat every 3 days. Repeat every [...] week(s) on {su,mo,tu,we,th,fr,sa}.
The presence of a weekday attribute means to repeat on this particular day. Any combination of the seven days is valid. The repeatWeekly recurrence occurs every period of weeks. If the attribute is not present, it defaults to 1 (every week).
Repeat on the [First, Second, Third, Fourth, Last] {su, mo, tu, we, th, fr, sa} of every [...] month(s).
Any combination of the {weekday} attributes are valid, including user-defined combinations for weekdays and weekend days. Specifies the month periodicity to recur on. If this attribute is not present, it defaults to 1 (every month). Repeats the occurrence every month on a particular day. The very first occurrence is created from the parent event's startTime and endTime, but the recurrence occurs as follows:
  • Repeat every month on [day] of [month].
  • Repeat every [monthFrequency] month(s) on [day] of [month].
    • Typically, the first occurrence is also an instance of the recurrence, but this need not be the case.     This optional attribute indicates the month periodicity. By default, it is 1, periodic every month. The start of the periodicity is determined from event startTime. Specifies the day of the month to recur on. Value is between 1-31. See forceExact for invalid day-month combinations. The proper recurrence pattern for repeating on the last day of the month is to use repeatMonthlyByDay. "Repeat on the [last] [day, weekday, weekend day] of ..." By default, an invalid day-month combination will cause .NET Calendar to search backwards to find a valid day-month combination. If forceExact is true, an invalid starting [month ,day] combination such as [6, 31] is ignored and will not be included as an instance of the recurrence. With forceExact, .NET Calendar follows ICAL behavior.
  • day=31 will only pick up months that have 31 days.
  • day=30 will pick up all months except February.
  • day=29 will pick up all months except February, except on leap years. February 29 is included on leap years.
    •      Repeat every year on a particular date. The very first occurrence is created from the parent event's startTime and endTime, but the recurrence occurs as follows:
  • Repeat yearly on [day] of [month].
  • Repeat every [yearFrequency] years on [day] of [month].
    • Typically, the first occurrence is also an instance of the recurrence, but this need not be the case.     This optional attribute indicates the year periodicity. By default, it is 1 (repeat every year). Specifies the month to recur on. Specifies the day of the month to recur on. Value is between 1-31. See forceExact for invalid day-month combinations. By default, an invalid day-month-year combination will cause .NET Calendar to search backwards to find a valid day for a particular month, year. If forceExact is true, an invalid starting [month ,day] combination such as [6, 31] is ignored and will not be included as an instance of the recurrence. With forceExact, .NET Calendar follows ICAL behavior.
  • day=31 will only pick up months that have 31 days.
  • day=30 will pick up all months except February.
  • day=29 will pick up all months except February, except on leap years. February 29 is included on leap years.
    •      Any additional repeat rules.     Contains a list of modified event properties for this particular orphan event. The properties that are not modified are inherited from the original event upon recurrence expansion (client-side). recurrenceId is always present. It is used to determine which instance of the original rule this modifiedException applies to.

    TODO: decide what other properties must belong.     This is the original start time (recurrenceId) of the occurrence that is being modified by this exception. ModifiedExceptions with recurrenceIds that do not match the recurrenceId of any occurrence are ignored. This is stored in UTC. modifiedException does not expose the id attribute. recurrenceId should be used to predicate instead, it functions as the id of modifiedException. This contains only the modifiable properties of the eventBody. Suppose the title changes. Suppose this particular instance has a revised description. Switch meeting location for this instance only. Switch the start time for this instance only. Switch the end time for this instance only. This particular instance is allDay. Suppose traffic is really bad for this instance. Suppose traffic is really bad for this instance. Priority is changed for this meeting. Suppose the original organizer is replaced by another organizer. The meeting organizer of a recurring meeting may wish to exclude a particular attendee for an instance of the meeting. This hs:idRefType (puid) indicates which attendee, (from the list of attendees at the event level) are not invited to this particular meeting instance. The meeting organizer of a recurring meeting may wish to exclude a particular attachment for an instance of the meeting. These are the properties of the reminder that may be modified. If there is no reminder subschema in the event body, exception reminders are ignored. Additional properties of the myCalendar/BaseEventType schema. Only certain event properties may exist here. This id is assigned by .NET Calendar. On a modify operation, sending in an id attempts to modify the modifiedException, and a blank id means that this modify operation adds a new modifiedException. On an insert operation, the id must be blank (it will be ignored if encountered due to the expense of this kind of validation).     The TransitionRule specifies the recurrence pattern for daylight savings time transitions.
  • Repeat on the [First, Second, Third, Fourth, Last] [day, weekday, weekend day, su ,mo, tu, we, th, fr, sa] of [Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec] [after [afterDay]].
  • Repeat on the [dayOfMonth] of [Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec]

    •      Used to specify a particular weekday of the month to transition on. If this attribute is present, then @day must also be present. Used to specify a day of the week for the transition to occur on. If this attribute is present, then @dayOfMonth must also be present. Used to specify a transition on a particular day of a month. Eg, Iraq (Baghdad) transitions on 5/1 and 9/30. afterDay is needed to support certain time-zone recurrence rules for countries that use the format of the first Friday after the 15th (i.e. New Zealand, which ends the first Sunday on or after 5 March).
  • Repeat on the [First, Second, Third, Fourth, Last] {su, mo, tu, we, th, fr, sa} of [Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec] every [yearFrequency] years.

    • Any combination of the {weekday} attributes are valid, including user-defined combinations denoting weekdays and weekend days.     This optional attribute indicates the year periodicity. By default, it is 1 (repeat every year).     Boolean flag that indicates whether the reminder is active for this event. In most cases, this will be true, but in the case of a recurring appointment, this flag may default to true with specific instances not to be reminded, or default to false, with specific instances to be reminded. Friendly name that this reminder is being sent to. Specifies the offset, in minutes, of how long before the event the user should be reminded. Recommended values are the following:
    Value Description
    5, 10, 20, 30, 45 5, 10, 20, 30, 45 minutes before the event
    60, 120, 180, 1, 2, 3 hours before the event
    startTime - startDay The day of the event (reminder sent at 12:00am)
    startTime - (startDay - (1440 * x)) "x" days before the event (reminder sent at 12:00am "x" days before)
    This optional element defines how interruptible this event is and it is used by notification routing software to make decisions about the relay and deferral of notifications that might occur while this meeting is active. The value contained in this element is a numeric value between 1 - 10. Low values represent a high cost of disruption, high values represent a low cost of disruption. Required by reminder engine. Determines the next time to trigger reminder.     Additional information about an event, found only in an event invitee's schema The intendedFreeBusy element is the event organizer's freeBusy information and is thus equal to event/freeBusyStatus. Invitees may overwrite event/freeBusyStatus with a new value, and intendedFreeBusy is intended to store the organizer's original freeBusyStatus. A delegate who responds on behalf of an invitee will have their information stored here. Additional attendee extra properties. The attendeeType contains the full information about an attendee. The display, email, puid, and the attendee's response. The meeting organizer uses this to define the kind of invitee {required, optional, resource}. The reply time on each attendee is set to the current time (Now) when the organizer sends a meeting invitation. When the attendee responds, they always update their responseTime. When the organizer receives responses, they will honor only those that have a higher responseTime than what s/he maintains in his/her own copy of the event for each attendee. While processing the response, the organizer will update their responseTime. This guarantees that the organizer honors only the most recent response from the attendee. This is stored in UTC.
    ICAL Equivalent: reply time on message.     The accept status indicates the valid types of responses that an attendee can reply with {accept, decline, tentative, counterpropose}. The absense of this field indicates that no response has been recorded (either the invitation has not been sent, or that a reply has not been received). If responseType=[counterPropose], then either the {startTime, endTime}, or location, or both can be present. This is the invitee's counterProposal for a new start time for the meeting. This is stored in UTC. If responseType=[counterPropose], then either the {startTime, endTime}, or location, or both can be present. This is the invitee's counterProposal for a new end time for the meeting. This is stored in UTC. If responseType=[counterPropose], then either the {startTime, endTime}, or location, or both can be present. This is the invitee's counterProposal for a location for the meeting. Optional message for invitees to include along with the response.     The type belongs to the following enumeration {free, tentative, busy, away}. Optional calendar type to return. Defaults to Gregorian. The starting time window of calendar objects to retrieve. This dateTime also contains the timeZone to retrieve the calendar information in. The ending time window to retrieve calendar objects. This dateTime also contains the timeZone to retrieve the calendar information in. It must be the same timeZone as startTime. This function returns an XML stream of calendar appointments / events between two dates. Recurrence rules are expanded to create individual calendar items. Holidays are represented as all-day events, and these are returned as well. getCalendarDays is a query-retrieval of data, but the behavior expands recurrence rules into individual (aliased) events, adds in holidays, and adds regular events and sorts the entire list based on start time. No merging of event blocks occurs. Any object which overlaps the method parameters {startTime, endTime} will be returned. For example, if an event crosses midnight and the startTime is 12am, that event will be returned. In case the startDate, endDate is one day, the events are sorted in the following order: holidays, all-day events, and regular events (based on startTime).
    The {startTime, endTime] time window can define any interval: 24hr period, week, month, or any other user-defined period.
    getCalendarDays returns the calendaring info of any puid that is specified for which the caller has sufficient privileges. The user's own puid must be specified to retrieve their own information.
    getCalendarDays may be used to retrieve multiple calendar data from other users using
  • <h:key instance="0" cluster="0" puid="xyz"/>
    • in the SOAP headers provided that puid "xyz" is provisioned on the .NET Calendar server, and provided that the user has been granted access in puid "xyz"'s rolelist.     Normally, the recurrence sub-schema, (minus modifiedException and minus deletedExceptionDate components) is returned with each instance of a recurring event, like "recurring-instance" and "recurring-exception". This allows clients to properly render the recurrence pattern without having to explicitly query the recurring-master. However, because it is heavy on bandwith, .NET Calendar includes the option to not return this data.     Response XML blob format, consists of the base event type minus recurrence. Depending on if <removeRecurrence> parameter is passed into getCalendarDays Distinguishes between a single instance of an event or an instance of a recurring event. The recurring instance is a modified exception if eventBody/recurrenceId is present: single, recurring-master, recurring-instance, recurring-exception. This function returns a stream of xml fragments defining the user's freeBusy information between two dates. Single events and recurring events within the time window are translated into blocks of free/busy time.
    getFreeBusyDays only returns the blocks and their associated type. There is no explicit method to return unmerged freeBusy info, that kind of behavior is fully contained within getCalendarDays.
    This method follows the precedence order:
    • Away(OOF), Busy, Tentative, Free
    • Overlapping blocks of the same freeOrBusyStatus kind are coalesced to form larger blocks.
    • Overlapping blocks of different freeOrBusyStatus are overlaid. The events with higher precedence overlay on top (not by starting time).

    For example:
  • Busy from 8 to 9
  • Tentative from 8:30 to 10
  • OOF from 9:30 to 11
  • Free from 10:30 to 12

    • Merged as:
  • Busy from 8 to 9
  • Tentative from 9 to 9:30
  • OOF from 9:30 to 11
  • Free from 11 to 12

    • Multiple users' freeBusy information are retrieved by specifying a puid for each user in question. The caller of this function must also specify their own puid, no implicit assumptions are made.
    The calling method takes a startDate and an endDate to define the duration over which freebusy information is returned. A third parameter determines if free blocks are explicitly returned. Free blocks are intervals where no calendar object exists.
    getFreeBusyDays may be used to retrieve multiple calendar data from other users using
  • <h:key instance="0" cluster="0" puid="xyz"/>
    • in the SOAP headers provided that puid "xyz" is provisioned on the .NET Calendar server, and provided that the user has been granted access in puid "xyz"'s rolelist.     This boolean causes .NET Calendar to explicitly return free time as freeBusy blocks. By default, free blocks are not returned. This boolean causes .NET Calendar not to coalesce/merge freeBusy information. By default, freeBusy information is merged.     Response XML blob format, consists of freebusy xml fragments. The purpose of this method is for a meeting organizer to invite and uninvite (cancel) attendees to this event. sendMeeting also sends updated invitations to existing invitees. Inviting a user to a single instance of a recurring event will cause only that instance to be sent. However, future updates to that event will overwrite the existing instance, including the case where an update is the full recurring event.
    Meeting requests will be sent out as iCal attachments from an SMTP server unknown at this point in the design.
    When inviting or uninviting, .NET Calendar searches for these existing attendees by puid first, and then by email address such that the puid receives precedence in the search predication. .NET Calendar will not allow multiple meeting requests/cancellations to the same puid or email address within the scope of the same invite or uninvite block. However, an organizer may uninvite an attendee and then reinvite again (non-standard behavior).     This is the puid of the event which to send meeting invitations or cancellations to. This event must already exist within the .NET Calendar service. Additional server constraints are implemented which verify that potential updates to the attendee tables occur for this event only. This is a required field. When this attribute is set to "true", <lastUpdateTime> is updated when invitations are sent to the attendees. If "false", <lastUpdateTime> remains untouched. The optional recurrenceId allows the meeting organizer to send invitations for only a particular instance of a recurring event. If the event is not a recurring event, or if recurrenceId does not correspond to a valid instance/exception, sendMeetingRequest will fail with an error. Specifies to .NET Calendar to continue performing the sendMeetingRequest even on a failure. Points of failure:
  • <uninvite> may delete attendees, and the HSDL delete may encounter errors
  • <updateRequest> may encounter HSDL errors.
  • The optional final delete of the event may encounter errors.
    •      This event will be deleted upon completion of this sendMeetingRequest. This behavior is intended for deleting a meeting and sending cancellations. If recurrenceId is present (and valid), only this particular recurring instance or exception is deleted, in which case a new <deletedExceptionDate> is added to the recurrence rule. This attribute will give the option to either choose to send cancellations to "all" attendees in the event's attendee table, or send to "none" of them. A third value of "default" would give the default behavior of sending cancellations to all attendees who are replaced in the <replaceRequest> block. When this attribute is set, .NET Calendar will ignore anything within the <uninvite> node. Contains a list of people to uninvite. Uninvited attendees must already exist in the organizer's attendee table, or else these users are ignored. This replace request can only affect the meeting invitation in question, and is thus constrained to be only @select="/m:myCalendar/m:event[@id=@eventId]/...". It will not be allowed to replace-on-null so that event creation cannot be a side-effect. This attribute will give the option to either choose to send invitations to "all" attendees in the event's attendee table, or send to "none" of them. A third value of "default" would give the default behavior of sending invitations to only the new attendees in the <replaceRequest> block. When this attribute is set, .NET Calendar will ignore anything within the <invite> node. Contains information about this attendee to be invited. An invited attendee must already exist in the organizer's attendee table. This attendee may originally be there prior to the sendMeetingRequest method, or be the result of the update operation to this meeting.
    To change the attendee's inviteType, the update operation should be used.
    When invitations are sent, the attendee's <responseTime> is set to the current time (now) as a side-effect.     The purpose of this method is for a meeting invitee to respond to an invitation. Invitees may accept, decline, accept tentatively, or counterpropose in some means. Currently, we allow the counterproposing of time and location, but we may consider future additions. The eventId for the meeting. The invitee. This function is used to update the status of a reminder once the user has received the notification. We may expose this as an HTTP API so that non-.NET My Services clients have a means to dismiss, snooze, or be reminded again at a different time. (WIP) Response XML blob format, contains the myAlerts hs:idType for the resultant create/modify operation. This function delegates a call to .NET Alerts to delete an existing meeting reminder. .NET Calendar acts as a client to the Notification Service. In the underlying implementation, setReminderRequest simply issues a .NET My Services delete message. This function provides an efficient, lightweight means to query a date range to indicate days that have 1 or more appointments (1) and days without appointments (0). Outlook and OWA use this for their datepicker functionality.

    The date range takes timeZone-specific start and end times, using just the year, month, and day. The time zone can be a simple bias, since this is merely a request for data. startTime and endTime are required to have the same time-zone bias. In effect, the method "overlays" the incoming time zone onto the user's calendar to define the dayblocks for which the QuickView returns data.     Optionally specifies a timezone to retrieve the quickView in. If this or biasOffset are both missing, TZ_UTC is assumed. Optionally specifies a numeric integer offset timezone bias to retrieve the quickView in. tzid takes precedence over biasOffset (pending xsd:choice).     The return value of getQuickView is a list of calendar days grouped into months. Specifies the month block for the grouping of calendar days. Specifies whether this day is free (0) or has at least one event on it or overlapping (1). Specifies day in this month. Contains the full (extended) structural definition of the timezone. Specifies the current bias, in minutes, for local time translation. The bias is the difference, in minutes, between Coordinated Universal Time (UTC) and local time. All translations between UTC and local time are based on the following formula: 
    UTC = local time + bias
    This property is read only, except for id is USER_DEFINED.     [Optional] Specifies an additional bias value to be added to standardBias used during local time translations that occur during daylight saving time. In most time zones, the value of this member is minus 60. This fragment describes the standard date to daylight date transition using the RepeatYearlyByDay recurrence rule. Specifies a date and local time when the transition from standard time to daylight time occurs. Specifies the local time (e.g. 2am) to transition from standard to daylight. This fragment describes the daylight date to standard date transition using the RepeatYearlyByDay recurrence rule. Specifies a date and local time when the transition from daylight saving time to standard time occurs. Specifies the local time (e.g. 2am) to transition from daylight to standard.     The scheme the message contents were encoded in. Examples of this are '7bit', '8bit' and 'base64'. This element contains information about an individual attachment in a mail message. This element contains the content type of the attachment. This element contains the encoding of the attachment. This information is necessary for decoding the attachment. This element contains the size of the attachment in bytes. This element contains the MIME body of the attachment. Contains the attachment body. The system define unique id of an attachment on a given message. Specifies which week in a month [first, second, third, fourth, last]. This element's attributes contain whether a given day is or is not considered by the user as part of the work week. If this element has no attributes, we will assume that the user has a Monday to Friday work week. Restrict to 1-13. Some calendars have 13 months. This is a .NET My Services specific integer enumeration defining the exact supported time zone. If id is USER_DEFINED = -1, then this time zone's schema defines the entire time zone rule, including any applicable daylight bias. .NET My Services clients are expected to understand the base set of enumerations. .NET Calendar as a service will provide the enumerations and the additional metadata necessary to fully describe the time zone, including daylight calculations. .NET Calendar will not provide localizable names for the enumerations. This field identifies an enumeration which determines the kind of calendar event this is. .NET My Services v1 will only support HSCAL_GREGORIAN_US.
    http://msdn.microsoft.com/library/psdk/winbase/nls_9bg8.htm plus several others:

    Value Enumeration Constant Description
    -1 HSCAL_ALL_CALENDARS Unknown Calendar; system default (HSCAL_GREGORIAN_US)
    1 HSCAL_GREGORIAN Gregorian (localized) calendar
    2 HSCAL_GREGORIAN_US Gregorian (U.S.) calendar
    3 HSCAL_JAPAN Japanese Emperor Era calendar
    4 HSCAL_TAIWAN Taiwan Era calendar
    5 HSCAL_KOREA Korean Tangun Era calendar
    6 HSCAL_HIJRI Hijri (Arabic Lunar) calendar
    7 HSCAL_THAI Thai calendar
    8 HSCAL_HEBREW Hebrew (Lunar) calendar
    9 HSCAL_GREGORIAN_ME_FRENCH Gregorian Middle East French calendar
    10 HSCAL_GREGORIAN_ARABIC Gregorian Arabic calendar
    11 HSCAL_GREGORIAN_XLIT_ENGLISH Gregorian Transliterated English calendar
    12 HSCAL_GREGORIAN_XLIT_FRENCH Gregorian Transliterated French calendar
    13 HSCAL_KOREA_LUNAR Default Korea Lunar calendar
    14 HSCAL_JAPAN_LUNAR Default Japanese Lunar calendar
    15 HSCAL_CHINESE_LUNAR Chinese Lunar calendar
    16 HSCAL_SAKA Indian Saka calendar
    17 HSCAL_LUNAR_ETO_CHN Chinese Zodiac calendar
    18 HSCAL_LUNAR_ETO_KOR Korean Zodiac calendar
    19 HSCAL_LUNAR_ROKUYOU Japanese Lucky days calendar
    This element contains attachment metadata, name, content-type and id's, and may also contain the attachmentBody. A user may optionally define a reminder for this appointment. Reminders for recurring appointments will be sent periodically before the appointment as per the rules defined in the reminder subschema. A non-recurring event may have the following:
  • Define no reminders
  • Define a reminder with <set> = "true"
  • Define a reminder with <set> = "false" (useless)

    • A recurring meeting may have any of the following:
  • Define no reminders
  • Define a recurring reminder with all instances receiving reminders
  • To define no reminders by default, but to define reminders for particular meeting instances in the exception body: Create a reminder <set> = "false", and turn it on and/or modify it for particular instances.
  • To define a recurring reminder, but turn it off for particular meeting instances: Create a reminder <set> = "true", and turn it off for particular instances.

    • If the event's reminder subschema is non-existent, yet the exception body has a reminder blob, then the exception reminder is ignored. The alternative is to require 1..1.     Required for Hijri calendar support. @advanceHijriValue ranges from {-3,-2,-1,1,2,3} and is added to the current date, but the day of the week stays the same. For example, if today is the 24th and @advanceHijriValue is set to be +2, then the user sees the date as being the 26th. Typically @advanceHijriValue is +/-1, and this suffices in most cases. Theoretically it can be any number, but the worst case scenario is +/-3.     Optionally specifies whether or not to delete this attendee from the organizer's attendee table. If the attendee is not deleted, .NET Calendar will not know the status of this attendee because the status {not-sent, sent, cancelled} is not stored per-attendee.