Release 0.81
This release contains only a parser. There is no unparser functionality in this release.
The following are not yet implemented as of this release:
Numeric Types: decimal, integer, nonNegativeInteger
- textNumberPattern
Other Types: boolean, hexBinary
...
, and all associated properties.
- For types date/time/dateTime
...
Choice: several features are not yet implemented including:
- choiceLength
- tbd
...
- binary representations (text representation IS supported)
nilKind="literalCharacter"
- nilKind="logicalValue"
- useNilAsDefault
- lengthKind="endOfParent"
- lengthKind="prefixed"
- occursCountKind="stopValue"
- Defaulting of values for required elements
- separatorSuppressionPolicy
- ignoreCase="yes"
- the newVariableInstance annotation element
- textNumberKind="zoned"
- any 'packed' binary number representation (packed, bcd, ...)
- unicodeByteOrderMark
- bi-directional text properties
- unordered sequences
- documentFinalTerminatorCanBeMissing
- external variables
- choices: choiceLength property
- raw-byte entities
- validation - to be clear, one can call the dfdl:checkConstraints function from an assertion or discriminator or inputValueCalc, but there is no command-line option to tell Daffodil to validate the data with respect to the schema.
- utf16Width='variable'
- save/reload of a parser
- alignment, alignmentUnits, leadingSkip, trailingSkip
- dfdl:contentLength and dfdl:valueLength functions
- attributeFormDefault (attribute of the xs:schema element)
Some additional limitations:
- File sizes are limited to 4Gigabytes due to underlying Java libraries using type int for offsets.
- A Java 7 JVM is required as a number of its regular expression capabilities are passed through to Daffodil's DFDL implementation (as is required by the standard).
- An expression enclosed in {{ ... } cannot have whitespace before or after the brace {{, } characters. To work around this limitation, use CDATA, that is, as the body of an element, wrap expressions like this: <![CDATA[{...expression...}]]>