@bpow Changed the AlleleConservation.conservationType to conservationOutcome and added the additional value set concepts to allow the "negative and unknown" outcomes to be options.
Note: in doing this, I discovered the duplication of "conservationType" on the AlleleConservationScore which was removed. We currently use the Statement.evidenceLine to provide a mechanism for showing the AlleleConservationScore that was used to make the qualifiying statement AlleleConservation. So I did not think it wise to duplicate the qualified outcome on the Score statement since it is a conflation of statement types. @bpow can you weigh in on this?
@bpow Changed the AlleleConservation.conservationType to conservationOutcome and added the additional value set concepts to allow the "negative and unknown" outcomes to be options.
Note: in doing this, I discovered the duplication of "conservationType" on the AlleleConservationScore which was removed. We currently use the Statement.evidenceLine to provide a mechanism for showing the AlleleConservationScore that was used to make the qualifiying statement AlleleConservation. So I did not think it wise to duplicate the qualified outcome on the Score statement since it is a conflation of statement types. @bpow can you weigh in on this?