Currently the interlinking method that is declared in config for annotations applies to all matching AnnotationTypes. There should be a way to differentiate the semantics of the AnnotationTypes in different lists. For example, the AnnotationType ABBREV in a Code might want to come out as skos:prefLabel whereas in a Concept it might be skos:altLabel. Moreover, the best approach for this would be to differentiate based on the identifier. The config should take in the identifier (of a Concept or Code) in which to apply the interlinking to. Consider also implementing a catch all approach (sort of like how it currently works now).
Currently the interlinking method that is declared in config for annotations applies to all matching AnnotationTypes. There should be a way to differentiate the semantics of the AnnotationTypes in different lists. For example, the AnnotationType ABBREV in a Code might want to come out as skos:prefLabel whereas in a Concept it might be skos:altLabel. Moreover, the best approach for this would be to differentiate based on the identifier. The config should take in the identifier (of a Concept or Code) in which to apply the interlinking to. Consider also implementing a catch all approach (sort of like how it currently works now).