This schema defines the elements and attributes which are added to managed object definitions and property definitions in the "preprocessor" profile. Managed object definitions are annotated by listing the parent managed objects which the definition inherits from. This can be used to enforce a simple managed object naming scheme where sub-definitions use the uppermost definition's name as a suffix. For example, "ldap-connection-handler" is derived from "connection-handler", and therefore has the suffix "-connection-handler". Applications can take advantage of this naming schema to shorten sub-definition names where appropriate. For example, a CLI which supports creation of connection handlers, can use remove the suffix from "ldap-connection-handler" in order to derive a "type", in this case "ldap". Each property definition is annotated as follows: firstly a "managed-object" element is added defining the name and package of the managed object which defines the property (i.e. this will be a parent managed object for inherited properties). Secondly, if the property is referenced from a Property.xml file, an additional "package" element is appended identifying the referenced package. Specifies the name and package of the managed object definition which defines a property definition. The name of the managed object. The name of the package containing the managed object. This optional element specifies, for referenced property definitions (i.e. those defined in a Package.xml file), the name of the package defining the definition. The name of the package. Specifies the name and package of a parent managed object definition. Elements are order such that the immediate parent is the first node in document order and the last element represents the uppermost definition in the inheritance hierarchy. The name of the parent managed object. The name of the package containing the parent managed object.