[DAFFODIL-1630] lengthKind explicit and expressions when unparsing - expression not being evaluated but should be

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.1.0
• Component/s: Back End, DFDL Language
• Assignee: Dave Thompson
• Reporter: Mike Beckerle
• Created: 11/Oct/16 14:42
• Updated: 20/May/21 12:34
• Resolved: 16/Aug/18 15:13

Description

This was clarified on DFDL workgroup call on 2016-10-11

Verify that Daffodil conforms to erratum 5.18 per below.

lengthKind ' expression ' when unparsing

Spec says "When dfdl:lengthKind is 'explicit' (and dfdl:length is an expression), 'delimited',
'prefixed', 'pattern' the data value is padded to the length given by the XSD minLength facet
for type 'xs:string' or dfdl:textOutputMinLength property for other type" .

This is not the latest agreed thinking. The desired behaviour is as documented by erratum 5.18
in Experience Document 4, which states the expression is evaluated and the result taken as
the explicit length. This has not yet been added to the spec.

Issue Links

• relates to: DAFFODIL-1584 Unparser lengthKind explicit for xs:string - minLength facet should not be used