Export (0) Print
Expand All

7 Change Tracking

Office

This section identifies changes that were made to the [MS-CONFPRO] protocol document between the February 2014 and April 2014 releases. 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.1
Transport

Updated the protocol transport description.

N

Content updated.

2.2.2.1
addConference Request

Changed "CAN" into "can".

N

Content updated.

2.2.2.5
getConferences Request

Changed "static flag" to "static attribute".

N

Content updated.

2.2.3.1
addConference Response

Changed "mcuType" into "MCU-Type" in the description of "mcuTypeNotAvailable".

N

Content updated.

2.2.3.5
getConferences Response

Removed the sentence". This reason MUST be used when a failure is not caused by one of the other reasons outlined here" from the description for "otherFailure".

N

Content removed.

2.2.3.6
getEncryptionKey Response

Removed the sentence". This reason MUST be used when a failure is not caused by one of the other reasons outlined here" from the description for "otherFailure".

N

Content removed.

2.2.3.7
getAvailableMcuTypes Response

Removed the sentence". This reason MUST be used when a failure is not caused by one of the other reasons outlined here" from the description for "otherFailure".

N

Content removed.

2.2.3.7
getAvailableMcuTypes Response

Changed "mcuTypes" into "mcu-types".

N

Content updated.

2.2.3.8
getConferencingCapabilities Response

Removed the sentence". This reason MUST be used when a failure is not caused by one of the other reasons outlined here" from the description for "otherFailure".

N

Content removed.

2.2.3.8
getConferencingCapabilities Response

Changed "entry-exit global announcements feature" into "entry-exit announcement feature" and added explanation for "entry-exit announcement feature".

N

Content updated.

2.2.3.8
getConferencingCapabilities Response

Updated figure 15: getConferencingCapabilities element hierarchy.

N

Content updated.

3.1.4.1
Create a Conference

Changed "static flag" to "static attribute".

N

Content updated.

3.1.4.4
Query for a List of Conferences

Changed "static flag" to "static attribute".

N

Content updated.

3.1.4.5
Query for the Details of a Conference

Added link "section 2.2.2.4" for "Create an appropriate getConference request".

N

Content updated.

3.1.4.7
Obtain a List of MCU-Types

Added link "section 2.2.3.7" for "appropriate MCU-Types".

N

Content updated.

3.1.4.8
Obtain Focus Factory Capabilities

Added link "section 2.2.3.8" for "appropriate MCU-Types".

N

Content updated.

4.2
Modify a Conference

Removed notes for modifyConference request from a client application to the Focus Factory.

N

Product behavior note removed.

4.4
Query for a List of Conferences

Removed notes for getConferences request to get the static meeting.

N

Product behavior note removed.

4.7
Obtaining a List of MCU-Types

Updated the getAvailableMcuTypes response example with changing 'mcu-type' to 'mcuType'.

N

Content updated.

4.8
Obtaining Focus Factory Capabilities

Removed notes for obtaining focus factory capabilities.

N

Product behavior note removed.

4.9
Delegation Request

Removed note for delegation request.

N

Product behavior note removed.

Show:
© 2014 Microsoft