Choice parsing leads to missing data errors

[aj-stein-nist]

Describe the bug

As reporting while debugging examples for usnistgov/metaschema#530, Dave and I determined that some model elements are being dropped when analyzing and validating document instances for fields, flags, and assembly node items bound to <choice/>s. I will be updating this ticket with example feature branch and tests with modules and instances that exhibit this error.

Who is the bug affecting?

Metaschema model developers and maintainers using the CLI or library.

What is affected by this bug?

Properly serilaizing and deserializing node items bound to fields/flags/assemblies in choices.

When does this occur?

Consistently.

How do we replicate the issue?

1. Run tests from the bug report branch.

If applicable, add screenshots to help explain your problem.}

Expected behavior (i.e. solution)

The library and/or CLI deserializes choice-based fields, flags, and correctly.

Other Comments

N/A

[aj-stein-nist]

Also per discussion with @david-waltermire, we ought to fix the space in the warning about skipping unhandled data in the fix for this bug, like Skipping unhandled JSON field 'y'FIELD_NAME 'y' at location '3:15'. from the model in the bug report below.

$ metaschema-cli validate-content -m metaschema.xml example.json --show-stack-trace
Loading module 'file:///home/me/code/issue-308_metaschema.xml'
Generating Java classes in: /tmp/validation-18284471153627273139
Validating '/home/me/code/issue-308_instance.json' as JSON.
Skipping unhandled JSON field 'y'FIELD_NAME 'y' at location '3:15'.
Validation identified the following in file '/home/me/code/issue-308_instance.json'.
The file '/home/me/code/issue-308_instance.json' is valid.