Revision Summary Date Revision History Revision Comments 12/3/2008 1.0.0 Major Initial Release. 4/10/2009 2.0.0 Updated technical content and applicable product releases. 7/15/2009 3.0.0 Major Revised and edited for technical content. 11/4/2009 4.0.0 Major Updated and revised the technical content. 2/10/2010 5.0.0 Major Updated and revised the technical content. 5/5/2010 6.0.0 Major Updated and revised the technical content. 8/4/2010 7.0 Major Significantly changed the technical content. 11/3/2010 8.0 Major Significantly changed the technical content. 3/18/2011 8.1 Minor Clarified the meaning of the technical content. 8/5/2011 9.0 Major Significantly changed the technical content. 10/7/2011 9.1 Minor Clarified the meaning of
technical content. 4/30/2014 13.0 Major Significantly changed the technical content. 7/31/2014 14.0 Significantly changed the technical content. 10/30/2014 14.1 Minor Clarified the meaning of the technical content. 5/26/2015 15.0 Significantly changed the technical content. 6/30/2015 15.0 None No changes to the meaning, language, or formatting of the technical content. 9/14/2015 16.0 Significantly changed the technical content. 6/9/2016 17.0 Major Significantly changed the technical content. 2/28/2017 18.0 Major Significantly changed the technical content. 4/18/2017 18.0 None No changes to the meaning, language, or formatting of the
specified time. OrganizerName (section 2.2.2.36) The name of the user who created the calendar item. OrganizerEmail (section 2.2.2.35) The e-mail address of the user who created the calendar item. DtStamp (section 2.2.2.18) The date and time at which the calendar item was created or modified, or the date and time at which the exception item was created or modified. EndTime (section 2.2.2.20) The end time of the calendar item or exception item. Location (section 2.2.2.27) The place where the event specified by the calendar item or exception item occurs. Reminder (section 2.2.2.38) The number of minutes before the calendar item's start time to display a notice. Sensitivity (section 2.2.2.41) The recommended privacy policy for this calendar item or exception item. Subject (section 2.2.2.43) The subject of the calendar
12.0 Yes 12.1 Yes 14.0 Yes 14.1 Yes 16.0 Yes 16.1 Yes Name The Name element is a required child element of the Attendee element (section ) that specifies the name of an attendee. It is defined as an element in the Calendar namespace. The value of this element is a string data type, as specified in section 2.7. A command request or response has only one Name child element per Attendee element. Protocol Versions The following table specifies the protocol versions that support this element. The client indicates the protocol version being used by setting either the MS-ASProtocolVersion header, as specified in section 2.2.1.1.2.6, or the Protocol version field, as specified in [MS-ASHTTP] section 2.2.1.1.1.1, in the request. Protocol version Element support 2.5 Yes 12.0 Yes 12.1 Yes 14.0 Yes 14.1 Yes 16.0 Yes 16.1 Yes NativeBodyType The airsyncbase:NativeBodyType element is an optional element that specifies how the body text of the calendar item is stored on the server. It is defined as an element in the AirSyncBase namespace and used in ActiveSync command requests and responses as specified in section . The of this element is an unsignedByte data type, as specified in section 2.8. For details about the airsyncbase:NativeBodyType element, see section 2.2.2.32.
14.1 Yes 16.0 Yes 16.1 Yes Sensitivity As a top-level element of the Calendar class, the Sensitivity element is an optional child element that specifies the recommended privacy policy for the calendar item. It is used in ActiveSync command requests and responses as specified in section . As an optional child element of the Exception element (section ), the Sensitivity element specifies the recommended privacy policy for the calendar item exception. A command request or response has a maximum of one Sensitivity child element per Exception element. If the Sensitivity element is not specified as a child element of an Exception element, the Sensitivity element for the exception is assumed to have the same value as the value of the top-level Sensitivity element. The Sensitivity element is defined as an element in the Calendar namespace. The value of this element is an unsignedByte data type, as specified in section 2.8. The value of the Sensitivity element MUST be one of the values listed in the following table. Value Meaning 0 Normal 1 Personal 2 Private 3 Confidential Protocol Versions The following table specifies the protocol versions that support this element. The client indicates the protocol version being used by setting either the MS-ASProtocolVersion header, as specified in section 2.2.1.1.2.6, or the Protocol version field, as specified in [MS-ASHTTP] section 2.2.1.1.1.1, in the request. Protocol version Element support 2.5 Yes 12.0 Yes 12.1 Yes 14.0 Yes 14.1 Yes 16.0 Yes
Appendix B: Product Behavior The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs. Microsoft Exchange Server 2007 Service Pack 1 (SP1) Microsoft Exchange Server 2010 Microsoft Exchange Server 2013 Microsoft Exchange Server 2016 Windows Communication Apps Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition. Unless otherwise specified, any statement of optional behavior in this specification that is prescribed the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription. <1> Section 2.2.2.10: Microsoft Exchange Server 2013 Service Pack 1 (SP1) returns a value of 0 when a client specifies a value of 1 (Gregorian). <2> Section 2.2.2.25: If Interval is set to 0 in command request, Exchange 2007 SP1 and Exchange 2010 return Status value 6; Microsoft Exchange Server 2010 Service Pack 1 (SP1), Exchange 2013, and Exchange 2016 return Interval value 1. <3> Section 2.2.2.37.1: In Exchange 2007 SP1, the DayOfWeek element is not supported when the Type element is set to zero (0). <4> Section 2.2.2.46: If the UID element is not included in the command request, Exchange 2007 SP1 creates a and includes it in the command response. <5> Section 3.1.5.3.1: Exchange 2007 SP1 does not support deleting elements of a recurring calendar item in an Exception element.