[mdht-dev] Validation Properties

[Sean Muir <sean.w.muir@xxxxxxxxx>]

Dave -

I was updating the validation stereotype to add to additional attributes

I noticed in the code set we have code such as to populate severities - 

Enumeration severityKind = null;

 

Profile cdaProfile = CDAProfileUtil.getCDAProfile(modelElement.eResource().getResourceSet());

if (cdaProfile != null) {

severityKind = (Enumeration) cdaProfile.getOwnedType(ICDAProfileConstants.SEVERITY_KIND);

}

Two questions - How come we do not leverage the Validation eclass (assume this was a timing issue with static profiles)

second - we end up loading the profile numerous times - based on the model element - this seems inefficient and was wondering if there was a particular reason

Thanks

Sean