Concur that optional choices and also nillable are fundamentally important
data-representation capabilities to support.
Note that similar issues occur for attributes, which also need to be
supported by DFDL. When we round-trip convert element+attribute XML to
element-only XML so that DFDL can han
Becomes
Now the child of the choice is a non-optional sequence element.
On Fri, Mar 25, 2022 at 8:15 AM Roger L Costello wrote:
> Thank you Steve!
>
> You've provided a workaround for optional choice: omit minOccurs="0" and
> add within the ch
Well, the good news is that your 3rd item, about allowing hyphens (or non
ES generally) as nilValue for complex type elements is targeted for release
3.4.0 of daffodil as an experimental extension to DFDL which assuming it
works out, we would propose for inclusion in a future DFDL revision. (Now
we
Also, is there a workaround for this issue: DFDL does not allow an element with
complexType to have a nilValue other than %ES;
-Original Message-
From: Roger L Costello
Sent: Friday, March 25, 2022 8:15 AM
To: users@daffodil.apache.org
Subject: Re: Recommended changes to the DFDL langua
Thank you Steve!
You've provided a workaround for optional choice: omit minOccurs="0" and add
within the choice.
Is there a workaround for optional elements in a choice?
/Roger
-Original Message-
From: Steve Lawrence
Sent: Friday, March 25, 2022 8:07 AM
To: users@daffodil.apache.org
One alternative for minOccurs on a choice is to have an empty branch:
I admit that minOccurs="0" is a little more self documenting.
I think minOccurs also means something different if there are delimiters
on the choice. For example, say we had these two snippets to implement
a
Hi Folks,
I am converting 350 military data formats to DFDL.
Everyone of the 350 data formats has an optional choice:
DFDL does not allow optional choice. Why?
I recommend changing the DFDL language to allow optional choice.
Everyone of the 350 data formats has branches of a choice that are
