See information about the latest product version
Unsupported features
The following features of the DFDL 1.0 specification are currently not supported in this implementation.
Property enumerations
The following property enumerations are unsupported.
Feature | Reference in DFDL specification |
---|---|
dfdl:truncateSpecifiedLengthString "yes" | 13.4 Properties Specific to String |
dfdl:textBiDi "yes" | 21. Optional DFDL Features |
dfdl:occursCountKind "stopValue" | 16. Properties for Array Elements and Optional Elements |
dfdl:occursCountKind "parsed" Note: Use dfdl:occursCountKind "implicit" with maxOccurs="unbounded". |
16. Properties for Array Elements and Optional Elements |
dfdl:binaryCalendarRep "packed" | 13.13 Properties Specific to Calendar with Binary Representation |
dfdl:sequenceKind "unordered" | 14.3 Unordered Sequence Groups |
dfdl:floating "yes" | 14.4 Floating Elements |
dfdl:lengthKind "endOfParent" | 12.3 Properties for Specifying Lengths |
dfdl:lengthKind "pattern" |
12.3 Properties for Specifying Lengths |
dfdl:assert testKind "pattern" dfdl:failureType "recoverableError" (dfdl:assert) |
7.3 The dfdl:assert Statement Annotation Element |
dfdl:discriminator testKind "pattern" | 7.4 The dfdl:discriminator Statement Annotation Element |
dfdl:separatorSuppressionPolicy "trailingEmptyStrict" 1 | 14.2 Sequence Groups with Separators |
dfdl:encodingErrorPolicy "replace" | 11.2 Character Encoding and Decoding Errors |
dfdl:textZonedSignStyle "asciiTandemModified" | 13.6 Properties Specific to Number with Text Representation |
1 This property is called dfdl:separatorPolicy in the IBM implementation.
Properties
The following properties are unsupported:
Feature | Reference in DFDL specification |
---|---|
dfdl:hiddenGroupRef | 14.5 Hidden Groups |
dfdl:inputValueCalc |
17. Calculated Value Properties. |
dfdl:choiceBranchKey |
15. Choice Groups |
Functions
The following functions are unsupported in DFDL expressions:
Feature | Reference in DFDL specification |
---|---|
fn:count |
23.5 Constructors, Functions and Operators |
fn:name |
|
dfdl:contentLength |
|
dfdl:testBit |
|
dfdl:occursIndex | |
dfdl:checkConstraints | |
dfdl:timeZoneFromDate |
|
All dfdl: constructor functions | |
dfdl:decodeDFDLentities |
Annotations
The following annotations and annotation placements are unsupported:
Feature | Reference in DFDL specification |
---|---|
dfdl:defineVariable with external=true | 7.7 The dfdl:defineVariable Annotation Element |
dfdl:newVariableInstance | 7.8 The dfdl:newVariableInstance Statement Annotation Element |
dfdl:assert on global element and simple type | 7.3 The dfdl:assert Statement Annotation Element |
dfdl:discriminator on global element and simple type | 7.4 The dfdl:discriminator Statement Annotation Element |
Other restrictions
The following restrictions also apply:
Feature | Reference in DFDL specification |
---|---|
Use of default values is not supported in the following circumstances:
|
|
When dfdl:lengthKind is 'implicit' for a complex element, it is possible that the element is prematurely terminated by encountering a higher level terminating delimiter. |
12.3.2.1 Simple Elements of Specified Length within Delimited Constructs |
When encoding is 'UTF-8', 'UTF-16' or 'UTF-32' a byte order mark at document start is not automatically processed, and must be modeled explicitly if it is to affect the encoding of the document. |
|
Schemas must contain only one DFDL xs:appinfo element within each xs:annotation element, as subsequent xs:appinfo elements might not be processed correctly. |
|
When dfdl:lengthKind is 'prefixed', the simple type referenced by the dfdl:prefixLengthType property can not also have dfdl:lengthkind 'prefixed'. |
|
Not all instances of inapplicable DFDL property placement are reported. |
|
All global elements are assumed to be potential document roots and are validated accordingly. |
|
Complex elements are not allowed to be nillable. |
|
When parsing, the distinction between an element being 'missing', having an 'empty representation' and having an 'absent representation', is not in accordance with the specification. |
|
When an element has binary representation, a DFDL character entity is not allowed in the definition of a nil value for the element. |
|
When serializing a nillable element with binary representation, dfdl:nilKind cannot be set to 'literalValue'. Use 'logicalValue' or 'literalCharacter' instead. |
|
dfdl:textStandardDecimalSeparator is not allowed to be a list of values. |
|
dfdl:textStandardExponentRep is not allowed to be more than one character, and not allowed to be empty string.2 |
|
The '@' (significant digits) symbol is not allowed in dfdl:textNumberPattern. |
|
The '_' (underscore) character is not allowed in dfdl:calendarLanguage. |
13.11 Properties specific to Calendar with Text or Binary Representation |
dfdl:calendarPattern does not support any use of the symbols 'O', 'x', 'X', nor does it support the symbol 'V' when used singly. 13.11 | 13.11 Properties specific to Calendar with Text or Binary Representation |
dfdl:calendarTimeZone is not allowed to be empty string or to be an Olson format time zone. |
13.11 Properties specific to Calendar with Text or Binary Representation |
When serializing a fixed length element of type xs:hexBinary, dfdl:fillByte is not used to pad the data when the data is shorter than the length. |
|
dfdl:lengthUnits 'bits' is not allowed for binary signed integers. |
|
A binary packed number with dfdl:lengthUnits 'bits' is not checked to see that the length is a multiple of 4 bits. |
|
A binary packed number with dfdl:alignmentUnits 'bits' is not checked to see that the alignment is a multiple of 4 bits. |
|
All elements with text representation are assumed to align on an 8-bit boundary. There is no support for encodings that are not 8-bit aligned. |
|
dfdl:textStandardDecimalSeparator, dfdl:textStandardGroupingSeparator, dfdl:textStandardExponentRep, dfdl:textStandardInfinityRep, dfdl:textStandardNanRep and dfdl:textStandardZeroRep are not checked to ensure they are all distinct from one another. |
|
dfdl:calendarLanguage is not allowed to be an expression. |
13.11 Properties specific to Calendar with Text or Binary Representation |
dfdl:assert message is not allowed to be an expression. |
|
dfdl:discriminator message is not allowed to be an expression. |
|
Adjacent white space is collapsed in DFDL properties that are DFDL expressions. |
|
Path locations in DFDL expressions are not correctly validated. Specifically, array elements without predicates and references into other choice branches are not flagged as errors. Avoid using such path locations. |
|
dfdl:initiator and dfdl:textStandardZeroRep incorrectly allow the use of %WSP*; entity class on its own. Use %WSP+; instead. |
12.2 Properties for Specifying Delimiters , 13.6 Properties Specific to Number with Text Representation |
dfdl:terminator and dfdl:separator incorrectly allow the use of %WSP*; entity class on its own when scanning for delimiters. Use %WSP+; instead when scanning for delimiters. |
13.6 Properties Specific to Number with Text Representation , 14.2 Sequence Groups with Separators |
When serializing, the application of an escape scheme takes place after the application of dfdl:emptyValueDelimiterPolicy. |
|
dfdl:calendarPattern allows symbols 'T' and 'U' as specified by the original DFDL 1.0 specification. These symbols have been deleted in the latest revision. Avoid using these symbols. | 13.11 Properties specific to Calendar with Text or Binary Representation |
dfdl:calendarPattern allows symbols 'T' and 'U' as specified by the original DFDL 1.0 specification. These symbols have been deleted in the latest revision. Avoid using these symbols. | 13.11 Properties specific to Calendar with Text or Binary Representation |
Encodings other than ASCII-compatible encodings and EBCDIC encodings are allowed whendfdl:textNumberRep is 'zoned'. Avoid using such encodings. | 13.6 Properties Specific to Number with Text Representation |
dfdl:occursCountKind and related properties are not allowed on global elements. | 13.16 Properties for Nillable Elements |
dfdl:representation must be set for an element of type xs:string | 13.12 Properties Specific to Calendar with Text Representation |
dfdl:representation must be set for an element of type xs:hexBinary | 13.12 Properties Specific to Calendar with Text Representation |
A value of empty string for dfdl:binaryBooleanTrueRep is not supported. |
13.10 Properties Specific to Boolean with Binary Representation |
The fn:concat function is limited to four arguments. | 23.5.2.3 String Functions |
2 This property is called dfdl:textStandardExponentCharacter in the IBM implementation.