stevedlawrence commented on a change in pull request #517:
URL: https://github.com/apache/daffodil/pull/517#discussion_r601740690
##########
File path:
daffodil-test/src/test/resources/org/apache/daffodil/section14/sequence_groups/SequenceGroupNestedArray.tdml
##########
@@ -219,6 +219,7 @@ notice blank lines are skipped
<ex:record>
<ex:item>notice lines of all commas are skipped</ex:item>
</ex:record>
+ <ex:record />
Review comment:
``emptyElementParsePolicy="treatAsMissing"`` does change Daffodil's
behavior, but it is still slightly different from IBM's default behavior. With
that property set, Daffodil stops parsing when it hits that comma, considers
the parse a success, and outputs an infoset, just with left over data starting
at that comma. So it does seem like we both think that comma is an error, but
Daffodil interprets it as the end of the ``record`` array, whereas IBM DFDL
interprets it as a fatal error.
We both have the same behavior when ``minOccurs="0"``. So it seems there's
only one discrepency about how this parse error should be handled.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
