ng attributes of the entities are visible across the interface: Name: The entity instance on the CCV can be uniquely identified using the "name" attribute. Once the naming OS sets the attribute, its value does not vary for the life of the entity. Discovered name: In the case where the OS that publishes the entity on the CCV is not the naming OS, the name of the entity is known as the discov- ered name. This attribute may be left empty if the naming OS publishes the entity first on the CCV. The value of the name attribute and the discovered name attribute of the entity can be set to the same value or different value. Naming OS: The os that is responsible for setting the "name" of the entity also sets up the naming OS attribute and this attribute represents an identi- fier for the steward of the entity. There is a unique naming OS for each entity published on CCV. Alias name list: The attribute is a list of name-value pairs for the entity. The name refers to the type of alias and the value component holds the alias itself. User label: It is an optional attribute that represents the "user friendly" name for the entity. Owner: It is an optional attribute that is used to identify the owner of the entity. Vendor extensions: This attribute is used by vendors to further qualify and extend the entity characteristics. MTOSI provides steps to discover new network entities such as managed elements and topological links in cases where two different suppliers are providing the net- work inventory management OS and the network discovery/activation OS. Another interesting feature in MTOSI is backward and forward compatibility. Backward compatibility: This feature allows a new version of a client os to be rolled out in a way that does not break existing server OSs. An older ver- sion of a message can be sent to a client os (by server OS) that understands the new version and still have the message successfully processed. Forward compatibility: This feature allows a new version of a server os to be rolled out in a way that does not