Unsupported features

dfdl:choiceBranchKey
dfdl:choiceDispatchKey

fn:count
fn:exactly-one

fn:name
fn:local-name
fn:namespace-uri

dfdl:contentLength
dfdl:valueLength

dfdl:testBit
dfdl:setBits

dfdl:timeZoneFromDate
dfdl:timeZoneFromDateTime
dfdl:timeZoneFromTime

dfdl:decodeDFDLentities
dfdl:encodeDFDLentities
dfdl:containsDFDLentities

Use of default values is not supported in the following circumstances:

• during parsing;

• during serialization for a complex element where content is a choice group.

9.4 Element Defaults

When dfdl:lengthKind is 'implicit' for a complex element, the element can be 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.

11.1 Unicode Byte Order Marks (BOM)

Schemas must contain only one DFDL xs:appinfo element within each xs:annotation element, as subsequent xs:appinfo elements might not be processed correctly.

6. DFDL Syntax Basics

When dfdl:lengthKind is 'prefixed', the simple type referenced by the dfdl:prefixLengthType property can not also have dfdl:lengthkind 'prefixed'.

12.3.4 dfdl:lengthKind 'prefixed'

Not all instances of inapplicable DFDL property placement are reported.

2.7 Optional Checks and Warnings

All global elements are assumed to be potential document roots and are validated accordingly.

2.7 Optional Checks and Warnings

dfdl:lengthKind 'pattern' can not be used with elements of binary representation.

12.3.5 dfdl:lengthKind 'pattern'

Complex elements are not allowed to be nillable.

5.1 DFDL Subset of XML Schema

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.

9.2 DFDL Data Syntax Grammar

When an element has binary representation, a DFDL character entity is not allowed in the definition of a nil value for the element.

13.15 Nil Value Processing

When serializing a nillable element with binary representation, dfdl:nilKind cannot be set to 'literalValue'. Use 'logicalValue' or 'literalCharacter' instead.

13.15 Nil Value Processing

dfdl:textStandardDecimalSeparator is not allowed to be a list of values.

13.6 Properties Specific to Number with Text Representation

dfdl:textStandardExponentRep is not allowed to be more than one character, and not allowed to be empty string.

13.6 Properties Specific to Number with Text Representation

The '@' (significant digits) symbol is not allowed in dfdl:textNumberPattern.

13.6 Properties Specific to Number with Text Representation

The '_' (underscore) character is not allowed in dfdl:calendarLanguage.

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.

12.3.7.2.6 Length of Binary Opaque Elements

dfdl:lengthUnits 'bits' is not allowed for binary signed integers.

12.3.7.2.1 Base-2 Binary Number Elements

A binary packed number with dfdl:lengthUnits 'bits' is not checked to see that the length is a multiple of 4 bits.

12.3.7.2.5 Length of Packed Decimal Binary Number Elements

A binary packed number with dfdl:alignmentUnits 'bits' is not checked to see that the alignment is a multiple of 4 bits.

12.1.3 Mandatory Alignment for Packed Decimal Data

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.

12.1.2 Mandatory Alignment for Textual Data

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.

13.6 Properties Specific to Number with Text Representation

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.

7.3 The dfdl:assert Statement Annotation Element

dfdl:discriminator message is not allowed to be an expression.

7.4 The dfdl:discriminator Statement Annotation Element

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.

23. Expression language

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.

When serializing, the application of an escape scheme takes place after the application of dfdl:emptyValueDelimiterPolicy.

13.2.1 The dfdl:escapeScheme Properties

A value of empty string for dfdl:binaryBooleanTrueRep is not supported.

13.10 Properties Specific to Boolean with Binary Representation