Under construction
Release 0.81
Errata
Some of the official errata in the DFDL specification are supported in this implementation of DFDL.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 status of the DFDL 1.0 specification is currently Proposed Recommendation. A number of errata are described on the Open Grid Forum (OGF) website. Some errata are clarifications to the specification document, but several errata affect an implementation. The following tables show which errata are supported by the IBM implementationDaffodil. 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, and recommendations to avoid problems when the erratum is implemented.
Major errata
| Erratum | Supported | Notes | ||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 3.1 | Yes | |||||||||||||||||||||||||||||||||||||||||
| 3.2 | Yes | dfdl:outputValueCalc not supported (because unparsing not supported) | ||||||||||||||||||||||||||||||||||||||||
| 3.3 | Yes | |||||||||||||||||||||||||||||||||||||||||
| 3.4 | No | recoverableError not supported | ||||||||||||||||||||||||||||||||||||||||
| 3.5 | Yes | |||||||||||||||||||||||||||||||||||||||||
| 3.6 | No | Not supported | ||||||||||||||||||||||||||||||||||||||||
| 3.7 | No | unicodeByteOrderMark not supported. Use UTF-16BE or UTF-16LE, UTF-32BE or UTF-32LE | ||||||||||||||||||||||||||||||||||||||||
| 3.8 | No | Properties for some unimplemented features are ignored. No warning or error. | ||||||||||||||||||||||||||||||||||||||||
| 3.9 | Partially | dfdl:lengthKind 'pattern' is limited to only text. Recursively children are not checked for text and same encoding. | ||||||||||||||||||||||||||||||||||||||||
| 3.10 | Yes | |||||||||||||||||||||||||||||||||||||||||
| 3.11 | Yes | dfdl:occursCountKind 'implicit' and 'parsed' are supported. | ||||||||||||||||||||||||||||||||||||||||
| 3.12 | No | Validation is not supported. | ||||||||||||||||||||||||||||||||||||||||
| 3.13 | No | The property encodingErrorPolicy is not supported. The behaviour in the presence of decode errors is undetermined. | ||||||||||||||||||||||||||||||||||||||||
| 3.14 | Yes | Both old (deprecated) property is supported along with the new one. | ||||||||||||||||||||||||||||||||||||||||
| 3.15 | No | The new properties elementID and choiceBranchRef are not supported. | ||||||||||||||||||||||||||||||||||||||||
| 3.16 | Partially | The removed property documentFinalSeparatorCanBeMissing is not accepted. However, documentFinalTerminatorCanBeMissing is not supported. | ||||||||||||||||||||||||||||||||||||||||
| 3.17 | See sub table |
| ||||||||||||||||||||||||||||||||||||||||
| 3.18 | Yes | Functions use the new names. (The rest of this erratum is not observable in behavior of the system.) | ||||||||||||||||||||||||||||||||||||||||
| 3.19 | No | Default values are not consistently evaluated. Constants can be used, but reference between default value expressions may cause a schema definition error. | ||||||||||||||||||||||||||||||||||||||||
| 3.20 | No | dfdl:newVariableInstance not supported | ||||||||||||||||||||||||||||||||||||||||
| 3.21 | Partial | New placement restrictions are not checked. External variables are not supported. | ||||||||||||||||||||||||||||||||||||||||
| 3.22 | No | (This erratum is not behavioral, however, it is relevant that single-assignment checking of variables is currently not consistently performed.) | ||||||||||||||||||||||||||||||||||||||||
| 3.23 | Yes | |||||||||||||||||||||||||||||||||||||||||
| 3.24 | Yes | |||||||||||||||||||||||||||||||||||||||||
| 3.25 | Partial | dfdl:newVariableInstance is not supported. | ||||||||||||||||||||||||||||||||||||||||
| 3.26 | No | Default values not supported. |
...
| Erratum | Supported | Notes | |
|---|---|---|---|
| 2.1 | Yes | ||
| 2.2 | PartiallyNo | Do not use dfdl:decimalVirtualPoint to indicate the start of fractional secondsbinary calendars not supported | |
| 2.3 | Yes | ||
| 2.4 | Yes | No | delimited binary not supported |
| 2.5 | No | dfdl:lengthKind 'endOfParent' not supported | |
| 2.6 | N/A | ||
| 2.7 | NoYes | dfdl:inputValueCalc and dfdl:outputValueCalc not supported (as unparsing is not supported) | |
| 2.8 | Yes | No | nilKind='literalCharacter' not supported |
| 2.9 | Yes | No | Facets must be used with lengthUnits='characters' |
| 2.10 | N/A | ||
| 2.11 | Yes | ||
| 2.12 | NoVariables | not supportedMulti-file schema interactions with variable naming not yet tested. | |
| 2.13 | No | Prefix length type with prefix length not supported | |
| 2.14 | PartiallyNo | Prefix length type with prefix length not supported. All property restrictions are checkedNo checking for these constraints. | |
| 2.15 | Yes | No | Zoned format not supported |
| 2.16 | Yes | ||
| 2.17 | Yes | Partial | Raw byte entities not supported |
| 2.18 | Yes | ||
| 2.19 | Yes | ||
| 2.20 | Yes | Partial | Raw byte entities not supported. 'literalCharacter' not supported. |
| 2.21 | No | dfdl:textNumberCheckPolicy behaves according to the specificationnot supported. It is ignored. | |
| 2.22 | Partially | Do not specify an expression for dfdl:textStandardDecimalSeparator that evaluates to the empty string | |
| 2.23 | Nodfdl:decimalSeparator may not be a list | Property unimplemented. | |
| 2.24 | Partially | No | Property unimplemented.Do not specify an expression for dfdl:textStandardGroupingSeparator that evaluates to the empty string |
| 2.25 | Yes | ||
| 2.26 | Partially | No | Property unimplemented.Do not specify an expression for dfdl:textStandardExponentCharacter that evaluates to the empty string |
| 2.27 | NoEnsure that dfdl:textStandardDecimalSeparator is set sensibly even for integer types | Property unimplemented. | |
| 2.28 | NoICU significant digits symbol '@' not supported | textNumberPattern property is unimplemented | |
| 2.29 | N/A | ||
| 2.30 | Partially | No | boolean type not implemented.Ensure that when element length is fixed and not trimming or padding, all dfdl:textBooleanTrueRep and dfdl:textBooleanFalseRep values must be the same length |
| 2.31 | No | dfdl:occursCountKind 'stopValue' not supported | |
| 2.32 | N/A | ||
| 2.33 | N/A | ||
| 2.34 | Yes | ||
| 2.35 | No | dfdl:inputValueCalc return value is not range checked if numeric. Validation not supported. | |
| 2.36 | Yes | ||
| 2.37 | YesNo | Untested. | |
| 2.38 | Yes | Partial | dfdl:byteOrder applies to the types and binary representations currently implemented. |
| 2.39 | Yes | ||
| 2.40 | Yes | No | decimal type unsupported, textNumberPattern unsupported |
| 2.41 | N/A | ||
| 2.42 | YesNo | Property unimplemented | |
| 2.43 | Yes | ||
| 2.44 | Yes | ||
| 2.45 | YesNo | Property unimplemented | |
| 2.46 | NoOnly | single characters allowed for exponent usng property dfdl:textStandardExponentCharacterProperty unimplemented | |
| 2.47 | Yes | ||
| 2.48 | Yes | No | Testing status unclear (TBD) |
| 2.49 | YesNo | Untested. | |
| 2.50 | NoAll | calendar values have a time zone, either explicit or via dfdl:calendarTimeZoneUntested. | |
| 2.51 | NoEnsure that all calendar elements have an explicit time zone when serializing | Unparsing not supported | |
| 2.52 | Yes | No | ICU 'u' extended year is untested. Negative years using 'y' and 'G' untested. |
| 2.53 | Yes | No | binary calendar types not supported |
| 2.54 | No | textNumberPattern not supported | |
| 2.55 | N/A | ||
| 2.56 | NoDo not create elements of type xs:date or xs:time that have binary representation and binaryCalendarRep set to 'binarySeconds' or 'binaryMilliseconds | 'binary calendar types not supported | |
| 2.57 | Yes | No | binary calendar types not supported |
| 2.58 | Yes | No | nilKind='logicalValue' not supported |
| 2.59 | Yes | ||
| 2.60 | Nodfdl:textBidi 'yes' not | None of the bidi text properties are supported | |
| 2.61 | N/A | ||
| 2.62 | Yes | ||
| 2.63 | No | For affected properties, do not specify an expression that returns the empty stringRuntime-valued properties not supported. | |
| 2.64 | Yes | ||
| 2.65 | No | Olson timezones are not supported. | |
| 2.66 | No | ||
| 2.67 | N/A | ||
| 2.68 | No | ||
| 2.69 | N/A | ||
| 2.70 | Yes | ||
| 2.71 | Yes | No | ignoreCase="yes" not supported |
| 2.72 | No | endOfParent not supported. | |
| 2.73 | Yes | No | endOfParent not supported. |
| 2.74 | No | unparsing not supported | |
| 2.75 | YesN/A | ||
| 2.76 | Yes | No | prefixed lengthKind is not supported |
| 2.77 | N/A | ||
| 2.78 | YesNo | unparsing not supported | |
| 2.79 | YesNo | textNumberPattern not supported | |
| 2.80 | No | textNumberPattern not supported | |
| 2.81 | Yes |