NamespacePrefix contains external sources that we don't capture

[korikuzma]

I'm not sure if this is intended, a bug, or just outdated so creating general question for this.

I recently updated my ddb (disease_norm_update --update_all --update_merged) and noticed that some members in the NamespacePrefix enum do not exist in my ddb. For example, NamespacePrefix.DECIPHER does not exist in my ddb data. Is this intended? Should we include members in this enum that do not appear in the data? Did these members exist in the data at some point?

[jsstevenson]

We definitely imported DECIPHER xrefs at one point, but their scope can vary between equivalentTo and relatedTo and we don't really want to be capturing the latter if we can help it. I think there would be some work on an upstream library to support parsing of the trailing modifiers that designate that relationship in the OBO release.

[korikuzma]

Namespace prefix members we don't capture: