9 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.4.1 t:AbchPersonItemType Complex Type

Changed "should not" to "MUST NOT".

N

Content updated for template compliance.

2.2.4.1 t:AbchPersonItemType Complex Type

Updated AbchPersonItemType to include PersonIdGuid element.

N

Content update.

2.2.4.3 t:ContactItemType Complex Type

Updated schema for t:ContactItemType type.

N

Content update.

2.2.4.3 t:ContactItemType Complex Type

Updated ContactItemType to include DisplayNamePrefix, YomiGivenName and YomiSurname.

N

Content update.

2.2.4.3 t:ContactItemType Complex Type

Updated the description of the EmailAddresses child element to remove the response code ErrorInvalidContactEmailAddress.

N

Content update.

2.2.4.3 t:ContactItemType Complex Type

Updated ContactItemType to include the PersonalNotes element.

N

Content update.

3.1.4 Message Processing Events and Sequencing Rules

Updated the table to include GetUserPhoto and SetUserPhoto operations.

N

New content added.

3.1.4.1.1.1 t:AbchEmailAddressDictionaryEntryType Complex Type

Updated description for IsMessengerEnabled.

N

Content update.

3.1.4.1.1.3 t:AbchPersonContactHandle Complex Type

Updated the description for AccountName.

N

Content update.

3.1.4.1.1.10 t:EmailAddressDictionaryEntryType Complex Type

Updated the description of the Key attribute to remove the response code ErrorInvalidContactEmailIndex.

N

Content update.

3.1.4.7 GetUserPhoto

Updated WSDL binding for GetUserPhoto.

N

Content update.

3.1.4.7.3.2 GetUserPhotoResponseMessageType

Added new element ContentType.

Y

Content update.

3.1.4.7.3.2 GetUserPhotoResponseMessageType

Added behavior note for new element ContentType.

Y

New product behavior note added.

3.1.4.7.3.2 GetUserPhotoResponseMessageType

Updated the description for HasChanged.

N

Content update.

3.1.4.8.3.2 SetUserPhotoResponseMessageType

Updated schema for SetUserPhotoResponseMessageType.

N

Content update.

6 Appendix A: Full WSDL

Updated WSDL binding for GetUserPhoto.

N

Content update.

7.1 Messages Schema

Updated Messages schema to include elements and types.

N

Content update.

7.1 Messages Schema

Updated schema for GetUserPhotoResponseMessageType to include ContentType element.

N

Content update.

7.1 Messages Schema

Updated schema for SetUserPhotoResponseMessageType.

N

Content update.

7.2 Types Schema

Updated ContactItemType to include DisplayNamePrefix, YomiGivenName and YomiSurname.

N

Content update.

7.2 Types Schema

Updated AbchPersonItemType to include PersonIdGuid element.

N

Content update.

Show: