-
Notifications
You must be signed in to change notification settings - Fork 5
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
YAML file enumeration value superstructures #106
Comments
Another possibility would be to allow https://gedcom.io/terms/v7/enum-BIC might have:
instead of what it has now:
The former is more specific than the latter, since multiple structures have type |
This is one proposal to address #106 Signed-off-by: Dave Thaler <[email protected]>
GEDCOM Steering Commitee Discussion 11/30/2023: |
Per GEDCOM Steering Committee discussion on FamilySearch/GEDCOM.io#106 Note that this does not affect what is permitted in GEDCOM, it just improves the ability of tools to validate what is permitted. Signed-off-by: Dave Thaler <[email protected]>
In the YAML file format,
superstructures
is not allowed for enumeration values.This limitation resulted in bugs like #100 since it could not be validated. If instead, https://gedcom.io/terms/v7/enum-BIC had had something like
then the bug with
would have been automatically detected.
The text was updated successfully, but these errors were encountered: