Remove validationAsErrors property from ISMVocabulary validation
Description
(Imported from Google Code) Starting in DDMS 3.1, the ISM vocabularies are automatically enforced via the generated CVE schemas. Validating against the XML vocabulary files is overkill.
CVE vaidation should only look out at the XML CVE files in DDMS 2.0 or 3.0.
The validationErrors configurable property should only work in DDMS 2.0 or 3.0. In later versions, an invalid set of values would not even make it past schema validation.
Activity
Brian Uri September 30, 2011 at 10:03 PM
Complete in Rev 697.
Brian Uri September 30, 2011 at 9:51 PM
The description above is half-assed and doesn't do a strong job of closing loopholes.
Clearer description of problem space and solution:
DDMS 2.0/3.0:
Values are not validated during schema validation when loading from XML files.
Values must be validated against the CVEs when loading from XML files.
Values must be validated against the CVEs when building up from scratch.
DDMS 3.1/4.0:
Values are validated during schema validation.
No additional validation against the CVEs is required when loading from XML files.
Values must be validated against the CVEs when building up from scratch.
Unified Approach:
Where viable, values will be validated against the schema when loading from XML files.
Values will always be validated against the CVEs when loading from XML files, to cover 2.0/3.0 cases.
Values will always be validated against the CVEs when building up from scratch.
The validationAsErrors property should be removed.
(Imported from Google Code)
Starting in DDMS 3.1, the ISM vocabularies are automatically enforced via the generated CVE schemas. Validating against the XML vocabulary files is overkill.
CVE vaidation should only look out at the XML CVE files in DDMS 2.0 or 3.0.
The validationErrors configurable property should only work in DDMS 2.0 or 3.0. In later versions, an invalid set of values would not even make it past schema validation.