See also: Bulk Import of XML Data. 1. Verifying changesPlease check that your changes don't cause problems. A minimal test is to run ConsoleCheckCLDR with the following parameter: <!ELEMENT commonlyUsed (true | false ) #IMPLIED >. I changed to <!ELEMENT commonlyUsed EMPTY > to 2. Explicit defaultsDon't use them, since they cause the XML to be fluffed up, and may interfere with the inheritance unless you make other modifications. Instead, the default should be documented in the spec 3. Mixing meanings.Attribute and element names should be unique, unless they have the same meaning across containing elements, and same substructure. This is a hard-and-fast rule for elements. For attributes, it is better to have unique names (as we've found by bitter experience) where possible. It is *required* when the attribute is distinguishing for one element and not for another. |