8 Change Tracking

This section identifies changes that were made to this document since the last release. Changes are classified as New, Major, Minor, Editorial, or No change.

The revision class New means that a new document is being released.

The revision class Major means that the technical content in the document was significantly revised. Major changes affect protocol interoperability or implementation. Examples of major changes are:

  • A document revision that incorporates changes to interoperability requirements or functionality.

  • The removal of a document from the documentation set.

The revision class Minor means that the meaning of the technical content was clarified. Minor changes do not affect protocol interoperability or implementation. Examples of minor changes are updates to clarify ambiguity at the sentence, paragraph, or table level.

The revision class Editorial means that the formatting in the technical content was changed. Editorial changes apply to grammatical, formatting, and style issues.

The revision class No change means that no new technical changes were introduced. Minor editorial and formatting changes may have been made, but the technical content of the document is identical to the last released version.

Major and minor changes can be described further using the following change types:

  • New content added.

  • Content updated.

  • Content removed.

  • New product behavior note added.

  • Product behavior note updated.

  • Product behavior note removed.

  • New protocol syntax added.

  • Protocol syntax updated.

  • Protocol syntax removed.

  • New content added due to protocol revision.

  • Content updated due to protocol revision.

  • Content removed due to protocol revision.

  • New protocol syntax added due to protocol revision.

  • Protocol syntax updated due to protocol revision.

  • Protocol syntax removed due to protocol revision.

  • Obsolete document removed.

Editorial changes are always classified with the change type Editorially updated.

Some important terms used in the change type descriptions are defined as follows:

  • Protocol syntax refers to data elements (such as packets, structures, enumerations, and methods) as well as interfaces.

  • Protocol revision refers to changes made to a protocol that affect the bits that are sent over the wire.

The changes made to this document are listed in the following table. For more information, please contact dochelp@microsoft.com.

Section

Tracking number (if applicable) and description

Major change (Y or N)

Change type

2.2.2.1 AllDayEvent

Removed description of server behavior when this element is present under certain conditions with older versions of the protocol.

N

Content removed.

2.2.2.1 AllDayEvent

Added description of server behavior when this element is present under certain conditions with protocol version 16.0.

Y

New content added.

2.2.2.5 AttendeeStatus

Added details about client command request requirements when using this element with protocol version 16.0.

N

Content update.

2.2.2.9 BusyStatus

Added an entry for value 4 to the table listing possible values for this element, and added a sentence to indicate that value 4 is only supported in protocol version 16.0.

N

Content update.

2.2.2.13 ClientUid

Added a new section for this element.

Y

New content added.

2.2.2.18 DtStamp

Clarified that this element also specifies the date and time at which the exception item was created or modified.

N

Content update.

2.2.2.18 DtStamp

Added a sentence to indicate that this element is only appropriate for command requests with protocol version 16.0.

N

Content update.

2.2.2.20 EndTime

Added a sentence to indicate behavior of this element with protocol version 16.0.

N

Content update.

2.2.2.21 Exception

Added airsyncbase:Location, calendar:Location, airsyncbase:Attachments, and airsyncbase:InstanceId to the list of possible child elements for this element.

N

Content update.

2.2.2.21 Exception

Updated details about the behavior and support for this element with different protocol versions.

N

New content added.

2.2.2.22 Exceptions

Added a sentence to indicate behavior of this element with protocol version 16.0.

N

Content update.

2.2.2.23 ExceptionStartTime

Updated details about the behavior and support for this element with different protocol versions.

N

Content update.

2.2.2.25 Interval

Updated product version for returning status 6 if Interval is set to 0.

N

Product behavior note updated.

2.2.2.25 Interval

Updated supported products in the product behavior note for Interval.

N

Product behavior note updated.

2.2.2.27 Location

Added a sentence to indicate behavior of this element with protocol version 16.0.

N

Content update.

2.2.2.35 OrganizerEmail

Added a sentence to indicate behavior of this element with protocol version 16.0.

N

Content update.

2.2.2.36 OrganizerName

Added a sentence to indicate behavior of this element with protocol version 16.0.

N

Content update.

2.2.2.37 Recurrence

Specified that in protocol version 16.0, the Type element is optional in client requests and the client can change a recurring event to a single event by including an empty Recurrence element.

N

Content update.

2.2.2.37.1 Recurrence Patterns

Updated product version for not supporting DayOfWeek element.

N

Product behavior note updated.

2.2.2.38 Reminder

Specified that in protocol version 16.0, the client can send a request with an empty Reminder element to create an item without a reminder.

N

Content update.

2.2.2.42 StartTime

Added a sentence to indicate behavior of this element with protocol version 16.0.

N

Content update.

2.2.2.46 UID

Clarified definition of this element.

N

Content update.

2.2.2.46 UID

Updated details about the behavior and support for this element with different protocol versions.

N

New content added.

3.1.4.4 Creating a New Meeting Request

Updated details about the behavior and support for this event with different protocol versions.

N

Content update.

3.1.5.3.1 Indicating Deleted Elements in Exceptions

Updated product version for not supporting deleting elements of a recurring calendar item in an Exception element.

N

Product behavior note updated.

3.1.5.3.2 Omitting Ghosted Properties from a Sync Change Request

Updated details about the behavior and support for this event with different protocol versions.

N

Content update.

4.3 Setting Attendee Status from the Server

Changed NonTruncatedSize element to EstimatedDataSize element in example.

N

Content update.

6 Appendix A: Full XML Schema

Updated schema to include airsyncbase:Location, airsyncbase:Attachments, and airsyncbase:InstanceId as child elements of Exception.

N

Content update.

7 Appendix B: Product Behavior

Updated list of applicable products.

Y

Content update.

Show: