The validation "on" is expensive. It serializes the data to XML then parses the XML using xerces with validation features on. This does full validation.
Validation limited is probably what you want. Daffodil does it's own facet validation. At end of each element. It also validates max/minoccurs at end of each array. The parser is generated from the schema and so always enforces proper element tree structure. Validation off ignores the facets and max/minoccurs for validation. Sometimes parsing uses these, but often they are only for validation. The above only applies to parsing. Unparsing does no validation currently. But inherently, the schema is being traversed as the info set is provided, so unparsing insures the data conforms with the shape of the element tree, and unparsers need specific types in the info set. So facets aren't validated, but types and element tree are being enforced. Get Outlook for Android<https://aka.ms/ghei36> ________________________________ From: Costello, Roger L. <[email protected]> Sent: Tuesday, April 16, 2019 9:33:16 AM To: [email protected] Subject: I can't get the --validation flag to work Hello DFDL community, Question #1: If the --validation flag is not specified, what is its value (on, off, or limited)? Question #2: What does --validation on mean? What does --validation off mean? What does --validation limited mean? Question #3: I ran Daffodil using the --validation flag and I got this error message: [error] Excess arguments provided: '-s label-message-v2.dfdl.xsd -r input --validate on -o output/label-message-v2-with-erroneous-label.xml input/label-message-with-erroneous-label.txt' What am I doing wrong, please? /Roger
