How version numbers are assigned

Interface version numbers are assigned each time the particular interface is updated.

A version number for an interface consists of major and minor versions:

Major version is used to track changes to the service that are not backward-compatible.
Minor version is used to track backward-compatible changes to the service.

For example, if a version number for a Web service is 3.0, its major version is 3, and its minor version is 0.

All interface changes result in a version number increase:

Major version numbers are increased only when changes that are not backward-compatible are introduced in the interface. These changes include removal of operations, elements, or attributes; addition of new required attributes to existing operations; or cases when services are split or combined, or operations are moved from one service to another.
Changes that are not backward-compatible are introduced with the following deprecation policy. When any of the interface's artifacts change, new artifacts are added, but old ones are not removed in the new version. Instead, old artifacts are deprecated and retained for a period of time.
The Oracle Endeca Server Migration Guide lists the following:
- Which service versions are shipped with the particular Oracle Endeca Server release.
- Which operations and/or services have been deprecated.
- The upgrade impact for each of the changes.
Minor version numbers are increased when backward-compatible changes are introduced. Backward-compatible changes include new operations that may be added, or new operations with new types.

Interface version numbers for each of the Web service interfaces may differ and depend on the changes to that interface.

Interface version numbers do not correspond to the version number of the product that is being released.

After upgrading to a new version of the product, it is recommended to check the version numbers of each of the interfaces and ensure that your clients also have the corresponding versions.