Validating schema-specific attributes
If you want to guarantee that a particular set of schema-specific attributes are present in an exported fragment's (that is, the child object’s) top element and that it is assigned specific values, the attributes and their values must be entered into an AppData value as a space delimited string.
Note that the values are case-sensitive.
This example is for the schema, play.xsd, when located in the specified path.
| User | Key Path | Name |
|---|---|---|
| {Global} | /Document Types/PLAY | ROOT_ATTRS |
| Value | ||
| ||
If a schema or namespace attributes exist in the exported root element, they are deleted and replaced by the ones in AppData.
If there is a user who edits document types using a schema stored on the local workstation, then there are entries in AppData under that override the ones in Global.