biolink / biolink-model

Schema and generated objects for biolink data model and upper ontology
https://biolink.github.io/biolink-model/
Other
171 stars 71 forks source link

FMA identifiers don't resolve #1458

Open cbizon opened 7 months ago

cbizon commented 7 months ago

There are many mappings from biolink predicates to FMA terms. They mostly look like readable identifiers.

FMA:connected_to
FMA:continuous_with
FMA:homonym_of

Using the expansion in biolink_model_prefix_map.json, these get expanded to things like: http://purl.obolibrary.org/obo/FMA_connected_to

But these IRIs don't resolve.

Interestingly, FMA has these relationships in its class structure rather than as properties, and they have the normal kind of numerical identifiers. e.g. the first relation there should be replaced with: http://purl.obolibrary.org/obo/FMA_62802 "connected_to relation"

cmungall commented 7 months ago

Note also that FMA currently resolves to a very old artefact, there is an almost decade old issue about this: https://github.com/OBOFoundry/OBOFoundry.github.io/issues/21

On Wed, Feb 21, 2024 at 7:59 AM cbizon @.***> wrote:

There are many mappings from biolink predicates to FMA terms. They mostly look like readable identifiers.

FMA:connected_to FMA:continuous_with FMA:homonym_of

Using the expansion in biolink_model_prefix_map.json, these get expanded to things like: http://purl.obolibrary.org/obo/FMA_connected_to

But these IRIs don't resolve.

Interestingly, FMA has these relationships in its class structure rather than as properties, and they have the normal kind of numerical identifiers. e.g. the first relation there should be replaced with: http://purl.obolibrary.org/obo/FMA_62802 "connected_to relation"

— Reply to this email directly, view it on GitHub https://github.com/biolink/biolink-model/issues/1458, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAMMONDEJJZ62SPWSJDD63YUYKWNAVCNFSM6AAAAABDTKEGQGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE2DOMJSGE4DSNA . You are receiving this because you are subscribed to this thread.Message ID: @.***>