[
https://issues.apache.org/jira/browse/DAFFODIL-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16857042#comment-16857042
]
Michael Beckerle edited comment on DAFFODIL-2143 at 6/5/19 9:19 PM:
--------------------------------------------------------------------
DFDL spec 15.1.2 states that a choice cannot have both dfdl:initiatedContent
and dfdl:choiceDispatchKey.
was (Author: mbeckerle):
Also: a choice using dfdl:choiceDispatchKey does not create a point of
uncertainty. Use of dfdl:initiatedContent AND dfdl:choiceDispatchKey on the
same choice should be an SDE. However, the DFDL spec does not say so (that I
could find) so I will seek clarification.
> dfdl:initiatedContent="yes" on sequence should only affect optional children
> ----------------------------------------------------------------------------
>
> Key: DAFFODIL-2143
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2143
> Project: Daffodil
> Issue Type: Bug
> Components: Back End
> Affects Versions: 2.4.0
> Reporter: Michael Beckerle
> Priority: Major
> Fix For: 2.4.0
>
>
> EDIFACT uses sequences which have dfdl:initiatedContent="yes" but one or more
> of the child elements of the sequence is required, not optional.
> Daffodil appears to execute a discriminator=true behavior even for these
> required elements, which means the point of uncertainty being discriminated
> is some enclosing one, as the element itself in the sequence doesn't have one.
> The DFDL Spec clearly says that the initiatedContent only affects optional
> elements.
> The right thing is for a required child to ignore initiatedContent.
> If all children of a sequence are required and the sequence has
> initiatedContent, that should at least be a warning, because the
> initiatedContent property would then be entirely ignored. This case does come
> up in EDIFACT.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
