Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Under construction

 

Release 0.81

Errata

Some of the official errata in the DFDL specification are supported in Daffodil.

Keep in mind that Daffodil does not implement (currently) an unparser, so when the tables below indicate 'Yes' for support of an erratum, that means it is supported in the Daffodil parser.

The following tables show which errata are supported by Daffodil. The tables use the same numbering as the OGF errata document.
N/A means that the erratum is just a clarification to the specification. 'No' means either it is known not to work in conformance with the specification as modified by the erratum, OR, it is simply unknown whether it works properly or not. 'Yes' means it is known to work properly, and there is reasonable test coverage of this.
Where the erratum is partially supported, the Notes column provides further information.

Major errata

 

ErratumSupportedNotes
3.1Yes 
3.2Yesdfdl:outputValueCalc not supported (because unparsing not supported)
3.3Yes 
3.4NorecoverableError not supported
3.5Yes 
3.6NoNot supported
3.7NounicodeByteOrderMark not supported. Use UTF-16BE or UTF-16LE, UTF-32BE or UTF-32LE
3.8NoProperties for some unimplemented features are ignored. No warning or error.
3.9Partiallydfdl:lengthKind 'pattern' is limited to only text. Recursively children are not checked for text and same encoding.
3.10Yes 
3.11Yesdfdl:occursCountKind 'implicit' and 'parsed' are supported.
3.12NoValidation is not supported.
3.13NoThe property encodingErrorPolicy is not supported. The behaviour in the presence of decode errors is undetermined.
3.14YesBoth old (deprecated) property is supported along with the new one.
3.15NoThe new properties elementID and choiceBranchRef are not supported.
3.16PartiallyThe removed property documentFinalSeparatorCanBeMissing is not accepted. However, documentFinalTerminatorCanBeMissing is not supported.
3.17See sub table
FeatureDetectionSupportNotes
Text representation for types other than String
dfdl:representation="text" for Number, Calendar or Boolean types
PartialMany of the more advanced text number format properties are not supported.
Delimiters
dfdl:separator <> "" or dfdl:initiator <> "" or dfdl:terminator <>  "" or dfdl:lengthKind="delimited"
Yes 

BCD calendars

BCD numbers

IBM4690 packed calendars

IBM4690 packed numbers

 No 
Multiple schemasxs:include or xs:import in xsdYes 
Named formatsdfdl:defineFormat or dfdl:refYes 
Choicesxs:choice in xsdPartialchoiceLength, choiceBranchRef, and elementID not supported
Arrays where size not known in advance
dfdl:occursCountKind 'implicit', 'parsed', 'stopValue'
Partial'stopValue' not supported.
Expressions
Use of a DFDL expression in any property or attribute value
Partial

The dfdl:assert and dfdl:discriminator annotations are supported. The inputValueCalc property is supported.

Runtime-valued properties (e.g., byteOrder or encoding computed using an expression) are not supported.

End of parentdfdl:lengthKind='endOfParent'No 
3.18YesFunctions use the new names. (The rest of this erratum is not observable in behavior of the system.)
3.19NoDefault values are not consistently evaluated. Constants can be used, but reference between default value expressions may cause a schema definition error.
3.20Nodfdl:newVariableInstance not supported
3.21PartialNew placement restrictions are not checked. External variables are not supported.
3.22No(This erratum is not behavioral, however, it is relevant that single-assignment checking of variables is currently not consistently performed.)
3.23Yes 
3.24Yes 
3.25Partialdfdl:newVariableInstance is not supported.
3.26NoDefault values not supported.

 

Minor errata

...

this page has moved to https://daffodil.apache.org/unsupported/