...
- Edit core/tests/AA.dfdl.xsd in eclipse. Notice that it does not use xmlns="http://www.w3.org/2001/XMLSchema", which is the usual name space for XML Schema. Rather, it uses "http://www.ogf.org/dfdl/dfdl-1.0/XMLSchemaSubset" which provides much more DFDL-oriented schema validation.
- Note that the file extension ".dfdl.xsd" is the standard way to identify a DFDL schema file.
- Change one of the dfdl:inputValueCalc properties and misspell the property name. Save the file and you should see a validation error.
- Validation using the DFDL XML Schema Subset URL will validate short form and long form DFDL annotations, and enforce DFDL's subset of XML Schema.
...
- Edit core/tests/AH.dfdl.xsd in eclipse. Notice that it uses xmlns="http://www.w3.org/2001/XMLSchema", which is the usual name space for XML Schema.
- Note that the file extension ".dfdl.xsd" is the standard way to identify a DFDL schema file.
- Change one of the dfdl:inputValueCalc properties and misspell the property name. Save the file and you will NOT see any validation error.
- Change one of the attributes of the dfdl:defineVariable element, such as remove the name attribute and put in a ref="foo" attribute. Save, and you should see a validation error.
- Validation using the standard XML Schema URL will NOT validate short form DFDL annotations, nor will it care if you put a long form annotation element named dfdl:foobar. But if you do get the name of a DFDL annotation element correct, then it will validate the properties on that annotation element.
...