XML schema changes

Overview

The XML API has evolved over several releases and expanded and changed with the introduction of various network management and network element functions.

Deprecated properties and methods

Some deprecated objects of the XML API are subject to change or to be replaced, are no longer in use, or were never supported. Although deprecated objects remain in the software, Nokia recommends that OSS developers not use them because the deprecated object may not be included in a future release.

Schema changes for releases

The differences between releases of the XML API, including additions, deletions, and changes, are listed at a high level. Changes in the schema can be reviewed by examining details of the interface documentation in each release. Differences can be compared to the methods and objects used in OSS applications to determine whether application updates are required.

See To view release-specific XML schema changes for information about viewing schema changes between releases.

Note: If you are planning to use an OSS client that was tested in a previous release of the NFM-P, you must review your usage with the list of schema changes before you start development, in order to identify changes that must be made to the packages, classes, types, methods, or properties that are used by the OSS client.

Schema changes for network element versions

Various packages, classes, and properties may apply to a subset of network element products and versions. Values and applicability of properties may change after a network element upgrade or downgrade. OSS applications should be designed to process XML API such that extra or missing properties do not cause unexpected OSS behavior. For example, OSS applications should not expect specific assigned values for properties that are not applicable to a particular product version.

It is recommended that product-specific differences be compared to the methods and objects used in OSS applications to determine whether application updates are required.

See Supported network elements for information about products and releases that support a class. Product-specific details may also apply to various properties.

Note: If you are planning to use an OSS client that was tested in a previous release of the NFM-P or are planning to use different network element product versions, you must review your usage with the list of schema changes before you start development in order to identify changes that must be made to the packages, classes, types, methods, or properties that are used by the OSS client.