Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

E01C02 made non-mandatory #297

Merged
merged 1 commit into from
Dec 6, 2022
Merged

E01C02 made non-mandatory #297

merged 1 commit into from
Dec 6, 2022

Conversation

franciscave
Copy link
Collaborator

The element is already non-mandatory in the XML binding, so making it non-mandatory in the data framework eliminates an inconsistency. See issue #293.

The element is already non-mandatory in the XML binding, so making it non-mandatory in the data framework eliminates an inconsistency. See issue #293.
@mdovey mdovey merged commit 52d7257 into develop Dec 6, 2022
@anthonywhitford anthonywhitford deleted the E01C02-non-mandatory branch April 3, 2024 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

In a Manifestation entity, should E01C02 Manifestation identifier be mandatory ?
2 participants