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
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).
The text was updated successfully, but these errors were encountered:
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.
HL7 has published a few extensions that we could implement and influence validation of profiles:
"Instances can only be valid against this profile, if they also successfully validate against the profile referenced by this extension."
"Asserts that instances that are valid against this profile are also automatically valid against the StructureDefinition referenced by this extension."
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).
The text was updated successfully, but these errors were encountered: