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

Potentially dubious type 2 diseases #400

Closed
1 of 3 tasks
cmungall opened this issue Sep 29, 2017 · 2 comments
Closed
1 of 3 tasks

Potentially dubious type 2 diseases #400

cmungall opened this issue Sep 29, 2017 · 2 comments

Comments

@cmungall
Copy link
Member

For general background see #149

Briefly: At time t1, we have a disease D. At time t2, there is a purported discovery of a new type, which gets called D2. This effectively renders D a prototype.

The question then becomes how to interpret the semantics of D. The clearest thing to do is to make D generic and have an explicit subtype D1 (sib of D2). However, in many cases the purported D2 may turn out not be real, in which case we are left with a single-isa hierarchy with no difference between D1 and D. If D2 does turn out to be real it results in confusion over what D means, with some mentions in the literature presumably denoting D1. However, in these cases referring to D1 as D is not wrong, just lacks specificity.

This ticket is for collecting discussion on what type2s we believe to have insufficient evidence to warrant breaking down D. Check the box if we think insufficient evidence

@cmungall
Copy link
Member Author

In #399 @pnrobinson suggests an n=1 tag. We could do this as a subset tag (inSubset in OWL).

If we do retain the n=1s, then I think the relationship to the generic form should perhaps be something other than SubClassOf, to avoid true path violations. analog_of, phenocopy_of, ...?

@nicolevasilevsky
Copy link
Member

This issue was moved to monarch-initiative/mondo#162

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

2 participants