Open yogeshbdeshpande opened 1 year ago
CoRIM can handle an EAT profile type now that #77 is resolved. It would be helpful if EAT profile could support a CoRIM profile type too. But this seems like an issue with EAT rather than CoRIM. Should this issue be "won't fix"?
I vote close. I think we've decided this belongs to the evidence -> internal representation transformation specification, which is separate from the CoRIM profile for values that can match the internal representation.
Issue is inherited from the parent Issue #77 : where profile extensibility is discussed.
However the profile type choice for CoRIM differs from EAT Profile Type though the intent of the profile is the same!
Should we consider harmonization of EAT profile type and CoRIM profile type?