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

[Valdator] Support dependent profiles #137

Open
ewoutkramer opened this issue May 25, 2023 · 1 comment
Open

[Valdator] Support dependent profiles #137

ewoutkramer opened this issue May 25, 2023 · 1 comment

Comments

@ewoutkramer
Copy link
Member

HL7 has published a few extensions that we could implement and influence validation of profiles:

That last one looks like an optimization to me, and we already have this logic implemented in the new validator (if an instance is valid against a profile X, the instance is also valid against all parent profiles of X).

@marcovisserFurore marcovisserFurore transferred this issue from FirelyTeam/firely-net-sdk Jul 20, 2023
@ewoutkramer
Copy link
Member Author

ewoutkramer commented Sep 12, 2024

Operationally, I don't see what the results of that validation would do - except if you want to mark meta.profile with profiles against we have validated conformance. Then you can put both there.

The first one is basically saying: after finishing validation, continue with the profile given in the extension. I'd say just start a new validation and include the results in the end schema. We might want to double check that the locations and messages make sense if we have multiple profiles in use, but we do something like that when we validate meta.profile, an extension (which is another structdef) or a referenced profile (typeRef.profile), so it is not new.

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

No branches or pull requests

2 participants