Closed mcourtot closed 5 years ago
I think it makes sense to have two classes, ancestral population and cultural(?) population, with an annotation property indicating the mutual proxy relationship. Individual subclasses may be linked with logical axioms indicating overlap.
Closing this issue due to inactivity. Please file a new ticket if this is still relevant.
Based on some reading [1,2,3] it seems ancestry defines who your grandparents were, while ethnicity refers more to your current cultural environment (which impacts your diet, level of exercise, smoking status...). It'd be great if we could define and use those consistently.
[1] https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3237839/ [2] https://health.clevelandclinic.org/2014/03/how-your-ancestry-and-ethnicity-affect-your-health/ (has nice examples) [3] https://humgenomics.biomedcentral.com/articles/10.1186/s40246-014-0023-x
@cstoeckert says : Regarding ethnicity versus ancestry, I agree that they are different and it would be very helpful to have that difference defined! Ethnic group makes sense to me as a population (material entity) but not sure about what kind of entity is implied by ‘ancestry’. Is it a population with grandparents from a common geographic location?