-
Notifications
You must be signed in to change notification settings - Fork 149
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
Add forward-compatible flag to validator #517
Comments
this seems like a very unlikely change to make for the validator. There'd really be no way to decide if the content was valid or not |
If a validator is being used in a production system, and the production system wants to be 'forward compatible', this is needed. It's fine to spit out warnings saying "hey, this thing isn't valid in the version of FHIR you're using, but might be in a future one". But they wouldn't want it to raise an error. That's definitely a validation thing. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions. |
(from https://jira.hl7.org/browse/FHIR-13414)
The commitment of "normative" in common use is "no breaking changes". Acknowledging that the precise definition is TBD, one aspect I've heard frequently is the ability to add optional, non-modifier elements to existing resources. The intention as I understand it is for systems with normative definitions to ignore these new elements.
In practice today however, all validators reject resources with elements not included in the release of FHIR validated against. This means that a post-normative addition would be rejected by a validator using an earlier normative release.
Make the change and also provide documentation for other validators to follow (and/or test cases)
The text was updated successfully, but these errors were encountered: