Pavel Grafkin

@pbr6cornell, @hripcsa, @PRijnbeek, @gowthamrao, would be grateful for your review and ideas! tagging @gklebanov

> E.g. is there enough people of the phenotype in question Good point, @gowthamrao . This means that a user should be able to browse and extract sub-entities (nested entities)...

@PRijnbeek, thank you for your feedback > The question is do we need to add functionality in Atlas or in another tool like we have for the vocabularies now. Athena...

Although the **proposal 2** itself sounds good and allows to remove `location_history` table, I would be very careful with the general idea of untypified relations. Having more flexibility, you lose...

I would propose to treat `fact_relationship` table as a POC table. So that when you have a new use-case which requires some new relations between tables (but those relations don't...

> Right now, like in location_history, we recommend new tables in CDM WG based on expert opinion - and not a POC. If we take a POC approach, then one...

@rtmill , for me it sounds that you go to extremum, why don't you want to end up then with a single table with three field - "subject", "relationship", "object"...

@schuemie , why cannot we use hashing to create the covariate ids? So you'll concatenate all the original IDs and run a hashing function over the string. This is both...