13-116
Cisco CRS-1 Series Carrier Routing System XML API Guide
OL-4596-01
Chapter 13 Cisco CRS-1 Series XML Schemas
Common XML Schemas
The XML schema file containing all configuration operations is also among the BASE package common
schemas, and is named cfgmgr_operations.xsd.
Component XML Schemas
In addition to the common XML schemas, component XML schemas (such as native data) are provided
and contain the data model for each feature. There is typically one component XML schema for each
major type of data supported by the component—configuration, operational, action, administration
operational, and administration action data—plus any complex data type definitions in the operational
space.
Note Sometimes common schema files exist for a component that contain resources used by the component’s
other schema files (for example, the data types to be used by both configuration data and operational
data).
Schema File Organization
For the first release of the Cisco CRS-1 Series system, there is no hard link from the high-level XML
request schemas (namespace_types.xsd) and the component schemas. Instead, links appear in the
component schemas in the form of include elements that specify the file in which the parent element
exists. The name of the component .xsd file also indicates where in the hierarchy the file’s contents
reside. If the file ends with _cfg.xsd, it appears as a child of “Configuration”; if it ends with _if_cfg.xsd,
it appears as a child of “InterfaceConfiguration”, and so on. In addition, the comment header in each .xsd
file names the parent object of each top level object in the schema.
Schema File Upgrades
If a new version of a schema file becomes available (or has to be uploaded to the router as part of an
upgrade), the new version of the file can replace the old version of the file in a straight swap. All other
files will be unaffected. Therefore, if a component is replaced, only the .xsd files pertaining to that
component will need replacing.