document #349

Action 305 - Section 9.4 - Clarifications on Element Defaults

Added by Michael Beckerle 26 days ago. Updated 26 days ago.

Status:submitted Start date:06/27/2019
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:DFDL v1.0
Document Type:Proposed Recommendation

Description

Section 9.4
Item 2 under "For elements and element refs:" Change to: "dfdl:element following property scoping rules, which includes establishing representation as described in Section 9.3.2 and conversion to element type for simple types."

Section 9.4.2
Before the final phrase "There are three main cases to consider:" Insert this sentence: "The sections below indicate when an item is added to the infoset, and whether it has a default or other value. If there is no processing error then regardless of whether an item is added to the infoset or not, any side-effects due to dfdl:discriminator statements evaluating to true, or dfdl:setVariable statements, are retained."

Sections 9.4.2.2 and 9.4.2.3
The phrase "Optional occurrence: If dfdl:emptyValueDelimiterPolicy is not 'none'[12]," Change to "Optional occurrence: if dfdl:emptyValueDelimiterPolicy is applicable and is not 'none',...." (retaining the footnote)

Section 9.4.2.3. (IGNORING THIS AS NO CONCLUSION WAS REACHED)
We agreed that the paragraphs beginning with "For both required and optional..." need to be better tied to the material above. Wording TBD - pending Steve Hanson doing some tests on IBM DFDL.

History

Updated by Michael Beckerle 26 days ago

I discovered that erratum 5.10 already includes modified wording equivalent to one of the things discussed:

5.10 says: Add a clause in 9.4.2.2 and 9.4.2.3 so that the statement about optional occurrences says "If dfdl:emptyValueDelimiterPolicy is in effect and is not 'none'...", as the words today do not cover cases when it is ignored (no initiator or terminator).

Our discussion in this thread is slightly different wording:

Sections 9.4.2.2 and 9.4.2.3
The phrase "Optional occurrence: If dfdl:emptyValueDelimiterPolicy is not 'none'[12]," Change to "Optional occurrence: if dfdl:emptyValueDelimiterPolicy is applicable and is not 'none',...." (retaining the footnote)

I prefer the terminology "is applicable" here, as "in effect" can have the connotation of just "is set".

So the update is to the Erratum 5.10 and the specification document (which will have Erratum 5.10 applied to it ultimately.)

Also available in: Atom PDF