You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How we validate a codelist from a 3rd-party standard is an open question. It's not obvious to me that embedding the codes as an enum in JSON schema is the best way to go.
The critical issue is: what happens when there are changes to the 3rd-party codelist. How does that change get incorporated into validation of BODS data?
jurisdiction/code should be an ISO_3166-2 2-Digit country code, or ISO_3166-2 sub-division code.
country/code should be an ISO_3166-2 2-Digit country code.
We don't use an enum in the schema, so perhaps a warning is appropriate.
The text was updated successfully, but these errors were encountered: