A collector for old files. A mapping of old complex types to new complex types. This excludes simplistic complex types. A collector for old renamed types. A mapping of old simplistic types to new simplistic types. A collector for old renamed enum 'simple' types. A mapping of old enum values to new enum values. A container for information about an old file containing types. The name of the old file containing types. Information about a type in the old file. This is primarily intended to support a type that was split into two types (e.g., element groups) A container for information about an old type. The name of the old type. The status of the type: DELETE = The type was deleted. The file and type for the 'new type' will refer to the old file and type in order to define mapping of the elements. Information about a type related to the old type. The old type and/or file may have been renamed or it may have been split into multiple types in multiple files. Information about a new type related to an old type. The name of the file containing the type. The name of the type in the file. This may or may not match the name of the old type. A mapping from and old element name to a new element name. A mapping from and old attribute name to a new attribute name. Defines a mapping between element names. The old element name. A new element name in the type. If the new name is not in the type then it may be referenced in movedTo. The compatibility of the substitution: RENAME = Forward and backward mapping. FORWARD = Forward compatible . BACKWARD = Backward compatible. FWD-MOVED = Forward mapping move to one spot. Element movedTo should be populated. BWD-MOVED = Backward mapping move to one spot. Element movedTo should be populated. FWD/BWD-MOVED = Moved to one spot with Forward and backward mapping. Element movedTo should be populated. FWD/BWD-MULTI-MOVE = Moved to multiple spots with Forward and backward mapping. FWD/BWD-MAPPING = A simplistic mapping that supports both forward and backward. MAPPING = Complicated mapping. For any variation of a status of 'MOVED', the dot notation from a starting type to the new element. For example, 'cs_xxx.yyy' where yyy is the new element or attribute. A comment related to the status. Defines a mapping between attribute names. The old attribute name. A new attribute name in the type. If the new name is not in the type then it may be referenced in movedTo. The compatibility of the substitution: RENAME = Forward and backward mapping. FORWARD = Forward compatible . BACKWARD = Backward compatible. FWD-MOVED = Forward mapping move to one spot. Element movedTo should be populated. BWD-MOVED = Backward mapping move to one spot. Element movedTo should be populated. FWD/BWD-MOVED = Moved to one spot with Forward and backward mapping. Element movedTo should be populated. FWD/BWD-MULTI-MOVE = Moved to multiple spots with Forward and backward mapping. FWD/BWD-MAPPING = A simplistic mapping that supports both forward and backward. MAPPING = Complicated mapping. For any variation of a status of 'MOVED', the dot notation from a starting type to the new element. For example, 'cs_xxx.yyy' where yyy is the new element or attribute. A comment related to the status. Defines the compatibility of an old type to a new type. The name of the old type. Defines the status of a new type when substituted for the old type. Defines the compatibility of an old type to a new type. The compatibility of the substitution: FORWARD, BACKWARD, MAPPING, RENAME or CLARIFY. CLARIFY implies narrowing a constraint and is thus FORWARD compatible. RENAME is inherently MAPPING compatible. The name of the new type. A comment related to the status. Defines the compatibility of the values in an old enum type to the new values. The name of the old enum type. The compatibility of the substitution: CURRENT = The type is or a direct variant exists in the new schema. This is the default value. MAPPING = The type is only included for mapping purposes. This probably means that it was deleted. ADD = The type was added in the new schema. No new values should be defined. A comment related to the status. Defines the status of the equivalent type in the new schema. Defines the status of the equivalent type in the new schema. The name of the new type (may be the same as the old type). The name of an old value. Defines the status of an old enum value. The name of the old value. Required except for ADD. The compatibility of the substitution: ADD = The value was added to the new version. No backward mapping. CLARIFY = Implies narrowing a constraint and is thus forward compatible. Comment should be given. RENAME = Forward and backward mapping. One newValue should be given. DUPLICATE = Semantic duplicate. Forward compatible and backward mapping. One newValue should be given to represent the value that was retained. SPLIT = Split into multiple values. Forward mapping. Multiple newValues should be given. MERGE = Multiple values combined into one value. Backward mapping. One newValue should be given with each old value. MOVED = Moved with no appropriate mapping. Comment should be given. FWD-MOVED = Forward mapping move to one spot. Element movedTo should be populated. BWD-MOVED = Backward mapping move to one spot. Element movedTo should be populated. FWD/BWD-MOVED = Moved to one spot with forward and backward mapping. Element movedTo should be populated. FWD/BWD-MULTI-MOVE = Moved to multiple spots with forward and backward mapping. Comment should be given. FWD/BWD-MAPPING = A simplistic mapping that supports both forward and backward. Comment should be given. MAPPING = Complicated mapping. Comment should be given. For any variation of a status of 'MOVED', the dot notation from a starting type to the new element. For example, 'cs_xxx.yyy' where yyy is the new element or attribute. The name of the old value A comment related to the status. Defines the compatibility of a new enum value. The name of the new enum value. The compatibility of the substitution: FORWARD, BACKWARD, MAPPING, RENAME, DELETE or CLARIFY. CLARIFY implies narrowing a constraint and is thus FORWARD compatible. RENAME is inherently MAPPING compatible. For any variation of a status of 'MOVED', the dot notation from a starting type to the new element. For example, 'cs_xxx.yyy' where yyy is the new element or attribute. A comment related to the status.