Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce a way to explicitly document conflation decisions #311

Open
matentzn opened this issue Aug 18, 2023 · 0 comments
Open

Introduce a way to explicitly document conflation decisions #311

matentzn opened this issue Aug 18, 2023 · 0 comments

Comments

@matentzn
Copy link
Collaborator

matentzn commented Aug 18, 2023

Defining mappings across semantic spaces is a hazy business, because the conceptual models underlying the semantic spaces we are mapping are rarely explicitly defined. Even when mapping between two resources that model entities from the same category (disease, gene, phenotype, chemical entity), the underlying conceptual models can differ quite a bit, so there is always some level of conflation (even if what ICD 10 calls a disease is something else then what Mondo defined as a disease, we still want to map ICD10:Diabetes to MONDO:Diabetes for practical reasons). It gets worse though when we have some resources distinguishing certain categories cleanly (say, disease from disease susceptibility, or disease from clinical finding, or disease from disorder) and another that conflates them into the same hierarchy (e.g. diabetes is a "clinical finding/phenotype" and not a "disease").

Some people will just conflate, and not document, no matter what we preach. I would prefer to just provide a way to somehow say: in this mapping, we conflate the two (i.e. we use skos:exactMatch where we should have used skos:relatedMatch).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant