-
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 acceptUnknownHL7Extensions flag #910
Labels
Comments
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
from https://jira.hl7.org/browse/FHIR-31721:
Will submit a Git issue asking for a flag to be added to the validator that says "acceptUnknownHL7Extensions" that will handle the special case of the stricter validation that we apply to HL7-defined extensions that would choke at seeing extensions from an unrecognized version. This same extension should also make extension validation more lenient - i.e. don't presume that the definition available in the current version for the HL7 extension is the right one and treat validation errors against a defined extension or missing extension as warnings rather than errors.
I have no idea what this is supposed to do though. The way it's described doesn't match how the validator actually works, so nothing will happen unless someone/ some committee provides a clearer description that matches how the validator works. e.g why would there be an unrecognised version? Why wouldn't the definition be the right one? Why wouldn't there be errors if the extension is wrong?
The text was updated successfully, but these errors were encountered: